I raised a support ticket and the guy confirmed he did not know when or if this would be addressed in an OS update.
So I figured out another way to deal with it.
I’ve got a new workflow going where Rytm sends PC changes when it switches patterns to a BOME translator, BOME converts them to CC69 and pushes them out to my Pyramid to fire sequence changes on other devices. Then I use the Song mode on the Rytm to sketch end to end jams which I track out into Bitwig as audio for fine editing and finishing. Obviously you can turn Song mode on or off depending on whether you want to jam live or play a linear sequence, so it works nicely as a control centre for sequences. Everything is super tight and firing bang on time. It was a joyful moment when I got it working as expected!
Everything is clocked from Bitwig via an ERM Multiclock. So I gotta press play on Bitwig to start everything. But I can live with that.
(You can get a HW translator to remap the PC changes if you don’t want to use a computer, although the ones I came across were $150+)
It’s all good until I want to start my Song from say, mid way through. Unless Rytm is the master clock source, it always plays the Song from the start of the chain. Irrespective of where you place the ‘play from’ cursor.
Tried to fix this by clocking Bitwig to the Rytm (over DIN, USB clocking is broken too!) but somehow ended up double clocking the Multiclock which scuppered everything else.
Must have a clock loop or something somewhere in my setup but struggling to locate it. I use a MIO 10 to distribute clock and the interface is baffling at times. Gave up in the end but will return to it once I’ve turned it over in my head a few times.
If you want to fire scenes or clips in your DAW in line with PC changes from the Rytm. Get a translator and re-map the Rytm PC to a MIDI note or CC message and map that to the scene or the clip you want to trigger.
Spent a bit of time on this over the last week so might be able to help you.