This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Weird CRASH work-around !
#8
(02.09.2024, 14:29)Selur Wrote: Without any details, nothing I can check, workaround, etc., but happy you found the cause of your problem.

Cu Selur

Do i sense a "debug file request" there 😏 ?

I get it.. And i did created one to see and check it for myself, .. 

But i didn't find anything unusual compared to an debug from an normal working source file , you know !
so.. but if you still want it to DL and have an look, i'll post it..

Granted, the Devilish devil 😈 is in the "details" sure enough 😉.

And again, just ran a test sample (long filename) = no errors / crashes..  
But check this, running the complete media file (same long filename) = crash 

Here's the ↑ other thing we have covered numerous times in the past ,→ for some reason it's impossible to reproduce an certain crash/issue using an small samples taken from the original source !?

For some reason , hybrid doesn't have any problem processing the small samples completely ...   

Wich leads me to believe, something has been corrected / changed during remux for hybrid to complete the task.. yet the strange part is, i can overcome all this read/write stuff by just changing the file name.. wich is comparing apples with oranges and raises another question !?!? Is it "realy" the source.. or just a matter of the filename !?

And thats the interesting and most funny part of all...

There's 2 way's to work around that issue..  Either i have to remux it keep the same EXACT LONG filename, and hybrid will process it completely despite of the long complex file name..

Orrr... i simply use the quickest route, and just shorten the filename from the source...  Strange... 2 complete different approaches, yet one is necessary to defeat this strange issue !

Up untill know i thought only a remux would work around this, but clearly something about what and how long the filename is from the source is causing this aswell... interesting..  



Anyhow, it's nothing that can't be remedied by adjusting the source or settings in hybrid fortunately 🥹👌



 

(02.09.2024, 15:00)humanoid86 Wrote: aah....

when coding there are multi-threaded HDD drives and letters of the name with symbols, like &&&&?????!!!!!!!!!!!!@@@@@@@@@@%%%%%&&&&^^^^^^^^^^^^^^^^^''''''''''''''''''''''' and etc

... duck senses tingling (° ^°) *smelling a malicious bot * Dodgy ..


Ta Ta
TD(° ^°)
Reply


Messages In This Thread
Weird CRASH work-around ! - by ToiletDuck - 02.09.2024, 01:57
RE: Weird CRASH work-around ! - by humanoid86 - 02.09.2024, 04:09
RE: Weird CRASH work-around ! - by Selur - 02.09.2024, 05:06
RE: Weird CRASH work-around ! - by ToiletDuck - 02.09.2024, 10:41
RE: Weird CRASH work-around ! - by Selur - 02.09.2024, 14:29
RE: Weird CRASH work-around ! - by humanoid86 - 02.09.2024, 15:00
RE: Weird CRASH work-around ! - by Selur - 02.09.2024, 15:34
RE: Weird CRASH work-around ! - by ToiletDuck - 02.09.2024, 18:55
RE: Weird CRASH work-around ! - by Selur - 02.09.2024, 18:59
RE: Weird CRASH work-around ! - by ToiletDuck - 02.09.2024, 19:41

Forum Jump:


Users browsing this thread: 2 Guest(s)