When playing a track that has OS2L actions like "os2l_button" if the receiving TcpClient is not running then as each OS2L POI message is reached the track briefly stops playing while the waveform rapidly move backwards and forwards over the POI cue around 10 times before play continues. This happens on each OS2L cue and the music output stops for approx 1.5 seconds.
When the TcpClient is running and can receive OS2L messages everything is fine.
While I accept that you would expect the TcpClient to be running there may be times where this may not be the case, as in software failure or no requirement for DMX. In this scenario we would not be able to play any tracks that had embedded OS2L POI's.
Can this bug be fixed please?
When the TcpClient is running and can receive OS2L messages everything is fine.
While I accept that you would expect the TcpClient to be running there may be times where this may not be the case, as in software failure or no requirement for DMX. In this scenario we would not be able to play any tracks that had embedded OS2L POI's.
Can this bug be fixed please?
Posté Sun 10 Mar 19 @ 12:54 pm
djdad
Cant reproduce and not sure how TCP is used here. I run Sunlite Suite 2 whch has OS2L implementation, and no matter if its running or not, when track reaches the POI with os2l_button 'name' continues playing properly.
More info please
More info please
Posté Mon 11 Mar 19 @ 2:02 pm
Not sure what else I can add other than to show you: https://youtu.be/NQRKMYWOHng
If the receiving TCP / OS2L server is running all is well. If it's not running when a POI is reached I get the effect you see in the video.
If the receiving TCP / OS2L server is running all is well. If it's not running when a POI is reached I get the effect you see in the video.
Posté Wed 20 Mar 19 @ 1:01 pm
Adion
Do you use os2lDirectIp with a fixed ip perhaps?
Posté Wed 20 Mar 19 @ 1:57 pm
Ramirez48
i looked at your viedo and i had the same thing happen to me . my fix was making sure that your laptop updates we not only current but to make sure you restart you machine in order to complete updates.. clean ups quick scans optimize.. etc.. and don't start program until you know they took effect. this help me.
Posté Wed 20 Mar 19 @ 2:22 pm
Yes, it's utilising os2lDirectIp with a fixed IP and removing those settings clears the issue. However removing the IP address and port from os2lDirectIp then adding it back when the DMX software is or is not running is a pain. When using VDJ I do not always want to connect and run the receiving DMX software.
Do you think it could be coded in such a way that we can have "os2lDirectIp IP and port" set and it not stutter or perhaps an additional OS2LDirectIp ON/OFF setting if it cannot be fixed, at least it would remember the IP address and port numbers that way?
Do you think it could be coded in such a way that we can have "os2lDirectIp IP and port" set and it not stutter or perhaps an additional OS2LDirectIp ON/OFF setting if it cannot be fixed, at least it would remember the IP address and port numbers that way?
Posté Wed 20 Mar 19 @ 2:46 pm