View Full Version : MPEG2Dec3 v0.9 for Avisynth 2.5
MaTTeR
5th January 2003, 23:58
Originally posted by MrBunny
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. If a performance hit exists it has to be very minor, so much so that you won't notice. Before we started filtering the performance hit was coming from DebugView gobbling up lots of RAM, if you filter you shouldn't see this anymore.
AFAIK MarcFD already said he would give the user an option to disable the output in the next version.
Evil Andy
10th January 2003, 17:23
I know something like this has come up before but I'm getting 'Unrecognised exception errors' with 0.94
All I have access to are progressive PAL sources and so far not a single one will work even for such a simple script as
LoadPlugin("C:\ANDY\GORDIA~2\mpeg2dec3.dll")
MPEG2Source("C:\andy\dvd ripping\test\series 1 - episode 2 - the new girl.d2v")
Guest
10th January 2003, 17:41
Make a very small VOB available for download that causes the problem. Use VOBSplitter if necessary. Then we can try to duplicate your issue.
Just for fun, try making your d2v and VOB files have no spaces in their names.
Evil Andy
10th January 2003, 23:39
Tried making the filenames 8.3 standard, still no joy.
Attaching a small vob.
Evil Andy
10th January 2003, 23:40
Ahem, attaching a small vob
Guest
11th January 2003, 01:01
Your VOB works just fine for me with mpeg2dec3_094, 1/10/03 Avisynth 2.5, DVD2AVI 1.76, and this script:
LoadPlugin("d:\avisynthplugins\mpeg2dec3_094.dll")
mpeg2source("ickle.d2v")
You must have a hosed-up installation or an unexpected DLL floating around that is being loaded.
cweb
11th January 2003, 09:56
Hello Neuron2,
Thanks for compiling mpeg2dec for avisynth 2.5. I did find another case which gives the looping problem with Marc's mpeg2dec3 (see the other thread in this forum). So I think the problem is not yet solved.
If you want, I can give you the clip in question.
Guest
11th January 2003, 12:00
The fact that a VOB fails for you and not for the rest of us suggests that there is a problem with your system. I'll try your new VOB if you like, but you oughtn't ignore this finding.
cweb
11th January 2003, 12:24
Hmm.. actually I don't use VOBs :) - I presume you are replying to Andy,
not me. My clip is a satellite dvb-s MPEG2 recording.
Originally posted by neuron2
The fact that a VOB fails for you and not for the rest of us suggests that there is a problem with your system. I'll try your new VOB if you like, but you oughtn't ignore this finding.
Guest
11th January 2003, 12:37
You're right. Sorry.
Evil Andy
11th January 2003, 19:14
This is most frustrating. Here's what I've done so far.
1.) Clean install of Win98
2.) Install both Gordian Knot 27 packs, rip and system.
3.) Unzip the latest avisynth 2.5 dll and place it in windows/system, overwriting the original dll placed there by Gordian Knot.
4.) Install the latest release of VirtualDubMod.
5.) Unzip the latest release of mpeg2dec3 (0.94) and put the 3 files in my Gordian Knot directory.
6.) Rip DVD using DVDDecrypter and get a project file with DVD2AVI 1.76 (doing no editing in DVD2AVI).
7.) Write out the above script exactly (well, apart from the filenames and paths).
8.) Attempt to load my avs in VDMod.
9.) Swear loudly as I get unrecognised exceptions.
What am I doing wrong? It must be something embarrassingly simple as no one else is having these problems.
Guest
11th January 2003, 20:13
What happens with the Avisynth 2.5 port of dividee's mpeg2dec that I posted on another thread?
scmccarthy
11th January 2003, 22:20
@ evilandy
neuron2
an unexpected DLL floating around
Don't forget to search your entire drive for avisynth.dll and compare the results with your paths and the versions of the dll to make sure there is no conflict.
Stephen
MaTTeR
11th January 2003, 23:09
It's just a thought but you might also put the avisynth.dll inside of the Vdub folder.
Evil Andy
11th January 2003, 23:14
Your avisynth 2.5 port of mpeg2dec works fine and I know avisynth 2.5 is installed correctly because a simple version script works fine.
This script works
LoadPlugin("C:\test\MPEG2DEC_avisynth25.dll")
#LoadPlugin("C:\test\MPEG2Dec3.dll")
mpeg2source("C:\test\test.d2v")
crop(10,9,701,557)
BicubicResize(544,304,0,0.5)
This script doesn't
#LoadPlugin("C:\test\MPEG2DEC_avisynth25.dll")
LoadPlugin("C:\test\MPEG2Dec3.dll")
mpeg2source("C:\test\test.d2v")
crop(10,9,701,557)
BicubicResize(544,304,0,0.5)
Evil Andy
11th January 2003, 23:17
And no joy putting avisynth.dll in my vdub folder either.
I'm stumped :confused:
MaTTeR
11th January 2003, 23:37
One last thing, make sure your always cropping and resizing using even numbers.
Evil Andy
12th January 2003, 00:13
Whoops, that was sloppy of me, but that's not the problem either as
LoadPlugin("C:\test\MPEG2Dec3.dll")
mpeg2source("C:\test\test.d2v")
Still throws up an exception.
That last script, however, does load up in vdubmod. The exception comes when i try any of the seek or preview buttons. A check under file info shows it is recognising the source as YV12 and is using DivX 5.02 as the decoder.
trbarry
12th January 2003, 01:07
Some versions of DVD2AVI get bundled with a DVD2AVI.ini file from a machine of different processor type. For instance you don't want to have one saying IDCT=4 if you aren't running on a P4. (use 2 for mmx)
You might just try deleting your DVD2AVI.ini file and remaking the .d2v with the defaults, using DVD2AVI 1.76.
- Tom
Evil Andy
12th January 2003, 01:21
still a no go.
Guest
12th January 2003, 04:44
Redownload the mpeg2dec3. Maybe it got corrupted.
Evil Andy
13th January 2003, 16:55
Sigh, still a no go. Perhaps I'll try compiling the source for myself and see how that works out.
blue`ostyler
15th January 2003, 06:18
Evil Andy
I had exactly the same problem.
"Unrecognized Exception!"
I tryed almost everything:
- Recompiling MPEG2dec3
- Changing the IDCT under DVD2Avi
- Changing from Avisynth 2.5 with MPEG2dec3 0.94 to Avisynth 2.07 with MPEG2dec3 Beta6
- Installing AVS with VdubMod and xvid codec on another PC which didn't have anything before
- other things i don't remember
BUT, i tryed too to simply go back from DVD2AVI 1.77.3 to 1.76
and it works.
In fact, i don't have to use DVD2AVI 1.76 to make the thing work perfectly. I just open the D2V file and delete the bracket, then change Luminance_Filter=0,0 to Luminance=0,0 and all is ok :)
But if you use DVD2AVI 1.76 to create the d2v, then your problem still remains weird...
scmccarthy
15th January 2003, 16:54
@blue
If Andy is smart enough to use Gordian Knot, then he is using DVD2AVI 1.76. Gordian Knot only uses well tested, compatible versions of the software.
Stephen
Evil Andy
16th January 2003, 16:18
I'm using the DVD2AVI that came bundled with Gordian Knot ie 1.76
Latest thinking is that it's maybe a problem with Avisynth 2.5 after all as I've found that Convolution3d produces the same error.
I'll go through a plug in spree to find what others give me the same error.
sh0dan
16th January 2003, 16:27
@EA: Have you tried searching through you entire HD for avisynth.dll to be sure that there isn't another version lying around somewhere?
Evil Andy
16th January 2003, 16:36
Yep, just the one copy in Windows/System
A quick 'Version' script confirms it as 2.5
Some 2.5 plugins are working for me (e.g. the recompiled mpeg2dec) and some aren't (e.g. mpeg2dec3 & convolution3d)
kilg0r3
16th January 2003, 19:12
@evilandy
sorry if this sounds stupid, but, have updated your system with recent drivers (for chipset etc.), directx version and all the nice things you can get from windowsupdate.microsoft.com?
is avisynth 2.0x working for you?
how about uninstalling divx and using xvid for yv12 decoding?
that's all i can think of atm
scmccarthy
16th January 2003, 19:30
Some 2.5 plugins are working for me (e.g. the recompiled mpeg2dec) Ah Ha! mpeg2dec.dll was recompiled for AviSynth 2.5 without added YV12 capability. If I am right, mpeg2dec3 would work it you converted to YUY2 in your script.
Stephen
Evil Andy
30th January 2003, 11:14
Well I don't know what changes were made to avisynth or mpeg2dec3 for the beta release but everything's working fine now. Thanks to all developers and people who tried to help me with my problems.
snooty
24th February 2003, 03:04
Hi - Can someone please tell me where to download the latest version? Mr. Marc FD has changed his sig so I don't know where to get it.
Thanks,
Paul
Guest
24th February 2003, 05:22
Originally posted by snooty
Hi - Can someone please tell me where to download the latest version? Mr. Marc FD has changed his sig so I don't know where to get it.
http://ziquash.chez.tiscali.fr/
Monamona
9th March 2003, 03:46
I got broken image (like stripe) with the following AVS file.
---
LoadPlugin("mpeg2dec3.dll")
Mpeg2Source("dvd.d2v")
crop(8,0,704,480)
YV12toYUY2(interlaced=true) or YV12toYUY2()
---
The source is interlaced anime(NTSC 30fps).
When I delete crop(), everything seems to be perfect.
---
[Encoding Environment]
Mpeg2Dec3 1.00
Avisuynth 2.5 (latest beta)
VirtualDubMOD 1.4.13.1
(Pentium 3)
---
ryangs
15th March 2003, 03:41
I can't open my MPEG2 file at all--it tells me that it "couldn't open file." It's odd, because Nic's mpegdecoder has no trouble dealing with it. I'd just use that but I'd like to try MPEG2Dec3's postprocessing. It's a 480x480 MPEG2 SVCD source... any ideas?
Marc FD
16th March 2003, 20:17
"couldn't open file" mean that the input path is wrong
ryangs
16th March 2003, 21:11
Originally posted by Marc FD
"couldn't open file" mean that the input path is wrong
I've double and triple-checked the path--I know it's correct. If I hadn't typed the path right, Nic's wouldn't open it, either.
Marc FD
16th March 2003, 21:31
"couldn't open file" ?
okay it wasn't env->ThrowError("MPEG2Source : unable to load file \"%s\" ",path);
so it's an internal error.
it should NEVER appear !!
try to make a small cut of you mpeg2 (about 5 mo) and upload where i can leech it, i'll take a look in my freetime (nothing granted)
i think it's due to the unhabitual format. (remeber dev are often the ones who use the less their own tools ^^)
Prettz
4th April 2003, 21:25
I'm not sure if this question can really be answered, but about how much difference in quality should you expect using idct=5 (32bit SSE2) with MPEG2Dec3 versus, say, using the 64bit FPU mode (or the 64bit IEEE reference mode)? Would any differences be dependent on the source?
Also, wouldn't there be a way to do the algorithm with 64bit SSE2? I can understand if it's just that nobody wants to code that right now, but I'm just curious since I thought I remembered there being both 32bit and 64bit versions of all of the SSE2 instructions.
ryangs
5th April 2003, 18:19
Marc FD:
I tried two other MPEG2 files, and neither worked. One is another SVCD encoded file, the other is DVD encoded. The problem must be with my system somehow. Could the MPEG2 filters from some programs I installed (like WinDVD or PowerDVD) be interfering with MPEG2Dec3? I'm running WinXP Pro SP1 with Avisynth 2.5.1 beta and VirtualDub 1.5.1.
Marc FD
16th April 2003, 19:53
>Could the MPEG2 filters from some programs I installed (like WinDVD
>or PowerDVD) be interfering with MPEG2Dec3
no
litz
19th April 2003, 05:54
Using mpeg2dec3.dll to read HDTV transport streams, I'm running into TERRIBLE problems with bitstream errors.
These are short little subframe to 1 frame glitches in the transmission.
There is no way to avoid these - they simply happen.
But mpeg2dec3.dll totally explodes any time it runs across one, causing an access violation error in avisynth - crashing avisynth and causing any and all subsequent frame requests to fail.
At that point, the only solution is to shut all the software down, restart, and try again, avoiding the frame in question.
is there ANY way around this? This problem effectively makes the dvd2avi/mpeg2dec3 solution to HDTV recompression impossible.
A sample of a .ts file that causes the error is available upon request.
thanks
- litz
bartnl
5th May 2003, 18:03
I'm having the same trouble with digital TV recordings from satellite. On some recordings avisynth will crash when there is a single bad frame. Bad thing is that these bad frames do not get recognized by the 'scan video stream for errors' option of VirtualDubMod.
As a workaround I use the YV12 decoder from http://nic.dnsalias.com/MPEGDecoder.html that doesn't read the start- and endpoint in d2v files very well. I.e. it reads the whole source. This can be corrected by making proper selection in VirtualDubMod.
Therefore I will always first start with mpeg2dec3.dll and if that fails I use the other. It seems however that more and more recording fail with mpeg2dec3.dll . I hope this is just because I actually have more recording errors :confused:
trbarry
5th May 2003, 22:04
is there ANY way around this? This problem effectively makes the dvd2avi/mpeg2dec3 solution to HDTV recompression impossible.
A few months ago I implemented a couple HDTV solutions out of desperation on MPEG2DEC2, for Avsynth 2 and below (YUY2 only).
See www.trbarry.com/MPEG2DEC2.zip .
In that one I made all the buffers a lot bigger. This wastes memory but lowers the chance of falling off the end of the buffer during motion estimation when trying to process garbage. That alone saves a lot of clips, since that is where it would usually crash.
And for really desparate measures that zip also contains a copy of MPEG2DEC_ER.dll (Error Recovery). If you do a Loadplugin for that instead of the regular MPEG2DEC2.dll then it will have an error trap that properly returns garbage frames out for garbage in.
However it is slower and seems to also sometimes crash Vdub when you finally exit. On the good side your encoding will be finished by then. ;)
- Tom
great news for all mpeg2dec3 fans! for all of you who dont know it by now: there is a new version of mpeg2dec3 out! more infos here (http://forum.doom9.org/showthread.php?s=&threadid=53164)
Is it already recommended to use Nics new version or is it still only for testing? The one included in Gknot is the original 1.0, isn't it?
it's ok to use nic's new build! the one in gknot is still 1.0 but lenox is thinking about replacing it with the new one
dapipa
10th February 2004, 10:48
Originally posted by Prettz
I'm not sure if this question can really be answered, but about how much difference in quality should you expect using idct=5 (32bit SSE2) with MPEG2Dec3 versus, say, using the 64bit FPU mode (or the 64bit IEEE reference mode)? Would any differences be dependent on the source?
havin'rule 1 on my mind,i searched first for an answer,but found only this question - precisely what i wanted to ask - but it's almost a year old and there's no response:(could anyone answer it for me?
Nic
10th February 2004, 11:11
The difference in visual quality would be minuscule. Your best bet, if you really want to know. Is to try two small clips with both ssemmx2 and reference dct and see if you can tell any difference. I doubt you will be able to. (Doom9 once did a test himself and was unable to determine a difference)
However, it was once thought that trbarry's simple idct produced smaller files when used to compress and was better quality than ssemmx idct. But, it wasn't tested much and the difference would only be very small. I recommned using the fastest idct for your computer.
There, hopefully that finally answers that question,
Cheers,
-Nic
Cyberia
11th February 2004, 23:58
Nic, does the 64bit FPU mode use Miha's code? I'm pretty sure DVD2AVI does use miha's code for 64bit idct.
If that's the code you are using, Miha produced a page demonstrating how his(her?) code was superior. Basically, the 64bit code produced fewer color errors in individual pixels than ANY 32bit implementation, and the errors that did occur were much smaller in scope.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.