I am using tracks and song actions in conjunction with a midi track to control my guitar processor. It has worked fine, besides bugs in areas, but now when I select a song from my setlist and hit play, my guitar processor isn’t changing. But if I then manually rewind the track by grabbing the cue head and sliding it back, I can hit play again and it works. So it seems I have to play the midi track twice to get the messege sent. this is true on all 13 of my songs on setlist.
Please fix.
Also, I thought I should mention that multicore audio has never worked correctly for me on 16gb m1 mac mini.
Hi @trixdropd , already signalled to devs, first couple of seconds stopped being sent with chase on start ON. If you disbale chasing on start it will work as soon as you switch the song.
For now, untill it’s fixed you can move the midi event to like 1.3.1 or 2.1.1 and it will be sent. Or you can chase event as soon as song witch without waiting for transport.
In preferences/MIDI set Chase Events ON, but Chase on start OFF. this way midi events placed on 1.1.1 will be sent even before transport start. Chase on start insted will wait for transport play to send events on 1.1.1.
Hope it will be fixed soon, for now in my project i simply disabled chase on start so midi events on 1.1.1 is sent at song activation.
PS: for multicore, for me it works but i need to set a audio track , even empty, with monitor on to avoid continuous crackle in track playbacks. but i decided to go with multicore audio and also multicore video OFF because i have lot of sends, vst plugins, videos, outputs, so the audio chain is complex and i had no advantages from multithreading, instead more issues!
Cheers. Ciro.
Cannot reproduce anymore, but testing with the next version to come. We did change Song transitions, so pls give it another try.
Sending pgm chg from 1.1.1 with Song Action “Start Next Song”, with or without “Chase Events on Start”, always works here.
If it still fails with the next version, pls report again.
This also happened to me. I’ve discovered that if I put the midi track a little bit forward (see attached screenshot) then MIDI is received with my Line6 HX Stomp. If I put the program change at the beggining of the song then most of the time MIDI is not sent when we hit play.
Although using MIDI with Layers, program change allways gets fired after changing the song, so have to be some little but with MIDI playing if midi data is close to the beggining of the song.
In my case I have to say that despite of MIDI chase value, happened the same. With Chase On or Off I’ve found the same problem
@Adam_Viusa Yup, same behaviour as me, moving the container more or less 1 bar away from 1.1.1 sends the events.
But if you set midi chase on and midi chase on start off, the events on 1.1.1 (exactly 1.1.1, yours is not, it is slightly after start) will be sent as soon as song is loaded, before hitting play.
a) pls check again with 2.2.51
b) if still. what chase settings, and which actions to reproduce (change Part/Song only etc)
Tried in .51, all works as expected now for me both with chase on and on start off or on.
