Preview + encode disaster !

[ToiletDuck]

While iam talking about the HWdecoding setting in Config→Input→Decoding→Use Gpu for Decoding=  section from hybrid 

That will be used if you don't use Avisynth or Vapoursynth and will crash is you select something that doesn't work.

REALY   → !?! 

I could have sworn, the first thing i did when i encountered that preview filter issue = Deselecting → HWencode totaly under input tab.. 
And that ↑ immediatly solved the problem    .  

what else , what other setting could have fixed / worked around that issue, since Libav HWdecoding is only for Intel/nvidia users...
I would guess "filesize", but the workarround did overcame that issues with that big file  

Strange thing is, when I indexed it with FFVideoSource, closed the preview and reindexed it, is was faster.

Could it be a Windows disk caching issue?
Cu Selur

By disk cache, iam guessing you are refering to write caching for SSD/HDD ?  Do you?
Or are you refering to the reserved memory space (RAM) to write to and read from ?
And there is the swap/page file too..


It's best to enable that in device manager me thinks..

But more importantly, erratic speeds can be due to the ssd firmware, bios mobo, even device driver etc ...  
I wish it only wos that easy to improve speed by flipping an switch (registry/background services etc..)   



Anyway, was it faster like in → did u saw the preview window in a snap of a finger (Litterally) ?

If so, i keep mention that..  

With LWlibav, each time you tune the filters , lwlibav needs to created the index file from scratch ... 
The waiting game all the time untill the preview pops up ! 


With FFmpegSource2 it's way different, it only create the index just ONCE yes, ONE TIME, to get the preview to see, no matter what you change or enable what filter you get to see that window like INSTNANTLY ... Boom   
I mean, could it be that ffmpegsource2 stores an portion of that media in the ram (or ramdisk)..  


Because ,i saw via islc that my 32GB ram sinks quite a bit using ffmpegsource2   


And just to be sure, u did tried this out using Ffmpegsource2 did you?


cheers,
td

[Selur]

By disk cache, iam guessing you are refering to write caching for SSD/HDD ? Do you?

read-/write cache assigned by the OS.

I could have sworn, the first thing i did when i encountered that preview filter issue = Deselecting → HWencode totaly under input tab..
And that ↑ immediatly solved the problem

That is the mplayer preview, that (normally) has nothing to do with the actual processing.
(removing mplayer dependencies is one of my 'large' to-dos I never get to,...)

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.

And just to be sure, u did tried this out using Ffmpegsource2 did you?

The benchmarks: Yes
No clue what you are referring to otherwise.

Cu Selur

[ToiletDuck]

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.

I could have sworn, the first thing i did when i encountered that preview filter issue = Deselecting → HWencode totaly under input tab..
And that ↑ immediatly solved the problem

That is the mplayer preview, that (normally) has nothing to do with the actual processing.
(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.

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

[Selur]

Index files are created in the temp folder that is configured in Hybrid. (Config->Paths->Default temp path)
Like I wrote before, I would recommend to a. set a dedicated path for this b. add an exception to your virus scanners etc. for this.

I mean, the index files are created each time in the source folder in my case.

That should only be the case if source and temp folder are the same,...

[ToiletDuck]

Index files are created in the temp folder that is configured in Hybrid. (Config->Paths->Default temp path)
Like I wrote before, I would recommend to a. set a dedicated path for this b. add an exception to your virus scanners etc. for this.

I mean, the index files are created each time in the source folder in my case. 

That should only be the case if source and temp folder are the same,...

that's the first thing i do when config any software..
I mean, it's only logical to choose the biggest and fastest storage device for temp usage. is it not  .


And yes, how did you guess   .  
Indeed, temp + source has the same path for me, just for the sake to keep everything tight and together   .

ps: I've saw you took care of the smooth seller .. selur   ..
I guess the store is closed (banned ^^ ) as of now   ?

cheers,
TD

[Selur]

And yes, how did you guess

index is always written to temp folder, you said yours is in the source folder, so the conclusion was, you set the temp folder to the source folder or something was wrong.
-> seems like everything works as good as it can

Cu Selur

[ToiletDuck]

-> seems like everything works as good as it can

Cu Selur

So far so good... except for E-AC3 (DD+) 

today i have gotten my AVR back from repairs.

And i wos very curious to see how my trusty "old" Denon receiver would cope with DD+ streams at differenten → Bitrates...

so, i ran an sample with DD+ → @1500Kbps ... And iam telling you , some very weird stuff is going on when i choose high bitrates for E-AC3.

check this, i have sound and bitstreamed uhuh... Whereas with the former soundbar, i did not get any sound.. unless pcm in pdvd..

BUT..  the sound plays very choppy, and the framerate / playback is very very choppy aswell BOTH in PDVD and my hardware bluray player.

So you see, the hardware player seems to agree with pdvd and vice versa, but god knows why !?!?
See, something is very wrong using given bitrates in DD+ format... if only knew what..  
Have contacted cyberlink about that already, yet have to receive an plausible explanation .. 

One thing is certain, it doesn't seem to be an AVR issue... 
Denon is one of , if not the best brands next to marantz for AVR's ..


Cheers,
TD