Now Im Pissed...


Crazy Goat posted on Apr 16 2006 at 03:58 AM said:
The MagicEyes co-proc has a max resolution of 1024x768 - I am quite sure it is capable of rendering content at NTSC and PAL standards.
If TV-Out is detected, mplayer will scale the video stream to TV-Out resolution using the CX chip and ignoring the scaler altogether.
 
Last edited by a moderator:
AireTamStorm posted on Apr 19 2006 at 03:14 AM said:
You're probably right. They said 720x480 in the specs, but thats a weird res, I don't believe that too much. Most NTSC TVs display at one of these 3 resolutions: 640x480; 800x600; 1024x768.

It's not very weird. It's the NTSC DVD standard resolution and was probably picked for more ideal playback of ripped DVDs at their native resolution. I believe you're a bit off on those TV resolutions; while standard-definition NTSC TVs display a picture with 480 lines of resolution (and sometimes 240), I've never seen or heard of an NTSC implementation using over 525 vertical lines. Newer HDTV standards support 720 and 1080 lines of vertical resolution. What you listed, however, are standard PC resolutions.

I agree though, that I look forward to using the '2x as a simple computer one of these days, connected to a TV, USB keyboard, mouse, network adapter and sizable storage medium. It'd be very useful for on-the-fly development rather than crosscompilation and copying prebuilt binaries over to the machine all the time for testing.
 
Last edited by a moderator:
Holy cow I just bought the ACCUPOWER 2900 maH batteries and there a huge difference from the crappy MAHA 2500's I bought. So in the end my MAHA's just suck and probabaly nowhere close to the sanyo 2700's either.
 
thelamer posted on Apr 13 2006 at 10:36 PM said:
i only get about 2 hours of video max with mine with full charged 2500 mah . And about 1:45 of playing drmdx while overclocked .

I thought that was normal .

Why would you overclock DrMDX? It works perfectly at 200mHz ;)
 
Last edited by a moderator:
Epicenter posted on Apr 19 2006 at 08:11 PM said:
AireTamStorm posted on Apr 19 2006 at 03:14 AM said:
You're probably right. They said 720x480 in the specs, but thats a weird res, I don't believe that too much. Most NTSC TVs display at one of these 3 resolutions: 640x480; 800x600; 1024x768.

It's not very weird. It's the NTSC DVD standard resolution and was probably picked for more ideal playback of ripped DVDs at their native resolution. I believe you're a bit off on those TV resolutions; while standard-definition NTSC TVs display a picture with 480 lines of resolution (and sometimes 240), I've never seen or heard of an NTSC implementation using over 525 vertical lines. Newer HDTV standards support 720 and 1080 lines of vertical resolution. What you listed, however, are standard PC resolutions.

ntsc is and has always been 525 lines. however, not all of the lines carry the picture signal.

edit: whoops. i guess we're in agreement. i read a little too fast, sorry about that epicenter. yes, i think that what AireTamStorm is talking about is connecting the s-video out from a computer graphics card to an ntsc television set. in this case the pixels are not preserved as such so it makes no sense to talk about resolution. the signal is analog and in a sense it is like taking a picture of the video card output. you can tell what the screen says on the photograph, but you have no reason to assume that the piece of paper you're holding has the same resolution as your computer monitor.
 
Last edited by a moderator:
NoidZ posted on Apr 21 2006 at 11:40 AM said:
thelamer posted on Apr 13 2006 at 10:36 PM said:
i only get about 2 hours of video max with mine with full charged 2500 mah . And about 1:45 of playing drmdx while overclocked .

I thought that was normal .

Why would you overclock DrMDX? It works perfectly at 200mHz ;)

Maybe if you skip frames. If I set DrMDx to run with 0 frameskip and 22050hz audio samplerate, it will be irritatingly slow; 40-50 FPS. If I overclock to 250-266 MHz it will maintain 60 FPS at all times. And I don't know about you, but I can't stand frameskip. I like the authentic experience. If you use Frameskip 1 anything that blinks (LOTS of sprites do this on the MD and other consoles) they will vanish until they stop blinking as the frames where they are VISIBLE are dropped, so you need to go to Frameskip 2, which is choppier, so on and so forth. This is why I always overclock when I run it.
 
Last edited by a moderator:
Back
Top