Pd-list July 2005

pd-list@lists.iem.at

116 participants
170 discussions

problems with TOXY and GRIPD
by rez 27 Jul '05

27 Jul '05

ei lista I'm trying to add a image background to my patch using toxy or gripd to do it. Well, the problems are: WITH TOXY. I put an object like this [widget img il] and PD says to me: #beware! this is widget 0.1, 15th alpha build... #warning (Widget): no file 'setup.wid'... using built-in defaults and the object dissapears from my patch or hangs the patch until I delete it. I look 4 setup.wid and I can't find nothing. WITH GRIPD I put an object [gripd] and PD says to me: #GrIPD: Using port 32820 #GrIPD: Waiting for a connection... and nothing happens... What's my stupid error?? Gracias a lot.

1 0

Re: [PD] pd cheatsheet
by Georg Holzmann 26 Jul '05

26 Jul '05

Hallo! > I just sometimes would like the open source community to remember that > if something is going to "catch on" with the general public, it needs to > have certain basic "out of the box" functionality. A little more work > on GUI and provision of a library of oscillators, samplers, and > grain-synthesis externals, WITH FULL DOCUMENTATION, would go a huge way > towards making PD competitive with the commercial software packages. you could have a look at the rradical patches from frank ... I don't know if they contain a good documentation, but I think they are what you want ... LG Georg -- 5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail +++ GMX - die erste Adresse f�r Mail, Message, More +++

1 0

Re: [PD] pd cheatsheet
by David Powers 26 Jul '05

26 Jul '05

