50fps HEVC with VHS video

[tugatomsk9]

I have a ton of home recorded and edited motorsports videos on VHS that I'd like to capture. It will have to be done with composite cables and a MAGIX pen because at the moment I can't afford either a better PC or a better video capture device... (all PCI and PCIe slots are in use).

My goal is to produce QTGMC deinterlaced 50fps at approximately 576p (probably less due to some slight cropping needed) with an average video bitrate of 800-1000 kbps.

I've heard that HEVC is extremely useful at low bitrates, so I was thinking of using the "very slow" preset given the high framerate. Is it overkill? Should I also use 10bit for the banding?

Or is HEVC not all that's cracked up to be and I should just go with 8bit x264 at a higher bitrate?

[Sharc]

I don't know what a MAGIX pen is an what it does. Is it a capture HW/SW package with an on-the-fly encoder?
First of all you should capture your VHS tapes lossless using HUFFYUV, Lagarith or UTVideo codec. Composite video is not the best choice as it is prone to producing dotcrawl and rainbows, but I understand you have no other choice.
Once you have succeeded with the lossless capture (no dropped frames, etc) you can view the captured video and only then decide on next steps like cropping, denoising, deinterlacing/bobbing. You have to do some test encodes using x264 (AVC) or x265 (HEVC) and see what CRF or bitrate gives the desired quality level. Finally, one needs to mux video and audio in a container format of your choice.
The first step is very crucial though. If the VHS capture is flawed it is nearly impossible to recover any losses at a later stage.

[tugatomsk9]

I don't know what a MAGIX pen is an what it does. Is it a capture HW/SW package with an on-the-fly encoder?


https://www.magix.com/int/video-editor/vhs/

It is bundled with a below-average capture software and a proprietary video codec that did not please me at all.

Yes, I did plan to capture using Huffyuv of Lagarith from the start.

My doubts about which encoder to use arised from my PC being very old and low-spec: intel i3-2100, intel HD graphics card...

Is S-Video a better option even though it's still VHS? I do own a Sony RDR-HX710 DVD video recorder, but I wanted to avoid recording using mpeg2 before reencoding to x264/x265. The Sony does have S-Video line in and line out, though. Is there any benefit from using the Sony as a pass-through between the VHS VCR and the USB capture drive using S-Video?

EDIT: BTW, the VCR in question is a Panasonic NV-FJ623 Hifi Stereo with 6 heads bought in 2003 and operating in good conditions.

[Blue_MiSfit]

Regarding s-video vs composite, it depends heavily on the quality of the comb filter.

VHS is a composite format, period. Splitting it into separate luma + chroma requires a comb filter, and it either happens on the player when you're making S-Video, or on your capture card.

Old laserdisc players for example had shitty comb filters by today's standards, so with a pro capture card you'll get much better results with composite. Not sure if that's the case with your basic capture device :) Try it both ways and see which method produces less dot crawl.

Regarding compression, HEVC is a good fit for this if you don't mind spending the compute. Use 10 bit. With an i3 doing the encoding I'd say it's overkill though :)

Why do you want the bit budget to be so low? You're using QTGMC so presumably you do care about the quality! ;) I'd have transparent quality be a top priority. Just use low CRF encoding with x265 or x264.

[RanmaCanada]

x265 is really not advisable for SD content. You will get far better results with x264. As Sharc says, try to use Huffy lossless for your capture. VHS is a noisy medium, and you will need to keep as much of the original footage as possible.

[benwaggoner]

x265 is really not advisable for SD content. You will get far better results with x264. As Sharc says, try to use Huffy lossless for your capture. VHS is a noisy medium, and you will need to keep as much of the original footage as possible.
Yeah, on a low spec machine, the quality @ perf of x265 might not be that much better than x264, since you might be able to run x264 in slower and x265 at medium for the same total encode time.

[tugatomsk9]

Regarding s-video vs composite, it depends heavily on the quality of the comb filter.

VHS is a composite format, period. Splitting it into separate luma + chroma requires a comb filter, and it either happens on the player when you're making S-Video, or on your capture card.

Old laserdisc players for example had shitty comb filters by today's standards, so with a pro capture card you'll get much better results with composite. Not sure if that's the case with your basic capture device :) Try it both ways and see which method produces less dot crawl.

Both produce dot crawl. :\ At least now I know the cause of it.

