Jump to content

JonnyStrinati

Member
  • Posts

    29
  • Joined

  • Last visited

JonnyStrinati's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Week One Done
  • One Month Later Rare

Recent Badges

0

Reputation

  1. I upgraded whenever Logic Pro 10.8 first came out, which was a couple of months ago. It's Mac OS Extended. I could try formatting the drive, but it's 2TB and at capacity, so I don't have anywhere to back up the data in the meantime.
  2. Since upgrading both Logic Pro to 10.8 and the Mac OS to 14 (Sonoma), the browser on Logic Pro doesn't recognise the contents of one of my external hard drives. It recognises the HD, but when I open the drive there's nothing there ... my other external drive works fine ... any help much appreciated!
  3. Whilst this advice/workflow is appreciated. You could have simply said in your first comment, what actually took you numerous replies before you mentioned it: (with any form of exporting tracks) ... 'You will not get any processing downstream (Sends to other FX, Bus processing, Master processing).' This answered my question and confirmed what I already suspected. So many thanks. Likewise, gonna get back to work now Have a splendid afternoon.
  4. Maybe with your work stems means without processing, but that's definitely not the case for everyone working with stems. Remix stems, for example, labels will always request for both 'Wet' (with processing) and 'Dry' (without) stems. And indeed this can often be the case for sample library work too, presenting 'music/inspiration' stems in both Wet and Dry formats. But that's besides the point. I'm not sure how you got so confused, if you read the beginning of this thread it's obvious what we're all talking about. "I'm trying to export/bounce individual tracks with all plug-ins and bus sends on them." .... "Sounds like you want to be printing stems." ... "The process of 'printing stems' is so easy in other DAWS, not sure why Logic doesn't have a better way. " ...
  5. 'exporting single (individual) elements with all their processing' or 'printing stems' (as it was referred to at the start of this thread) was always the only question here.
  6. which is your convoluted way of admitting that there is in fact no easy way
  7. 'Export All Tracks As Audio Files' will not necessarily print your mix as it is. This is all dependent on how your have your project set up. To give some context, I was asked to export the tracks from an old project. I went back and (optimistically) did an 'Export All Tracks As Audio Files' hoping it would yield useable stems, but when I checked them over the levels were all over the place. Which lead me to do some digging to see if there was a better workflow ... Is there any different between 'Export All Tracks As Audio Files' and highlighting all your tracks and choosing 'Export 12 (or whatever) Tracks As Audio Files'???
  8. If clicking on the stems and hitting Export isn't straightforward enough, then I don't know what is. Wait, so simply highlighting all your MIDI/audio regions in your tracks area and right clicking and selecting Export>Export As Audio Files will print stems? ...
  9. NEVER send off stems before checking them first!!! Though personally I would always do this with a new project and import the audio files I'm about to send off. My projects tend to have a combination of Summing Stacks and Audio/Audio Instruments ... so yeah I guess you could sum everything and follow the method you describe. But my point being, that there really should be a more straightforward way. In other DAWS it's literally two clicks and then you go make yourself a brew and come back to printed stems.
  10. Is this really the best way? Still seems convoluted. I've always put each track in solo and then exported one by one ... I never really need to do a full track, but exporting remix stems/etc, you're exporting shorter loops so this method isn't so bad. The process of 'printing stems' is so easy in other DAWS, not sure why Logic doesn't have a better way. Unless it does and I don't know about it!
  11. So working with some sounds yesterday I noticed this problem is persisting. But thankfully this is the fix, turning off Auto Levelling prevents this from happening. Presumably as we were saying, audio gets imported as an Apple Loop or maybe Logic applies Apple Loop behaviour therefore it will auto level the Region gain. This was happening with some audio loops and not others, so no idea what was causing the problem. A lot of my sample loops caused this issue, but I was simply exporting from Logic 2/4 bar loops at 24bit/44.1khz, which is fairly standard. Unfortunately the issues with auto flex persist without any fix. The most frustrating thing with this is often Logic incorrectly analyses the tempo of imported regions. For example, my project tempo is 125bpm and the audio/region I drag into the tracks area is the same tempo, and then you have to manually turn off Flex and Follow or manually adjust the region.
  12. Thanks for your reply on this! Whilst the auto levelling feature changes this behaviour when importing apple loops, or indeed loops from an 'untagged loops' folder where the audio is treated as an apple loop. This problem was occurring when I was dragging and dropping loops into the tracks area from a Finder window. I think there was an issue between Logic automatically reading the files as Apple Loops and then automatically Flexing and levelling the audio. I've not been able to find a pattern as to why this happens. Some audio is left unaffected and some gets auto flexed and levelled. Though I have noticed this hasn't happened since I updated to 10.6.2, so hopefully it was just a bug that has now been fixed!!
  13. Flex isn't turned on on the track header, but is in the region inspector (flex and follow box gets checked automatically), along with auto gain adjustment.
×
×
  • Create New...