Live's Export MIDI File resolution is 96 ppqn.

[d-track]

in older version of fruity loops you were able to change this in the options midi tab
now its gone
i dont know if it makes any sense...

[tomjordan]

Regarding live sounding less tight then logic.. This is far fetched but just in case: did you check delay compensation?

Im switching it on and of all the time. If its on, midi keyboard latency is late but sequencer timing is good, and if its of lives midi timing is sloppy but controller latency is tight. So when recording midi from instruments I set it of, and when its done, I switch it back on.

Thanks for the tip.. I have to try that.

[3dot...]

It looks like the import MIDI file works as expected, thankfully !
I imported both the original MIDI track at 960 ppqn, and the one that was exported out of LIve.
I set the tempo to 20 bpm and zoomed in on both tracks..
sure enough, there original track seems intact, and looks and sounds much different from the track that was exported out of Live.
So, the issue only seems to be with the MIDI file export.
Good news !

I'm judging that based on sequences that were generated from an algorithmic composition environment in Ruby where I specifically set rhythms to Pi and Golden Ratio, etc..

neat..
how far are you going with the Pi thing... and how do you scale it?

I like to use values of Pi and the Golden Ratio, etc, that are close to 16th-note divisions, but different enough to give it a nice groove.
Such as: instead of having a dotted-eighth note at 3 16th notes, I'll have it last 3.14 16th notes,
and combine it with another dotted-8th at 2.86 16th notes, so that when used together it equals 6 16th notes.
If you then use a regular 8th note with each pair of modified dotted-8ths,
you can do any permutation such as:

pi-3-2
pi-2-3
2-pi-3
3-pi-2
2-3-pi
3-2-pi

where the "3" is actually 2.86, to "make up" for the 3.14 pi value, since 3.14 + 2.86 = 6, and 3.14 + 2.86 + 2 = 8.
This may sound like a lot of unnecessary technicality, but it does sound awesome when using it for certain accents and parts..
it sounds really organic..

It's easy for me to generate these kind of timings now because I can just specify the values directly in Ruby and it will generate a MIDI file.
I used to figure out the tick values and input them by hand into Logic. The new way is much faster..

interesting ...
so you're using it for timing values ... not tones...
so.. has anyone found out if it's the import or export that causes the 96ppq quantize ?

I actually never quantize over 64...
but this behaviour should also affect unquantized midi being recorded then exported...
so I'd like to know..
I've had a piano player record in my studio a year ago... and she always complained about the recordings not being played back like she played them...
(playing live sampler...recording quantize was off btw... buffer was 128... and she did not notice latency when playing)
had to go in and move notes manually with her.. which was hard/frustrating work..

[rikhyray]

Interesting. I never use Live for midi recordings, I am not complaining type, if something does not work as I need, use something else.
96 is definitely unusable for any serious (read rhythmically demanding) production.
If indeed such low resolution is the obstacle there is old workaround used by Triton users- double speed. In fact I dont know any arranger (unless they use Motif or other Yamaha) of Jazz or Salsa not using that trick .

[zigzag]

that explains the trouble i had with another program reading the exported midi tracks from Live - the notes were off although quantized to 16ths. this is terrible. has anyone submitted a bug report yet?

[q.musgrove]

good question! Does ableton have anything to say yet?

[kb420]

I was going to, but I left it up to tomjordan. It was his find. Personally, I don't export midi files from Live, only audio.

I'm actually surprised that the Abes haven't commented on this thread yet. I guess they already have too many 8.1 bugs to fix to even chime in on this fiasco.

[locojohn]

A happy end to this thread will be finding out how to export MIDI from Live at the highest possible rez.

The MMA has been "discussing" the MIDI 2.0 spec for years. Has it been implemented anywhere? What's the big delay?

I would also be interested to have a possibility in the future versions of Live to be able to export several MIDI tracks at a time into a single .mid file. This would also help when transferring data to various notation programs, while Live does not provide its own notation support.

Andrejs

[zigzag]

anyone had a comment from support yet?
is this filed already? or forgotten?