Jump to content

nikoli

Member
  • Posts

    27
  • Joined

  • Last visited

nikoli's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. The gain reduction "needle" on a compressor... for instance. I put the Wave CLA-76 comp on a snare track, the needle bounces when the snare hits... the needle visibly reacts to the attack settings too... as one would expect. I put the TG on the drum bus (or any other buss) and the needle on the CLA-76 bounces well before the snare hits. If I remove the CLA-76 from the track and add the Logic comp, the needle bounces as the snare hits... as one would expect. I sent a video of this behavior to Waves support, and they acted like it's Logic's fault. I honestly don't get how it could be Logic's problem.
  2. Logic Compressor has no latency. Anyway, i cannot replicate the behaviour with 10.4.5, even DeBreath doesn't screw with metering anymore... Maybe they fixed something. Right but the CLA-76 is also extremely low latency. Regardless, if the TG Mastering Chain is the high latency plug that is throwing the meters off ... shouldn’t it throw the meters off for all plugs? Hopefully this is all academic and the update fixed it lol. Will test later.
  3. Honestly can't wrap my mind around this... if Logic isn't compensating metering for delay... then why does the metering work with the Logic compressor plug while the TG Mastering Chain is on the stereo bus? Remember, the metering goes wonky only with other Waves plugs while the TG chain is on a bus. I'm not saying Logic doesn't have latency issues, but in this case I can't point my finger at Logic.
  4. No, the visual problem does affect Logic plugins as well. They just need to be creating enough latency for it to be an issue, or at least, be part of a high latency chain. With Logic's plugins like it's Compressor and EQ, they don't cause enough latency for it to actually be noticeable. I haven't tried this, but if you put one of it's Noise Gate's on track, set the "Lookahead" to a very high value, it should affect the VU's of other plugins. Try 2 if you have to. I'm pretty sure it will illustrate the problem. Well, I say it's a problem, but its probably actually a design "feature" believe it or not. In order to optimise the DSP for audio processing, Apple probably opted to make the visuals a low priority for the CPU. Possibly. Or maybe they were waiting for Metal to improve so it could implement quicker draw calls without the latency. Maybe we'll see an improvement in the next release. MAYBE. I wouldn't hold my breath though. Waves Tech Support is right though, it's a Logic issue. The reason why their Live versions work is they have been designed to induce minimal latency. The only problem is, you loose a tiny bit of quality in the process. Oversampling might be one, but there could be other features you lose as well because they induce too much latency. Thanks for the response! If what you say is true and accurate... I'd say this is a major problem. But it is truly odd that it only seems to happen with this specific plugin. Also, part of my workflow / template is that I place the Logic noise gate plugin at the 2nd plugin of every track in my project. I usually set the look ahead somewhere between 9 and 12 milliseconds for most tracks. For vocals I set it to 20ms... and typically there's at least 3 vocal tracks. Never noticed any VU meter problem until this Abbey Road plug.
  5. I suppose... but imo the burden should be on Waves to make sure their plugs work on the platform. Do you have the TG Mastering Chain? If so, does it work normally with Logic?
  6. I've had the 2012 'server' machines, but they were used as SQL/PHP servers and never for audio, i also have an i5 Mac Mini but it's used for shop stock inventory/pricing etc. Good machines but they've been temperamental in the past for losing Bluetooth connectivity to devices and just freezing up randomly. My question on the Mac Mini's such as the new i7 is how reliable will they be if you're running them at 80+% load in summer months for continual periods of 2-4 hours several times a day, Thermals and the reliance on the machine running through the hottest summer months is why i've always steered through the Mac Pro range. I suppose in a way, i'm answering my own question as i type this - the i7 maybe won't need to run at anything near that load due to it's capability. But alas, 'what if'? Is that their intended use? Are they spec'd internally to cope? Bluetooth connectivity in some older Mac Mini models is a known/fixable issue. I know... I had one that would lose my bt mouse at the worst times. I found out about the fix after I tossed out my bt mouse. lol, never had problems with any bt devices after the fix. Google for the iFixit bt shielding kit. Totally solved my problem.
  7. UA leads the way on TB too... which is nice cuz I'm bought in on UA's ecosystem to the same degree I'm bought in on Apple's.
  8. You don't understand the basic principle of Dunning Kruger. DK addresses a person's cognitive capabilities. It has nothing to do with folks jumping to conclusions during the course of a product release and the information being examined, hashed out, discussed and dissected. The key element for you to understand, "cognitive bias." Maybe the below will help you understand what DK means: "In the field of psychology, the Dunning–Kruger effect is a cognitive bias in which people mistakenly assess their cognitive ability as greater than it is. It is related to the cognitive bias of illusory superiority and comes from the inability of people to recognize their lack of ability..." I hope this helps. It has absolutely nothing to do with what's happening here. Dunning himself says the concept applies to specific topics... even down to specific points being made about a specific topic. For instance, some people think they know a lot about computers and are biased against a particular brand of computers. Therefore, when said company releases a new computer... these people exhibit a strong opinion about said computer without actually knowing much about the computer itself. That is the Dunning Kruger effect in its very essence, and it is on fully display in this thread.
  9. ...you really felt the need to post this? That's brilliant! To be fair, it's not just you. After seeing 3 pages worth of people confidently posting bold opinions based on pure cojecture and misinformation (see the post above this re: audio output)... I felt compelled to post the Dunning Kruger graph... because it applies perfectly to this thread.
  10. Why would an audio professional care about this on a tower? Audio professionals have audio interfaces. If anything, assuming what you're saying is true, this is better for audio professionals. No dollars or system resources being used by a soundcard that's never going to be used.
  11. HDD's ? Ya know, for someone who doesn't know much about this new computer... you sure do have some strong opinions.
  12. Maybe I haven't been able to wrap my mind around this yet... but I'm not able to understand how this is a problem with Logic. (Am I crazy or is that what the Waves support guy is suggesting? ...that the problem is in Logic and not Waves). The problem only affects Waves plug ins. I can have an instance of the native Logic Compressor going, and it remains perfectly aligned with the snare drum, while the needle in the Waves CLA-76 is noticeably ahead of the audio. If I remove the TG entirely, the Waves CLA-76 needle syncs back up. Their support recommended using the "Live" version and that seems to work. This all suggests to me the problem is the plugin, and nothing to do with Logic or how it handles latency.
  13. I had not seen that article. Thanks. I suppose I'm not sure what to do with it though as it relates to the problem I'm having with this particular plugin though.
  14. Hey all, I'm experiencing an odd problem in Logic with the TG Mastering Chain plugin. I'm wondering if anyone else is experiencing it too. Basically the TG screws up all my Waves VU meters. For instance, if I put the CLA-76 on a snare drum track, the "needle" acts in accordance with the recorded snare drum. If I then add the TG Mastering chain to the drum buss (or master bus), the "needle" on the CLA-76 plug anticipates the recorded snare drum. In other words, the needle moves well before the sound of the snare drum occurs. If I turn the TG plug off, the problem still occurs. If I remove it from the buss completely, the needle syncs up again. This seems to only happen with Waves plugs. I spoke with Waves support. I gave them a sample project and even made a video for them. Here is their response... It seems like he's saying this is expected behavior. Anyone else reading it that way?
  15. Hi all, I've opened an old project that I hadn't worked on in a while... since before the last major Logic update. I needed to finish recording some vocals for it. So I armed the vocal track I had previously used and began recording. When I go to edit the new region with flex pitch, it does something really bizarre... kind of hard to describe but it basically takes the region and stretches it out the length of the entire project. The audio seems to be stretched out along with it. So it essentially destroys the region. When I disable flex pitch on the track, it goes back to normal. Unfortunately disabling flex pitch isn't an option because 1. I'm a terrible singer and 2. flex pitch has been used extensively throughout this particular project. (Lots of vocal tracks, lots of plugins, etc). Here's the weird part. I can export the region to a wav file, and then drag it back into the project... and it behaves normally when I open the flex pitch editor. WTF? That's an okay work around for now, but man... I'm hoping there's a better answer for this!
×
×
  • Create New...