For some reason my songs do not end, with the time settings that I have put in in the playback and trim section. I have it on auto play but if I had cut off 10 seconds or whatever the number is the next song will not start until that 10 seconds has expired.

Is this with version 3.4.3? I don‘t see this problem on my end. Does it happen with every song? Please try to reload the song metadata in the song details view.

    peter Version 3.4.2, I have been using this version for the last year and a half with no problems it just started with my performance yesterday. I have tried putting back in the numbers to the original length of the song, and re-trimming back to the settings that I want. But it adds whatever time I trimmed off the end of the song before the next song will play.

      JeffMueller Yes it happens with every song that I trimmed back. The only way I can do it now is to turn off the auto play, then the song will stop at where I cut it off at, but then I have to push the button to start the next song

      Ok, first please update to version 3.4.3. If the problem is still there, please send one of the audio files to support@stagetraxx.com. I will then try to reproduce the issue with your file as I don‘t see any problems with my files.

      I played around a bit and I can now reproduce the problem. This is definitely a bug and will be fixed in the next update.

      In the meantime this workaround will fix it: go to Settings -> Fade Settings and Set a set a crossfade length of 0.1 or 0.2 seconds. Now autoplay will work correctly and you will not really notice the short crossfade time.

      I did what you told me to do with the CrossFade.It works great. Thank you. I do not see anything to click on to do an update.

      Open the App Store and go to your updates or search for Stage Traxx and tap on Update.

      OK I got the app updated to 3.4.3. Thank you for your help. Even with the update I have to use the Crossfade that I have set at 0.1. It works fine like that. You are a blessing to me!

      The bug will be fixed in 3.4.4.