Open Beta Version 3.8.0
Issue with out of sync playback is fixed in the new Beta 8869. 6 tracks songs are playing perfectly. When I add 2 more tracks to test all available slots in a multitrack song ST3 playing those 2 new tracks out of sync. Restarting the app solves that problem. Crossfade between 8 tracks songs is smooth, no issues there.
- Edited
Damir Exporting selected songs from a playlist crashes on iOS. Works only on macOS. This will be fixed in the next update. But I can not reproduce your loading issues. If I export 2 songs, then delete one of those songs and load the exported file, all load options work as expected.
SignalProducer Could you send me your logfiles anyway? I would like to take a look at how long the playback now needs to initialize on your device.
Btw, I guess the next update will be the release candidate. I feel confident that version will be stable enough for general release. So most likely the release of version 3.8 will be next week
Thats strange, i will do the test again perhaps it could be something to do with me creating the exported files in ST3 and importing them in to the Beta version, i havent tried exporting on Beta and importing on beta, perhaps i will try both again.
peter Exporting selected songs from a playlist crashes on iOS. Works only on macOS. This will be fixed in the next update
Perhaps that’s why I experienced the fault I might have used playlist export, I have tested song .stsa export using ST3 to Beta to export in song mode on iPhone and also beta to beta and it works fine so I will keep a close eye on this feature , I think it’s a lot simpler to use now that the renaming is labeled better and I like the self naming of exported files it works for us quite nicely and we can always rename the export if specific naming is required.
Well done.
New Beta build 8874
Finally, this is the release candidate for version 3.8.0
If nothing unexpected happens I will release the final version next week.
Thanks for all your feedback!
Changed
- Updated what's new dialog
Fixed
- Crash when sharing multiple songs from within a playlist
- Possible crash on iOS17 and macOS Sonoma when opening multitrack configuration in new song
- Possible crash when using the search functionality
Hi Peter, feedback, i have saved on ST3 my full playlist i use to perform which has 377 songs in .stsa format and i successfully imported this file in 3.8 beta but i noticed something, having 377 songs it takes a lot of time to create the .stsa file and there is no indication that the software is number crunching so the user thinks nothing is happening the same thing as you import this file it takes ages but there is no indication anything is happening i almost shut down the software to restart it thinking it froze but i suspected it was taking time so i persavered and sure enough yes it all eventually worked , we need a visual spinning wheel to let us know to be patient.
Secondly i still dont know how to import .stpl files , i can export in this format but i cant work out how to import this file format, or am i missing something?
Had 2 large gigs lately and kicked ass but i am always having the same issue with hitting the area which drops down the main screen which is rather frustrating because when i stop play to engage the crowd and then i go to select my next loop i actually accidentally bring down the screen which is at the moment where i am totally engaging the crowd and its the last thing i need to be unnecessarily interrupted by something i never want , this has happened at least one every gig , its really off-putting to use loops, hope you c@n come up with a solution.
Im really looking forward to the new features especially the visual metronome i could have really done with it last two gigs , i can really see its potential now.
Great work!
Hello everyone,
Last night I used Steve's great application for the first time in concert (previously I had my samples on Beatbuddy controlled by pedals and the lyrics in PDF).
I encountered a problem and I don't know if it's related to the beta version or to my configuration, so I'll detail it all for you:
The problem encountered is that there is latency between the moment I press my airtun pedal and the audio starts. This poses a problem every time we make an introduction before starting the audio (example if we do a simple restart on the bass and the audio must start on the 3rd beat of the measure, this does not work, the audio starts later on the 4th or 1st of the next measure and it's annoying because I can't anticipate it, even by pressing a little before on the pedal I can't get it in tune, which does not occur on the beatbuddy which starts the moment you press).
I initially thought that this could be due to the fact that the tablet was connected via bluetooth to my xr18 sound system, so I connected a cable to the headphone output but that didn't work either
My tested configuration:
- iPad Air 2 iOS 15.7.9
- Traxx3 BETA training application Version 3.8 (8874)
- Another musician connected to my session to view his scores always at the right time (it's so great, well done Peter!)
- Air turn PED PRO bluetooth pedal (I also tried with an iRig BlueTurn and it's the same thing, and even without a pedal I feel this lag by simply pressing the green play button on the application)
- The titles were multitrack (with only one active track - Drums)
Thank you very much for your clarification, has anyone ever had this problem?
Olivier
(Message translated by Google translate)
- Edited
peter
Hi Peter
Sorry but as you will see in my last post, this latency problem does not seem to be resolved, I am having a problem with this (more details in my post)
Is there a way for me to measure this latency to compare it between a single track song and a multitrack for example, or also between version 3.7.5(8793) and 3.8 (8874) in the different modes please?
Thanks again for all this work
Olivier
I add that I have just tested the following:
If I create a single track title with just a kick in audio, and the same audio on a multitrack title, I can see that:
- On the single track, we hear the audio at the same time as the Play button turns red (for pause)
- On the multitrack, the sound comes after seeing the red color of the button
(I don't know of any other way to measure latency more precisely, sorry ;-)
Damir You are really pushing the boundaries. I have to admit I have never envisioned someone using the export feature to export 377 songs which is more than most users have in their whole library. I thought this feature would be primarily used to transfer a bunch of songs. Maybe 10 or 20 which is more or less exported within a second or so.
Regarding stpl loading: You need to load it with the share with Stage Traxx option. It is meant to send playlists (withou songs) to your bandmates and you will do that most probably via email. So when you receive the file via email it will automatically open it in Stage Traxx.
Olivier Multitrack songs need 250ms to prepare playback. This is necessary to line up all the tracks to play them in sync. There is no way around this. So if you need play to work without delay you have to stick with stereo files. Here the usual delay is about 10ms.
peter
Thank you Peter for the answer but it seems to me that this latency was not there even in multitrack on version 3.7.5(8793) right? Have you measured the latency in 6-track multitrack of this version please?
If it is minimal, many users who are used to using it may prefer to stay on 6 tracks without latency than with 8 tracks with difficulties to be in sync live... Not easy.
- Edited
Multitrack playback always had 250ms latency in all past versions. I only tried to lower it to 50ms in the first beta version but had to revert that change later as it would lead to out of sync playback on some devices.
Maybe you accidentally enabled the start delay in Settings > Playback Settings if the latency feels bigger than in version 3.7.
peter
Thank you for your always precise answers. It doesn't matter, I'll make songs with a single file for times when latency needs to be reduced, it's already great as it is! (I checked my start delay is well positioned at 0.0s, it must have been the same with the previous version you are right, it is difficult to measure when you are not in live condition, I did the test today by activating a metronome and clicking on play but we will especially see in Live situation at the next concert, I can't wait! You have boosted the passion, I will be able to increase creativity thanks to your application).
- Edited
peter You are really pushing the boundaries. I have to admit I have never envisioned someone using the export feature to export 377 songs which is more than most users have in their whole library. I thought this feature would be primarily used to transfer a bunch of songs. Maybe 10 or 20 which is more or less exported within a second or so.
Regarding stpl loading: You need to load it with the share with Stage Traxx option. It is meant to send playlists (withou songs) to your bandmates and you will do that most probably via email. So when you receive the file via email it will automatically open it in Stage Traxx.
I use ST3 where playlists are my whole gig , I have all my performance songs in all playlists , for very good reasons, I don’t rely on search as it’s awkward with my AirTurn foot switch hogs the keyboard so my way around it is, I start my whole playlist in alphabetical order then I arrange my 50 first songs I actually am planing for the gig to suit the requirements of the gig and my playlists are actually named to what the gig is, this then allows me to run to plan but if I need to change the order I just use my foot control to find the next required song if it’s not in my first 50 organised songs I can easily use my foot pedal to find the songs further as they are in alphabetical order.
Because I have three devices it’s a lot simpler to just transfer .stsa method as it’s quicker to transfer 4gb of data then full backup 22gb
But you don’t get any idea it’s actually doing anything as there is no wheel spinning around like when you load full backups, the consistency of operation is not there, which is confusing.
Regarding .Stpl files , this should follow .stsa file capability.I don’t have band members so I export and save to local devices , I normally am working on my iPad and when I want to load a song or text I usually use the import on the software then hunt down the folder it is in, then I hit import, I agree the other way is good too and I use that method also, but it’s confusing when you have different methods for different file formats, both systems should be available so things are logical and you can follow some consistent pattern of operation other wise people might not use these facilities which are great when you understand them, but they need to be consistent.
Regarding foot pedal delay , I run AirTurn stomp six and even with stereo files there is a slight delay, I know in multitrack there’s a lot more going on that’s why a greater delay, what I don’t understand is why the buffering doesn't happen as the song/loop is loaded and not while the play button is hit, I would expect instant start as soon as a song is chosen the buffers should be loaded and ready to go.
Is there a technical reason for this?
I have just finished another very big gig and have been let down by the damn screen dropping down again when I hit loops its making me very paranoid to the point of being scared to touch the screen and the foot pedal method is too slow to choose next loop as things are really happening fast when you are manipulating the audience.
Olivier Theoretically I could make the start delay configurable but the problem is that if you choose a delay that is too short, you might get slightly out of sync playback of the tracks. And here the issue is that this can vary from song to song. Some songs need only 20ms to start while others could even need 380ms. So I am not sure I want to open up this setting for anyone to change as it could lead to lots of support requests because tracks are not in sync.
@Damir The reason for ST3 preparing playback right before you start it is that the Apple Audio framework is very unreliable in counting time. Preparing the track when you load it can lead to the displayed time being off by a very large amount (even 30 seconds and more) especially when you move the app to the background and back. This is even worse when playing multitrack files as they could be out of sync by multiple seconds. So the only way I found reliable is to prepare playback at the time you start it. Then the timing is working reliably.
- Edited
Over the last two weeks I've used the 3.8 Beta exclusively at my gigs. This weekend alone a total of 11 hours gigging. It worked without a single flaw!! Not a glitch! Absolutely an amazing piece of work, Peter!
My concern is that with all these special needs that people have for ST3, it's gonna become a beast to maintain. Midi for this device, and then another, and yet another, file transfers in all formats, and the list goes on. I see the multi track/stem thing, but even that is going crazy. For nearly 20 years(!) I used a Windows XP program called OnStage Performer. I loved it for its (already then) audio regions, witch was the best thing ever. Yes, they were already there in 2003!
It was developed by two Canadians and as a prime Beta tester I got it working ok. I programmed midi for lights and VoiceLive harmonizer for hundreds of hours. I had two XP laptops for all these years, and I dreaded changing to the iPad world, because no backing track apps had the aurio region solution. Then when I saw that ST3 had the audio regions, I switched, and I swore NEVER to program a single midi command ever again for live shows. My pedal board is manual, harmonizer is aux out/in, and lights are steady. If you can play and/or sing well, the audience don't give a shit about your lights, whether it's flashing or steady, bright or dark. But they care if you sound awful. Keep it simple, please don't ruin the best piece of backing tracks software the world has ever seen with lots of crazy demands. Spend the time practicing instead.
This might not be a positive contribution to 3.8, but I simply get overwhelmed by many of the requests in here.
royandreno Agree!