Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion.

Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules.

 

Go Back   Doom9's Forum > Capturing and Editing Video > Avisynth Development

Reply
 
Thread Tools Search this Thread Display Modes
Old 12th June 2003, 14:48   #201  |  Link
trbarry
Registered User
 
trbarry's Avatar
 
Join Date: Oct 2001
Location: Gainesville FL USA
Posts: 2,092
Quote:
@cuisinart: Thats because im going straight from yv12 to RGB. I could make it so you can set it either to do interlaced chroma upsampling or not. Or go from yv12 to YUY2 (or 4:4:4) and then goto RGB. Ill look into that for you.
As mentioned, the code upsampling in MPEG2DEC2 seems already to be correct. It's not really a user option but determined by the flags, prog frames, etc.

- Tom
trbarry is offline   Reply With Quote
Old 12th June 2003, 21:44   #202  |  Link
WarpEnterprises
C64
 
WarpEnterprises's Avatar
 
Join Date: Apr 2002
Location: Austria
Posts: 830
I'm too strongly voting for integrated D2V creation:
- There are MANY "bug-reports" coming from version incompatibilities only.
- I can't understand how you can use an inaccurate framecount input
- even without the other goodies (CSS, audio,...) we would have an up-to-date reference mpeg2 decoder.
- maybe you can summarize in the docu the pros and cons of the many many iDCTs

Thanks for your work!


[EDIT]: "Bug Reports" like "it's not working, why? What version of DVD2AVI? Took the wrong one...

framecount: how can you use a source in avisynth if the framecount is not reliable (esp. if the actual count is less than predicted)? Are black frames outputted?

Last edited by WarpEnterprises; 12th June 2003 at 22:23.
WarpEnterprises is offline   Reply With Quote
Old 12th June 2003, 21:59   #203  |  Link
Nic
Moderator
 
Join Date: Oct 2001
Location: England
Posts: 3,285
"MANY "bug-reports" coming from version incompatibilities only" What bug reports are you referring to?
" can't understand how you can use an inaccurate framecount input" ? What does that one mean too ?

I do need to rewrite the docs, or at least part of them. I explain the pros and cons of the iDCT's. But its reasonably simple. Use 2 if your non-p4 and 5 if you have a p4. Unless you want the slightly (& it is only slight "not magnitudes" as Isibaar puts it ) more accurate idct i.e. SimpleIDCT, which is 7. All others should probably be ignored.

-Nic
Nic is offline   Reply With Quote
Old 12th June 2003, 22:06   #204  |  Link
bond
Registered User
 
Join Date: Nov 2001
Posts: 9,770
Quote:
Originally posted by Nic
Use 2 if your non-p4 and 5 if you have a p4.
what will be used if i dont define any idct?
__________________
Between the weak and the strong one it is the freedom which oppresses and the law that liberates (Jean Jacques Rousseau)
I know, that I know nothing (Socrates)

MPEG-4 ASP FAQ | AVC/H.264 FAQ | AAC FAQ | MP4 FAQ | MP4Menu stores DVD Menus in MP4 (guide)
Ogg Theora | Ogg Vorbis
use WM9 today and get Micro$oft controlling the A/V market tomorrow for free
bond is offline   Reply With Quote
Old 12th June 2003, 22:12   #205  |  Link
Nic
Moderator
 
Join Date: Oct 2001
Location: England
Posts: 3,285
It does it automatically. 2 if your non-p4 and 5 if you are using a p4.

-Nic
Nic is offline   Reply With Quote
Old 12th June 2003, 22:14   #206  |  Link
symonjfox
IUUULEEEENZ
 
symonjfox's Avatar
 
Join Date: Mar 2002
Location: Italy
Posts: 452
The DEFAULT ... =2
Else you can edit your defaults so you won't need any more to write the entire string.
__________________
PC1:AMD Athlon II x4, 4GB DDR2, Ati Radeon 4830, 4 hard disks
symonjfox is offline   Reply With Quote
Old 13th June 2003, 00:01   #207  |  Link
V-tec
Registered User
 
