Pd-list February 2002

pd-list@lists.iem.at

89 participants
173 discussions

pd asio
by Thomas Grill 08 Feb '02

08 Feb '02

Hi list, hi Miller, i succeeded in building the asio version of pd for Windows (using the s_mac.c interface). The reason trying it out was that i realized that pd grabs about 20% of cpu time when using 8 ins and 8 outs with MME drivers. As the audio interface (RME HDSP Multiface) is busmaster and optimized for asio it doesn't need to be that way. (under Max/MSP it needs about 3% of G4/400 at 18in/18out) Yet, the resulting version of pd is incredibly slow (eats all the cpu time) so that trying out things is really annoying. I don't even know whether it produces sound. As i do not have the time to search for the reasons now.... has anyone tried to build the asio verson as well? Is there any usable executable out there? greetings, Thomas

1 0

Re: [PD] Using C++ sources for externals
by Frank Barknecht 08 Feb '02

08 Feb '02

mark wrote: > The trick is to have C functions (global functions in C++ I guess) exported > and to work in C++. C++ is geared up nicely for this. I have a version > of my library that builds in C++ - I'll dig out the source code later if I > get > a chance. That would be nice. In the meantime I have read some source code and the comp.lang.c++ FAQ. Basically it seems to me that there are two ways to reuse C++ libraries/header/cpp files: <now I'll start jabbering, as I don't fully understand the following ;) > 1) Wrap it up with CPPExtern of GEM or something similar, maybe more sophisticated - and code in pure C++ yourself, with OO and all that bells and whistles. 2) Leave out the _real_ object orientation and write the main external code in C++, but not using a lot of the C++ features. I think, that's what Yves did in his stksitar adaption of Perry Cooks C++(!)-library STK. Reading through "stksitar~.cc" all this looks a lot like your typical C-external code, except usage of a sitar class which comes out of a C++-class defined in sitar.h (by P.Cook?!) Later on the setup function "stksitar_tilde_setup" is defined as: extern "C" void stksitar_tilde_setup(void) So obviously this function needs special treatment, whereas the others work without the extern declaration. Why does 2) work? Can I just code right away in C++, and then just declare the _setup function as 'extern "C"' and all is well? I don't think so, but where is this the right, or the convenient way to go? Regards, -- Frank Barknecht <barknecht(a)dradio-online.de> -= www.dradio.de =- DeutschlandRadio-Online * Redaktion KÃ¶ln tel 0221 - 345 1471 * fax 0221 - 345 1480

3 3

[announce] xeq's testing time: feature freeze of xeq 0.1
by Krzysztof Czaja 08 Feb '02

08 Feb '02

hi all, now the main focus will be on testing (please help!), code cleaning, writing user documentation (still very incomplete), and examples (they are in the most miserable state one could imagine). The more recently added classes are: xeq_polyparse (multilayer version of xeq_parse), xeq_polytempo (a tool for heterophonic textures and other `polirubato' effects), xeq_record (sequence recorder), and xeq_host (a hostifying wrapper for the players). One major feature left for the beta phase is a derivation api usable by anyone willing to build new classes prefixed by xeq, but dynamically linked. Linux releases are now generated whenever there is any modification to the code, using a simple snapshot build counting mechanism, while dll synchronization is still manual (and usually somewhat lagging behind). Let me remind the obvious: since xeq is a qlist extension retaining all of qlist's functionality, it is a _generic_ sequencer, not only a midi file player and recorder. It is ready for scoring arbitrary events, building sequence hierarchies, etc. General purpose extensions include time-positioning, looping, multilayer playback and more. The new features planned for xeq 0.2 (first alpha build due in a few weeks, hopefully) are: xeq~ microsequencer, handling of delta vectors (and tempo vectors), and xeq_vexing (sequence to multiple arrays mapper). Also the real xeq_data is going to replace current dummy (if only Pd data templates stabilize). Downloadable at suita.chopin.edu.pl/~czaja/miXed/externs/xeq.html Krzysztof

2 1

[PD][announce] shoutamp~ for win!
by Olaf Matthes 07 Feb '02

07 Feb '02

Hi, I finally found a version of lame / mpg123 that _works_ under win. Now you can also find a window$ version of the shoutamp~ external at http://www.akustische-kunst.de/puredata/shoutamp.html Btw., connecting to SHOUTcast servers does now also work... Olaf

2 1

building .dlls in VC++ for windows
by Mark Khemma 06 Feb '02

06 Feb '02

hello, i'm new to pd and the list so bare with me. How does one go about building externs/dll's using VC++ 6? where does the .c and the .obj come into the picture. i looked at the howto-externals but it there is no info on building dll's in windows. -thanks in advance mark k.

2 2

Using C++ sources for externals
by Frank Barknecht 06 Feb '02

06 Feb '02

Hi, I'm considering for some time now to rewrite PDX7, my 6-operator FM-synth-abstraction, as an external, because that patch is quite a resource hog. This old plan is fueled again, because Juan Linietsky now published his dx7 emulator rx-saturno, availabe @ http://reduz.com.ar/rx_saturno The program source code is nicely modularised, so I would like to reuse a lot of the code written by Juan. Unfortunatly it is written in C++, which is no problem to me, as I know C++ better than C, but it obviously is a problem for PD. Now my question is: How could I reuse most of the C++ code, but still have this run as a PD external? In my C++ books, the other way around (using C libraries in C++) is well explained, but I have no idea how to use C++ in C. Do you have any pointers for me, what should I read, example code?? Thanks and bye, -- __ __ Frank Barknecht ____ ______ ____ __ trip\ \ / /wire ______ / __// __ /__/ __// // __ \ \/ / __ \\ ___\ / / / ____/ / / / // ____// /\ \\ ___\\____ \ /_/ /_____/ /_/ /_//_____// / \ \\_____\\_____\ /_/ \_\

4 3

Some newbie questions
by rinks 06 Feb '02

06 Feb '02

Hi list, i am new to this list and i am very impressed by pd. I could not find an answer to the following questions in the archive: 1. I want to save and recall groups of values (like snapshots) 2. I want to record and replay the modification of values (like a midi sequencer for midi controllers) 3 Is it possible to seperate the gui from the rest of a patch? Do you have an idea? Any help is appreciated... Thanks rinks

2 2

[announce][sorry for all these releases] shoutamp~v0.2+
by Yves Degoyon 06 Feb '02

06 Feb '02

hi again, because Olaf brought an enhancement to shoutamp~, got to release a v0.2+ : new feature is : support for connections like : connecturl http://myserver:myport/mymountpoint well, this way, it will behave like xmms, winamp, ..... otherwise, it's just like v0.2. cheers, Yves/ http://ydegoyon.free.fr [ don't get no cash from ur visit ]

1 0

[announce][candidate] shoutamp~ v0.2
by Yves Degoyon 05 Feb '02

05 Feb '02

hi, ok, there were some bugs in shoutamp~ v0.1, it was really alpha. so, here's v0.2 with the following improvements : * gracefull disconnection * buffer status displayed when graphic * fixed a potential buffer overflow which might have lead to some crashes * connection to a shoutcast server [ thanx to Olaf for this one ] + resampling will not be implemented since you can run pd at the desired samplerate in order to connect to non-44100 streams. joined is the list of files i've streamed through shoutamp~, it played them steadily. cheers, Yves/ http://ydegoyon.free.fr

1 0

[announce] shoutamp~
by Yves Degoyon 05 Feb '02

05 Feb '02

hi, here's the sunday delivery : shoutamp~ is an icecast/shoutcast(soon) client for PD. it is co-authored by Olaf Matthes & I. it has only been tested with icecast on linux. it should be quite ok for shoutcast. BUT, there's a problem ( reported by Olaf ) with MP3 decoding on Windows, so mp3live~ and shoutamp~ are not available for windowers. Here's the state-of-the-art for MP3 streaming : PD <------> PD : mp3streamout~/mp3streamin~ [ mp3live~ ] PD --------> Shoutcast/Icecast : shoutcast~ Shoutcast/Icecast -----> PD : shoutamp~ PD ------> File : mp3write~ File -----> PD : mp3fileout~/mp3streamin~ [ mp3live~ ] I'm sorry not to mention d_mp3 but i only had bad sound with it. It's even not compatible with mp3live~ and shoutamp~ due to the rewritting of lame's decoding routines. Enjoy !!! Yves/ http://ydegoyon.free.fr

2 3

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 February 2002