I have setup universe 5 for handling osc input.
The port is set to 7704 ( by default) on 127.0.0.1
When I send a osc command to this port, no packets received.
However, the osc monitor which I use (kamperman utility) registers the osc command send on port 7704.
What can be the problem?
Sending osc from qlc works good….
Thanks for your help.
Paul
Windows 11
QLC 4.12 latest
Osc input not receiving
-
GGGss
- Posts: 3052
- Joined: Mon Sep 12, 2016 7:15 pm
- Location: Belgium
- Real Name: Fredje Gallon
Does your monitoring application run at the same time as QLC+? This is erroneous, since only one application can claim a network port.
Does the joystick wiggle when info is sent? If it does, you could create an input profile. If not, QLC+ does not listen to the network port... Verify with QLC+ running in a dos command prompt with this command: netstat -an. This should show you that port 7704 is present in the list (hence listening). Verify again with QLC+ __not__ running. The port should not be listed anymore.
Does the joystick wiggle when info is sent? If it does, you could create an input profile. If not, QLC+ does not listen to the network port... Verify with QLC+ running in a dos command prompt with this command: netstat -an. This should show you that port 7704 is present in the list (hence listening). Verify again with QLC+ __not__ running. The port should not be listed anymore.
All electric machines work on smoke... when the smoke escapes... they don't work anymore
-
SPS
- Posts: 70
- Joined: Fri Apr 05, 2019 9:51 am
- Real Name: Paul Misset
Ok. I have the monitor app shutdown.GGGss wrote: ↑Tue Jun 28, 2022 8:55 am Does your monitoring application run at the same time as QLC+? This is erroneous, since only one application can claim a network port.
Does the joystick wiggle when info is sent? If it does, you could create an input profile. If not, QLC+ does not listen to the network port... Verify with QLC+ running in a dos command prompt with this command: netstat -an. This should show you that port 7704 is present in the list (hence listening). Verify again with QLC+ __not__ running. The port should not be listed anymore.
With my qlc project open and I run Netstat -an, The port 7704 is listed.
However, Netstat does not indicates: listening.
The line says: upd 127:0:0:1:7704 *:*
And no foreign address or State
With qlc not running, the port is not listed as you said.
What now.??
I also do not see a joystick in the universe line…..
-
sbenejam
- Posts: 607
- Joined: Sun Apr 12, 2015 6:28 pm
- Real Name: Santiago Benejam Torres
- Contact:
As a test, try to uncheck and check the input checkbox again.
-
GGGss
- Posts: 3052
- Joined: Mon Sep 12, 2016 7:15 pm
- Location: Belgium
- Real Name: Fredje Gallon
There is another thread dealing with qlc+ not listening to network packets, in the latest version.
So give it some time so @Massimo can pick this up also...
So give it some time so @Massimo can pick this up also...
All electric machines work on smoke... when the smoke escapes... they don't work anymore
-
SPS
- Posts: 70
- Joined: Fri Apr 05, 2019 9:51 am
- Real Name: Paul Misset
-
mcallegari
- Posts: 4711
- Joined: Sun Apr 12, 2015 9:09 am
- Location: Italy
- Real Name: Massimo Callegari
- Contact:
Yes, which thread? 
-
GGGss
- Posts: 3052
- Joined: Mon Sep 12, 2016 7:15 pm
- Location: Belgium
- Real Name: Fredje Gallon
viewtopic.php?f=29&t=15642 - not related to OSC but smells network issues? No?
All electric machines work on smoke... when the smoke escapes... they don't work anymore
-
mcallegari
- Posts: 4711
- Joined: Sun Apr 12, 2015 9:09 am
- Location: Italy
- Real Name: Massimo Callegari
- Contact:
Not related. It's a specific OS2L protocol implementation issueGGGss wrote: ↑Fri Jul 01, 2022 8:15 am viewtopic.php?f=29&t=15642 - not related to OSC but smells network issues? No?
Can we see network traces (wireshark) of this thread issue?