Open Beta Version 4.0.0

peter

OK, I decided against another hosted solution for tracking beta feedback. Instead I have enabled all users to create new threads in the Beta forum. I have also enabled upvoting of threads in the Beta forum. I think with these changes, the forum has all we need for good feedback tracking and no need to register at a new website.

So for future feedback, please check first, if there is already a thread describing the issue or request you have. If yes, upvote that thread and if you want add a comment. If there is no existing thread, please create a new one.

I will prioritise my work on the number of upvotes a certain issue gets.

MarkGuitar

peter Hi Peter. Is the new way of working just for feature requests/changes or for suspected bugs as well?

AnthonyB

peter OK, I decided against another hosted solution for tracking beta feedback. Instead I have enabled all users to create new threads in the Beta forum. I have also enabled upvoting of threads in the Beta forum. I think with these changes, the forum has all we need for good feedback tracking and no need to register at a new website.

So for future feedback, please check first, if there is already a thread describing the issue or request you have. If yes, upvote that thread and if you want add a comment. If there is no existing thread, please create a new one.

I will prioritise my work on the number of upvotes a certain issue gets.

Did you want us to start new threads based on things previously mentioned above that we believe are still in progress even if you have acknowledged them? My thinking there is so that it is clear what some of the known issues are and trying to prevent re-raising of them? Or did you want to create a bunch of posts based on your own list (sorry, I know that is more work up front)?

musicadi

peter Great idea 👍💪Maybe we could also get rid of the whining and dramas somehow 😂 I personally just stopped reading replies longer than 2-3 sentences 😀

MarkGuitar

Sharonzaz I like the new buttons and the visuals on it as the region moves.

I am sure lots of folks here will like the buttons. Just asking for an option to hide them, not remove altogether. We all work differently eh? 😁

Sharonzaz

MarkGuitar sure. Being able to move the assignable buttons would also be nice

MarkGuitar

peter Make the title view a bit taller and show a small waveform instead of the solid bar
Add an option to select what to show in the space currently occupied by audio regions: off, regions, waveform

Oh yes!
Either is great for me. But whichever it is can we have the option to hide the buttons pls?
Thanks @peter

MarkGuitar

peter I would consider 11gb rather big.

Hey @peter
A wee bit worrying that you think my ST data collection is big at 11gb. I currently have about 300 songs loaded, 200 or so are lyrics only. Of the remaining 100, most have only a single stereo file which I am using as a placeholder for duration and a guide whilst practicing. I probably have only about 10 that have multi-tracks. They have typically 8-10 tracks per song. So roughly about 200 audio files and probably about 200 PDFs.
Given that I will be aiming to add multi-tracks to at least another 100 songs (probably more), with on average 10 tracks per song, that data size is going to grow substantially.
My audio files are uncompressed WAV files at 48khz. Each stem is typically about 75Mb.

Maybe the answer is just to do a catalog backup and I will keep my audio files backed up separately. I guess that would make moving from device to device a bit more cumbersome though.

Is there anything I can do for you to work on/check this out without having to clutter up the forum threads?
Thanks 🙏

jaytrax

MarkGuitar

17.6GB here with 727 songs
95% multitracked at MP3 320

peter

Both, features and bugs.

AnthonyB

jaytrax 17.6GB here with 727 songs
95% multitracked at MP3 320

Woah! OK, I think you're "winning" (creating & saving off backups on iPad must take a while!) 🙂

On the compression topic, given you're using MP3, you'd see almost no benefit from compression, then again, 5% of 17.6GB is still 880MB... so that would be down to the individual whether the extra time compressing the backup (as opposed to just packing it into a container file) AND the extra working space potentially needed on the device was worth it to reduce 17.6GB of raw data down to 16.7GB compressed backup file.

peter

AnthonyB Did you want us to start new threads based on things previously mentioned above that we believe are still in progress even if you have acknowledged them?

Let's start with new issues that pop up. The old issues will be implemented in a couple of days and I don't want to add any additional work.

MusicMan81 Please create a new thread for this, but a fully (or highly) customisable user interface is definitely not something I will add in version 4.0. That's way too much work to build this. Maybe you could post this in the Feature Request forum for a future update.

MusicMan81

Hey @peter …

I don’t know how complicated it can be to do this.

Apart from the general bugs we have shared, I’m reading all post “took me a while” and I notice that the biggest problem here is that we all use ST3 in a different way and we all have different needs, ALL are equally valid…

So, my 2 cents, and I hope this can be done because it might solve most of the discrepancies regarding the layout, options, and buttons etc etc.

Just like your idea of adding the option to Show the Audio regions, Waveform, or None is amazing because you solve everyone’s needs, even tho I think it would be impossible to fulfill everyone’s, is there a way to do the same in different parts?

For example. Let’s call this 3 layout zones “bars”... not physical or visual bars, just for reference…
Top bar, side bar and Lower bar.

That way we can choose what to put in each place, like in the “Top Bar” we can choose what to see…. Name, duration, waveform, audio regions, etc etc…

Side bar… a list of options to choose from… zoom, auto scroll, None, etc etc…

Bottom bar…. Assignable buttons, midi, none, etc etc…

This way we can all customize the app in the way we need, we can have as busy or light as we need, and avoid discrediting each others opinions, because this place is for request or discuss bugs… we are lucky to be able to take part in the shaping of the app, let’s not discourage Peter by making this a crazy circus, he’s giving us the opportunity to help shape the app, let’s make it happen and let’s all just take a moment to be in Peter shoes an make an effort to be more positive and effective.

Thanks!

royandreno

Deleted

AnthonyB

