If you dont mind the older form factor the M2 Pro 13' might be a good deal. Again, my knowledge is limited.) What is are yalls computer specs for running Logic Pro X smoothly. (Sorry if what I am saying doesnt make sense. Use Live Loops to capture inspiration and quickly build. Use a complete set of Spatial Audio authoring tools that provide everything you need to mix and export your music for Dolby Atmos. I have seen sales here in the USA for the M2 MBP 13' around 1000 and sometimes 1050 for a base model. I am not very good with computers, so I am currently trying to figure out what I should upgrade in order for my laptop to successfully run Logic Pro X without it giving system errors. Logic Pro includes a massive collection of instruments, effects, loops and samples, providing a complete toolkit to create amazing-sounding music. 1 With a 40 percent faster Neural Engine to accelerate machine learning tasks and 50 percent more memory bandwidth, M2 brings astonishing performance and new capabilities to iPad Pro. They will most likely all be way over 1,000. The M2 chip is the next generation of Apple silicon, with an 8core CPU that delivers up to 15 percent faster performance and a 10core GPU that provides up to 35 percent faster graphics performance. APPLE 2021 Macbook Pro M1 Pro - (16 GB/1 TB SSD/Mac OS Monterey), Rs 243990. I noticed this a few days ago when my boss finished a Logic Project and the file size was about 700 MB, compared to 20 MB for the other ones he worked on. So waiting a month to see if the new MBP M2 versions come out seems a bit futile. This multi-touch-enabled strip of glass changes. It appears irrelevant if there is any audio in the project at all. My MacBook Pro Retina 15-inch from late 2013 has a 2.6 GHz i7 processor, 16GB of memory, and a 1 TB hard drive. I have "Auto Backup" set to "Last Alternative Version". The current suggested minimum for Logic Pro X is 4 GB. File -> Project Management -> Clean Up -> Delete Backups will reduce the file size back down to its 'normal' size I have not tested this against "adding" tracks, etc etc. So if I have a 50 MB LPX Project, duplicating a track will, on average (this is all just from watching file sizes) add about 50 MB to the project. Duplicating a Software Instrument track (not sure if this applies to audio tracks) increases the file size by ABOUT double it's starting size. This is very early in my troubleshooting process but its a start: Here's the info I've gathered so far (Its hard to tell if this is a 'bug' or what exactly is going on). I've started noticing the same issue, which presents a very annoying problem for my workplace, where we have multiple identical rigs including a remote rig, and these quickly escalating project sizes are becoming a problem when transferring with lots of files on a daily basis.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |