hi again,
i still cannot get this to fly . . . . i will be soooooooooo happy when i can figure out why or what :
error parsing RC arguments is . .
any ideas . . . anyone . . . . at all . . . . 2 days / no pd !!!
i am almost ready to weep uncontrollably.
if the .pdrc is obsolete how can i stop pd from looking for it?
then again, if finding it is not the issue [as suggested] but parsing is . . . how can i parse ? i am dying to parse !!!!
i tried starting from scratch and i still get this same #%$! message.
thanks,
. zehn
what kind of text editor are you using, because maybe the linefeed/carriage return character isnt what PD is expecting?
try -lib zexy on one line only, and see if it will parse that ok, and keep adding lines until you can find at what point the error is?
if you delete your ~/.pdrc, do you still get the error?
what if you have it, but its empty?
good luck!
On Feb 15, 2005, at 4:44 PM, .°·' ±
.° '· wrote:
hi again,
i still cannot get this to fly . . . . i will be soooooooooo happy when i can figure out why or what :
error parsing RC arguments is . .
any ideas . . . anyone . . . . at all . . . . 2 days / no pd !!!
i am almost ready to weep uncontrollably.
if the .pdrc is obsolete how can i stop pd from looking for it?
then again, if finding it is not the issue [as suggested] but parsing is . . . how can i parse ? i am dying to parse !!!!
i tried starting from scratch and i still get this same #%$! message.
thanks,
. zehn
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://iem.at/cgi-bin/mailman/listinfo/pd-list
vade Geschrieben hat . :: . ::: : .
if you delete your ~/.pdrc, do you still get the error?
no, error is gone . . . but no audio. it's a start though . .
before a go deeper, i can pretty much avoid the pdrc altogether at this point right? or, do i need to find a way to get it back into the mix?
thanks,
. z
hi again,
i still would like to know from an expert [or non-expert but "in-the-know"] whether i could permanently leave out .pdrc.
but, anyone using digi002 + Pd?
i just got one and the Pd-0.38-0test4HCS1 build is new to me. i guess i'm trying to go about establishing my audio device but it seems i am getting the error :
error number -9997 occured opening portaudio stream error message : invalid device ID
i was getting this even with the .pdrc in the mix.
admittedly, i feel like a cat chasing his tail because i took too much for granted my old Pd set-up which seemed quite problem free from this perspective.
the 0.38 has the audio preference but i don't see any options. i feel like i've exhausted this as well and am equally stumped. when trying to determine my audiodevices i get :
using default input device number : -1 using default output device number : -1
error message invalid device ID.
i used os9.22 prior except for Pd, so i may be missing something very obvious.
i apologize for my less than exciting contributions to the list, but i promise i will make up for it . . . . i promise!
thanks,
zehn
try running PD with -listdev and then setting the appropriate device number that it detects from the digi002
are other apps able to see the digi002 with out a problem?
On Feb 15, 2005, at 8:44 PM, .°·' ±
.° '· wrote:
i just got one and the Pd-0.38-0test4HCS1 build is new to me. i guess i'm trying to go about establishing my audio device but it seems i am getting the error :
vade Geschrieben hat . :: . ::: : .
try running PD with -listdev and then setting the appropriate device number that it detects from the digi002
ok . . . now, i am getting somewhere! i've got :
input device 0, channels 2 output device 3, channels 2
and sound "built-in" audio sound!!
now, why doesn't it recognize the digi002 +?
i'm working on this but open to suggestions :]
are other apps able to see the digi002 with out a problem?
absolutely seeeeeemlessly. except, digi doesn't like more than one device open at a time which seems strange. with my motu828 i could have everything my memory could support simultaneously, the manual says this is the case . . . . one device only . . weird. no?
. z