XviD1.1beta2 not read anymore on KiSS standalone

[Jackzeripper]

hello,
just a little problem with beta2 : XviDs made with it are not read anymore on KiSS DP 1000 (chip Sigma Designs EM-8500). Parameters are exactly the same than beta1 that works perfectly (DNX HT PAL, Bvop at 1, packed bitstream). I remade a 2nd pass with beta1 and it is read again ... on two different movies.

:(

[pelle412]

I have a LiteOn LVD-2001 (EM-8500) and I haven't had any problems with beta2. I encode the same way I did with beta1.

[Sharktooth]

Originally posted by Jackzeripper
hello,
just a little problem with beta2 : XviDs made with it are not read anymore on KiSS DP 1000 (chip Sigma Designs EM-8500). Parameters are exactly the same than beta1 that works perfectly (DNX HT PAL, Bvop at 1, packed bitstream). I remade a 2nd pass with beta1 and it is read again ... on two different movies.

:(
Try this version: http://www.aziendeassociate.it/cd//XviD.cvs.head.exe and see if it works.

[Koepi]

Does that build have the "other" userdata string for packed bitstream? (the old one instead the new one which DXN suggested to us?) Then this would indicate a firmware bug of the player.

[Sharktooth]

dunno. i only read the autogk 2.06 readme and this build was included. It seems to fix problems with some standalones.

[Jackzeripper]

hello,
the cvs version has still the "DivX503b1393p" USER string ... and isn't read. Same thing without "packed bitstream". I'm not so sure this new string is a good thing, at least for KiSS hardware, maybe for new standalones...
The "old" string "DivX999b000p" works better on KiSS.

I "downgrade" to beta1, that remains a f... good build ! :cool:

see you ;)

[Jackzeripper]

Originally posted by Koepi
the old one instead the new one which DXN suggested to us.

Don't listen to them... :rolleyes:

[vladlp]

I have a Scott 842 (Cosmic co-301 clone, EM-8500) and I haven't had any problems with beta2 too. Even more, I have added additional profile that is complytly the same as DNX HT PAL, but have no ristriction for 1 bvop, and use 2 bvop and everysing works fine.

[bond]

Originally posted by Jackzeripper
[B]hello,
the cvs version has still the "DivX503b1393p" USER string ... and isn't read. Same thing without "packed bitstream".aha so probably the user string isnt the cause, unless xvid also adds the userstring inclusive the "p" at the end for not packed encodes

apart from that the divx profiles dont allow unpacked 1 b-frame streams, so when choosing the divx profile in xvid you shouldnt be allowed to untick packed bitstream

[Jackzeripper]

hi,
thank you for your answer.
B-vops @ 2 works perfectly on KiSS but my KiSS DP-1000 runs with an "old" firmware (2.7.6), because new firmwares (2.8.0, 2.8.5, 2.9.1) bring much more problems than solutions on that standalone, that may be the cause...
A friend has a DP-450, not with last KiSS firmware, and he can't read beta2 as well.

[len0x]

FYI the problem with official beta 2 build and standalones is: when DXN profiles are used along with b-frames then xvid doesn't signal ASP into the stream so, so advanced features (like custom matrixes in case of AutoGK) won't be played properly in hardware.

@Koepi - is there a chance of having that CVS fix build by you officially?

[bond]

Originally posted by len0x
[B]FYI the problem with official beta 2 build and standalones is: when DXN profiles are used along with b-frames then xvid doesn't signal ASP into the stream soindeed, xvid signals simple profile when choosing divx5 profiles

so advanced features (like custom matrixes in case of AutoGK) won't be played properly in hardwareafaik custom matrices are not allowed with the divx5 profiles anyways, but b-frames are and therefore signalling simple profile is wrong, as b-frames are not allowed in SP

[len0x]

Well, all I know is that for instance MTK chipset players can't play custom matrixes when DXN profile is selected in beta 2 (b-frames are not the problem), but can with the fix from CVS head.

[SeeMoreDigital]

Originally posted by len0x
Well, all I know is that for instance MTK chipset players can't play custom matrixes when DXN profile is selected in beta 2 (b-frames are not the problem), but can with the fix from CVS head. I have not tried this setting!

There does not seem to be any problems generating 1B-VOP and multiple B-VOP encodes using the "Unrestricted" profile, with or without packed bit-stream.

I've tested such encodes in devices fitted with Sigma's EM851x chip-set (http://www.sigmadesigns.com/products/em8510.htm) and their EM8620L chip-set (http://www.sigmadesigns.com/products/em8610Lseries.htm). And also MediaTek's MT1389xx chip-set.


Cheers

[Poutnik]

I am getting confused by this or related threads.
I am going to make my first standalone aimed XviD and would like maximum compatibility.
I do not know target HW, just know it can play Divx.
I understand not using GMP, QP, maybe 2+ B-VOP, not sure packed bitstream.

But:
Should I use DXN profiles, or can use ASP or even unrestricted ?
Can I use custom matrices ?
Should I avoid those ones with coefficients <16 ( but DC one ) ?
( some of them are noted having troubles )
Should I set FourCC as DIVX ( DIV50 ) ?

(Using either Koepi 1.1b2, or CVS(06?0405) )

Thanks in advance for hints or links.
---
I use the search, but not very clever from results.
(As non native speaker there is real danger of bad or misspelled keywords. )

[Jackzeripper]

you'd better not use GMC /Q-Pel and use consecutive B-Vop only at 1. use DXN HT profile. To use custom matrices with DXN profiles, you must select ASP or unrestricted, choose your MPEG-custom matrice, and then reselect DXN.
XVID's FourCC is read by almost every new standalones (my old KiSS does).
beta2 seems to be unreadable only on some EM8500 chipset (KiSS 1000, 450, probably this old firmware).
Beta1 works perfectly on my standalone (KiSS 1000 with firm. 2.7.6)

[bond]

Originally posted by Jackzeripper
you'd better not use GMC /Q-Pel and use consecutive B-Vop only at 1. use DXN HT profile. To use custom matrices with DXN profiles, you must select ASP or unrestricted, choose your MPEG-custom matrice, and then reselect DXNif this really leads to that custom matrices are used with dxn profiles, than the xvid gui is borked, as dxn profiles dont allow the useage of custom matrices, so you should not be allowed to combine custom matrices and a dxn profile

[SeeMoreDigital]

As far as I can see... It is not possible to create "Custom MPEG Matrices" using any of the DXN Profiles!

http://img118.echo.cx/img118/9651/xviddxnprofiles6av.gif

So in this regard XviD1.1 beta2 is working fine ;)


Cheers

[Poutnik]

DXN Profiles do not even allow to choose H263 vs std MPEG matrixes.

I have chosen ASP5 with custom MPEG.
I select DXN HT PAL
Then both quantization type box (still showing "custom-MPEG" )
and "Edit matrix" button are dimmed.

What kind of quantisation DXN use ?

[celtic_druid]

They use h.263, that is why the profiles lock it to that.
I did some custom MTK profiles in a few builds. One also included the original DXN patch with a strict DXN check box.

The MTK profiles were basically DXN HT, but with qpel unlocked, along with custom quants. So basically you get DXN HT, but with custom quants.

[BigDid]

Originally posted by celtic_druid
They use h.263, that is why the profiles lock it to that.
I did some custom MTK profiles in a few builds. One also included the original DXN patch with a strict DXN check box.

The MTK profiles were basically DXN HT, but with qpel unlocked, along with custom quants. So basically you get DXN HT, but with custom quants.
Hi Celtic_druid,

I still have your MTK profiles (as a few others in unite-video) does it needs updating for use with the beta2 ?

Did

[celtic_druid]

For the last revision (the one with updated DXN profiles), no. Just a few files to edit and it should work nicely with beta2.

[BigDid]

Originally posted by celtic_druid
For the last revision (the one with updated DXN profiles), no. Just a few files to edit and it should work nicely with beta2.
:)
Well it does work indeed, but as the encoder GUI has changed (koepi) I was wondering... Thanks for answering.

