Orion host issue-'mm timer can not be initialized'
Posted: Mon Oct 28, 2013 1:31 am
Heya,
I see that our devs have their hands full dealing with bugs recently,
That .exe CPU issue is a real pain in the neck.
After building some full projects in Orion,
the multiple instances bug is solved.
However something else has come up,
it is Orion specific.
The playlist cursor in O uses 'mm timer',
Windows multi-media timer. When loading a new FS plug,
it will stop the timer, if the audio engine in O is not running-
and give 'Error-mm timer could not be initialized'
If the engine is switched on, there is no error.
This bug has only developed in a project with like 15 tracks,
so a somewhat full mix.
To delete an instance, the engine has to be stopped,
otherwise O hangs, need to be stopped from task manager.
So it's a little rocky and easy to crash Orion atm.
I would really appreciate a fix.
Thanks RDSP
I suspect this bug has to do with initializing part of Ruby's timing systems,
but it's just a guess.
little edit- this isn't system specific IMO,
I have the same behaviour on both my systems-
running Win7 on one and 8 the other
I see that our devs have their hands full dealing with bugs recently,
That .exe CPU issue is a real pain in the neck.
After building some full projects in Orion,
the multiple instances bug is solved.
However something else has come up,
it is Orion specific.
The playlist cursor in O uses 'mm timer',
Windows multi-media timer. When loading a new FS plug,
it will stop the timer, if the audio engine in O is not running-
and give 'Error-mm timer could not be initialized'
If the engine is switched on, there is no error.
This bug has only developed in a project with like 15 tracks,
so a somewhat full mix.
To delete an instance, the engine has to be stopped,
otherwise O hangs, need to be stopped from task manager.
So it's a little rocky and easy to crash Orion atm.
I would really appreciate a fix.
Thanks RDSP
I suspect this bug has to do with initializing part of Ruby's timing systems,
but it's just a guess.
little edit- this isn't system specific IMO,
I have the same behaviour on both my systems-
running Win7 on one and 8 the other