Hello. I have been having difficulty using wav files in PD generated from cakewalk and cubase. Always the same message: "can't read past header"...or something similar, then it pukes. I recall that this didn't happen with earlier versions of PD (.32, .33), and that the release notes for .34 mention that an improvement was made to read audio file headers more accurately (?). Related issue? Anyone else have this problem? Platform is WinME and Win2k.
-Ben Sommer
hi,
that very well might be the ``chunk skipping syndrome'', discussed many times here already...
Could you send a very short (like few ms of sound), yet offending sample to my private address? Try not to send it to pd-list, please.
Krzysztof
Ben Sommer wrote:
Hello. I have been having difficulty using wav files in PD generated from cakewalk and cubase. Always the same message: "can't read past header"...or something similar, then it pukes. I recall that
Could you send me (NOT the list) a very short soundfile Pd isn't opening? I've adopted Krzysztof's changes which might improve things but I can't test it without having some of the offending soundfiles...
(and could someone send me a floating-point WAVE file too? and a wave file with a non-12-byte header? thanks...)
cheers Miller
On Wed, Jan 30, 2002 at 08:05:02AM -0500, Ben Sommer wrote:
Hello. I have been having difficulty using wav files in PD generated from cakewalk and cubase. Always the same message: "can't read past header"...or something similar, then it pukes. I recall that this didn't happen with earlier versions of PD (.32, .33), and that the release notes for .34 mention that an improvement was made to read audio file headers more accurately (?). Related issue? Anyone else have this problem? Platform is WinME and Win2k.
-Ben Sommer
What kind of soundcard are you using Ben? I have found on several occaisons that a file recorded using my soundcards recorder will have a bad header for pd. I have had to open the file in Soundforge and simply save it again as 16 bit PCM .wav for it to be read. Could be a soundblaster thing
Cheers Pat
Hello all
I was hoping someone can summarize the state of affairs of multichannel io in pd? under what circumstances is it possible? I am using a creamware pulsar as my soundcard which allows me various types of multichannel io setups, including mme and directsound (and asio of course but i understand that is not currently supported), but none of them seem to work. Why does pd have the option to specify the dac # if it cany only support two channels? When I do a pd -listdev, I see four creamware ins and outs - how do i access these babies?
thanks much!
josh w. hampshire college jwhiting@hampshire.edu
Josh Whiting hat gesagt: // Josh Whiting wrote:
I was hoping someone can summarize the state of affairs of multichannel io in pd? under what circumstances is it possible? I am using a creamware pulsar as my soundcard which allows me various types of multichannel io setups, including mme and directsound (and asio of course but i understand that is not currently supported), but none of them seem to work. Why does pd have the option to specify the dac # if it cany only support two channels? When I do a pd -listdev, I see four creamware ins and outs - how do i access these babies?
Here (linux) this does work, if I simply tell the dac~ which channels to use, say I use [dac~ 1 2 3 4], then I get four inlets for each channel, that I can send signals to. But maybe your Creamware is treated as two soundcards by the OS. Then you should activate it with -soundindev. Or you could try the option "-outchannels 4" to force PD into realizing it has 4 output channels.
bye,
__ __
Frank Barknecht ____ ______ ____ __ trip\ \ / /wire ______
/ __// __ /__/ __// // __ \ / / __ \ ___\
/ / / ____/ / / / // ____// /\ \ ___\____ \
/_/ /_____/ /_/ /_//_____// / \ \_____\_____
/_/ _\
If Windows-PD has to use more than 1 stereo I/O the ins and outs must be visible to Windows in the Control Panel -> Multi Media as a Windows sound device (so, no ASIO). Then it is normally just a matter of specifying the number of I/O at PD start. I have a feeling though that Windows-PD is compiled for two channel I/O only (perhaps 4 but I am sure that someone will set me straigh on this). On Linux/Irix it normally just takes a recompile to make PD "see" the number of I/Os. Same thing for the Windows version, I think.
If PD is ready to run with 4 ouputs you just type:
"PD -outchannels 4"
PD will then use the first 4 outputs.
The dacs will then be accessible as "dac~ 1", "dac~ 2" and so forth. (Remember space between ~ and dac number).
More info in the html documentation (in your PD dir).
HTH Soeren
I was hoping someone can summarize the state of affairs of multichannel io in pd? under what circumstances is it possible? I am using a creamware pulsar as my soundcard which allows me various types of multichannel io setups, including mme and directsound (and asio of course but i understand that is not currently supported), but none of them seem to work. Why does pd have the option to specify the dac # if it cany only support two channels? When I do a pd -listdev, I see four creamware ins and outs -
how
do i access these babies?
Søren Bovbjerg schrieb:
I have a feeling though that Windows-PD is compiled for two channel I/O only (perhaps 4 but I am sure that someone will set me straigh on this).
I used pd (0.34 I think) with 4 channels under WinNT (using two different soundcards!). The -outchannels 4 setting works and makes pd open the device specified with "-soundoutdev n" and additionaly device n+1. My only problem was that I wanted to open n and n+2 which does not work. Changing the order of devices in the control pannel can help... Btw. what's about "-soundoutdev 1,3", I think this is already possible with midi devices unter linux. This would help to use exactly the devices one wants to use.
Olaf
PS: my font-size-8-crash on w2k is fixed in 0.35-test8, thanks....
devices in the control pannel can help... Btw. what's about "-soundoutdev 1,3", I think this is already possible with midi devices unter linux. This would help to use exactly the devices one wants to use.
the -soundoutdev 1,3 should work on linux (as with pd-0.35-4; i don't know about the newer versions) not only for midi but for audio too.
i do not think, that this feature is supported under windos...
... I'll throw taht on the lo-list...
Btw. what's about "-soundoutdev 1,3", I think this is already possible with midi devices unter linux. This would help to use exactly the devices one wants to use.
Olaf
PS: my font-size-8-crash on w2k is fixed in 0.35-test8, thanks....
Glad to hear it...
cheers Miller
-
Ben Sommer -
Frank Barknecht -
IOhannes m zmoelnig -
Josh Whiting -
Krzysztof Czaja -
Miller Puckette -
Olaf Matthes -
ppagano＠bellsouth.net -
Søren Bovbjerg