Jump to content

Soundsauca

Member
  • Posts

    6
  • Joined

  • Last visited

Soundsauca's Achievements

Rookie

Rookie (2/14)

  • Reacting Well Rare
  • First Post Rare
  • Conversation Starter Rare
  • Week One Done
  • One Month Later Rare

Recent Badges

3

Reputation

  1. Hi @Jordi Torres & @des99. Thanks both for your answers. Disabling core audio and unloading the mininova plugin did the trick. The plugin isn't present on my new machine due to age etc. Interesting that it might be caused by another plugin. I'll keep an eye out if it happens again and maybe have a look through if there's anything I don't need as in legacy plugins.
  2. I've got an older project (not that old mind) that loaded fine in Logic on Ventura. I tried to load it with Sonoma today and it just hung. It contains a plugin that's not available on my new system. This isn't normally an issue but it just beachballs. Any ideas?!
  3. I'm beginning to understand. So effectively the new Logic sandboxes and loads plugins "externally". This may well be the reason I cannot get VStation running. I know it's not supported anymore, but I'm a sucker for punishment and have been trying every which way to get all my older plugs working in some way. I had a brainwave to use Plugin Guru's Unify plugin to try and authorise VStation. I got further than Logic crashing (just about!) and got the message (attached). So far I haven't lowered the security settings as I'm not sure what the consequences could be and how I could revert the security if it doesn't work out.
  4. Ah right ok. Thanks for the information. So it's a known quantity. Yes I didn't see anything wrong in the vsts in Reason, however I only have Reason for the instruments these days but I digress. I did move over an old version of Logic (10.5.1) to try and run some old plugins, but I haven't spent enough time with this to be sure. It's not a big deal now I know what it is. I'm sure as you say over time things will improve.
  5. Hi there, A few months ago I upgraded from an 2017 MBP to a Mac Studio M1. I didn't use it immediately for music as it was bought primarily for video editing. Recently I've had the chance to load my plugins on it and for the most part things are fine. However I have noticed that some plugins appear to suffer from a GUI freeze that also affects Logic itself. It doesn't last long. In fact it can go almost unnoticed (hence I didn't!). Now I see it, I can't "un-see" it. I tried to rule things out such as audio drivers etc, however it occurs even on the internal audio out. I don't think it's all plugins but I've noticed it in Korgs Modwave, some Arturia synths to name a few. They're all 3rd party so I guess there's that. I was initially concerned it was the Mac, but now I'm not so sure. As a test I loaded up Reason 12 (latest M1/M2 version) and loaded the equivalent in VST. I played for quite some time and didn't see this happening. Unfortunately I haven't updated my Ableton Suite to run natively so I can't confirm for sure if it's an AU issue or a Logic issue, or some sort of Metal/Open GL issue. Modwave for instance, is dependant on Metal or OpenGL so maybe that has some influence. The other thing that happens is that the mouse input disappears upon using certain plugin GUI controls. I appreciate that these issues may be due to the architectural changes and a multitude of software updates compared to my Macbook. It's just a little disconcerting that my 6 year old laptop runs things at times more smoothly. Less CPU for sure, but smoother yes! I mean is this to be expected, or is there some hardware issue at play? I'm relatively sure it isn't but thought I'd put it out there. Thanks a lot for reading my poorly constructed brain dump, but I figured this would be a good place to ask for any advice. Best, Michael
  6. Hi there, I'm Michael. I signed up here to post on this issue. Similarly I currently have a: • MBP 2017 15" 3.1gz • RME UFX (Firmware 360, Driver 3.21 • OSX 10.14.6 Mojave • LogicX 10.5.1 (The last version to work with Mojave) I can concur that this happens to me too. I went through a phase maybe 6 - 8 months ago with some really nasty overs with certain settings & plugins. I tried to understand why and when it happened. One plugin was the Korg Legacy Arp Odyssey, I thought it was plugin specific at first but there were others. I used Cerberus Audio Ice 9 thinking it might at least save my speakers/headphones and ear drums, but no joy as it happens outside the master channel in Logic. I started getting more irked when it occurred whilst I was using iTunes and listening to a radio stream. It was so weird... As with Ctrl-Alt-Delete I added a channel limiter on the RME mixer which at least brick walled it at 0db I guess. I did do some further research which may, may not have been said already so apologies if I have. The signal is like a massive DC offset, when it happens the pop is huge and the meters go off the chart as mentioned. On my RME fader you can still hear the frequency rumble after the pop. For me, unloading the plugin usually killed the signal. I then started to investigate the Audio Midi setup application found in: /Applications/Utilities/Audio MIDI Setup.app (image below). At that time I had split the sound for my DAW to a separate channel in here to bus it to a separate fader in RME Totalmix. I decided to remove this and just bus it to a single channel. Since then I haven't (touch wood) had it happen again. Likewise I do believe it's CPU/software related. I also don't think it is specific to RME as I've had someone with an Apollo interface experience the same. It may be something to do with multi-core processing and separation of threads, but also maybe the cpu throttling or the T1/T2 chip?? I'm not sure but that's my best guess. Anyway, the settings below might be worth looking at for any RME (or other) owners out there.
×
×
  • Create New...