Can you help on a simple test ? I have a thread already for this link below but now think its Sequoia and C14
If I highlight any bars/beat numeric Field (by double clicking) and then re check on it C14 quits, can be an empty project with no tracks.!
Thank you so much for trying this, I believe this could be most of my (what I thought were random quits) over the past month in C14 as I just didn’t noticed I was double clicking the text feild! only found this while programming LE presets .
Martin jirask , has been helping me with this , he doesn’t have the crash, but is running OS14 .
I just got a new MAC M4 so everything is updated. So I hope not too many bugs on latest OS with Cubase 14 as I am just getting starting on the MAC platform.
Yeah, that’s it, Great to get confirmation I’ve done everything. I’m a bit of a Mac expert. It led me to believe it had to be something to do with Sequoia.
Same behaviour here too! Cubase 14.0.10 on Sequoia 15.3.1, M2 Max. Crashes Cubase whether bars and beats, seconds, timecode. First double-click in the box, clear the contents, then click once in the box again. Cubase instantly disappears.
Just heard from Steinberg they can’t reproduce this at this point so anyone else running Cubase 14.0.10 on Sequoia 15.3.1 on apple silicon , please give this quick test a try thanks
I managed to reproduce that once on Sonoma 14.5 by double clicking the right locator box on the transport panel and it crashed after a few double clicks.
But I could only reproduce it once. When I tried again in an empty project and one of my larger projects I couldn’t reproduce it, so it seems like an intermittent bug. Mac M2, Cubase 14.0.10.
Reproduced on C14Pro as well (Not N13). If I double-click in the location you identified in your screenshot, the field contents become highlighted as shown, and if I then click on that field again, I get a hard crash/exit as well. MBP Max M3 build on Seq 15.3.1. Here’s a copy of your screenshot for reference and my crash file.
Maybe this needs to made into a reproducible bug report? @Martin.Jirsak, do we need to do more with this? Three reproducible crashes on three different machines (sorry four) running Sequoia 15.3.1?