Jump to content

ReDRuMxxx

Member
  • Posts

    127
  • Joined

  • Last visited

ReDRuMxxx's Achievements

Newbie

Newbie (1/14)

  • Reacting Well Rare
  • Week One Done
  • One Month Later Rare
  • One Year In Rare

Recent Badges

0

Reputation

  1. Sorry, false alarm, not fixed It seems I was hallucinating
  2. Hello! Q: Is there a way to remove Logic's default I/O label assignments? I can add my own but that's just confusing. Clarification below. I recently bought an RME Fireface 802. On my patchbay I will have rows 1 through 12 as Fireface inputs, rows 13 through 20 will be Focusrite inputs. The "issue" is that Fireface reports SPDIF/AES I/Os as 13 and 14, but I will not be using those. So my patchbay setup will either have missing number labels, or be misaligned with what Logic reports, because the inputs are numbered always as reported by the driver. I can “ADD” my input / output name labels, but the original numbering is always visible - which is quite silly IMO. Any way to change this? Please see attached pics of my setup. Thanks! P.S. - If there was a way to simply not show Logic's default labels at all, that would be perfect.
  3. Found a way to remove markers in an already created WAV file. Navigate > Other > Remove Marker from Audio File. Really simple
  4. Hello! I don't want project markers as metadata in the WAV file. Can they be removed without actually removing the markers from the project before export?
  5. Yes, and everything you both claim I'm agreeing with There still is an actual benefit (not huge) to using oversampling while mixing / processing audio, even if the original recording was lower resolution, and the delivery is lower resolution. That is a technical fact. You guys haven't shown in anything you wrote that you actually understand what exactly I'm claiming, and I cannot explain it here better than it's explained in the paper. The 'counterclaims' made by triplets have nothing to do with the topic of the part of the paper I referenced above. Please keep in mind that I'm not claiming some huge benefit. But it is there. It is not a matter of belief, this is not religion
  6. Wow, you guys are really stubborn Please read the part of the paper I quoted, if you have the time. If you are disagreeing with me, that's perfectly fine, but at least try to understand what my actual claim is
  7. I agree with 100% of what you said. Even though it might seem counterintuitive, there is some knowledge in the paper I posted that you do not have. If you want to acquire it, read the paper. Cheers.
  8. Thanks for your input. I will adapt to the situation now that I now that I have to I was thinking that maybe I am doing something wrong, hence the question. Regarding the "upsampling" topic, sorry, but what you are saying is not correct. This is the paper I was mentioning before, starting on page 43 ( IN-THE-BOX OVERSAMPLING ), but I think the whole chapter 7 might be of interest to you. https://www.dropbox.com/s/57mfbtzjypw90gx/Perica%20Suran%20-%20Modern%20Audio%20Consumer%20Formats%202015.pdf?dl=0 Cheers. P.S. - This is all technically true, but using higher sampling rates for mixing can still be beneficial. Not for recording or for final delivery IMO. Digital audio is complicated
  9. iTunes was stopped. Plus it doesn't matter. iTunes can be turned off completely while one changes the sample rate from within Logic (or just opens an existing 88.2k Logic project). Then after you turn off Logic, the system setting remains at 88,2 k - that's the whole point. And now everytime you play a song from (again opened) itunes it uses the 88,2k setting, which in my case (Antelope Orion) results in a click. It is obvious that changing the samplerate from within Logic changes the system setting, and keeps it changed even after Logic is closed! I do a lot of mixing only. Also, this would solve nothing in this case, as Logic doesn't upsample 'live', it creates new files. iTunes, on the other hand, can conform 'live' to any system samplerate setting. Try it Anyway, thanks for your input guys
  10. I also record at 44.1k. The point is that I MIX in 88,2 k samplerate. I don't think going into 'why' is relevant here. The point is that the system (or some part of the system) is not behaving as intended. I don't think OSX said: 'mixing in 88,2 k is stupid, here's some clicks' :) I don't think the sample rate should stay at 88.2 k if I turn of Logic. And it most definitely shouldn't be creating clicks. If you would like to know why I choose to mix in 88,2 k, I can send you a paper I wrote on the topic (in part).
  11. I don't have anything multiple running on my Mac... Not sure where the misunderstanding is. Have you watched the video?
  12. I haven't had time to thoroughly test on other soundcards, but I did figure out that there's another "symptom". Not sure if it's related to the topic of this post. What happens is that every time the device samplerate changes, I hear a click (like a relay switching). I'd say this is normal, except that the samplerate needlessly changes at random. For example, if I turn on the computer, and play songs from iTunes using the Orion, everything is fine - no clicks. BUT - if I open Logic, set the samplerate to 88.2k, and CLOSE Logic - the systemwide setting somehow remains set to 88.2k, and every time I play something from iTunes (or any other system sound plays) there is an audible CLICK before and after the sound. Also, I see in the Orion control panel these clicks correspond to the samplerate changing from 44.1k to 88.2k and back. I know it's maybe hard to understand, so here's a video. https://www.dropbox.com/s/70hx018a69phel4/Samplerate%20error%202.mov?dl=0 I can see in AudioMIDI that after I've closed Logic, the Orion device samplerate remains at 88.2k. It's tedious to fix this every time manually + it might be related to my original problem. What do you guys think?
×
×
  • Create New...