USB Capture for VHS and DV8

[Alwyn]

Each PCIe card I have put in my machine (admittedly Win 11) has shown up in Device Manager without driver installation on my part. The TI card didn't work as far as transfer goes but it was definitely showing as installed in the computer. The Tunghey VIA card worked "out of the box".

You could try it in another machine, since you have a couple. If it's not showing up in those, then it could be DOA.

doing this on the iMac (buts its not the fastest and definitely not very up to date, hence wanting to to get the PC working).

Your Mac should do it easily. DV "transfer' is a doddle. I was doing it on a Pentium machine 15 years ago with no problems.

[DB83]

Just for clarity, when you say "The intended machine would be running...." does that mean, at present, Windows 7 is not installed on that PC ?

I did not see "Texas Instrument" on the product description but I might have over-looked that. But it should still be evident on the actual chip.

[Alwyn]

I did not see "Texas Instrument" on the product description

My interest was piqued by DB83's (lack of) observation so I had a look. I notice that that card has drivers to be downloaded. None of my Firewire cards have had specific drivers.

Perhaps it does have specific drivers that are needed as well as the "standard" Windows inbuilt driver (although I see one of the available drivers is called "Legacy"...).

[JonnyAlpha]

Just for clarity, when you say "The intended machine would be running...." does that mean, at present, Windows 7 is not installed on that PC ?

I did not see "Texas Instrument" on the product description but I might have over-looked that. But it should still be evident on the actual chip.

The onboard chip is a XI02213BZAY.

On the Texas Instruments Website it lists an XI02213BA which I hope is the same chips and is a x1 PCIe to 1394 Host Controller.

[JonnyAlpha]

I did not see "Texas Instrument" on the product description

My interest was piqued by DB83's (lack of) observation so I had a look. I notice that that card has drivers to be downloaded. None of my Firewire cards have had specific drivers.

Perhaps it does have specific drivers that are needed as well as the "standard" Windows inbuilt driver (although I see one of the available drivers is called "Legacy"...).

See above ref the chipset.

