mwk

I’m one of those who has followed the belief of “the more RAM the better”, but I’ve had to readjust my thinking with the M1. I’ve got one Mini with 32GB and one with 64GB. While I don’t think an M1 Mini at 16GB is high on my list at the moment (my 2018s are working fine), I’ll certainly be paying attention to what “unified memory” means in actual practice. Good article here about the RAM in general... https://www.macworld.com/article/3597569/with-m1-macs-memory-isnt-what-it-used-to-be.html

Mac Pro, perhaps? Don’t know... not in my price range so I haven’t examined it that closely. Didn’t mean to make it sound like any Mac is easily upgradeable or that upgradability should play into the OP’s decision, though. Just mourning the specific loss of a Mini having that option with the HD and the RAM. I think you can still get to the RAM, but it’s not made easy. A step back from the prior model where RAM was right there when you opened the Mini.

I’m using a Mac Mini 2018 with Catalina. I’ve got 64GB and running three monitors (two 27” and one 23”), and three of the SanDisk 2TB SSD connected. Just started using Spitfire products, the BBCSO in particular. (The cheap version... the $1,000 edition will have to come later.) I’m on Logic 10.4.8. I intensely dislike the lack of easy upgradability with the current Mini compared to earlier models, but there’s nothing I can do about that. Other than that, the system runs pretty slick. I haven’t done any music work that would really stress the system, though. Generally speaking, it can get hot at times, but not too bad. I have a laptop cooler underneath in the belief that it helps a bit. I don’t have a ton of plug-ins so I don’t know how that might affect performance. Good luck with whatever move you make. A new system is both exciting and stressful.

software is always a work in progress; the point is, this update happened reasonably quickly, and brings a lot of fixes. and, down the line, there will be another update... then another. apple didn't release a bad version of logic, it released it's latest version. etc etc etc etc same as it ever was. I remember so clearly a meeting after I had started at Microsoft. We were getting close to releasing one of the Windows operating systems, but I had full access to the bug database and knew how many bugs still existed. I expressed my shock that we would release an OS with so many open bugs. How could we?!?!? I actually thought you didn’t release software until there were zero open bug reports. After rolling their eyes at how naive I was, they calmly explained that, for various reasons, “perfect” software of this magnitude was pretty much impossible. It didn’t take long for me to see, first hand, just how complex software development is at that level, and the process involved in deciding when to release something.

On the one hand, I’m happy I didn’t miss something right under my nose. On the other, it’s disappointing (for me, at least) that the option isn't available. But at least I know now. Thanks.

I’m, perhaps, misunderstanding what Automation means in Logic because I’m not quite zeroing in on this issue: I’m got a track that has 60 short regions on it. I want to apply values for Fade In (200), Curve (99), and Fade Out (200) to each region on the track. Currently, I can easily select the track (which selects all regions on the track) and make the changes so each region is altered at once. But I was wondering if there’s some automation where I can select all (or a combination of) tracks and with a one button (or shortcut key) apply these values that I’ve setup beforehand. It would be a nice time-saver when I’m doing this a lot in my work. Searching for “automation” with Logic on the web and I’m getting other types of automation that’s not exactly what I’m looking for. So the goal is to select a track (which selects all region on the track), or select a group of regions, then click a single button (or use a shortcut key) to automatically apply pre-chosen Fade In, Curve, and Fade Out values for those regions. Am I missing something simple, or is it not possible? Thanks.

Thanks for the math lesson! This continues to be an adventure for me. I never know with someone new if we’re speaking exactly the same language when it comes to specs. And as Eriksimon points out, there can be different ways to say something in this case. The latest from the potential client is that he ultimately needs it one of the following formats: WAV mono 8Khz 64kbps WAV mono 16Khz 128kbps SLN 8 khz format SLN 16 khz format I think at this point he’s going to do the conversion. I’ve asked him what he uses to get the file he needs and hopefully he’ll answer as it might tip me off in terms of getting us on the same page. Anyway, thanks for all the input and links that have been shared. I really do appreciate it!

> That makes no sense, kbps doesn't apply to wav files, only to compressed formats like mp3. That’s what I thought, but didn’t know if the client mis-spoke, or there was something I simply didn’t know. So I told him that the other two aspects were easily done and if he wanted to tell me how he typically did the third, I’d be happy to do it. Or if he found someone else who already knew, I understood if he went with that person. Haven’t heard back so an assumption might be possible. > There's quite a good rundown to create audio for crappy but standard telephone systems here: I appreciated that. This is new for me and I found that link very helpful.

Thanks! I’ll take a look.

