Conductor Track--tempo events entry beat value issue--need solution-

[greg328]

Hello all-

I'm experiencing an unexplainable problem as I attempt to enter tempo beat events in the conductor track.
This problem occurs both when drawing lines/curves with the pencil tool, and entering single events with the pencil tool.

I am needing specific beat values for these events of course, and I've selected that value in the right-side drop down menu in the conductor track, where I can select the appropriate beat value. In this particular song, I'm needing dotted quarter beat value in 9/8, and then quarter note beat value when it switches to 3/4. I adjust the right-side drop down menu tempo beat value accordingly, but when I enter tempo events, they are consistently dotted 16th notes! Not even close to what I'm specifying. I'm having to manually edit each event to the correct beat value, which of course is extremely tedious.

I've even adjusted the grid value setting, with no effect. Of course, this just affects the grid and not event entry values.

Surely I'm missing a setting somewhere--right? Any assistance greatly appreciated as I'm in the middle of a large orchestral project and needing to enter LOTS of tempo beat events!

[stubbsonic]

I was just doing some tests with this; and I couldn't find any combination of things to make this work.

It's super-annoying because DP has already made selection and the playback wiper follow the grid setting (as opposed the older behavior where it never snapped -- which I prefer). In this case where we might want the option to have the tempo events follow a grid snap selection, there doesn't appear to be a way to do it!! Grrr.

Hopefully, someone can chime in about how to make this work. It does seem VERY useful.

[greg328]

Thanks Jon--so it's not just happening to me!

Very odd--and very inconvenient that MOTU sets the default beat value for entered tempo events to a TINY value!

I would categorize this bug as "inexcusable".

Greg

[HCMarkus]

Thanks Jon--so it's not just happening to me!

Very odd--and very inconvenient that MOTU sets the default beat value for entered tempo events to a TINY value!

I would categorize this bug as "inexcusable".

Greg

Please report to MOTU.

[greg328]

Im currently discussing the issue with Matt at MOTU. I’ll report any useful findings here.


Sent from my iPhone using Tapatalk

[stubbsonic]

I want to make sure I understand the issue. Here's what I'd like to see, can you see if I'm on the same page?

1. Be able to draw/drag tempo changes with a pencil at a particular grid resolution such that tempo changes will be placed on the time-line at the same resolution that is set in the grid value (if grid-snap is on) and if the grid-snap is off, then it will work as it does now.

2. The note-values of tempo events (i.e., X-note-value = Y BPM), should match the note-value of the "click" part of the current meter, any time tempo events are clicked or dragged in that particular section. This way, a section in a 9/8 meter with a dotted-quarter note click will by default have tempo events based on dotted-quarters for that section.

[greg328]

Jon--Drawing tempo curves that match the grid resolution is not an issue for me -- pretty sure that works fine but I'll check later today-

As I understand it--the note value attached to a time signature event is the click resolution-not necessarily the same as the beat value. For example, I've selected dotted quarter for my beat value when I create the meter/time signature. After this, I can click on the note value of the time signature event and switch to eighth note--so my click is now on every eighth note, but beat value (as witnessed in the counter) is still dotted quarter-- "Fairly" sure I have that right--I'll confirm that too, later today!

My issue is--the pencil tool will NOT honor the chosen tempo beat value selected in the right-side conductor track contextual menu. It usually creates tempo events with either eighth or sixteenth note beat value--which is of course ridiculous. So--I have to manually adjust each event.

Matt at MOTU and I are in discussion--will share my findings--
Greg

[Phil O]

Thank you, Greg, for this thread. This has been bugging me as well and I haven't had time to pursue a solution. Please DO report back on what you find out. It will be very helpful.

Your friendly neighborhood Phil

[greg328]

My pleasure, Phil, Matt has been silent the past day or so--maybe he's off during the week?

Good to know that last least 2 others on here are experiencing the same issue--that means it's a real bug! I'll let Matt know.

BTW, I opened a fresh, empty DP session with no data or plug-ins loaded, and was able to pencil draw accurate tempo events--so something is going on once a session loads up, either with MIDI data or plug-ins--who knows?

And who among us has time to experiment with EVERY possible permutation of what we use to figure it out??

Greg