Jump to content

HasseFX

Member
  • Posts

    6
  • Joined

  • Last visited

HasseFX's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Thank's for the reply! Maybe so, but they stress on that info everywhere! However I'll try to confront the designers about it!
  2. Hello, I use Logic X on a Mac Mini 2018 with a RME UCX interface, working flawlessly! Furthermore, all of my Logic projects are at 44.1 kHz. The other day I added a NDSP Quad Cortex (QC) that can operate as an 8-channel USB interface. My first thought was to run the UX and QC as an aggregate device (monitors etc connected to the UCX and guitar, bass etc to the QC). However, the USB interface option on the QC can only run at 48 kHz and as all my old and current projects are at 44 kHz I planned to run the QC via analog I/O - not very desirable but what to do... OK, to the point: I still created an aggregate device - maybe I'll switch to 48 kHz for new stuff. To my pleasant surprise the aggregate works flawlessly at 44.1 KHz, using the UCX as clock master master Not a trace of any glitches or artefacts in the audio!! I've been on the digital audio train since the early 90s (AudioMedia II etc) and knows how sample rate mismatch wreaks havoc with audio, but obviously not in this case. I've tried to google this but find no conclusive answer - does the audio aggregation function in Mac sample rate convert the 48kHz from the QC to match the 44.1 kHz of the UCX, set by the Logic project?? What is going on here?? In the audio device settings i can see that the QC does not secretly handle 44.1 kHz - only 48kHz is available with the QC as clock source while the UCX can be set to several different (44.1 up to 192kHz). Any clarification would be much appreciated! Cheers, HasseFX
  3. Yes, that is exactly function I was looking for, intended just for this kind of situation! Thanks! An alternative I discovered meanwhile is to do a Bounce-in-Place of the imported regions before applying Flex, which creates a new audio file with the project tempo written. Useful maybe in the case when you chop up an audio file in several regions, some that you do want to adapt to the project tempo, while others should not.
  4. Maybe something basic I've missed but... Background: I created a song, containing a hundred or so tempo changes (tempo from live drummer), from which I made WAV stems and sent to the singer. He returned his vocals as WAV-files which I imported with no issues. Problem: I need to do some temporal adjustments on the imported vocal tracks! But those WAV files are recorded using the stem files as reference, at some fixed tempo. They play back fine, but as as soon as I enable Flex Time, Logic X "adjusts" the timing according to the project tempo changes and the timing gets completely off. FIxes: IDK... I can turn off the Flex & Follow for a region, but then Flex Time is also disabled. I can manually circumvent by chopping up the vocal tracks into parts and manually reset the timing affected by the tempo changes, feasible but tedious. Question: Is there a way to be able to Flex Edit a track, without the automatic tempo adaption happening? Or a smoother way to get around the problem? Thanks /HasseFX
  5. It seems like the "fix" with reinstalling the Presonus FaderPort Classic control driver each time Logic has updated finally is broken, as the unit is not reckognized! I removed the FaderPort as control surface in Logic, added a HUI and reassigned the input/output to the FaderPort and the unit again is operational.
×
×
  • Create New...