Bristol_Jonesey

Set workspaces to none. Pretty sure Control Bar placement is independent of screensets

If you engage offset mode at some point in the future, all non-adjusted faders will jump to 0dB whilst the ones you have adjusted will show it's new value View it in Console View to see what's going on

This sort of thing can easily be done using offset mode. Switch on Offset Mode Raise TRACK FADER by 0.5dB Switch off offset Mode

Craig, when you did it by Copy + Paste ,you didn't select a track before pasting When you used cut, you selected track 8 - why? What happens when you don't select a track?

Work perfectly here I downloaded your track, inserted TTS-1 and it picked up all of your tracks

You would OPEN a Project template but you would IMPORT a Track Template Only you would know what you've done ?

1 is the default screenset. If you do change it, just hit 1 again and it will revert

Turn Snap off altogether ('n' key to toggle)

In addition to the screenset advice, make sure your Workspace is set to "None"

This bit is totally wrong I've never need Write on in order for Read to work. Let me say this politely - you're doing something wrong

Why bother with the Assistant?

Sony CD Architect. It's not free and is not easy to find but it's the dogs doodahs

Just turn them off, here

If you're recording an mice'd up amplifier, you must plug the mic into a mic input - not line, not inst. And if it's a phantom powered mic, switch the power to it on AFTER you've plugged the mic in

Not really, but then again you don't need to, provided you've chosen the relevant options when inserting TTS-1 or any other soft synth Inserting the synth like this will expose all the audio tracks (24 - 31) for you and you can insert Fx directly into the track FX bin or use the Pro Channel The one thing you cannot do is apply clip Fx, not until you freeze the synth

All you need to do is slip edit your midi clip for as long as the tail lasts.

If you're using soft synths, try freezing them rather than bouncing to audio

I run EWQLSO and my typical template is 135 tracks It's never used more than 9Gb of RAM in my 32Gb system The biggest improvement in speed was moving all the sample libraries over to a 1Tb SSD Load time dropped from about 9 minutes to 90 seconds

Those aren't files, they're folders I used to have a Saffire 6 and had no problem with the ASIO driver which is always infinitely preferable to MME. Why didn't it work?

If you can wrap your head around the concept, using Drum Maps for mapping articulations in CbB is a very elegant solution For each instrument track, say 16v, you need 3 tracks - a pair of traditional audio + midi tracks plus an additional midi track set to the drum map This way, in the prv, you can view all available artics in the drum map and immediately below it, the other midi track for your note data

What made the difference for me was learning how to use drum maps as a means for entering articulations in a separate area of the screen but totally in sync with the note data, viewed underneath the drum map I work exclusively in the prv for all orchestral work

Nope, works as expected here I've been using the Velocity plugin for years without issue

Issue 1 - Apply Trimming after quantize Issue 2 - Turn the clip into a groove clip, then just drag it out as far as you want

So how you do you eliminate the unavoidable latency introduced by look ahead plugins?

Can you actually see the Fx bin? A screenshot would be useful