Forum

Forum



SearchSearch   Users   Registration   Entrance
Today: 04.02.2026 - 00:45:57
Pages:  1  

More than ~10 clips is a memory buster?

MessageAuthor

I was attempting to automate splicing of 40-50 short clips, with transitions, various subtitle effects, etc. Finally got script to work as desired using 3-4 test clips, but when trying 40-50 clips (or even just 15) it results in memory errors when loading into MeGUI or VDub. I didnt realize that it would open two(2) Haiaii Splitters (not sure why two) and a Fdshow Video decoder for each of the 40-50 short 1080p clips. Anyway, I am dumb(founded) and would be very grateful for any help pointing me in the direction of some solution to get around the memory issues. Is there a method to process the clips that doesnt load into RAM (speed is not an issue)? or any potential solution would be much appreciated!!!! Here is an shortened version of the script: Code:




J-Dawg

user


Statistics:
Messages: 310
Registration: 03.24.2001
16.02.24 - 11:38:12
Message # 1
RE: More than ~10 clips is a memory buster?

I suspect most of the memory is used by the repeated calls to Overlay(). As a first step in the investigation, try using () instead. You will have to convert your clips to RGB32 if they are not already in this format.


---------------
#17 M42 CLUB

joeytomato

user


Statistics:
Messages: 173
Registration: 08.23.2001
16.02.24 - 11:46:07
Message # 2
RE: More than ~10 clips is a memory buster?

Thank you Gavino for your reply.. you are clearly a scholar and a gentleman. I changed Overlay to Layer (/w convertoRGB32) as you suggested but unfortunately the scripts result in the same memory errors when using 10+ video clips and loading into virtualdub. Code:




///Manuel

user


Statistics:
Messages: 97
Registration: 08.14.2001
16.02.24 - 11:53:53
Message # 3
RE: More than ~10 clips is a memory buster?

In a furthur effort to narrow down things, I have basically removed everything from the script (no plugins, no subtitles,no function,animate) - leaving basically just converting all clips to the same framesize, framerate, audiorate and then splicing using dissolve. Code:


---------------
MAB

MAB Badgerbimmer

user


Statistics:
Messages: 591
Registration: 04.21.2001
16.02.24 - 12:02:57
Message # 4
RE: More than ~10 clips is a memory buster?

Try something like Setmemorymax(2048) and different source filters (avisource/ffms2)


---------------
John 2001 ///M Roadster F: CG/Koni short coil-over struts/Eibach, Wilwood front brakes, CG tubular swaybar. R: TC Kline springs, short Bilsteins, shortened swaybar, IE sub & swingarm bushings & shock mounts, 3.23 gear, Rogue dual-ear cover, Eisenmann

QikSilver

user


Statistics:
Messages: 826
Registration: 08.26.2002
16.02.24 - 12:07:47
Message # 5
RE: More than ~10 clips is a memory buster?

He also reported that DGDecNV is "useless", based (apparently) on his evaluation of a cracked binary that is almost 30 versions old. I'm not holding my breath waiting for him to explain that.


---------------
,,,2011 black M3 sedan comp. pk vf 620 sc kit aka "KMPRSSR",,, 2013 x6 5.0 m sport pk "WIFE's",,2007 X5 4.8,,,2013 "BLACK OPPS"

95m3sc

user


Statistics:
Messages: 614
Registration: 03.03.2003
16.02.24 - 12:17:51
Message # 6
RE: More than ~10 clips is a memory buster?

DirectShowSource is probably the absolute last thing I would try if all else fails. I'm not saying it's the source of your problems but I certainly wouldn't want to be using it either way. Try .




Shawnee

user


Statistics:
Messages: 183
Registration: 12.13.2003
16.02.24 - 12:27:04
Message # 7
RE: More than ~10 clips is a memory buster?

Don't lots of codecs have issues when you load them multiple times? I've hit this with AVISource and over 60 clips joined together - first I lost audio, then with even more clips I lost the lot.




OWFVDRZN

user


Statistics:
Messages: 151
Registration: 07.05.2002
16.02.24 - 12:32:44
Message # 8
RE: More than ~10 clips is a memory buster?

I was able to resolve the audio issue with the ffmpegsource2 sourced clips after a read thru of the FFMS2.avsi script and a slight modification. I was very excited after days of mind numbing scripting to have finally completed an avisynth script that automatically spliced 25 or so HD clips together with transitions, fading titles, etc. HOWEVER,( as it always goes).. although FFmpegsource2 allowed me to utilize more clips in my script, the audio is now out-of-sync in many of the clips. DirectShowSource did not have the same sync issues. Some more testing revealed that the issue is the audio/video delay on the clips. DirectShowSource accounts for any audio/video delay to sync the clips properly but FFmpegsource2 does not appear to handle the delays. Does anyone know of a modification (besides manually looking up and entering in the DelayAudio() for each clip) to allow FFMS2 to accurately handle the audio/video delays? As always, i am very grateful to the kind contributors to this very helpful forum.




cdriley

user


Statistics:
Messages: 146
Registration: 12.09.2003
16.02.24 - 12:39:17
Message # 9
RE: More than ~10 clips is a memory buster?

^I did not specify the adjustdelay so it is at default. Is there adjustdelay setting that would handle a video delay? (ffmpegsource2 seems to handle an audio delay without issue ).


---------------
1995 M3 (sold) 1997 M3/4 (sold) 2004 GT3 2008 E90 M3 on order -- week 23 build -- DCT and 19's!

ArcticFox

user


Statistics:
Messages: 2,104
Registration: 12.13.2001
16.02.24 - 12:44:18
Message # 10
RE: More than ~10 clips is a memory buster?
Цветные потолочные решения : Previous topic
Pages:  1  

The administrator has prohibited guests from replying to messages! To register, follow the link: register


Participants

Forum powered by: PunBB 5.0.6