1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Logic 8 Logic not tracking cc info correctly

Discussion in 'Logic 8' started by daveyboy, Apr 24, 2009.

  1. daveyboy

    daveyboy Senior member

    Working on some mostly midi stuff today I was experiencing some bizarre behavior where as some of my vi's (K3, omnisphere) weren't always following the volume change info. I would have a piano set to 43 and would go to mix the song it will have jumped up to 127. Sometimes the fader was up, sometimes the fader was still at 43. Also would happen if I had committed the change in automation or not. I've checked prefs and nothing's checked in the input filter. Also, these songs were imported midi files from the client from some big home yamaha thing. I went through the tracks looking at them in the event list and got rid of all the extra cc garbage (in which there was a lot). I don't know if some midi voodoo was imported in the process. Was thinking about deleting prefs to see if that fixed it. Of course this stuff only happens when I'm on the clock and have someone watching! Good times.
  3. Eli

    Eli Senior member

    I doubt this has to do with your prefs. It's most likely something you missed when going through the imported files and deleting unwanted CC info. I'd suggest another detailed check through all the regions and make sure there is no erroneous data there.

    Also, are you using track automation now? It could be conflicting / competing with old MIDI CC info still buried inside the regions.
  4. daveyboy

    daveyboy Senior member

    Thanks Eli. Is there some other way besides using the event list to find hidden cc data (besides the piano roll editor)? It's coming up "clean". I'll keep poking around though.
  5. Eli

    Eli Senior member

    Check for hidden tracks maybe?? It sounds like you're doing everything right. If you want to try more drastic measures; try copying al the region data into a new fresh empty project. See if the problem persists?

    And if you are not using any track automation, maybe try and use the "delete all track automation data on all tracks" command just to make sure there's nothing erroneous lying around on any of the tracks.
  6. daveyboy

    daveyboy Senior member

    I think it's fixed (somehow) as when I played the tracks back today all was well. MIDI voodoo perhaps? I had a bunch of autotune evo crashes though (using graphic mode). It's always something, huh!?

Share This Page