06-01-2016 09:10 AM
Hey ! I have a problem,
When I export my video without flux, it work but the short slowmo part of the edit isn't fluid.
When I export w/ flux, it doesn't work and the export fail at 40% (each time) .
My clip is entierly in 48fps, 1080p Superview.
I export it in mp4 48fps, fullhd 25mbp
Sorry for the bad english I'm a frenchie
06-05-2016 06:19 PM
Same here. They should invest sometime improving the stabilty of their software. It's really frustrating.
Please at least run some static code analysers in your code. It has been years that the last time I saw a so low quality product.
06-05-2016 06:49 PM - edited 06-05-2016 06:50 PM
Sorry to hear about that @Anonymous @Anonymous, @Anonymous.
GoPro states before using Flux this can only be used for 5 second parts or this could happen.
It takes a lot of processing power to do this, and lots of users don't have it so then the software will crash.
Also you might want to get the latest GoPro Studio, and GoPro App for Desktop.
@Anonymous you did say GoPro needs to fix this GoPro has a new team now on the jib fixing everything, and allowing really cool
upcoming updates to edit your videos for you. You can read more here: https://community.gopro.com/t5/Support-Hub-Suggestions/What-s-Upcoming-For-GoPro/m-p/9490
06-05-2016 06:54 PM
BTW, I'm using a GoPro template where the greatest cut is 4 seconds.
My computer is a desktop i7 with 8Gb of RAM. I believe it is enough for editing a 2min video.
I'm using GoPro Studio version 18.104.22.1684
06-05-2016 07:00 PM
Thanks for your reply @Anonymous.
Alright so right off the bat you do have the specs to do so.
I would get the new update its now V 1.8: http://shop.gopro.com/softwareandapp/gopro-app-%7C-desktop/GoPro-Desktop-App.html
If that doesn't work, then well trouble shoot more.
06-05-2016 07:27 PM
Thanks Chris here's hoping.
Im not sure why 5 seconds would be a limit, and it's never been one in the past. Doesnt seem relevant to my system.
The software or computer is not like a muscle doing a weight lift, it doesn't "get tired" ha ha!
I am not fluxxing a lot of clips, but maybe 60 seconds worth, out of a 10 minute overall project.
The machine is a high end i7, 32gb ram, triple SSD's, a decent quadro, all latest drivers, firmwares ... windows 10x64bit.
The machine is definitely not getting exhausted (and if it were, that would really just mean it's doing its job)
infact, the contrary is true when flux is running ... my CPU, ram, disk io and gpu loads all hover around 25-40% ... it's not really even utilising the power of the machine. Other non-flux sections of the project the CPU's do ramp up to almost 100% (disk IO gets busy, but never too busy... strong SSD's can cope).
Sometimes i can get the whole project sorted, other times it crashes within 5 seconds. Totally arbitrary, it always has been. Different DLL's, at different times over the last 2 years, but roughly the same issue... flux.
I know there's lots of blame toward other system components, but really it's up to the software to stop being so sensitive and prone to injury. My Adobe premiere, lightroom, CS6, handbrake, Camtasia etc all run OK.
I did have a sneaking suspcicion that the security camera software I am using might be involved, so i shut it down whilst running my exports in GOprostudio ... and got through an export. Either way, again, the code should be written in a way to tolerate "whatever" that conflict is ... and besires, the DLL in question is gopro's own, so i dont even understand the correlation.
I love gopro's, just wish the software was more robust ... and i know i'm not alone.
06-05-2016 08:13 PM
That's awesome @Anonymous.
So now youv'e said your on Windows 10, and this makes me think more that this is a common issue right now.
GoPro has been having lots of issue with Windows 10.
Also the GoPro team is having some really cool upcoming software for editing I think you'll like if you want to read more on that.