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. |
18th September 2008, 18:16 | #221 | Link |
Registered User
Join Date: Mar 2005
Location: Finland
Posts: 2,641
|
Perhaps there is some hardware postprocessing going on even when the video is not deinterlaced. Denoising might cause such a difference, for example. You could do some lossless encodes with both hardware and software decoding and compare the output frame-by-frame.
|
18th September 2008, 19:23 | #222 | Link |
Registered User
Join Date: Apr 2002
Location: Germany
Posts: 4,926
|
Ahh right crypto you should make sure your settings in the Control Panel dont include Nvidias Denoiseing or Sharpening Post Pro (Shaders) crazy maybe it can applied this way too
__________________
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 |
18th September 2008, 23:21 | #223 | Link |
Registered User
Join Date: May 2002
Posts: 16
|
A quick test of the Nvidia deinterlacing capabilities. I'm impressed.
The source is a crapy Main@L4.0 ~7.5Mb/s 25fps (Beijing Olimpics 2008 Opening Ceremony 1080i CCTV.ts) http://rapidshare.com/files/14643643...rlace.zip.html All Nvidia processings are turned off (edge=off, noise=off). |
19th September 2008, 00:46 | #229 | Link |
Registered User
Join Date: Mar 2005
Posts: 89
|
Sorry for getting off-topic in-between the lines - between all this discussion on deinterlacing - I will come back to this point later on.
I also checked DGAVCIndexNV on two XP SP3 machines with GeForce 8600 GT, and it is really fantastic. No more artifacts on my AVCHD recordings of my Canon HF100 (which I had with DGAVCIndex before). When trying to install it on the second machine, the plug-in did not load. I installed the latest drivers 177.92 (which seems to be beta; from the "the force within" promotion section of the site), tried it with the "special" cuda drivers, installed the toolkit, nothing worked until I checked again with Sysinternals Processmon. It was finally the nvcuvid.dll which was missing in the system32 directory - after installing this I could even remove the cuda toolkit and reinstall the latest (beta) drivers. I still have some remarks on the tool itself: - When doing a SeparateFields(), BFF seems to be used although even DGAVCIndexNV itself says that it is TFF. Currently, I would have to set an AssumeTFF() before in any script handling with the fields. - I think it has not really clearly been said: TempGaussMC is a bobber which makes an 1080i50 being a 1080p50 while the NVIDIA deinterlacer just outputs 1080p25. This might be interesting for Blu-ray ripping but when it is about scaling while preserving the fields e.g. for an AVCHD-to-DVD conversion, this deinterlacing is useless IMHO - or did I miss something? - One little request: Could you please add the extension "mts" to the list of ts-streams in DGAVCIndexNV? Itīs the extension used by Canon AVCHD-Cams. |
19th September 2008, 01:38 | #230 | Link | |||||
Guest
Join Date: Jan 2002
Posts: 21,901
|
Quote:
Quote:
Quote:
Quote:
Quote:
Last edited by Guest; 19th September 2008 at 01:45. |
|||||
19th September 2008, 02:52 | #231 | Link |
x264aholic
Join Date: Jul 2007
Location: New York
Posts: 1,752
|
As a note to everything, please remember that my deinterlacer comparison was very naive, I never changed the TempGaussMC settings so it could theoretically do better.
__________________
You can't call your encoding speed slow until you start measuring in seconds per frame. |
19th September 2008, 03:37 | #232 | Link | |
Registered User
Join Date: Jan 2004
Posts: 849
|
Quote:
1) If AVS is something more than "open file", then avs is a bottleneck negating advantages of hardware decoding 2) If AVS just contains an "open file" statement, then CPU cycles freed up by hardware decoding of source are inconsequential Either way, at least we get greater stream compatibility (with paff and such). Still too bad we don't get encoding speed boost.
__________________
Geforce GTX 260 Windows 7, 64bit, Core i7 MPC-HC, Foobar2000 |
|
19th September 2008, 04:03 | #233 | Link | |
Registered User
Join Date: Mar 2006
Posts: 1,538
|
Quote:
|
|
19th September 2008, 04:31 | #234 | Link |
x264aholic
Join Date: Jul 2007
Location: New York
Posts: 1,752
|
I suppose when it comes to using faster settings, the GPU decoding definitely comes out on top. I'm curious how this would benefit a Core 2 Quad overclocked to 3.2 GHz Those would be -really- starved for data between my decoding Blu-ray, filtering, and encoding.
__________________
You can't call your encoding speed slow until you start measuring in seconds per frame. |
19th September 2008, 06:25 | #235 | Link |
Registered User
Join Date: Jan 2002
Location: San Jose, CA
Posts: 216
|
Unless decode is the bottleneck (ie encode runs at 50+fps) and/or CPU is pegged at 100%, the speed boost for having even infinitely fast decoding would be small. As the numbers from rack04 show, a ~10fps encode gets a 2-5% speed boost.
|
19th September 2008, 06:29 | #236 | Link |
x264aholic
Join Date: Jul 2007
Location: New York
Posts: 1,752
|
As I said, I'm curious what the results would be on a workhorse like I just described I plan on upgrading to such a system in the near future so this will be helpful having one thing offloaded from my chain.
Also, the encode doesn't need to run at "50+ fps" for it to be a bottleneck. The decode eats up a significant portion of my cpu time on my desktop computer, where I have a lowly Opteron 170.
__________________
You can't call your encoding speed slow until you start measuring in seconds per frame. |
19th September 2008, 06:30 | #237 | Link | |
Registered User
Join Date: Mar 2005
Posts: 89
|
Quote:
I thought that the deinterlacers are just for all those TV-to-DivX encoders that donīt care about fluid movements. Concerning the DVD at double rate: For creating high-quality downconversions of the HD material to SD material, the HD material has first to be bobbed to 1080p50 at best quality (this takes huge time with TempGaussMC). Just then, you can scale it down at high quality. The resulting 576p50 has then to be weaved to 576i50. Any possibility to bob it to 1080p50 at a comparable quality like the deinterlacer would also be a great improvement for a lot of users - at least at PAL land |
|
19th September 2008, 06:33 | #238 | Link |
x264aholic
Join Date: Jul 2007
Location: New York
Posts: 1,752
|
@JK1974: There was a thread on this before. Yes, bobbing with a very high quality bobber like TGMC would produce the best results in both 1080p and 576p, but the reality was that there was VERY little difference between a dumb bob and smart bob when downsizing to 576p.
__________________
You can't call your encoding speed slow until you start measuring in seconds per frame. |
19th September 2008, 07:33 | #239 | Link | |
Registered User
Join Date: Mar 2005
Posts: 89
|
Quote:
|
|
|
|