GP Cinema from entware


This has been covered on gp32emu already, see the forums there.

I'm sure i posted about this here too, about 3 weeks ago. Its been on the cards since moviepark went off, it runs at 15fps at full screen but can go upto 24fps i believe with certain settings. It is also backwardly compatable with movie park.

-Craig

www.gbax.com
 
As films generally keep ur gp on 4 a while 4 the duration of watching them then i suppose that overclocking would b for extended periods then. i think ill stick with lower frame rates then :unsure:
 
NiN^_^NiN posted on Jul 23 2003 said:
it says 15fps for 320 x 240 display at 133mhz.

Why is this dangerous? i thought the gp32 went up to 133mhz i know 132 is what some emulators run at. Whats the risk of running it on 133mhz?

:ph34r:
I set mine to 133 mhz and so far nothing bad has happend. The video file runs perfectly at 15fps.
 
Last edited by a moderator:
I've just bought mine. Something to bear in mind- If you normally encode at 128kb at 10fps, you should really encode at 192kb to maintain the same quality at 15fps. Otherwise you'll be spreading the same amount of data over more frames, dropping the quality. This will probably push some films over 128MB. Guess i'll have to invest in another 128 to cater for LOTR :)
 
Just bought my gp cinema copy, but i'm currently not too happy about it. My GP crashes on movies i encoded with xvid, while Moviepark plays them without any problems. Movies like honey_gp.avi do work with gp cinema.

I'll be testing some more stuff this afternoon, so i'll keep u guys informed on my findings.
 
I bought this as it was only £3 since i already had moviepark and it works just as well as moviepark, the interface is similar but the shortcuts are more logical i find.

Just to clear up this overclocking, 166mhz mode is only required to achieve 24fps, you can encode your films normally as with moviepark and run them at 133mhz. There are also many intermediate settings from 100 upto 166mhz.
 
After some testing it appears gp cinema only supports xvid encoded with the old 04102002-1 koepi build. Moviepark doesn't have this problem at all. It works with all builds including the latest 24062003-1 koepi build.

Has anyone else tried newer builds and/or which one works best for you?
 
khephren posted on Jul 24 2003 said:
I've just bought mine. Something to bear in mind- If you normally encode at 128kb at 10fps, you should really encode at 192kb to maintain the same quality at 15fps. Otherwise you'll be spreading the same amount of data over more frames, dropping the quality. This will probably push some films over 128MB. Guess i'll have to invest in another 128 to cater for LOTR :)
I always encode at 256kb.
 
Last edited by a moderator:
Which version of Virtual Dub do most people use? Im using 1.5.1 is that ok?
 
Back
Top