[RESOLVED] DGDecIM bug or not ?

This is the home of QuickSync (aka Intel Media SDK) stuff.
Post Reply
DAE avatar
Nico83500
Posts: 78
Joined: Thu Jan 02, 2014 9:28 am

[RESOLVED] DGDecIM bug or not ?

Post by Nico83500 »

Hi,
I just noticed there is perhaps a bug in DGDecIM latest version only (b21 if I'm not wrong).
From a 1920 x 1080 source, the output is allways 1920 x 1088 ! This problem was not present in previous version.
Thank you.
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: DGDecIM bug or not ?

Post by admin »

Try this one:

http://rationalqm.us/misc/dgdecim_b50.zip

The previous versions did not auto crop the bottom 8 pixels when the coded size is 1088.
DAE avatar
Nico83500
Posts: 78
Joined: Thu Jan 02, 2014 9:28 am

Re: DGDecIM bug or not ?

Post by Nico83500 »

Thanks, I’ll try and let you know.
But only the latest version (compiled with INDE 2015) isn’t OK, previous versions were OK.
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: DGDecIM bug or not ?

Post by admin »

Check that the CLIP line in the index file shows 0 0 0 8 for those streams. So it is DGIndexIM that must be the correct one and you have to remake your index file, or edit it by hand if you don't want to re-index.
DAE avatar
Nico83500
Posts: 78
Joined: Thu Jan 02, 2014 9:28 am

Re: DGDecIM bug or not ?

Post by Nico83500 »

So I have compared b19, b21 and b50 index files and results are the same :

b19 :
DGAVCIndexFileNV14 DGIndexIM beta 19 X32
c:\DGDecIM_b19\

00098.track_4113.264 21664500284

DEVICE 0
DECODE_MODES 0,1,0
STREAM 0
CLIP 0 0 0 8
RANGE 0 0 21664500283 0
AUDIO

SIZ 1920 x 1088
FPS 120000 / 5005
CODED 188857
PLAYBACK 188857
0.00% FILM
ORDER 0
b21 :
DGAVCIndexFileNV14 DGIndexIM beta 20 X32
c:\DGDecIM_b21\

00098.track_4113.264 21664500284

DEVICE 0
DECODE_MODES 0,1,0
STREAM 0
CLIP 0 0 0 8
RANGE 0 0 21664500283 0
AUDIO

SIZ 1920 x 1088
FPS 120000 / 5005
CODED 188857
PLAYBACK 188857
0.00% FILM
ORDER 0
b50 :
DGAVCIndexFileNV14 DGIndexIM beta 50 X32
c:\DGDecIM_b50\

00098.track_4113.264 21664500284

DEVICE 0
DECODE_MODES 0,1,0
STREAM 0
CLIP 0 0 0 8
RANGE 0 0 21664500283 0
AUDIO

SIZ 1920 x 1088
FPS 120000 / 5005
CODED 188857
PLAYBACK 188857
0.00% FILM
ORDER 0
But with b19 width = 1920 and height = 1080 and with b21 width = 1920 and height = 1088.

I have not tried b50, do you think it could solve the problem even if index files are identicals ?

Thanks !

Edit : I've launched an encoding with b50, I'll tell you the result.
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: DGDecIM bug or not ?

Post by admin »

Hi Nico,

Honestly I can't remember exactly when I fixed it, but running b50 things work fine for me. If that's not the case not for you, we'll get to the bottom of it.

It doesn't matter if the indexes are the same, what matters is if the DLL honors that CLIP line. My previous statement was a bit imprecise, we need the indexer to set CLIP and we need the DLL to honor it.
DAE avatar
Nico83500
Posts: 78
Joined: Thu Jan 02, 2014 9:28 am

Re: DGDecIM bug or not ?

Post by Nico83500 »

Hi,
I've tried with a movie and b50, the issue seems to be solved :)
I'm going to try with an other movie to be sure...
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: DGDecIM bug or not ?

Post by admin »

Thanks for the test results, Nico. If it works for that movie it will work for all of them. ;)
DAE avatar
Nico83500
Posts: 78
Joined: Thu Jan 02, 2014 9:28 am

Re: DGDecIM bug or not ?

Post by Nico83500 »

Yes, all movies encoded by b50 are OK, thank you again :)
A last question : why 1 of 20 movies is OK with b21 ? Output resolution is 1920 x 1080 and not 1920 x 1088 like others ? Even if the resolution is OK with b21, perhaps I should re-encode this movie ?
Thank you !
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: DGDecIM bug or not ?

Post by admin »

Yes, it could be that the single movie is in fact only 1080. You can check that very easily with DGIndexNV. Look at the 'Coded size' in the info dialog.
DAE avatar
Aleron Ives
Posts: 126
Joined: Fri May 31, 2013 8:36 pm

Re: [RESOLVED] DGDecIM bug or not ?

Post by Aleron Ives »

Such a stream would be non-standard though, right? It's my understanding that H.264 requires mod16 dimensions and allows you to specify cropping values to achieve your desired AR, but actually encoding to a non-mod16 resolution would produce a technically invalid stream.
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: [RESOLVED] DGDecIM bug or not ?

Post by admin »

You are correct but the poster did not state that this movie was AVC.
DAE avatar
Nico83500
Posts: 78
Joined: Thu Jan 02, 2014 9:28 am

Re: [RESOLVED] DGDecIM bug or not ?

Post by Nico83500 »

You are right ;)
Movies with a resolution output issue (1920x1088 instead of 1920x1080) with b21 are H264, but VC1 was OK with b21 (output resolution 1920x1080).
So the right resolution is 1920 x 1088 ? Why output resolution is 1920 x 1080, in order to match with 16/9 format ?
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: [RESOLVED] DGDecIM bug or not ?

Post by admin »

Yes, 1080 is to match 16:9. But coding is most efficient with 16-pixel blocks, so they are padded out for coding. DGIndexNV shows both the coded and display sizes in the info dialog.
Post Reply