Re: [PD] [GEM] pix_write option for rendering a texture only
Quoting chris clepper [EMAIL PROTECTED]: pix_write should just write the pix buffer to a file and not also have pix_snap functionality embedded in it. Unfortunately doing this would break a lot of patches. Maybe pix_image_write would be an acceptable option. i totally agree. i think the best way to go would be to just wrap [pix_write] into an abstraction with [pix_snap] and [pix_image_write] (or whatever name) in the meantime i noticed that nobody yet has suggested using [pix_buffer] afaik you can save contents of the [pix_buffer] to file...(but thinking about it, it might has as well been on my todo list...) fgasmrd IOhannes This message was sent using IMP, the Internet Messaging Program. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] netreceive text messages
hi PDers, thanks for previous help - i have now got basic messages going over tcp, but am having trouble passing text messages to PD. the problem is spaces (and the first word getting dropped). can anyone tell me what is wrong with this patch? i'm sending messages from the shell using pdsend (but will eventually have it coming from a batch file) -- Joseph Barrows live video performance; web site design; new media artist jjbarrows.artwww.net [EMAIL PROTECTED] receive text.pd Description: Binary data ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] gem2pdp
hola, some more informations about troubles i get with gem-cvs and pd 0.41 on an Nvidia 7000 : in fact, it seems that all rendering in single-buffer mode doesn't work ( see attached patch for testing ) and, as the pixels capture only works in single-buffer mode, all objects depending on it fail, including gem2pdp, pix_write and pix_snap. maybe it's only on this hardy installation with : GEM: Graphics Environment for Multimedia GEM: ver: 0.91-cvs GEM: compiled: May 22 2008 GEM: maintained by IOhannes m zmoelnig GEM: Authors :Mark Danks (original version) GEM:Chris Clepper GEM:James Tittle GEM:IOhannes m zmoelnig GEM: with help by Guenter Geiger, Daniel Heckenberg, Cyrille Henry, et al. GEM: found a bug? miss a feature? please report it: GEM: homepage http://gem.iem.at/ GEM: bug-tracker http://sourceforge.net/projects/pd-gem/ GEM: mailing-list http://lists.puredata.info/listinfo/gem-dev/ GEM: compiled for SIMD architecture: MMX GEM: using MMX optimization maybe, i compiled it wrong, it didn't complain about anything.. saludos, sevy #N canvas 5 49 822 360 10; #X obj 33 16 gemwin; #X obj 521 -167 gemhead; #X floatatom 629 -95 0 0 0 0 - - -; #X obj 521 -107 color; #X msg 623 -162 1 1 1; #X obj 521 -56 rotateXYZ; #X obj 392 -141 world_light; #N canvas 203 0 600 400 init 0; #X obj 73 30 loadbang; #X obj 73 53 t b b; #X msg 113 77 reset; #X msg 73 103 lighting 1; #X obj 73 129 outlet; #X connect 0 0 1 0; #X connect 1 0 3 0; #X connect 1 1 2 0; #X connect 2 0 4 0; #X connect 3 0 4 0; #X restore 79 -76 pd init; #X msg 623 -197 1 1 0; #X obj 669 -56 metro 10; #X obj 708 -28 + 1; #X obj 668 -29 f; #X msg 681 -94 bang; #X obj 681 -123 loadbang; #X msg 79 -114 dimen 320 240; #X obj 79 -140 loadbang; #X msg 200 -111 buffer 1; #X msg 97 4 buffer 2; #X obj 519 28 cube; #X msg 65 -201 create \, 1; #X msg 71 -174 0 \, destroy; #X obj 520 -13 pix_write; #X msg 387 -78 file /tmp/gem.jpg; #X msg 385 -36 bang; #X msg 197 -171 1; #X text 264 -109 -- click here and rendering dies; #X text 108 -36 click here and it will save a black image --; #X text 146 -200 -- normal rendering; #X connect 1 0 3 0; #X connect 1 0 6 0; #X connect 2 0 5 1; #X connect 2 0 5 2; #X connect 3 0 5 0; #X connect 4 0 3 1; #X connect 5 0 21 0; #X connect 7 0 0 0; #X connect 8 0 3 1; #X connect 9 0 11 0; #X connect 10 0 11 1; #X connect 11 0 10 0; #X connect 11 0 2 0; #X connect 12 0 9 0; #X connect 13 0 12 0; #X connect 14 0 0 0; #X connect 15 0 14 0; #X connect 16 0 0 0; #X connect 17 0 0 0; #X connect 19 0 0 0; #X connect 20 0 0 0; #X connect 21 0 18 0; #X connect 22 0 21 0; #X connect 23 0 21 0; #X connect 24 0 0 0; ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] gem2pdp
On Sun, 2008-05-25 at 14:11 +0200, yves degoyon wrote: in fact, it seems that all rendering in single-buffer mode doesn't work ( see attached patch for testing ) and, as the pixels capture only works in single-buffer mode, all objects depending on it fail, including gem2pdp, pix_write and pix_snap. if i am not totally mistaken (or misunderstanding the underlying concept of Gem), i used to use [pix_snap] or [pix_write] in double buffer mode. it's just a matter of correct order to get expected results. what makes you think, that those classes only work in single buffer mode? roman ___ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [PD-announce] GridFlow 0.9.1
Hi all, Some ruby still exists for code generation but you don't need the ruby headers anymore. Live camera input doesn't work yet but you can play videos. Playing videos is about 2x faster on OSX than linux but the rest is noticeably slower. The [#out] on quartz does not support all the features of X11 (mouse input, hidecursor). Many of these issues should be solved by next week but any help is welcome, especially for quartz. Cheers, Alexandre On Saturday 24 May 2008 15:18:58 marius schebella wrote: Steffen Juul wrote: On 23/05/2008, at 15.51, marius schebella wrote: just wanted to say that it needed some time, but finally this also runs on mac (at least on intel with os x 10.5). thanks to mathieu! How did you go by installing? I'm confused since the install guide in the manual [0] mentions ruby but the changelog for 0.9.1 says ruby have been removed (so it can't be called rubyext anymore right?). [0] http://gridflow.ca/svn/trunk/doc/install.html it's a long story, and is far away from being automatic.. but yes, all ruby was removed. grab the latest sources and then do ./configure --no-mpeg3. after that add the path to your pd sources to the CFLAGS in config.make. mine is -I/Users/marius/devel/pd-rsync/pd-extended/pd/src and set -mtune=k8 -march=k8 if you have an intel mac. then it should compile and run. have not tested all objects, some seem not to work (like live input?), but most of them will. marius. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] UI developer volunteering to help
Everything is working quite well. My only issue with it is what I
mentioned before, the popup text entry box for editing. But it is
definitely usable as it is now.
Thanks for taking this on!
.hc
On May 25, 2008, at 2:22 AM, David Golightly wrote:
Since it's been a few days since my last update, and I haven't
received any responses, I submitted patch #1971585 to SourceForge,
including the updates to the Path and Startup dialogs. Any further
suggestions are still welcome; I will be investigating
consolidation of the 4 preferences dialogs into a tabbed dialog of
some sort (a la Tk notebook). However, perhaps an earlier priority
for me will be figuring out some improvements to GUI control
dialogs; perhaps bulk-editing/updates modeled (I think) on the
iTunes UI for editing the metadata on multiple songs.
Anyways, thank you to everyone who offered feedback and code
reviews to my efforts! Much appreciated. I'm grateful to be able
to contribute code to a piece of software that has been so useful
to me in the past.
Best,
David
On Wed, May 21, 2008 at 8:50 PM, David Golightly
[EMAIL PROTECTED] wrote:
Ok, how does this look?
I was still unable to reproduce the clicking bug, but I changed the
code to avoid the scenario that your stack trace seems to indicate
as the problem, hopefully you won't see it any more.
Turns out I also have Tcl/Tk 8.4.7. Don't know where I got the
idea I had 8.5 installed. So it seems either the tcllib or the
Tile/ttk widgets might be a good bet for the next revision to these
dialogs. One goal here also I think is to eventually provide a
good basis for further customization of the Pd environment and UI,
which will of course require someone to delve in the C for some of
it, although perhaps to the extent that some customization can be
done in pure Tcl/Tk, C work can be avoided.
Thanks again,
David
On Tue, May 20, 2008 at 3:00 AM, Hans-Christoph Steiner
[EMAIL PROTECTED] wrote:
Just tried your new version, very nice, I think it's sorted, except
one tiny bug with the resizing of Add new startup command. I
think you'll want to set a minimum window width, since you can
resize it smaller and make the OK button disappear.
You might look into the Tile/ttk widgets, they are now included in
Tcl/Tk 8.5. I'd like to use 8.5 for Pd-extended 0.41, so they
would be there. For example, a ttk::notebook could be used to host
all of the pref panes into a single window.
About the error, I just dropped your u_main.tk into Pd-vanilla
0.41-4, so that uses the version of Tcl/Tk included with Mac OS X,
8.4.7. I have Tcl/Tk 8.4.18 installed, it might be using that.
But I definitely don't have 8.5 Here's the error:
Startup panel:
can't use empty string as operand of +
can't use empty string as operand of +
while executing
expr {$height + $top}
(procedure ScrollBox::dbl_click line 8)
invoked from within
ScrollBox::dbl_click .gfxstub5b1230 dlg_Startup::edit
dlg_Startup::add 65 45
(command bound to event)
Path pane:
can't use empty string as operand of +
can't use empty string as operand of +
while executing
expr {$height + $top}
(procedure ScrollBox::dbl_click line 8)
invoked from within
ScrollBox::dbl_click .gfxstub5b1930 dlg_Path::edit dlg_Path::add
81 42
(command bound to event)
.hc
On May 20, 2008, at 8:32 AM, David Golightly wrote:
PS I was unable to reproduce that issue where you saw an error
message from clicking on an empty cell. For me, clicking on empty
cells just brought up the Add new item dialog. Could this be a
difference of platform/TclTk version? I'm running 8.5 on OS X
10.4. I'd also like to get the specific error message if you can
get it.
Thanks,
David
On Mon, May 19, 2008 at 10:07 PM, David Golightly
[EMAIL PROTECTED] wrote:
Here's a revised copy with a few minor changes (the startup
flags field now expands to fill the window, you can resize the
startup command popup arbitrarily).
I'm wondering about the protocol of introducing dependencies in
PD. It seems that BWidget gives us a widget that we can use for
the listbox (http://tcllib.sourceforge.net/BWman/ListBox.html),
however, it's perhaps not distributed with older distributions of
Tcl/Tk. BWidget is distributed with Tcllib, which is apparently a
default library packaged with most installs of Tcl, http://
wiki.tcl.tk/12099 says that it comes by default with the
ActiveState distro, with .deb and .rpm packages, and it was
installed by default on my Mac OS X 10.4 distribution. But it's
not guaranteed to be installed with ALL distributions of Tcl/Tk -
I just have no idea exactly how many users might lack it.
Failing that, the popup should behave exactly as inline editing
does, even though it looks a little strange. You can still use
the keyboard to navigate: down, down, enter, type, enter, up,
enter, esc... Just think of it as inline listbox
Re: [PD] netreceive text messages
Maybe this can help.++Jack test.pd Description: Binary data Le 25 mai 08 à 13:27, Joseph Barrows a écrit :hi PDers,thanks for previous help - i have now got basic messages going over tcp, but am having trouble passing text messages to PD. the problem is spaces (and the first word getting dropped).can anyone tell me what is wrong with this patch? i'm sending messages from the shell using pdsend (but will eventually have it coming from a batch file)-- Joseph Barrowslive video performance; web site design; new media artist jjbarrows.artwww.net [EMAIL PROTECTED]receive text.pd>___PD-list@iem.at mailing listUNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] netreceive text messages
Hallo, Jack hat gesagt: // Jack wrote: Maybe this can help. ++ It's probably better to use: [netreceive ...] | [list prepend text] | [list trim] | [textextruded ...] as you don't need to concat the list to a single symbol, [textextruded] can handle a list of symbols as well, also you don't need any more externals then. Le 25 mai 08 à 13:27, Joseph Barrows a écrit : hi PDers, thanks for previous help - i have now got basic messages going over tcp, but am having trouble passing text messages to PD. the problem is spaces (and the first word getting dropped). What problem are spaces? Regarding the first word being dropped: YOu may want to read up a bit on how messages are handled in Pd, e.g. here: http://puredata.info/dev/PdMessages Basically it's like this: Messages in Pd have two parts: A selector, which is the first word from above, and the actual message data. The selector is float for number messages, symbol for symbol messages, list for list-messages and other words for other or meta-message. As a special rule, a message without data is converted to a bang message, and messages, whose data part start with a number, can omit the float or list selector. [netceceive] will spit out whatever message type you send to it. So if you send text pi pa po, it will output a text meta message, if you send list a b c, it's a list-message, if you send hello world, it's a meta message with selector hello i.e. a hello-message. Now the tricky part that was wrong in your patch: dollar variables in message boxes like [hello $1( take the replacement values from the *data part* of incoming messages. The dollar variables ignore any selectors. See attached patch for an example. Note that some selectors actually make a message box do special things, like the set or addsemi meta-messages. Ciao -- Frank Barknecht _ __footils.org__ majortom.pd Description: application/puredata ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] Getting Sysex output to work on Linux
Hi, I am hoping someone can give me advise on getting my Ubuntu box to send sysex message over MIDI. Some questions.. 1) What is the proper format for messages to go into [midiout] or [sysexout]? Do I make a list of numbers such as [247 NN .. .. .. NN 240 or do I need to serialize them as [sysexin] receives each byte as individual messages? 2) Previous posts on the same topic were a bit too vague for me to catch up with. Although I use Debian Ubuntu daily, unfortunately I am not fluent in developing practices enough to design my own workarounds (at least not yet). The closest I could get was the understanding that there is no method to get Sysex output to work other than patching Pd so a different kind of function in ALSA-API will be used. (also that the current releases have a 20 byte limit. This is probably not my case though) If current pd-extended (which I am comfortable with, either stable or testing) needs patching in order for midiout to work, I would highly appreciate specific procedures on how to get it going, hopefully on a fresh installation of Ubuntu 8.04 or 7.10. Any type of help appreciated. Thanks. -- David Shimamoto ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Getting Sysex output to work on Linux
Is it out of the question simply to use the OSS MIDI API? That should be the default, and it's much less buggy than the ALSA one. (Apparently, though, there's sometimes a good reason to use teh ALSA one instead, I remember vaguely.) To put out sysex MIDI, theoretically in either ALSA or OSS, send the bytes out serially, as in 247, NN, NN, 240, not in a list as in 247 NN NN 240. cheers Miller On Mon, May 26, 2008 at 02:20:19AM +0900, PSPunch wrote: Hi, I am hoping someone can give me advise on getting my Ubuntu box to send sysex message over MIDI. Some questions.. 1) What is the proper format for messages to go into [midiout] or [sysexout]? Do I make a list of numbers such as [247 NN .. .. .. NN 240 or do I need to serialize them as [sysexin] receives each byte as individual messages? 2) Previous posts on the same topic were a bit too vague for me to catch up with. Although I use Debian Ubuntu daily, unfortunately I am not fluent in developing practices enough to design my own workarounds (at least not yet). The closest I could get was the understanding that there is no method to get Sysex output to work other than patching Pd so a different kind of function in ALSA-API will be used. (also that the current releases have a 20 byte limit. This is probably not my case though) If current pd-extended (which I am comfortable with, either stable or testing) needs patching in order for midiout to work, I would highly appreciate specific procedures on how to get it going, hopefully on a fresh installation of Ubuntu 8.04 or 7.10. Any type of help appreciated. Thanks. -- David Shimamoto ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Pd-extended PPC autobuild Jack OSX
Yeah, there are some jack issues under investigation, so please test things once there is something new to test. :) .hc On May 22, 2008, at 11:23 AM, Si Mills wrote: I noticed the other day that when selecting to run in Jack mode (with Jack booted) the system becomes unusably sluggish. This happens in the PPC version of 0.40.3 -extended that I downloaded the other day from Autobuild and Jack osx 0.77. I haven't tried one of the latest builds. I'm adding this to the bug tracker thanks ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/ listinfo/pd-list Looking at things from a more basic level, you can come up with a more direct solution... It may sound small in theory, but it in practice, it can change entire economies. - Amy Smith ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Problems with [pdp_mixer] ??
There is no patch attached.But i think that you want to talk about [pdp_mix].Here a patch for your problem (with [pdp-glx]).++Jack mix_pdp.pd Description: Binary data Le 25 mai 08 à 19:30, Javier Garcia a écrit :Hi!if i pause one channel of the two that [pdp_mixer] supports, the other channel pauses also on the pdp render windows after [pdp_mixer] !!! Any idea?See the patch I have attached with 3 pdp render windows.Ciaowww.myspace.com/vjgarffTodo ruedas: información práctica y todo el glamour del mundo del motor. MSN Estilo y Tendencias___PD-list@iem.at mailing listUNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Problems with [pdp_mixer] ??
Sorry, i forgot an abstraction.Here a better patch used with MacOSX.4.11 on PowerBook G4 with [pdp_glx].++Jack mix_pdp.pd Description: Binary data Le 25 mai 08 à 22:34, Jack a écrit : There is no patch attached.But i think that you want to talk about [pdp_mix].Here a patch for your problem (with [pdp-glx]).++Jackmix_pdp.pd>Le 25 mai 08 à 19:30, Javier Garcia a écrit :Hi!if i pause one channel of the two that [pdp_mixer] supports, the other channel pauses also on the pdp render windows after [pdp_mixer] !!! Any idea?See the patch I have attached with 3 pdp render windows.Ciaowww.myspace.com/vjgarffTodo ruedas: información práctica y todo el glamour del mundo del motor. MSN Estilo y Tendencias___PD-list@iem.at mailing listUNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list ___PD-list@iem.at mailing listUNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Getting Sysex output to work on Linux
On Sun, May 25, 2008 at 11:12:24AM -0700, Miller Puckette wrote: Is it out of the question simply to use the OSS MIDI API? That should be the default, and it's much less buggy than the ALSA one. (Apparently, though, there's sometimes a good reason to use teh ALSA one instead, I remember vaguely.) I think that the good reason to use ALSA is that OSS is even more deprecated than [namecanvas], in that everyone is switching away from it as fast as possible. Best, Chris. --- http://mccormick.cx ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Getting Sysex output to work on Linux
On Sun, May 25, 2008 at 11:12:24AM -0700, Miller Puckette wrote: Is it out of the question simply to use the OSS MIDI API? That should be the default, and it's much less buggy than the ALSA one. (Apparently, though, there's sometimes a good reason to use teh ALSA one instead, I remember vaguely.) To put out sysex MIDI, theoretically in either ALSA or OSS, send the bytes out serially, as in 247, NN, NN, 240, not in a list as in 247 NN NN 240. OSS has, IIRC, been deprecated for many years now. ALSA should be the correct one to use on Linux. And, also, for the past year or so there's been a new JACK MIDI API which is a lot cleaner (and strongly-timed) than ALSA, although it of course uses ALSA for transmission to actual MIDI devices. -ken ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
