Quote:
What would be a reason to go with really high tick resolution on a MIDI file?


For a MIDI file, 960 tick resolution generally isn't necessary, but it will give you better resolution of glissandos or very fast notes (64th or 128th notes) Also, if you use audio or render MIDI to audio, you will get more head room for slicing and dicing the audio.

As far as MIDI is concerned, I believe the standard BIAB resolution of 120 is too low, because once you divide a note to 64th notes, the program has to decide whether to use 7 ticks or 8 ticks, since it splits at 7.5. Likewise, if you go to 128th notes (maybe a harp glissando), then at 240 ticks, it would also have to decide whether to split the 7.5 at 7 or 8.


Resolution - Ticks to represent the note
Resolution - 960 - 240 - 120
1/4 Note - 960 - 240 - 120
1/8 Note - 480 - 120 - 060
1/16 Note - 240 - 060 - 030
1/32 Note - 120 - 030 - 015
1/64 Note - 060 - 015 - 007.5
1/128 Note - 030 - 007.5 - 003.75

(I apologize that the table doesn't line up - the forum collapses multiple spaces into a single space).

That's why I believe the default 120 resolution that BIAB uses is too low. At least RealBand supports the higher resolutions.

John

Laptop-HP Omen I7 Win11Pro 32GB 2x2TB, 1x4TB SSD
Desktop-ASUS-I7 Win10Pro 32GB 2x1.5TB, 2x2TB, 1x4TB SATA

BB2025/UMC404HD/Casios/Cakewalk/Reaper/Studio One/MixBus/Notion/Finale/Dorico/Noteworthy/NI/Halion/IK

http://www.sus4chord.com