22.08.2023, 11:35
(22.08.2023, 05:09)Selur Wrote:Quote:By disk cache, iam guessing you are refering to write caching for SSD/HDD ? Do you?read-/write cache assigned by the OS.
Yes, that's what i actually meant by "reserved memory space" by os.
(22.08.2023, 05:09)Selur Wrote:Quote:I could have sworn, the first thing i did when i encountered that preview filter issue = Deselecting → HWencode totaly under input tab..That is the mplayer preview, that (normally) has nothing to do with the actual processing.
And that ↑ immediatly solved the problem
(removing mplayer dependencies is one of my 'large' to-dos I never get to,...)
"Normaly"? You lost me there...!
No what iam trying to say, the issue with the filter preview window only went away after deselection HWdecoding not before ?
So, in some way to me it seems it is infact related to the issue. Or is it coicidence.
I'll try another BIG source next time to see what it does.
(22.08.2023, 05:09)Selur Wrote:Quote:I mean, could it be that ffmpegsource2 stores an portion of that media in the ram (or ramdisk)..nope, ffmpegsource2 only saves the .ffindex file in the temp folder. (might be windows defender or similar)
While creating the index it eats ram.
You absolute sure, it creates the files in windows "default" temp folder noless?
You probebly mean by default in hybrid?
I mean, the index files are created each time in the source folder in my case.
After all iam using Custom Temp & Destination paths Selur.
cheers,
TD