Topic: Drumtracker Midi file timing | Toontrack

Drumtracker Midi file timing

Other Pre-sales

Posted December 12, 2010 at 14:41 #1893504

WayneKiser
Participant

If a click track is not used during original performance, when you export midi file in say 120 BPM does it quantize or keep original timing? If quantized, it wouldn’t fit my original song tempo. Demo doesn’t let you get this far and product description is unclear.
Creator

Topic

Viewing 2 replies - 1 through 2 (of 2 total)

Replied December 12, 2010 at 14:48 #1942813

Scott
Moderator

If the track was not tracked to a click, you set the tempo to in DT to 120BPM and it will keep the original timing when imported to your host.

Scott Sibley - Toontrack
Technical Advisor

Replied February 9, 2011 at 18:42 #1945537

Jeffsco
Participant

I’ve just got my Drumtracker up and running and have not had any problems importing the Midi files into my DAW (RML Labs’ SAWStudio). I do have a problem with EZPlayer Pro. Any Midi file i create in EZPro and import into my DAW is “Quantized” to a degree. In talking with Bob lentini (SAWSTudio creator and developer) it would appear that it is a Midi Tick resolution problem. SAWStudio supports up to 960 Tick resolution. It would appear that EZPlayer pro has a much much higher resolution and it becomes an issue for any DAW that tries to import the Midi file. The problem is..you don’t need ecxeptionally high Tick resolution. I mean…at 120 BPM and 920 tick resolution the note is accurate to 1/2 a millisecond. I can’t hear that….Can you?

I’d like to see Toontracks give us the ability to alter the Midi Tick resolution in the Preferences so that we can match up our DAW’s
Author

Replies

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.

Please log in to read and reply to this topic.

< previous

> next

0:00

0:00

volume

×