Anyway I dug out another PC, that used to dual boot Windows 7 and XP on separate HDDs (that bit stopped working last few times I remember using it. Been in my garage not used for a few years.
Wiped off the dust and fire it up. It booted into XP. I switched the Boot drive and now it boots into Windows 7.
The Motherboard is an Abit ANM2-HD which has a 1394 connector on the motherboard.

Before I installed the PCIe card the 1394 Host Controller is visible in Device Manager as a Texas Instruments device, assuming due to the onboard 1394.

Anyway I put the PCIe Firewire Card and there was no change in Device Manager - should it have also shown the Syba card listed as a separate sub device?
Following the Studio 1 guide linked in my previous posts above, I changed the driver to Microsofts Legacy Driver.
Now this is what it shows.


[Attachment 75299 - Click to enlarge]

I guess I won't know if the FireWire Card is working until my cable turns up - still waiting!!!

[DB83]

The only thing I will add since AFAIK Windows 7 does not require a legacy driver (drivers should be part of the OS since it was only when Win 10 stopped natively supporting firewire/1394 that legacy (specifically Win8) drivers came into play)

Personally, I try to ignore any personal comments by Alwyn. Maybe I upset him in the past (I do not remember) but if he wants to be a good servant of these forums he really needs to concentrate on fact (and if he has NEVER done ANY DV transfer on a Mac he should not even comment on that) and not fallacy (or personal grudge).


And, for the record, I have no idea if these two chips are one and the same.

[Alwyn]

Anyway I put the PCIe Firewire Card and there was no change in Device Manager - should it have also shown the Syba card listed as a separate sub device?

Good question. Perhaps not. The system already knows it has Firewire in it, on the motherboard. I would remove the Syba card as it is not needed. My old machine had onboard Firewire and it has worked without issue on XP and then Win 7. I don't recall what driver was being used ie Legacy or otherwise, although I note David Knarr suggests using the Legacy driver for Win 7. I'm not sure what he is getting at there; my understanding is that the system driver in Win 7 is the one you want. That may be the "legacy" driver but I wouldn't be installing the MSI file over the top of the system driver unless the system driver didn't work.

DB, you said "I did not see 'Texas Instrument'" so I said "DB83's (lack of) observation". I'm sorry if I offended you with that. I wasn't being critical. As for concentrating on fact, I said "should" not "will". In any case, you're being a bit hypocritical because you made a comment "That connector looks DOA" earlier on. You have no idea if that is fact or not.

[DB83]

Maybe I missed somat but with all the various PCs that the OP is trying it is quite hard, for me, to establish which one(s) are responding.

Now here's a potential issue. Any firewire connector beit on on the front or back of a PC is 'wired' to the mainboard. The wire may be soldered but with mine it has a pin connector - and you really do need a manual to determine where it goes for the next comment.


Now I could well be wrong but let's just assume for one minute that any PC can only have one 1394 host interface. Plugging in a pci-e card expecting that to also work may be dissilusional due to conflict. So, to be sure, any wires from the visible port(s) need to be disconnected first.


As for the Mac, I will not go there since I have no knowledge of these systems.

[JonnyAlpha]

I did not see "Texas Instrument" on the product description

My interest was piqued by DB83's (lack of) observation so I had a look. I notice that that card has drivers to be downloaded. None of my Firewire cards have had specific drivers.

Perhaps it does have specific drivers that are needed as well as the "standard" Windows inbuilt driver (although I see one of the available drivers is called "Legacy"...).

See above ref the chipset.

Anyway I dug out another PC, that used to dual boot Windows 7 and XP on separate HDDs (that bit stopped working last few times I remember using it. Been in my garage not used for a few years.
Wiped off the dust and fire it up. It booted into XP. I switched the Boot drive and now it boots into Windows 7.
The Motherboard is an Abit ANM2-HD which has a 1394 connector on the motherboard.

Before I installed the PCIe card the 1394 Host Controller is visible in Device Manager as a Texas Instruments device, assuming due to the onboard 1394.

Anyway I put the PCIe Firewire Card and there was no change in Device Manager - should it have also shown the Syba card listed as a separate sub device?
Following the Studio 1 guide linked in my previous posts above, I changed the driver to Microsofts Legacy Driver.
Now this is what it shows.


[Attachment 75299 - Click to enlarge]

I guess I won't know if the FireWire Card is working until my cable turns up - still waiting!!!

So cable arrived and last night I tested it in the old PC importing using iMovie. Info on my Mac thread here, but it imported ok and I exported the video in this old version of iMove (08). What I need to confirm is that:
(a) I am importing the video in the correct format
(b) That I export the video in the correct format, to ensure that I save these memories in the best quality possible.

Back to Windows
So this morning I tried the FireWire Card again. First I disabled the onboard Firewire and confirmed that it had disappeared from Device Manager.
Then I shutdown and plugged the FireWire Card in and booted up.
The card was still not seen in Device Manager.
I tried to install the Legacy Drivers but the .inf file will not install.
So after this card not working in two older Windows 7 PCs I am nearing the conclusion that it is DOA.

After re-enabling the onboard FireWire, I downloaded and installed WinDV and plugged the Camera in. As soon as the camera switched on, it was recognised as an imaging device in Device Manager.


[Attachment 75327 - Click to enlarge]

And a window automatically appeared asking if I wanted to import the video, not sure if this had anything to do with WinDV?


[Attachment 75328 - Click to enlarge]

After capturing a short clip in WinDV I checked the playback quality of the captured video clip.
In Windows Media Player the clip seemed OK:


[Attachment 75329 - Click to enlarge]

However in VLC it is washed out (newly downloaded version of VLC:


[Attachment 75330 - Click to enlarge]

When I right click on the captured video clip file and select the 'Details' tab these are the settings:


[Attachment 75331 - Click to enlarge]

can anyone help with getting the correct import and export settings.

I guess I need to read a guide on here ref capturing and encoding DV?

Thanks for all the help so far.

[Alwyn]

Excellent, we have a connection!

I did mention above: if you have Firewire on your motherboard, do not insert that PCIe card.

The "Import Video" screen is a Windows screen: close it.

If you are able to "import" (better, "transfer") some video with WinDV, that's great, because it can't do anything with the data except just transfer it. Just what you want for DV.

I can't explain VLC's spazzo on the video.

A great program for analysing files is Mediainfo. After installing, open a video file in it, go to View>Text, and you'll get a heap of data on the file. In this case, the critical field is the Video Format. If it says DV or similar, you're in business.

You can set up WinDV to capture one long file or break it up into clips and named by date and time taken. I've let WinDV fall by the wayside because it no longer works for me, I use Scenalyzer. If WinDV works for you though, great. If you go onto the WinDV website, there is a great interactive feature (mouse pointer on each part of the screen) that explains each part.

Once you've transferred the video onto your PC, you can edit, deinterlace, recode into MP4for general viewing. DV files generally are not supported by TVs. The only way I can play my DV files is through the Apple TV, but MP4s are playable by everything.

[Alwyn]

Import settings will be dictated by the file data: you don't want to fiddle with that at all. PAL DV is 720x576, 4:3 ratio (some later DV was recorded in 16:9 but will still be 720x576 pixel size) at approx 13GB per hour. Here's the MediaInfo report on a bog-standard DV file after transfer:

General
Complete name : H:\Comparisons\DV Analogue\Front Yard Nov2023\Gs25 DV'20000101 00.00.00.avi
Format : AVI
Format/Info : Audio Video Interleave
Commercial name : DVCAM
Format settings : BitmapInfoHeader / WaveFormatEx
File size : 170 MiB
Duration : 46 s 760 ms
Overall bit rate mode : Constant
Overall bit rate : 30.4 Mb/s
Frame rate : 25.000 FPS
Recorded date : 2000-01-01 00:00:00.000
TAPE : sclive

Video
ID : 0
Format : DV
Commercial name : DVCAM
Codec ID : dvsd
Codec ID/Hint : Sony
Duration : 46 s 760 ms
Bit rate mode : Constant
Bit rate : 24.4 Mb/s
Width : 720 pixels
Height : 576 pixels
Display aspect ratio : 4:3
Frame rate mode : Constant
Frame rate : 25.000 FPS
Standard : PAL
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan order : Bottom Field First
Compression mode : Lossy
Bits/(Pixel*Frame) : 2.357
Time code of first frame : 00:00:00:17
Time code source : Subcode time code
Stream size : 161 MiB (95%)

Audio
ID : 1
Format : PCM
Format settings : Little / Signed
Codec ID : 1
Duration : 46 s 760 ms
Bit rate mode : Constant
Bit rate : 1 536 kb/s
Channel(s) : 2 channels
Sampling rate : 48.0 kHz
Bit depth : 16 bits
Stream size : 8.56 MiB (5%)
Alignment : Aligned on interleaves
Interleave, duration : 497 ms (12.44 video frames)

I've resurrected my WinDV transfer/capture tute.

[DB83]

As Alwyn mentioned, install mediainfo and send a text-mode report of that clip.

The vlc 'window' looks odd so I suggest you look at the video settings for that rather than blame the DV clip.


Even so, the bitrate for the DV clip is much higher than what is to be expected. Hence the need to see what mediainfo is reporting.

[JonnyAlpha]

Here's the Media Info on the 4s clip:

General
Complete name : C:\Users\JonnyAlpha\Downloads\WinDV-1.2.3\.07-01-06_18-16.00.avi
Format : AVI
Format/Info : Audio Video Interleave
Commercial name : DVCAM
Format settings : BitmapInfoHeader / WaveFormatEx
File size : 15.3 MiB
Duration : 4 s 160 ms
Overall bit rate mode : Constant
Overall bit rate : 30.8 Mb/s
Frame rate : 25.000 FPS
Recorded date : 2007-01-06 18:16:41.000

Video
ID : 0
Format : DV
Commercial name : DVCAM
Codec ID : dvsd
Codec ID/Hint : Sony
Duration : 4 s 160 ms
Bit rate mode : Constant
Bit rate : 24.4 Mb/s
Width : 720 pixels
Height : 576 pixels
Display aspect ratio : 4:3
Frame rate mode : Constant
Frame rate : 25.000 FPS
Standard : PAL
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan order : Bottom Field First
Compression mode : Lossy
Bits/(Pixel*Frame) : 2.357
Time code of first frame : 00:00:33:09
Time code source : Subcode time code
Stream size : 14.3 MiB (94%)

Audio
ID : 1
Format : PCM
Format settings : Little / Signed
Codec ID : 1
Duration : 4 s 160 ms
Bit rate mode : Constant
Bit rate : 1 536 kb/s
Channel(s) : 2 channels
Sampling rate : 48.0 kHz
Bit depth : 16 bits
Stream size : 780 KiB (5%)
Alignment : Aligned on interleaves
Interleave, duration : 40 ms (1.00 video frame)
Interleave, preload duration : 40 ms

[JonnyAlpha]

Import settings will be dictated by the file data: you don't want to fiddle with that at all. PAL DV is 720x576, 4:3 ratio (some later DV was recorded in 16:9 but will still be 720x576 pixel size) at approx 13GB per hour. Here's the MediaInfo report on a bog-standard DV file after transfer:

General
Complete name : H:\Comparisons\DV Analogue\Front Yard Nov2023\Gs25 DV'20000101 00.00.00.avi
Format : AVI
Format/Info : Audio Video Interleave
Commercial name : DVCAM
Format settings : BitmapInfoHeader / WaveFormatEx
File size : 170 MiB
Duration : 46 s 760 ms
Overall bit rate mode : Constant
Overall bit rate : 30.4 Mb/s
Frame rate : 25.000 FPS
Recorded date : 2000-01-01 00:00:00.000
TAPE : sclive

Video
ID : 0
Format : DV
Commercial name : DVCAM
Codec ID : dvsd
Codec ID/Hint : Sony
Duration : 46 s 760 ms
Bit rate mode : Constant
Bit rate : 24.4 Mb/s
Width : 720 pixels
Height : 576 pixels
Display aspect ratio : 4:3
Frame rate mode : Constant
Frame rate : 25.000 FPS
Standard : PAL
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan order : Bottom Field First
Compression mode : Lossy
Bits/(Pixel*Frame) : 2.357
Time code of first frame : 00:00:00:17
Time code source : Subcode time code
Stream size : 161 MiB (95%)

Audio
ID : 1
Format : PCM
Format settings : Little / Signed
Codec ID : 1
Duration : 46 s 760 ms
Bit rate mode : Constant
Bit rate : 1 536 kb/s
Channel(s) : 2 channels
Sampling rate : 48.0 kHz
Bit depth : 16 bits
Stream size : 8.56 MiB (5%)
Alignment : Aligned on interleaves
Interleave, duration : 497 ms (12.44 video frames)

I've resurrected my WinDV transfer/capture tute.

Sorry can't read it?


[Attachment 75338 - Click to enlarge]

[dellsam34]

Just use SClive to transfer and don't worry about what VLC or Mediainfo show.

[DB83]

Yes, that guide is a visual 'mess'

But no need to worry. Compare Alwyn's mediainfo report and yours and the critial info is identical. So what you have done is fine. As to what MS is reporting is anyone's guess.


But I would still read the guide prepared by WinDV's author. There is a setting if you do not want each and every time you started your camera to be transfered as a separate clip. Under discontinuity threshold from 'Config' set it to 0 and the whole tape is captured as one.


And WinDV is fine especially on a Win7 system.

[Alwyn]

Sorry about my resurrected WinDV guide. I was in a rush to bed. Fixed now, you'll probably need to clear your browser cache to get rid of the corrupted page data. For Chrome>three dots menu>Clear Browsing Data>untick everything except "Cached Images and Files">"Clear Data".

Corrected guide for WinDV here.

[DB83]

Works ok for me now (not that I needed it) and without any browser settings.

[Alwyn]

Thanks DB.

[JonnyAlpha]

Sorry about my resurrected WinDV guide. I was in a rush to bed. Fixed now, you'll probably need to clear your browser cache to get rid of the corrupted page data. For Chrome>three dots menu>Clear Browsing Data>untick everything except "Cached Images and Files">"Clear Data".

Corrected guide for WinDV here.

Thanks Alwyn, sorted now.

[JonnyAlpha]

Excellent, we have a connection!

I did mention above: if you have Firewire on your motherboard, do not insert that PCIe card.

The "Import Video" screen is a Windows screen: close it.

If you are able to "import" (better, "transfer") some video with WinDV, that's great, because it can't do anything with the data except just transfer it. Just what you want for DV.

I can't explain VLC's spazzo on the video.

A great program for analysing files is Mediainfo. After installing, open a video file in it, go to View>Text, and you'll get a heap of data on the file. In this case, the critical field is the Video Format. If it says DV or similar, you're in business.

You can set up WinDV to capture one long file or break it up into clips and named by date and time taken. I've let WinDV fall by the wayside because it no longer works for me, I use Scenalyzer. If WinDV works for you though, great. If you go onto the WinDV website, there is a great interactive feature (mouse pointer on each part of the screen) that explains each part.

Once you've transferred the video onto your PC, you can edit, deinterlace, recode into MP4for general viewing. DV files generally are not supported by TVs. The only way I can play my DV files is through the Apple TV, but MP4s are playable by everything.

So,

Now that I can capture the DV files, what software do you recommend for editing and de-interlacing the video and re-encodiing it to mp4? What settings are best for general viewing?

Prior to posting up on here, I contacted a friend of mine (who used to do a lot of CCTV work with Mini DV tapes), he used to have a Mini DV player and cables, but sadly thinks he got rid of it all Anyway when we were chatting, he mentioned that back in the day when DV was popular, companies used to use extra fast HDDs to save the video on 10K RPM, along with hardware / software to stop them spinning down when writing data. Without this you are at risk of losing frames and getting audio 'pops'.

DV Capture Storage
So what's the best storage media for saving the original DV and then saving the encoded video to?

[DB83]

The simplest program to convert is avidemux. That being said you still need the knowledge of settings. but that is why we are here.

I have not the foggiest of what your friend is talking about. We have a digital file. RPMs do not come in to the equation.


Storage media . Practically anything. And anything not permanently connected to the initial storage. So no internal HDDs but anything else. But when you encode by all means use the internal storage (separate HDD prefered) having backed up the initial capture first.

[dellsam34]

Now that I can capture the DV files, what software do you recommend for editing and de-interlacing the video and re-encodiing it to mp4? What settings are best for general viewing?

Depends on who you talk to, There is a wide variety of tools and methods people use, from full fledged NLE, to simple apps and script based processes.

For DV/DVCAM/D8, I personally decode the video first to get rid of the DV codec using vdub2 into HuffYUV, Once the video is in its AVI lossless form (though DV loss can never be recovered), any processing you do to it is minimal. I start with a quick QTGMC de-interlace, followed by a resize to 1440x1080 then encode to h.264. For Youtube I just upload the de-interlaced HuffUYV version and let YT do the encoding.

Depends on the quality of the imaging sensor the camcorder used, the average DV quality after processing would look like this.

I haven't processed DV/DVCAM tapes from pro camcorders, I would assume the quality in those is somehow better.

[Alwyn]

The next step in the process depends on how seriously you want to get into it. At the most basic level, you just trim off the bad bits, deinterlace it, perhaps crop off the black bars on the sides and denoise it and then export it into MP4 format for distribution. If you want to do more, a full-blown Non Linear Editor gives you endless editing possibilities such as re-ordering clips and adding other clips, titles, soundtracks, effects and easy export options, all in a fully visual environment.

Probably the biggest bogeyman is deinterlacing. Arguments rage on the internet (well, at least here on VH) about the need to deinterlace at all. For Youtube, you should deinterlace. The Deinterlacing process itself is a tradeoff between quality and complexity. AVISynth+QTGMC gives the best result but is complicated to set up. Other programs such as VDub, AVIDemux and Handbrake will all deinterlace fairly well and are more user-friendly/GUI-based.

I have a start-to-finish tute using only VirtualDub 2 here. Have a read to get a handle on the process. It's a case of learning to crawl before you start walking, and though that process may not suit your eventual desired needs, you'll develop the knowledge to understand what's involved to help you decide how far you want to go.

My workflow: Capture/Transfer>In VDub, Deinterlace, crop, resize to 768x576>export in lossless AVI format (I use MagicYUV codec for my NLE but others are HUFFYUV, Lagarith, UT video) >Import into my NLE (Magix Movie Studio) > edit (eg denoising, audio adjustments, colour adjust, further cropping/zooming, re-ordering clips, titles)>Resize if desired and Export to MP4. There are plenty of other NLEs out there, both free and paid.

he mentioned that back in the day when DV was popular, companies used to use extra fast HDDs to save the video on 10K RPM, along with hardware / software to stop them spinning down when writing data. Without this you are at risk of losing frames and getting audio 'pops'.

None of that applies these days. Systems are so fast, dealing with DV is a doddle and no special drives are needed.

So what's the best storage media for saving the original DV and then saving the encoded video to?

It's great you're thinking of this. I have two offsite (in the shed!) backups, both different-brand HDDs. I have about 10TB backed up. I use Freefilesync: nothing flash, just a file-to-file compare and update. Other options include Bluray disks for the final exports (at around 2GB per hour). It's up to you whether you continue to keep the original capture/transfer files after you have processed them (as above). You may want to revisit the projects later on in life and so it would be best to use the originals for that; re-editing MP4s is not ideal.

[JonnyAlpha]

The next step in the process depends on how seriously you want to get into it. At the most basic level, you just trim off the bad bits, deinterlace it, perhaps crop off the black bars on the sides and denoise it and then export it into MP4 format for distribution. If you want to do more, a full-blown Non Linear Editor gives you endless editing possibilities such as re-ordering clips and adding other clips, titles, soundtracks, effects and easy export options, all in a fully visual environment.

Probably the biggest bogeyman is deinterlacing. Arguments rage on the internet (well, at least here on VH) about the need to deinterlace at all. For Youtube, you should deinterlace. The Deinterlacing process itself is a tradeoff between quality and complexity. AVISynth+QTGMC gives the best result but is complicated to set up. Other programs such as VDub, AVIDemux and Handbrake will all deinterlace fairly well and are more user-friendly/GUI-based.

I have a start-to-finish tute using only VirtualDub 2 here. Have a read to get a handle on the process. It's a case of learning to crawl before you start walking, and though that process may not suit your eventual desired needs, you'll develop the knowledge to understand what's involved to help you decide how far you want to go.

My workflow: Capture/Transfer>In VDub, Deinterlace, crop, resize to 768x576>export in lossless AVI format (I use MagicYUV codec for my NLE but others are HUFFYUV, Lagarith, UT video) >Import into my NLE (Magix Movie Studio) > edit (eg denoising, audio adjustments, colour adjust, further cropping/zooming, re-ordering clips, titles)>Resize if desired and Export to MP4. There are plenty of other NLEs out there, both free and paid.

he mentioned that back in the day when DV was popular, companies used to use extra fast HDDs to save the video on 10K RPM, along with hardware / software to stop them spinning down when writing data. Without this you are at risk of losing frames and getting audio 'pops'.

None of that applies these days. Systems are so fast, dealing with DV is a doddle and no special drives are needed.

So what's the best storage media for saving the original DV and then saving the encoded video to?

It's great you're thinking of this. I have two offsite (in the shed!) backups, both different-brand HDDs. I have about 10TB backed up. I use Freefilesync: nothing flash, just a file-to-file compare and update. Other options include Bluray disks for the final exports (at around 2GB per hour). It's up to you whether you continue to keep the original capture/transfer files after you have processed them (as above). You may want to revisit the projects later on in life and so it would be best to use the originals for that; re-editing MP4s is not ideal.

I have had a look at your guide and have installed VirtualDub2 and started to have a play. In the guide it warns that some actions need to be carried out before others, e.g. Cropping WARNING - DeInterlace First before cropping and resizing.

Dose this mean open the video clip, set the de-interlacing and noise filters then apply the changes? How do you apply the changes? Do you simply hit File / Save Video? Does this overwrite the capture and if so I guess i should 'Save' the edited video in a separate folder.

[Alwyn]

Dose this mean open the video clip, set the de-interlacing and noise filters then apply the changes?

VDub runs the filters in the order you've got them in the filters list, and they all get run, from top to bottom, as soon as you hit OK on the Filter window. You will see the result of the filters you've set up in the right hand pane. For example, find a bit of vidoe with motion, so the jaggies (interlace lines) are visible in the original (left) pane. Apply the Deinterlace filter and as soon as you hit OK to close the filter window, you'll see the jaggies disappear from the video in the right pane as the video is deinterlaced.

Re the filter order, Deinterlace first, then do the others eg cropping, resizing, colour adjustments. You can change the filter order by using the move up/down buttons.

When you're all set with your filters and the result looks like what you want in the right hand pane, go ahead and "Save Video..." as per the instructions.

[lollo]

DeInterlace First before cropping

Not really. Cropping should be before deinterlacing, because the top and bottom good lines could be affected by bad lines present at the top and the bottom of a capture, generating small flickering. For interlaced material check appropriate mod for cropping if source is in YV12 colorspace

For QTGMC, some details here: http://avisynth.nl/index.php/QTGMC#Miscellaneous_Settings

[DB83]

The 'discussion' crop before or after will never go away.

The simplistic arguement is, for me, if you do not understand field structure you deinterlace first since one sees so many a video with artifacts that would have been avoided otherwise. And more so since cropping also typically comes with resizing.


Just my own 2 cents.

[lollo]

I agree, but in general the damages we see are caused by resizing before deinterlacing.
The field structure has nothing to do.
The cropping before deinterlacing can introduce a problem if you do not respect the appropriate mod according to the source.

[JonnyAlpha]

Dose this mean open the video clip, set the de-interlacing and noise filters then apply the changes?

VDub runs the filters in the order you've got them in the filters list, and they all get run, from top to bottom, as soon as you hit OK on the Filter window. You will see the result of the filters you've set up in the right hand pane. For example, find a bit of vidoe with motion, so the jaggies (interlace lines) are visible in the original (left) pane. Apply the Deinterlace filter and as soon as you hit OK to close the filter window, you'll see the jaggies disappear from the video in the right pane as the video is deinterlaced.

Re the filter order, Deinterlace first, then do the others eg cropping, resizing, colour adjustments. You can change the filter order by using the move up/down buttons.

When you're all set with your filters and the result looks like what you want in the right hand pane, go ahead and "Save Video..." as per the instructions.

This confused me as I only just found that cropping is accessible from within the filters list, I thought it was a separate process.
What I am struggling to find is a stepo by step guide on editing DV and then exporting for general viewing, I guess though not one guide fits all