hello,
i've got somes problems : nothing is draw on the gemWindows in buffer 1 mode (gem debian installer and latest cvs, linux, pd 38.4)
i can't find any example patch of the "buffer 1" feature in gem, so I don't know where the problem comes from.
does anyone have an example to share?
thanks Cyrille
cyrille henry wrote:
hello,
i've got somes problems : nothing is draw on the gemWindows in buffer 1 mode (gem debian installer and latest cvs, linux, pd 38.4)
i can't find any example patch of the "buffer 1" feature in gem, so I don't know where the problem comes from.
you are sure you are banging the [gemhead]s ?
does anyone have an example to share?
04.pix/10.PixDataSimple.pd ??
i thought the "buffer 1" was broken somehow, but the example told me it works.
btw, what do you people need the "buffer 1" feature for ? i thought of removing it a la long and "replace" it with some controllable feedback in double-buffered mode. (this means: if single-buffered mode is used only to not make "traces" of objects, this could be handled otherwise.) if someone needs full control over the render-chain, removing would probably be a bad idea.
mfg.asd.r IOhannes
Personally I only ever used it for "traces" that is manual control of clearing the buffer before flip.
It would be handly to have a "clear 1|0" message to gemwin. Chris Clepper was talking about some kind of alpha clearing of the buffer that sounds nice, that is the buffer is cleared to a certain degree (fill with a solid colour but only at a settable opacity. Using this you could control how the old frames get fall-off the buffer (get occluded by multiple iterations of transparent "clearing".
Maybe "clear 0" clears the screen as normal (the default) "clear 1" clear the screen with 1% transparency "clear 100" clear with 100% transparency (no clearing).
The scale from 1-100 is very un-gem like, and its transparency, and not opacity, which is confusing. I find new users to Gem get damn confused when some messages "dimen" depend on the state of others "create" so when its not nessesary it would be handy to keep this functionality in one message.
The most gem-like way would be:
"clear 0" turns off clearing "clear 1" turns it on. "clearalpha 0" clears 100% transparent (default). "clearalpha 1" clears 100% opaque. This is not so bad when I look at it. :)
Oh and I think buffer 1 on MacOS is what does not work. Other platforms I think are fine. With the above added functionality we would not need to remove it for buffer freaks, but those who want traces would no longer use it.
B.
IOhannes m zmoelnig wrote:
cyrille henry wrote:
hello,
i've got somes problems : nothing is draw on the gemWindows in buffer 1 mode (gem debian installer and latest cvs, linux, pd 38.4)
i can't find any example patch of the "buffer 1" feature in gem, so I don't know where the problem comes from.
you are sure you are banging the [gemhead]s ?
does anyone have an example to share?
04.pix/10.PixDataSimple.pd ??
i thought the "buffer 1" was broken somehow, but the example told me it works.
btw, what do you people need the "buffer 1" feature for ? i thought of removing it a la long and "replace" it with some controllable feedback in double-buffered mode. (this means: if single-buffered mode is used only to not make "traces" of objects, this could be handled otherwise.) if someone needs full control over the render-chain, removing would probably be a bad idea.
mfg.asd.r IOhannes
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
btw, what do you people need the "buffer 1" feature for ? i thought of removing it a la long and "replace" it with some controllable feedback in double-buffered mode. (this means: if single-buffered mode is used only to not make "traces" of objects, this could be handled otherwise.) if someone needs full control over the render-chain, removing would probably be a bad idea.
i would hardly wish not to remove it - if it does not break anything otherwise. its a feature and has possibilities - even if "we" do not know at the moment what to do with it
cheers
erich
btw, what do you people need the "buffer 1" feature for ? i thought of removing it a la long and "replace" it with some controllable feedback in double-buffered >>mode. (this means: if single-buffered mode is used only to not make "traces" of objects, this could be >>handled otherwise.) if someone needs full control over the render-chain, removing would probably be a bad idea.
i would hardly wish not to remove it -
i use single bufferd mode a lot in my pixel/video processing patches. for me definitly a feature. please dont remove it !!!
cheers rainer
Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
rainer _ wrote:
btw, what do you people need the "buffer 1" feature for ? i thought of removing it a la long and "replace" it with some controllable feedback in double-buffered >>mode. (this means: if single-buffered mode is used only to not make "traces" of objects, this could be >>handled otherwise.) if someone needs full control over the render-chain, removing would probably be a bad idea.
i would hardly wish not to remove it -
hardly or hard ?
i use single bufferd mode a lot in my pixel/video processing patches. for me definitly a feature. please dont remove it !!!
again, the question is, what for did you need it exactly ? what feature of the single-buffer do you need ?
mfg.a.sdr IOhannes
again, the question is, what for did you need it exactly ? what feature of the single-buffer do you need ?
mostly for non-realtime hand knitted videoprocessing, kind of pixeldrawing. sometimes drawing traces could be very useful, at least for me. so i can draw one frame without ruffle and put say 50.000.000 rectangles per frame. additionally i can clear gemwin whenever i want.
here are some examples, if you are interested:
http://members.liwest.at/hsoe/webpreview/
cheers rainer
Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Hi,
again, the question is, what for did you need it exactly ? what feature of the single-buffer do you need ?
The pix_data examples in 04.pix are demonstrating what can be done with a little fantasy and buffer 1. These are great patches, and one would need a wagon load of geos to emulate this sort of drawing in double-buffered mode. Another approach would involve a snap2tex after each rendering cycle, followed by some alpha blending ... In any case, that would be much less efficiently than buffer 1. Additionaly, the rendering would have to be done off-screen, which isn't possible yet afaik. Single-buffered mode is more like actually drawin on the gemwin, which comes in handy from time to time ... I therefore second the requests to leave it in as a feature.
___________________________________________________________ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
IOhannes m zmoelnig a écrit :
cyrille henry wrote:
hello,
i've got somes problems : nothing is draw on the gemWindows in buffer 1 mode (gem debian installer and latest cvs, linux, pd 38.4)
i can't find any example patch of the "buffer 1" feature in gem, so I don't know where the problem comes from.
you are sure you are banging the [gemhead]s ?
i thought i tryied, but there was certainly something wrong in my patch!
does anyone have an example to share?
04.pix/10.PixDataSimple.pd ??
it's exaclty what i was looking for. (sorry, i read the help files a long time ago, i forget this one).
i thought the "buffer 1" was broken somehow, but the example told me it works.
yes, it also work here (.deb and cvs).
btw, what do you people need the "buffer 1" feature for ?
i wanted to try this to be able to display the position during time of some chaotic oscilator. each time iteration should add 1 new point. it's just to make images that can not be computable in real time. (very similar to the example) I never used buffer 1 before.
thanks cyrille
i thought of removing it a la long and "replace" it with some controllable feedback in double-buffered mode. (this means: if single-buffered mode is used only to not make "traces" of objects, this could be handled otherwise.) if someone needs full control over the render-chain, removing would probably be a bad idea.
mfg.asd.r IOhannes
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list