I know there are avisynth filters for dot crawl, it's just that I've never been a big fan of the usage of avisynth; some of its filters are rather complicated to set up. But I guess I'll have to give it a try.



Why do you want the bit budget to be so low? You're using QTGMC so presumably you do care about the quality! ;) I'd have transparent quality be a top priority. Just use low CRF encoding with x265 or x264.

Oh, the values were more of an example. ;) I was aiming for 230MB for a 25min 50fps video, for example. The main reason is hard drive constraits. Hard drives are not that cheap in my country - the coronavirus ins't helping at all - and I've been unemployed for quite some time, so I was trying to be as filesize efficient as possible. Being unemployed also prevents me from bying a modern, up to date PC with a proper video capture card that I've been wanting for years...


There's something I forgot to mention: the recordings are mostly second or even third generation recording using two VCRs at the time for the editing. There are some which are first generation, but they're not the norm, sadly. Also sad is that my father never owned a S-VHS video, which would have been ideal for such edits. But what is done is done. :/ I know there isn't much to retain, but I do want to retain the original smoothness of high speed sports such as motorsports, which is why I wanted to double the framerate and not let the video bitrate go through the roof.

[tugatomsk9]

Yeah, on a low spec machine, the quality @ perf of x265 might not be that much better than x264, since you might be able to run x264 in slower and x265 at medium for the same total encode time.

I did ponder to use x265 at the "very slow" preset despite the looooooong encoding time due to my old i3... But it's not set on stone.

What I was going for is that how much am I gaining with HEVC versus x264 with SD footage using the same preset and settings, like "very slow": is it worth it or is it just peanuts?

[Sharc]

What I was going for is that how much am I gaining with HEVC versus x264 with SD footage using the same preset and settings, like "very slow": is it worth it or is it just peanuts?
I would suggest to stick to x264 in your case. But why don't you just try and judge yourself?
As I said, start with the critical lossless capturing process with your setup. The subsequent encoding (apart from filtering) is almost peanuts IMHO.
If you have problems with the lossless capturing use your DVD recorder and set it for the best mpeg-2 quality (highest bitrate) and leave as is. Only if file size really matters reencode to AVC (x264).

[tugatomsk9]

I would suggest to stick to x264 in your case. But why don't you just try and judge yourself?
As I said, start with the critical lossless capturing process with your setup. The subsequent encoding is almost peanuts IMHO.

Oh, absolutely, I'll capture lossless.

I had the feeling x264 would be the more sensible option given my hardware, but I wanted to sort things out once and for all about this. Thanks, guys. ;) If I had a proper computer, though, I'd go all out with HEVC. :D

BTW, would it be of any help if I uploaded an excerpt to youtube and show you what it's going to be like 70% of the time? It'd be from the only DVD I burned with my Sony recorder, the portion of the original VHS recording that no longer exists.

[tugatomsk9]

If you have problems with the lossless capturing use your DVD recorder and set it for the best mpeg-2 quality (highest bitrate) and leave as is. Only if file size really matters reencode to AVC (x264).

Filesize is always an issue to me - I have many, many hours of tape to transfer -, so I'd always reenconde it to x264/HEVC.

I also considered using the Sony recorded as a video capture device. There's even a HQ+ option which raises the video bitrate to 15Mbps, outside the original MPEG2 norm. But even if I were to burn it to a DVD+RW and rip it on my computer, the burn itself would have to be an MPEG2 reencode itself due to a limitation imposed by Sony, which is a shame.

But even if I recorded in standar HQ (1h), HSP (1,5h) or even SP (2h) and fill the Sony's 160GB harddrive, I'd still have to burn my DVD+RW a massive number of time. It's a very long and boring process... (Of course, if there was a way to extract the original mpeg2 videos onto my PC, especially if they were HQ+, I'd be all over it.)

Not to mention that I was under the impression that mpeg2 was in itself a poor codec compression-wise?

[Sharc]

BTW, would it be of any help if I uploaded an excerpt to youtube ….
Youtube reencodes again. Hence it is not apropriate to judge quality. Upload a few seconds to a filehoster which keeps your original format intact. But I would just guess that your DVD recorded video is blocky …..

Edit:
I had a quick glance to your MAGIX converter and I would assume that it supports lossless capturing with a codec of your choice (Huffyuv). So that's the way to proceed.

[tugatomsk9]

