Direct Monitoring with Samplitude 9

musikrolf · Post by **musikrolf** » Sat Aug 18, 2007 8:43 am

Hi everybody,
since Samp9 I have a problem with the direct (hardware) monitoring option in Samplitude. In short, it does'nt work anymore. I contat the support of magix, without result. Are here others who use Samp9 and have a solution for my problem.

I connect Samp to Scope big mixer. All other monitoring options in SAmp are working exept hardware monitoring. javascript:emoticon(':-?')
javascript:emoticon(':-?')
Any help?

thanks
Rolf

Scope prof + pulsar II

siriusbliss · Post by **siriusbliss** » Sat Aug 18, 2007 5:43 pm

Which ASIO module are you using?

Try different ASIO modules to see if it makes any difference.

Things DID change since the hybrid engine came along, but it is working for me.

Try this and let us know what happens.

Greg

p.s. a long time ago Samplitude tech. support told me that they 'don't support Creamware Scope. (whatever that means)

musikrolf · Post by **musikrolf** » Sun Aug 19, 2007 1:16 am

Hi Greg,
thank you forr reply, but I've tried all different ASIO Modules, I've tried also WAVE Modules, even with them, no hardware monitoring is possible.

Rolf

siriusbliss · Post by **siriusbliss** » Sun Aug 19, 2007 7:01 am

OK, I'll do some trials today and see what I can figure out.

Why do you want to use hardware monitoring?

Greg

musikrolf · Post by **musikrolf** » Sun Aug 19, 2007 8:22 am

Cause I do a lot of recording with natural instruments and voices, so a delay from the source in the monitor path in unacceptabel. To make workflow more smooth I avoid the set up of a different mixer in Scope only for that monitor reason. I connect the Scope ADAT source direct to Samplitude and the returns into the big mixer. There I can add a compressor or so without latency.

Rolf

alfonso · Post by **alfonso** » Sun Aug 19, 2007 8:52 am

I don't have Samplitude, but can't you just disable Samplitude monitoring and only monitor the Scope Mixer with the card inputs connected there? You won't have any latency this way....maybe I miss something?

siriusbliss · Post by **siriusbliss** » Sun Aug 19, 2007 9:57 am

musikrolf wrote:Cause I do a lot of recording with natural instruments and voices, so a delay from the source in the monitor path in unacceptabel. To make workflow more smooth I avoid the set up of a different mixer in Scope only for that monitor reason. I connect the Scope ADAT source direct to Samplitude and the returns into the big mixer. There I can add a compressor or so without latency.

Rolf

I use the analog Dest module to montitor through an external mixer either from the mix output, or from the ctl output of the big mixer. I also then send the channels I'm recording to Samplitude via the ASIO Dest. This way I'm not monitoring through Sampliitude.

With Scope it's really not necessaryy to monitor through Samplitude.. You shouldn't have to send returns back to the big mixer.

I DO have separate recording environment projects that are setup differently from a mixdown project.

If you're trying to insert an external compressor via the new hardware monitoring in Samplitude 9, then I can't help you (yet), because I haven't needed to use that because Scope provides so much routing flexibility.

Can you elaborate on how your project environment is setup?
Maybe a screenshot?

Thanks,

Greg

musikrolf · Post by **musikrolf** » Mon Aug 20, 2007 9:02 am

So here are screenshots from the scenary. While recording, Samp is the master for all overdubbing and punch ins. While mix down it is Scope. So I can start mixing while other instruments will be inserted later.

alfonso · Post by **alfonso** » Mon Aug 20, 2007 12:07 pm

Only thing you need to bypass Sam monitoring is to send the ADAT sources to mixer channels as well. You can double the out cables and have each ADAT source connected separately to the Mixer and the Asio, so, for example you can send an unprocessed signal for recording but you can hear it at a different level or processed to help the performance. Seeing your setup you would need the 4896 Mixer, but you can also add a small mixer to the project just for the ADAT sources and route it to one stereo channel of the 2448.

P.S. Why that Control room? The mixer already has one, it seems a waste of dsp power...

siriusbliss · Post by **siriusbliss** » Mon Aug 20, 2007 8:32 pm

I agree with alfonso that you could probably just use the 4896 mixer and a smaller mixer (instead of the control room) for mixing in the ASIO.at will.

This way it's all transparent to Samplitude and reduced CPU load.

I route incoming/recording channel ASIO through a small mixer and use the 4896 for mixdown.

I also use the analog out for listening during recording, and digital out for mixdown.

This means you wouldn't have to even concern yourself with hardware montitoring through Samplitude.

Hope this helps.

Greg

musikrolf · Post by **musikrolf** » Tue Aug 21, 2007 7:43 am

Thank you for reply. The reason I want the Samplitude Monitoring is to avoid a second mixer in Scope. Cause in that reason I will have Samp playing till the punch in point and also the original singer while rehearsing. That doubles the singer till punch in and might be annoying. I want to handle Samp like a tape maschine in the old days. Also I like to add a VINCO on the vocal chanel for playback reason. To do so I must copy the effects on the monitor mixer to keep sound compatible.

@Greg I need the control room module later, cause after mixing I record two track back to Samp and add some master effects there. The output of those Samp tracks will later be added to the control room. Than I can listen for and back to mastering and mixing. Even in that stage I can overdub or add tracks so I have an integrated platform for recording mixing mastering within the same project.

Rolf

Post by **garyb** » Tue Aug 21, 2007 11:50 am

you don't need the control room module for that.

you want to make scope the central monitoring point(sequencer, scope synths, altered tracks and live inputs), then there will be NO latency and seamless monitoring of overdubs and punch ins/outs.

personally, while tracking, i just use a stereo pair out of the sequencer. it's quick and easy and painless, since all sequencers use the first stereo bus by default. if i need to send a track out a seperate output to run through a scope or external effect and then back into the sequncer, i can still do that using the record bus or direct out of the track on the stm mixer or by returning directly to an asio dest channel.

when i'm done tracking, i move to mixing(it's bullshit to try to mix while you track. how can one mix when all the elements are not there yet?) and then i use individual outputs for each track or effects bus, and do the final mix/polish in scope. this method is fast and efficient.

musikrolf · Post by **musikrolf** » Fri Aug 31, 2007 9:44 am

Hi,
I was on vacation, so it took some time to answer. Still my problem is harwdare monitoring in Samplitude. Thanks for the work arrounds, but I want it this way.
Another guy with the same confiiguration told me, that he has no problems with this kind of monitoring, so could it be a secret entry in the registry or something like that. To show you my problem here are two pictures first the option with Track FX Monitoring, than with Hardware Monitoring. You see in the Scope track 1 a signal than non.

siriusbliss · Post by **siriusbliss** » Sun Sep 02, 2007 5:06 pm

and you are using hybrid mode?

I'm not sure what else to try.

Greg