PlanetZ forums - scopeusers.com

After installing Reason 10.3 it crashes accessing Scope on startup. Interested to see if mine is an isolated case (any other Reason users here ?)

Here is the ticket I raised with Propellerheads :

just sent the Reason patch, but you may already have that....

otherwise, Propeller Heads will have to make a new patch.

Nope didn't work - I thought it did initially, as Reason started - but as soon as I selected 'Scope XITE in the Reason Audio setup, crashed. So I will wait for the PHeads.

Meanwhile I've set up alternative I/O and run the new Reason that way. I can still run the old Reason - but ATM I need the VST optimisation more than I need Scope.

as you wish.

as i understand it, Reason is asking questions of the soundcard that cannot be answered. there is no reason such queries need to be answered, except to gain control of the soundcard. Scope is not controlled by Windows, so the hardware can't respond to the software's actions(no ASIO panel in the application). this is my non-technical summation. there might truly be a simple solution. the patch has always addressed this issue in the past(Reason doesn't HAVE to make such queries to the soundcard).

this might be a different issue.

i will let Holger know.

Yeah its a different issue. I have dual boot so Reason 10.2 is on the other boot partition so I made a shortcut to it and can run it at will and I believe it will still pick up the (same) preferences file from the current partition and use Scope OK.

I would guess Propheads have modified the initialisation of audio ports as part of their audio engine rework (which has taken a few months). So if you disable Scope in device manager prior to starting Reason then select the MOBO driver, then close Reason - re-enable Scope in device manager, then restart Reason it will start OK because it remembered the last active (non Scope) audio driver. So then, if you go to Reason then try to select Scope as its audio port, then crash occurs. So then - after reboot from crash - you have to disable Scope in device manager - restart Reason and select Mobo sound. From there its OK again (but no Scope).

that sounds like the same issue, re-broken.

Here's reply from the props :

"Thanks for reporting! If you install a logging version of Reason 10 on your computer, R&D can use the logs to pinpoint what goes wrong. You can download a logging version of 10 here:
http://cdn.propellerheads.se/logging/re ... dbanks.zip

This version will install to a different folder than your current Reason installation, and will leave your standard version unaffected. Please run this, re-create the problem/crash and send us the log files generated by Reason. You'll find the logs in Documents\Propellerhead Logs

Please report back!"

So I've sent logs back to props and Holger - keen to know if anyone else wants to try logging ver and gets the same crash or not.

latest reason crashes on load here too, win10

Thanks Faxi that reduces the chance of it being an issue with my workstation !

Just got the following from the Propheads - if anyone else wants to test. Ill test tomorrow & fwd to Holger

Hello
We are working on a fix to a similar problem as the one that you reported.
It would be of great help if you could try to reproduce it in this build:
https://www.dropbox.com/s/wiwwnz91yp4pd ... s.zip?dl=0
https://www.dropbox.com/s/h4ssrg89s3y4i ... s.dmg?dl=0
This is a slow logging build just meant for testing this problem, so please switch back to normal Reason version when you’ve tested this.

Its Fixed ! In update Reason 10.4. According to https://www.propellerheads.com/en/reaso ... ease-notes release notes :

Made a change on Windows to allow certain ASIO drivers incompatible with Reason 10.3 compatible again

nice one! awesome