Edit:
I had a quick glance to your MAGIX converter and I would assume that it supports lossless capturing with a codec of your choice (Huffyuv). So that's the way to proceed.

Righto. :)

[benwaggoner]

For compute-constrained encodes, using --preset slower --limit-sao 3 will give you most of what HEVC is capable of.

[foxyshadis]

If you really do want to scrape the bottom of the bit budget, x265 will always be better than x264, and likewise AV1 will always be better than x265 -- when compute time is no obstacle. But if your electricity is metered, it would probably be a lot cheaper to buy an extra terabyte or two and not go that route. At the fairly reasonable 1 megabit for SD video, the only reason to go with x265 would be if you edited and cleaned it to the point that banding will matter and built-in 10-bit will be meaningful. But if you're trying to keep closer to what a raw VHS capture actually looks like, even with some basic filtering, 8-bit x264 will still do plenty of justice at an extremely fast speed.

[benwaggoner]

If you really do want to scrape the bottom of the bit budget, x265 will always be better than x264, and likewise AV1 will always be better than x265 -- when compute time is no obstacle.
Well, AV1 is a bitstream and x265 is an encoder; comparing x265 would be versus a specfic AV1 encoder. While various assertions have been made about AV1 being "20% more efficient" than HEVC, most of those claims fall apart when subjective comparisons are made between an optimally-tuned x265 and an optimally-tuned libaom or rav1e. The 20% number was comparing mean PSNR at a fixed QP without any rate control, dynamic frame type selection, and a bunch of other constraints typical of reference encoders but far from how anyone actually encodes video for people to watch.

[Stereodude]

...At the fairly reasonable 1 megabit for SD video, the only reason to go with x265 would be if you edited and cleaned it to the point that banding will matter and built-in 10-bit will be meaningful. But if you're trying to keep closer to what a raw VHS capture actually looks like, even with some basic filtering, 8-bit x264 will still do plenty of justice at an extremely fast speed.
There's always 10-bit x264 also.

[benwaggoner]

There's always 10-bit x264 also.
Alas, supported on fewer devices than HEVC 10-bit, particularly mobile.

[Stereodude]

Alas, supported on fewer devices than HEVC 10-bit, particularly mobile.
For hardware decoding, yes. But it's SD resolution, so software decoding shouldn't be an issue.

[benwaggoner]

For hardware decoding, yes. But it's SD resolution, so software decoding shouldn't be an issue.
Really depends on the playback platform and players being used.

[tugatomsk9]

After some time experimenting with avisynth, I finally conjured a good avs script using QTGMC deinterlacing. The resulting image quality - checked using Virtualdub as a frameserver - turned out really nice, especially taking into account the not-so-good original PAL VOB.

Here's the script:

LoadPlugin("C:\Program Files (x86)\MEGUI\tools\avisynth_plugin\FFMS2.dll")
LoadPlugin("D:\USER\Documentos\IMPORTANT STUFF BACKUP\avisynth plugins\hqdn3d\hqdn3d.dll")
mpeg2source("G:\WORKING\Duarte&co\Duarte e Companhia - 10 RTP memoria.d2v")
AssumeTFF()
QTGMC( Preset="Slower", MatchPreset="Slower", MatchPreset2="Slower", SourceMatch=3, Sharpness=0.9, TR2=3, Lossless=2 )
#(TR2= 0 for clean sources TR2=3 for noisy sources)
SelectEven()
#SelectEven() maintains original framerate
hqdn3d(ls=1.0, cs=1.0, lt=6.0, ct=1.0, restart=7)
LanczosResize(768,576)
Crop(10, 2, -16, -0)

However, I'm still experiencing difficulties trying to maintain the original aspect ratio. I scaled to 768x576 because I read in avisynth's wiki that operation changes the PAR to 1:1, which is what I want: a universal resolution for modern displays (LCD and such), giving up on CRTs.

Yet, when I open the resulting video file, VLC player still changes the aspect ratio when I switch from original to 4:3. This confuses me, because I thought I had created a video file that did not require aspect ratio changes on modern LCDs.

Which one is right: my stipulated resolution or VLC?

[Cary Knoop]

SelectEven()

Don't do that, especially not for motorsport.

[tugatomsk9]

Don't do that, especially not for motorsport.

