RobertWS Posted March 8 Share Posted March 8 I doubt there is a workaround for this and it will probably never be fixed but.... I disassembled a MIDI file to see the controller messages: MFile 1 2 960 MTrk 0 Meta SeqName "Test" .... MTrk 0 Meta TrkName "Track 1" 0 PrCh ch=1 p=0 0 Par ch=1 c=10 v=4 0 Par ch=1 c=91 v=77 (This one) 64 On ch=1 n=60 v=127 608 On ch=1 n=60 v=0 ... You can see controller 91 (external effects, reverb in this case) is set to 77. Here is how it looks in Cakewalk: Note: The reverb dial is set to 77 but there is no controller in the event list. Is there anything that can be done about this? Link to comment Share on other sites More sharing options...
David Baay Posted March 8 Share Posted March 8 Controllers for which CbB has dedicated track controls are read into those controls and removed from the clip, but only when you open a .mid file as a new project. If you import into an existing project that won’t happen. And in any case, they will be written back to the file on save as MIDI. 2 Link to comment Share on other sites More sharing options...
RobertWS Posted March 8 Author Share Posted March 8 I'm confused. Sometimes they DO show up in the Eventlist. Link to comment Share on other sites More sharing options...
John Vere Posted March 8 Share Posted March 8 Did you look in the controller pane of the PRV? The event list is sort of limited in usefulness. As David said the track inspector settings override any other data. By default if you don’t touch them then they are set to None and don’t have any bearing but the minute you move anything it seems this is stored in the file. But these changes don’t show as events anywhere. Link to comment Share on other sites More sharing options...
David Baay Posted March 8 Share Posted March 8 (edited) Anything other than CC7 Volume, CC10 Pan, CC91 Reverb and CC94 Chorus will remain in the track because there's no dedicated track control for it. Also, only the initial value will be moved to the track control; if there are additional events that change tha value later in the track, those controllers will remain visible in the Event List and PRV Controller Pane. That initial value is sent every time playback is started unless it's overriden by starting playback later in the track with Event Chase enabled in Preferences > Project > MIDI (which it is by default). Edited March 9 by David Baay 1 Link to comment Share on other sites More sharing options...
David Baay Posted March 9 Share Posted March 9 (edited) The screenshot is showing a few events at 640 ticksso CbB is at the default 960PPQ. If you open a MIDI file recorded at a lower PPQ, CbB will adopt that. Or did you maybe mean rpn/nrpn messages? Edited March 9 by David Baay Link to comment Share on other sites More sharing options...
msmcleod Posted March 9 Share Posted March 9 On 3/8/2024 at 4:58 PM, David Baay said: Controllers for which CbB has dedicated track controls are read into those controls and removed from the clip, but only when you open a .mid file as a new project. If you import into an existing project that won’t happen. And in any case, they will be written back to the file on save as MIDI. 22 hours ago, RobertWS said: I'm confused. Sometimes they DO show up in the Eventlist. @David Baay is correct - but it's only the first occurrence of those CC's / Program Change messages that is transferred to the track controls. Any subsequent events are left intact. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now