Well my guess would be that each track responds to an individual channel, and then for each channel it responds to there is a scene parameter per channel. Im just on my phone and not looking at the manual, but thats my guess.
Each track is assigned its own channel, and if you want to play the rytm externally younwould have to send cc’s on that channel to trig the machine. Since each track has its own channel, im assuming scene data controls all tracks it would need to send data on each channel . Make sense?
If you want yo play your rhythm externally you need to channelize track parameters.
For example track Level is CC95, so to affect Track 1 Level (assuming default channels are set )you need to send CC95 ch 1, to affect track 2’s level CC95 ch2 and go on.
Track Level is a track parameter, each track has a “Track Level” so it make sense to use MIDI channel to control them independently.
The Scene parameter is not a track parameter, it is a Common parameter, this means there isn’t a scene parameter per track but a single one for the whole kit. So it is pointless to use different channels to reach a single parameter.
This behaviour is like to have the Reverb Time parameter changing its channel depending on which track you are on.
From a data perspective it makes total sense. How is the data contained within a “scene” supposed to communicate to each individual track independent values simultaneously without having it separated per channel?
I can’t seem to get rytm to send any midi when activating scenes or perfs.
The reason is I want to record these into Ableton to capture a full performance.
Currently it seems I can record Perfs when in OB mode, but not scenes
Any ideas?
Hmm, was wondering the same – in the manual there is nothing about scene midi notes or CCs. Would be awesome to have this! Will try in a bit – maybe changing the auto channel could help?
Okay… so it does work - I changed the Auto channel (I think it’s a bit buggy).
Sadly this is annoying to work with since it only sends out one CC with the value (Pad 16 127, 15 119, 14 111 etc.) - not really useful to map anything onto this in a 3rd party app… would have to convert it first … grrr …