Jump to content

large number of MIDI Volume (Ctrl 7) events (SOLVED)


charliem22

Recommended Posts

Hi --

 

I'm using a fairly low-end controller (M-Audio Keystation 49e) to play orchestral parts into Logic9 running GPO4. Most of the instruments use the ModWheel for "expression control," ,i.e. changes in volume and -- to a lesser degree -- timbre. I find that I often get hundreds of Cntrl 7 events even though I'm not touching the MW (which is Cntrl 1 anyway) and the volume fader on the M-Audio is set to MIN (having it another position sends lots more Volume events). Each time I record a section of a track, I end up just selecting the unnecessary Volume/Cntrl 7 events and deleting them.

 

Any ideas how I can keep them from entering the MIDI stream in the first place as they are simply not needed and erasing them is a bit of a hassle?

 

Thanks in advance --

 

charlie

Link to comment
Share on other sites

Interesting that you don't mention your channel faders going crazy with these controller 7 messages...

 

Anyway, these lower-end M-Audio keyboards are famous for sending MIDI data on their own. You could program the slider to send something else, but seeing that you're mostly bothered by the amount of data ending up in your regions, you should simply filter these events before they reach the sequencer's input using a transformer object in the environment:

 

http://www.logicprohelp.com/files/filter7_146.png

 

J.

Link to comment
Share on other sites

Thanks to both of you. The Transform works perfectly (not that that would surprise you)...and yes, my channel faders were very nervous...that was my first clue that it was MIDI data overload.

 

I don't think the Project Settings --> Recording --> MIDI settings work (I thought of going there before I put up this post) because -- unless I'm misunderstanding the UI -- you can't filter for a single controller, i.e. you can filter out all control data or none. Am I missing something?

 

Thanks again --

 

charlie

Link to comment
Share on other sites

I don't think the Project Settings --> Recording --> MIDI settings work (I thought of going there before I put up this post) because -- unless I'm misunderstanding the UI -- you can't filter for a single controller, i.e. you can filter out all control data or none. Am I missing something?

 

You mean the MIDI Input Filter? (maybe that's what redlogic meant also, because MIDI data reduction won't help).

 

But anyway, that's correct. Checking the Control Changes will filter all control change data. You can't pick just one or two to filter out.

 

J.

Link to comment
Share on other sites

Flexibility......and something that can be setup once rather than per every project... though I do agree you can do it with the transformer.. but cleaning the data before it arrives in Logic, can also have benefits when dealing with 'overloaded' midi channels if that makes sense?
Link to comment
Share on other sites

and something that can be setup once rather than per every project

 

You only need to do it once if you save a project template that includes the transformer...and actually, I don't see which of the tools in MIDIPipe can be used to filter out a single CC.

 

but cleaning the data before it arrives in Logic

 

As long as it doesn't get to Logic's sequencer input, no "damage" will be done. This is what the transformer method does.

 

can also have benefits when dealing with 'overloaded' midi channels if that makes sense?

 

Nope, it doesn't make sense Nigel...what do you mean?

 

PS: I use MIDIPipe and like it a lot by the way....just not for this application.

 

J.

Link to comment
Share on other sites

Nope, it doesn't make sense Nigel...what do you mean?

 

Hi J...

 

Heh.. and you might well be right....

 

I think the last time I used MidiPipe for such a purpose..was with L7... and in that instance I used it to filter out a client's keyboard midi output that kept sending out wayward/errant aftertouch messages by the thousand.. to Logic... so i (think I) used MidiPipe to filter those out prior to them arriving in Logic... and any of his other midi programs..

 

At the time... It saved me time just doing it 'at source' rather than setting up everything in his various DAWs... to filter them out... hence my suggestion but upon further thought and after reading your helpful comments, it probably doesn't make much sense to do it 'my way' at all....

 

Oh well.... This is probably what comes from answering posts when i have had about 2 hours of sleep in the last 48.....

 

Thanks as always, for pointing out the 'error of my ways' :)

 

Cheers...

 

P.S. Want to do some cleaning up of this thread to get rid of my 'suggestion'? ;)

Link to comment
Share on other sites

I think the last time I used MidiPipe for such a purpose..was with L7... and in that instance I used it to filter out a client's keyboard midi output that kept sending out wayward/errant aftertouch messages by the thousand.. to Logic... so i (think I) used MidiPipe to filter those out prior to them arriving in Logic... and any of his other midi programs..

 

At the time... It saved me time just doing it 'at source' rather than setting up everything in his various DAWs... to filter them out... hence my suggestion but upon further thought and after reading your helpful comments, it probably doesn't make much sense to do it 'my way' at all....

 

Ok, I see...

 

Oh well.... This is probably what comes from answering posts when i have had about 2 hours of sleep in the last 48...

 

Ouch!

 

P.S. Want to do some cleaning up of this thread to get rid of my 'suggestion'?

 

Well, since MIDIPipe is a useful program to know about anyway, why don't we just leave it like it is? No harm done.

 

Cheers,

 

J.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...