Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
|
|
Thread Tools | Search this Thread | Display Modes |
31st May 2020, 13:32 | #21 | Link | |
RipBot264 author
Join Date: May 2006
Location: Poland
Posts: 7,815
|
Quote:
https://www.mediafire.com/file/hdpef...Tester.7z/file
__________________
Windows 7 Image Updater - SkyLake\KabyLake\CoffeLake\Ryzen Threadripper |
|
23rd August 2020, 13:51 | #24 | Link |
Professional Code Monkey
Join Date: Jun 2003
Location: Kinnarps Chair
Posts: 2,555
|
Bug report: you're more or less thread bombing systems with many cores
I didn't look at the internals but you seem to spawn one ffmpeg instance and effectively one ffvideosource instance per thread in system (I know you can limit the decoding threads in the script but that's not the default). Both ffmpeg and ffvideosource will in turn spawn as many threads as are available each. So if you have a system with 32 threads you get 32 * (32 + 32) threads and probably 32 more for the linear decoding. ~2080 threads! Or ~1000 threads if you do single threaded decoding. You see the problem and accidental ways to make it worse. Solution: Add a configurable number of threads and make it a template variable too. For example 4 threads would be a sane default. Note that the number of threads may affect the decoding result so having it as an explicit option is generally good. Also change the number of instances depending on the number of threads selected. For example if both ffmpeg and ffms2 uses 4 threads then only spawn system threads/4 instances to keep things sane. Drag and drop would also be nice.
__________________
VapourSynth - proving that scripting languages and video processing isn't dead yet Last edited by Myrsloik; 23rd August 2020 at 14:00. |
6th November 2020, 23:11 | #26 | Link |
RipBot264 author
Join Date: May 2006
Location: Poland
Posts: 7,815
|
Double click on script error message
__________________
Windows 7 Image Updater - SkyLake\KabyLake\CoffeLake\Ryzen Threadripper |
18th November 2020, 21:20 | #28 | Link |
Registered User
Join Date: Dec 2005
Location: Germany
Posts: 1,795
|
Idk what I'm doing wrong. Extracted 7z. set path of ffms2.dll, clicked on save.
Win10 x64, Avisynth x64 3.6.1 (r3300)
__________________
AVSRepoGUI // VSRepoGUI - Package Manager for AviSynth // VapourSynth VapourSynth Portable FATPACK || VapourSynth Database |
19th November 2020, 01:55 | #30 | Link |
RipBot264 author
Join Date: May 2006
Location: Poland
Posts: 7,815
|
Personally I'm still using avisynth+ 3.4 x64. Perhaps your newer version 3.6.1 does not recognize framecount argument?
__________________
Windows 7 Image Updater - SkyLake\KabyLake\CoffeLake\Ryzen Threadripper |
19th November 2020, 03:53 | #31 | Link |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
there was bug in AviSynth+ 3.6 that was fixed in AviSynth+ 3.6.2-test2, you can try AviSynth+ 3.6.2-test4
__________________
See My Avisynth Stuff |
19th November 2020, 09:12 | #33 | Link |
Registered User
Join Date: Dec 2005
Location: Germany
Posts: 1,795
|
Yep 3.6.2-4 fixes it.
__________________
AVSRepoGUI // VSRepoGUI - Package Manager for AviSynth // VapourSynth VapourSynth Portable FATPACK || VapourSynth Database |
Thread Tools | Search this Thread |
Display Modes | |
|
|