I forgot to mention this particular case is not the aforementioned motorsports videos, but is instead an old Portuguese drama series. It was originally entirely shot on film, hence why I felt that it was of no use to bob the framerate to 50fps and increase the bitrate further; 25fps seemed more than enough in this case.

[benwaggoner]

I forgot to mention this particular case is not the aforementioned motorsports videos, but is instead an old Portuguese drama series. It was originally entirely shot on film, hence why I felt that it was of no use to bob the framerate to 50fps and increase the bitrate further; 25fps seemed more than enough in this case.
If it was shot on film and transferred to PAL, it should have 25p frames even if the container specifies interlaced. Bobbing in that case would either do nothing or wreck your content, making it look all soap-opera like, ala turning on aggressive motion smoothing settings on a TV.

[tugatomsk9]

If it was shot on film and transferred to PAL, it should have 25p frames even if the container specifies interlaced. Bobbing in that case would either do nothing or wreck your content, making it look all soap-opera like, ala turning on aggressive motion smoothing settings on a TV.

The production originally shot on film, yes, but the show was broadcasted on cable (and had been broadcasted decades earlier on aerial TV) and I recorded it in DVD format with a standalone Sony DVR. That's why my source is interlaced.

[Boulder]

You could post a sample, it's easier to see what it actually needs Avisynth-wise. There's a variety of high-quality denoisers out there and hqdn3d may not be optimal especially with content with lots of motion.

[Sharc]

LanczosResize(768,576)
Crop(10, 2, -16, -0)

However, I'm still experiencing difficulties trying to maintain the original aspect ratio. I scaled to 768x576 because ....
But you crop after resizing. Your player has probably stretched the cropped picture to 4:3 DAR.
Upload a short sample of the captured video for obtaining better advice how to crop and resize.

[tugatomsk9]

But you crop after resizing. Your player has probably stretched the cropped picture to 4:3 DAR.
Upload a short sample of the captured video for obtaining better advice how to crop and resize.

I cropped heavily because there were significantly large black areas on the sides. Another reason was it was my understanding that cropping after setting the desired aspect ratio did not change it.

Here's a sample of the original VOB:

https://drive.google.com/file/d/1IYQDLi3g9CFIRuTSO7dyQ92HWhJ6JITx/view?usp=sharing

[Sharc]

For converting to square pixels and 4:3 DAR I would suggest:
crop(10,2,-16,-2)
LanczosResize(720,542)
AddBorders(0,16,0,18)

It returns a 720x576 frame, square pixels, for DAR 4:3.

[Boulder]

That one's definitely progressive. If you just load the source and use Bob(), you can see that there is no motion between the fields. This means you can ditch QTGMC.

In my opinion it doesn't need that much denoising, but you could try MCDegrainSharp. Adjust to taste.
https://forum.doom9.org/showthread.php?p=1737045#post1737045

[tugatomsk9]

For converting to square pixels and 4:3 DAR I would suggest:
crop(10,2,-16,-2)
LanczosResize(720,542)
AddBorders(0,16,0,18)

It returns a 720x576 frame, square pixels, for DAR 4:3.

Most interesting! Thanks for correcting me, I' going to use this method as a template for VOBs. ;)

[tugatomsk9]

That one's definitely progressive. If you just load the source and use Bob(), you can see that there is no motion between the fields. This means you can ditch QTGMC.

I didn't notice it was progressive! :scared: It's just that all my recordings from that DVR are interlaced, so I assumed this one was too. I guess that particular episode was broadcasted as progressive and the DVR detected it?

Anyway, thanks for pointing that out. Removing QTGMC will boost the encoding speed by a lot. :D



In my opinion it doesn't need that much denoising, but you could try MCDegrainSharp. Adjust to taste.
https://forum.doom9.org/showthread.php?p=1737045#post1737045

What's the main difference between MCDegrainSharp and HQDenoise3D? Is the former much faster?

[Sharc]

