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.

Processing a 48 min MiniDV clip is ending with a 4 minutes clip
#1
this is the debug log:  http://www.wcn.it/debug.txt

i processed others MiniDV clips from the same camera, aquired using winDV application without any issue

Hybrid is used to deinterlace (bottom field) and make a temporal degrain
the clip is 720x576 (PAL) with a PAR of 64x45 ( 16:9 setting from a sony MiniDV recorder that stretch the video to obtain a wide video using the standard 720x576 size)
i don't think this is related to the PAR BTW.

this clip (10 GB) is ending without crashes or other after 4/5 minute of processing
Reply
#2
Try whether the Vapoursynth Preview does show the whole clip, if not, try whether disabling 'Prefer BestSource' helps.
If it does, and you can share a link to a smaller clip, which allows reproducing the problem, I could send it to the author of BestSource to look into it.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#3
also in preview the clip is showed long only 4 minutes...

i cutted a piece of the original clip (6 minutes)  .. also processed as 4 minutes:

http://www.wcn.it/6.avi

just reinstalled hybrid deleteing everything and the video is correctly displayed (lenght) on preview. trying to degrain rightnow

[Image: half.jpg]

this need a lot.. because is used only 40% of the cpu... no idea why (usually i can use 85% )
Reply
#4
Thanks, for the download I can reproduce the problem with BestSource and disabling 'Prefer BestSource' does fix the problem.
=> Will report it to the BestSource author, and hopefully he has time and is willing to fix it. (reported it)

Quote: this need a lot.. because is used only 40% of the cpu... no idea why (usually i can use 85% )
no clue either only thing that really changed was the preference of BestSource,...

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#5
Okay, problem found:
You format changes in the file. Vdub2 will barf out warnings about it. I think it's only a few frames so you may be able to cut out a bit around frame 6886 to fix it too.
-> seems like your source is buggy (in theory, I could add an option to set 'variableformat=True' in BestSource, but changing characteristics would just cause problems in later filters.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#6
This is the issue i had, my video is cut out of DVD to cut ads and stuff so maybe thats why it was cutting 10k frames, shouldnt do that anyways spent days troubleshooting just for a simple fix Tongue Smile
Reply
#7
UMh.. this mean that WinDV is creating bugged outputs? never heard about this on last 21 years..
BTW.. for some reason i was able to process correctly the file using a fresh new installation of hybrid
Reply
#8
(14.10.2024, 10:19)Bartoloni Wrote: UMh.. this mean that WinDV is creating bugged outputs? never heard about this on last 21 years..
BTW.. for some reason i was able to process correctly the file using a fresh new installation of hybrid

Huh 
How long have you been using an AMD CPU?
When did all these problems start?
Huh
Reply
#9
Quote:UMh.. this mean that WinDV is creating bugged outputs?
Not sure, what could cause this, but that the format changes inside a file is rather uncommon.
Some formats support it. Like myrsloik wrote, it were only some frames, so this is probably the result of some (smart) cutting where some headers got broken. (could also be some transfer error)

If this happens more often, I can add an option to enable the support for 'variableformat=True', but like I wrote that probably will cause problems later, since Hybrid and most filters assume that the input has a constant format (color space, sampling, matrix,..).
I expect something like this to potentially happen with transport stream captures (resolution, audio count, etc. can change in transport streams), with other stuff content it's really rare and Hybrid will not handle it properly.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)