Hi, Thanks for your help. I will try some of the suggestions you gave. The bottom line is, maybe the build I'm using is too old, but I just don't want to lose access to all the externals and I had great problems installing them individually before - until I realized the MIDI IN wouldn't work, this distribution was working the best for me. Maybe I just don't like starting from the command line... I will say, despite my current frustration, I do think that PD, for now, is great as a learning tool. I never understood Reaktor in the past, but knowing some PD has allowed me to program incredibly fast in Reaktor! I will keep going with PD as it does certain things that Reaktor does not, and if I understood OSC, I might even be able to get the two programs to play together... I want to program Python modules for Reaktor as well (okay, I lied, I know a little programming, but not enough to understand what people are talking about on the list most of the time). I just sometimes would like the open source community to remember that if something is going to "catch on" with the general public, it needs to have certain basic "out of the box" functionality. A little more work on GUI and provision of a library of oscillators, samplers, and grain-synthesis externals, WITH FULL DOCUMENTATION, would go a huge way towards making PD competitive with the commercial software packages. And, of course, a complete Windoze binary distribution which includes the important external libraries, and works (okay I know some of you hate it but it works)! However I will still find uses for PD in the meantime, it is much better for testing a concept with dataflow or data manupulation than Reaktor, even if Reaktor has more tools right now to create a finished "performance". ~David jmmmp wrote: > I'm sorry that I can't help now - I use the other distribution, and as > I still have a slow connection (and now not so much free time), I > can't download the other installation and try it myself. Maybe it > would help to see where you got this version and ask the e-mail > contact that might be there directly (that doesn't seem to be the > original Puckette build), or check Help->about pd and say to the list > exactly which version you have (until now I thought we were speaking > about the same thing). > can you open the .exe from the command window with the flags you need? > (I don't know this distribution, but that would make sense) > > if you had the time, you could try to install the "official" version > (which you can get in http://crca.ucsd.edu/~msp/software.html), and > then the externals individually. it isn't that hard, and when you do > it once you do it thousands of times - but if you have already too > much on your mind, then leave it for later. > > >> 1. Midi In doesn't work. And the Midi Setup will NOT let me fix >> it! It "sees" the devices but it refuses to enable them. It says >> PD needs a flag on startup, which I can't supply because my PD does >> not start the normal way (as I'm trying to explain). > > > >> 2. The cheatsheet doesn't exist in my PD. > > > that I find strange, and doesn't make that much sense - maybe it was > forgotten somewhere. Anyway, I can send you my copy. As I said before, > put it in [pd]/doc/5.reference and it should open automatically - if > not, open it yourself with your text editor. > Specific to my copy is that I added all the externals that I have > installed. the objects are originally divided into categories, and > somewhen comes the ";" symbol - after that are externals (which you > should also have, if your version comes with everything). > > > >> I'm using Reaktor for now, I wanted to do open source but I see that >> PD is just not developed enough yet for the "average" user. It's a >> shame though, as some operations I can do better with PD objects >> (though I wish PD had the granular samplers and oscillators of >> Reaktor as built-in abstractions or externals). I'm a composer >> though, not a programmer, and I have an August 11 performance I have >> to be ready for. I can't afford waste time trying to fix broken >> things in a program, when I can be making tools instead. And >> honestly, right now Reaktor adapts to "my" ideas that I imagine in >> my head much better than PD. PD has the potential but I think needs >> to be developed farther and with more attention for the "average" >> user needs. > > > well, the most important of all is that each one can go further with > their work, no matter if he uses pd, reaktor or excel. > I don't know Reaktor (but have always heard good about it), but the > main advantage of pd is also it's biggest frustration: to work with > it you must really know what's going on in all levels. it's good > because you get the knowledge which will later allow you to make your > own personal ideas come true, but it'll take you some time before you > can get there and really do something which sounds nice. I'm also a > composer and not a programmer (never had a programming class or read > a computer manual). and with this kind of practice you'll also learn > a lot about acoustics, electronic music, etc. if you have some free > weeks in the summer you can download Puckette's book (don't have the > link now, try the above mentioned site) and read through it and try > out the examples in pd - that is, if pd is for you. if not, then > better use what it suits you best. > > > when you reply, you should use the "reply to all" button. one > specificity of this list is that if you do only "reply", you reply > only to the guy who wrote the previous mail (that I find not so > efficient, but they're used to it). > > good luck, > > João

1 0

Re: [PD] pd cheatsheet
by jmmmp 26 Jul '05

26 Jul '05

I'm sorry that I can't help now - I use the other distribution, and as I still have a slow connection (and now not so much free time), I can't download the other installation and try it myself. Maybe it would help to see where you got this version and ask the e-mail contact that might be there directly (that doesn't seem to be the original Puckette build), or check Help->about pd and say to the list exactly which version you have (until now I thought we were speaking about the same thing). can you open the .exe from the command window with the flags you need? (I don't know this distribution, but that would make sense) if you had the time, you could try to install the "official" version (which you can get in http://crca.ucsd.edu/~msp/software.html), and then the externals individually. it isn't that hard, and when you do it once you do it thousands of times - but if you have already too much on your mind, then leave it for later. > 1. Midi In doesn't work. And the Midi Setup will NOT let me fix it! > It "sees" the devices but it refuses to enable them. It says PD needs a > flag on startup, which I can't supply because my PD does not start the > normal way (as I'm trying to explain). > 2. The cheatsheet doesn't exist in my PD. that I find strange, and doesn't make that much sense - maybe it was forgotten somewhere. Anyway, I can send you my copy. As I said before, put it in [pd]/doc/5.reference and it should open automatically - if not, open it yourself with your text editor. Specific to my copy is that I added all the externals that I have installed. the objects are originally divided into categories, and somewhen comes the ";" symbol - after that are externals (which you should also have, if your version comes with everything). > I'm using Reaktor for now, I wanted to do open source but I see that PD > is just not developed enough yet for the "average" user. It's a shame > though, as some operations I can do better with PD objects (though I > wish PD had the granular samplers and oscillators of Reaktor as built-in > abstractions or externals). I'm a composer though, not a programmer, > and I have an August 11 performance I have to be ready for. I can't > afford waste time trying to fix broken things in a program, when I can > be making tools instead. And honestly, right now Reaktor adapts to "my" > ideas that I imagine in my head much better than PD. PD has the > potential but I think needs to be developed farther and with more > attention for the "average" user needs. well, the most important of all is that each one can go further with their work, no matter if he uses pd, reaktor or excel. I don't know Reaktor (but have always heard good about it), but the main advantage of pd is also it's biggest frustration: to work with it you must really know what's going on in all levels. it's good because you get the knowledge which will later allow you to make your own personal ideas come true, but it'll take you some time before you can get there and really do something which sounds nice. I'm also a composer and not a programmer (never had a programming class or read a computer manual). and with this kind of practice you'll also learn a lot about acoustics, electronic music, etc. if you have some free weeks in the summer you can download Puckette's book (don't have the link now, try the above mentioned site) and read through it and try out the examples in pd - that is, if pd is for you. if not, then better use what it suits you best. when you reply, you should use the "reply to all" button. one specificity of this list is that if you do only "reply", you reply only to the guy who wrote the previous mail (that I find not so efficient, but they're used to it). good luck, João -- Lugostr. 14 79100 Freiburg i. Br. Deutschland +49 (0)761 7074997 jmmmp(a)arcor.de

1 0

Re: [PD] pd cheatsheet
by cyborgk＠nocturnalnoize.com 26 Jul '05

26 Jul '05

No, not exactly... I can't get PD to set any MIDI IN device. Nor will it allow me multiple MIDI OUT devices for some reason. Okay, undoing the MIDI revolution sounds all right but for now outputting MIDI (probably into Audiomulch) would be the easiest way to get prebuilt sounds since there are not a bunch of prebuilt synths etc. for PD. I want to use PD to do logical processing and create aleatoric rhythms and melodies. I know there are flags that can be set on start up, but from the binary installation I don't have access to change the start up (I don't see any batch file), and I need to keep this installation because it has all the libraries with it. If I can't solve this I'll unfortunately have to use commercial software... ~David > well, even if that were the case, it wouldn't be that big of a deal. pc > final scratch pro only works on linux too, right? ;) > > [midiin] is the raw midi interface. > > you do have notein/noteout & ctlin/ctlout on windows as well as a host > of other midi-related objects that work just fine. > > On Thu, 2005-07-21 at 20:36, David Powers wrote: >> Like there is no MIDIIN, it gives an error message saying that only >> works on Linux?! >> >> ~David

9 12

Patch background
by rez 26 Jul '05

26 Jul '05

ei lista i've a new question. Can I use a jpg or something to put a background image in my patch? ... like an asshole to put a bang in the middle. XD. for exemple... Thank you a lot.

5 4

Xeq Documentation Down?
by saint 26 Jul '05

26 Jul '05

Hi, It seems that the help files for xeq at the... http://suita.chopin.edu.pl/~czaja/miXed/externs/xeq.html ...page seem to be down. I can access xeq plain, xeq host and xeq parse but the rest seem to be 404 not found. Can these pages be found anywhere else? or a pd help patch? John. ___________________________________________________________ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com

2 1

Pd-0.38.4-extended-RC2.app released
by Hans-Christoph Steiner 25 Jul '05

25 Jul '05

I got optional Jack support working on this and cleaned up the Pd.app build system quite a bit. Otherwise its basically the same as the previous release. http://at.or.at/hans/pd/installers.html Unless there are any new problems with this one, then I am going to release it. .hc ________________________________________________________________________ ____ "The arc of history bends towards justice." - Dr. Martin Luther King, Jr.

2 2

CVS question
by Jacob Last 25 Jul '05

25 Jul '05

Hi-- I'm trying to figure out how to check the latest pd-devel out of CVS, and all I see in the repository is the non-devel miller's version. Am I missing something? How can I check out the pd-devel CVS? Thanks, Jacob

2 3

Re: [PD] strcmp - comparing paths
by Georg Holzmann 25 Jul '05

25 Jul '05

Hallo! > [select] ? > > like [select symbol], if you want to change the symbol to compare with. oops ...you are right, it's so easy ... :) Thanks, LG Georg -- 5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail +++ GMX - die erste Adresse f�r Mail, Message, More +++

1 0

← Newer
1
2
3
4
5
6
7
...
17
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

Pd-list July 2005