Comments

browj2 wrote on 12/09/2017, 05:19

Hi Peter,

I don't have the material to test this out the same way and since I am still out camping, I only have my Surface Pro 4 with 8GB RAM and using the latest patch that came out on Monday for VPX.

I put 640 photos into a folder taken using 3 cameras - DSLR, and cell phones BB and iPhone, with resolutions of 5184x3456 (3:2 but is supposed to be 16:9), 3264x1836 (16:9), 4032x3024 (4:3).

I dragged all onto the timeline. For the record, here is the message that pops up:

I had never tried importing in bulk before, so this was new to me. It creates a nested sequence, which I have used before.

Then I exported the main movie, the one with the nested sequence. It started fine albeit slow with 90-100 CPU usage. At about 35-40% I was getting low CPU usage, but 100% memory and disk drive usage. Then I got the request to close some programs, VPX. I didn't. Then got a memory overload error message, the project did an auto-save, then I clicked the error message off and VPX crashed.

I did not follow your instruction about not playing back the movie. I did it once, then deleted everything, including the second movie, then without closing and reopening VPX, I re-imported the 640 photos, then exported.

Did you export the nested sequence movie, or the one with the photos?

Edit: I just tried exporting the movie with the images and it went to 11s of the 21s movie before crashing.

Re-Edit: Strange, my DSLR is supposed to be set up for 16:9 but the images came in a 3:2 and the movie changed to 3:2, but the main movie with the nested sequence stayed at 16:9.

I exported the images movie as a movie, not to Magix format and imported the movie into a new project. It automatically switched to 3:2 but I changed it to 16:9 NTSC, then exported to mxv and it worked.

Last changed by browj2 on 12/09/2017, 05:53, changed a total of 3 times.

John C.B.

Desktop System - Windows 10 Home 1903; 16Gb RAM; i7 CPU 860@2.80Gz; ATI Radeon HD5770 w1GB; SSD 500GB, HD 2TB; others 1.5TB, 3TB, 500GB, 4TB, 5TB, 6TB; dual monitors - 27" main, 25" secondary; Casio WK-225 piano keyboard; M-Audio M-Track USB mixer; Notebook - Microsoft Surface Pro 4, i5, 8 GB RAM, 256 SSD, W10 Pro 1903

Scenestealer wrote on 12/09/2017, 07:14

Hi John

Thanks for testing.

Looks like you have found what I found when exporting via the nested movie after following the VPX prompts.

As I implied in my second paragraph, I could only avoid crashing during export by importing all the still images into the timeline instead of letting VPX create a nested sequence. Even then it just completed by the skin of it's teeth, with maxed out RAM (15GB odd) and some heavy paging to the SSD Page file. The problem seems to be that using the second movie and main movie sequence route, the program can not release, or release fast enough, the memory to the disk Page file (SSD or not).

I have found a Program Setting that stops the gobbling up of the available RAM during preview but unfortunately not export, ie. Video/Audio Tab > Other > tick "Reduce resolution for Preview (increased performance)" . I suggest this scenario is just what that setting is there to help (and is not the same as reducing the resolution with the Lightning Bolt).

Peter

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 1903, MEP2016, 2020 Premium and prior, VPX7, VPX11. Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 1903, MEP2015 Premium.

johnebaker wrote on 12/09/2017, 10:49

Hi

I have tested this, not having hires images I used 2900 1920 x 1080 images (4 hour time lapse sequence).

VPX loaded all images and created the nested sequence - combined video? - no crashing, CPU 62-63 %, RAM (16GB) usage 31 - 32%.

Exported to MP4 with HWA (Intel HD4600) same resolution 1920 x 1080 - CPU 30-31%, RAM maxed out at 91%, C: drive maxed out at 100%.

I did find the VPX slowed down considerably during export from a rate of approx 50 frames per sec to 6 fps.

Looking at the performance monitor I found the 'offending' service was Memory Compression - a new feature introduced with Windows 10 to speed up paging, reducing page faults by compressing/decompressing data to/from the page file.

@browj2

Did you notice or monitor the processor for slowing down due to the thermal management lowering the clock speed to keep the processor within limits?

HTH

John EB

 

Last changed by johnebaker on 12/09/2017, 10:49, changed a total of 1 times.

Lateral thinking can get things done!

VPX, MEP Premium, MEP 2016, and earlier versions, Music Maker Premium, Music Maker 2016, 2015.

Running Windows 10 64bit on Intel i7-8700K 3.2 GHz, 16Gb RAM, 1Tb + 2 x 2Tb internal HDD + 60Gb internal SSD, + 6 x 2Tb ext HDDs, Sony FDR-AX53 Video camera, Contour HD 1080 and Sony HDR-AS30V Sports cams.

browj2 wrote on 12/09/2017, 15:23

@johnebaker

The export process did slow down to a crawl, about 1 fps., but I did not monitor the processor for slowing down due to thermal management....

 

John C.B.

Desktop System - Windows 10 Home 1903; 16Gb RAM; i7 CPU 860@2.80Gz; ATI Radeon HD5770 w1GB; SSD 500GB, HD 2TB; others 1.5TB, 3TB, 500GB, 4TB, 5TB, 6TB; dual monitors - 27" main, 25" secondary; Casio WK-225 piano keyboard; M-Audio M-Track USB mixer; Notebook - Microsoft Surface Pro 4, i5, 8 GB RAM, 256 SSD, W10 Pro 1903

Scenestealer wrote on 13/09/2017, 02:13

Hi John EB

Looking at the performance monitor I found the 'offending' service was Memory Compression - a new feature introduced with Windows 10 to speed up paging, reducing page faults by compressing/decompressing data to/from the page file.

Interesting that John - I could see that band in the graphic of the memory tab in TM if you hover the mouse over it it says something about compression. This band grows then suddenly shrinks during export and I assume it may be corresponding to the memory being compressed before being paged out to virtual.

Thanks for your tests but I think the key is the Hi resolution of the images is creating problems. Actually I read something in the FAQ's at Magix support2 some time ago that they recommend resizing stills to the Res. of your project before importing to "Improve performance".

Using the nested movie method do you see the extreme cumulative increase in RAM usage if you play the same section several times? ( presuming you do not have the "Reduced resolution for preview" selected in Program Settings>Video Audio tab that I mentioned above).

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 1903, MEP2016, 2020 Premium and prior, VPX7, VPX11. Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 1903, MEP2015 Premium.