Jump to content

GoodBear

Member
  • Posts

    28
  • Joined

  • Last visited

Recent Profile Visitors

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

GoodBear's Achievements

  1. Alright all! This "myth" is basically confirmed in my mind. Here's ranked performance for buffer size from best to worst on my 1600+ track template (in a very full session) 1. 64 2. 256 3. 128 4. 512 5. 1024 & 32 (Tied for being absolutely and completely unusable) The buffer size common wisdom seems to no longer be "the higher it is, the better performance" but rather "test what works for the specific computer and session you're working with".
  2. This is so fascinating! I'm gonna take my buffer size down to 64 and see what happens! lol.
  3. Hey all! Just got a new MacBook Pro - M2 96GB Ram, 4 TB SSD. Ventura 13.4, Logic 10.7.8. My settings are I/0: 256, Processing threads: 12 High Performance, Process Buffer Range: Medium. It's performing pretty well! I'm doing my best to make a 1600+ track composing template built for a more powerful mac studio work super well on this computer and, for the most part, it is! I am getting some weird issues though. I have quite a few plugins loaded in the session, possibly up to 3 per track, as well as busses with reverbs and track stacks with just as many plugins. One track may have up to 12 -15 plugins in its path. That considered, performance is great. No pops or clicks. My CPU on a heavy session is hanging out around 50-60% on most of the threads. The thread furthest to the left is hanging out at around 90%. I believe this is because of all the plugins, but I'm not sure. The furthest thread on the right though, (the live track thread) is doing incredibly well. Basically hovering at 10%. I'm definitely pushing this computer a bit passed what it's supposed to be doing, but eh, it's basically handling it great. Here's my question - this template is absolutely performing better the LOWER my buffer size is set. It's really weirding me out. Its best performance by far is with the buffer size set to 256 or 128. When I try to set the buffer at 1024, the template basically falls apart. Pops, clicks, dropped samples. It's falling to pieces. I have absolutely no idea why this is. Any valuable insight here? I'd like to be able to kick my template into "5th gear" and set the buffer at 1024 so that I can get a few extra tracks in when absolutely needed. Or at the very least, I'd like to gain some understanding into what might be happening here. Any thoughts are absolutely appreciated. Thank you! 🙂
  4. Is it a realistic possibility with logic to revert to a previous version? I've never tried it before.
  5. I have read other threads and it seems that, for me, paste at original position is almost completely broken in logic 10.7.8. I don't know exactly when it broke. I've tested this with my large composing template as well as completely empty projects, and the behavior is the same. Pasting notes "at original position" is offset by however far away the region is from bar 1. If my region is at bar 3, and the note is at bar 4 (one measure into the region), "paste at original position" drops the note at bar 2 of the selected track or region. This means that if a region starts at bar 1, the bug is not there. Watch the attached video to see how it's working. It's worth mentioning that the command works totally fine when I'm copying and pasting regions within the arrange window, but when I try to do this in the piano roll, all hell breaks loose. The other bug I'm getting is that when I do this command within a region that is track stacked, that region disappears when the track stack is closed. No real rhyme or reason for that... when the track stack is open, you can see the region, no problem. When the track stack is closed, it just appears to be an empty track stack. Then I'll press command z a few times to undo all the shenanigans, and THAT will snap the region I pasted to out of its original position by however many bars the off-note was pasted by. Then I have to manually drag that region back into place. Undoing causes the problem, and can't solve it. I'm sure this is a bug, and I've gone through Logic's "If Logic Pro isn't working" checklist. Curious if anyone here has thoughts about how to fix this! Unorthodox solutions welcome. Paste in original location has been a pretty integral part of my workflow, so anything's welcome! Screen Recording 2023-06-02 at 11.09.39 AM.mp4
  6. I hope so! And I certainly hope that I can nudge the developer into updating it to work a little better.
  7. It took one very tiny test to figure it out! It's Berlin Studio Reverb! I ran a kontakt instrument into 17 aux channels with True Iron, Cinematic Rooms, Pro q 3 and Berlin Studio Verb on each of the auxes. Then I took off the plugins one by one. With ALL of the other plugins active and engaged, but no Berlin studio verb on the auxes, the template (in native) went back to performing extremely well, like I feel it should when running in native! When Berlin was activated, but the other plugins removed, I was getting those same spikes across many of the CPU threads! I'll have to send some of this info into Samplicity.
  8. Absolutely! I'm trying to run some tests today and see if I can find anything specifically that is making this difficult on my system. If I find anything even remotely conclusive, I'll let you all know! Thanks so much for your thoughts!
  9. I'm running a fairly huge template (1600 tracks, but with a fair amount of those disengaged). And my performance with Rosetta is phenomenal, unbelievable, almost - CPU at 25% percent on all cores. Though, it will definitely spike and have some pops/clicks when I record enable a track... but that's fine and to be expected for such a huge session running at 256 (I can get better performance out of 512, but I honestly don't care if there's a small glitch here or there when I'm recording an instrument, and only in the biggest sections, and the lack of latency makes up for it). Generally it's very consistent, very good. Native is a different story. I can't have one instance record enabled on the session without everything crumpling TO THE GROUND. lol. Literally, maxing out almost every core. Something's obviously wrong. These are the plugins I'm using in this session. As far as I know, I've updated all of these to their latest native versions - - Stock Logic Gain - Stock Exciter -Stock Tube EQ - Fab Filter Pro Q3 - Fab Filter C2 - Karzog True Iron - LiquidSonics Cinematic Rooms - Berlin Studio Verb - Kontakt 7 - Massive X - Some Valhalla Verbs (the latests "native compatible" versions) And that's about it! Curious to hear what y'all think. Interested why performance can be so much better with Rosetta than in Native. Oh also, I'm on a Mac Studio Ultra, 128GB of Ram, Ventura 13.3.1, Logic 10.7.7
  10. AHHH. Fair. Apologies, and thank you! This is super powerful. Excited to get into it! 🙂
  11. This is awesome. Thank you! So much helpful information. Is there anything within the sysex edit window that will let me control the value that I'm sending? Lets say I set up a sysex button and want to send a value of 30 to controller 7, and a value of 40 to controller 1. Is that possible?
  12. Oh, interesting! So could I potentially send a bunch of different signals out with the click of one sysex button, and a bunch of different values and controls set within the sysex editor box?
  13. Ahhh, ok. This makes sense. But if I do this, will the fader information always be sent at a particular bar and beat? Like a 0 sent to volume controller at 1 1 1 1 as it’s shown here? Or can I just control it like a normal fader?
  14. I feel like this is what I'm getting wrong, but I'm not sure how to fix it. Here's what happens when I try to set up mine like you have it. What do I need to change? Screen Recording 2023-04-16 at 1.50.28 PM.mov
  15. I wasn't able to find an answer to this in the forum so far - Can you use one sysex fader to control another fader? I'm making mix/mic position macros, and I'm hoping to create a system where I can exclude certain faders from sending to tracks when I press "send all fader values (except sysex). But as I've set up a Sysex fader or button, then sent that to another fader, I can't get it to do what it's normal behavior was when it was just a fader sending information... or get it to do much of anything, really. Any help would be great appreciated. Thank you!
×
×
  • Create New...