Most interesting! Thanks for correcting me, I' going to use this method as a template for VOBs. ;)
Just word of caution:
My proposal was based on the assumption that the .vob had an ITU PAR of 1.092 (for DAR=4:3). The left and right borders are an indicator for this assumption.
You will find other .vobs (usually of newer DVD's) with a 'Generic' PAR of 1.067 (for DAR=4:3). These do normally not have left and right black borders, and the resizing to square pixels would become slightly different.
But anyway, if you pick the wrong one the error is 2.4% only.

[benwaggoner]

I didn't notice it was progressive! :scared: It's just that all my recordings from that DVR are interlaced, so I assumed this one was too. I guess that particular episode was broadcasted as progressive and the DVR detected it?

Anyway, thanks for pointing that out. Removing QTGMC will boost the encoding speed by a lot. :D
24p film is converted to 25p PAL by speeding the film up 4% so each film frame becomes one PAL frame. Nothing like the 3:2 telecine NTSC countries have been cursed with.

So, the broadcast was probably interlaced, and the bitstream is probably flagged as such. But the actual frames themselves are progressive source, and with MBAFF are made entirely of progressive macroblocks.

[tugatomsk9]

Just word of caution:
My proposal was based on the assumption that the .vob had an ITU PAR of 1.092 (for DAR=4:3). The left and right borders are an indicator for this assumption.
You will find other .vobs (usually of newer DVD's) with a 'Generic' PAR of 1.067 (for DAR=4:3). These do normally not have left and right black borders, and the resizing to square pixels would become slightly different.
But anyway, if you pick the wrong one the error is 2.4% only.

Thank you once more. ;)

[Boulder]

What's the main difference between MCDegrainSharp and HQDenoise3D? Is the former much faster?

Probably slower :D MCDegrainSharp does motion compensated denoising, simply put it sharpens blocks of good matches and blurs ones of bad matches with some weighting. Basically it should enhance edges and detail while removing noise.

It's easy to test how a filter changes the frame by using Interleave(), for example:

DGSource("test.dgi")
Interleave(last, MCDegrainSharp(bblur=0.2, csharp=0.4, frames=1))

Then you can switch between the original and processed frame in VirtualDub2 and adjust the parameters much faster.

[tugatomsk9]

So, I ended up buying the Avermedia Game Capture HD II which generates mp4 video files.

The recorded video quality of the Avermedia device in "576i optimal" (for VHS content) is good, but not great. The 8bit AVC average bitrate of only 7500 kbps is merely serviceable. VLC player plays it fine, though. :) The aspect ratio is 1:1, apparently, resulting in 720x576 video files. I guess it makes resizing easier?

The VCR being used is primarily a 2003 Panasonic NV-FJ623, with an older mono Sony SLV-135 whenever tracking becomes an issue.

The recording process is somewhat convoluted because I lack a composite to HDMi converter (I've ordered one, it just hasn't arrived yet). The signal from the VCR passes through a Sony DVD recorder (Sony RDR HX-710) via SCART. Then, the signal from the component output of the Sony recorder enters the Avermedia through the component input via a composite cable. It may seem terrible, but guess what, it works great, all things considered!

I'm trying to adapt the earlier avisynth script to these new mp4 files. I'm using Virtualdub 1.10.4 as a frameserver so I can check for errors.

Another issue is light aliasing present in the original VHS playback, like this, albeit not as strong:
https://forum.videohelp.com/threads/390999-aliasing-when-capturing-analog-Component-v-s-S-video

I tried figuring out if the aforementioned convoluted recording setup could be related to this. The conclusion is that it seems to be completely random, it doesn't happen all the time. I can't find a logical explanation. The tape in question was recorded in the late 80s with a long-gone National VHS VCR. There's no correlation with any of the cables used or the VCRs. Moreover, I used the Sony DVD recorder plenty of times in the past without aliasing issues.

To make matters worse, opening the avisynth script in Virtualdub is only sucessful if I don't use QTGMC, santiag (trying to test its anti-aliasing). It returns the error "File does not have a video stream"...

I even dumped the whole original mp4 in Virtualdub just so I could figure out if it was a case of fields swapped. I used "Field Swapping" in Virtualdub but it did not improve things.


EDIT: Here's a sample video.
https://mega.nz/file/aZBSyQZY#cPYbb4OV8dOzM3oajvUt1-Eg-HzWg1ywo51OREItECs

Right at the start of the video, notice the aliasing on the characters's contour lines.

[Sharc]

EDIT: Here's a sample video.
https://mega.nz/file/aZBSyQZY#cPYbb4OV8dOzM3oajvUt1-Eg-HzWg1ywo51OREItECs

Mixed interlaced and progressive content, frame rate doubled with a broken pattern.
Try
QTGMC()
selecteven()
It will return 50fps progressive video preserving the temporal resolution of the interlaced sections.

[benwaggoner]

So, I ended up buying the Avermedia Game Capture HD II which generates mp4 video files.