Edited: the old (celtic)xvidfw.dll seems working for standard autogk use (profile As L5 or is it A5 Ls?)

Did

[Poutnik]

Originally posted by celtic_druid
They use h.263, that is why the profiles lock it to that.
I did some custom MTK profiles in a few builds. One also included the original DXN patch with a strict DXN check box.

The MTK profiles were basically DXN HT, but with qpel unlocked, along with custom quants. So basically you get DXN HT, but with custom quants.

Maybe I can make my friend to see what chip is in his player
and then find its capabilities.

If understand things well, sub16 CQMs (like my favourite EQMV3ULR,LR,HR) could be dangerous, but should be safe with
max quants = 2 and maybe Trellis OFF....

[celtic_druid]

Current cvs with MTK profiles: http://celticdruid.no-ip.com/test/xvidvfwtest.7z

Should work fine on Sigma based players.

xvidvfw.dll only. Use cvs xvid.ax and xvidcore.dll.

Oh yeah. Max zones = 128.

[Jackzeripper]

thanks for this link :) I'll try this build for my KiSS (Sigma chipset)


and...

http://cinergon.free.fr/IMG/Shot173.jpg

here, does MPEG custom or H.263 works ? :rolleyes:

maybe H.263 even if I choose MPEG custom, that in fact I never choose for DXN encodes... :D

