Pd-dev November 2005

pd-dev@lists.iem.at

30 participants
97 discussions

[ pure-data-Feature Requests-1362003 ] Add a serialize operation to [list]
by SourceForge.net 20 Nov '05

20 Nov '05

Feature Requests item #1362003, was opened at 2005-11-20 10:54 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478073&aid=1362003&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: puredata Group: None Status: Open Priority: 5 Submitted By: Frank Barknecht (fbar) Assigned to: Nobody/Anonymous (nobody) Summary: Add a serialize operation to [list] Initial Comment: I benchmarked the way, lists can be serialized using [list split] as described in the list-help.pd file against the binary external version in Zexy called [drip]. The patched version is about 430 times slower than Zexy's [drip]. As serialization is used a lot to do many other list operation (like reversal, rotation, math-operations on lists etc.) including an equivalent to Zexy's [drip] in [list] can be a huge performance boost for little cost, so I suggest to just do that and ship something like [list drip] or [list serialize] with [list] (I prefer the version, that is less typing.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478073&aid=1362003&group_…

1 0

[BUG][alsamidi] no alsamidi init with -alsamidi switch
by federico 20 Nov '05

20 Nov '05

launching pd with the -alsamidi switch has no effect. in order to let puredata open the sequencer port, I have to click Media->ALSA-MIDI and click Apply or Ok, then pd status window will print: Opened Alsa Client 128 in:1 out:1 this can be a bug or a feature, but maybe it is logical, if I set the -alsamidi switch, I *want* MIDI ports opened. also, is there a switch or something to connect these sequencer ports directly to some other ports? (are we planning to insert lash support?) -- ciao Federico

2 1

Re: [PD-dev] Makefile.am ----> Makefile ?????
by Frank Barknecht 19 Nov '05

19 Nov '05

Hallo, zack hat gesagt: // zack wrote: > Trying to compile the msd externs, checked out of the pd CVS externs > dir. > > Something must be done to convert the file "Makefile.am" into a > makefile. You generally don't compile msd* using "make", instead you should use the flext buildsystem. That is, chdir to the respective msd* directory and then run something like "sh $FLEXT_ROOT/build.sh pd gcc install" (I have no idea, why there is a Makefile.am) Ciao -- Frank Barknecht _ ______footils.org_ __goto10.org__

1 0

Makefile.am ----> Makefile ?????
by zack 19 Nov '05

19 Nov '05

Trying to compile the msd externs, checked out of the pd CVS externs dir. Something must be done to convert the file "Makefile.am" into a makefile. I did't get very far: > automake > automake: `configure.ac' or `configure.in' is required > Anyone have a suggestion? thanks Zack

1 0

Successful Pd build with MinGW?
by Hans-Christoph Steiner 18 Nov '05

18 Nov '05

Has anyone built either Pd or Pd-devel using MinGW? Currently, I am working on Pd, but pd-devel would be a good example to work from. FYI: I got basically all of externals/build/src compiling using MinGW. MSVC can only do about half. .hc ________________________________________________________________________ ____ Using ReBirth is like trying to play an 808 with a long stick. -David Zicarelli

1 0

Newbie in problems
by Javier Jimenez Urbano 18 Nov '05

18 Nov '05

Hello, I'm newbie in pure data externals development and I'm trying to compile the externals from the examples in the doc folder with Dev-C++ and Gcc under windows XP but i can't. I'd like to see a makefile that do this or something like that. Is it the best way for windows compiling? Can anybody help me? Thanks. P.D: I'm spanish.

3 2

renaming iemabs help files to the standard
by Hans-Christoph Steiner 18 Nov '05

18 Nov '05

Any chance of renaming the iemabs help files from (help-*.pd) to the standard (*-help.pd)? It would be a matter of running this script that's in CVS: "scripts/convert-help-to-standard.sh" and checking it into cvs. You could do the checkin like this (from tcsh): foreach file (*-help.pd) cvs add $file cvs remove `echo $file | sed 's/$.*$-help\.pd/help-\1.pd/' end I'd do it myself, but I don't know whether the copy in pure-data CVS is the canonical version. .hc ________________________________________________________________________ ____ "Information wants to be free." -Stewart Brand

3 3

pd-cvs's diff format
by Mathieu Bouchard 18 Nov '05

18 Nov '05

would it be possible/desirable to change pd-cvs's diff format to -u ("unified", the one with plusses and minuses) ? ____________________________________________________________________ Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju Freelance Digital Arts Engineer, Montréal QC Canada

2 1

RFC: extended build system layout
by Hans-Christoph Steiner 17 Nov '05

17 Nov '05

