Using diff sample rates in same project... not a good idea?
-
- Posts: 6659
- Joined: Sun Nov 19, 2006 1:56 am
- Location: greater toronto area
Re: Using diff sample rates in same project... not a good idea?
seems like fair advice ...
http://soundcloud.com/umbriel-rising http://www.myspace.com/leedsquietmandemos Live 7.0.18 SUITE, Cubase 5.5.2], Soundforge 9, Dell XPS M1530, 2.2 Ghz C2D, 4GB, Vista Ult SP2, legit plugins a plenty, Alesis IO14.
Re: Using diff sample rates in same project... not a good idea?
^^^
yeah, i can't see that i said anything different... really... just expressed my opinion... and i was not really talking about the sound at all!
more about the possibility (which i said that i did not tried it myself out) that it lays more strain on the CPU.
anyone? more CPU usage or not? i would have to make some extra different sample rate recordings, only work since years in the same...
seriously, anyone?
yeah, i can't see that i said anything different... really... just expressed my opinion... and i was not really talking about the sound at all!
more about the possibility (which i said that i did not tried it myself out) that it lays more strain on the CPU.
anyone? more CPU usage or not? i would have to make some extra different sample rate recordings, only work since years in the same...
seriously, anyone?
*** GAFM ***
-
- Posts: 1193
- Joined: Fri Jun 04, 2004 10:38 am
- Location: Berlin
Re: Using diff sample rates in same project... not a good idea?
i guess my main point with all those discussions is that quite binary notion of good distortion versus bad distortion. SRC is bad distortion. Tube amp is good distortion. My snare is broken. It rattles.
Rob
Rob
Re: Using diff sample rates in same project... not a good idea?
^^^ that is why i hate yamaha... even it is everything but poorly designed, but it rattles wrong
still anyone, more CPU strain or not? that was more or less my main guess what would happen (more strain on the CPU) and why i said not a good idea as long as you can avoid it.
still anyone, more CPU strain or not? that was more or less my main guess what would happen (more strain on the CPU) and why i said not a good idea as long as you can avoid it.
*** GAFM ***
Re: Using diff sample rates in same project... not a good idea?
PM sent to Funk, it's all good.
In my life
Why do I smile
At people who I'd much rather kick in the eye?
-Moz
Why do I smile
At people who I'd much rather kick in the eye?
-Moz
-
- Posts: 1193
- Joined: Fri Jun 04, 2004 10:38 am
- Location: Berlin
Re: Using diff sample rates in same project... not a good idea?
@ SubFunk:
The SRC is always running. Without SRC you cannot even pitch a sample with warp off! Or it will sound like in Sampler with interpolation set to "none" - try it and you will understand that the SRC is quite essential
The SRC only is "transparent" when it does not need to work. But I am not sure if this saves significant CPU cycles. The thing is, just having an audio track there with volume, pan, routing, sends, latency compensation etc... etc.. costs CPU. The SRC does not really add a huge portion to it.
What adds CPU load is the more advances FFT based timestrech algorithms like "complex" and "complex pro". Here it becomes obvious that one would want to avoid them if not needed.
Robert
The SRC is always running. Without SRC you cannot even pitch a sample with warp off! Or it will sound like in Sampler with interpolation set to "none" - try it and you will understand that the SRC is quite essential
The SRC only is "transparent" when it does not need to work. But I am not sure if this saves significant CPU cycles. The thing is, just having an audio track there with volume, pan, routing, sends, latency compensation etc... etc.. costs CPU. The SRC does not really add a huge portion to it.
What adds CPU load is the more advances FFT based timestrech algorithms like "complex" and "complex pro". Here it becomes obvious that one would want to avoid them if not needed.
Robert
Re: Using diff sample rates in same project... not a good idea?
^^^ cool, so it was not that difficult to clear that up. was it.
*** GAFM ***