From the original SynthMaker forum (2004–2014), with its members’ names and dates.
angstrom ·
Hi all,
I made what I thought would be the simple begining for something, but I only seem to be making microscopic bitmaps ... I can't figure out the problem after nearly 2 hours of changing things. 😕
it's a very simple bitmap OSM
Download the OSM, which explains itself really!
I'm making a bitmap from using 'Bitmap Create' taking its source from the V output from a standard SM item (parametric EQ)
when I take the output bitmap data and use a 'Bitmap Size' on it I see decent values (200px by 80px), but the problem comes when I take those sizes into the BmpR for display
I run my height and width through an 'F to A' and into the BmpR, but the bitmap that is displayed is tiny. possibly 20px by 8px
The odd thing here is that although the pixel values displayed are correct - they don't seem to be reflected in the actual bitmap data.
EG : even entering huuge values into the original "bitmap create" such as '1400 by 800' , only delivers the same tiny bitmap, yet the reported pixel values are correct when checked with a bmp size.
this has baffled me very succesfully!
😕 😕 😕
oddson ·
Set grid step to 8 and divide the pixels by 8 (mult by 0.125) before feeding to the F2Area.
OSM
See this thread Bitmap Area primitive src input is in pix instead of grids
angstrom ·
no that's not it. I read that thread when I first encountered the issue, but I am familiar with the pixel requirements.
you are talking about display right?
zoom is at 8 - and using a multiplier of any size to display, you see that the stored data appears wrong. Proof?
BmpR should display the image without scaling if no A is attached. You can see this by detaching it in the supplied schematic, detach and it displys quite obviously without scaling (no aliasing) . yet it is tiny.
Also note that I said that the bitmap to size outputs the correct pixel sizes
it seems stored tiny
if it was a display issue I could have simply scaled up the display manually until I found a rough multiplier, which is the first thing I tried, but that is not the problem. scaling up dimensions into bitmap display area simply exposes lack of stored data
oddson ·
The 'Grid Step' on the Bitmap Create tells SM how many pixels to store per grid square.
If you pass it 1 you will get a bit map with 1 pixel per grid square.
It will still store the same size bitmap but most of it will be empty.
Then when you display most of the bitmap doesn't fit in the huge area you're giving it (which is in grid square and not pixels)
It doesn't really make a lot of sense to me but that's the deal.
angstrom ·
ah, sorry I missed the osm link,
you got a blue forum table , combining with your dark blue link. I missed it completely 😊
anyway - yes, thats the key bit of info ... the 'grid step' input on the store.
I thought you were refering to the 'grid step' of the view as refered to in the main schematic zoom or the view properties.
I understand now. I thought it related to a previous incarnation of the bitmap array (as in array index step)
thanks
oddson ·
I could have been clearer.
Also using 8 and 1/8 isn't exactly right. I've amended the OSM above to use the Pixel to Grid and Grid to Pixel primitives instead.
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker