AGK 2.08 + DVP642 = Doesn't play

[esojmc]

OK, "doesn't play" is a lie - it does play but the colors are all messed up and it's basically unwatchable. I have the Philips DVP-642 SA. When I did the compress I selected XviD as the codec and I also selected compatibility->ESS in the hidden options. Everything used to work fine with AGK 2.07.

Any ideas? Thanks.

[unskinnyboy]

Press the 'System Menu' button on your remote twice when the picture gets messed up and then report back.

[esojmc]

Yes, that fixes it but just wondering why it's happening. Anything I can do so it works like it did before?

Thanks.

[unskinnyboy]

This is a bug in the Philips player which should be fixed in the next firmware update. Nothing to do with AutoGK.

[bugmenotwillyou]

Wow thank you alot, i had the same problem Here (http://forum.doom9.org/showthread.php?s=&threadid=94407) and i couldnt figure out why so thanks alot!

[tipsypenguin]

ESS support use to solve this problem. I don't think it's working right in the new beta.

[esojmc]

I've gone back to AGK 2.07 and everything works like it used to.

[mhudson7]

Originally posted by esojmc
I've gone back to AGK 2.07 and everything works like it used to.
I dropped back to 1.95 with complete success. Apparently there's a bug in the ESS support option...

[unskinnyboy]

Please don't jump into conclusions. This issue (garbled picture in DVP642) is known for a long time now, -much- before even 1.95 came out. 1.95 was released on 03/18/05, while I have heard of this issue even starting last year.

[mhudson7]

Originally posted by unskinnyboy
Please don't jump into conclusions. This issue (garbled picture in DVP642) is known for a long time now, -much- before even 1.95 came out. 1.95 was released on 03/18/05, while I have heard of this issue even starting last year.
Good point. For me, however, the garbled picture issue was completely resolved by enabling ess support as far back as the stable release before 1.95 (I believe it was 1.60 or so). Unfortunately, it took me 2 months to figure out that you had to reinstall agk to enable it!

[bassgoonist]

I can imagine the problem being some tiny change in autogk that should be totally insignificant to the player...but because mpeg-4 support is still more or less experimental on hardward players (IMO) little tiny things can change it...
Despsite that...I doubt autogk has anything to do with it, nor should they worry about it.

[unskinnyboy]

About standalone support, copy/pasting an excerpt from my own post from another thread:
Originally posted by unskinnyboy
Have you checked out AutoGK 2.08beta? Now there is an option in the 'hidden options' to enable standalone support. And you can choose between ESS (will restrict bitrate spiking I believe) and MTK/Sigma (this beta uses a new XviD VFW dll packaged for MTK/Sigma chipset support) chipsets. Also looking at another thread here, this beta enables packed bitstream in the AVI and packed bitstream is part of the DXN profile and is more standalone compatible.

[Namcats]

It has to be something related to the 2.08 Beta release, and not the DVP-642 itself. I had the exact same problem with mine. In fact, I just came here intending to post a question about it, but found this first.

With v2.07 and previous versions I had been able to encode perfectly having selected ESS Support for the Phillips. But the very first attempt with 2.08 resulted in the cartoonish (i.e. 16-bit color), even though I had selected ESS Support again in the hidden settings. It's actually nice to know that the "System Key" trick corrects it for playback, but the problem still remains. Up until now I've had to correct the XviD using VirtualDub. That's a 1 to 1.5 hour process in itself.

Could it possibly have something to do with installing the base v1.95 AutoGK with ESS Support, and then selecting ESS Support again for each job after you've upgraded to v2.08? I haven't taken it back that far with mine to find out. I finally had a nice setup with v2.07, so I hadn't wanted to mess with it. I suppose I can do that now because I'll at least have to go back to 2.07. I want them encoded correctly without having to tack on another hour long process...

[mhudson7]

Originally posted by Namcats
Could it possibly have something to do with installing the base v1.95 AutoGK with ESS Support, and then selecting ESS Support again for each job after you've upgraded to v2.08? I haven't taken it back that far with mine to find out. I finally had a nice setup with v2.07, so I hadn't wanted to mess with it. I suppose I can do that now because I'll at least have to go back to 2.07. I want them encoded correctly without having to tack on another hour long process...
Let us know if you figure anything out. I think I'll stay with 1.95 until it's all resolved.

[esojmc]

If you're intersted in trying something new, give avi.NET (http://forum.doom9.org/showthread.php?s=&threadid=94529) a try. It creates files that are playable on the Philips. I've been happy with it.

[Thomas Davie]

I've been using AGK 2.08 to create .avi files that play perfectly well on my and my girlfriend's DVP642; so no, it can't be 2.08 or the DVP642. And this is with; a) DVD backups, b) converts to.avi from my DVD recorder, or c) transcodes from other .avi files.

Tom

[Namcats]

Originally posted by Thomas Davie
I've been using AGK 2.08 to create .avi files that play perfectly well on my and my girlfriend's DVP642; so no, it can't be 2.08 or the DVP642. And this is with; a) DVD backups, b) converts to.avi from my DVD recorder, or c) transcodes from other .avi files.

Tom

Well now, that makes it even more confusing. I test encoded an mpeg-2 last night using 2.08, but didn't enable standalone support, and it still wouldn't playback correctly. I'm taking it back to 2.07 tonight and encoding the same file again. If it plays correctly I'll just stick with the older version. With all other factors being equal, if it plays back correctly it would seem to indicate some small anomoly with the new version that's causing it. Can't make that assumption though until after I see the results. I have no problems with the older version anyway. I don't believe the changes between the two were that significant. I can wait for a newer version and try again then...

[BigDid]

Originally posted by Namcats
... I don't believe the changes between the two were that significant. I can wait for a newer version and try again then...
See main AGK thread and 2.08 & packed bistream thread.

There is a significant change/problem in 2.08, check the workarounds.

Did

[Thomas Davie]

Originally posted by Namcats
Well now, that makes it even more confusing. I test encoded an mpeg-2 last night using 2.08, but didn't enable standalone support, and it still wouldn't playback correctly. I'm taking it back to 2.07 tonight and encoding the same file again. If it plays correctly I'll just stick with the older version. With all other factors being equal, if it plays back correctly it would seem to indicate some small anomoly with the new version that's causing it. Can't make that assumption though until after I see the results. I have no problems with the older version anyway. I don't believe the changes between the two were that significant. I can wait for a newer version and try again then...

I'm doing a test burn on an episode of Doctor Who that I had converted down from a 700 mb .avi to a 350 mb .avi last night, and i'll see if it plays.


This is recorded using Nero 6.3.1.17, with generic 700 mb CDRs at 40x burning speed, on some generic internal IDE burner. Oddly, I had problems with 2.07, so what I did was uninstall everything, and then when I had a need to re-encode, I downloaded 1.95, and then upgraded to 2.08, and it worked fine.

Tom

[I just popped the CD in my DVD player that I had burnt a few minutes ago. It's 592x336, 25 FPS, 976 kbps Video, at 350 mb in size for a 41 m 44s episode. Works just fine; can fast forward/rewind and jump back and forth]. Hope this helps a little bit.