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. |
2nd June 2010, 18:27 | #1521 | Link |
Registered User
Join Date: Apr 2002
Location: Germany
Posts: 4,926
|
@Neuron2
Does nvcuvid.dll (VP2) support Mpeg-2 4:2:2 Studio Broadcast streams ?
__________________
all my compares are riddles so please try to decipher them yourselves :) It is about Time Join the Revolution NOW before it is to Late ! http://forum.doom9.org/showthread.php?t=168004 |
4th June 2010, 08:57 | #1523 | Link |
Registered User
Join Date: Apr 2009
Posts: 478
|
neuron2, I'm thinking of donating for your DG NV Tools and I have some questions I hope you can help me with.
The Purevideo deinterlacing function looks great, and that's what I guess I will be using most. The thing is my work computer is also my gaming computer. I'm currently using a Radeon 4870 and need an nVidia card. I have come up with 2 choices 1) Get a Fermi (GTX 470 is my first choice) 2) Continue using my Radeon 4870 and get a cheap GT210/GT220 and use it alongside with the 4870 purely for Purevideo. My question is, is the purevideo deinterlacing quality dependent on the card or are there differences? Also, do you know if your software will work in scenario 2? I'm aware that only Windows 7 supports heterogeneous video card support. I'm currently on vista and will have to upgrade to 7 for that, but I hope to find out whether it will work first. Thanks! |
4th June 2010, 13:29 | #1526 | Link | ||
Guest
Join Date: Jan 2002
Posts: 21,901
|
Quote:
Quote:
|
||
4th June 2010, 14:48 | #1528 | Link |
Guest
Join Date: Jan 2002
Posts: 21,901
|
DGDecNV 2010
* The previously hidden transport stream trim functionality is now exposed in
the GUI. A progress dialog for the trim operation has been added. Performance of the file write operation has been improved. The functionality is now more robust for writing proper packet boundaries. 192 byte transport packet streams are now properly supported. Refer to the users manual for important usage notes and caveats. * Added a CLI avs template command: -at file. * Fixed the Disable Display function for double rate deinterlacing. The operation of this function has been made more robust. * Fixed a problem causing some AAC streams to not be detected. * Fixed a problem causing some teletext streams to be detected as audio. * Added an error popup for non-4:2:0 streams (until supported by Nvidia). * Fixed a problem in indexing of MPEG2 streams that caused some unusual but legal GOPs to be considered malformed and cause an abort of the indexing. http://neuron2.net/dgdecnv/dgdecnv.html |
4th June 2010, 18:11 | #1531 | Link | |
Registered User
Join Date: Apr 2009
Posts: 478
|
Quote:
Thanks. I'm aware that heterogeneous is supported on XP as well, but I greatly prefer 7 to XP. Last edited by aegisofrime; 4th June 2010 at 18:35. |
|
6th June 2010, 02:15 | #1534 | Link |
Registered User
Join Date: Aug 2007
Posts: 112
|
I've got a video that isn't behaving optimally. It's an extra from a blu-ray disc, encoded at 720x480 (and it should be 4:3 but it's apparently not flagged as such, it appears to even display on a television in a slightly stretched AR). eac3to detected it as "480p24/1.001 (3:2) with pulldown flags". When it's indexed using DGindexNV 2010 it reports "Frame Rate: 23.976024 fps" but it seems to be counting 30fps worth of frames. As a result, when I encode the video I end up with ~22mins of audio and ~28mins of video (30fps played back at 24fps). Small sample here:
http://www.megaupload.com/?d=PW53CQ2O Any help would be appreciated. |
6th June 2010, 05:06 | #1536 | Link | ||
Guest
Join Date: Jan 2002
Posts: 21,901
|
Quote:
Quote:
Please post a link to a larger M2TS source sample direct from the bluray that I can use to duplicate the problem. |
||
6th June 2010, 14:52 | #1538 | Link | |
Registered User
Join Date: Aug 2007
Posts: 112
|
Quote:
http://www.megaupload.com/?d=MKOFDA0W Here's the full m2ts file, in case it helps (763mb): [link removed] This particular episode (there are 4) is 20:17, but the video ends up being 25:21. And here's something interesting. Last night I was using CUVIDserver 2006 and DGindexNV 2010 (accidentally, due to MeGUI not using the newest version) and it said 23.976. This morning I used 2010 and 2010, and it said 29.970. So I've spent 15 minutes switching between various combinations (and switching between input files: the 100mb sample, the full m2ts, and the demuxed vc1) and in fact I'm not seeing a pattern at all - sometimes I get 23.976, sometimes 29.970. I've managed to get a DGI file of each, and the one created at 29.970 plays back at the correct length in an AVS file. So, besides the obvious "what's going on here?", there's the interesting point that in either case, it counts the same number of coded frames and playback frames. Is this correct? Is eac3to wrong about it having soft pulldown? Edit: Alright, I've found the pattern (and btw I'm only using 2010 now, so I don't know how this applies to 2006). If I open one of the m2ts files first, it shows 29.970 and any of the test files I subsequently open (inclding the demuxed vc1 stream) show as 29.970. If I then close and re-open DGindexNV, and open a vc1 first, it detects as 23.976 and opening the m2ts afterwards will make it show as 23.976. Last edited by Guest; 6th June 2010 at 16:05. |
|
6th June 2010, 15:32 | #1539 | Link | |
Guest
Join Date: Jan 2002
Posts: 21,901
|
Quote:
I've duplicated this with your samples. Investigating... |
|
6th June 2010, 16:05 | #1540 | Link |
Guest
Join Date: Jan 2002
Posts: 21,901
|
The stream is 29.97 fps without pulldown.
Regarding the initial sample.vc1 you linked: I don't know what you demuxed that with but it really is 23.976. Let's forget that because I don't know how you made it. If EAC3TO did that you should report it. If you demux with DGIndexNV 2010 from your sample.m2ts, the resulting sample.demuxed.vc1 opens as 29.97, as it should. I've located the bug that you exposed. When you open a new file from within DGIndexNV (without closing and reopening DGIndexNV), there are cases where the new sequence headers are not processed. One case is if the only change is the frame rate, which applies in your scenario because you open sample.vc1 first and then open sample.m2ts. The fix will be in the next release. Your workaround is to close DGIndexNV before opening new files. (BTW, I have deleted your full sample link for copyright reasons.) Last edited by Guest; 6th June 2010 at 16:14. |
Thread Tools | Search this Thread |
Display Modes | |
|
|