palmdoogie
Junior Member
Re-living the 80s
Posts: 66 
|
Post by palmdoogie on Aug 19, 2009 20:01:55 GMT 1
Hopefully someone can help with this one. I want to incorporate the fast 1.25x scaler renderer to work with the palmMAME module I have incorporated into LJP lite, but I'm having trouble choosing parameters that do not scramble up the video pattern. I believe I am passing the first two parameters correctly for the pointer to the source and destination buffers, but the size parameters are giving me trouble. Since these are assembly routines, there is no function prototype to guide me as to exactly what should be passed for these args. Lets assume I'm trying to scale a 256W by 224H MAME screen(like zaxxxon) to 320W, what values would I use? Also, since I've changed so much of the code and UI as well as incorporating a lite version of PMAME, would there be any objection to my changing the name of my LJP-Lite project to some other name of my choosing? I would of course give credit to both LJP and PMAME in my about screen, since I started from those sources  |
|
|
|
Post by coder12 on Aug 21, 2009 16:21:27 GMT 1
Hmm, maybe stretching each pixel to 1.25 times its size would be the correct parameter. Due to the fact that 320/256=1.25.
I dunno if it's right (I couldn't understand your message perfectly, but that's prolly just me) but I figured I'd give it a shot.
|
|
|
|
Post by _Em on Sept 1, 2009 4:55:10 GMT 1
How is it done in the other modules? Do they just hard-code it based on the fixed dimensions of the target architecture?
You might need to create a routine from scratch that checks the target architecture against values in a data block and assign the ones that matches.
Not sure if this at all answered your question, but it's as close as I can get without looking at the code.
|
|
palmdoogie
Junior Member
Re-living the 80s
Posts: 66
|
Post by palmdoogie on Sept 2, 2009 6:14:25 GMT 1
Well, some of the arguments passed are constants, but some are variable. That's what makes it hard to figure out. I know that the end result is a 1.25x scale. I'm just not sure how to get it to work with the PMAME display buffer. Some values look like scrambled video, my best guesses look like split screen with overlap. Because these are ARM assembly routines, the parameters passed are not self-documenting(don't have variable names that make sense like dest_height, src_height, etc...). For scaled screens that are also smoothed, both pMame and LJP use Scale2xSAI, but this is slower than the assembly renderer, so it would be nice to have that option for pMame as well...
|
|
|
|
Post by luckyluke on Sept 3, 2009 1:15:05 GMT 1
I can't promise anything but I can a little bit ARM assembler. I needed to learn it for MoreHeapHack and some other stuff. How long is this assembly function? Where can I find the sources of it?
|
|
