Dear PD'lers,
on October 8, I posted to the pd-list und pd-dev list a call for participation in an online survey concerning the dynamics of software development within the PD community. For background on the survey, please check my original message (http://www.iem.at/mailinglists/pd-list/2002-October/000840.html).
By now, already thirty people have filled out the form. This is a very good response rate, thanks a lot to all of those who took the time.
Of course, some more replies would be even better :).
So if you have thought about participating but haven't done it yet, please do so now. It won't take more than a few minutes.
Survey: http://oss.zsi.at login: pdsurvey pw: ppddpdpp
I will leave the survey online for another three days, afterwards I will take it down.
Once I have the survey results available, I will post an short announcment, so that you can see that your time was well invested, I hope :).
If you have any questions regarding this survey, the research project that it is a part of, or anything else, don't hestitate to write me.
grtz. Andrea
Hello PD'lrs
In the past, I've succesfully installed PD on quite a lot of machines. They were running under windows 98, Me, 2000, XP. PD is running even in a Mac, here at home, under MacOS X... Installation of PD was always been very easy, nice, without any problem, MIDI and Audio worked very well. Work with it has been always great and exciting.
This academic year I'm giving a course about musical algorithms... I though that PD could be a good tool, because of its portability... people could try examples at home, etc... But I'm having problems that appear quite randomly...
Machines are 16 Pentium IV at 1,7 GHz and 750 Mb RAM, with an inbuilt audio card, that appears, in system's sound control panel, to be well installed and running without any problem. All of them have the same hardware and software configuration.
After installation of PD, some of them run PD aparently without any inconvenience. Other, after launching PD, when Whish appears, a message is displayed at the log : "I/O stuck... closed audio". When opening the test Audio and MIDI patcher, there is not any activity in audio input... all inputs are set to 0...
I've tryed launching PD with the -audiodev, -audiooutdev, etc.. options without any success!
The most strange thing is that this behaviour is not always followed by the same machines. Sometimes, some of them are working fine and other do not work. After a while, the set of machines working can be a different one than before...
Sometimes, when, after running succesfully for a while, I close PD and restart it again, I get the same message at log! I've tryed disconnecting the ethernet wires to avoid possible conflicts with processes in the net. Anyway, this does not change this strange behaviour...
Sometimes, restarting the system seems to be a solution... But this is not very comfortable! At home, people and myself, all have PD running nicely...At the University, where things should work even better, we are having this rare troubleshouting. Our system administrator does not have any idea about what could be happenning...
Anybody has experienced such a things? Is there any idea on how could we solve this situation?
Best whishes
Jose Manuel
Jose Manuel Berenguer jmbeal@telefonica.net +34932857046 696538403 jmberenguer@cccb.org +34933064128 http://212.163.142.140/jmb/index.html http://sonoscop.cccb.org http://ocaos.cccb.org/caos Sonoscop/Orquesta del Caos. CCCB. Montalegre, 5. 08001 Barcelona. Spain
Hi Jose,
Any idea what chipset or brand of "mainboard"? Maybe someone on the list has something similar. I really want to make it possible for people in situations such as yours to use Pd. If something isn't working I'll certainly try to help. I just have to figure out how to get a machine around here to misbehave in the same way...
cheers Miller
On Thu, Oct 17, 2002 at 02:50:09AM +0200, Jose Manuel Berenguer wrote:
Hello PD'lrs
In the past, I've succesfully installed PD on quite a lot of machines. They were running under windows 98, Me, 2000, XP. PD is running even in a Mac, here at home, under MacOS X... Installation of PD was always been very easy, nice, without any problem, MIDI and Audio worked very well. Work with it has been always great and exciting.
This academic year I'm giving a course about musical algorithms... I though that PD could be a good tool, because of its portability... people could try examples at home, etc... But I'm having problems that appear quite randomly...
Machines are 16 Pentium IV at 1,7 GHz and 750 Mb RAM, with an inbuilt audio card, that appears, in system's sound control panel, to be well installed and running without any problem. All of them have the same hardware and software configuration.
After installation of PD, some of them run PD aparently without any inconvenience. Other, after launching PD, when Whish appears, a message is displayed at the log : "I/O stuck... closed audio". When opening the test Audio and MIDI patcher, there is not any activity in audio input... all inputs are set to 0...
I've tryed launching PD with the -audiodev, -audiooutdev, etc.. options without any success!
The most strange thing is that this behaviour is not always followed by the same machines. Sometimes, some of them are working fine and other do not work. After a while, the set of machines working can be a different one than before...
Sometimes, when, after running succesfully for a while, I close PD and restart it again, I get the same message at log! I've tryed disconnecting the ethernet wires to avoid possible conflicts with processes in the net. Anyway, this does not change this strange behaviour...
Sometimes, restarting the system seems to be a solution... But this is not very comfortable! At home, people and myself, all have PD running nicely...At the University, where things should work even better, we are having this rare troubleshouting. Our system administrator does not have any idea about what could be happenning...
Anybody has experienced such a things? Is there any idea on how could we solve this situation?
Best whishes
Jose Manuel
Jose Manuel Berenguer jmbeal@telefonica.net +34932857046 696538403 jmberenguer@cccb.org +34933064128 http://212.163.142.140/jmb/index.html http://sonoscop.cccb.org http://ocaos.cccb.org/caos Sonoscop/Orquesta del Caos. CCCB. Montalegre, 5. 08001 Barcelona. Spain
PD-list mailing list PD-list@iem.kug.ac.at http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-list
Any idea what chipset or brand of "mainboard"? Maybe someone on the list has something similar.
for me it's a Via Apollo KT266 with a VT8233 Southbridge
as I said (but it only got to Jose), -audiobuf 500 helped the latency sucks of course, but this is only my development box I never ran any tests on how low I could get the buffer size - would that be of interest to you, Miller?
personally, I wouldn't expect good (or even decent) performance from an on-board sound chip - if I were to perform or produce with this machine I would most definitely throw in a quality sound card of course, at universities you have to make compromises...
hello,
Any idea what chipset or brand of "mainboard"? Maybe someone on the list has something similar.
for me it's a Via Apollo KT266 with a VT8233 Southbridge
the chipset is intel D845HV. it seems to run at 1,7 GHz and has quite enough RAM in this computers to allocate heaps and buffers...
operating system is windows2000
the card I was speaking about this mornig is an ethernet AngelCustodios card...
any idea, for now, about the in-built sound chip.
personally, I wouldn't expect good (or even decent) performance from an on-board sound chip - if I were to perform or produce with this machine I would most definitely throw in a quality sound card of course, at universities you have to make compromises...
indeed we must! :))) we have better computer and audio devices at home. i agree with you : i'd never try to produce or give a concert with this. anyway, i believe that to introduce students to PD and computer music, in general, is better this than nothing. if we do not make compromises, people will remain forever on the "trivialities" of manual sound editing and processing. and the worst thing is that they could feel themselves as knowing all that a computer can do in the sound domain! it's a pity that people could thing on computers only as a way to do faster the same things we did before without them.
if you knew about the difficulties i have to be understood by the direction staff when i speak on the necessity of using good sound material !! to have a minimal pro tools system has been a battle, but well, there is a while i'm falling in the off-topic! excuse me, please.
whishes and many thanks
jose manuel
hi all,
so here's a bit of a newbie question: i was just wondering if there was an efficient way of loading audio files live without getting dropouts. i've tried the experimental threaded version of pd 35, as well as using readsf~ to stream audio data from disk into arrays, both of which improve performance somewhat but still cause fairly frequent stutters in the output.
i'm currently running PD on a PIII notebook with a bundled (ESS Maestro sound card (no functional ASIO drivers, so i can't use the -blocksize flag) under Windows 98, audiobuf set to 500 and sleepgrain set to 2, and am using xgroove~ to read the sound tables. any suggestions?
sorry if this has been better covered elsewhere (i looked through the archives, but didn't see anything that was of particular help.)
glyn
On Thu, 17 Oct 2002, Sukandar Kartadinata wrote:
personally, I wouldn't expect good (or even decent) performance from an on-board sound chip - if I were to perform or produce with this machine I would most definitely throw in a quality sound card of course, at universities you have to make compromises...
I'm using the on-board sound-chip on an nforce board. As far as I can see, it has great performance, ~impossible to get anything better. 64 frames latency for jack-applications works quite good. Cant remember my best pd-settings, but it was low.
hi Miller
Hi Jose,
Any idea what chipset or brand of "mainboard"? Maybe someone on the list
finally I know the chipset and soundcard
chip set is -was known yesterday, yet- intel D845HV. soundcard is a SoundMax!
Olaf Matthes said yesterday that this soundcards were "behaving like pure woodoo"...
i believe you are right, Olaf!
don't worry about possible solutions : the department coordinator will switch us to an other classroom with other machines!
perhaps it could be a good idea to make a list of devices, chipsets, cards... that has been shown they are not good enough to run PD... or does this exist yet?
i thank you all very much for your advises and suggestions. i've learned a lot this two days.
jose manuel
-
Andrea Mayr -
glyn -
Jose Manuel Berenguer -
Kjetil S. Matheussen -
Miller Puckette -
Sukandar Kartadinata