You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The olad daemon has flags to set the RPC port used by OLA. Unfortunately, (almost?) none of the included command-line programs provide a way to specify an alternative port.
For example, ola_streaming_client, ola_set_dmx, ola_dmxconsole, and ola_dmxmonitor all seem to use the RPC server (default port: 9010), but none of them provide a way to use an alternative port. Internally, the C++ client class supports it, but the command-line tool doesn't expose this to the user.
This isn't a big deal for normal usage -- I don't think I'd ever want to run multiple instances, or need to use a non-standard port for my only instance -- but today I'm doing some troubleshooting and it sure would be handy in this case.
The text was updated successfully, but these errors were encountered:
Yes, agreed. For some of the newer clients (not the stuff in ola-client.cpp) it's probably possible to do them en-mass by adding a flag somewhere common, in the same way as the log level stuff is done.
The biggest challenge will be coming up with a good flag to use given we've got ports in the OLA DMX sense too...
I think I've previously suggested running two copies actually for some edge-case issues (maybe Art-Net related?).
Pull requests definitely welcome for this one, and should be a good little starter for someone!
The
olad
daemon has flags to set the RPC port used by OLA. Unfortunately, (almost?) none of the included command-line programs provide a way to specify an alternative port.For example,
ola_streaming_client
,ola_set_dmx
,ola_dmxconsole
, andola_dmxmonitor
all seem to use the RPC server (default port: 9010), but none of them provide a way to use an alternative port. Internally, the C++ client class supports it, but the command-line tool doesn't expose this to the user.This isn't a big deal for normal usage -- I don't think I'd ever want to run multiple instances, or need to use a non-standard port for my only instance -- but today I'm doing some troubleshooting and it sure would be handy in this case.
The text was updated successfully, but these errors were encountered: