I suspect the issue is that rg has two ways of handling Control
Change messages in a standard MIDI file. CCs at time zero are shown in
the MIDI Instrument Parameters Panel. CCs after time zero are simply
events in the segments. Those can be viewed using the controller rulers
in the matrix and notation editors (and the event editor).
If you have a CC at time zero followed by a CC at a later time, the
CC at time zero will be "overridden" when the later CC comes in. So
adjusting the CC in the MIDI instrument parameters panel will appear to
have no effect. You need to work with the controller rulers instead to
edit CCs after time zero. Or you can just delete them all and only work
with the one in the instrument parameters. Although that can have some
surprising consequences if the track needed those volume CCs.
As an example to get to the controller rulers from the matrix editor...
- Select a segment.
- Press "m" to launch the matrix.
- In the matrix menu: View > Rulers > Add Control Ruler > Volume Controller.
Hopefully this is helpful. CCs in general are tricky for MIDI
sequencers. rg's support is somewhat limited. Let us know if you have
any further questions.
Ted.
On 4/29/24 6:29 AM, Thomas Sonne Olesen wrote:
Hi
(New to this group, but have used Rosergarden on and off for many
years)
I realised importing a Midi-file that the rosegarden mixer didn't
reflect the volume setting in the midi-tracks.
So I startet to look at the way Rosegarden handles these event, and saw
that each time I read a midi-file, and export it again all controller
events, that Rosegarden handles (reset, volume pan ect) will be written
again - along with the old one.
If I change a tracks volume in Rosegarden the new value i written first
in the list of controller event, followed by the old(originale volume-
setting, which then is send last, meaning that the rosegarden setting
is ignored.
I have tried to follow the code-flow from import to internal rosegaren
representation, and I cant find any places, where the rosegarden
represtation is match against the midi-file representation. It dosen't
help to save the file as a rosegarden file and read it again before
midi-export. Alle the dublicated controller-events is kept.
Have I missed something - shouldn't the mapping be handled and these
dublicates detected - and if yes, should it be handles when
reading (only keep one volume setting) or on the write (only write
rosegarden value and igonore others?)
Any hint appreciated - I might look deeper into this.
Regards Thomas
_______________________________________________
Rosegarden-devel mailing list
Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
_______________________________________________
Rosegarden-devel mailing list
Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