Join Date: Feb 2003
Location: Italia
Posts: 31
I have made a comparison between different version of Mpeg2dec3 from 1.00 to 1.08 and Mpegdecoder-YV12

My config is:

Athlon Xp 1800+, 512Mb DDR 2100 cas 2b MB Asus A7V266-E etc...
Vdubmod 1.5.1a + debug view, Xvid Koepi 14.05.03 quant 2
Mpeg2dec3 1.0x

The Avisynt scripts,

for mpeg2dec 1.0x:

Code:
#  SOURCE 
mpeg2source("C:\driven\driven.d2v", idct=X) 
#  CROPPING 
crop(14,74,690,424) 
#  SELEZIONE 
trim(5000,7999) 
#  RESIZING 
BicubicResize(608,256,0,0.5)
for MpegDecoder-YV12

Code:
#  SOURCE 
mpegsource("C:\driven\driven.d2v") 
#  CROPPING 
crop(14,74,690,424) 
#  SELEZIONE 
trim(5345,8344) 
#  RESIZING 
BicubicResize(608,256,0,0.5)

and the results:

Code:
mpeg2dec3 1.00

idct1=_________34.21fps_______87.68s_____30.217Ko
idct2=_________34.54fps_______86.86s_____30.217Ko
idct3=_________29.68fps_______101.06s____30.269ko
idct4=_________28.53fps_______105.09s____30.353ko
idct5=_________28.67fps_______104.63s____236.900Ko


mpeg2dec3 1.01

idct1=_________34.25fps_______87.59s_____30.217Ko
idct2=_________34.46fps_______87.03s_____30.217Ko
idct3=_________29.56fps_______101.46s____30.267ko
idct4=_________28.53fps_______105.15s____30.241ko
idct5=_________28.61fps_______104.93s____236.900Ko


mpeg2dec3 1.02

idct1=_________34.25fps_______87.59s_____30.217Ko
idct2=_________34.20fps_______87.70s_____30.217Ko
idct3=_________29.67fps_______101.11s____30.267ko
idct4=_________28.45fps_______105.46s____30.241ko
idct5=_________28.70fps_______104.54s____236.900Ko


mpeg2dec3 1.03

idct1=_________34.37fps_______87.28______30.217Ko
idct2=_________34.53fps_______86.88s_____30.217Ko
idct3=_________29.71fps_______100.97s____30.267ko
idct4=_________28.64fps_______104.73s____30.241ko
idct5=_________28.75fps_______104.34s____236.900Ko


mpeg2dec3 1.04

idct1=_________33.72fps_______88.97s_____30.217Ko
idct2=_________33.77fps_______88.84s_____30.217Ko
idct3=_________29.39fps_______102.08s____30.240ko
idct4=_________27.15fps_______110.49s____30.241ko
idct5=_________28.49fps_______105.29s____236.900Ko


mpeg2dec3 1.06

idct1=_________34.98fps_______85.77s_____30.217Ko
idct2=_________35.34fps_______84.90s_____30.217Ko
idct3=_________30.28fps_______99.07s_____30.269ko
idct4=_________29.14fps_______102.94s____30.353ko
idct5=_________35.28fps_______85.02s_____30.217ko
idct6=_________35.46fps_______84.60s_____30.330Ko
idct7=_________32.96fps_______91.30s_____30.245ko


mpeg2dec3 1.07

idct1=_________35.07fps_______85.52s_____30.217Ko
idct2=_________35.29fps_______84.98s_____30.217Ko
idct3=_________30.24fps_______99.20s_____30.269ko
idct4=_________29.14fps_______102.93s____30.353ko
idct5=_________35.28fps_______85.04s_____30.217ko
idct6=_________35.33fps_______84.89s_____30.330Ko
idct7=_________32.84fps_______91.34s_____30.245ko


