• SONAR
  • Hidden CC codes at start of midi file? What to do?
2012/11/01 12:54:42
SuperG

I'm having a hard time comprehending why I can't see midi CC codes that occur before the first note. within a midi file.  When I view a track in the event list - the list starts with the first note. However, the CC's are there as the first thing X2 does is set the reverb send level (CC 91) - which is what you'd expect, but not what I want. (I'm using the Garritan library - ARIA uses that CC as expect/ed).

Now, mostly this is an annoyance. In fact there's a few other CC's in there as well for modulation and expression levels. Is it me, is there a way within X2 to show/Edit CC's that occur before the first note? I can bring the midifile up in Sony's Acid and see those CC's there - they're all at time 0. Is there some method or menu setting in X2 where I can get at them?

2012/11/01 13:01:16
Bristol_Jonesey
Try sliding the entire clip down to measure 2 - or even further, then have another look at the Event List

I think there's also a filter you can apply to home in on specific CC's


2012/11/01 14:48:46
soens
There's a quick way to adjust some of these in Console View.
 
In CV go to the Options tab in the Menu bar and select FX - Show Assignable Controls. It will display CC91, 93, 11, & 74 in each channel strip.
 
These are sliders you can adjust with your mouse.
 
 
Steve
2012/11/01 16:45:01
swamptooth
in midi preferences there is an option for zero controllers and patch/searchback. uncheck both of those to see if it helps.
2012/11/02 03:47:18
SuperG
I hadn't thought about if sliding would work... good suggestion. I'll try it later when I get a chance.

Yep, I went and some envelopes. See, the problem with the files was that modulation (CC 1) was coming up at zero (yeah, I had the reset controller option set... but I kinda like that option). The tracks would then use modulation as an articulation in places where it would drop to half and then sweep back up to full - however, without a code setting CC 1 to full initially, the first third of the song (in most tracks) was incorrect. So - I set an automation level for it to full and fixed the problem.

It is a bit interesting though, knowing you have both automation running and midi codes in midi file you're editing. It seems that they two are unaware of each other - that way setting a simple level worked out fine.

Anyone know if Sonar can import an automation curve from the embedded midi codes? Would be nice to have...

© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account