Jump to content

oldbetseysatan

Member
  • Posts

    208
  • Joined

  • Last visited

oldbetseysatan's Achievements

Newbie

Newbie (1/14)

  • Reacting Well Rare
  • First Post Rare
  • Collaborator Rare
  • Week One Done
  • One Month Later Rare

Recent Badges

0

Reputation

  1. Hi des88, I know it's only been a few hours but did you give it a go on your M1? I'm eager to update as reports are that Pro Tools is using all cores now and running really smoothly but I'm 50/50 between LPX and PT and don't want to tank all my Logic projects. R.
  2. For future reference: Wexdan over at KVR suggested opening up any Melda plugin in Ableton Live (where the graphics weren't wonky) and checking the preferences to see if Retina support was enabled. In fact it was enabled and UNCHECKING the preference actually solved the problem. R.
  3. Hi guys, I'm sure this is just (another) schoolboy error but I'm getting these graphics quirks (oversized GUI) on my M1 Air using Melda plugins but only with LPX and Soundsource. Pro Tools and Live are playing fine though. Strange, right? So technically not strictly a LPX problem but thought I might ask here (no response on the Melda KVR forum, also seems to be populated by mainly PC users) to see if it's just happening on my system or if anyone else is having these graphics issues. I also can't seem to be able resize the GUI to get to the plugin preferences to see if there's anything there that can help. Many thanks! R. M1 Air / Big Sur / 10.7.2
  4. EDIT: I knew it was something stupidly obvious... In that same RX preference window there's a checkbox that says "Host Performance - Enable Analytics" and me being so hyper anti-Big Brother nowadays I left it unchecked and I didn't want iZotope phoning home, well, basically ever. But of course it's nothing (NOTHING!) to do with that. All good now. Thanks for sending me back there though and keeping me focused on the preference pane. R.
  5. HI Christian, Thanks for the reply! I did notice that before but just now went back and double double checked and yes I definitely have Delay Compensation enabled - both in the plugin and in the LPX Preferences. The strange thing is that it doesn't happen when I open a new empty project and create a couple of test files and process one of them. I went back to the original and took off all Channel/Bus/Master inserts/routing etc and the new audio file is still offset. Very strange. I'm sure it's something staring me right in the face but I just can't see it. R.
  6. Hello LPX gurus, I'm sure this is just a schoolboy error but my audio is shifting back on the timeline when using RX and SBP. My buffer is only 32 but the file (or I should say the processed audio IN the file) is coming out about 8000 samples late. What am I overlooking? Cheers! R.
  7. So basically I narrowed it down to two things! 1. A chap over on Gearslutz said he'd run into this once when, and I'll quote, "This can happen if you have two copies of the same plugin, one in the system components folder where they normally live, and one in the user version of that folder: /Users/[user name]/Library/Audio/Plug-Ins/Components' and lo and behold I found HornetVU in both folders. Not sure how it got there, maybe an installation gremlin, but deleted the instance in my User folder and I was down to four plugins still acting up. 2. The remaining plugs were all leftovers from my Mojave install that didn't seem to have the proper security signing/clearances that Apple brought in with Catalina. Somehow they could still be validated in the AU scan (not sure how?) but it was holding it up for a moment (hence the consistent rescanning on start-up) before launching. I found that if I "aborted" the scan during launch (I had to be quick because it would only flash for a second or two) it would ask if I wanted to continue without the plugins and I would hit yes (or 'continue' or whatever it said) and then if I immediately went to the Plugin Manager I could see which plug was causing the problem. I repeated this four times deleting each plugin and then restarting and relaunching and voila finally no rescan at launch. R.
  8. Nope. Nada. If anything I pulled things out that weren't compatible then deleted the AU cache and then rescanned but all to no avail. I wish there was a way to see (in Console or something) the scanning process. R.
  9. I did indeed. Is there any way to see which plugins might be (ever-so-slightly) holding it up? I mean it's not a show-stopper but you know how it is. Just wish I knew what plugins were causing it. R.
  10. Hello LPH, Wondering if anyone has any ideas? I finally moved up to Catalina and 10.6.2 a couple of days ago and now every time I start up LPX it rescans 6 (and only 6) plugins. All of my plugins (including those 6 whatever they are) are validating and I also tried deleting the AU cache but no joy. Is there any way to find out which 6 plugins (of my 100's) are rescanning? I tried to watch Console but stuff is just flying by and, to be quite honest, I'm not sure what I'd be looking for anyway! Cheers! R.
  11. Haven't seen Shiver around in ages but just wanted to shout out a big thank-you for this info! R.
  12. Holy thread resurrection Batman! But just to post this here in case a Google search for 'how to create markers without snap' brings others here. Not sure when it was added but there is now a "Create Without Rounding" menu item that can (obviously) be given it's own key command. I just remapped the ⌅ to 'create marker without rounding' and Bob's yer uncle. R.
  13. Bizarre. Now I'm committed to this. If I get a chance over the next day or so I'll do a little screen capture of it...
  14. No. Try this. Drag a loop into your session to, say, bar one. Now imagine you've just read about the above behaviour and you're thinking "Hmmm. It always works for me" so you go to the loop, press Shift and click on with your mouse. It then blinks in a "I've been selected" type-way. Meaning the high-lighted header goes clear and, well, yea, a slight blink happens. I've just done it 15 times to make sure I'm not going crazy! Does yours not do that? And I should add this disappearing of the header doesn't happen with normal audio or midi regions either. A huge sorry to the OP. This is obviously not helping you! R.
  15. My apologies! OK so I just did a quick test and it seems it only does it (the blink) with Apple loops. With normal clips it works as described. The irony is that I hardly ever use loops but had a session open at the time that I was using some drum and bass loops to experiment with McDSP Comp and that's what I was using to check for the behaviour. So yes, having double-checked, with normal audio and midi files pressing Shift *first* and then selecting the region creates the blue rectangle. The blinking of the loop (or I should say one blink of the loop) happens when you have Shift pressed before selecting the loop. Not sure if the blink even means anything? So I shall take my snarky comments and leave forthwith!
×
×
  • Create New...