02-23-2019 10:49 AM
Not sure if this will be a possible workaround for Fusion Studio users, but I had trouble with rendering at 5.2k Cineform. What was happening for me was memory usage would skyrocket past 90% and would close the program without any warning to prevent the system from completely locking up/crashing. I did research on the forums and didn't find anything useful
My system has 16GB of RAM... saving with H.264 I had no issues, ProRes was so-so for usage, but Cineform would use nearly 60-75% of total memory available, an absolute ridiculous amount. My main workaround was to close other programs to get my total memory usage to below 30% for my system BEFORE lauching Fusion Studio. Once I would begin the rendering process with Cineform, it would gradually climb to around 80% total usage, then it would finally level off and hang around 80-90% total usage and was successfully running, without crashing.
My advice for other users... try closing other programs that you're not currently using and monitor your memory usage with Task Manager. You could possibly adjust your Paging File Size (Advanced System Properties --> Performance Options --> Advanced --> Virtual Memory), but I didn't do this step as with SSDs is not reccommended as will deteriorate number of writes more rapidly.
I don't know why something like this would be happening... poor software coding is all I can guess. That's all the advice I can give on this that worked for me, but good luck.
My system specs: Windows 10, Intel Core i7 2600k, Nvidia GTX980, 16 GB RAM, SSDs, ASUS P67 Sabertooth Mobo
03-08-2019 07:29 AM
Another work around is to swap from 360 audio to normal stereo, there won't be a memory leak this way but you will loose the directional audio which is a big no no for me, so I usually just use H.264, if it's CineForm for editing purposes then I have to babysit the process.
05-12-2019 11:16 AM
I am having this exact issue. I had submitted this as a big to GoPro and it has not been corrected. I have also tested the new Fusion 2.0 beta software and the problem still exists.
I wish this would be corrected.
05-12-2019 11:40 AM
I just found a weird workaround. So it appears that our computers are running faster than the program is calculating for. It we can slow down the speed at which it converts, it should be possible to keep the memory under control. If not, it keeps increasing until it maxes out. What I have done it limit the amount of cores it is using to slow down the conversion and keep the memory growth in check.
Before starting the conversion process, open the task manager and do the following (Your fusion software must be open to do this):
1. Find the GoPro Fusion Process on the Processes tab and right click on the process. Click the go to details.
2. Choosing this option will take you to the details tab where you you should see the program's .exe running. You'll right click on this and choose set affinity to select how many processsors you want this program to use.
3. I selected 2 as any more makes my memory creep up too fast and crash the program. It worked perfectly and videos converted just fine. To be honest, I don't know why but I didn't notice the conversion process taking signifigantly longer.
Hope this works as well on your computers as it did on mine. Keep adjusting how many CPUs to find the perfect mix.
05-19-2019 01:51 PM
This did it for me. I have a more than capable computer, overclocked i7-6700k, 24GB of RAM and an RTX 2080, however when I tried to render video with the default settings (5.2k, Cinneform '422 high' etc) It would keep consuming more and more memory and finaly crash around 15-20%. I was already researching alternative cameras when I came across your post. Setting the affinity to 3 processors does the trick. It never goes above 11GB of Ram. Granted, it's going to take a bit longer, but I guess I can live with that.
Thank you! You've saved me returning this camera.
05-19-2019 02:06 PM
With some experimentation, I've realized That I can select all 7 of my other processors, and just leave 'CPU 0' unchecked, and it works just fine. If I leave CPU 0 checked, it crashes at 15-17% every time. Strange.
a month ago