MIDI cc resolution/density

[ibbod0]

Is there any way to record MIDI ccs at a more fine resolution? If I am recording it in I get one event per 40 ticks. The line tool draws one event every 60 ticks. Very coarse. I can get it much finer adding points manually as shown in the image. Did I miss the setting for this somewhere?

[BScout]

What are you using for your fader/recording input device?
What is your midi interface or usb depending on what you are using for your input device)?

In preferences, mixing, there is a "smooth and thin data after pass" setting but as coarse as yours is showing, that seems like a problem with communication from your fader to pro tools. Or a hardware failure with your fader.

[musicman691]

Originally Posted by BScout

What are you using for your fader/recording input device?
What is your midi interface or usb depending on what you are using for your input device)?

In preferences, mixing, there is a "smooth and thin data after pass" setting but as coarse as yours is showing, that seems like a problem with communication from your fader to pro tools. Or a hardware failure with your fader.

To add to this: what MIDI cc are you showing in your example? No all MIDI data goes 0-127; pitch bend goes much much finer.

The freehand section looks like it was done via mouse.

[clausiii]

go to preferences -> MIDI -> Pencil Tool Resolution when Drawing Controller Data -> done

[clausiii]

Btw i don’t understand why the density is in ms not ticks (or selectable)...

[ibbod0]

Thanks for replies everyone. I realize now I was looking at it the wrong way and also the example I posted wasn't a good one. Actually that was the recorded midi output of a plugin that generates midi data. Seems like no matter what I try with the settings of that plugin, it won't give me smooth output.

The reason I assumed it was Pro Tools' fault was that when I record pitch bend from my midi keyboard I get the same steppy result but with 3-4 breakpoints on the start of each step. So it looked to me like Pro Tools was quantizing the data. Still don't know why there's several break points on the vertical part of each step. may be a hardware issue.

Recording from my midi keyboard controls gives me midi data with a resolution of around 9ms (not ticks, thanks clausiii), so it's not as bad as I thought, really...