Hi Martin, thanks heaps for testing. Can you confirm a couple of things?
Likewise, I can manually warp the tempo by using the warp tool in the tempo track.
My crash occurs when the Detect Tempo window is still open after using the Analyse function. My workflow (used to be) to analyse, then working through the event, adjusting manually for anything that wasn’t correctly detected, with the detect / analyse function still open and working to adjust points to the right of my manual corrections. This is the scenario that crashes.
Do you also have the detect window open after having first done the analyse in say a 96k project?
Yes that’s the only way… which is what I’ve been doing when pressed. However, inevitably the detection is wrong anyway (especially for 96k projects), so you end up having to make so many manual adjustments that it’s easier to build the tempo map from scratch. For projects that include time signature changes (for some reason I get too many of those!), there’s the added hassle of having to delete a whole bunch of tempo points too. Bottom line is that the tool is broken.
Not sure if it’s related, but another issue that got me last week was hit point detection in a midi track. The midi was recorded in to a 96k project without click. I needed to build a tempo map from the midi event and tried the detect process. It got it badly wrong per bug, but then I dropped the project back to 44.1 (and in trying to find a solution also exported the midi and imported into a fresh 44.1 project), however the hit point markers in the midi file persisted making it impossible to quantise or do any tempo detection. Ended up getting the musician to re-record into a 44.1 project.
Overall this whole area of tempo / tempo track / hitpoints seems to be going down hill in Cubase.
Hi,
I am experiencing a similar bug on my Mac. Specs are i7 with 32 gigs of RAM and Radeon graphics card. Interface is an RME Fireface 800 or a Universal Audio Apollo 8p.
Whenever I do analyse on tempo detection, it performs the task. But as soon as I click either continue or cancel to change tools, Cubase crashes.
I forgot to note down the error code, but this is definitely happening on the MacOS platform as well and is not just a Windows bug.
I’m sorry, I’m not a developer to be able to read the crash files properly and completely. I see all 3 crashes are the same, but I can specify what exactly caused the crash. If I would send it to Steinberg, they would ask to update Cubase first.
Apologies for confusion Martin. I’m not the one with the crash reports. I’m the one that created the thread. You indicated that that the bug was confirmed and you were sending to Steinberg previously. The post with crash reports was a later addition by Jimmy_Rage, not I.
So on the basis of your original response to me, have you reported this bug and is there a CAN issue number?
