Can't decode with AviSynth

[NorthPole]

I have attached a 35 second H.264 HD cap that I haven't been able to decoded with avisynth on win7.

The video starts at 1920x1080i then switches to 720x480i then switches back to 1920x1080i.

I've tried dgavcindex (v1.0.9) and it crashes when it hits the change in resolution. I've also tried ffms2 (v2.15) and that also crashes at the resolution change and the video is quite jumpy.

The only thing that seems to work is directshowsource(...) but only on my Vista machine and not on my Win7 machine.

I'm using version 2.5.8 with the updated DirectShowSource.dll from 01/27/2010. On the Vista machine, it process fine but with Win7, the encoding just hang when it hits the resolution change.

Also, I was looking to get as frame accurate as possible with directshowsource. Any ideas anyone?

Thanks.

http://http://www.mediafire.com/?s9qbca6n5d3ci32

[poisondeathray]

use win7dsfiltertweaker on the win7 machine to enable ffdshow

if still doesn't work, then render file in graphstudio, and report back the results

try dss2 for "as frame accurate as possible" (avss.dll from haali)

[Didée]

Well, in Avisynth you cannot have different resolutions in the same file.

How does this actually work when you have it running with DSS in Vista? Are the 720x480 sections blown up to 1920x1080? And what about the interlacing structure?

[TheFluff]

FFMS2 is supposed to support inline resolution changes (everything gets rescaled to the resolution of the first frame, or to a given resolution if you specify it). It should definitely not crash. I'll take a look at the sample.

[NorthPole]

Ok, well I have had success.

Heres what I've found out. I had previously run win7dsfiltertweaker and had the Arcsoft filter set. Once I set it to anything else, both dss2 and directshowsource worked fine. I installed the ffdshow tryout beta7 and set that as the prefered with no deinterlacing and got the results I was looking for.

Interestingly, I can also get the cyberlink decoder to work properly as well although my encoder can't determine if the source is interlaced (telecined). With ffdshow, my encoder correctly determined the telecine and field order.

I did two encodes using the ffdshow filter, one with dss2 and the other with directshowsource. I encoded the video as telecined into mpg format and ran dgindex and opened it in vdub to see what I got.

The dss2 encode shows no movement in the raindrops in the first 7 frames (fields) and reports 1055 frames (fields). The directshow encode shows movement in the raindrops right way and reports 1056 frames (fields).

Not sure which one is more field accurate.

[NorthPole]

Well, in Avisynth you cannot have different resolutions in the same file.

How does this actually work when you have it running with DSS in Vista? Are the 720x480 sections blown up to 1920x1080? And what about the interlacing structure?

I'll try a few samples and report back. On the win7 machine with ffdshow, the 720x480 video section is centered within the 1920x1080 screen.

[NorthPole]

FFMS2 is supposed to support inline resolution changes (everything gets rescaled to the resolution of the first frame, or to a given resolution if you specify it). It should definitely not crash. I'll take a look at the sample.

FFMS2 acted exactly like dgavcindex did with the sample, runs ok until it hits the resolution change and then crashes.

[NorthPole]

Well, in Avisynth you cannot have different resolutions in the same file.

How does this actually work when you have it running with DSS in Vista? Are the 720x480 sections blown up to 1920x1080? And what about the interlacing structure?

After running some futher test, both win7 and vista generate the same results depending on the directshow decoder. If ffdshow is used, the 720 video stays at 720 but center in the middle of a the screen. If the cyberlink decoder is used, the video is blown up to 1920x1080.

[NorthPole]

use win7dsfiltertweaker on the win7 machine to enable ffdshow

if still doesn't work, then render file in graphstudio, and report back the results

try dss2 for "as frame accurate as possible" (avss.dll from haali)

Thank you for the suggestion. Your solution generates the results that I was looking for.