11-18-2018 12:24 AM
does anybody have the same problem?
Using a memory monitor program while rendering with version 1.3, I see the memory (16Gb) fills up and causes the computer to 'crash' (infact it just goes so slow you think it has crashed) if the render is set to 360 Audio 4 or 5.2k video. Lower resolution and 360 Audio rendering and the memory stays about half full as it does with 4 and 5.2K with Stereo audio. This was with a 3 minute video. with the earlier version of the program (1.1) the memory did not fill up to overflowing. I have the original problem entered in another post on here but this is the latest full findings.
11-22-2018 11:31 AM
Yep this is also happening to me. I also made a thread about it but it seems to have mysteriously disappeared (although I was really jetlagged and may not have posted it correctly).
Made 5 or 6 movies in a batch the day before flawlessly with version 1.2, all over 20gb (my system has 16gb memory). Tried with one the next day after updating versions and now the memory fills to 16gb and then the program crashes/exits.\
Have not seen anyone post a solution. A gopro rep said previously they either can not or don't have the previous version to offer, but suggested that we try to find another user with the install file.
11-22-2018 02:56 PM - edited 11-22-2018 02:58 PM
Here is my solution Change the codec used. Change from the CineForm '422 High' which seems to be the one the program selects, to ProRes 422 the memory does not fill up and I can render the video at 5.2Kresolution and 360 Audio.