From the original SynthMaker forum (2004–2014), with its members’ names and dates.
Shifrin ·
Hi,
Check out the following .osm :-
Stage0Bug.osm
It's a simple schematic with a basic saw-synth feeding a lowpass filter. I want to keep the filter at a fixed frequency/resonance so I only need to calculate the filter coefficients once! At the moment they are calculated every sample.
It is my understanding that if I move the filter coefficient calculations to a :-
stage(0)
{
...
}
...then they'll only be calculated once. Saving many CPU cycles! However if I take the could between the comments (the coef calculations) and move them into a stage(0){...} construct I get a bunch of crashes. Sometimes it works a while but crashes on reloading. Sometimes it'll seem OK but crash when I press a key on my controller.
Also, when this schematic crashes SM and I reload (sometimes I have to remove the recovery file too as it will continually crash on loading after the initial crash) I often find I am unable to select MPU-401 as a midi input source. It seems to 'freeze' it out and can't be selected even though it is listed!
After a few restarts without crashes I am able to select the MPU-401 midi input again. This is something that has happened before by the way - I'm sure I've mentioned it and it seemed to work OK for a while. But problems again now unfortunately!
Shif.
unkargherth ·
I have no idea on MPU issue but for the crashing when playing notes, take the following into account:
The stage(0) get executed once ( on link time ) for MONO code. for Poly code it gets executed Once for every Note on. Also al Stage0 sections in a schematic get executed before any stage(1). Then, if something on your input values used in stage0, depends on the result of some other stage 1 code, you could find problems there
malc ·
Sorry about this Shif. I think it will need Jorge to look at the stage(0) issue. Could very well be related to the current instabilities we've been seeing after implementing arrays.
Regarding the MIDI problem - yes, you had mentioned this before, along with Tom I think. Sorry, just hadn't got round to looking at it yet 🙂. It sounds to me like the MIDI device is being left open after the crash.
Next time you get a crash have a look and see if there is still a SynthMaker process running after the main window disappears. On some occasions it can take a minute for the process to close down and it'll hold onto the midi device until this happens.
If there is no loitering process and you still get the MIDI problem then it might be that the crash still leaves the device open. Perhaps we need to do a flush on opening the application.
Anyway, let me know what happens next time and we can go from there.
Shifrin ·
unkargherth wrote: The stage(0) get executed once ( on link time ) for MONO code. for Poly code it gets executed Once for every Note on. Also al Stage0 sections in a schematic get executed before any stage(1). Then, if something on your input values used in stage0, depends on the result of some other stage 1 code, you could find problems there
Thanks for the input unk, there is no dependency on stage(1) code in the stage(0) code - just some simple calculations - which is why I tend to think this is a bug, also because sometimes it works, other times it crashes!
Good to know about the mono/poly differences regarding stage(0), cheers!
malc wrote: Next time you get a crash have a look and see if there is still a SynthMaker process running after the main window disappears. On some occasions it can take a minute for the process to close down and it'll hold onto the midi device until this happens.
I'll check it out, the thought occurred to me too - that the device was being left open and hence couldn't be reopened on restarting SM straight away!
I'll let you know how things go.
Shif.
Shifrin ·
Hi malc,
The 'frozen out' MPU-401 thing is happening a lot now for me, using the 0.9.3u beta, and without SM crashing! If I open a schematic that has a 'Midi In' component in it with MPU-401 already selected, then close the schematic and reopen it the MPU-401 is frozen! This has happened with a fair few different .osm's
Not sure why it does it?!
Anyone else have this problem at all?!
Shif.
Wrote something here? To have a post removed or your name hidden, write to [email protected].