Log in

View Full Version : DV to DVD encoding issues


puddy
20th August 2009, 01:31
Been reading and doing a lot of trial and error and I just can't seem to get this right.

Running WinXP SP3.

My source is a Canon ZR100 (NTSC) miniDV camcorder. I'm capturing via Firewire using WinDV.

I'm using the Cedocida DV Codec with only YUY2 checked in the Decoder output formats section. I've confirmed that this codec is set active in the registry for Vidc.dvsd

I'm reading that DV Video is always BFF. I am used to working with TFF video only. So all my AviSynth scripts are written for TTF.

Here's my modified avs script for dealing with the BFF video.

# AVS Script for BFF DV Video
#
Setmemorymax(1536)
Load_Stdcall_plugin("C:\Program Files\AviSynth 2.5\plugins\yadif.dll")

AviSource("G:\VideoCapture\tape1.09-08-18_23-30.00.avi")
Trim(96877,97776)

AssumeBFF()
yadif(mode=1, order=0)
HDRAGC(coef_gain=1, max_gain=4, min_gain=0, min_sat=1.0, max_sat=1.5, black_clip=.4, corrector=.8, reducer=1.0, debug=0)
FFT3DGPU(sigma=4, bt=3, bw=32, bh=32, ow=16, oh=16, sharpen=1, interlaced=false)

AssumeBFF()
SeparateFields()
SelectEvery(4,1,2)#if BFF
Weave()

FadeOut2(55)
FadeIn2(55)



I am encoding using CCE-SP2. The critical settings here are:
Output top field first is CHECKED
Offset line = 0

My resulting video looks ok when viewed on the monitor, but when burned to DVD and watched on a regular TV it is strange. Low motion parts look almost progressive and fast motion has the jerky feel.

I've tried several variations of changing the CCE settings, but nothing seems to work. In some cases the results are worse but never correct.

I am just not sure what I'm missing.

If there's info that I should have supplied that would help solve this mystery, please let me know. I'd be glad to fill in any gaps.

Thank you!

Ghitulescu
20th August 2009, 09:21
http://forum.doom9.org/showthread.php?t=135690

2Bdecided
20th August 2009, 16:36
There are websites out there that still incorrectly suggest using SelectEvery(4,1,2) - that's a source of confusion!

btw, I'd probably do the fades before re-interlacing, otherwise you have interlaced footage with progressive fades (which is fine, and slightly easier to encode, but the fades aren't as smooth as the footage).

Cheers,
David.

puddy
20th August 2009, 17:09
http://forum.doom9.org/showthread.php?t=135690

Thank you. I read through that thread. As a test I modified my avs script to test each of the 4 scenarios laid out by scharfis_brain while keeping the rest of my script the same as in my original post. All other settings outside aviscript were kept the same as well (WinDV, Cedocida codec, CCE).


1. AssumeTFF().SeparateFields().SelectEvery(4, 0, 3).Weave() -> TFF
2. AssumeBFF().SeparateFields().SelectEvery(4, 0, 3).Weave() -> BFF
3. AssumeTFF().SeparateFields().SelectEvery(4, 1, 2).Weave() -> BFF
4. AssumeBFF().SeparateFields().SelectEvery(4, 1, 2).Weave() -> TFF

RESULTS:
1. Low motion looks progressive, fast motion jerky.
2. Low motion looks interlaced/jerky, fast motion appears smooth.
3. Low motion looks interlaced/jerky, fast motion appears smooth.
4. Low motion looks progressive, fast motion jerky.

None of them look correct. So I can only assume my issue lies elsewhere. I guess it could have something to do with the capture/transfer into WinDV, a Cedocida codec issue, yadif deinterlace issue or CCE settings.

I never have any issues like this with captured analog video, which is TFF.

btw, I'd probably do the fades before re-interlacing, otherwise you have interlaced footage with progressive fades (which is fine, and slightly easier to encode, but the fades aren't as smooth as the footage).

I thought it didn't matter where you placed the fade commands within the avs script? I'll have to mess around with that. I never noticed any issues with the fades before.

Sorry guys, I know for some of you this is just second nature, but I just can't seem to parse it out.

:thanks:

Ghitulescu
20th August 2009, 19:10
Sorry, I cannot help you further, I never needed to process my DV footage in avisynth/vdub. I understand that some filters work better if they process a progressive frame, thus I suggest you to do the field separation before any of these filters, and reweaving back after them.

For me, if you have red my posts, I use hardware encoders. Long time ago, when I used CCE (gosh, I had time then :)), I simply selected BFF and DVD compliant and that was all (well, apart from quality settings :)).

I assume you have red the sticky -> http://forum.doom9.org/showthread.php?t=60392

Ghitulescu
21st August 2009, 09:38
I've rered your first post again.

Have you resent the "worked-out" DV AVI file back to your camcorder (DV deck?) to check it on a real TV (camcorder->TV) in comparison to your original footage (which I hope you still have it)?

It's a common mistake to judge a DV footage by looking it on PC.

puddy
21st August 2009, 14:19
I'm actually burning it to a rewritable DVD and checking on a standard TV using a standard DVD player.

There is just something not quite right in this process chain. I successfully create tons of DVD's from S-Video captured sources (Hi8, VHS). These are all TFF.

Working with DV over firewire is new to me. Since I tried all 4 SelectEvery combinations and none of them worked correctly, I can only assume the issue is elsewhere in my process chain.

Ghitulescu
21st August 2009, 17:02
I'm actually burning it to a rewritable DVD and checking on a standard TV using a standard DVD player.

I know that, you said it before.

It's not what I said, do this over the WE and compare the results. This way you can exclude a bad transcoding of the footage into MPEG2.

If there's no difference, then you may either edit your options in CCE, or, this is what I like, send it directly to a DVD recorder in its highest quality (since a DV tape is anyway 60min).

puddy
21st August 2009, 20:50
Well, I feel a little foolish. I hooked up the miniDV directly to the TV and played the tape. Turns out low motion simply has that progressive look and fast motion has some stuttering and jerkiness. It was in the original the whole time!

No clue why, it is an older camera. It is not mine, so I wasn't familiar with the look of the video shot with the camera. I was simply being over sensitive.

Here's the avs script I ended up using:
# AVS Script for BFF DV Video
#
Setmemorymax(1536)
Load_Stdcall_plugin("C:\Program Files\AviSynth 2.5\plugins\yadif.dll")

AviSource("G:\VideoCapture\tape1.09-08-18_23-30.00.avi")

ReInterpolate411()

yadif(mode=1, order=0)
HDRAGC(coef_gain=1, max_gain=4, min_gain=0, min_sat=1.0, max_sat=1.5, black_clip=.4, corrector=.8, reducer=1.0, debug=0)
FFT3DGPU(sigma=4, bt=3, bw=32, bh=32, ow=16, oh=16, sharpen=1, interlaced=false)

FadeOut2(55)
FadeIn2(55)

AssumeBFF().SeparateFields().SelectEvery(4, 1, 2).Weave()


In CCE-SP2 I DO check the "Output top field first" setting and keep Offset line = 0.

I made no other changes to the way I brought in the video using WinDV or with the Cedocida DV Codec.

So, I think there was never a problem in the first place. Very strange.

Thanks everyone!