Jump to content

Jonathan Levine

Member
  • Posts

    115
  • Joined

  • Last visited

About Jonathan Levine

  • Birthday 02/19/2001

Recent Profile Visitors

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

Jonathan Levine's Achievements

Apprentice

Apprentice (3/14)

  • Reacting Well Rare
  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Week One Done

Recent Badges

12

Reputation

  1. I’m trying to use higher sample rates for my projects, but despite having an M1 Max in my 14” MacBook Pro, I still can’t use a 32 buffer size with a 96 KHz sample rate without getting a lot of lag/distortion. With that being said, I figured I’d try using a 44.1/48 KHz sample rate with a 32 buffer size at first to reduce any distortion/lag when I’m working on stuff, and convert the project to 96 KHz afterwards, but I can’t do that without all the audio files becoming warped, distorted, or shortened. Is there a way to prevent this from happening, or would I just have to stick with one sample rate or the other to avoid the issues that come with converting between them?
  2. I don’t even own an iPad but now that Logic Pro is coming to it, I’m extra excited to see what they have in store for the Mac version because I imagine a pretty major revamp is coming to that at some point too. Aside from bug fixes, I’m also curious to see what else they include in 10.7.8 if that also drops tomorrow.
  3. This has made me wonder if they’ll announce some type of support for porting regular 3rd-party AU plug-ins to iPadOS at WWDC this year. With how long it has taken some developers just to update their stuff with native Apple silicon support, I have absolutely 0 faith those same 3rd-party plug-in developers will ever develop proper Audio Unit Extensions for iPadOS in a reasonable amount of time to make them useful. Seems fairly reasonable that they’d add support for Apple silicon-native AU plug-ins for Logic outside of the App Store, especially now that they’ve brought Logic to the iPad.
  4. I don’t think it is. This almost certainly seems like a preview for a massive Logic Pro overhaul for the Mac. Even if they’re not going to add a ton of new features, a completely refreshed UI seems to be on the table at the very least. I mean just logically (no pun intended) speaking, I imagine they’ll want to try and have somewhat similar/consistent UIs for it across macOS & iPadOS to make it easier for people to switch back and forth between the two. Obviously the Mac version will have a more advanced feature set, but at least they won’t be so drastically different that it would make switching back and forth between them a pain.
  5. Anyone else feel like this is some kind of a preview for a massive Logic Pro redesign for the Mac as well? I only hope that doesn’t mean the subscription-model doesn’t make its way over either though. I can understand why some smaller developers need to charge a subscription for their software, but I just can’t give one of the most profitable companies in the world a pass for charging a monthly or annual subscription price for this, no matter how cheap it is. It should really be available as a rent-to-own style type product where you can get it for a one-time purchase, or an annual or monthly subscription until you pay off however much it takes to get to the one-time purchase price.
  6. I have tried that with no luck. The plug-ins that seem to be giving me that issue are also passing the AU validation process. Very confusing issue. I also tried reinstalling them as well.
  7. This pop-up has become like a plague now and I have no idea what's causing it. This happens to a bunch of random plug-ins (Native Instruments, Plug-In alliance, etc.) and I don't know why. All but one plug-in I have isn't Apple silicon native yet, but this is happening with the native plug-ins too. I'm running Logic in native mode on macOS 13.3, and all of my plug-ins are up to date with the latest versions. I rescan all audio-units regularly as well. Any ideas of what to look out for or how to fix this?
  8. Ah, okay. Wish there was a setting somewhere that let you keep that portion of the plug-in window collapsed for all plug-ins upon opening. Will have to submit a feature request for that. Thanks David!
  9. Not sure if it's possible to do this but I'd prefer to keep this bar on plug-in windows (highlighted in red) collapsed when they're opened.
  10. @wonshu and @triplets I'm not talking about Logic applying colors based on an algorithm, maybe I explained this badly. All the auto-assign color feature does is something like what I've attached in this screenshot. The problem is I just had to do this manually by selecting the colors from the color palette, and I thought/wished there was a feature that let you do this with just a click of a button with existing tracks. I just think this is pleasing to look at, I know it doesn't add any real functionality and may be confusing to some. I mean they already added 90% of what I'd like it to be, the last 10% would be a button or command that let you color existing tracks like this. If they let you to do automatically it with newly created tracks, they might as well let you do it manually with existing tracks.
  11. @fisherking, not everyone has the same preferences, you know that right? It’s just track color, it doesn’t have to be logical. Some people find it aesthetically pleasing to look at instead of the same two boring colors all throughout a project. If anything, it’s more logical to color your tracks by instrument category like drums and synths because then all you need to do is search for a certain color in a project with a lot of tracks and you can easily find what you’re looking for instead of sifting through track names.
  12. I know it’s not, but if they have automatic coloring for newly created tracks then they might as well let you do it yourself with existing tracks.
  13. Well that’s unfortunate. Surprised it’s not there, seems like a pretty basic feature to have. I’ll submit a feature request for that one.
  14. I know that there is a setting in Logic that allows you to automatically assign "descending" colors when every new track in a project is created, but is there a way to select all the current tracks in a project to assign those descending colors to them without having to go into the color picker to do it manually?
  15. I was really hoping they'd finally implement a native "search-to-select" feature in the plug-in list with this update. That and the ability to change buffer size from the HUD would be absolutely amazing. Gonna have to keep requesting those two until they do it haha.
×
×
  • Create New...