I have a potential client who wants some on-hold messaging and liked my audition. However, his request (if we move forward) is, “WAV mono 8Khz 64kbps”. Most of my VO work is simple export of a WAV and then convert to MP3. For the life of me, I don’t see options in Audio to get that kind of result. I did a search here and the closest I found was dropping into QuickTime and exporting, but I don’t see those options there. (Version 10.5) Am I missing something simple or is this not possible in Logic? And if not, is there a third-party solution that gives me that option? I use MP3 Encoder but unfortunately, and not surprising because of the name, it will only give me an MP3. Thanks for any help/advice... or pointing out that this option was right under my nose.

I can see the value of both methods. My hope was that switching to a Folder method would eliminate the package file which is what I’m guessing is getting somewhat corrupted from time to time with this version of Logic. And only corrupted in the sense that I can’t open the package file in Logic. I can still open the package in Finder and pull out the audio files. It seems like removing DisplayStateArchive and/or ProjectData from the package allows the package file to open again in Logic, but without any of the audio regions (which are also still in the package file.) I located an earlier version of Logic on my daughter’s computer and will try to run that. I was unaware of that whole idea of keeping earlier versions on hand since this is the first time I’ve experienced a serious problem with Logic. Now I’m happy that I’ve been really lazy in keeping my daughter’s computer updated. But thanks everyone for the input on the Folder vs Package discussion!

OK, got it. Thanks.

I just saw 'saving as a folder' in another thread, and rather than hijack that thread, I found this one to ask a follow-up (apparently 5 years later.) Recently, I’ve been having occasional projects that start to slow down a bit as I move audio regions around. New computer with latest OS and Logic, so with 32 GB, it’s not a memory or space issue, and it’s just a few regions. If I close the project, I can’t reopen it. It tries to load, but I get the spinning beach ball and if I don’t force-quit Logic, it’ll spin forever. That same file can’t be opened on another computer (also latest OS and Logic). I’d love to find a solution to that problem and in researching it, I stumbled across the idea of saving as a Folder vs. a Package. But I need some clarification on what that’s really doing. When I save as a Folder, I still get the typical .logicx package file along with a separate Audio Files folder. So what am I gaining in having that separate Audio Files Folder? Is that only useful as a backup if the .logicx file can’t be opened? My hope was that saving as a Folder would take things out of the .logicx wrapper because my theory is that it’s this version of Logic that is corrupting some file within the package and preventing me from opening it. But if saving as a Folder still creates a .logicx wrapper, I’m not sure that’s going to solve my particular problem. At least I will have learned the value between Folder and Package.

I switched to a Mini earlier this year and haven’t regretted it. I use Logic for voiceover, so it’s rare I’m pushing the limits of a what a Mini or Logic can do. I’m actually planning on getting a second Mini for my non-VO work, but I’m waiting to see if there’s a refresh when the new OS is released in the fall. (So a rumor to that effect.) I’ve encountered a particular problem twice and I don’t know if it’s the Mini, Logic, the OS or a combination. A couple of weeks ago, I experienced a dramatic slow-down using Logic on the Mini. There was only one or two tracks, but things slowed to a crawl. I figured I’d save, close Logic and reopen to clear up any possible memory issue. But I couldn’t reopen the Logic file. I just got the spinning beach ball. I tried to open it on another computer, but had the same problem. It’s like the Logic file was corrupted. Then this happened again with a file I had created some time back. I’ve got the latest OS and Logic installed and don’t have have a clue where the problem might be... one of those, both, something else entirely? It’s only happened those two times. Otherwise, no issues. I’m slightly spooked because in the first instance I had to re-record some work. If that had been a large project, I would have been in a world of hurt. Didn’t know at that time that I could get into the contents of the Logic file and pull whatever audio was in there. By deleting a couple of files in the package (I forget which ones) I was able to reopen the Logic file, but the audio files weren’t in place. Now, after I finish a track, I immediately export instead of exporting all my files at the end... just in case. Despite that, I’m actually still really high on the Mini. It’s perfect for me and I don’t really believe the Mini is the cause of my two issues. But that’s just a guess. When you’re swapping out a computer, moving to the latest OS, upgrading to the latest Logic, and throwing in a new interface, it’s hard to know where the problem is. Other than those two file issues, the Mini has been a joy. (It’s my first computer with an SSD... world of difference right there.)

Thanks. That’s certainly... pricey. I have to get out of a mindset that others here have broken. I’ve got too many years thinking external drives are only for backing up and not working off of as part of a daily workflow. Probably need to shake that view that everything needs to be on your internal drive.