mpeg2dec3 1.08

idct1=_________35.08fps_______85.51s_____30.217Ko
idct2=_________35.33fps_______84.91s_____30.217Ko
idct3=_________30.23fps_______99.22s_____30.269ko
idct4=_________29.13fps_______102.99s____30.353ko
idct5=_________35.32fps_______84.91s_____30.217ko
idct6=_________35.40fps_______84.74s_____30.330Ko
idct7=_________35.61fps_______84.23s_____30.245ko


mpegdecoder YV12

idct2(?)=______37.87fps_______79.21s_____30.216ko
V-tec is offline   Reply With Quote
Old 13th June 2003, 01:48   #208  |  Link
trbarry
Registered User
 
trbarry's Avatar
 
Join Date: Oct 2001
Location: Gainesville FL USA
Posts: 2,092
Very interesting results above. It looks like:

1) Prior to release 1.06 idct=5 was busted on Athlons. It should have defaulted to 2.

2) It also looks like Athlon speed for idct=7 is now (v1.08) actually faster than idct=2 or the others. Nifty.

- Tom
trbarry is offline   Reply With Quote
Old 13th June 2003, 01:53   #209  |  Link
JohnMK
Registered User
 
Join Date: Sep 2002
Location: Seattle
Posts: 551
Tom I'd love to see if idct=5 is actually faster on P4's. I'd run a benchmark if I knew how to isolate it down to two decimal places like he does.
JohnMK is offline   Reply With Quote
Old 13th June 2003, 08:53   #210  |  Link
Nic
Moderator
 
Join Date: Oct 2001
Location: England
Posts: 3,285
@Tom:
"It also looks like Athlon speed for idct=7 is now (v1.08) actually faster than idct=2 or the others. Nifty"
It looked that way in my tests too, but I didn't want to say anything until I was sure (because I said the skal iDCT was the fastest...which obviously isn't correct )
(Very nice work , Oh and I looked into that MPEG2Dec3 parity thing, and couldnt find the problem. Let me know if you can look into it for me (& I hope you enjoyed the film))

@V-tec: Thanks for all those results That must have taken some work and time, so thanks a lot. And it shows that we have made it faster, even if its only fractional. (You were correct in saying MPEGDecoder does use almost exactly the same as iDCT=2)

@John: Im pretty definite that idct=5 is faster on P4s. But anyone that knows different please let me know.

-Nic
Nic is offline   Reply With Quote
Old 13th June 2003, 16:26   #211  |  Link
trbarry
Registered User
 
trbarry's Avatar
 
Join Date: Oct 2001
Location: Gainesville FL USA
Posts: 2,092
Quote:
Im pretty definite that idct=5 is faster on P4s. But anyone that knows different please let me know.
Cruncher posted some results back on page 3 that suggest 5 would still be faster on P4's.

- Tom
trbarry is offline   Reply With Quote
Old 14th June 2003, 18:24   #212  |  Link
Th3-S4int
Registered User
 
Join Date: Mar 2003
Location: Germany
Posts: 18
Hi Iam new here and come from Germany, but i hope you will understand what i mean:
1. Which idct is the best for a Athlon Thunderbird (1.2GHZ)? Until now i used standard, but i hope there are some faster! And what is the different form standard (0) to the optimal setting (exp. 7) (i mean is it faster or something else?)
2.For what is Post Processing? does it help to have better compressiblity? Increase it the Picture quality?
I hope someone helps me, Thx!
Th3-S4int is offline   Reply With Quote
Old 14th June 2003, 19:40   #213  |  Link
JohnMK
Registered User
 
Join Date: Sep 2002
Location: Seattle
Posts: 551
1: idct=7 on your particular CPU.
JohnMK is offline   Reply With Quote
Old 15th June 2003, 00:41   #214  |  Link
sapient
Unbeliever
 
