Muxing "m2ts" file, VERY SLOw !!!

[Selur]

Yeah, but I wanted a step-by-step based on the last version I send you,...

[ToiletDuck]

Yeah, but I wanted a step-by-step based on the last version I send you,...

EZ   

Basically did the very same thing as mentioned in my previous post.  i.e: uninstall + deleted all settings previous release, install, config + safe default, load, open, run preview...

...and... looked promising, saw hybrid moving/going forward in the right direction (FFvideo ←) when suddenly...

Bam ↓ 


Here are the following processes i see in task manager .. before the infamous error pops up ↑ ...



Ps: personaly , i have checked the security settings from my temp folder / drive to check if some permissions might causing this...
But, Write/READ & execute persmisions are allowed on that folder, but then again that can't be an thing since avisynth works, using LWlibavsource preview works too so... just saying..

EDIT: almost forget, about the "indexer finisher error"... i get that EXACT same message aswell when DGDecNV us enabled in vapoursynth→ misc→source !!?

Cheers,
TD

---

Update..

i also want you to know, that since i have checked the permission from the temp folder... 

i had an gut feeling that might be it, since i couldn't run hybrid with admin rights !!

Not onLY that, i couldn't / wasn't allowed to create an .ini file in hybrid folder to work arround that ... glad to be on win11   .. Can't wait for win 12 release 0_o
So, i granted permissions myself to hybrid folder to run hybrid in admin mode now..  

But the same error pops up... so, any "restrictions" can't be the root of the problem anymore... atleast i couldn't think of any other... have excluded folders/app folders, granted permission and so on... 


cheers,

[Selur]

The debug output should show the used indexing call.
From the looks of it, FFMpegSource2 can't properly process your source.
If DGDecNV also gives an indexer Finished with a negative return value, it also can't handle the source.

"-1073740791" = stack buffer overflow

Cu Selur

Ps.: can you reproduce this with a short sample that you could share?

[ToiletDuck]

The debug output should show the used indexing call.
From the looks of it, FFMpegSource2 can't properly process your source.
If DGDecNV also gives an indexer Finished with a negative return value, it also can't handle the source.

"-1073740791" =  stack buffer overflow

Cu Selur

Ps.: can you reproduce this with a short sample that you could share?

I think i have found what's causing the error selur    ...

EXACTLY dizz → an *.jpg attachement inside the container wos causing this erratic behaviour   ... my bad ... L   L 
 
I kid you not ...    Who would have thought, an small insignificant .jpg file ... !!

After i have removed that file throug remux process , hybrid summons the preview from an 3hour movie in like 5 secs whitout a hassle now hehe..

so, it's up to you to fix that, but i don't actuall use that method anymore ... so...

Much thanks to stand by my side in this ordeal LoL..

cheers,
td

[Selur]

Okay, seems like the FFMS2/libavsource can't handle the jpg attachment, sadly there is nothing I can do about that in Hybrid.

Cu Selur

[ToiletDuck]

Okay, seems like the FFMS2/libavsource can't handle the jpg attachment, sadly there is nothing I can do about that in Hybrid.

Cu Selur

No problem.. i could care less about that attachement now 
I mean , the most important thing is that we know whats causing these errors !!


Just for my gratification, could you check out and see if you can reproduce the error now by attaching an small jpg file to an short clip and try to open it in filter preview  
Now that you know what wos causing these issues, you might have an better chance to reproduce it hehe..


Cheers,
TD

[Selur]

Using the attached ffms2_r1363.7z
Replacing the ffms2.dll and ffmsindex.exe:

• 32bit/avisynthPlugins with the x86 versions
  
• 64bit/Avisynth/avisynthPlugins with the x64 versions
  
• 64bit/vsfilters/SourceFilter/FFMS2/ with the x64 versions
  

seems to fix the issue here.

Cu Selur

[ToiletDuck]

Using the attached ffms2_r1363.7z
Replacing the ffms2.dll and ffmsindex.exe:

• 32bit/avisynthPlugins with the x86 versions
  
• 64bit/Avisynth/avisynthPlugins with the x64 versions
  
• 64bit/vsfilters/SourceFilter/FFMS2/  with the x64 versions
  

seems to fix the issue here.

Cu Selur

Yes, that wos the next logical step. I thought about that too..
These kind of errors are often bug related in tools.

In the past , i attached scanned covers to my .mkv fiiles as an double backup , incase i lost my data for some reason...
Never ever have i had any problems using the content embbed in the mkv files in any application untill now.. 

Wos i surprised that wos the whole reason of the malfunction  ..!?


cheers,
td

[Selur]

I usually embed pngs not jpgs, so I never noticed the issue.

Cu Selur

[ToiletDuck]

I usually embed pngs not jpgs, so I never noticed the issue.

Cu Selur

so, the issue didn't happend using *.png files ?  What an coincidence.. 
From the zilion amount of extension you can chose from   , you have managed to chose the right format as attachement lol.


Cheers,
TD