From the original SynthMaker forum (2004–2014), with its members’ names and dates.
Disco_Steve ·
Hi I have gained an annoying problem with my synthmaker.
I have just up graded to a new machine (quad core with lots of other cool stuff) 🙂 and have moved across my old sound card and re installed the latest drivers (which were the same on my old machine).
'asio in' doesn't work properly on my new machine!? it plays back in 'packets' and if I connect an oscilloscope onto the input nothing displays. no matter how loud I sing into my mic (if I then load up sonar, recording works fine) however if I connect a mono readout analysis tool to the asio in output, it displays changing numbers but with a really low refresh rate.
I assumed that the threading in synth maker might be a touch off, so I set the affinity to only one of the cores-No help
I then set the affinity of the entire machine to only one core - no help
I just don't get it, ass all my other asio software is working perfectly.
asio out works fine, however I do get a message telling me that another instance of asiomme.dll is running when I try to use asiomme for comparison even though there are no other applications running?
my machine is xp
running synthmaker 1.1.0.
hope someone out there has had and fixed this problem as its making development considerably harder!
thank you in advance Steve
theun ·
Hi Steve, and welcome here at the SynthMaker forum!
Disco_Steve wrote: however I do get a message telling me that another instance of asiomme.dll is running
I never heard of asiomme before. Some googling learnt me that it seems to be a Steinberg driver that wraps mme (= a 'legacy' windows audio system) into asio.
Sound cards usually cannot be used by different devices simultaneously. e.g generally speaking one cannot use one and the same soundcard using asio drivers for say SynthMaker and a host. I don't know if you're trying to do that, but anyway there must be some program running that uses asiomme.dll driver. You may try to find out which application is using it by means of the windows task mananger.
I don't know details about the sound card you're using. If it's asio compatible its better to use the asio drivers that came with the card (or a newer version of that driver). Even Steinberg seems to advise (Cubase forum) to stop using asiomme. mme is already old, first introduced in windows 3.1, it's a predecessor of Direct Sound and WDM. So it seems better to use either the specific driver of the sound card or use asio4all, http://www.asio4all.com/, a driver that wraps wdm to asio.
hope this is helpful and wishing you succes, Theun
theun ·
I forgot to mention:
Disco_Steve wrote: my machine is xp
running synthmaker 1.1.0.
Current release is 1.1.1. There are some important fixes in this release, also with regard to external MIDI.
Disco_Steve wrote: I then set the affinity of the entire machine to only one core
Afaik there are no multicore problems associated with SynthMaker, so it's not necessary to look for the cause in that direction.
Finally, the forum where you posted your problem, is meant for posting SynthMaker bugs. I think this topic should have been adressed in the Help forum (no harm intended).
Again, wishing you succes!
malc ·
Did this get resolved? Are you up and running Steve?
Disco_Steve ·
theum your a GOD!!
there was this MATCH(c)JUKEBOX that came free with my motherboard, I just un-installed it and all works fine!!
Thank you so much for the advice
also SYNTH MAKER rocks
I'll upload my auto expander when I've made a good level meter, with over shoot detection etc.
I must say I feel vary cared for by this community and developers, I just wish all software makers could be so nice and responsive!!
Thank you again
Steve
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker