Virb Edit Mac 3.1.0 Web version out of memory

I am having enormous problems with Virb Edit Mac edition, downloaded from the web, not App Store, running out of memory.

I'm exporting a 7 minute video composed of about 3-4 clips with data overlays and some text overlays.

I'm working on a MacPro 2009 with 24 gigs of RAM, and exporting to a second drive Hardware RAID 0 composed of 3 disks.

I'm working in Mac OS X 10.10.4.

At the present moment, the OS keeps pausing all my apps including Virb due to system out of memory. A look at Virb's memory usage and Activity Monitor reports that Virb is using 74 Gigs of memory with 61.43 Gigs of compressed memory.

At this point, Virb is completely useless as an App if it sucks up all available memory and Swap Space.

Any ideas would be helpful.

Sincerely,

Andrew

0 Wurth over 9 years ago

Is this happening for every video you try to export or just the one?

Can you create separate videos for each clip and export them individually?

Can you make sure you have 'Export transparent PNG sequence for overlays' disabled in the VE application preferences.

Could you look in the system console (Look for 'Console' under Utilities in the Applications folder) for any VirbEdit messages while exporting?

0 andooo over 9 years ago

I'll try out your suggestions hopefully around Wednesday, worked late today and will be working late again tomorrow.

I'll keep you posted.

Thanks,

Andrew

0 sportsnapper over 9 years ago

Me to - though 3.2.0

Been exporting a couple of clips, with the 'Export transparent PNG sequence for overlays' checked, and get the same out of app memory issue.

If I uncheck the PNG sequence box in preferences, then it works OK, and a lot faster!

I get these message in the console log when it errors....

16/09/2015 17:13:41.000 kernel[0]: low swap: suspending pid 69903 (Garmin VIRB Edit)

16/09/2015 17:14:25.000 kernel[0]: low swap: resuming pid 69903 (Garmin VIRB Edit)

16/09/2015 17:14:25.000 kernel[0]: warning: loginwindow(100) performed out-of-band resume on Garmin VIRB Edit(69903)

16/09/2015 17:15:29.000 kernel[0]: low swap: suspending pid 69903 (Garmin VIRB Edit)

16/09/2015 17:15:37.000 kernel[0]: low swap: resuming pid 69903 (Garmin VIRB Edit)

16/09/2015 17:15:37.000 kernel[0]: warning: loginwindow(100) performed out-of-band resume on Garmin VIRB Edit(69903)

16/09/2015 17:15:38.000 kernel[0]: low swap: suspending pid 69903 (Garmin VIRB Edit)

16/09/2015 17:16:02.000 kernel[0]: low swap: resuming pid 69903 (Garmin VIRB Edit)

16/09/2015 17:16:02.000 kernel[0]: warning: loginwindow(100) performed out-of-band resume on Garmin VIRB Edit(69903)

16/09/2015 17:16:04.000 kernel[0]: low swap: suspending pid 69903 (Garmin VIRB Edit)

16/09/2015 17:16:10.000 kernel[0]: low swap: resuming pid 69903 (Garmin VIRB Edit)

16/09/2015 17:16:10.000 kernel[0]: warning: loginwindow(100) performed out-of-band resume on Garmin VIRB Edit(69903)

0 Wurth over 9 years ago

Thanks! We'll look into what's going on with the outputPNGSequence.

0 sportsnapper over 9 years ago

Great.

It's I think it's a great facility being able to output the overlays - then I can merge this with my original footage in Premiere. Even better would be to export just the overlays :)

G

0 NielsDesmo over 9 years ago

Me too!

Running Yosemite on a Mac Pro w/ 18 Gb of Ram I am having the same problem, not believing my own eyes watching the system profiler: A virtual disk on 80 GB+!!! Exporting png sequences is really messing up the memory. After 18000 pngs Virb Edit 3.2.0 went on strike, and after relentlessly relaunching the Finder numerous times I gave up. The video is OK though - 12 minutes. And the pngs are there, but not all of them.
Rewrite, Debug - please.
How about an option for exporting an overlay video as well? - Easy to key on black.

0 geomonster over 9 years ago

Same thing happening to me as well on 3.2.0 but I wasn't exporting any PNGs. VE is agonizingly slow at every step of the way: importing/editing/exporting are all as slow as molasses in Winter.

0 Wurth over 9 years ago

This problem should be resolved in the upcoming 3.3.0 release