The recorded video quality of the Avermedia device in "576i optimal" (for VHS content) is good, but not great. The 8bit AVC average bitrate of only 7500 kbps is merely serviceable. VLC player plays it fine, though. :) The aspect ratio is 1:1, apparently, resulting in 720x576 video files. I guess it makes resizing easier?
No, it's just a bug. It is almost certainly 720x576 4:3 if it is from VHS, so anamorphic. I'd keep the resolution the same. But if you want square pixel, stretch it horizontally to 768x576. Although you probably want to crop to 704x576 first due to horizontal blanking.

The VCR being used is primarily a 2003 Panasonic NV-FJ623, with an older mono Sony SLV-135 whenever tracking becomes an issue.

The recording process is somewhat convoluted because I lack a composite to HDMi converter (I've ordered one, it just hasn't arrived yet). The signal from the VCR passes through a Sony DVD recorder (Sony RDR HX-710) via SCART. Then, the signal from the component output of the Sony recorder enters the Avermedia through the component input via a composite cable. It may seem terrible, but guess what, it works great, all things considered!
I am besotted with a heady mix of nostalgia and PTSD reading the above.

Can't you just get a capture card that can go composite to lossless or perceptually lossless 4:2:2? Or at least real-time to something better than an ASIC H.264? That'd be fewer steps and better quality. Doing 4:2:0 capture with interlaced is just buying yourself pain.

Another issue is light aliasing present in the original VHS playback, like this, albeit not as strong:
https://forum.videohelp.com/threads/390999-aliasing-when-capturing-analog-Component-v-s-S-video
What field order are you capturing with? It should be Top Field First for PAL, and you should consistantly use that throughout the pipeline. Bottom Field First got used for NTSC by default sometimes, so if you are reusing any NTSC workflows, things could get off.

[Cary Knoop]

Mixed interlaced and progressive content, frame rate doubled with a broken pattern.
Try
QTGMC()
selecteven()
It will return 50fps progressive video preserving the temporal resolution of the interlaced sections.
No, it won't.

[Sharc]

No, it won't.
So? What's your proposal then?

[tugatomsk9]

Can't you just get a capture card that can go composite to lossless or perceptually lossless 4:2:2? Or at least real-time to something better than an ASIC H.264? That'd be fewer steps and better quality. Doing 4:2:0 capture with interlaced is just buying yourself pain..

I'd like to get a proper video capture card, but my PC is too old and archaic, not to mention there are no PCIe slots available. Also, they are too overbudget for me at the moment. (Perhaps someday in the future, when I hope to upgrade to a fine machine... and redo some of the captures (not all) and, of course, if my VCRs still work by then. :))

I thought of something like those pen-drives that capture video just like you mentioned, but after my experience with a MAGIX one (poor quality), I wasn't sure about ElGato's similar options. And they were still more expensive than this 129€ Avermedia.

I also have plans to record videogames for Youtube purposes, so that might have also influenced my decision.


What field order are you capturing with? It should be Top Field First for PAL, and you should consistantly use that throughout the pipeline. Bottom Field First got used for NTSC by default sometimes, so if you are reusing any NTSC workflows, things could get off.

I believe it's Top Field First, but I can't tell for sure.

I live in Portugal, so all my recordings are PAL.

EDIT: I just realized I never uploaded the new video sample of the VHS tape in case. Here it is:

https://mega.nz/file/aZBSyQZY#cPYbb4OV8dOzM3oajvUt1-Eg-HzWg1ywo51OREItECs

[Cary Knoop]

So? What's your proposal then?
Something like this and then either duplicate or interpolate the frames to get to 25p?

sourcefile = 'G:/Vapoursynth/vid.mkv'
c = core.ffms2.Source(sourcefile)

c = core.std.SeparateFields(c, tff=True)
c = haf.srestore(c,frate=25)
c = core.std.DoubleWeave(c, tff=True)[::2]
c = hnw.QTGMC(c, TFF=True, Preset="Very Slow")
c = c[::2]
c.set_output(0)

[tugatomsk9]

Guys, I've just realized something: I messed up. :( This is not my original thread regarding VHS capture with an Avermedia capture device, this is:

https://forum.doom9.org/showthread.php?p=1906694#post1906694

I'm terribly sorry about this confusion. I guess I should migrate my newer posts there in order to do some damage control.