VSE proxies #45870

New Issue

Maxime · 2015-08-22T17:21:37+02:00

Maxime commented

2015-08-22 17:21:37 +02:00

To generate multiple proxies in a batch way, one is to add the video files in the VSE then one selects all the video files then generates proxies in the side panel. In the VSE, add movie then select the files you want to generate proxies from then add movie strip will import video files in the VSE as strips.
When doing so with a large amount of files (superior to 30), blender crashes. When reducing the amount of files to around 10 to 20 files, it will work but the following happens: after selecting the file then clicking on "add movie strip", blender freezes for about 30 secondes to a minute. Once in the VSE, after selecting the video strips and asking blender to generate proxies, blender will freeze once again (not responding on top) and eventually will unfreeze after a minute or so and start generating proxies. The more files are added, the longer the wait (several minutes). Depending on the computer, adding more than 20 to 30 files at once in the VSE will generate a crash.

This bug has been noticed on several windows 7 and windows 8 computers (desktops and laptops) with 8 GB of ram.
Video files imported were 4K mp4 files (H265) from a samsung NX1 (samples available online)
Occasionnaly windows will display a window saying that there is not enough memory on the computer and will suggest to close all programs. Task manager shows use of 7,25 Gb of memory out of 8 gb, cpu used at 100% during the proxy building.

To generate multiple proxies in a batch way, one is to add the video files in the VSE then one selects all the video files then generates proxies in the side panel. In the VSE, add movie then select the files you want to generate proxies from then add movie strip will import video files in the VSE as strips. When doing so with a large amount of files (superior to 30), blender crashes. When reducing the amount of files to around 10 to 20 files, it will work but the following happens: after selecting the file then clicking on "add movie strip", blender freezes for about 30 secondes to a minute. Once in the VSE, after selecting the video strips and asking blender to generate proxies, blender will freeze once again (not responding on top) and eventually will unfreeze after a minute or so and start generating proxies. The more files are added, the longer the wait (several minutes). Depending on the computer, adding more than 20 to 30 files at once in the VSE will generate a crash. This bug has been noticed on several windows 7 and windows 8 computers (desktops and laptops) with 8 GB of ram. Video files imported were 4K mp4 files (H265) from a samsung NX1 (samples available online) Occasionnaly windows will display a window saying that there is not enough memory on the computer and will suggest to close all programs. Task manager shows use of 7,25 Gb of memory out of 8 gb, cpu used at 100% during the proxy building.

Maxime commented

2015-08-22 17:21:37 +02:00

Changed status to: 'Open'

Maxime commented

2015-08-22 17:21:37 +02:00

Added subscriber: @spaceman

Aaron Carlisle commented

2015-08-22 18:15:13 +02:00

Added subscriber: @Blendify

Sergey Sharybin commented

2015-08-24 10:47:07 +02:00

Added subscriber: @Sergey

Sergey Sharybin commented

2015-08-24 10:47:08 +02:00

Please follow report bug guidelines and provide:

Exact version of blender you're using
Sample .blend file and files needed to reproduce the issue

Please follow report bug guidelines and provide: - Exact version of blender you're using - Sample .blend file and files needed to reproduce the issue

Maxime commented

2015-08-24 11:51:17 +02:00

This bug occurs on version 2.74 and 2.75a windows and mac versions.

Sample images in 4k:
http://www.imaging-resource.com/PRODS/samsung-nx1/FULLRES/yvid_SAM_0164-C4K_Sample2.MP4
http://www.imaging-resource.com/news/2014/11/19/samsung-nx1-4k-video-samples-and-new-full-res-frame-grabs-available-for-do
multiplying file sample2.mp4 by 200 in a folder will reproduce the issue.

Importing the mp4 files in the vse in a new scene will reproduce the issue so I guess a sample .blend file would not be of any help but I'm happy to provide one if needed! :)

This bug occurs on version 2.74 and 2.75a windows and mac versions. Sample images in 4k: http://www.imaging-resource.com/PRODS/samsung-nx1/FULLRES/yvid_SAM_0164-C4K_Sample2.MP4 http://www.imaging-resource.com/news/2014/11/19/samsung-nx1-4k-video-samples-and-new-full-res-frame-grabs-available-for-do multiplying file sample2.mp4 by 200 in a folder will reproduce the issue. Importing the mp4 files in the vse in a new scene will reproduce the issue so I guess a sample .blend file would not be of any help but I'm happy to provide one if needed! :)

Sergey Sharybin commented

2015-08-28 15:28:21 +02:00

Changed status from 'Open' to: 'Archived'

Sergey Sharybin closed this issue

2015-08-28 15:28:21 +02:00

Sergey Sharybin self-assigned this 2015-08-28 15:28:21 +02:00

Sergey Sharybin commented

2015-08-28 15:28:21 +02:00

Added subscriber: @Psy-Fi

Sergey Sharybin commented

2015-08-28 15:28:21 +02:00

Sample images gives like 403 error, however looked into more details about timing/memory with 2K movie here.

The reason of initial delay is because there's some non-thread-safe code happening before re-encoding process, starting all the FFmpeg contexts and so. Depending on container/codec it could take more time or less.

As for memory usage -- currently contexts for all selected strips are being created.

Surely it could all become more lazily initialized and so, but it adds some extra tread safety issues and technically such an improvements does not belong to bug tracking process.

So thanks for the report, but closing as a TODO.

P.S. @Psy-Fi might be interested in looking into improving this system one day.

Sample images gives like 403 error, however looked into more details about timing/memory with 2K movie here. The reason of initial delay is because there's some non-thread-safe code happening before re-encoding process, starting all the FFmpeg contexts and so. Depending on container/codec it could take more time or less. As for memory usage -- currently contexts for all selected strips are being created. Surely it could all become more lazily initialized and so, but it adds some extra tread safety issues and technically such an improvements does not belong to bug tracking process. So thanks for the report, but closing as a TODO. P.S. @Psy-Fi might be interested in looking into improving this system one day.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

VSE proxies #45870