ProppFrexx ONAIR User-Forum

I have set a sweeper to play at Next Of Previous Track.
Sweeper starts playing as it should at the correct position of previous track.
There are times that the fade curve at the next track is shorter than it should.
So the sweeper continues to play over start of next track but the track volume returns to 0dB while the sweeper has not finished yet.

Regarding the 'transition':
I guess I see what might happen... if no cue-points have been set so far for a next track; in that case the transition will happen based on this - but once the track is loaded to the DJ Players, the ACDP (Automatic Cue Point Detection might have been enabled) and as such the CueIn position might 'shift', resulting in the transition volume-points ending too early.
I have already fixed that here, so the next version will cover that scenario as well...

It's happening in most of the tracks.
Those are automatic track-insert-transition. (I haven't tried Drag&Drop yet).
As I said it's at Next Of Previous Track.
I have't touched any cue points. I 've let it play and listen.

By the way, yesterday while the 09:00 to 13:00 playlist was playing (the same script), about 11:00 a transition started at the Next of previous track and then the playlist stopped playing. I had to click play (F9) to start playback again.
I was working and just listening to what pf was playing.

The script was already playing for 2 hours when this happened !
So b) = False;
About a) I can not find if something was corrupted. But I don't think so because with F9 started playback normally.

The script was already playing for 2 hours when this happened ! So b) = False

Why? Was it playing the same track over and over again?
I was talking about a track related option and not a script-line related option.
When you once send me some of your jingles to test with them, I have seen, that some of them already contained some track related options.
So maybe while testing things, you have set such an option on one of your tracks...and as the script might have just picked such a track...it stopped.

b) could still be valid, as I said it might be 'corrupt' in such a way, that its natural end could not be detected, which prevented the triggering of the start of the next track.
As such, the file was 'playable' - but its decoding stopped prematurely.
F9 simply starts the next track (which is not 'corrupt').
But as said, unlikely, but possible.

Is that happening with every of your tracks or only with certain tracks?
Was that an automatic Track-Insert-Transition or a manual one (via Drag&Drop), if yes to which element (currently playing, next or any other)?
Did you possibly recalculate or changed some cue-points of the previous or next track (e.g. the next cue point of the current track or the cue-in point of the next track)?

As in a short test here I couldn't reproduce the issue here.

I'll take a look at the transition issue...

Regarding the stopped playback - there are basically only two possibilities:
a) the audio file was somehow 'corrupt' so that the decoding stopped somewhere at end not being able to trigger its natural end (unlikely, but possible)
b) the 'StopAutoPlay' or 'StopAtEnd' option was set with the related media entry (track) playing at that moment

Fixed in v3.0.13.6!

Not fixed for me.
I am sending you (with pm) a video to see.

In the video I can not see what you did before hand and what exactly is wrong.
In my tests here it is working fine.
Please explain in detail step by step what you did to test things...so that I can clearly reproduce that here.