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. |
12th November 2009, 15:29 | #541 | Link |
Guest
Join Date: Jan 2002
Posts: 21,901
|
The audio is marked in the PMT as scrambled, but obviously it isn't. This puts me in a bind because I added the check to prevent crashing when trying to process a scrambled stream. Tell me about where the TS came from.
Looking at the upscaling issue... EDIT: OK, I have the upscaling fixed. I'll try to put out a new version tonight with fixes for both issues. Last edited by Guest; 12th November 2009 at 15:50. |
12th November 2009, 20:05 | #542 | Link |
Registered User
Join Date: May 2004
Posts: 27
|
The TS is an extract from a satellite mux in which scrambling was temporarily disabled. You could still check for scrambling via the bits in "transport_scrambling_control" since they're generally going to be more reliable. The info in the PMT only indicates that packets with particular PIDs may be scrambled, not that they necessarily are all of the time.
|
12th November 2009, 20:10 | #543 | Link |
Registered User
Join Date: Oct 2008
Posts: 17
|
I hit a little issue with DG NV tools 2.0.0 beta 2 on this capture sample converting from 1080i MPEG-2 TS to 720p x264. The source is a capture from a Motorola PVR copied to PC with CapDVHS and strangely I didn't have issues with a couple of earlier captures (though those were from a different channel).
When I don't use DG NV tools and deinterlace with tdeint the output is correct. Script: MPEG2Source("SpeedNov03b_edit.d2v") tdeint() spline36resize(1280,720) colormatrix() When I use NV Tools the whole ~45 minute capture comes out 30 seconds slow and then (of course) out of sync with the audio when I mux it back in. Script: LoadPlugin("C:\utilities\video\NVBeta11\DGDecodeNV.dll") DGSource("SpeedNov03b_de.dgm",deinterlace=1) spline36resize(1280,720) colormatrix() I've got Nvidia drivers version 191.07, EVGA GTX275 card, x264 r1222M, Windows 7 RC 32-bit x264 commands used in MeGUI: program --profile high --pass 2 --bitrate 3800 --stats ".stats" --level 4.1 --ref 2 --direct auto --subme 5 --trellis 0 --partitions p8x8,b8x8,i4x4,i8x8 --vbv-bufsize 50000 --vbv-maxrate 50000 --thread-input --cqmfile "C:\utilities\video\Matrices\eqm_avc_hr.cfg" --output "output" "input" Last edited by adiabatic; 12th November 2009 at 20:36. |
12th November 2009, 21:11 | #544 | Link |
Guest
Join Date: Jan 2002
Posts: 21,901
|
As stated in the DGDecodeNV user manual:
"Also note that setting deinterlace to 1 or 2 forces the field operation to be "Ignore Pulldown", regardless of the project setting." Your stream has irregular pulldown so treating it with ignore pulldown will kill AV sync. The correct way would be to use Force Film mode but that is not yet implemented (I'm working on it now). Until then you can: 1. Use Honor Pulldown and then deinterlace with another filter. It's not ideal because most of the stream is progressive. 2. Use Force Film mode in DGIndex. |
12th November 2009, 23:18 | #545 | Link | |
Registered User
Join Date: Oct 2008
Posts: 17
|
Quote:
It's a really weird source even when watching on the cable box... it seems to be pieced together from SD and HD cameras with segments where the video just looks odd. The "irregular pulldown", I guess. How would I determine had irregular pulldown in future captures? Is there a freeware tool or are you just stepping through frame-by-frame. |
|
14th November 2009, 00:20 | #552 | Link |
Aging Video Hobbyist
Join Date: Dec 2004
Location: Off the Map
Posts: 2,461
|
I'm considering a Sony All-in-One PC for a guest bedroom which has an Nvidia GT240M (note: mobile) chipset. I can't find this chipset to be supported with Nvidia's latest 186.81 for Vista/7 64-bit. Instead, there's a download on Sony's site which is listed as 8.15.11.8647. I can't relate this to anything: does anyone here know if 8.15=186.81?
Alternatively, does anyone here have a GT240M and use it successfully w/DGIndexNV? |
14th November 2009, 00:47 | #553 | Link | ||
Registered User
Join Date: May 2008
Posts: 1,840
|
Quote:
Quote:
I haven't used GT240M with DGNV. |
||
14th November 2009, 06:11 | #555 | Link |
Guest
Join Date: Jan 2002
Posts: 21,901
|
So there is no soft pulldown at all. Thus there is no pulldown to ignore and thus no possible AV sync issues due to ignoring irregular soft pulldown. The guideline I gave you applies only to streams with soft pulldown (pulldown using flags rather than hard field duplication).
Last edited by Guest; 14th November 2009 at 06:19. |
14th November 2009, 15:28 | #556 | Link |
Aging Video Hobbyist
Join Date: Dec 2004
Location: Off the Map
Posts: 2,461
|
Many thanks for your input. It appears therefore that Sony's specific driver is behind Nvidia's, which is to be expected of course. I will have to re-think my attraction to the All-in-One concept, as all the designs I've seen use "mobile" and/or proprietary components...
|
14th November 2009, 20:40 | #557 | Link |
Guest
Join Date: Jan 2002
Posts: 21,901
|
Version 2.0.0 beta 3
* Revise detection of scambled audio so that streams that are marked as scrambled in the PMT but which are not actually scrambled are not rejected.
* Fix crashes when upscaling streams with soft pulldown. * Implement Force Film mode for MPEG2. MPEG2 pulldown handling is now complete, including frame pulldown. Work is ongoing to complete full pulldown handling for AVC and VC1. Currently AVC can be Honor or Ignore but not Force Film, and VC1 can only be Ignore. Neither AVC nor VC1 yet support frame pulldown. http://neuron2.net/dgavcdecnv/dgdecnv200b3.zip Last edited by Guest; 14th November 2009 at 20:56. |
15th November 2009, 00:17 | #558 | Link |
Guest
Posts: n/a
|
Is the force film mode meant to remove the 3:2 pulldown and change the framerate to 23.976? I've just tried it out and when looking at the output it still has the 3:2 pulldown, it also has the same number of frames as the input. From what i can see it has just changed the framerate to 23.976 as the video is now about 10 minutes longer than before.
When comparing to the same option in DGindex 1.5.6 my output is 61171 frames and around 42 minutes where as the NVTools version is 76464 frames and around 53 minutes. |
15th November 2009, 00:32 | #559 | Link |
Registered User
Join Date: Oct 2008
Posts: 17
|
I tried Beta3 with the problem capture (irregular pulldown) mentioned above. Used Force Film in DGIndexNV then encoded with
LoadPlugin("<path>\DGDecodeNV.dll") DGSource("SpeedNov03b_de.dgm",deinterlace=1, resize_w=1280,resize_h=720) colormatrix() and my 45:07 29.97 fps source video ended up as a 55:42 23.976 fps file... I think I'm misunderstanding what you said in Post #544. Last edited by adiabatic; 15th November 2009 at 00:35. |
Thread Tools | Search this Thread |
Display Modes | |
|
|