Here's the README for the abstractions Makefile. It has the basic outline of what I am doing for all the sections. Comments, feedback, thoughts, etc. would be appreciated. Keep in mind its a work in progress, so there are incomplete parts. How to add your library of patches ================================== The best way to start is to copy the complete section of an existing library, like memento. Then do a case-preserving search-and-replace, replacing "memento" with the name of your library. Editors such as emacs will make the replacements will preversing the case of the text it is replacing. For example, replacing "memento" with "mylibrary" will make these changes: MEMENTO_NAME = memento objects_memento: to this: MYLIBRARY_NAME = mylibrary objects_mylibrary: If your editor does not do this, you will need to do two separate search-and-replace actions, one for all lowercase, and another for all uppercase. Once you have your section setup after the search-and-replace, you need to edit the paths of the files that you want to include. The paths will be the only text written out. All of the installation paths will be Makefile variables. Check the below example: install -d $(HELP_DEST)/$(MEMENTO_NAME) install -p $(ABSTRACTIONS_SRC)/rradical/memento/*-help.pd \ $(HELP_DEST)/$(MEMENTO_NAME) becomes: install -d $(HELP_DEST)/$(MYLIBRARY_NAME) install -p $(ABSTRACTIONS_SRC)/mylibrary/*-help.pd \ $(HELP_DEST)/$(MYLIBRARY_NAME) Also, since it is common to store the help patches in the same directory as the object patchs, you can use this pattern to exclude the help patches from being copied to $(OBJECTS_DEST): install -p $(shell ls -1 $(ABSTRACTIONS_SRC)/mylibrary/*.pd | \ grep -v '\-help.pd') $(OBJECTS_DEST)/$(MYLIBRARY_NAME) Explanations of Terms ===================== MYLIBRARY_NAME = mylibrary At the top of each library's section in the Makefile, you will see a variable MYLIBRARY_NAME. This variable is the name used to install the abstractions. This should be all lowercase since its used in the loading of objects within Pd (e.g. [mylibrary/myobject]). $(APPLICATIONS_DEST): If your project is an application or patch that is meant to be run directly, then it should go into this directory in its own subdirectory. This directory is a browsable collection of applications. If your application has a lot of files associated with it, put a main patch and have the extra files in a subdirectory. rradical/usecases/showcase is a good example of this. This is the only place were mixed or upper case is appropriate in directory names. $(DOCS_DEST): All help patches should go into this directory in a subdirectory with the same nameas the subdirectory for your objects. For example, for [mylibrary/myobject] above, the helpfile would be "mylibrary/myobject-help.pd". The subdirectory name (e.g. mylibrary) should always be all lowercase. $(MANUALS_DEST): If you have any other kinds of documentation, like a text or HTML manual, or a Pd-based tutorial, then it should go into this directory, again in a subdirectory with the same name as the library or application. Using the previous example again, the "mylibrary" manual would be "mylibrary/mylibrary.html". The subdirectory name (e.g. mylibrary) should always be all lowercase. $(OBJECTS_DEST): If your project consists of objects that are meant to be reused in other patches rather than used as a application, then they should go into this directory. They should be in a directory with a distinct name. This will be the name of your library of objects, which can be added to the path, or called directly (e.g. [mylibrary/myobject]). The subdirectory name (e.g. mylibrary) should always be all lowercase. "objects" targets To add your objects to this build system, first make your own target and add it to the "objects" target. For example: for the RRADical objects, there is a target called "objects_rradical:" which does everything needed to install the RRADical objects. This includes installing help patches and any other documentation. "applications" targets: This target is meant for any patch that is intended to be opened up and used, played, ran, etc. The RRADical showcase.pd is a good example ________________________________________________________________________ ____ News is what people want to keep hidden and everything else is publicity. - Bill Moyers

1 0

proposed fix for objects named with +,-,*,^, etc.
by Hans-Christoph Steiner 17 Nov '05

17 Nov '05

So I am able to get objects with +, -, *, and ^ in the name to compile as individual files, I was not able to get objects with / in the name to work, plus they might cause problems with geiger namespaces (i.e. [libname/object]). But the only problem left is the setup functions. AFAIK you are not allowed to have setup functions named mtx_+_setup(), mtx_-_setup() , etc. So if pd would translate the symbols to a word, like "mtx_plus_setup", like it does for ~, then this whole thing would work. Currently, there is a little workaround for objects with aliases. If you load [mtx_sub], for example, then you can load [mtx_-] since [mtx_sub] will generate the symbol "mtx_-", etc. .hc ________________________________________________________________________ ____ "[W]e have invented the technology to eliminate scarcity, but we are deliberately throwing it away to benefit those who profit from scarcity." -John Gilmore

3 13

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

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 November 2005