florence hi Florence yes it is possible to do this already, you can use it as a drum machine just place all your loops in permanent loop when creating the loops that you want as the main drum patterns and don’t select the ones you want as fills, yes you are correct the behaviour could be improved for drum machine type of control but at the moment we are just trying to get the basic concept to work really well for on stage.
There are still lots of little things that need tweaking and the idea of having a choice in settings to how the loops feature works is a really good one as I said ages ago the looping system feature of ST3 will make it one of the most advanced apps on the planet at this moment in time for on stage control of audio playback it has great potential to be able to serve many purposes without being ridiculously complicated.
Good luck with it.
I personally will also have a full playlist of drum patterns suited for all gender’s for those moments where you just want a basic beat accompaniment.
Open Beta Version 3.6.0
right, you understand my needs 
the only app that is doing that fine is Prime MultiTrack App but I really don't like the subscription requirements... Adding the feature here just in case:
• Section Looping: Loop and repeat any section
• Infinite Loop: Loop a section 1 time or infinitely
• Section Jumping: Jump in time spontaneously to different sections of the song
• Jump Time: Choose when Section Jumping takes place (end of section, after 1 bar, after 2 bars)
florence wondering if each region have preconfigured action when end is reach: continue on next region (default), continue on another region, or loop. would love to have this feature to use it as a drum machine
You can specify for each region if it should loop by default or not.
florence when do you schedule to release it?
I hope I can wrap up this release by the end of the month.
New beta build 8551
More bug fixes in this update. We are now moving towards the end of the beta. This means there will be no more functional changes. Only bug fixes and maybe some usability improvements. The next update will most likely be the release candidate.
Changed
- Updated "What's New" dialog
Fixed
- Constant flashing of current region in region editor
- Possible crash when seeking during playback
- Looping and scheduling audio regions at end of song not working
- Import of files through slow network connections aborts after 60 seconds
- Inconsistent behavior selecting regions when a song is revisited
peter I crashed ST3 a number of times but couldn’t leave feedback.
On iPhone 11 max pro I hit the playlist button than I scrolled the list than I hit the playlist button again that’s when the crash occurred.
But when I got the crash dialog to type in my report the keyboard that appeared was huge and the orientation could not be changed so I couldn’t fill in any information as the keyboard was unusable.
I crashed the software repeatedly but still no difference with fault report mechanisms it’s unusable on iPhone, am not sure about iPad.
- Edited
Damir The keyboard problem is a Testflight issue. I can do nothing about it. But you can reproduce the crash by scrolling within a playlist or in the list of playlists? Does it happen every time?
EDIT: I can't reproduce the crash on an iPhone 11. I also see absolutely no crash report for this. I only got one single crash report from Apple for the last Beta.
- Edited
Morning all.
Did a very quick test of the new Beta and reported fixes…
In the editor and while playing the region, if you use the ruler:
to move the playhead to just before either the start or end of the loop, the audio cuts off.
to move the playhead outside the region then click on the region, it enables flashing as expected. But then when you move the playhead back to within the region, the flashing continues indefinitely. It should stop flashing once it hits the end of the region and returns to the start of the region. Perhaps on playback stop it should also disable the flashing region.
Could you toggle the region lock icon to a locked/unlock icon? It's clearer than looking for grey/blue.
- Edited
Hi Peter tried to load new songs from live version to beta but .m4p files are not recognised- haven’t tried other types
When in loop edit and you grab the bottom handles and drag once the end of page view is reached the view should keep scrolling so you can keep on searching for final release point.
At the moment it just stops and forces you to reposition the view which is not efficient.
- Edited
DickyDutch How did you try to import it? From local files and then selecting the file from the ST3 non beta folder?
Damir When in loop edit and you grab the bottom handles and drag once the end of page view is reached the view should keep scrolling so you can keep on searching for final release point.
Hm yes. That's not ideal. I will see if I can do scrolling during the drag operation.
Samfbk hello, how to upgrade to the latest beta update? I am in 85 40 thank you
Open the Testflight app. The update will be available there.
- Edited
I've tried importing files as well but get error messages for m4a and mp3s. It worked fine last betas. I'm importing from the files app, files are on my iPad
Tried importing from stagetraxx non beta, still same error.
Emptysounds Yes, I see the issue now. The fix for importing over slow connections creates a new issue that prevents importing files from folders outside of the app folder.
Until the next beta you will need to copy the files with the Files app into the Stage Traxx 3 Beta folder and then refresh the song list.
Hello, Peter! Thank you very much for such an amazing program! I've been using it for running multitracks since November and it worked flawlessly for my band. With BlueBoard (start/stop mainly) and 2 CME Widi Masters I can control my 2 synths (presets changing and some automation) while focus on playing. Time coded lyrics (for song sections and chord structure) and Midi PC/CC became invaluable feature for me.
New Looping feature is a great addition for live performance. For some reason it behave not like I expected it to be.
Example.
If a song has structure like that:
A1-B1-Solo-B2
and I want to extend "Solo" section 2 times with Loop feature, I found that Time coded Lyrics+Time Coded Midi CC/PC+Visual waveform at the top are totally ignoring the Loop. So while "Solo" is playing for the second time (audio is fine), Visual waveform+Time Coded Lyrics+Midi messages "playing" next section "B2" for some reason (even when midi time code starts after first beat of the "B2" section). Because I rely heavily on Time Coded Midi messages to change presets I cannot use Loop feature at the moment. Is this a bug or a known limitation?
Another question. Is it possible to add option to ignore time code based lyrics and midi changes in a loop at the end of a section (like 1 sec before end) if that section will loop?
iOS 14.7.1 on iPad Pro 10.5 with 8551 version
Best regards, Sergey.
SignalProducer I dont't see this issue on my side. Timecoded lyrics and MIDI is sent in the loop and the waveform progress does also show the correct position in the loop.
Can you send me the song where you see this issue? Please use the new file format by enabling Edit Mode in the song list, selecting the song and then using the Share toolbar action. This will export your lyrics and timecodes so that I can try to reproduce the problem. Please send it to support@stagetraxx.com.
SignalProducer Another question. Is it possible to add option to ignore time code based lyrics and midi changes in a loop at the end of a section (like 1 sec before end) if that section will loop?
No, that's not possible. Lyrics and midi only see the current song position and react to that. They do not know that there is a loop.
New beta build 8556
A quick update to fix two pressing issues.
Fixed
- Possible crash when tapping multiple times on the playlist tab
- Import of files on iOS broke with last update
Peter I have had crashes lately when extremely zoomed in, when in loop edit mode and fine moving around the loop point crashed the software numerous times , I was on airplane without internet connection so I don’t think the crashes will be logged but it was definitely consistent, I have tried to reproduce it now that I’m back at home without luck so perhaps you have fixed this in the latest quick update.