CJ Jacobson

19 hours ago, David A. White said:

TASCAM US16x08 audio interface because not only does Cakewalk not work with it, but neither does Sound Forge or Band-In-A-Box. They all fail if you use the ASIO driver. They all work with MME or WDM, but who wants to use those?

WDM driver is just fine.

With some sound cards, like the TASCAM,  the ASIO driver mode is a POS.  If WDM gives you better performance, that use it. 

IIRC, TASCAM never had good ASIO drivers for windows

3 hours ago, greg54 said:

 But I don't want to do a clean install every time I need to delete the picture cache.   Or maybe it's something else.  

When I record vocals or guitar, the audio sounds  harsh, and there is a lot of mids, making it sound dark.  

I can assure you, its not your pic cache and it has nothing to do with a clean install either.  A pic cache will not make your sounds sound harsh, and give it extra mid frequency levels. Maybe you have an EQ enabled in the cuemix or maybe you are using a mic like the SM57 that gives you extra mid range. Or maybe sample rate mismatch, but that would make it slower or faster. you did not say that was the case... But its definitely not your pic cache and a clean install.

CJ

1 hour ago, maxsthaven said:

 I do know what you are saying, though, but one will find that doing this creates a worthwhile input difference in a guitar emulation plug-in.  If you’re up to it, give it a try.

You are not understanding the concept of mono and stereo instruments and tracks.

Guitar is mono, so there is no need to change the interleave to mono. Its already set to mono. Guitar is a mono instrument. Even  when you record with 2 mics onto 2 different tracks, you still have 2 mono tracks. 

You do not record a mono signal onto a stereo track and then change the interleave to mono, as you stated above. That's backwards. You record a mono track onto a mono track, like guitar, and the interleave is already set to mono. Hence, no need to change the interleave, even when sending the guitar to a bus with stereo effects. You got it now?

7 hours ago, maxsthaven said:

Signal Flow Quick Tip 1:  set the Interleave to mono when sending a clean guitar recording on to Amplitube or some other guitar emulation; unless, of course, you want it to enter the plug-in in stereo.  It’s easy to forget this.

The guitar is a mono instrument, so the track would be mono already and with the track being mono, the interleave would be mono automatically. You would not have a mono tack on a stereo track. It would enter any plugin mono, even if the effect outputs stereo.

Even if you use 2 mics to record a guitar, each mic would be recorded onto its own mono track.

Quote

3) The sound card (Realtek) is just a chip on the motherboard (i.e. a toy)

If you care about latency, then do not use the on-board sound chip. Get a dedicated audio interface with drivers written for audio production

Yea project template should work for you

21 minutes ago, Mik Urrey said:

P.S. I recreate the project with same samples and FXs, it was rendered very well. But when I add one more sample, I got invalid output vawe.

When I rendered another project with VSTi's and no samples, I got fine quality every time. So I assume now that some of my manipulations with the samples cause these errors.

Try bouncing down or freezing your MIDI to audio before exporting it out of your DAW.  It cannot handle the 64bit processing engine.

FYI: All these problems will go away with a audio interface.

Try making a template with those specific configurations selected...

4 hours ago, Mik Urrey said:

Whichever file format or samplerate or bitrate I choose at the output I hear clicks and pops in the file what I don't hear while I play the track in DAW.

How is your gain stage?

• Do your tracks go to the master bus
• Sends go to buses
• Buses go to the master bus
• Is the master bus the only bus  to go to the main outs?

What are the RMS, LUFS, and peak dB levels on your master bus and main outs read?

Are you 100% positive that your export setting are set up correctly? How are you setting them up?

Quote

Also source samples has this pops and clicks (visible to the naked eye DC offsets) and I can't remove them as DC offsets, using fade tool only.

How to deal with it?

There is a setting in the preference menu to fix DC off set upon audio files, so make sure that is selected

4 hours ago, Mik Urrey said:

Windows 7 x64, built-in audio interface.

You need a dedicated audio interface. The built in sound cards are not able to deal with the demands of producing audio and running a DAW proficiently. This built in card can give you artifacts, as its drivers are lacking and its converters for A/D and D/A are lacking and its internal hardware is lacking. 

2 hours ago, Rick said:

Then something in Windows popped up (running windows 10) saying something about the hard drive.

How much room is left on your hard drive and do you have a dedicated hard drive for only your audio files? That is something you should do, if you do not.

As far as your dropouts, that's just a buffer setting that may be too low for the current work load of your DAW & PC and/or the dropout configuration in your aud.ini file is set to low. I would first raise your buffers, before messing with the dropout setting.

To solve it, just raise your ASIO drivers for your audio interface or slide the WDM slider to the right, if you are using WDM driver mode.

Also make sure you have the latest drivers for your audio interface.. That's it!!

5 hours ago, Royarn said:

What do you think midi buffers should be set at as I have some midi tracks on this so at present.

Since its audio and you are not having any MIDI issues, keep them ware they are set at. The right settings are the Settings that work for you and they are working for you,  yes? 

Are you looping it during playback and is it audio or MIDI you recorded? 

Do you have any Plugin effects on this track? 

This is prob not it, but if its MIDI make sure your tempo map doesn't have any tempo changes and make sure your MIDI buffers are set for optimal response.  You can also try playing with your audio interface ASIO buffers as well

