Pd-list February 2002

pd-list@lists.iem.at

89 participants
173 discussions

Re: [PD] ASIO for win NT/2K
by Michael Iber 25 Feb '02

25 Feb '02

This is brilliant!!!!!! Will you publish your version? (I am afraid I don't have MSVC) I would appreciate it. Bravo, Michael At 18:24 19.02.02 -0500, you wrote: >I compiled an ASIO version of PD using PortAudio v1.7 with the beta ASIO >drivers and Steinberg's ASIO 2.0 SDK. The program compiled successfully >using s_mac.c and s_portaudio.c with MSVC++ 6.0. > >Both audio input and output are working as tested on a DIGIGRAM VxPocket >v2.0 PCMCIA audio card running on a Sony Vaio under win2k with the latest >driver package from Digigram (v4.4c). I tested it with a microphone and >monitor speakers. > >The software reports 12ms latency for each device: i.e. 24ms I/O latency. >This corresponds with what I heard and is a significant improvement over >the ~350ms latency reported when using the Microsoft Wave or DirectX >drivers. > >Here's the PortAudio startup report: > >P:\pd\bin>pd >MIDI: not yet implemented >read/write >PaASIO_QueryDeviceInfo: numDrivers = 1 >PaASIO_QueryDeviceInfo: InputChannels = 2 >PaASIO_QueryDeviceInfo: OutputChannels = 2 >PortAudio : possible sample rate = 32000 >PortAudio : possible sample rate = 44100 >PortAudio : possible sample rate = 48000 >---------------------------------- >PortAudio : minSize = 504 >PortAudio : preferredSize = 512 >PortAudio : maxSize = 2016 >PortAudio : granularity = 126 >PortAudio : User buffer size = 128 >PortAudio : ASIO buffer size = 512 >PortAudio : Minimum BufferOffset for Output = 0 >PortAudio : ASIOCreateBuffers with size = 512 >PortAudio : InputLatency = 572 latency = 12 msec >PortAudio : OuputLatency = 572 latency = 12 msec > >To do: create a new file called s_nt_asio.c that includes the NT MIDI >interfaces as well as the PortAudio calls from s_mac.c. Has someone done >this already ? If not, I'll try and make it. > >Best regards, > >Mike Casey >www.media.mit.edu/~mkc > > >----- Original Message ----- >From: "Miller Puckette" <mpuckett(a)man104-1.ucsd.edu> >To: "mark" <mark(a)junklight.com> >Cc: "Matthew Nish-Lapidus" <mattn-l(a)rogers.com>; "PD List" ><pd-list(a)iem.kug.ac.at> >Sent: Sunday, January 27, 2002 6:09 PM >Subject: Re: [PD] ASIO drivers in windows > > > Hi all, > > > > There's a Pd "portaudio" interface (in s_mac.c and s_portaudio.c), and > > portaudio supports ASIO in "beta"... see > > http://www.portaudio.com/ > > > > So in principle you can get Pd to talk to ASIO by just linking it all > > toghether. I haven't tried this because I don't have any soundcards in my > > Windows machine that support ASIO. Michael Iber http://www.iberspace.de mailto://mail@iber-online.de

4 4

new version of gripd 0.0.11
by Joseph A. Sarlo 25 Feb '02

25 Feb '02

There's yet another version of gripd available (mostly just to fix some things I accidently left broken in the last release). http://mambo.peabody.jhu.edu/~jsarlo/gripd/ -Changes in v0.0.11- Added keystroke catching Fixed open file bug (replace error trap) Added icon (Windows) Disconnect option is now available while connecting Socket and joystick poll times are now saved in gpd file -- ______________________________ | | Joseph A. Sarlo | | jsarlo(a)mambo.peabody.jhu.edu |______________________________

1 0

work
by Matthew Nish-Lapidus 24 Feb '02

24 Feb '02

hi, there's a lot of discussion on the list about how to get things to work, externals, programming, etc... all that stuff is great and very helpfull. but PD is meant for artists to use in creating art. i'd like to see/hear about some of the stuff everybody is doing with PD/GEM and how/why they do it. nobody seems to talk about why they need to learn all this information.. so if anybody is doing anything interesting with PD send a message to the list.. or if the list doens't want it, just send it to me. thanks, matt.

6 5

unresolved external symbol _garray_class
by Juha Vehviläinen 24 Feb '02

24 Feb '02

Hi, I get this when trying to compile arraysize.c from pixlib: arraysize.obj : error LNK2001: unresolved external symbol _garray_class My msvisualc++ commandline is cl arraysize.c /LD /Ox /I\pd\src \pd\bin\pd.lib Help! What am I missing? juha

1 0

shoutcast on linux
by Bill Orcutt 24 Feb '02

24 Feb '02

Hi- I'm having trouble getting shoutcast~ working on RH 7.2. everything seems to be ok-- lame (have tried both 3.89 and 3.91) compiles and installs ok in /usr/local/lib; shoutcast~ compiles and installs without errors, but when i try to create the object in pd, i get: /usr/local/lib/pd/externs/shoutcast~/shoutcast.pd_linux:libmp3lame.so.0: cannot open shared object file: no such file or directory shoutcast~ ...couldn't create libmp3lame.so.0 is in /usr/local/lib. should it be somewhere else? thanks Bill

2 2

shoutamp~ on a real scale
by Yves Degoyon 24 Feb '02

24 Feb '02

hi, i've been to a MAX/NATO/PD/SELF-MADE SOFTWARE workshop this week-end where a guy tried to mix several streams received with shoutamp~. unfortunately, this did not work with latest lame library [3.91]. i ran both tests at home, and, yes, only lame V3.89 works !!! 3.91 is a beta release and should not be used. i also fixed a bug in shoutamp~ : it was not handling input buffer overflow gracefully. so, there's a v0.4 uploaded now. cheers, Yves/ http://ydegoyon.free.fr

1 0

[Framestein][announce] 0.28!
by Juha Vehviläinen 24 Feb '02

24 Feb '02

0.28 - finally, the ability to write AVIs! see example-avioutput.pd - added searchpath, see example-searchpath.pd new in fs.frame: - "use <directory>" - like buffer, but no buffering (load on demand) - new popupmenu commands: save image as, undock - mousewheel functions as zoom (shift down to preserve aspect ratio) - fix: borders/stayontop discarded the image - dock <window title> string matching is now substring - window caption shows image resolution http://framestein.org

1 0

Re: [PD] sample looping problem
by mik 24 Feb '02

24 Feb '02

On Sunday 24 February 2002 07:13, you wrote: > That would loop between the beginning and end of the sustain segment, > right? I need it to play the beginning of the sample before entering > the loop. > > Ben Yes, I've been too quick in answering. The frequency of phasor~ isn't right either. Sorry. mik > On Sun, Feb 24, 2002 at 02:13:05AM +0100, mik wrote: > > output phasor~ 1 X length of sustain + beginning of sustain? > > > > mik > > > > On Sunday 24 February 2002 01:25, Ben Saylor wrote: > > > Hello, > > > > > > I am trying to find a way to play the beginning of a sample (attack > > > segment) and then loop the rest indefinitely between two fixed points > > > (sustain segment). For the input to tabread4~, I tried putting a line > > > signal through wrap~ and mapping the output to the correct range, but > > > it didn't work the way I hoped because wrap~ doesn't let negative > > > numbers through. Is there a clean way to do this? > > > > > > Thanks, > > > Ben (Pd newbie)

1 0

Re: [Csnd] [PD] release of csound~ for pd
by Stefan Kersten 24 Feb '02

24 Feb '02

"Matt J. Ingalls" wrote: > csound~ doesnt know, but csound does? i lost track of what i was trying to communicate :) the csound process started by csound~ writes to/reads from fifos as if they were regular soundfiles. i'm not sure how the -L command line flag changes its (csound's) notion of running in 'realtime'. > btw, how is csound~ [pd] sending control signals? > for csound~ [msp] [and maccsound] i created these 'invalue' and > 'outvalue' opcodes for receiving/sending k-rate [float] values. that sounds cool. how do you access the control slots from msp? do they show up as additional inlets/outlets or do you send/receive a message? how does msp transfer the values to the csound process? what we get away with currently is using separate control instruments and sending control changes as score parameters to these, but i guess eventually the OSC opcodes could be reworked and used instead. <sk>

1 0

Re: [Csnd] [PD] release of csound~ for pd
by Stefan Kersten 24 Feb '02

24 Feb '02

"Matt J. Ingalls" wrote: > > > whats the 'noheader' option? > > > > raw output without soundfile header. > > if its real-time then i think any header option or -h is ignored in pd's csound~-object csound doesn't even know it runs in realtime; it just issues its standard blocking reads/writes from/to the supplied fifo-files. therefore the no-header flag is required and a default floating-point output range would really be appreciable; no problem to scale if i know which range to convert from! OTOH, if a 1:1 mapping from orc amplitudes to output amplitudes is defined behavior it's OK, too: then it's up to the user to stick to the desired output range within the orchestra. <sk>

1 1

← Newer
1
2
3
4
5
6
7
8
...
18
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 February 2002