Post by DrCobalt on Jun 21, 2019 13:20:16 GMT 1
Hi Folks -
'm tearing my hair out. I am STILL trying to update a project I made in SE 1.01x to SE 1.3 and maybe SE 1.4. So, I have been advised tht it might be best to update the SE1.01x project to SE1.2 first, etc. This has been tedious, but now things have changed for the worse.
Even though my project USED to work fine in SE1.101x, it now crashes under the following circumstances:
(Using SE1.01x - in which the project was built and had worked fine for a long time...)
Now, the Project loads fine and works fine if ensemble is UNLOCKED...
1. Project crashes when I try to lock the ensemble when audio engine running.
2. If I try to lock when the audio engine has not been started, it locks fine BUT Project crashes when audio engine turned on
3. If I reload the unlocked ensemble and lock it before the engine is turned on AND THEN SAVE it and close out. The Ensemble will load fine BUT will crash when the audio engine is started.
I don't know what could have changed to make this behavior start.
Can anyone give me a clue as to what might case this sort of behavior and how to fix it?
Thnx
'm tearing my hair out. I am STILL trying to update a project I made in SE 1.01x to SE 1.3 and maybe SE 1.4. So, I have been advised tht it might be best to update the SE1.01x project to SE1.2 first, etc. This has been tedious, but now things have changed for the worse.
Even though my project USED to work fine in SE1.101x, it now crashes under the following circumstances:
(Using SE1.01x - in which the project was built and had worked fine for a long time...)
Now, the Project loads fine and works fine if ensemble is UNLOCKED...
1. Project crashes when I try to lock the ensemble when audio engine running.
2. If I try to lock when the audio engine has not been started, it locks fine BUT Project crashes when audio engine turned on
3. If I reload the unlocked ensemble and lock it before the engine is turned on AND THEN SAVE it and close out. The Ensemble will load fine BUT will crash when the audio engine is started.
I don't know what could have changed to make this behavior start.
Can anyone give me a clue as to what might case this sort of behavior and how to fix it?
Thnx