CJ

11 hours ago, jono grant said:

Hi there...

Every time I export some audio out of CBL, the "bounce settings" are set to "mix recall", I keep selecting "Entire Mix" which is what I want, but it always returns to "Mix Recall" and (mix 1 and mix 2 are selected) I'm not even using mix recall.

 

Anybody know why?

Cheers

Jono

I do what BR suggested, but if you want it to default to 'Entire Mix' you should make a project template with it saved like that and it should always be the default.

Pre fader is pre effect and post fader is post effect. Same for send, pre and post sends.

14 minutes ago, micv said:

The issue is often time I don't notice that a section is selected.  To use this new feature I now have do to a 'un-select all' first.  To me there's nothing to be gained here if that's the design.  Am I missing something?  thx

Just click your mouse anywhere on the track view and this will de-select and selections you have made before you export

10 hours ago, micv said:

unchecked the "re-scan existing plug-ins" but it still does a full re-scan. Is there a way to scan just the new plug-in?

You can define the folders it sans in the preference menu.

Just insert he folder location you added the plugin to and delete the rest and it ill only scan hat folder location.

4 minutes ago, MuFever said:

t I mix in -3dB but my audio interface (and propably all the mono devices out there) is 0dB?

No, i'm not saying that. You are confusing pan laws and actual dB levels

Quote

6 minutes ago, MuFever said:

So is there a solution that I mix in -3dB and Master at 0Db so it is calibrated with various audio mono devices out there?

No, no need. You are confusing pan laws and dB levels. They are 2 different things..

1 minute ago, MuFever said:

Yes I did not write it correctly. I am used to -3dB pan leveling that when I turn to 0dB it is like I need to do extra work with track faders.  

I understood you and my response/answer  is still the same:

You mixed the project with the -3 pan laws, so changing the Pan law in a project to something else will change all its levels and make it sound different your ears.. You would need to mix it all over when changing the pan laws.

Quote

In my ear the -3dB compensation is "sweeter" 

The pan laws do no changes the sound, it just changes the sound levels and how it behaves when its panned.  In simple terms..

This is what is happening to your ears.. You mixed the project with the -3 pan laws, so changing the Pan law in a project to something else will change all its levels and make it sound different your ears.. You would need to mix it all over when changing the pan laws.

Quote

So when I export a mastered track from Cakewalk (I use -3dB pan law) and see that my track is clipping when monoing my interface but it is not clipping when monoing in cakewalk then what decision should I take? Leave it trusting DAW or begin the mastering again? 

Never leave or trust anything.. If your target is mono and stereo, then you need to make decisions in your mixing and mastering stages for this. Not after its been exported.

If you change your pan laws, everything will change in ALL your projects signal chain. Its a global setting, so all projects will be effected, unless you change it back and forth, but is that feasible?

My pan laws are set at 0 center cor something... I prefer it that way and i like the way it behaves, but this is a personnel preference

On 2/21/2019 at 12:59 AM, Erik Putrycz said:

I have an insane latency in certain projects... Almost 3-5 seconds from a midi note to a VSTi sound... Have not been able to figure out the cause but haven't seen anything similar in other daws with similar setups. Any chances this could get looked at someday?

Things to do:

1.) Lower your ASIO buffer to 64 or WDM slider all the way down to its lowest latency setting in the preference menu.

2.) Make sure your dedicated audio interface has the most updated drivers for your windows operating system. If you are using the on-board sound chip, back off as it might blow!!!     ---   -----  --- Just kidding, or am i?????  ...                   But those sound chips are not meant for these things.

3.) Make sure you are not inserting and using plugin effects that are not meant for live monitoring and have hidden buffers, so they can process the signal better. These types of plugin effects are meant to be used in the mixing and mastering stage.

4.) Your PC just doesn't cut it (MOBO or processor power lacks)

5 hours ago, MuFever said:

monoing my audio interface then I see that the audio is louder and sometimes clipping. Why is this happening?

When you combine 2 channels into one channel, the volume will raise, because you are making 2 channels into one channel

5 hours ago, MuFever said:

When I "monoing" into Cakewalk I could hear a small attenuation of the overall signal comparing to the stereo.

Its because of your pan law setting . If you set to to  0 dB center, sin-cos taper - constant power, IIRC, it may behave like it does when you export it. Its one of those pan laws that behaves like that ans i think it is that one

Quote

I have also noticed that when i use the built in mono-interleave button in a track it is ok but when I monoing the Master Bus and my individual tracks remain in stereo then the meters of the individual tracks exceed the 0 dBfs reference point but I can't hear any noticeable clipping distortion.

If you are in 32bit floating for your project, it doesn't really matter, as long as your master bus and main outs are not clipping. But that doesn't mean you can slam the tracks and peak them to holy hell. Use common sense..

Yes, more ram, having a dedicated audio hard drive and i noticed you didn't mention a dedicated audio interface so i would add that as  one of your things to get.

Is it for every project or just one specific project? Maybe its having a hard time with a cache. 

Make sure you install the latest version of the eLicenser Control Center installed.  To add,the latest version of HALION  should be installed. 
http://www.steinberg.net/en/support/dow ... ion_5.html