Crash on exit in cubase

[o_range]

I know - there are very many variables, especially with windows PCs

A lot of the problems are Steinberg's making, although they love to blame plugin manufacturers for this kind of thing. I've been fairly lucky with it over the years though.

current cubase 10.5.10/12 has a crash on exit bug with rewire - and the recent mac version has been a bit of a disaster too - but I'm convinced that this bug is JS as it doesn't fit the normal cubase crash profile.

Cubase 10 was pretty solid for me too - there should be a v10.0.60 coming very soon....it will probably break more than it fixes but it's gonna be the last v10 update.

(fwiw been with cubase since 1989 !!!!)

[C_Holdz]

I love cubase as well, I think its the best DAW (for windows) by leaps and bounds, but cubase 10.5 pro has a couple of bugs too.... it seems other daws havent had issues with it though, even though it doesn’t help Cubase users like us...anyway , maybe there will be an update or something for both steinberg and rayzoon?

[o_range]

I love cubase as well, I think its the best DAW (for windows) by leaps and bounds, but cubase 10.5 pro has a couple of bugs too.... it seems other daws havent had issues with it though, even though it doesn’t help Cubase users like us...anyway , maybe there will be an update or something for both steinberg and rayzoon?

the crash is within Jamstix code so that what needs fixing - not a cubase problem as such...but yes Cubase 10.5 has plenty of bugs too

[C_Holdz]

I know it might be somewhat inconvenient if you don’t do backups but have you tried windows fresh install?

I think it’s the BESt feature of windows 10. You can basically get a brand new fresh OS and windows does it itself .

I did it after installing and uninstalling some software and the registry was beat, and I’ve had zero; and I mean zero; issues since I did it.

Just a thought

[o_range]

I know it might be somewhat inconvenient if you don’t do backups but have you tried windows fresh install?

I think it’s the BESt feature of windows 10. You can basically get a brand new fresh OS and windows does it itself .

I did it after installing and uninstalling some software and the registry was beat, and I’ve had zero; and I mean zero; issues since I did it.

Just a thought

appreciate the advice and obviously I'm doing backups (!) but that's a massive sledgehammer to attempt to crack the issue.

I have zero other issues - apart from documented bugs etc - this one is pretty clearly a problem within Jamstix - obviously may be something specific to my config but that's the config I use so not going to change it because of a jamstix coding error. May even be related to my other HiDpi bug, Most people aren't going to notice it because it's a crash on exit and only shows up on the logs...have you checked your logs ?

If you are seeing 'zero' issues then maybe look again....all modern software has bugs and issues - even the very latest builds of of windows 10...maybe you're not triggering them but they are there...as I say - take a look in your windows logs and then say you have zero issues

[C_Holdz]

You are right about “the surface” vs the logs....I just mean, I haven’t had crashes, error messages, delayed/lagging or frozen prompts and license checks. It just feels much smoother.

I have auto backups on an external so I dont care about doing a fresh install, like I mentioned it maybe inconvenient to some; I really appreciate it though.

Anyway, yes man, good luck either way, and I hope it gets resolved.

[Ralph @ Rayzoon]

Another fix for the crash on exit issue might be to check 'Use APS Mode' in the 'Troubleshooting' tab of the JS4 manager tool.

[o_range]

Another fix for the crash on exit issue might be to check 'Use APS Mode' in the 'Troubleshooting' tab of the JS4 manager tool.

hi Ralph - yes this mode fixes the crash ....and the "high DPI" error message BUT it's unusable because when I click on the JS GUI it disappears. ALT-TAB brings it back but obviously if you can't click on it......

we went through all these steps last year via email....the last email you sent me was in December was...

Please bear with me as I try to find a solution because I don't see a rollback fixing this.
Cubase 10.5 was only released a little over a month ago IIRC. The error you are seeing is triggered by Windows saying that the high-DPI context of the Cubase window given to Jamstix is not compatible with the context of Jamstix, which is high DPI-aware. This context is the same going back many Jamstix 4 versions. The issue does not require a 4k monitor being present. I only zeroed in on that monitor hoping it would run the same context when I saw 4k width data for it.

I propose to find a solution here but this will take me a few days. Is there any chance you could just work with Cubase 10 for the time being until we have a fix for you?

but that was nearly a year ago and I haven't heard anything since - and there has been no updates ?

[o_range]

bumping this

it would be really good to see a fix - or an update ?