From the original SynthMaker forum (2004–2014), with its members’ names and dates.
FreeRideSkier ·
On my industrial application I appear to have some instability regarding generating Midi.
We are using Midi to communicate with external relays and basically have 24 sensors that can generate a midi event. All of the events are on one midi channel and the different note numbers are used to communicate to the relevant relay. Currently there is no external hardware connected for test, so just my SM app. and a Midi interface ( Tascam US-1641).
I suspect that the problem (crash) occurs when two or more midi event are generated simultanously. I have wired all of the 24 midi wireless out links to one link in point, and then connected this to the Midi out module. ( Is this correct?)
I have also tried to use the 'Midi buffer' to receive the midi events and then flushed it every 10th of a second, but this also crashes.
If I remove the Midi from my application it is then stable.
Any Ideas?
FreeRideSkier ·
More information:
Firstly I am running as an .exe
To help rule out a specific Midi driver I have tried it with a internal Midi Loop back driver (LoopBe1), and the results are slightly better although ultimately it still crashed eventually. I also updated my Tascam Midi Driver as there was a newer version, which also improved the situation, but didn't solve it.
And last night It ran successfully over night for 12 hours, so I thought great and closed my app. at which point it crashed!
I have seen this a lot with SM, everything is fine but things crash when you close them including the SM program itself???
Focusing on my issue, things are also made less stable with screen savers or switching between different programs. Also this little test app. if far better than my actual real app. which is significantly bigger. So it could indicate some form of CPU overload.
For reference My CPU is running at 50% with my big application.
sunsynth ·
Hi FreeRideSkier,
please have a look here: Using timers with MIDI
Because the link is broken i attached the OSM...
Which version of SM do u use?
btw: wonderfull Led 😉
and don't forget 2 send malc ur crash reports!
exonerate ·
I'm not getting crashes here using the latest beta.
It's probably better to use the beta there's a lot of fixes in it, it's been in development for almost a year and is actually (from my experience anyway) more stable than the last official release.
Cheers 😉
Exo
FreeRideSkier ·
I was using the release version, but for the last few days I've been using the beta. The end result is the same.
I'll have a look at the thread proof timer and see if that helps.
thanks
FreerideSkier
PS. I made the LED's in 3DS Max
FreeRideSkier ·
More tests:
I just received the new boards yesterday for our embedded PC hardware, I was hoping that since these are super powerful they might solve my midi crash bug. (New Embedded PC: my app. uses 12% of the CPU vs My development PC 50%)
But unfortunately not, this was a clean XP install (SP3) with just my SM application running, it crashed after 12 hours of testing. Same app. with the Midi out link broken runs all day no problem??
So basically it comes down to, no midi out ok, Midi out crashes (usually within 12 hours).
The Midi in this case is used to control external relays so the amount of data is quite small. Ultimately if this issue isn't resolved then it can be worked around using 8 little console .exe's written in C++ to control the hardware outs on a USB relay board, instead of Midi. But this is a little messy!
Any Ideas Anyone??
sunsynth ·
DJGrobe has this probs 2 and i have the same and faster killer with midiCC in's!
Malc is/was working on it and said it's a multitasking(interrupt?) thingy...
My midiCC'ing is more stable now but crashes randomly even with one remote slider/knob with my standalones... 🙁
Have u checked the Interrupts XP is using? Often Soundcard and GPU uses the same and this can make probs 2!
FreeRideSkier ·
I've now tested it on our target hardware using Windows Embedded. On this set-up it seems to be ok with the Midi!
I think this issue with the midi out is a CPU power/timing issue. Occasionally the midi driver locks up when some other multi tasking operation takes over. The screen saver for example makes it worse. Fortunately on my embedded system there's not a lot else running.
infuzion ·
FreeRideSkier wrote: But unfortunately not, this was a clean XP install (SP3) with just my SM application running, it crashed after 12 hours of testing. Same app. with the Midi out link broken runs all day no problem??
SM has serious issues with making alot Page Fauts (as viewed in Windows Task Manager). I had observed a correlation between high Page Faults & long-use crashing in the old (1.x) vs new versions (2.x) of Firefox. As Firefox crashed less often, I noticed fewer Page Faults while running also.
SM makes Page Faults just by being open, many more with copy/paste, running, etc... so I think all the PFs catch up with SM & cause a crash after a while. I try to close out SM every 30-60 minutes.
I'm not sure if PF are caused by the parts of a program that also cause crashes (so more crash-bugs fixed = fewer PF indecently), or if the PF directly cause crashes, or both? MicroSoft officially says that Page Faults are a non-issue, but there you have my theory.
infuzion ·
FreeRideSkier wrote: ...this was a clean XP install (SP3) with just my SM application running
BTW, here are some links for the "cleanest XP install" possible:
[old link]
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker