MPEG2Dec3 v0.9 for Avisynth 2.5

[lighty]

Originally posted by Gannjunior
Any Suggestion?

Pls read this thread more carefuly. Use mpeg2dec3_0.93b. You can download it form Marc FD's site. Look for link in his sig.

[trbarry]

avoid to change anything in DVD2AVI. i ignore many parameter, and something may pass trought. i think i'll remove the croping stuff in a next verison. and some other small changes. but it's very low priority.

Marc -

Are you sure you really want to remove the cropping support? (not resize, which would be hard, and shouldn't be done in MPEG2DECx)

There are probably only half a dozen instructions somewhere in store.cpp that support the cropping by gimmicking the start offset and size. Likely the only problem is the adjustment for vertical cropping is off by a factor of 2 for YV12 instead of YUY2. I am goint to still support in in MPEG2DEC2 when I finally get around to it. (except I"m also using yours now )

But if we are to remove the cropping support I have an alternate proposal. It would be nice if some of the parms (resize, cropping, etc.) that can be nicely and interactively set in DVD2AVI just be passed on to Avisynth where they would appear as variables, which could be referred to in functions and scripts.

So if there were vars like "DVD2AVI_Crop_Left", DVD2AVI_Horiz_Size, etc., then the actual work could be done in Avisynth after IVTC/deinterlacing where it belongs, and possibly after other filters. We could write our own custom scripts and still refer to the choices made interactively in DVD2AVI where you can see what you are cropping/sizing. Even choices like Force Film or PC/TV scale could be passed on, for whatever use.

Just a thought.

- Tom

[Marc FD]

>Are you sure you really want to remove the cropping support?

in fact, no. if i do something with MPEG2Dec3, it'ld only be bugfixes.

>There are probably only half a dozen instructions somewhere in >store.cpp that support the cropping by gimmicking the start offset and >size.

or call Crop() after MPEG2Source.

>Likely the only problem is the adjustment for vertical cropping is off >by a factor of 2 for YV12 instead of YUY2. I am goint to still support >in in MPEG2DEC2 when I finally get around to it. (except I"m also >using yours now )

please take MPEG2Dec3 v0.93 source code and work on it. i'm not going to update the code, so YOU could continue to improve it. (like adding proper cropping).

>But if we are to remove the cropping support I have an alternate
>proposal. It would be nice if some of the parms (resize, cropping,
>etc.) that can be nicely and interactively set in DVD2AVI just be
>passed on to Avisynth where they would appear as variables, which
>could be referred to in functions and scripts.

for me, Avisynth/VirtualDub is interactive enough. i don't like DVD2AVI ^^.

>So if there were vars like "DVD2AVI_Crop_Left", DVD2AVI_Horiz_Size, >etc., then the actual work could be done in Avisynth after >IVTC/deinterlacing where it belongs, and possibly after other filters. >We could write our own custom scripts and still refer to the choices >made interactively in DVD2AVI where you can see what you are >cropping/sizing. Even choices like Force Film or PC/TV scale could be >passed on, for whatever use.

if a filter can create global vars (sh0dan do you know more about that ?) it would be very easy to parse that from the DVD2AVI project file.

[CruNcher]

@Trbarry Marc_Fd and Nic

I tested Save-Oe with Transport Stream support on a recorded PVA file and i saw only some visual errors can't make a pic even not with hypersnap i couldn't even save it to AVI No Compress its allways produceing a 0 byte file and demuxing isn't working i think because of the different File System a PVA file uses but a Picture is there
i think the errors caused by seek problems in the PVA file ? it would be nice if DVD2AVI and fillters build up on it would support demuxing and playing of PVA files people then don't need to use PVAstrumento anymore

Maybe this could be off help http://home.t-online.de/home/michael...ew-src-1.0.zip

[trbarry]

please take MPEG2Dec3 v0.93 source code and work on it. i'm not going to update the code, so YOU could continue to improve it. (like adding proper cropping).

Well, er, uhmmmmmm ...... that is kinda like feeding a stray cat. I'm afraid it might sort of make me responsible for it again and MPEG2DECx has never really been my top priority. It is much too much fun trying to talk you into doing all the work.

But I must admit you have done an admirable job of it with all these enhancements.

If it is okay with you I would like to sometime merge all the changes in your new version back into the save-oe Sourceforge project. But I guess I was waiting to see when/if you lost interest and I would not be doing anything in a timely enough fashion to help the current Avisynth 2.5.

DVD2AVI & MPEG2DEC are funny projects, often orphaned for some reason. Somebody takes them and runs with them for awhile and then for awhile they just sit. But I'm real happy with your recent changes. When I got the project from OGO the cropping was busted too, so I guess I'm used to fixing it.

@Sh0dan -

Is it easily possible somehow to pass back global vars from MPEGDEC to Avisynth like I suggested above? Is it like MPEG2Source creates a clip that could just have some more vars set by MPEG2DECx and referred to like other clips attributes?

- Tom

[trbarry]

Cruncher -

I'm afraid you are going to have to find someone who knows and uses PVA files to get support for those. Currently I'm pretty sure we look for the x'47' (IIRC) ATSC transport stream flags to identify US HDTV streams.

- Tom

[Gannjunior]

@Lighty

Pls read this thread more carefuly

I've not asked anything of strange and I've not asked nothing that has been treated many times...There's no answer about my problem in the others posts.And mpeg2dec3 0.93b isn't gone out one month ago...

However I've done the same encoding using mpeg2dec3 0.93b and I've had the same problem explained some post ago.I've also opened Vdub and the I've had the same problem even when I scroll DVD by Vdub.
So,dear Lighty,I've read CAREFULLY the thread and I've not seen any answer that could help me to solve my problem(If you have seen one,tell me ).For that reason,I've posted my question 8 messages ago!

Regards

[Wilbert]

I'm afraid you are going to have to find someone who knows and uses PVA files to get support for those. Currently I'm pretty sure we look for the x'47' (IIRC) ATSC transport stream flags to identify US HDTV streams.

Anyone knows about PVA files and is willing to help Tom?

edit: maybe BB knows enough about this stuff and is willing to help you?

[Bulletproof]

There seems to be a major problem in the post processing of MPEG2DEC3. There are tiny distorted blocks in the video on edges of things. Sometimes there are several of them, I made screenshots so you could see. I'm using an AMD Athlon CPU. The IDCT changes do not make a difference. However, on Jackei's page (Author of DVD2AVI), he has a similar type of distortion in his program when using the IEEE-1180 reference IDCT with distorted blocks, I don't know if they are related, you can see that problem here: http://arbor.ee.ntu.edu.tw/~jackei/dvd2avi/idctref/

This is with CPU=4:



This is with CPU=0 (post processing off):

[Marc FD]

well, i can only suppose things.
are you using iPP = true ??

BTW, the bug as nothing to do with what jackei's refers to.
it's really not easy to see, but i dunno why it's here.
i hope it's not my bad implementation ^__^

[Bulletproof]

Yes I was using iPP=TRUE, I have not checked yet if it happens with it off, but 99% of my material is interlaced so I always keep it on.

[Marc FD]

use separatefields, you'll see it does the job right.
as i writed in the readme, using iPP=true activates field-based PP.

i think deinterlacing will more or less remove these artifacts.

[Bulletproof]

On a somewhat related note, I just installed DivX 5.02, I had 5.01 installed for a while, and it's default post processing setting is up 1 notch. I noticed while playing a video today that it has the same exact problem with showing those blocks in frames, and this is from progressive video. After disabling post processing they dissapeared.

[Acaila]

@Marc FD:

When I use this filter (v0.94) I get the following output in debugview for every frame:
00000089 3.00058924 [1180] 1st-pass: size:106 total-kbytes:2 inter quant:2 MPEG kblocks:0 mblocks:0
00000090 3.00147482 [1180] MPEG2Dec3 log> pf = 1
00000091 3.01606831 [1180] MPEG2Dec3 log> fo = 0
00000092 3.01617335 [1180] MPEG2Dec3 log> top_field_first = 1
00000093 3.01622667 [1180] MPEG2Dec3 log> progressive_frame = 1

Now, since I get 4 extra lines for every frame it is increasing my disk usage, and in fact I believe it's actually slowing down my encodes because fps keeps dropping to zero every once in a while due to memory swapping. I've searched the readme that comes with it, but I haven't been able to find a way to disable MPEG2Dec3 from outputting these extra lines. Maybe I've overlooked something, but could you please tell me how to disable this extra info?

[iago]

@Acaila,

In DebugView, go to

Edit -> Filter/Highlight -> Exclude

and type in "mpeg2dec3". That's all!

regards,
iago

[Acaila]

Hadn't even thought of that. Thanks

[cweb]

Can you update the software you are using for your card? Updated
software should be able to save directly in MPEG-2. My hauppauge's
software does that. I never save in PVA. If I use PVA and PVAstrumento
I'd lose some bits of the video and/or audio, and that's not good.

I save in MPEG2 and then use DVD2AVI (the original or the improved
one by Tom) plus mpeg2dec3/avisynth 2.5 currently. The results are
great.

I would try updating the software (driver plus recording utility).
You can use a third party recording software such as Progdvb.

Originally posted by CruNcher
@Trbarry Marc_Fd and Nic

I tested Save-Oe with Transport Stream support on a recorded PVA file and i saw only some visual errors can't make a pic even not with hypersnap i couldn't even save it to AVI No Compress its allways produceing a 0 byte file and demuxing isn't working i think because of the different File System a PVA file uses but a Picture is there
i think the errors caused by seek problems in the PVA file ? it would be nice if DVD2AVI and fillters build up on it would support demuxing and playing of PVA files people then don't need to use PVAstrumento anymore

Maybe this could be off help http://home.t-online.de/home/michael...ew-src-1.0.zip

[CruNcher]

Can you update the software you are using for your card? Updated
software should be able to save directly in MPEG-2. My hauppauge's
software does that. I never save in PVA. If I use PVA and PVAstrumento
I'd lose some bits of the video and/or audio, and that's not good.

i use Progdvb a long time now mpeg-2 recording looks stable but there is now another problem with mpeg2dec3 Yv12, Marc has a test clip of the "repeating frame" bug and is investigating it. The problem recording directly to Mpeg-2 its more vurnearable to send errors loseing complete gops the bits loseing problem was corrected as i know in the new pvastrumento version 2.25

[cweb]

I never get errors when I record to mpeg-2. Of course, I get errors
if I try to record something while doing something computation intensive, so when recording I try not to do anything else with the PC.
As a result there aren't problems usually with the recording and you
can say I never use pvastrumento even though I did install it and I
do update it.

I did update the dvb-s drivers from the ones which were supplied, so
perhaps that helps.

Originally posted by CruNcher
i use Progdvb a long time now mpeg-2 recording looks stable but there is now another problem with mpeg2dec3 Yv12, Marc has a test clip of the "repeating frame" bug and is investigating it. The problem recording directly to Mpeg-2 its more vurnearable to send errors loseing complete gops the bits loseing problem was corrected as i know in the new pvastrumento version 2.25

[MrBunny]

Just to suppliment what Acaila was saying about mpeg2dec3 debugview output. Even if iago's method manages to disable the debugview from actually outputting the lines to the screen, mpeg2dec3 is still "sending" those lines to debugview. Although it's probably very minor, it's probably still results in a performance hit. I was wondering if it would be possible to have an option to disable that output.

Thanks