From the original SynthMaker forum (2004–2014), with its members’ names and dates.
trogluddite ·
Been pulling my hair out over a schematic that worked fine all afternoon, but now instantly crashes SM whenever I try to re-load it.
After lots of pulling things to pieces, I found some very odd behaviour - I'd like to know if this is this same on anyone else's machine, or if it is a weird soundcard driver type error. It's very quick to test...
1) Open SM with an empty schematic.
2) Drag in one ASIO In primitive and one ASIO Out primitive, and select your soundcard.
3) Drag in one Mono to Float primitive and connect its mono input to one of your ASIO ins.
That's all - on my machine, I get the 'Synthmaker has encountered a problem' box - and SM will not close without going to the task manager.
The only thing I could think of is that somehow opening an ASIO input before opening an output is fouling something up. Yet, I can get my 'broken' schematic to work every time if I connect a mono readout to the ASIO input before connecting up the rest of the schematic - but a mono readout has an M2F as it's first primitive!!
infuzion ·
Works fine here. You have to post full specs of your system it seems. Or mail your computer to Malc 😉
trogluddite ·
Thanks infuzion - that was my suspicion - just thought I'd do a quick check here before adding to Malc's 'to do' list.
infuzion ·
trogluddite wrote: Thanks infuzion - that was my suspicion - just thought I'd do a quick check here before adding to Malc's 'to do' list.
Welcome! You do have to note that there is no audio actually coming in from the ASIO driver though.
Then maybe you should label the title "Not a bug" or something?
aliasant ·
Works fine here too :/
trogluddite ·
@aliasant
Thanks for the confirmation.
@infusion
Yes, I'll see if I can find a workaround first -can't really expect Malc do a lot of fiddling with the SM code just for one rogue driver. The drivers for my mLAN system have always been a bit flaky like this, and Yamaha stopped supporting them years ago.
infuzion ·
trogluddite wrote: @infusion
Yes, I'll see if I can find a workaround first -can't really expect Malc do a lot of fiddling with the SM code just for one rogue driver. The drivers for my mLAN system have always been a bit flaky like this, and Yamaha stopped supporting them years ago.
Fix action: Get a new sound card!
trogluddite ·
infuzion wrote: Fix action: Get a new sound card!
Maybe when I win the lottery! 😉
Sadly, there's not much about that would replace my mLAN system without spending far more than I can save or borrow. It's not just a case of the audio/MIDI I/O - it also incorporates a control surface, 32ch digital mixer, virtual patchbay, 2 FX units and extended I/O in another room networked via firewire. I suppose all those goodies in one box was so cheap because Yamaha decided not to invest in any decent customer support. 😠
Luckily I've found an easy workaround - just editing the schematic in any tiny way before connecting the audio seems to fix the problem - I'm guessing it's a memory allocation problem that sorts itself out when you force the schematic to re-complile. Exported stuff all works fine.
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker