This command doesn't work when it's in the playlist, it only works if it's a single command in the event, or it's a multi-action event and this command is the first action. This is a limitation.I found with the most recent update that CueNextOnEnd does not work when inserted in the scheduler as an event but it does work when inserted as a multiple followed by a track. Is this by design or a bug?
Can you please specify what function needs explaining?Perhaps a tip to make some more videos with explanations of new functions.
The command fades out the current track, but after finishing the fade and starting the new track, the track that ended is heard again at full level for approximately half a second.next 10000 CueNextOnEnd
Hello Dmitry, I have the following command
The command fades out the current track, but after finishing the fade and starting the new track, the track that ended is heard again at full level for approximately half a second.
This is not new, it happens approximately 40% of the time, but it is quite messy on the air.
Thank you, this will be checked.The command fades out the current track, but after finishing the fade and starting the new track, the track that ended is heard again at full level for approximately half a second.
This is not new, it happens approximately 40% of the time, but it is quite messy on the air.
Does it always happen or only occasionally?We have also experienced this problem and avoid using the command at the moment...
This error still appears 40% of the time, in the latest versionThank you, this will be checked.
Does it always happen or only occasionally?
Interesting. How do you call this command, is it inserted into the playlist (by the event or manually) or you have an event that runs it?This error still appears 40% of the time, in the latest version
The track that is cut (music) is usually music with the normal crossfader parameters. the one that starts is this type of file (Comercial)Thank you, the track that plays before it, does it have a custom custom crossfade or custom parameters set in the Track Tool? It does not reproduce here with the latest version, so I suppose some other conditions must be met.