Why would you have a higher resolution during normal operation, then export it at a lower resolution, or import one and change it's resolution to a lower rate when you supposedly can accommodate it? Now you could say that it may have something to do with the importing / exporting function in Ableton, but from a programmer's standpoint, that would be highly illogical since you can easily set any ppqn of a MIDI file with just an integer value. That much can be repeatedly proven, if you read over the results that I got.
#MONITORS TICK ABLETON SUITE 8 PROFESSIONAL#
There are good reasons why Logic is at 960 and other professional DAWs don't shirk this responsibility.Īll I know is I imported a sequence into Ableton with a 960 ppqn, then exported it back out, and now it is at a 96 ppqn resolution. I can see why they would want to have it at 96, since it makes the MIDI very lightweight, and a much less drain on the resources,īut for a professional workstation, it is not acceptable. Or opt for a finer resolution at 480 or 960 (whichever they choose to use), with a possible decrease in available processing power.
I sincerely hope that they add a feature where you can choose between the standard resolution at 96, To me, this explains why there is no event list with tick values in Live, a feature that I've longed for, and why the ppqn is not advertised, or widely known. I can only assume that Ableton's resolution is 96 ppqn, since it wouldn't make sense to export it at a lesser rate. Since the MIDI file standard has the capability of using a wide range of ppqn, I brought it up in Logic, and its tick values matched exactly to the file that was exported from Ableton.
To check this, I then generated the same MIDI file from my environment, but now with a ppqn of 96. The values of the ticks are now: 10 notes at tick value 1 1 1 1, 10 notes at tick value 1 1 1 11, and 10 notes at tick value 1 1 1 21, for a total of 25 notes. The file now has many repeated values, and only changes twice I imported the same original file into Ableton, then exported it back out from Ableton, which I then brought up in Logic. The file has 25 notes, ranging from 1 1 1 1 - 1 1 1 25, with every tick represented in between. I imported that into Logic, looked at the event list, and there was a note on every tick. I generated a MIDI file from my live coding environment, where there is a note on every tick, at 960 ppqn. It seems like Live's resolution is 96 ppqn.Ĭompared with Logic's 960 ppqn, Logic has 10x more resolution. This thread shows the original messages and how we came to find out that it was only the MIDI file export, and not the playback or record resolution. Namely, that when using the MIDI file export command in Live, it outputs a MIDI file at 96 ppqn.Īt first I thought that the resolution in general was 96, but gladly, I was wrong. NOTE: This message has been updated to show some new developments.
0 kommentar(er)
