Play All Causes the PCH to Lock Up

[jtokach]

Hi,

When I hit Play All in a directory that contains several MPG's or AVI's one or two videos will play, but then it locks up into a black screen and won't respond to the remote so I need to pull the power to reboot the PCH.

Logs Attached.

Thanks!

Jim

[mvallevand]

This is possible, it's not something I ever tested outside of audio playback and especially with avi's in the mix I could see synchronization being a real problem. I will look at it, but it is not a high priority to fix.

If you need to play all files in a folder for now I suggest you try the native NMT software. Hit Play instead of OK starts play all mode.

Martin

[jtokach]

I thought it was AVI's only but it's just as bad with MPG's. We have cartoons in a few dirs and each episode is between 3-7 mins long, so it's a pain in the ass. I'll try the native software in the mean time.

Thanks for looking into it Martin.

Jim

[jtokach]

Oh, also, I think I looked at using the native and it didn't have a shuffle feature. I'll look again.

[mvallevand]

I think based on what I saw in the logs it relates somehow to the 1.4.7 bug of not playing more than two shows in a row. As soon as sub gets around to it, http://forums.nextpvr.com/showthread.php?t=43657 I'd like to see if this will fix both problems.

You should change your screen OSD values, I don't they are good since you don't account for overscan on the right side.

Martin

[jtokach]

Yes, it has never played more than two in a row using ver 1.4.7 so my money is on that.

The skin is off on the right side, but fussing with the values hasn't helped. (It looks fine when videos play.) I think I recall you saying that most people don't use the MVP Position plugin the right way. Are the instructions somewhere or guidelines/formulae?

[mvallevand]

Sorry, I've had to guess on how those config.xml values are used too when I code.

The real solution is for skin developers to not try and cram every pixel out of the monitor and concentrate on not positioning fields to close the overscan area so everyone would work with no offsets. Blue probably needs to be reviewed too. There was a discussion on this here http://forums.nextpvr.com/showthread.php?t=40344

You also might want to set the NMT skin rather than accepting the default skin.

Martin

[Jaggy]

I think I recall you saying that most people don't use the MVP Position plugin the right way. Are the instructions somewhere or guidelines/formulae?

Talking as the "person who volunteered to update the NMT section of the wiki".....I have been trying to find this out as well so I could write instructions/guidelines with formulas for users to follow, so far without much luck. Don't worry I haven't forgotten & I will comeback to this in the future when I have caught up a bit with what I have to get done.

Sorry, I've had to guess on how those config.xml values are used too when I code.

So I guess that is why I wasn't able to get a firm reply to my earlier question about this......hmmm maybe we will have to make an educated guess at it??

The real solution is for skin developers to not try and cram every pixel out of the monitor and concentrate on not positioning fields to close the overscan area so everyone would work with no offsets. Blue probably needs to be reviewed too. There was a discussion on this here http://forums.nextpvr.com/showthread.php?t=40344 Martin

Talking as "a user" this wouldn't have helped me as my TV was MILES out, probably had the positioning setup wrong at the factory & without opening it up & adjusting them there was NO WAY the menus were going to fit even closely.

Talking as a "skin developer of high visibility skins" I really require all the real estate I can get to get thing to fit at BIG sizes & as it is possible to set the overscan........