Quantization Quandry

obmit · Post by **obmit** » Tue Mar 28, 2006 11:44 pm

My DP has gone nuts, or I have. I am quantizing MIDI data and it thinks evey thing is a triplet. What is clearly a group of 1/8 notes must be quantized as 3/2 tuplet. If I leave it as a 1/8 setting it quantizes as if it is 1/4 triplet. If I do a set duration, those setting are good, an 1/8 is 240 ticks. The file is OK as on another machine it is fine. I also tried an older file and it has the same problem. Have treid it with conductor track on and off.

It all started when I was trying to convert a file in 4/4 to 12/8. I did it, but ever since I have had this strange problem. I have trashed prefs and restarted, ran the 4.61 updater again, all but reinstall. I am on a G5 dual 2.5 and have no other problems.

Anyone ever had it?

Obmit

kelldammit · Post by **kelldammit** » Wed Mar 29, 2006 1:16 pm

hmmm...and the "tuplet" box isn't checked in the quantize window?
that's just weird.
mebbe try checking it and unchecking it, and resaving the project?

kell

obmit · Post by **obmit** » Wed Mar 29, 2006 1:38 pm

Tried that, bit no luck.

kelldammit · Post by **kelldammit** » Wed Mar 29, 2006 1:43 pm

what about your grid values in the MIDI editor? do you have "snap to" on? at what value? that shouldn't muck with quantization, but you never know...

kell

obmit · Post by **obmit** » Wed Mar 29, 2006 1:58 pm

With or without grid, same thing.

kelldammit · Post by **kelldammit** » Wed Mar 29, 2006 2:49 pm

hmmm. then stop playing everything in triplets!

seriously...i have no idea...that's really bizarre.
all i could think to do is to undo all the quantization, export all the MIDI as a MIDI type 1 file, create a new project, and import the MIDI file into that.
does it exhibit the same behavior on every file? or just this one project?

kell

Shooshie · Post by **Shooshie** » Wed Mar 29, 2006 4:34 pm

obmit wrote:My DP has gone nuts, or I have. I am quantizing MIDI data and it thinks evey thing is a triplet. What is clearly a group of 1/8 notes must be quantized as 3/2 tuplet. If I leave it as a 1/8 setting it quantizes as if it is 1/4 triplet. If I do a set duration, those setting are good, an 1/8 is 240 ticks. The file is OK as on another machine it is fine. I also tried an older file and it has the same problem. Have treid it with conductor track on and off.

It all started when I was trying to convert a file in 4/4 to 12/8. I did it, but ever since I have had this strange problem. I have trashed prefs and restarted, ran the 4.61 updater again, all but reinstall. I am on a G5 dual 2.5 and have no other problems.

Anyone ever had it?

Obmit

I'm just guessing, of course, and may be completely off base, but I think you need to retrace your steps at the time of the change of meter. It sounds to me as if you made a mistake in the meter-change from 4/4 to 12/8, probably having to do with a dot. Maybe you were trying to make a dotted quarter = 1 beat. I'm not in front of DP, but I'm thinking that's not quite the right thing. I'd have to mess with it to figure out exactly what went wrong, IF it's what I'm thinking. (On the other hand, you may be right, and DP may have just flipped out on you.

)

Further, it would seem that this became a template, somehow, and descendents of that file are inheriting the problem. This is all very speculative; more of a feeling than a solid suspicion, but if you would retrace your steps, you might find the problem. Just remember that in Digital Performer, compound meters take the 8th note as their beat, not dotted quarter notes. You have to adjust your thinking to the beat falling on 1, 4, 7, 10.

Shooshie

simdrum · Post by **simdrum** » Fri Jan 05, 2007 5:15 am

I am having the same issue-- i have no idea why it happens, but quantizing is def not working-- it is very bizarre...i have a mac lab of 20 computers in a high school and this is happening on 2 of the 20 stations.....

mongoose · Post by **mongoose** » Fri Jan 05, 2007 6:35 am

Have a look at the conductor track in the event list editor. I had a problem last week where the click had seemingly gone mad; it turned out there was a spurious dot (beat set to dotted eighth rather than eighth) in the meter designation that only showed up in that editor. Dunno how that happened, but it's worth a look.

-m

simdrum · Post by **simdrum** » Thu Jan 11, 2007 4:40 am

Did anyone ever find a fix for this problem? I am still having the same issue, regardless of all of the fixes i tiried.

Shooshie · Post by **Shooshie** » Thu Jan 11, 2007 7:01 am

simdrum wrote:Did anyone ever find a fix for this problem? I am still having the same issue, regardless of all of the fixes i tried.

Simdrum, did each student create their own file in those 20 computers, or is it the exact same file with the exact same changes that works differently in the 2 computers where you find the problem? If the students did it, then it would stand to reason that 2 students did something differently.

I cannot help but think it has to do with the "beat" setting in the change-tempo dialog. Have you tested it? Have you looked at the beat setting in the Event Edit Window? A mistake in that area could possibly produce a mistake of this sort in the quantize function if the programmers were not careful in how they were merging all these functions in their algorithms. Something has to act as the master timekeeper, and each of these functions alters that master time. Where the Quantize function looks for its reference time would affect the outcome of its actions. This sounds like a deep bug, and one which under most circumstances would not be seen. If you can figure out where it's coming from, then MOTU could replicate it and fix it. I have yet to see it, so I am no help at this point.

Can you step through undo, back to the meter change, and try different configurations in the meter-change dialog?

Shooshie

MOTUnation.com

Quantization Quandry

Quantization Quandry

Re: Quantization Quandry

Quantizing problem

Quantizing problem

Re: Quantizing problem