Oh, just an FYI for everyone testing ST4 on the same device as ST3.

If you happen to have:

Both ST3 and ST4 running (even if one of them is in the background), AND
You have MIDI triggers configured for Song Start/Stop in both versions, AND
You hit said MIDI trigger
.. you will get playback from both ST3 AND ST4.

I had a rather confusing moment yesterday at a band rehearsal where I was testing ST4, but had ST3 ready to go in case we had to revert to it. Drummer hit his trigger to start a song and suddenly I could hear 2 different songs playing! Only took me a moment to realise what was going on, but it was confusing, then amusing all the same 🙂

mrculp

AnthonyB this is exactly what I was afraid of

MusicMan81

peter Ok, I didn’t know that could meant having to rebuild the interface, it sounded it my head easier to have a dropdown menu with things to choose to see or hide…. But you know more than we do, so respect.

But if applying that is too difficult, let’s just skip it and focus on st4 for now.

musicadi

Damir Apple skipped from 18 to 26. Check under “Other updates” under Settings - General - Software updates

peter

New beta build 1810

In a week of testing we managed to basically get rid of the crashes. Only 1 crash with the last beta 1792 in a total of 700 user sessions during the weekend. Thanks a lot so far!

Changed

Double tap setting is now split into separate settings for each action
Cycling through regions will automatically scroll to the selected region
Improved mixer layout by moving labels above knobs/faders and changing master layout to make it uniform
Output selector in mixer is now grouped by stereo and mono tracks
Double tapping on a song will add it to the queue when single tap to queue setting is off

Fixed

Possible crash using undo in lyrics editor
Start of songs could sometimes be cut off when starting playback
Creation of large backups could hang
Crossfades not fading out with the configured time
Track solo and mute might change the wrong track
Track level monitoring inactive when switching songs while mixer is open
Midi on load commands embedded in lyrics not sent
Next song and previous song remote actions not switching to new song in player
Import of year, bpm and lyrics tags in m4a files not working
Volume fader could involuntarily change value during scroll gesture (drag gestures on volume sliders will always take precedence over scrolling the view)

Damir

peter Feedback on Audio Segments area.
Hi Peter, i like how as you select a new loop it automatically jumps back to now playing loop but i don't like how quickly it does it, suggestion is to delay this action by a couple of seconds to let us see the actual selected new loop before it returns for reassurance purpose.

Things i still find bad, when in stop mode selecting a loop does not highlight it.
Suggestion on improving the the visual feedback as song is progressing, as the loop starts playing and becomes the now playing loop, there needs to be more instant visual feedback to which loop is playing, there is no visual feedback in the beginning of loop as there is no progress bar yet, my suggestion is as the loop starts you make this loop internal area BLACK like the background that exists behind it, this will immediately make that loop stand out from the rest, and then as it fills its also obvious the loop that is playing, all other loops to remain as is and i would suggest you double the white area surround on the next selected loop as it also needs a boost to see it more clearly.when in stop selecting a loop should also make the background BLACK and a white surround to indicate which loop is about to play.
There is no need to space out the loop buttons so much , as this was never a problem in ST3 ,
Because you have round edges i would almost join the buttons as you will still get a V dip between them , perhaps a very tiny gap so you only see a tiny black line.

When you use the assignable buttons to choose a next loop, there is a JERK happening as you step through the buttons and when you get off screen you cant see what you are selecting again i would make it when you select a new loop it highlights it and after a couple of seconds if you haven't made a new choice it returns to now playing segment.

The overall look and feel is great, its gong to make a big difference on stage to manipulate loops live and encourage users to segment their songs as there are many benefits to this.

Damir

peter
REPORTING 0n 1810
Sorry Pete
Multitracks X fading back and fourth between two songs has still caused audio drop outs and metering disappearing on TRACKS
It seemed more reliable then went bad after playing around .

Xfade seems to be reliable
Mute logic still corrupt , mute says ON the bus 2 yet track 2 set to bus 2 is ignoring It.
Audio dropouts on stereo file still experienced.

Sharonzaz

Updated. Having a quick look as I’ve had 10 hours in studio with a client and I need silence now 😆

Xfade seems to work 👍🏻
Double tap to stop separately from play and fade working 👍🏻

Scroll doesn’t work from the faders only from the bottom of them where the names and mute is

What I could check now 🙏🙂
Well done

peter

Sharonzaz Scroll doesn’t work from the faders only from the bottom of them where the names and mute is

That's what is intended. Faders have priority for grab gestures. That's a consequence of the fact that you can grab the fader anywhere if you want to change it. No need to hit the knob. So the only way around this would be to make only the fader knob react to drag movements. Then the whole fader track would react to scroll drags. But I prefer to be able to drag anywhere on the track.

Damir Please create new thread for each new issue so that we can get votes and comments on it. The delay to jump back to the playing region could only be done globally. The app does not know why the region is currently not in focus. So yes, I could add that delay but it would be applied any time and not just when you select another region.

Damir Reporting that ZOOM PINCH gesture on lyrics no longer works , and we still have no idea of what text size we are using, i know this is on the fix list.

You already reported that and I acknowledged it. There is nothing in the changelog indicating I have fixed it in this release.

Damir Multitracks X fading back and fourth between two songs has still caused audio drop outs and metering disappearing on TRACKS

I have just tried to crossfade about 2 dozen times without any drop outs, metering issues and unreliable mutes. Can anyone else confirm these issues?

byung Flag this as a possible bug in Mac version.

Not a bug. It works fine in the dedicated macOS build. Please don't report any issues on the current non-Mac version running on Mac. I will not spend any time looking into it.

« Previous Page Next Page »