It's the kind of software experience you get from some guy who forked open source code and is writing his first program.Īnd guess what? This happened also on my 2017 13" macbook pro as well! That one was running Mojave latest. This is *not* a "pro application" experience. But somehow a memory leak develops and crashes the interface and eventually you get this out of memory error and I have to force close Compressor every single time. So it seems that the actual process keeps running to completion in the background even though the front-end has crashed. Once GPU activity ceases, I check if I can open the file and if it plays, that means it finished the encode task. The only way I get a finished encode is by using the GPU monitor to tell when iGPU activity ceases. About, oh 15-20 minutes into an encode that takes about an hour I get the spinning beach ball. But it happens with ProRes encodes and H.264 encodes as well. Most encodes are HEVC, 8-bit color, fast profile. That is a big problem - because all of my videos are in the 40 minute to 2 hour range. This happens with every single encode that I do that is over a few minutes in length. It is not an overheating issue - I am monitoring CPU & GPU temps. On a brand spanking new 2019 16" macbook pro with an 8-core i9. The other answer can be helpful - but how does that help me?.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |