Various pd/gem Qs

Miller Puckette mpuckett at man104-1.UCSD.Edu
Mon Jul 10 19:19:17 CEST 2000

Hi all,

Pd currently insists on opening ALL MIDI input devices.  This is probably
not a good idea.  Unless anyone thinks this is a bad idea, I'll kludge
the next release so that the default is still to open them all but so
that "-midiindev" specifies that it open one MIDI input device only...


On Mon, Jul 10, 2000 at 11:30:19AM +0200, Thomas Loop wrote:
> Hi,
> thanks for the numerous answers to my virtual midi dev question.
> Got it running. Initially I thought midiindev would be the plug INTO pd, but now I realized that midioutdev is the input.
> Not really intuitive, I think. Setting midiindev still doesn't work, by the way, so I can't output midistuff internally with pd.
> Some new questions:
> Don't know if I understand the camera object correctly. I only get it to work if I put it into a gemlist and then it only works for that single gemlist.
> Is it possible to get it working globally, for all gemlists and subpatches? The camera should influence the perspective of the complete scene, of course...
> Also I am having trouble with a pix_multiimage in a patch. 
> The patch consists of one gemhead with 4 separators downstream that split to 4 squares.
> 2 of those squares get textured with a pix_multiimage, each. The 2 multiimage objects live on the same set of images.
> When adding the second multiimage the first one stops iterating through the images. Same metro, different counters for the 2 objects.
> It only shows the first image, while the second multiimage works just fine.
> Any ideas? Does multiimage work at all with split gemlists?
> Is there any documentation available concerning data structures and the use of pointers?
> Would it be possible to load images on events, flushing memory from previously loaded files while the patch is running?
> Lots of questions, hope they are not to trivial ... :-)
> Greetings.
>         .loop.

More information about the Pd-list mailing list