Pd-dev October 2004

pd-dev@lists.iem.at

32 participants
58 discussions

makefile.nt: how to make asiolib.dll / lib
by Tim Blechmann 28 Oct '04

28 Oct '04

hi all.. i'm currently trying to compile pd for windows using the command line compiler ... since the mingw makefile of devel_0_37 is broken (linking fails: filename or extension to long) i'm fighting with the ms cl compiler ... pd builds fine, but requires a asiolib.dll / .lib ... how can i build that? cheers ... tim -- mailto:TimBlechmann@gmx.de ICQ: 96771783 http://www.mokabar.tk After one look at this planet any visitor from outer space would say "I want to see the manager." William S. Burroughs

3 5

Re: [PD] pure data alsa sequencer support
by Pablo 28 Oct '04

28 Oct '04

well... i have been playing with the code today and managed to add native alsa sequencer support to pure data. output, input and configuration window are working nicely, as well as most of the midi objects (theres still some midi messages i don't know -touch and polytouch, and pitchbend passes strange values). if there is any interest in adding this code to pd i can provide the code, it's just an s_midi_alsa.c and some changes to the interface file. (must still touch the make system and input command line options, but would like to see what people think). pablo Buenas Frank Barknecht, el 27 de oct de 2004, a las 02:35 escribiste: > Hallo, > pablo hat gesagt: // pablo wrote: > > > i was wondering whether pd has support for the alsa sequencer or it just > > admits connecting through the oss devices. i have been looking around but > > found nothing, just a method to connect it through an alsa virtual device > > to the sequencer. > > It's the only method: You need a snd-virmidi card. Actually Pd was the > reason for me to write the Softsynth-Sequencer-Howto. > > Ciao > -- > Frank Barknecht _ ______footils.org__ > > _______________________________________________ > PD-list(a)iem.at mailing list > UNSUBSCRIBE and account-management -> http://iem.at/cgi-bin/mailman/listinfo/pd-list

5 5

Re: [PD-dev] Re: [PD] PDContainers alpha release
by Georg Holzmann 27 Oct '04

27 Oct '04

Hallo! > Yes, I think, this is probably bad. I'd vote for making this a message > to the object, like [init 10(. The last one will win then. ;) I don't know how you really mean this. Now there is the message [resize 10(, where you can resize the array. Do you mean with [init 10( the same ? > Maybe I'm spoiled by Python, but I think, Exceptions are quite useful. Of course ... LG Georg -- Geschenkt: 3 Monate GMX ProMail + 3 Ausgaben der TV Movie mit DVD ++++ Jetzt anmelden und testen http://www.gmx.net/de/go/mail ++++

2 1

Re: [PD-dev] Re: [PD] PDContainers alpha release
by Georg Holzmann 27 Oct '04

27 Oct '04

Hallo! > Actually I think, that maybe throwing an exception would be a cleaner > way here and in other places, where something tries to access > non-existing Elements (like the other "Element &get()" methods. > However then all uses of get() will need to catch possible exceptions. Yep, I also though about this yesterday. The problem is/was, that i decided at the begin to not use exceptions (but this was a bad decision). I think I will rework the code a bit and use exceptions (not only in the get methods), because there were some more situations where I thought I should use them. > outlet gets a bang in the catch block, if an exception occurs, but > that's just for illustration and should be removed, as the list is > not empty in fact, when the exception is thrown. > Or maybe it should not be removed? It depends on what the right outlet > should indicate: an empty list or the "end" iterator of a container. > Thinking of how [textfile] and [qlist] use the right outlet, banging > it at "EOF" would also be sensible, IMO. Thats a good question. The concept of the right outlet isn't really clear (because all the containers are different...). My idea was, that if get doesn't output an element (so the list is empty or the iterator is at a position where's no element) there should be a bang at the right outlet, so that you can react in PD. The same e.g. with the map: if the requested key (with get) isn't stored in it, there's a bang at the right outlet. Now I just saw that there's a problem with the vector and deque: I didn't write it into the help-patches, but you can give a vector or a deque a second init-arg: the size (i thought then it's similar to the array). Then all the elements are initialized with Elements of length 0 and the bang at the outlet is handled a bit different (see attached patch)! But maybe this with an init-size isn't a good idea ? And the bang should also be if theres an invalid index (see attached patch) !? Thanks for your advices, LG Georg -- Geschenkt: 3 Monate GMX ProMail + 3 Ausgaben der TV Movie mit DVD ++++ Jetzt anmelden und testen http://www.gmx.net/de/go/mail ++++

2 1

Re: [PD-dev] Re: [PD] PDContainers alpha release
by Georg Holzmann 27 Oct '04

27 Oct '04

Hallo! An other problem with the init size of vector/deque: If you have more objects with the same namespace in a patchand every object with a different size (e.g. [h_vector blabla 100] ... [h_vector blabla 10] ... [h_vector blabla 1]) it will be very funny to debug, because if it's a big patch, you're not shure if this size will be initialized !? LG Georg -- +++ GMX DSL Premiumtarife 3 Monate gratis* + WLAN-Router 0,- EUR* +++ Clevere DSL-Nutzer wechseln jetzt zu GMX: http://www.gmx.net/de/go/dsl

2 1

Re: [PD] PDContainers alpha release
by Frank Barknecht 26 Oct '04

26 Oct '04

Hallo, (switching to pd-dev mode.) Georg Holzmann hat gesagt: // Georg Holzmann wrote: > > I will, as soon as I get a deeper look. However I also have found one > > bug, see attached patch, but unfortunatly no solution yet. Maybe you > > can find out, why this is happening. > Thanks, just fixed and again on http://puredata.info/Members/holzi/ ! I see your fix, which as you comment is a bit hairy. ;) Actually I think, that maybe throwing an exception would be a cleaner way here and in other places, where something tries to access non-existing Elements (like the other "Element &get()" methods. However then all uses of get() will need to catch possible exceptions. I implemented an example of this in attached files. There, the right outlet gets a bang in the catch block, if an exception occurs, but that's just for illustration and should be removed, as the list is not empty in fact, when the exception is thrown. Ciao -- Frank Barknecht _ ______footils.org__

1 1

Trans.: Re: [PD-dev] re: branch convergence (fwd)
by ydegoyon＠free.fr 26 Oct '04

26 Oct '04

----- Message transféré de ydegoyon(a)free.fr ----- Date : Tue, 26 Oct 2004 04:52:10 +0200 De : ydegoyon(a)free.fr Adresse de retour :ydegoyon@free.fr Sujet : Re: [PD-dev] re: branch convergence (fwd) À : Matju <matju(a)sympatico.ca> ok, i can fairly understand, but will it be JBoss MVC's model compatible? this means you would allow some .css styles definitions? i don't see what's personal in this mail too, really. sevy Selon Matju <matju(a)sympatico.ca>: > > ydegoyon(a)free.fr wrote: > > > hi, matthieu, > > > * switched to a jmaxish look > > this, we all told you 'no go'! ! > > Imitating your style of bringing personal mails to the pd mailing lists, > here am I, replying to you. > > FYI, the jMax look will require a commandline option (pd -modelview) to > enable the new GUI code, and even then, the look is configurable, so you > can set the colours you want as well as some other details. (and in Graz, > I all showed you how ridiculously easy it is to change the color scheme in > ImpureData!) > > > think the graz t-shirts are all in pure > > 'pd aesthetics' style and they are cool ) > > My aesthetics aren't the jMax aesthetics. They are the mechanism/policy > separation aesthetics and the model/view separation aesthetics. Those > things I bring in will make it easier for you to make a version of Pd that > uses NCurses instead of Tk... if you want to. Or to have easy-to-maintain > Catalan translations of Pd menus and dialogs. Or ... (so on). > > The jMax look is a very secondary feature, and I won't force it over any > people, and I won't even force it on those who will want to use "pd > -modelview" ! > > _____________________________________________________________________ > Mathieu Bouchard -=- Montréal QC Canada -=- http://artengine.ca/matju > > > _______________________________________________ > PD-dev mailing list > PD-dev(a)iem.at > http://iem.at/cgi-bin/mailman/listinfo/pd-dev > ----- Fin du message transféré -----

2 1

Trans.: Re: [PD-dev] re: branch convergence (fwd)
by ydegoyon＠free.fr 26 Oct '04

26 Oct '04

1 0

Re: [PD-dev] re: branch convergence (fwd)
by Matju 26 Oct '04

26 Oct '04

ydegoyon(a)free.fr wrote: > hi, matthieu, > > * switched to a jmaxish look > this, we all told you 'no go'! ! Imitating your style of bringing personal mails to the pd mailing lists, here am I, replying to you. FYI, the jMax look will require a commandline option (pd -modelview) to enable the new GUI code, and even then, the look is configurable, so you can set the colours you want as well as some other details. (and in Graz, I all showed you how ridiculously easy it is to change the color scheme in ImpureData!) > think the graz t-shirts are all in pure > 'pd aesthetics' style and they are cool ) My aesthetics aren't the jMax aesthetics. They are the mechanism/policy separation aesthetics and the model/view separation aesthetics. Those things I bring in will make it easier for you to make a version of Pd that uses NCurses instead of Tk... if you want to. Or to have easy-to-maintain Catalan translations of Pd menus and dialogs. Or ... (so on). The jMax look is a very secondary feature, and I won't force it over any people, and I won't even force it on those who will want to use "pd -modelview" ! _____________________________________________________________________ Mathieu Bouchard -=- Montréal QC Canada -=- http://artengine.ca/matju

1 0

Re: caching user settings in .pdrc
by cdr 26 Oct '04

26 Oct '04

> blah blah courier is ugly but tahoma doesnt exist on linux... > > Well, it happened in a checkin by "ix9": know it sounds crazy, but a cvs admin checked it in...it seems CVS caches diffs in a user RCS dir on the server, if you dig youll see the comment was "fixed_bug_in_shell", and at the same time a fix was committed by someone else to externals/ggee/shell...perhaps ssh keys somehow facilitated this? clearly the solution is to make a font selection dialog. saw some nice examples on the tcl-wiki...my question is what is the standard procedure for storing these prefs between sessions? some new delineated section in .pdrc? > I haven't tried it but I heard it was missing features. Is it an > optional console? if you care about adjusting scrollback maybe, couldnt get mswConsole to work on win32, and couldnt get the big box to disappear when using -stderr, but lets wait till its actually out. if those work i dont see a reason to not use it...but since they all work in matjuConsole, maybe just using that would be simpler? not my decision... was thinking a 'view' menu in the top window to invidually show/hide the console log, peak-meters, and message/gui input...and saving this state between session rather than polluting more command arguments...refer to comment above about where to store settings..

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pd-dev October 2004