is very cool and works very nice
Thank you Spencer.
i am going to try to use this with the wii control if i can that to stop crashing
very nice Xenakians
pp
I would love to find a way to stream from GEM directly, but I haven't found
anything at all that allows you to stream with GEM or OpenGL directly. If
anyone knows how this would be possible, even in theory, I'd love to hear
it. It seems like there should be a way to handle this with OpenGL, but I
wouldn't even know where to start.
I've attempted to get the [pdp_theonice~] object working on Mac OSX
(streaming to an Ubuntu server running Darwin Streaming Server) but so far
have not had any luck.
On a more positive note, I have been able to stream audio to Darwin
Streaming Server with [mp3cast~], but video is what I really want.
Ben Baker-Smith
--
http://bitsynthesis.com
>have been looking for an object that can stream video out, preferably
starting from GEM and ideally running on windows or mac os.
>the only option i've found so far is pdp_ffmpeg~ - which throws an error
that the object couldn't be created when i opened the help patch on a mac,
though it doesn't say >why... (missing server? dependencies?)
>to the best of my knowledge, the pidip and pdp, despite having been rolled
into extended, don't work on windows.
>
>i'm sure i'm not the first to have this question :)
>would appreciate any pointers as to where to look next
>
>thanks
>
>rene
Hi everyone,
We have a new post in our department, which might interest some of you.
http://www.publicjobs.ie/publicjobs/en/star/goToJobDetails.do?id=419
Unfortunately, given my involvement in the selection process, I can't
answer any queries related to this post, but
my colleague Gordon Delap will be most happy to do so.
Maynooth is an interesting place to be at the moment, so I hope some
of you will find this worth a go.
All the best
Victor
Hi Pd-ers,
I've been working off and on for a bit on a C++ library to implement a
variant of Dynamic Stochastic Synthesis, a technique developed by
Iannis Xenakis. (For a great history and more details check out Sergio
Luque's thesis [1].
The library is still pretty rough around the edges and more or less
completely undocumented, but the PD object that uses it should be
pretty functional. Included with the code is a helpfile as well as a
gui that should make it pretty easy to jump right in.
The basic idea of DSS is to describe a waveform with a set of
"breakpoints" and interpolate between them to generate the actual
audio signal. The set of breakpoints forms a single cycle of a
waveform, and each time one cycle gets played, the breakpoints each
move for the next cycle. So each breakpoint traverses a
two-dimensional random walk.
One improvement I've made to some traditional DSS implementations is
the use of cubic spline interpolation instead of linear, which
improves the aliasing considerably. It's not a truly bandlimited
signal, but is differentiable. "improves" is obviously subjective, and
linear interpolation is also available by sending a "linear" message
to the object.
The other modification is the introduction of selectable center
waveforms that the breakpoints will gravitate towards. Right now I
only have flat, square, and sine implemented, but I'm planning on
including basic triangle and sawtooth as well. The "h_pull" and
"v_pull" controls effect how much the breakpoints are pulled towards
the center waveform.
The external requires Thomas Grill's Flext library. Once you have it
installed simply run
FLEXTDIR/build.sh pd gcc
>From the base gendy directory (Where FLEXTDIR is the location of your
flext install) and you should have a shiny new binary in the pd-linux
directory. The arguments to build.sh will vary depending on your
system, as will the directory containing the binaries.
Please report any bugs to http://code.airwav.es/projects/gendy/issues/new
Downloads:
Source Tarball - http://code.airwav.es/attachments/download/4/gendy-0.6.0.tar.gz
x86_64 PD Binary - http://code.airwav.es/attachments/download/3/gendy~.pd_linux
You can also get the code with
git clone http://git.airwav.es/gendy.git gendy
[1] http://www.sergioluque.com/texts/luque_stochastic.pdf
_______________________________________________
Pd-announce mailing list
Pd-announce(a)iem.at
http://lists.puredata.info/listinfo/pd-announce
Hi Frank,
I had tried assigning the devices as described in the
"MultipleUSBAudioDevices" article before but I kept losing my soundcard. Now
I tried it again and gave ALL midi interfaces a vendor id. This finally
works!
Originally I had the plan of using 2 internal midi interfaces and assign
them to index 1 and 2 and leave index 3 open for an external interface to be
plugged in from time to time. This does absolutely not work as any
"undefined" USB midi interface grabs any of the other indexes although I
have specified the maximum number one number higher so that there would be
room to get an unused index number. Very strange! I guess I'll drop the idea
about keeping an empty slot for an external interface.
The weird thing is: now that the midi ports are being sorted out in the
system pd doesn't seem to find them anymore. Even if I put the "-mididev
1,2,3" flag. I'll have to keep investigating about that.
Ingo
>Hi,
>
>On Mon, May 17, 2010 at 11:28:42AM +0200, Daniel Wilcox wrote:
>> Why udev rules then ...? I use the portaudio index of the soundcard to
>> pass to pd with -audiodev on startup (I use -nogui and alsa) and
>> another script which parses aconnect -io to determine the alsa mdii
>> index, then calls aconnect again to connect pd with the midi device.
>>
>> Actually, perhaps you are right as it would be nice to have udev run
>> aconnect whenever my midi device is plugged in.
>
>If your devices are different, you can use the vendor and product ids to
specify the soundcard index ALSA uses:
>http://alsa.opensrc.org/index.php/MultipleUSBAudioDevices
>
>If you really must use udev, maybe this helps:
>http://alsa.opensrc.org/index.php/Udev
>
>Ciao
>--
>Frank
> ---------- Forwarded message ----------
> From: "Ingo Scherzinger" <ingo(a)miamiwave.com>
> To: "'pd-list'" <pd-list(a)iem.at>
> Date: Mon, 17 May 2010 09:10:27 +0200
> Subject: [PD] udev & usb midi interfaces
>
> Hi,
>
>
>
> does anybody know the search path to get udev information about usb midi
> interfaces?
>
> It should be something like “udevadm info -a -p / ??? …”. I’m not realy
> sure how to search for the soundcard either.
>
> I was using “lshal” which gives me a lot of information but I can’t tell
> which part to use for the udev device rules.
>
> I read Daniel Drake’s “writing udev rules” but he doesn’t mention sound at
> all.
>
Yeah, it's easy ... try
udevinfo -a -p $(udevinfo -q path -n /dev/*your device*)
and plug in the device ... this command will list all the udev attributes it
sees when it makes the sysfs usb tree. I use it it see what attributes I can
use for writing udev rules. Drake may not explciity list "sound" or "midi"
devices, but they are covered by the tutorial as well ... just find where
the device is mounted in /dev and use that node in udevinfo.
> I really need to write some udev rules to straighten out my 2 usb midi
> interfaces and soundcard that get mixed up all the time.
>
Why udev rules then ...? I use the portaudio index of the soundcard to pass
to pd with -audiodev on startup (I use -nogui and alsa) and another script
which parses aconnect -io to determine the alsa mdii index, then calls
aconnect again to connect pd with the midi device.
Actually, perhaps you are right as it would be nice to have udev run
aconnect whenever my midi device is plugged in.
--
Dan Wilcox
danomatika
www.robotcowboy.com