Pd-list March 1999

pd-list@lists.iem.at

18 participants
32 discussions

Re: Pd 0.25 pre-release
by Miller Puckette 15 Apr '99

15 Apr '99

HI all, in the 0.25 pre-release (NT only!) the "-adc" flag has been renamed "-nodac" and the "-dac" is now "noadc,", contrary to the usage message that "pd -help" outputs. On SGI I've only compiled Pd for "o32" so far (my SGI machine is 5 years old!) and would like someday to put out an "n32" version which would run quite a bit faster. I would suggest leaving "pd-gui" in o32 so that it works with TK, and only compiling "pd" itself with n32. The two only communicate via sockets and there's no need for them both to be n32. cheers Miller

4 3

Possible Memory Leak in pd-linux-0.25TEST4.tar
by John Michael Davison 01 Apr '99

01 Apr '99

Regarding pd-linux-0.25TEST4.tar --> pd/src/m_memory.c, is this a memory leak? void *getzbytes(size_t nbytes) /* get bytes, zeroed out */ { void *ret; if (nbytes < 1) nbytes = 1; ret = getbytes(nbytes); ret = (void *)malloc(nbytes); <------ MEMORY LEAK? if (ret) memset(ret, 0, nbytes); return (ret); } -- John Davison jdavison(a)inch.com

5 6

Re: Possible Memory Leak in pd-linux-0.25TEST4.tar
by Miller Puckette 30 Mar '99

30 Mar '99

It sure is. Thanks! >is this a memory leak? ... ret = getbytes(nbytes); ret = (void *)malloc(nbytes); <------ MEMORY LEAK? ... cheers Miller

1 0

Re: Re: pd-documentation
by CHRISTIAN FELDBAUER 27 Mar '99

27 Mar '99

Hi Guenter ! You wrote: > The most important thing to do is to check the online documentation. > > Comment on things you think are not clear. > > Finding out what is missing is actually the most important part for > documentation :) I noticed, that many objects haven�t got a help-patch (reference) yet. I also found the existing patches rather unsatisfying. Don�t you think it would be a good idea if i wrote some ? Ciao Feldi

1 0

Fast Test pd.025TEST4.tar.gz
by Winfried Ritsch 27 Mar '99

27 Mar '99

Hi, I had downloaded and unpacked, made a directory /home/msp/pd ;-) (PREFIXPATH was that) and testet pd-oss with pvoc.pd and it worked without clicks even moving windows: Pentium II -233 MHz, Debian Linux 2.1, Kernel 2.0.36 OSS-free driver using isapnp to initialize I didnt test MIDI on my office computer top shows always 95% CPU even no patch is open. Loadmeter says 204, but when I set pd-oss to suid root (in linux use suidregister) then my system deadlocks I have to reboot: I will examine this more at home... mfg winfried PS.: Your noisefloor does it sound like open Input constant hiss or digital noise (brizzeln). I dont know your card but, a common problem is that the mixer does not work correctly so that, one input is mixed to the output. Test this with putting your finger on the hot part of the inputs and hear if you there is a sort of hum. There are also inputs on the card directly for the CD-Players or tuners, even the FM-Synth-Chip can make a lot of noise.

1 0

Release: Pd-0.25 test 4 for Linux
by Miller Puckette 26 Mar '99

26 Mar '99

Hi all, I've put out a "test release" of Pd for Linux. So far I haven't been able to get it to get audio in or out reliably; I don't know if this is a problem with Pd, my drivers, or my audio hardware. I would be eager to hear if any of you who has a running version pf Pd could test this one out! I compiled Pd for both ALSA and OSS drivers; you should just be able to type "~/pd/bin/pd-oss" or ~/pd/bin/pd-alsa" to run it. cheers Miller

1 0

Re: FW: Audio drivers again?
by Miller Puckette 26 Mar '99

26 Mar '99

HI all, Well, I can now report that after a couple of weeks of trying, I still haven't been able to get either OSS or ALSA (0.2 or 0.3) to run reliably with my "opl3sa3" sound hardware. I'm going to try one more thing (using ALSA's native mode) today, but I don't really expect it will change much. To answer some of Guenter's specific questions: OSS (at least as it's delivered in RedHat 5.2) doesn't work in full duplex with my opl3sa3 card. My high noise floor problem in OSS didn't go away when I tried switching DMA channels. Guenter's remarks that both channels are 8 bit conflicts with comments in the INSTALL documentation for the ALSA distribution, but anyway switching the channels didn't help. In ALSA 0.2 I got a 25 dB noise floor, roughly the same as in NT, and in 0.3 I got 40 dB in the left channel, 25 in the right. I confirmed Guenter's finding that ALSA's OSS emulation doesn't provide full duplex. I think the next step should be for me to change teh audio hardware, but I can't do this before mid April. So I now plan to put out another "test release" in case any of the rest of you are curious to see how is works on other cards... cheers Miller

