MOTUNATION (formerly UnicorNation) is an independent community for discussing Digital Performer and other MOTU audio software and hardware. It is not affiliated with MOTU.
Forum rules
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
And I continue to say this issue comes close to false advertising, as on the MOTU website, they specifically mention syncing Stylus RMX on their 'PT8 support page' of DP7 features:
Yes, I agree! I've had to write 38 cues last week, and a lot of them were at 120bpm! just because that was easiest solution.
But, I'll tell you I'm getting better at composing in Pro Tools 8.
Got to go now and see if MOTU has posted an update with the tempo sync fix....
In MAS-mode with any audio-driver (digi or system-audio) there´s not such a problem, it´s an issue with the combination Leopard, PPC and PT HD hardware and only if DP working in DAE-mode
DOH! DAE!
|l|OS X 10.12.6 |l| DP 10.0|l|2.4 GHz 12-Core MacPro Mid-2012|l|40GB RAM|l|Mach5.3|l|Waves 9.x|l|Altiverb|l|Ivory 2 New York Steinway |l|Wallander WIVI 2.30 Winds, Brass, Saxes|l|Garritan Aria|l|VSL 5.3.1 and VSL Pro 2.3.1 |l|Yamaha WX-5 MIDI Wind Controller|l|Roland FC-300|l|
So I have heard from my open tech link on this issue:
(as of 11/25/09):
We have reproduced this issue and we hope to address it in a future update of Digital Performer 7.
So at least it is acknowledged. Those of us who use DP 7 with DAE need to keep on this and other DAE related issues.... But fingers crossed there is progress.
Just curious, re this issue - I had a problem in DP 5.13 with Stylus RMX and tempo sync. Not quite as cut and dried as what you're describing - the "next beat" previewing mode didn't work. After flailing around, I found that the fix was to change my DP tick resolution from 960 ticks/quarter note to 480 ticks/quarter note. Totally solved the problem. This may seem like a dumb question, but can you confirm that the tempo sync problem exists with the resolution set to 480?
I checked that out, and confirm that it doesn't make a difference what the tick resolution setting is set to.
I can also confirm that the 7.02 update still has the same issues with tempo sync under DAE mode.
And keep in mind, this isn't just a Stylus issue, it holds true for any plug in getting it's tempo from sequence tempo, including the Waves H-Delay, Omnisphere, etc etc etc.
workshirt wrote:I checked that out, and confirm that it doesn't make a difference what the tick resolution setting is set to.
I can also confirm that the 7.02 update still has the same issues with tempo sync under DAE mode.
And keep in mind, this isn't just a Stylus issue, it holds true for any plug in getting it's tempo from sequence tempo, including the Waves H-Delay, Omnisphere, etc etc etc.
aargh.
And yet... still MOTU trumpets that they're the best front end for PT hardware. This makes it DP7 completely unusable for me. "Aargh" indeed... but thanks for checking it out.
Agreed. I really feel that this quote from their upgrade splash page should be revised:
Digital Performer fully supports TDM and RTAS plug-ins that receive MIDI data, including: the click (accented/unaccented beats), MIDI Beat Clocks, MIDI Time Code, and meter/tempo information. For example, you can use the Digidesign Click plug-in, as well as other RTAS plug-ins that require tempo and metrical information. As another example, you can use the beat and tempo based features in the RTAS version of the Spectrasonics Stylus RMX virtual instrument.
Since none of it is true under DAE. MOTU specifically mentions stylus in this paragraph in a section very near the DAE improvements section. One might think there was some false advertising going on.
My open tech link mentions that it is a problem they are aware of and will be addressed in future versions of DP. I would LOVE for anyone from Motu to weigh in on this....
<<I would LOVE for anyone from Motu to weigh in on this....>>
And world peace would be nice!...:=) But hey, let's live and hope. At least they've acknowledged it. And I have to believe this is big enough for them to fix.
Pardon my ignorance, but is this the same problem that is causing me to not be able to enter any numeric data in AudioSuite plugins? For example, in Pitch-n-Time Pro (which always worked flawlessly in DP5 on Tiger) it won't let me enter tempo info for source BPM or target BPM. This is very frustrating. I can move the slider and get the end-result, but I can't tell it to, say, change a soundbite from 100 bpm to 110 bpm. Can't change tempo data in echoboy either. All work fine in ProTools.
On a side note, does anyone know of a good - hopefully simple - calculator to figure out these bpm shifts in case I can't get this going. Thanks!
DP 7.1 seems to have fixed the tempo sync problem. I'm currently running DP 7.1 with ProTools HD 8.01cs1, and the issues I had with tempo sync seem to be fixed. I've tested with Stylus, Omnisphere, and the Waves Hybrid Delays.
DP 7.1 seems to have fixed the tempo sync problem. I'm currently running DP 7.1 with ProTools HD 8.01cs1, and the issues I had with tempo sync seem to be fixed. I've tested with Stylus, Omnisphere, and the Waves Hybrid Delays.
DP7.1 now running on PPC / Leopard, PT8 (had always crashed on hitting play/rec)
but still it´s not possible to enter numerical values in TDM-plugs (with rtas plugs there´s no problem)
DP 7.2, Logic 9, PT HD 8 , G5, macmini with VE Pro http://www.live365.com/stations/perfect" onclick="window.open(this.href);return false;" onclick="window.open(this.href);return false; ... /?site=pro
