I have had some real problems getting started with the above... I have not been able to hear a single sound from the Spectrasonics Atmosphere Dreamsynth Module vsti even though I've tried many ways for almost 1 month. Creamware support can't help because they have no copy of Samp... Samp support is trying to help.... perhaps one of you might know what I need to do to get this to work.... I have the midi source & dest connected to the sequencer source and dest.... but it is not recognized by samp. as a midi record or playback device. Anyone know how to make connections in Pulsar so that Samp. will recognize the midi modules?
Thanks,
Mike
Pulsar II, Samplitude Pro 7.1, & Spectrasonics Atmosphere
I don't have the Spectrasonics Atmosphere Dreamsynth, but I know Samp 7.1 has troubles with some VSTi's. Matter of fact, midi is generally wonky in Samplitude. Some VSTi's work ok (Like NI B4), some not at all (like z3ta). Same thing with SFP devices - sometimes they receive midi data thru Samp, sometimes not. My guess is it relates to a problem with the midi thru function.
I'm sure Magix is aware of this and are working on a fix.
I think the midi implementation in Sam7 is a bit too young to be reliable. I do my midi tracking in SX and leave the audio mixing/mastering for Samplitude.
/dave
I'm sure Magix is aware of this and are working on a fix.
I think the midi implementation in Sam7 is a bit too young to be reliable. I do my midi tracking in SX and leave the audio mixing/mastering for Samplitude.
/dave
-
- Posts: 2310
- Joined: Sun Mar 25, 2001 4:00 pm
- Location: Canada/France
-
- Posts: 2310
- Joined: Sun Mar 25, 2001 4:00 pm
- Location: Canada/France
Forget midiyoke, it induce latency, is not as full featured as midi-ox, is redundant (midi-ox conver it all) and also can create bad midiloop a bit too easily.
The sfp problem is possible, but i doubt it, if everything else work except Atmosphere, it's probably more a problem with the vsti host imho...
I read somewhere that Samplitude had problem with a couple of vsti like this, their vsti implementation is still not perfect it seems.
Anyway, i got atmosphere, and it work perfectly in fruityloops and Logic, so i'm sure the problem is not atmosphere itself at least...
The sfp problem is possible, but i doubt it, if everything else work except Atmosphere, it's probably more a problem with the vsti host imho...
I read somewhere that Samplitude had problem with a couple of vsti like this, their vsti implementation is still not perfect it seems.
Anyway, i got atmosphere, and it work perfectly in fruityloops and Logic, so i'm sure the problem is not atmosphere itself at least...

I think Tom from XVision Audio found the solution.... I'm going to give it a try today... apparantly, others have had the same problem with other soft/hardware and it had nothing to do with that... it was in Windows.... check this out:
http://www.rme-audio.de/english/faq/10entrye.htm
I think it has to do with this win. limitation and is supposedly easily fixed with cleaning up the "drivers32" folder in the registry...
Thanks!
Mike
http://www.rme-audio.de/english/faq/10entrye.htm
I think it has to do with this win. limitation and is supposedly easily fixed with cleaning up the "drivers32" folder in the registry...
Thanks!
Mike
After thinking I had the problem all solved (well, it was partially, anyway) I had all kinds of trouble with boot failures, etc... so I'm back to repartitioning the Hdd and reinstalling XP.
The article from rme-audio is useful info. But now it's clean install time around here with the hopes of the crashless system I have read about that many of you have.
The article from rme-audio is useful info. But now it's clean install time around here with the hopes of the crashless system I have read about that many of you have.