digital grunge when wav recording

[siriusbliss]

I'm suddenly getting digital clipping and noise on a simple 24-bit wav recording during mixdown.

Project is ASIO from Samplitude V10.21 mixed through a STM4896 mixer with a 24-bit wav dest module on the mix output of 4896 mixer (which is also being monitored via analog and/or SPDIF dest out to monitors).

I load a second instance of Samplitude V7, which sees the WDM and records a wav file no problem - EXCEPT that the wav has digital grunge mixed in with the audio.

I've tried various other more straight-through configurations with no change.

I swear I used to use this method before to get raw mixes basically in real time.

Note that sometimes I have a Optimaster inline with the main output from the 4896, but even taking this out makes no difference.

Note that I'm usually recording at 32/48, and have never had this problem before.

What am I doing wrong?

Thanks,

Greg

[garyb]

you could try setting the sequncers' priority to "above normal", and Scope's to "below normal". you could also just route back to another track in the first Sam instance.

[fidox]

hey,
i had something similar in one of my project,
just, i'm using cubase here,
so , while recording in realtime in cubase i had clicks and similar,
while recording into Sound Forge works fine, just i had to change priority , normaly scope to below normal and cubase to high, something like that,
maybe some vst plugins causes that, not sure,
cause on my new project where i don't have so many vst's loaded works fine, recording thru asio.

not sure if it's the same, just a though,


all the best


matej

[siriusbliss]

you could try setting the sequncers' priority to "above normal", and Scope's to "below normal". you could also just route back to another track in the first Sam instance.

I've already tried routing back to the main Samplitude project and get the same result.

'Internal' mixdown in Samp. sounds great, just that I miss the extra 'oomph' from Scope.
I have plenty of other things to try.

I already have Sam priority to high, and Scope to normal, but will try other settings.

Greg

[Music Manic]

Well if it's clipping then it must be at the master bus stage. You are protected from clipping in Samplitudes individual channels no matter how hard you drive them.

Could you be specific on the noise?
Artefacts and commonly introduced if your memory is maxed out.

[siriusbliss]

Well if it's clipping then it must be at the master bus stage. You are protected from clipping in Samplitudes individual channels no matter how hard you drive them.

Could you be specific on the noise?
Artefacts and commonly introduced if your memory is maxed out.

Well, memory is not maxed out, and I'm getting no LAB's or DSP overload in Samplitude during tracking, and internal mixdown in Samplitude sounds fine. I see no clipping in any Samplitude channel.

It almost sounds like clock noise intermixed with the audio, and both Samplitude's are set at same 48KHz clock rate, etc.

I've been busy doing more tracking lately, so I haven't had the time to try out other configurations.

Greg

[Shroomz~>]

I know this is stating the obvious, but if you think it sounds like a clock issue, then it's possibly a clock issue. The easiest way to trace a clock issue as with so many others is by means of elimination. So, I'd probably start by disconnecting the spdif, then try again. If it's still the same, disconnect another digital connection & try again etc etc.

What's your exact digital setup of I/O connections to and from external devices incl. master/slave settings?

~Mark

[siriusbliss]

Below is a big-ol screenshot of my main project setup.

Noise remains with SPDIF disconnected. Already tried that. I also get the same result with Optimaster taken out of the main output.
During tracking Scope is slaved to Yamaha 01V96V2 mixer, and during mix Scope is master (tried it either way with same result).

Most monitoring is doing via analog.

2nd instance of Samplitude (mixdown) sees wav dest module as singular wdm input while main Samplitude project is ASIO. (This may be part of the problem, but it shouldn't be).

I've tried capturing at 24-bit instead of 32float, tried direct path out to Samplitude as well with same result.

Next step will be to just route back into main Samplitude project and mix to another track. I'm really only testing out using Optimaster in-line on the main output at this time.

Any further enlightenment is appreciated, as I'm probably forgetting something with the Yamaha, or just simply dealing with something leaking into the mix post-Samplitude.

Thanks again,

Greg

p.s. I may post an .mp3 if/when I get a chance.