VideoHelp Forum




+ Reply to Thread
Page 2 of 2
FirstFirst 1 2
Results 31 to 39 of 39
  1. Captures & Restoration lollo's Avatar
    Join Date
    Jul 2018
    Location
    Italy
    Search Comp PM
    Originally Posted by dellsam34 View Post
    For some reason I can still see filed blending in your sample, someone can correct me if I'm wrong.
    I do not see field contamination in Recapture.avi. But each field is very low quality and their timing architecture is weird, as Sharc alreay pointed out.

    Is not a simple (constant) phase shift because a DoubleWeave().SelectOdd() does not fix the video. It must be some dynamic phase shift, embedded in the tape or introduced by a faulty device.

    It can be fixed with a field matching operation, here a comparison comp.avi. But OP should solve his capture issue first.

    Code:
    video_org=AviSource("Recapture.avi")
    
    #video_org_rep=video_org.DoubleWeave().SelectOdd()
    
    video_org_rep=video_org.TFM(order=1, mode=0, PP=0, slow=2, field=1)
    
    stackhorizontal(\
    subtitle(video_org,"video_org",size=20,align=2),\
    subtitle(video_org_rep,"video_org_rep",size=20,align=2)\
    )
    Click image for larger version

Name:	comp.png
Views:	26
Size:	2.01 MB
ID:	89873
    Quote Quote  
  2. Yes, 25p content was broadcast BFF but captured TFF. It can also be made progressive again with something like:

    Code:
    AssumeTFF()
    SeparateFields()
    Trim(1,0)
    Weave()
    Though this has the same problem as DoubleWeave().SelectOdd(). The filter chain gets confused because there are an odd number of fields left after removing the first field. If you work linearly from start to end there's no problem. But if you go to the end and step backward the filtering gets messed up.

    On the other hand, TFM() can sometimes mismatch or deinterlace inappropriately.
    Last edited by jagabo; 23rd Nov 2025 at 09:56.
    Quote Quote  
  3. Captures & Restoration lollo's Avatar
    Join Date
    Jul 2018
    Location
    Italy
    Search Comp PM
    Originally Posted by jagabo View Post
    On the other hand, TFM() can sometimes mismatch or deinterlace inappropriately.
    With PP=0 TFM does not look for combed frames, so no deintarlacing is applied. And I add mode=0 for this type of material.

    The only case where I noticed a such configured TFM in confusion is in rare footage where the picture is static and there is some vetical/horizontal shifting (i.e. end credits on uniform background); but the outcomes is just a frame pattern change, so nothing serious.

    But again, if the defect is not baked on tape, better to fix the capture.
    Quote Quote  
  4. Member
    Join Date
    Jun 2024
    Location
    United States
    Search Comp PM
    The one i saw was a European model apparently. Slightly different layout on the front as it doesn't have the Tint buttons. One of the later models anyway
    You saw one that had 2004 on it that was PAL? I’m pretty sure you just saw a board image of mine. I haven’t heard of anyone else having one that was made that late.Image
    [Attachment 89878 - Click to enlarge]
    Quote Quote  
  5. Originally Posted by lollo View Post
    Originally Posted by jagabo View Post
    On the other hand, TFM() can sometimes mismatch or deinterlace inappropriately.
    With PP=0 TFM does not look for combed frames, so no deintarlacing is applied. And I add mode=0 for this type of material.
    Sorry, I didn't notice you used pp=0.
    Quote Quote  
  6. Member
    Join Date
    Jun 2024
    Location
    United States
    Search Comp PM
    Well I guess we know that a recap doesn’t fix that now. https://www.digitalfaq.com/forum/vcr-repair/14060-tbc-3000-causing.html LS has the same issue with his 3rd and 4th gen TBC 3000s and from what he said there is not a known way to fix it.
    Quote Quote  
  7. Originally Posted by Gary34 View Post
    Well I guess we know that a recap doesn’t fix that now. https://www.digitalfaq.com/forum/vcr-repair/14060-tbc-3000-causing.html LS has the same issue with his 3rd and 4th gen TBC 3000s and from what he said there is not a known way to fix it.
    Thanks for the link. So the TBC flaw and the capture window offset has obviously been known, and the OP may now revisit his capture process to address the remaining issues with the fields sequence mess - unless this is also caused by the flawed TBC-3000.
    Quote Quote  
  8. Member
    Join Date
    Jun 2024
    Location
    United States
    Search Comp PM
    The ATI AIW cards don't have anything in the way of resilience. If your frame TBC isn't there you might want a more resilient card.
    https://www.digitalfaq.com/forum/video-capture/15204-ati-aiw-card.html
    Quote Quote  
  9. Member
    Join Date
    Jun 2024
    Location
    United States
    Search Comp PM
    The TBC 3000s are really risky to buy now. I had bought mine in 2023 from a college professor nearby who just wanted the 800 he paid for it forever ago and said he would feel bad charging the prices he saw online. The online ones are beat up ones that don't work. The one he had was kept in air-conditioning and labeled in a neat office for 20 years. The guy went to his friend who was into professional video and music and tried to have him sell it and everyone he talked to said it was old and they didn't want it. then he listed it under regular facebook using a stock photo of a Pal unit. He didn't take into account condition of inflation or anything. It was really risking the 800 though because anything could have been wrong with it. It's best to buy refurbished. Even if you buy something refurbished stuff happens.
    Last edited by Gary34; 23rd Nov 2025 at 22:29.
    Quote Quote  



Similar Threads

Visit our sponsor! Try DVDFab and backup Blu-rays!