2 1

Audio drivers again?
by Miller Puckette 25 Mar '99

25 Mar '99

Hi list, I'm now running Pd under Red Hat Linux, and (like everybody else) I've run into some questions about audio/MIDI drivers. Would anyone already know the answers to these? 1. I've got an OplSa3 soundcard and so far I've been using the OSS drivers (the free ones from the RedHat 5.2 CDROM). I notice that the ADC noise floor (measured in the test tone patch) is around 45 dB, whereas the SAME HARDWARE gets a noise floor of 20 dB under NT. I've got a wild guess that this might be related to which of the two "DMA channels" I assign to "DMA0" and "DMA1"... any other wild guesses out there? 2. I also want to test the ALSA drivers. I note in the ALSA FAQ (part of the release) that ALSA comes with an OSS compatibility package. So is there any advantage to using the ALSA drivers "natively" (as s_alsa.s does) rather than just using s_linux.c and having ALSA emulate OSS audio? 3. Same question for MIDI... is it likely to be worth the trouble of rewriting the MIDI I/O code to address ALSA natively? If any of you have any experience that might suggest answers to these I'd be grateful! Miller

2 1

FW: Audio drivers again?
by Guenter Geiger 25 Mar '99

25 Mar '99

The following was supposed to go to the list too. Guenter > -----Original Message----- > From: Miller Puckette [mailto:mpuckett@man104nfs.UCSD.EDU] > Sent: Wednesday, March 24, 1999 6:29 PM > To: pd-list(a)iem.mhsg.ac.at > Subject: Audio drivers again? > > > Hi list, > > I'm now running Pd under Red Hat Linux, and (like everybody else) I've > run into some questions about audio/MIDI drivers. Would > anyone already know > the answers to these? > > 1. I've got an OplSa3 soundcard and so far I've been using > the OSS drivers > (the free ones from the RedHat 5.2 CDROM). I notice that the > ADC noise > floor (measured in the test tone patch) is around 45 dB, whereas the > SAME HARDWARE gets a noise floor of 20 dB under NT. I've got a wild > guess that this might be related to which of the two "DMA > channels" I assign > to "DMA0" and "DMA1"... any other wild guesses out there? > Hmmm .. if it is not a problem of the mixer settings, IÅ½d rather suspect something in the OplSa3 driver code. DMA0 and DMA1 are both 8 bit DMAÅ½s and they shouldnÅ½t do anything else but transfer the data to the card. So it could be any open mixer channel "mic in", "line in" or "CD in", or prob. the relation between "wave out" and "master out" channels. Or something in the driver code. Do you get reliable full duplex with this card ? (Just asking cause I want to know which cards work) > 2. I also want to test the ALSA drivers. I note in the ALSA > FAQ (part > of the release) that ALSA comes with an OSS compatibility package. So > is there any advantage to using the ALSA drivers "natively" > (as s_alsa.s > does) rather than just using s_linux.c and having ALSA > emulate OSS audio? ALSAÅ½s OSS emulation simply doesnÅ½t work in full duplex (on my system at least). Seems it doesnÅ½t like the small audio buffer settings. Anyhow, I never understood why they really changed the API instead of expanding it in a compatible way and wrapping their ALSA library around it. > > 3. Same question for MIDI... is it likely to be worth the trouble of > rewriting the MIDI I/O code to address ALSA natively? > Together with WiniÅ½s MIDI library we can use the "raw midi device". This is supported the same way on OSS and ALSA. Its just opening the device file and reading or writing to it the MIDI bytes. Currently we donÅ½t support MIDI for accessing the internal sequencer (should we ?). Guenter

1 0

Re: Waveout
by Miller Puckette 25 Mar '99

25 Mar '99

Christian Guirreri wrote: >... Anyway, I can't seem to get Waveout to work - loading it normally it doesn't find any errors, but I have no sound. When I choose the desired port manually through command prompt and use verbose, I get the mmsystem error (ie - waveOutOpen: MMSYSTEM004 The specified device is already in use. Wait until it is free, and then try again.), which means pd itself is probably choosing a port I can't really use feasibly when I load it without the command line settings (I have a virtual audio device loopback installed that to pd probably appears to be an open port). I believe in Pd-0.24 the port numbers for audio devices were off by one; i.e. to get "audio output device 2" you have to specify -soundoutdev 1. Perhaps this is part of the problem... Miller

1 0

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 March 1999