But obviously these plugins are meant for use across all applications that can utilize them.Īlso noted a reported issue with the GoPro Webcam software: I should note I had no intention of using any of these with Resolve. So there's something that probably needs to be written up about this - for now, it makes no sense to install any plugins that aren't written for Apple Silicon.Įrror loading /Library/Audio/Plug-Ins/VST/Addictive Keys.vst/Contents/MacOS/Addictive KeysĮrror loading /Library/Audio/Plug-Ins/VST/DAWCassette.vst/Contents/MacOS/DAWCassetteĮrror loading /Library/Audio/Plug-Ins/VST/FreeAMP.vst/Contents/MacOS/FreeAMP The DR logs indicated that the plugins were reported as "wrong architecture". The plugins themselves work fine, but I wouldn't be surprised if they're causing issues with memory allocation. One thing I noticed was that I had installed a handful of third party plugins for audio (nothing for the Scarlett 2i2 as I don't believe Focusrite has released anything for Apple Silicon yet). I spent a few hours over the weekend trying to see what happened with memory and my use cases, plus trawled through the logs generated by DR. I also have experience in coding with C++, I just gave that whole gig up. Incidentally, I used to do QA and software testing for Oracle's analytics product lines. Using dual monitors, have a Scarlett 2i2 for audio. At the time I was working through the DR training classes, whilst using my Speed Editor. There's definitely something amis, albeit it's not easy to reproduce. The other app I was using at the time was Opera browser, which I seldom close down. I was a bit shocked at the time that this error had popped up, thinking it must have been a mistake. But to displace the posts about using the minimal sized machine, mine is a 16Gb RAM/512GB SSD (with almost 400GB of that space unused). This was using Beta8 at the time, and since it is beta I ignored it until seeing this thread. I wanted to add to this thread the fact that I've also experienced "your System has run out of application memory" as an error message reported by Resolve.Īt the time, I had DR running as a background process, I was doing something else entirely. I've also already advised friends and family to let me (and others) sort through these new M1 machines until they're better resolved, bugs worked out and to hold off purchases until the next gen arrives from an otherwise stellar firm in my experience. I have to say, this is the first time ever I feel burned by Apple Support and frustrated with a troublesome new product. I went ahead and spent $400 more dollars on a 16gb/512gb MBA M1 as Im out of patience. It continues to crash for the same reason so I filed for a return and Im giving it back. This is cause for serious pause.Īs it happens though, Apple won. The main reason I stuck with Apple all this time despite the premium price was exceptional customer service and top notch hardware/software. As a longtime fan who recommends their stuff to all friends and family Im taking a very serious new look at them and their new policies. Um, my 4mo old MBA runs Safari just fine with no such issues. ![]() Apple's response: "well then it seems like you like to keep too many tabs open and should buy an upgraded Mac with more power". I told them I only use Safari, not talking Photoshop or anything heavy and this never happened on an older machine which was supposedly far less powerful. As such, Apple cant help and we recommend returning your machine and buying the more expensive model with more RAM and a larger SSD and seeing if that helps." Thats just your preference and the MacBook isn't broken or defective (even though it crashes all the time). So, the final chapter: I wrapped up with a final call yesterday & the Apple reps response to me (Im paraphrasing), "well this seems just an inconvenience for you & seems you likely need more memory for this issue to not happen or happen less often. Here's a snippet from someone posting on the Apple forums having the same problem using only SAFARI: Maybe memory corruption because of resuming from SLEEP mode with DR not restarted between sleep/wake?Īpparently, this is not a unique issue to DR. ![]() ![]() I restarted DR and now is only using 6.23GB. system has run out of application memory. All working fine until I turned on MOTION BLUR on 1 of 3 comps I'm working on, and that's when MacOS popped up a warning. I'm just playing with some fusion comps on a single timeline, no media. I purchased the MacBook Pro with M1 with minimum specs because I did my research as well and all the experts were saying that memory is handled differently with the M1 systems, which seems to hold true except for this strange bug you describe, which I am having as well. I agree with every point you make, Joe Kelly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |