DGAVCDec 1.0.9

[ACrowley]

Im a little bit confused..

1.0.9 is the latest Version ,including dll

Megui made a update on dgavcindex and dgavcdecode today. Its DGAVCIndexd/Decode 1.0.1-1 ? The exe and dll are 1.0.0.0 from 30.04.2009 ? So its a updated Version ?

[Guest]

I don't know anything about those version numbers. You can ask the Megui guys what is going on.

[Sharktooth]

@ACrowley: No, it's 1.0.1 (the -1 means it was repackaged - the reason for repackaging was: missing libavcodec.dll).
however, ill update degavcindex/dec packages with the new version as soon as i get home.

[ACrowley]

Originally Posted by Sharktooth

@ACrowley: No, it's 1.0.1 (the -1 means it was repackaged - the reason for repackaging was: missing libavcodec.dll).
however, ill update degavcindex/dec packages with the new version as soon as i get home.

Ok, Thx

obviously its the old 1.0.1 Version. Mhh...so i used the old dgavcdecode Decoder for some BluRay to x264 encodes via megui. I havent noticed that megui use/updates a old Version.
But i cant see any Problems in these x264 encodes encoded through dgavcdec.dll 1.0.0.0

[krosswindz]

I am not sure if this has been discussed earlier, but I find that encoding BluRay to x264 using AVCSource is 4-5 times slower that using DirectShowSource with ffdshow+haali for me. Is this a known issue or am I doing something weird. I would prefer to use AVCSource as it is frame-accurate while DirectShowSource decoders neednt be frame-accurate. Any information regarding this is appreciated.

[Guest]

Nah, they both use the same decoder: libavcodec. You must have changed something else between the cases. Five times slower would have been noted by now.

[stpdrgstr]

Hi neuron2

I'm getting this problem with lossless encoded h264 raws.



While getting this warning when loading the h264 stream.

PicParset 0 references are invalid (uninitialized) Sequence Parameter Set with ID 0, expect the unexpected... (lol yeah)

Hit Yes continue notifying this specific error type; hit No to disable it.
Hit Cancel to supress all further errors.

If I press Yes, it goes right away to the second frame, with the same Warning. If there I press Yes again, it will stop displaying the error until I advance to any other frame, where it will display the warning and not show anything else but a black frame. If I press No, I get the problem in the screenshot.

Here's the sample

[nixo]

You need to use the old lossless mode, meaning x264 builds earlier than revision 994. The version of libavcodec.dll in dgavcdec is too old to decode the new lossless mode.

--
Nikolaj

[stpdrgstr]

Damn, that's not cool

Is there any difference from indexing it through here and loading it with DSS2 using CoreAVC or libavcodec from lastest ffdshow?

[b66pak]

i have the same problem as stpdrgstr...how can be properly decoded the new x264 lossless mode?
_

[ChronoCross]

Originally Posted by nixo

You need to use the old lossless mode, meaning x264 builds earlier than revision 994. The version of libavcodec.dll in dgavcdec is too old to decode the new lossless mode.

--
Nikolaj

Originally Posted by b66pak

i have the same problem as stpdrgstr...how can be properly decoded the new x264 lossless mode?
_

see the above quote.

[LoRd_MuldeR]

Originally Posted by b66pak

i have the same problem as stpdrgstr...how can be properly decoded the new x264 lossless mode?
_

Try muxing your "raw" H.264 stream into an MKV container via MKVToolnix and then use FFVideoSource() or even DirectShowSource() instead of AVCSource().

[G_M_C]

Originally Posted by Sharktooth

@ACrowley: No, it's 1.0.1 (the -1 means it was repackaged - the reason for repackaging was: missing libavcodec.dll).
however, ill update degavcindex/dec packages with the new version as soon as i get home.

Talking about wich;

I know you used a "custom" libavcodec in your package Neuron2. But i forgot if it was possible to to update your package with a current "regular" vversion of libavcodec. I seem to remember that that was possible, but i'm not shure about it atm.

I ask this cause libavcodec changes once in a while, and getting more/better/faster/whatever decoding through DGAVCIndex (if applicable) by simply changing the libavcodec is simple to do.

[StifflerStealth]

I have a MKV with one h264 video stream and one aac audio stream. I demux them out with mkvextract from the MKVToolNix package, and then open it with the indexer. I then use that file with my AVS script. The audio is converted to Wave64 which is opened with the NicAudio package. The two streams are then AudioDubed together. I use Info() at the end of the script. The Indexer reports correctly that the video is 29.97FPS, the info function shows the video frame rate as 60000/2002 instead of 30000/1001. Also, the video plays fast in MPC. The Info function shows the video as being 18 minutes long and the audio is 22 minutes long. The correct time is 22 minutes. The video is all there, but playing faster than what it should. I tried all three settings under video on the indexer (honor pulldown, ignore pulldown, and force film), but all three settings produce the same results. I looked in the dga file and at the end, there is this:
SIZ 720 x 480
FPS 60000 / 2002
CODED 33629
PLAYBACK 33629

So, it is telling MPC that the frame rate is that number, which is 29.97 FPS, but I have always heard of it as being 30000/1001. Is this the reason why it's playing fast?

[Guest]

Originally Posted by G_M_C

But i forgot if it was possible to to update your package with a current "regular" vversion of libavcodec.

It's not possible because I check that it is the DLL that I supply. I cannot use the newer versions because they are broken for accurate frame random access.

[Guest]

Originally Posted by StifflerStealth

So, it is telling MPC that the frame rate is that number, which is 29.97 FPS, but I have always heard of it as being 30000/1001. Is this the reason why it's playing fast?

No, because 60000/2002 = 30000/1001. You can just change it to 30000/1001 in the DGA file if you like. I don't expect it to behave any differently.

[G_M_C]

Originally Posted by neuron2

It's not possible because I check that it is the DLL that I supply. I cannot use the newer versions because they are broken for accurate frame random access.

Thx for the fast reply Neuron2 !

[nm]

Originally Posted by StifflerStealth

The Indexer reports correctly that the video is 29.97FPS, the info function shows the video frame rate as 60000/2002 instead of 30000/1001. Also, the video plays fast in MPC. The Info function shows the video as being 18 minutes long and the audio is 22 minutes long. The correct time is 22 minutes.

Those numbers suggest that the correct framerate is ~24 fps. Upload a sample clip (to MediaFire, for example).

[StifflerStealth]

I uploaded a segment to MediaFire. MPC detects it as 29.97 FPS as well as the AVC Indexer. Avidemux (latest SVN build) always gets the audio out of sync when I try to edit it (Bleach episodes have annoying end of part 1 things that I am trying to edit out for fun and experience and do some filters to enhance the picture. ). Also, I tried the indexer that came with FFmpegSource2, and it showed the video as 24 fps, but it was out of sync with the audio. -_-' So, the detection of the fps has a bug somewhere, either this tool or ffmpegsource2 or both. :P Or something else is wrong, like my ripping/coding. I thought I got all the details correct for the encode. Anyways, I hope you can tell me what's wrong and how to open this in AviSynth or other programs so that the video is in sync.

{Link removed since issue solved}

Thanks.

[Guest]

@StifflerStealth

You have posted an MKV. Where did you get it?