Open Beta Version 4.0.0

Anakin

@peter, I noticed that with this build the CPU usage stays around 30%, while in the previous build it was about 5%. I’m using a MacBook Pro M4 Pro.

peter

Anakin I don't see a difference in CPU on iOS and macOS is not yet supported.

Sharonzaz I will increase the time to 0.2. That's right in the middle of the original 0.3 and the current 0.1.

Sharonzaz

peter

Thx lets give that a try 🙏🙏

peter

New beta build 1966

This is the first build that is also officially available for macOS.

Changed

Decreased responsiveness of knobs and faders a bit again to reduce chance of involuntary changes
Improved performance when switching between playlist, song list and queue in sidebar

Fixed

Crash exiting audio region editor
Double tap to reset faders in mixer on iOS 16 and 17
Possible hang when changing mixer speed knob
Text input in alerts not visible on iOS 16 and 17
Alerts with text input field missing OK button on iOS16
Alert buttons not working when initially disabled below iOS26
Double tap gesture to open / close full screen lyrics not working reliably
Scroll speed buttons temporarily shown for songs with timecoded scrolling
Closing and reopening playlist view in sidebar does not show the correct playlist on iOS16

Sharonzaz

peter

Thank you, definite improvement for the mixer for me 🙏

Felt it’s faster response when selecting next song to queue for xfade

💪😎
Will test and report

peter

New beta build 1977

Fixed

Possible crash navigating back from a playlist to the playlists overview
Autoscrolling not keeping configured position for highlighted line
Double tap protection applied twice if active on network client and host
Midi trigger to select songs does not work with program changes containing a bank
Chords misaligned with centered lyrics
Crossfade can be started even if no playback is running
Mini player in song details not updating playback time and position continuously
Region pulse animation pushing song details view up and down

rowe2000

Not bugs, but design proposals..
1.
I suggest the buttons for editing song and show mixer should beplaced in the stop bar next to the settings button instead of the bottom bar.
This will make it a more consistent toolbar. It wil be easier to find the base functionalities and reduce the overall clutter.
The bottom bar is then for custom buttons and it maybe should be transparent to show lyrics an setlist trough it.
2.
I think the metronome flash should outline the whole app instead of just the lyric area.
On iPhone in portait mode you woun't see the lyrics but only the setlist, that is how it is meant, but therefor you can't see the metronome either.

Lishy

rowe2000 you need to create a separate post for each suggestion.

peter

I don't agree. Top bar is for global actions or views. Bottom bar is for song specific actions or views. And there is no room for 2 more buttons in the top bar.
There is no room for that around the whole UI but I could make the bottom bar flash instead.

rowe2000

peter

OK, I'm convinced, as long as there is an design idea about it I'm good!
Good enough, that sure solves it!
Thanks. 🙂

peter

New beta build 1991

Changed

Next and previous song remote commands now work either on the song list or playlist depending on whether list was shown last in the sidebar
When opening the mixer closes the sidebar, it will reopen it when the mixer closes
Changing screen orientation with mixer open will now hide and restore the sidebar automatically
Song list and playlist view now show the whole folder path in navigation bar when within a subfolder
Tapping outside of add songs to playlist dialog will no longer close it automatically

Fixed

Another try to fix the iOS16 crash navigating back from a playlist
Autoscrolling positioning bug on iOS16
Taps in folder picker not registering outside of labels
Bus selector in mixer modifying wrong track after reordering tracks
Region button scrolling delayed when playback jumps to next selected region

TimRyland

peter , brilliant. App no longer crashes when returning to Playlist view. Great work and hearty thanks for a superb app.

Damir

peter Audio segments selection buttons area is starting to fall in to place logic is improving.
Found when in STOP mode, using assignable buttons to move through audio segments, there is no highlight of buttons when selecting a starting segment, the lyrics move to correct segment its just not highlighting the segment you are on , giving you no confidence to when you hit start.

Damir

peter This update has made IPhone use much better 👍
Reporting one small issue using iPhone in portrait mode.
A double tap on lyrics opens LYRICS ONLY the issue is it always opens the lyrics at the end of song and waits until the next timecode is triggered then sets up the lyrics to where they should be , ideally you want it to open the lyrics on the existing timecode position in use so you immediately see correct lyrics position.
This applies to iPad.

royandreno

Hey @peter! Build 1991 fixed the stuck button bar/keyboard issue! Now the keyboard collapses after button assignments. Hopefully that issue is gone..🙏🏻😊

vangrieg

My first post here, and let me start by saying that I love this app, it's a real gem and a super helpful tool.

I've been using ST3 for a while, and was anticipating ST4 for the announced ability to run midi files. I finally got the beta and tried the midi playback functionality, but found that it doesn't actually do what I needed it to do at all. 🙁

The point of having midi files in the backing track app for me is to sync outgoing messages with audio, and to lock hardware devices to song tempo. However, importing midi files doesn't appear to affect song tempo at all, the only tempo ST4 seems to recognize is the static number set in the song properties.

Am I missing something or does the app indeed not use tempo information contained in midi files? If it doesn't, is this on the roadmap?

One other question I have is what's the syntax for SysEx midi events here?

Thanks!

AnthonyB

vangrieg Am I missing something or does the app indeed not use tempo information contained in midi files? If it doesn't, is this on the roadmap?

No, it does not, and was never intended to.
The MIDI file capability is to allow you to export MIDI tracks from your DAW which contains MIDI events for other devices, and attach that to a song and have them 'played back'.

vangrieg One other question I have is what's the syntax for SysEx midi events here?

Exactly the same as MIDI events in ST3 except you have to add 'SX' in front of the SYSEX command, e.g.
[midi@00:00.250: SXF0 00 20 32 32 2F 66 78 2F 32 2F 74 79 70 65 20 44 4C 59 F7]

vangrieg

AnthonyB The MIDI file capability is to allow you to export MIDI tracks from your DAW which contains MIDI events for other devices, and attach that to a song and have them 'played back'.

Well that’s exactly what I’m trying to do and what’s failing to work when songs have variable tempo.

AnthonyB

vangrieg
You should open a new thread and provide some detail on what you are doing as I'm having to make a lot of guesses and assumption. In short, ST is just playing back your audio file and the MIDI track 'as is'. It doesn't care about the tempo value you enter when playing back audio files, that tempo value is just a field for reference. So if your audio files have tempo variations, then as longs as in your DAW, the MIDI and Audio variations were in sync, then as long as you have exported your audio stems and MIDI track with the same start point and duration, they will play in sync.

Open a thread and provide more details of what you are doing, how you are doing it, what you want to achieve, and it can be discussed in more detail. It will get lost in a general thread like this one.

vangrieg

AnthonyB You should open a new thread and provide some detail on what you are doing as I'm having to make a lot of guesses and assumption. In short, ST is just playing back your audio file and the MIDI track 'as is'.

I’m not sure which additional details would be needed here. Tempo information sent by ST4 is wrong (because it’s constant for the duration of the song), so any devices that rely on tempo fall out of sync, that’s it.

And I’m not sure what playing a MIDI file “as is” actually means. Playing a midi file can be done with importing the tempo information from it by the host and following it, or it can be played at whatever tempo the host is set to. Both would be “as is”.

« Previous Page Next Page »