etclabs / oscrouter Goto Github PK

Failing to build with Xcode 12.0

"Command PhaseScriptExecution failed with a nonzero exit code"

Build target OSCRouter_2022-03-26T15-02-58.txt

Would like to use OSCRouter on a show coming up. I had used this program before and don't believe I had to compile with XCode first. Is there a place to just download the built App?

thanks!

I noticed that outgoing TCP packets are not logged. Is there a particular reason for this?

A Raspberry Pi support will helpful which is configurable through a web interface, like Companion Pi.

Hello,
unfortunately i can't say much about the context because i'm trying to help a remote user that get this error once in a while on specific messages.
Thoses messages don't have arguments, and apparently the error appears approximately one out of 3 times, not in a regular way.
Some other messages seem to never rise this error.
I looked up the code, and general udp error but couldn't find anything about error 64..
Any idea ?

Thanks

Like others I'm really interesting by a linux version. Is there any chance that you integrate a linux version in future releases?

Unable to forward messages that are under a size of 12:

IN [192.168.1.105:3021] [OSC Packet] /gyrosc/comp, 197.462(f)
OUT [192.168.1.102:3002] error, malformed bundle of size 8, expecting minimum size of 12

I think the minimum size should be 4.

On windows. when there is no network. and then when a new wifi network is connected. we need to open the app and hit 'Apply' OR close it and reopen it in order to make it work

Hi I cannot add more then 41 lines!!! This is painful, awc. Cannot open app anymore! TEST IT, mac os X used.

Add a simple route:

Incoming Port: 5001
Incoming Path: /path/to
Outgoing IP: 127.0.0.1
Outgoing Port: 5002
Outgoing Path: /path/to

Go to "TCP Settings..." to add a TCP Server

Mode: Server
Framing OSC 1.1
IP: 127.0.0.1
Port 5002

Now connect to the TCP server though telnet:
telnet 127.0.0.1 5002

Connection is immediately dropped, log goes into a loop

Sat 09 Feb 2019 [16:42:19] tcp server 127.0.0.1:5002 new connection(0.0.0.0:0)
Sat 09 Feb 2019 [16:42:19] tcp client 0.0.0.0:5002 thread started
Sat 09 Feb 2019 [16:42:19]  initialize failed, already initialized
Sat 09 Feb 2019 [16:42:19] tcp client 0.0.0.0:5002 reconnecting in 5...
Sat 09 Feb 2019 [16:42:24] tcp server 127.0.0.1:5002 new connection(0.0.0.0:0)
Sat 09 Feb 2019 [16:42:24] tcp client 0.0.0.0:5002 thread started
Sat 09 Feb 2019 [16:42:24]  initialize failed, already initialized
Sat 09 Feb 2019 [16:42:24] tcp client 0.0.0.0:5002 reconnecting in 5...

On macOS in darkmode, the help text is not good readable because it is black on grey. It should better white on grey.

Hi all,
unfortunately for me latest version crashes for me. I posted the Apple crash report here. https://pastebin.com/Y9ev8xWu
Let me know if you need anything else.

Hello, I know this isn't a bug or issue.

I am wondering if there is any chance of this working on a linux distribution. OSCRouter has been great when I bring my computer to the venue and can get a bunch of tablets talking to EOS at the same time. (the .255 broadcast is hit or miss) Now the venue want's to make it a permanent thing so I'm wondering if there is any possibility of using a Raspberry PI instead of a full fledged computer since this would be the only task.

Trying to filter out floating point values of incoming OSC. It looks like the values are floating point, so aren't being filtered properly by the min/max fields. Does anyone know how to make filtering work?

Fri 06 Sep 2019 [13:43:49] IN [127.0.0.1:5555] [OSC Packet] /atem/preview/1, 0.000(f)
Fri 06 Sep 2019 [13:43:49] IN [127.0.0.1:5555] [OSC Packet] /atem/preview/2, 1.000(f)

Long story short, I want to use the messages with a value of 1 and discard the rest.

