Weird CRASH work-around !

[ToiletDuck]

 

PS
The Japanese love/LIKE to add copy protection

..🤨

@ToiletDuck:
Your post states:

• you use Win11 23H2 with Hybrid 2024.16.06.01
  
• for some mkv files (no details about these) Hybrid crashes right at encode stage with "Crash Exit Code 10".
  
• if you remux the files (I guess using mkvtoolnix), the encoding works.
  

So it seems the issue might be some incompatibility with your source and whatever is doing the decoding.
It might be that the used decoder / source filter can't handle the source or the source is broken somehow.
Since, I assume you remuxing from .mkv to .mkv, helps, the latter seems more likely.
It could also be that some antivirus software or similar is interfering.

Can't reproduce, can't really help with random problems.

Have checked the source file thorougly, and can't find anything strange about it..
i.e: i know crashes can happend when timecodes are fubar for instance.. but the source seems to be clean,yet..  After remux, containing every bit of info (sub, chapters, audio etc..) hybrid doesn't have one bit of problem with it encoding it 🤔..

So, if the content (tracks, subs, audio etc) of the source would cause this, i shouldn't be able to remedy / work around that issue that easily .. right ?

Also, an bad source file shouldn't be playing flawless on a Hw/sw restricted player...  In 99,99% of the cases if something is wrong about the source file, that alway's will translate into an problematic playback .. i.e hickups, distortion, no sound / broken sound, no video / missing frames during playback..  you name it ... atleast in my experience..

Also, i have had these EXACT crashes before in the past, and instead of just remuxing the thing  (easiest work around) , i did work around that by changing containers restrictions and/or some settings in VapourSynt→Source settings ..  But i don't know what i have changed in combo to overcome these weird crashes .. just fyi, something about hybrid isn't playing nice with some sources ... !
Ta TA
Toilet(°^°)

---

... update..

Hmm... just copied/moved (no remux) the exact source file to another storage device (internal nvme.m2) and hybrid is playing nice and started the encoding whitout any crashes   !!

Strange, it picks just this file to refuse and encode from the default HDD drive, but other files that are on the same HDD do in fact encode (no crashes) .. it just crashes with that One specific particular file 🤔...
So this seems to be NOT a remux fix / work around...!



I wonder... could the problem be → using very long file names ?

EDIT 2: Yep → CONFIRMED , seems using Long / weird filenames will induce hybrid to crash 😑
That's ↑ the quickest fix , my personal best imo 🤭

Although, iam shocked long filenames is STILL a THING ... 😦! An restriction of the Ol DOS dayz 😑!!