2015/06/09 16:15:20
synkrotron
That piece of music was not produced using methods we are using today. Some parts may have been synths played and recorded as audio onto tape or a sequencer used to drive a synth and recorded to tape. The played stuff would not have been "quantized" and the sequencer stuff would not need "quantising" because it would be in perfect time.
 
 
2015/06/09 16:39:57
AdamGrossmanLG
Oh but I was just asking if that lead synth sound in the beginning before the drums start was actually "quantized" meaning, do they fall on the beats or not?  I know it was made differently, but if the drums fall exactly on the quarter notes, would that top lead sound notes hit on the beats too or would they be slightly off?
2015/06/09 16:47:42
mettelus
What method are you using for quantizing? I am finally at my computer so downloaded and pulled that into X3 (no MIDI outputs enabled), and the file comes up as 135bpm with a 5/16 time signature. Based on your PRV capture, the time signature is different which would make quantizing go out the window on you (You are quantizing to a different time sig).
 
In X3 and above, if you have no MIDI outputs selected in preferences, SONAR will open a MIDI file and insert/route the TTS-1 for you. I am wondering if you did a file/import on this instead?
 
Edit: In the transport module in SONAR, what time signature do you see just to the right of the project bpm?
2015/06/09 16:49:43
AdamGrossmanLG
ohhh hold up...  how did you get Sonar to open up the tempo to 135?  I just did a "IMPORT>MIDI" and it just added the tracks, but I had to adjust the tempo myself.
 
 
2015/06/09 16:52:08
mettelus
First... go into preferences... MIDI->Devices, and uncheck ALL available "MIDI outputs" Save and close SONAR.
 
Then right-click the .mid file and "Open With..." and use SONAR... it will auto load/route the TTS-1 for you.
 
Then the transport module should read 135 bpm and 5/16 for the time sig.
2015/06/09 16:53:10
AdamGrossmanLG
ahh cool, will have to do later when i get home :)
2015/06/09 16:54:05
mettelus
If you are quantizing to (both) a different bpm and time signature, it will "blow up" on you completely.
 
Edit: Looking at this file in more detail makes even that time sig look wrong though. I am definitely not savvy with quantization methods, but when "snapping" any notes, that underlying grid needs to be really close to the notes before quantization or they will shift in a "seemingly haphazard" fashion.
2015/06/09 16:54:07
synkrotron
Hi mettelus,
 
That's weird, because in X2, I had a project left at the default of 120BPM and it exported it in no problem. All I had to do was shrink it all down to 80 percent... I didn't realise that MIDI files were set to a BPM, just TPQN. It's a long time since I've bothered, or even have to import a third party MIDI file...
2015/06/09 17:05:41
mettelus
The TTS-1 routing was done in X3. MIDI will conform to the bpm of an existing project if imported (default template is 120 at 4/4). The method above is using what the mid file "says" it is. This is not "cut and dry" by any means though, since even the 5/16 doesn't "match" either.
2015/06/09 17:08:35
synkrotron
mettelus
that underlying grid needs to be really close to the notes before quantization or they will shift in a "seemingly haphazard" fashion.




The MIDI file that the OP has provided the link for does not need quantising. I don't know why, but the whole song does not fit into a 4/4 grid, even though it's a 4/4 song.
 
try to follow this if you can:-
 
I then selected all of the MIDI tracks and selected the following command, with the now time set to the start of the song:-
 
Process > Length
 
That brings up a dialogue box.
 
In that box, make sure that "Start Times" and "Durations" are ticked.
 
Set "By" to 80 percent.
 
This will move all the notes back onto the beat.
 
I'm off to bed now... I'll call in first thing to see how we've progressed 
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account