Making the pixels larger [than the 2x necessary to overcome supersampling] won't help keeping the color detail, unless you use dithering, which I don't think happens here.
Actually, it does. It just depends how you sample it. If you sample it using point, all (2*n)x larger would all keep the color.
Bisqwit wrote:
Also keep in mind that the NES produces YUV (or some variant thereof) too, which means that it's the RGB rendering that actually loses color information, not the YUV one.
While this may be true, the emu still has all the color. Also if the colorspace is in 4:4:4 YUV, then there is no color loss.
You said it is integrated, so it doesn't have a GPU (it uses your CPU instead). However, it may still be capable of running the game at full speed.
Naw, integrated means the GPU is in the chipset instead. No way it is using CPU as a GPU.
koippis: I used Glide64 (latest here http://glide64.emuxhaven.net/index.php) to capture. Out of all the plugins I've tried, it was the fastest, but it may have a memory leak. Worth a try, I guess.
While testing the pcsx-rr version(pcsx-rr-v012+-fix1.7z), I think that I figure out what was the crash/blackscreen problem with kkapture... just play a bit with the value in "auto-skip" groupbox and then the encoding process should run fine.
Weird, I never use autoskip, since I want all frames
Yes, I am and people have been for over two years. I know the TAS community moves slow and everything, but this is ridiculous. Twice people have done the work to help the process along, but it's been ignored both times.
EDIT: Scratch that, it's been over three years
Oops, sorry I didn't notice the recent discussion on it. I do agree on the naming point though, maybe I'll bug some people.
No, there isn't.
all PlayStations (except some rare models) have their names starting with SCPH-something...
when someone dumps a BIOS it's usual to name the BIOS with that model's name.
sgrunt wrote:
The PlayStation BIOS name is derived from the console model, like the SCPH1001, SCPH7502 etc.
There's no PlayStation model (U) (v4.1). My guess is that he is using a normal BIOS with a fancy name.
Oh yea, having seeing the complete run w/o sound like 6 times over while trying to figure out the best way to capture, I'd say it looks like a fun run. Yes vote.
I also really like some of the soundtrack =)
The emulation lag in the impact stages were complete overkill, I just hope these encoders know some magic formula to eliminate it.
I'm guessing impact stages are the stages with the giant robot?
On a side note, I have successfully figure out a method to capture (although painful) and will have all effects in the final encode. I can't tell if the sound would be fix yet until I get the answer above.
Does RGB -> YV12 conversion really matter, especially with the games which would most benefit from lossless compression (ie. the ones which use a few colors to begin with, ie. NES, GB...)? Even if it does change some color by one step, I assume the change won't be visible in practice.
It matters a ton because of the small resolution. There are a ton of 1 pixel width or height things that when the color is loss, (1 color info per 2 x 2 pixel box) it really looks completely different. Maybe when I have time I can show a comparison.