Join Date: Sep 2002
Location: Greece
Posts: 111
I am a recent convert to the intel CPU's. My limited experience so far with a celeron @ 1.7 and a p4 @ 2.8 w/ HT has shown me that the speed difference between iDCT 2 and 5 is inconcequential. I can't think of a way to test them in an accurate way though. I just try to look at virtualdub's fps count @ a specific time. Obviously this "method" isn't exactly dependable. Does anyone have a simple and accurate method to standardise such a mesurement?

sapient
sapient is offline   Reply With Quote
Old 15th June 2003, 00:47   #215  |  Link
Nic
Moderator
 
Join Date: Oct 2001
Location: England
Posts: 3,285
Well idct=2 & idct=5 produces exactly the same output, so if you've got a p4 id still say use idct=5 over 2. Just because he can't do any harm and won't be slower.

-Nic
Nic is offline   Reply With Quote
Old 15th June 2003, 11:01   #216  |  Link
Blight
Software Developer
 
Blight's Avatar
 
Join Date: Oct 2001
Location: Israel
Posts: 1,005
Nic:
As someone who wrote a directshow source filter, is there any chance you'd port this effort into a directshow MPEG2 decoder filter, making it the first (and I believe only) freely available such filter?

Not to mention it could be a boon for HDTV decoding as transport support is really bad under directshow at the moment.
__________________
Yaron Gur
Zoom Player . Lead Developer
Blight is offline   Reply With Quote
Old 15th June 2003, 11:29   #217  |  Link
Nic
Moderator
 
Join Date: Oct 2001
Location: England
Posts: 3,285
I tried it once with libmpeg2. It worked...almost (not quite Cant remember why not though). Yes I'd forgotten about that. Ill look into that again soon

-Nic
Nic is offline   Reply With Quote
Old 16th June 2003, 12:44   #218  |  Link
colin.findlay
Registered User
 
Join Date: Mar 2003
Posts: 4
Excuse me if this has already been asked a million times before (Although I couldn't find it on a search). The old v1 of MpegDecoder used to support decryping VOB's on the fly. As far as I can tell, the new version & MPEG2Dec3 don't support this. (Probably because it's based on DVD2Avi now?)
Are there any plans on putting it back in? It really was the core reason I used to use MPEGDecoder/AviSynth, and I loved it, although the speed increase is nice :-)

Regards
C

PS: Yes I know working from the DVD is slower and would probably negate months of processor optimiations - but I like the disk space it saves :-)
colin.findlay is offline   Reply With Quote
Old 16th June 2003, 12:46   #219  |  Link
Wilbert
Moderator
 
Join Date: Nov 2001
Location: Netherlands
Posts: 6,364
MpegDecoder <> Mpeg2dec3

mpeg2dec/mpeg2dec3 was never able to import vob files. Why don't you continue with using mpegdecoder?
Wilbert is offline   Reply With Quote
Old 16th June 2003, 13:10   #220  |  Link
Nic
Moderator
 
Join Date: Oct 2001
Location: England
Posts: 3,285
Hmmmm, ill add D2VCreation support into MPEG2Dec3 into the next release, and reactivate OpenDVD.DLL support (and release my version of OpenDVD.DLL, the original is based on VobDec which I never liked)

So my planned changes for 1.09 are:
  • Compile with MSVC .net 2K3 (I tested it over the weekend and it improved the speed)
  • Add D2V Creation and release a new OpenDVD.DLL, this will keep MPEG2Dec3 still legal as all the DeCSS stuff will be in OpenDVD.
  • Try and make it so that using mpeg2dec3's internal colorspace functions (YV12toYUY2, etc) it will hopefully be able to call avisynth's colorspace routines instead and detect if its interlaced or not without the user having to specify.
  • Make it so that GetParity works ok, trbarry reports that it might not (in the TomsMoComp readme.txt). If anyone can test to see if its working or not that would be a great help

Sound ok? (This might take a while, due to me being busy and not being around next week)

-Nic
Nic is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 04:23.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.