[RESOLVED] Problem with fps

[checker]

hi,

my fps was @ xvid encode to 220fps with geforce gtx285

but now

with the same hardware @xvid encode 120fps

this speed is too little

what can i do?

greets checker

[admin]

What changed between the two cases?

Type of input video?
Size of input frame?
Size of output frame?
Contents of the AVS script (i.e., what proceesing was done by the scripts)?
Settings for your encoder?
Etc.?

Without more information from you all I can say is all the above things can affect your transcoding speed.

[checker]

I have changed nothing of the first preferences

input video is vob with 25 fps
avs filters is deinterlaced, noise and resize filter

but i have nothing changed, is from one day to the speed so lame

i need help


greets

[admin]

You say you changed NOTHING and one day it just slowed down by 100fps?

How can I possibly help you with that? There's no way to duplicate it and you've given me essentially no useful details at all about what you are doing.

[kypec]

Are you sure that you didn't chage anything at all? Perhaps you (or Windows Update silently) have installed new GeForce drivers...

[cosmix]

Hi.
I have a question. I did ran DGIndexNV file. Dgi and the creation of a file. Avs have a question. How well did my avs script?

LoadPlugin("D:\Program Files\megui\tools\dgindexnv\
DGMultiDecodeNV.dll")
DGMultiSource("D:\Ripy\Wielkie migracje e01.dgi",fieldop=0, deinterlace=0, resize_w=1280, resize_h=720)
Load_Stdcall_Plugin("D:\Program Files\megui\tools\yadif\yadif.dll")
Yadif(order=-1)
crop( 2, 2, -2, -2)

#resize
#denoise

The idea is to use the full power of your graphics card. In this script, after activating the GPU-Z my GPU load ~ 14% and VideoEngineLoad ~ 50-60%. My graphics card is a Palit Geforce GTX460 1GB, and the latest drivers from nvidia.com. I'm using version 2013 dgindexnv and megui I can not install a newer version dgindexnv because it is not a new version DGMultiDecodeNV. There is only DGMultiDecodeNV v.2013

PS. When encoding file. ts HD. to .mkv I had speed 42 FPS. For the graphics card to do more?

Thank you and I hope to help

[admin]

I don't support 2013 anymore. Please start a new thread as you are hijacking this one.

[admin]

Marking resolved due to non-response by OP.

[cosmix]

I had a Nvidia GTX460 graphics card and obtain the result of encoding 75fps (. ts>. mkv-x264). When you change the graphics card on the GTX570, despite more and better-core CUDA clock gets the same result as the previous card. In what may be a problem?
File. ts is the same as recorded with the Nat Geo HD.

I'm using the latest version of MeGUI, x264 codec and DGIndexNV.

I have Windows XP 32bit, processor i7 2600, 2x2GB OCZ 1600MHz RAM.

[admin]

The VP engine clock speed is probably the same and that is the clock that primarily determines decoding performance.

[cosmix]

You think no matter the amount of cores CUDA? What is important is the GPU clock?

[admin]

Is there something about my reply that you do not understand?

[cosmix]

I'm Polish and I have a problem with understanding what your response.

[admin]

What part do you not understand?

[cosmix]

"The VP engine clock speed is probably the same and that is the clock that primarily determines decoding performance."

VP?
...that primarily determines decoding performance?

[admin]

VP is the video processor pipeline, otherwise known in marketing speak as PureVideo. Video decoding is accelerated by means of functionality of the VP engine.

[cosmix]

Simple terms, this means that the faster encoding is not possible?

[admin]

Of course faster *encoding* is possible. Use a faster CPU, use faster settings for your encoder, reduce the resolution, preprocess to reduce detail, etc.

The primary advantages of DGDecNV, as I have said several times, are correct decoding of AVC/MPEG/VC1 in different flavors (such as interlaced VC1, which seems to be problematic for other decoders, for some inexplicable reason; but also with some omissions, such as 4:2:2 and lossless), consistent workflow for AVC/MPEG/VC1, proper pulldown handling, access to hardware deinterlacing/resizing, and, especially, reliable frame-accurate random access. Additionally, DGIndexNV is useful as a stand-alone stream analysis tool. In some scenarios (e.g., transcoding SD/HD to HD on mid/low end CPUs), offloading decoding to the GPU can yield modest speed ups for transcoding, but that is not the raison d'etre of DGDecNV. The prime raison d'etre is the frame accurate serving via Avisynth.

There, I've said it all again.

[laserfan]

The prime raison d'etre is the...

Say what??!!

I think with minor edits you've just written a nice features/benefits paragraph for your DGDecNV web page!

[admin]

Even in English it can be useful to dispel the belief in some quarters that GPU decoding can magically accelerate transcoding rates by large amounts.

[laserfan]

The primary advantages [include] correct decoding...

Well, I like the summary a lot especially that you led with this one. I'd had inexplicable decoding errors myself which found their way (of course) into my encodings and there was no rhyme/reason to it. Very frustrating. But since my exclusive reliance on this tool I never ever get any more glitching. That I love using it in debug mode (with Vdub) for chaptering and editing is certainly nice icing on the cake.