martin7

Ha! Great advice. Already made that blunder

Thanks David - that was indeed my experience after posting. Really depends on what stage you're at vis the film, as the xml allows further individual clip mixing in back Final Cut's limited audio environment. As I've just been looking at different sound ideas - Ive bounced the project as a whole and imported as a new file in FCP.

After importing an xml file from Final Cut then applying effects etc including on the stereo buss, I re import back into Final Cut. Should I expect to hear any processing applied on the 2 buss in logic. It doesn’t sound like it’s happened. thanks m7

Indeed. I try to use that mnemonic problem to make it so ridiculous it becomes easy to remember for cool but not often used commands. For example - V (show/hides plugs) I use a lot, so Ive assigned all the modifier keys + V (⌃⌥⌘V) to Remove all Bypassed Plugins. A profligate use of modifier keys but it means my old sticky brain has an easier/quicker journey to make to a great command I don't use a lot .

There are so many sneaky cool ones that get half forgotten because I don’t use them in my workflow enough. But, for me, I would recommend starting with - C (cycle range on/off) A (automation view) R (record) and ctl M (mute - which I’ve changed to just M). CMD , gets you into your global preferences to fiddle around with your audio buffering etc. CMD b to bounce and CMD q to turn off Logic and go to sleep.

It’s so ridiculous and frustrating. It makes no sense. Other daws have it. Logic had it! Because there are clearly occasions where you need it. Some projects take a wrong turn and you/client realize it a day later a week later or even a month later. It used to be you could go back and oh so easily change it. I can only imagine that from the devs point of view fixing it would be too costly and/or time consuming to make it work with some other feature (third party plug in parameter history?). Gear grindingly annoying.

Yes. In this case one wonders whether it has something to do with Logic’s less than great(and recently added?) ability to follow third party plug in parameter history

Perhaps then it’s a case of ‘robbing Peter to pay Paul’. Whatever the reason it’s a poor one as it undermines one the basic advantages of using a daw over tape - the ability to easily go back.

The frustrating thing is that until recently logic did retain history beyond a session so it’s not like it’s a design issue.

Thanks - that’s what it sounds like. I just didn’t want to double up on the buss/2 buss processing.

I don’t. I need to create a new bounce to send a bounce without the ‘temp’ limiter I currently have bounced with. I am up in Norway with only a laptop headphones and these export files. i just need to know if exporting each track includes any send return from auxes and What was on the two bus. It’s not clear in the manual

I don’t. I need to create a new bounce to send a bounce without the ‘temp’ limiter I currently have bounced with. I am up in Norway with only a laptop headphones and these export files. i just need to know if exporting each track includes any send return from auxes and What was on the two bus. It’s not clear in the manual

Sorry to bump but

pretty sure I used 'all tracks as audio files". what is confusing (a 1000 miles away from my studio computer!) is I can hear 'wetness' on the relavent tracks but some of them also had sends to busses with further ambience, which didn't get bounced as separate files, so its hard to be sure if the individual tracks are properly affected...

Hi Ive exported all tracks of a project and now, on vacation, have to reconstruct the project to send for mastering. My question/concern is - during the export would all the send effects been 'burnt into the individual track bounces I did? Would the plugins on the 1-2 bus have been bounced into the individual export bounces? many thanks M7