Forums
New posts
Articles
Product Reviews
Policies
FAQ
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Menu
Log in
Register
Install the app
Install
Forums
Digital Lifestyle
Music, Audio, and Podcasting
Running Logic Studio, Macbook Or iMac ???
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Zoolook" data-source="post: 1015464" data-attributes="member: 21101"><p>Chud - I actually just wrote out what I thought was a very well thought out and considered reply, hit submit and got 'this page cannot be displayed'. Maybe I need an upgrade...</p><p></p><p>First of all, my post was not supposed to be antagonistic, although I can see that it will be. However it's not a personal attack on anyone, so apologies if that's how it came across.</p><p></p><p>Your example is interesting, because you imply that you're only asking very reasonable things of your set up, but still get spikes. Now I haven't used Cubase since version 4 and only briefly, but I did use 3.x (up to 3.7) for almost 4 years, but there is no reason why 4 tracks of anything should tax a modern system, even in Cubase.</p><p></p><p>First of all, I don't think 24-bit/96khz is necessary for scratchpad composing, or even putting together a track, you can use much lower fidelity. Unless you're using that exact set up live, initial composition should stick to 16-bit/48khz if you're trying to keep CPU use to a minimum. It also saves RAM and HDD bandwidth if your samples are using this quality as well.</p><p></p><p>Your two intruments are really glorified samplers, and should barely get CPU use into double figure % points, unless you're using multiple fxs per sample. During the compose stage, this should not really be necessary, although I know a lot of people who have only ever made music using DAWs do this, because they think individual sounds muct be perfecting during composition. They don't and in fact you'll run into problems later on, if your building blocks are laden with effects right from the start (phase and possibly compression issues later on).</p><p></p><p>Once you have the basic sound/melody/drum pattern on a soft synth you can work with, I'd just bounce it down to an audio track (I assume this is easy in Cubase) and work with that. If you added fx, they get bounced too, so you're literally playing back 16-bit audio in AIFF format... your CPU won't even get warm until you hit 30 or 40 tracks! Obviously as things firm up, you can go back to the original track and bounce it ata much higher sample rate (your 24-bit/96khz) and start adding EQ, compression, limiters or whatever else you need.</p><p></p><p>Yes this is more work, there is more to manage, but in my opinion you'll get better results anyway in a final mix, because you won't find yourself limited to what your CPU can do at any one time, AND you might be more careful about liberal use of samples prior to mixing.</p><p></p><p>And yes, this is only my opinion - there is no right or wrong here. <img src="/mac_images/images/smilies/Cool.png" class="smilie" loading="lazy" alt=":Cool:" title="Cool :Cool:" data-shortname=":Cool:" /></p></blockquote><p></p>
[QUOTE="Zoolook, post: 1015464, member: 21101"] Chud - I actually just wrote out what I thought was a very well thought out and considered reply, hit submit and got 'this page cannot be displayed'. Maybe I need an upgrade... First of all, my post was not supposed to be antagonistic, although I can see that it will be. However it's not a personal attack on anyone, so apologies if that's how it came across. Your example is interesting, because you imply that you're only asking very reasonable things of your set up, but still get spikes. Now I haven't used Cubase since version 4 and only briefly, but I did use 3.x (up to 3.7) for almost 4 years, but there is no reason why 4 tracks of anything should tax a modern system, even in Cubase. First of all, I don't think 24-bit/96khz is necessary for scratchpad composing, or even putting together a track, you can use much lower fidelity. Unless you're using that exact set up live, initial composition should stick to 16-bit/48khz if you're trying to keep CPU use to a minimum. It also saves RAM and HDD bandwidth if your samples are using this quality as well. Your two intruments are really glorified samplers, and should barely get CPU use into double figure % points, unless you're using multiple fxs per sample. During the compose stage, this should not really be necessary, although I know a lot of people who have only ever made music using DAWs do this, because they think individual sounds muct be perfecting during composition. They don't and in fact you'll run into problems later on, if your building blocks are laden with effects right from the start (phase and possibly compression issues later on). Once you have the basic sound/melody/drum pattern on a soft synth you can work with, I'd just bounce it down to an audio track (I assume this is easy in Cubase) and work with that. If you added fx, they get bounced too, so you're literally playing back 16-bit audio in AIFF format... your CPU won't even get warm until you hit 30 or 40 tracks! Obviously as things firm up, you can go back to the original track and bounce it ata much higher sample rate (your 24-bit/96khz) and start adding EQ, compression, limiters or whatever else you need. Yes this is more work, there is more to manage, but in my opinion you'll get better results anyway in a final mix, because you won't find yourself limited to what your CPU can do at any one time, AND you might be more careful about liberal use of samples prior to mixing. And yes, this is only my opinion - there is no right or wrong here. :Cool: [/QUOTE]
Verification
Name this item. 🍎
Post reply
Forums
Digital Lifestyle
Music, Audio, and Podcasting
Running Logic Studio, Macbook Or iMac ???
Top