Thanks,
Alexander

In the IP address field, DNS names can be entered but don't resolve. This would be quite helpful when it's not practical to make devices have static IP addresses. Such as iPads and the like.

Running Eos 3.0 (Yes I know I need to update it) and Qlab 4.6.11. The OSCRouter makes things work but...

I would like to trigger specific cues in qlab for different cues in Eos.

Right now, whatever Q# in Eos is fired, it triggers that same # in qlab. I would like it set up based on this example: LQ 3 triggers SQ2.

I just installed OSCRouter today so still very new to it. Got it working based on the online documentation about what settings to put in. Is there different text to for the incoming and outgoing path for this?

Current incoming path: /eos/out/event/cue/1/*
Current outgoing path /cue/%6/start

As I said, very new to this (not new to Eos or Qlab, just getting them to talk to each other) Any help would be appreciated. Thank you in advance.

Hey,
the Download version of OSCRouter crash on my Mac System direct at the startup.
My System:
Mac Pro 2 x 2,4GHz Quad-Core Xeon
6 GB Ram
Mac OSX 10.8.5

any Ideas ?
Greetings Peer

Hi all,
Have a situation where I am making my EOS broadcast to the network broadcast address (192.168.0.255 in this situation). The OSC monitor software on my computer can see the incoming OSC but the OSCRouter on the same computer cannot.

If I set the OSC UDP TX IP on the EOS to my computer IP directly the OSCRouter works, but this means it is not broadcast (and I am trying to trigger to independent QLAB machines at once)

Looking through the commits I can see there was a commit on 24 March 2016 which references this but it doesn't seem any files where changed and I can't see associated issue in the repo.

Is this a bug or (more likely) user error, that I cannot get OSCRouter to listen to incoming broadcast OSC?

Cheers

Update: I have now realsied you can enter multiple IPs separated by spaces in the OSC UDP TX IP which allows me to point the console at every computer so I have an issue for the workaround. I am leaving the issue up though as I believe it is still a correctly identified issue.

Every once in a while some OSC strings are not received to route. Receiving from EOS Ti sending to QLab. The string to fire a cue is not displayed in the log, but shows the updated pending next cue. This causes QLab to "miss fire" a cue as it is not sent the OSC string.
This is inconsistent.

Actual address : /composition/video/effects/strobe/effect/frequency
Resulting address : /video/effects/strobe/effect/frequency

• Need to strip the 1st parameter : /composition/video/effects/strobe/effect/frequency

Please let me know how to do it....!

A simple way to enable high-resolution mode on supported OS X machines (i.e. any with "Retina" displays) is to add the following to Info.plist:

<key>NSHighResolutionCapable</key>
<true/>

In addition, to prevent the application forcing discrete graphics over the CPU's iGPU:

<key>NSSupportsAutomaticGraphicsSwitching</key>
<true/>

...though it doesn't seem to require discrete graphics as it is, but just to make sure.

Using %0 in the output path while packets are being forwarded causes a crash.

Ex: /eos/cmd="Chan 999 Pan" %0

Thank you all for developing this great tool!

To synchronize Ableton Live and an ETC EOS I need the possibility to remap an OSC-argument to a part of the path, i.e.

Ableton sends "/cue 1" -------> EO recieves "/eos/cue/XX/1/fire"

Is there a possibility to intruduce another variable, like !1, !2, etc. or something similar, to use the argument in the output-path?

The tooltip seems to imply that it does:

But in practice, I'm seeing an incoming ICMP ping coming in the input side but not going out the output side.

I don't know how to resolve this issue, but I'm going to do my best to explain what is happening.

I set up the OSC Router so it can convert the Ion's fire language to a another that Qlab can understand. It has been working inconsistently throughout the week. Sometimes, the sound cues will delay from firing or not fire at all. Yesterday, it worked perfectly, but tonight it stopped working altogether. I'm perplexed as to why this keeps happening. Anyone who has insight on this issue, your advice is crazily appreciated.