FastImageOutput

[Fred]

I think it's a good approach to have a flexible fast image manipulation. It could be added natively to PB in a future version.

[nco2k]

sounds good.

ImageOutput() = ~200ms
FastImageOutput() = 0-15ms

c ya,
nco2k

[Joakim Christiansen]

Illegal memory access...
I testet it with remi_meier's "The beauty of z^2 + c" trick...
http://www.purebasic.fr/english/viewtopic.php?t=22446

[S.M.]

Illegal memory access...
I testet it with remi_meier's "The beauty of z^2 + c" trick...
http://www.purebasic.fr/english/viewtopic.php?t=22446

Thanks , I corrected the code above.
Now FastImageOutput() returns zero if a device dependent bitmap (bitmap created with #PB_Image_DisplayFormat) is used.
To get the code working, just replace:

Code: Select all

img = CreateImage(#PB_Any, #S, #S)

with:

Code: Select all

img = CreateImage(#PB_Any, #S, #S,32)

Now it should work.

@all
Thanks for the nice feedback!

[GeoTrail]

It says 0 ms on my machine. Is that possible?

[netmaestro]

It will say 0 ms if you aren't using a high-enough-res method of timing. ElapsedMilliseconds() is only good to a resolution of 15 ms or so, and if the operation you're timing finishes faster than that the ElapsedMilliseconds() value will not have changed. Hence the 0 ms. You can get 1ms accuracy easily with:

Code: Select all

timeBeginPeriod_(1)
start = timeGetTime_()
  ; timed operation
ending = timeGetTime_()

or look to QueryPerformanceFrequency_() for microsecond accuracy (you shouldn't need this much)

IIRC, when I tested this FastImageOutput() I had to drop to a lower-res method as well to avoid getting 0 ms for a result. I think I posted the method if you look a few posts back in this thread.

[GeoTrail]

That seemed to work, I'm getting 15 ms now.
But if I run it two or three times after each other then I sometimes get 0 ms and then back to 15 again.

[PB]

This code no longer works with v4.10 B3, and I don't know how to fix it.
Changing to "img = CreateImage(#PB_Any, #S, #S,32)" doesn't help as
it doesn't exist in the original code snippet.

[DoubleDutch]

Maybe it's now native? Fred?

[IceSoft]

I think it's a good approach to have a flexible fast image manipulation. It could be added natively to PB in a future version.

@Fred,
Maybe together with the 'DirectX9' Version of PB?

[Psychophanta]

Native or not, the tip should work!?
And it doesn't for 4.10 version

[Mistrel]

Is this faster than drawing on a window with WindowOutput()?

[dige]

Since PB4.40 drawing on Gadgets with StartDrawing(GadgetOutput(GadgetID.i))
does not work anymore.
May be the Structure has changed?

Code: Select all

Structure DrawingInfoStruct
  Type.l
  Window.l
  DC.l
  ReleaseProcedure.l
  PixelBuffer.l
  Pitch.l
  Width.l
  Height.l
  Depth.l
  PixelFormat.l
  StopDirectAccess.l
  StartDirectAccess.l
EndStructure

Global FastImgOutputID.DrawingInfoStruct

Procedure ReleaseGadgetOutput()
  ReleaseDC_(FastImgOutputID\Window, FastImgOutputID\DC)
EndProcedure

Procedure GadgetOutput(GadgetID) ; returns the outputID for the declared window handle
  hwnd = GadgetID(GadgetID)
  FastImgOutputID\Type=2
  FastImgOutputID\Window=hwnd
  FastImgOutputID\DC=GetDC_(hwnd)
  FastImgOutputID\ReleaseProcedure=@ReleaseGadgetOutput()
  ProcedureReturn FastImgOutputID
EndProcedure 

[Michael Vogel]

Any news about FastImageOutput for PB4.50?

[Fred]

It shouldn't have much difference since 4.40.