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. |
14th March 2013, 23:30 | #2881 | Link | |
Registered User
Join Date: Dec 2002
Posts: 1,022
|
Quote:
Compute 3.0 (using sm_30) Memory 2049 MB L2 cache 393216 bytes Symmetric multiprocessors 7 Processor clock 980 MHz Memory bus width 192 bits GPU/PureVideo version GK104/VP5 1: "Quadro 4000" Compute 2.0 (using sm_30) Memory 2049 MB L2 cache 524288 bytes Symmetric multiprocessors 8 Processor clock 950 MHz Memory bus width 256 bits GPU/PureVideo version unknown AVC: cuvid MPG: cuda VC1: cuvid |
|
15th March 2013, 00:10 | #2882 | Link |
Guest
Join Date: Jan 2002
Posts: 21,901
|
That looks fine.
Can you save a project and serve video via the script into VirtualDub (without using BDRB)? There's no reason I can see for there to be any problem, unless maybe your BDRB settings are now wrong for the DGDecNV paths, etc. You can also try changing the INI file to use the Quadro (see manual for auxiliary INI file options). Finally, you might try connecting a monitor to the 660. We'll have to get this resolved before I give you the test load we discussed, since there's no point if you can't run DGDecNV. Last edited by Guest; 15th March 2013 at 00:15. |
15th March 2013, 00:51 | #2885 | Link | |
Registered User
Join Date: Dec 2002
Posts: 1,022
|
Groovy. I'll test it tomorrow, off to bed now.
Quote:
|
|
15th March 2013, 17:22 | #2887 | Link |
Registered User
Join Date: Dec 2002
Posts: 1,022
|
About the RAM issue. Nvidia Control Panel claimed the system was running Quadro drivers for both the Quadro 4000 and the 660 Ti, and I could tell from a desktop gadget BD-RB used the 660 Ti for decoding when set for DGDecNV use.
So I re-installed the latest GeForce drivers, rebooted, checked Nvidia Control Panel to make sure the drivers took, and gave BD-RB a backup job using DGDecNV. It's been running a few hours now and RAM usage has remained normal. Looks like case closed. |
15th March 2013, 20:38 | #2889 | Link | |
Registered User
Join Date: Dec 2002
Posts: 1,022
|
Quote:
My knowledge of the subject is close to zero but it sure looks like something's leaking a whole lot of memory. Sysinternals' RamMap shows me something is allocating huge loads of RAM to Modified Memory, but in the Processes tab the largest chunk of Modified RAM is taken by Avast: 7400 Kilobytes. Next biggest is svchost with 3900KB. One thing to note: this behaviour was triggered by me aborting a BD-RB job and starting another. The system finished one BD-RB backup job successfully earlier today, and when I started another an hour later, RAM use was normal. Last edited by colinhunt; 15th March 2013 at 20:49. |
|
16th March 2013, 00:05 | #2891 | Link |
Registered User
Join Date: Dec 2002
Posts: 1,022
|
Hmm... but BD-RB did nothing like this before I installed another Nvidia GPU in the PC. And even though my testing is still incomplete, it's beginning to look like this RAM issue does not apply when using DirectShow or LAVF.
|
16th March 2013, 15:28 | #2893 | Link | |
Registered User
Join Date: Dec 2002
Posts: 1,022
|
Yes, I did. I thought that maybe aborting a job left something "open", so to speak. I'm not a programmer, far from it unfortunately, but it looks to me like finishing a BD-RB job closes/resets things properly but aborting a job does not. Does that make any sense?
Quote:
|
|
16th March 2013, 16:01 | #2894 | Link |
Guest
Join Date: Jan 2002
Posts: 21,901
|
I don't know about BDRB internals. That's why I thought asking jdobbs about it would be appropriate. I have no other reports of similar behavior.
When you get into the high RAM usage state, can't you use Task Manager (or similar) to see who is holding the memory? |
16th March 2013, 16:19 | #2895 | Link | |
Registered User
Join Date: Dec 2002
Posts: 1,022
|
Quote:
RamMap lets me browse through the Modified Memory area for process names etc. but the only thing I found were a few mentions of the .mbtree file. I've been running tests all morning but they've turned out inconclusive. In fact, I haven't managed to "force" the system into a high RAM usage state once! Not with DirectShow, LAVF or DGDecNV. I don't know what the hell is going on here... :/ What's more, this is the only one of my three encoding rigs doing this (at random, apparently). It's also the only rig which has two Nvidia GPUs installed - and this behaviour started after I installed the 2nd Nvidia GPU. And the high RAM use state has so far occurred only when BD-RB was set up for DGDecNV. Typical RAM use during indexing: Typical RAM use during encode (1st pass): High RAM use state (a minute later the Modified RAM was over 10GB): Processes listing during high RAM use state: Last edited by colinhunt; 16th March 2013 at 16:58. |
|
30th March 2013, 06:48 | #2898 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,752
|
This float value is not exact ... there are presets or fractions instead: AssumeFPS("ntsc_double") or AssumeFPS(60000, 1001).
http://avisynth.org/mediawiki/FPS |
30th March 2013, 12:16 | #2899 | Link |
Registered User
Join Date: Jul 2011
Posts: 50
|
The problem is not really the framerate. The problem is that it only takes 25FPS along the movie. I mean, my video have 284286 frames in 59.64FPS (1:19:03) but DGIndexNV only recognize 142143 frames (its interlaced but i didnt change any option to deinterlace it). If i force it changin the dgi or using assumeFPS final lenght will be 39:31 and video will be speed up (coz it shorter than the source one).
.. .. .. 142139:FRM 5 29 -1 5 IDR 284558594 142140:FRM 7 0 -1 5 142141:FRM 5 1 -1 5 142142:FRM 5 2 -1 5 SIZ 720 x 480 FPS 25000 / 1000 CODED 142143 PLAYBACK 142143 0.00% FILM ORDER 0 And changing coded/playback wont work coz there are no info of the other ~142142 frames. Last edited by stranno; 30th March 2013 at 12:19. |
30th March 2013, 12:32 | #2900 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,752
|
Why 59.64? 2*29.97=59.94
And then this SD resolution ... makes me wonder why you do believe in "double_ntsc" at all; this may be a "field rate", not a "frame rate". Which analysis tool did you use, that it got confused by PAFF interlacing? Which makes me wonder: What kind of video format is it originally — MPEG2, VC-1, MPEG4-AVC? A "full" report created by a recent MediaInfo would be useful. Last edited by LigH; 30th March 2013 at 12:35. |
Thread Tools | Search this Thread |
Display Modes | |
|
|