Jump to content

rasmusmarshagen

Member
  • Posts

    31
  • Joined

  • Last visited

Personal Information

  • Mac
    MBP M1 Max 64GB

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

rasmusmarshagen's Achievements

  1. Yeah hopefully they're aware of the problem. I will definitely report to apple and also try contacting fabfilter for example. Thanks for the reply!! 🙂
  2. Interesting. It's very ironic that it's only (except for audio hijack I suppose) apple's own software that has this issue running it natively on their chips. Why can't Logic just host the plug-ins like it used too? I never had any problem with that, and the argument that Logic doesn't crash anymore makes no sense, if a plugin crashes and you click recover, it kind of re-loads all plugins up anyway, takes equally long... Yeah agree, it's workable, but very annyoing IMO.
  3. Hi, I've been experiencing 3rd party GUI's slightly lagging/freezing up shortly now and then (at least once a minute). And after a lot of research and troubleshooting I've finally found the culprit. It's Logics new "external plugin hosting system" (AUHostingService) that it has to use for third party plugins when running it in Native mode. This is extremely easy to reproduce and isolate. Try this 1. Load up a Fabfilter Pro Q 3 in an empty project. (could be any plugin really, but this one is easy to test with) 2. Create a band, grab it and drag it around. 3. Within a minute (or in some rare case up to two minutes), the graphics will hang slightly. (this is quite subtle, but very very annoying IMO,. Audio is not affected) This is a good test because it's so clean. Just an empty project and you don't even need to press play. I've tested this in rosetta mode and it's absolutely fine. And in a bunch of other daw's in Silicon native, and it's fine there too. And in plugin-wrapper BC Patchwork, buttery smooth graphics. I also have a M1 Macbook air (2020), with Logic 10.7.3. And it happens there too. So I'm confident that this has nothing to do with my settings or anything, but rather it's a fundamental issue with how they've implemented the AUHostingService. No problem CPU-wise, projects play butterysmooth, but these graphics hangs are driving me nuts. Can someone please confirm this with an apple silicon computer? Cheers,
  4. This behaviour started in 10.7. When dragging any "track stack" into a "folder stack" which already contains tracks in it (midi or audio/or aux or even other track stacks), the dragged track stack now swallows the tracks below the position where you drop it. Meaning the tracks below the position you drop the track stack, basically joins the track stack instead of staying on top level in folder stack, as originally intended. The only exception to this is when you drop the track stack at the very top inside the folder- then it doesn't "swallow" any tracks. Related to this is that any track (audio/midi/aux) that you drop right below a track stack (collapsed or uncollapsed) which is inside a folder stack- will be included in that track stack. This is obviously not the intention when making this move. I just reported this bug to apple- please do it you too: https://www.apple.com/feedback/logic-pro.html Thanks!
  5. Yeah noticed that too... Maybe this one needs to fixed from Celemony i don't know. Since I don't have these issues with any other plugins.
  6. Ough... Thats not good:( I kind of don't wanna go back to the previous version because they fixed the "automation chase" issue on this latest one. Which is awesome.. They listed lots of "marquee" entries in the change log, but this one looks like the one that changed it? "Fixes an issue where option-drag copying a Marquee selected area that encompasses a number of complete regions could truncate some of the resulting copies." I don't know. So maybe it's not a bug and they intended it to be like this now. But even if its a bug, the problem with Logic is that we will have to wait months for tiny fixes like this.
  7. NOOO... This function is broken/removed in latest 10.7. I can't believe they're doing this? Have I missed something?
  8. Important part to note that I left out- this error occurs when using the latency-inducing sidechain plugin on a bus/aux, its working fine directly on tracks. So to summarize: With a ZERO LATENCY sidechain plugin (such as a compressor etc without lookahead or oversampling etc) the sidechain delay compensation now with 10.6.3 works brilliantly, even when placed in between lots of high latency plugins. Works on both tracks and buses now. However- when using a latency inducing sidechain plugin (one that adds latency within itself, such as any plugin with lookahead and or oversampling turned on for example Fabfiter C2 or MB, or Soothe 2 which always adds latency) - then that signal won't be latency compensated when used ON A BUS/AUX. It does work when using on a track though. Hope all this is clear. Very easy to troubleshoot with the flamming technique (soloing original percussive sound and auditioning the sidechain signal from the plugin)
  9. The sidechain PDC issue is almost completely fixed in 10.6.3 You can now place high latency plugins on tracks and buses/auxes in any order before and after sidechain plugins and its synced proprely- IF the actual sidechain plugin is ZERO latency. As soon as you turn on lookahead or some oversampling etc on the actual sidechain plugin- its not synced correctly. Huge progress, thank you apple team. Would be magical if they could just fix this last issue too. For example soothe 2 always add some latency by itself, so this one's sidechain signal won't be aligned properly. I just reported this, please everyone do it too. https://www.apple.com/feedback/logic-pro.html
  10. For anyone following this... I've done some extensive experimentation with the settings and come to the conclusion that: 1. Logic Pro X's multithreading option "Playback and live tracks" is completely useless since it stacks CPU load on 1 thread whenever auxes are involved. If you only use tracks and route them to the stereo bus with nothing on it, you should be fine, as it distributes the load very evenly (although still a bit more taxing than the regular playback mode). This option somehow makes logic extremely snappy and wonderful to use except for that CPU con. 2. Sadly for the rest of us we have to use the "playback only" multithreading option. And what I found out is that Logic Pro X does NOT play well at all with the hyperthreading. My iMac Pro has 10 cores, so 20 threads are available in the audio setup in logic. When 20 threads are chosen I get this extreme latency which makes it totally unusable. But when I choose 10 threads, there's almost no latency, or very minimal and not disturbing. It's even better if I pick 8, 4, and the best at 2. So to sum it up- use ONLY the amount of threads equal to the amount of cores your computer have and you should not have latency issues. I just wish apple would take care of this and not let us enable hyperthreading in logic if its not supported. And also, give us a comprehensive explanation about that multithreading "Live and playback tracks", I have no idea whats going on there. Who would ever use that option? Anyway, 10 threads is well enough for me to make music with, and it works now, hope this helps anyone in a similar situation:) cheers
  11. Hi, I've recently upgraded my computer from a 2013 iMac intel duo core to an iMac Pro 10 core. I'm having serious issues with audio playback latency/delay, for example when I click solo on track- it takes well over 1 whole second for the sound to respond to that. And this delay seems to be that fixed time amount no matter what I try to do, start/stop playback, EQ-ing etc. I've ruled out buffer size from this problem, since it's also happening when set to buffer range:low and i/O buffer size even down at 32. What seems to be the problem is the multicore/thread support, because when I switch from 20 threads down to 2, there's almost no latency at all. Now here's the weird part, when my setting is on 20 threads, large buffer range, and 1024 buffer size- IF i switch the "multihreading" option from "Playback tracks" to "Playback & Live Tracks" its extremely snappy and theres absolutely no latency at all. What is going on here? I've tried to understand Apple's own explanation but they're just vaguely saying that it could be better sometimes when running a lot of live instruments. Now this mode solves all my problems, except for one thing- this mode stacks CPU on one core, and doesn't spread when I try to force CPU spreading by routing to busses, it all ends up on core 1, which makes it unusable. The cpu load is significantly better on the regular "playback mode" as well, but WHY is the sound so delayed? Can anybody please shed a light on this subject because it shouldn't be this hard to make music on a crazy expensive computer optimized for they're very own pro software! Thanks in advance:)
  12. I see what you're saying but I just couldn't see a practical use for any of those messages from an encoder/button/fader midi controller so just wondered why it was there by default but I get now that it doesn't matter what device ur using. Also didn't know you could reprogram the button to different cc message. Anyway I'm happy now, glad that it could be solved in the environment! Back to music:)
  13. I solved the problem. I get that the MIDI protocol is old have its standards but I how is this pan message relevant in logic today, why "should" it do that by default? Who pans inside a software instrument like that? I have mapped buttons from my midi controller (kenton killamix mini) and one of the buttons happened to send cc#10. So I wanted Logic to receive that message and do what I mapped it to do, but at the same time it then also panned the signal to the left. That feels like dictating to me if the solution would be not to use that button. There should be an easy way to bypass those standard messages I think. Anyway I did figure out a way to get this to work the way I want it- two tranformers, one filtering out all control messages from the MIDI-controller, and another just passing all midi messages through from my midi keyboard (so that I don't filter out the sustain pedal). Thanks
×
×
  • Create New...