[bond]

Originally posted by Jackzeripper
here, does MPEG custom or H.263 works ? as i trust in xvid, i would say h.263 :D

[len0x]

Originally posted by celtic_druid
Current cvs with MTK profiles: http://celticdruid.no-ip.com/test/xvidvfwtest.7z


What is the difference between MTK and MTK 6000 profiles?

[BigDid]

Originally posted by len0x
What is the difference between MTK and MTK 6000 profiles?
Hi Len0x,

Basically MTK is an extension of DXN HT tuned for the Mediatek chip, from Celtic_Druid post up this page:
"The MTK profiles were basically DXN HT, but with qpel unlocked, along with custom quants. So basically you get DXN HT, but with custom quants."

So it is 4000 kbps but some (many?) Mediatek based players like the H&B 3220 accepts 6000kbps so Celtic kindly made another profile for 6000kbps; works fine :)

Did

[len0x]

I see, so it 4000 vs 6000... I wonder if there is really any difference in having VBV set at 6000 or not having any profiles at all for those mediatek players. I remember having Yamada 6600 for a little while and despite the fact that I didn't use any VBV features I still was able to play everything smoothly.

[BigDid]

Originally posted by len0x
I see, so it 4000 vs 6000... I wonder if there is really any difference in having VBV set at 6000 or not having any profiles at all for those mediatek players. I remember having Yamada 6600 for a little while and despite the fact that I didn't use any VBV features I still was able to play everything smoothly.
There is a difference: it is stuttering or, depending on the SAP, stop playing or not starting to play. If you remember, I asked a while ago ( a few months) to have access to the DXN HT profile in AGK. It is accessible now and thank you for that.
In the meanwhile I tried other solutions.

One was and still is to lower the final bitrate (by lowering the final file size) so with time and efforts you can manage it with a fairly good final bitrate (my limit is around 1200/1500kbps, discussion in another thread on that subject) but no "high" bitrate.

Here comes the DXN HT profile you raise the bitrate (and the size) and the limiter does its job; you can have high bitrate but quick motion scenes will degrade in accordance (4000 kbps instant), nothing is perfect !

So with the MTK 6000 profile the quick motion scenes will less degrade (6000Kbps instant) or degrade slower depending on the level of the bitrate :)

To me, It's a matter of compromise or choice as the SAP chipsets won't, at least in a near future, accepts very high bitrate :(

Did

PS: still no encoding guru, this is why I still appreciated and use AGK :)

[Jackzeripper]

will it be possible to have a cvs head with old "DivX999b000p" userdata string on beta2 ? :rolleyes: (

[celtic_druid]

So you want DivX999b000p instead of DivX503b1393p? Shouldn't be that hard. Just change #define DIVX5_ID.

[Sharktooth]

What's the reason for that?

[bond]

you can always change the userdata on existing files with mpeg4modifier

[Jackzeripper]

thanks for the tip. I'll try. :)

[Jackzeripper]

Originally posted by Sharktooth
What's the reason for that?

it seems this new userdata string makes by XviDs unredable on Kiss DP-1000 standalone : see 1st post;)

[Sharktooth]

It's not the userdata...
The answer is on Page 1... and btw you still need to update the firmware.

[Jackzeripper]

I won't because new KiSS firmwares (2.8.0, 2.9.1) don't work on my old chipset (not the same revision, not the same DVD player) :(

many people try the neww firmwares and downgrade to oldest

[Jackzeripper]

Originally posted by bond
you can always change the userdata on existing files with mpeg4modifier

isn't there an other solution : mpeg4modifier needs .NET v1.1 Framework and I haven't DSL to download 108 Mo... :(

[Leak]

Originally posted by Jackzeripper
isn't there an other solution : mpeg4modifier needs .NET v1.1 Framework and I haven't DSL to download 108 Mo... :(

That's the SDK you're posting about; all you need are the .NET redistributables (http://www.microsoft.com/downloads/details.aspx?FamilyID=262d25e3-f589-4842-8157-034d1e7cf3a3&DisplayLang=en), clocking in at a slightly smaller 23.5 megabytes... (you wouldn't happen to be French, would you? ;))

np: Autechre - Radio 10.04.05

[Jackzeripper]

yes, I have seen :rolleyes:
only 23 Mb (yes I'm french :D )

Let's talk about mpeg4modifier in 3 hours of download... :)

[Jackzeripper]

Well, with mpeg4modifier I only change in "DivX999b000p" the userdata string on a XviD1.1beta2 movie and...

...this XviD11beta2 movie is now PERFECTLY read on my KiSS standalone. :)
So, the change of the userdata string in the beta2 is the problem.