Hi Miyazaki,
The '-midiindev' and '-midioutdev' are called flags, you put on the
same line on your terminal when you start PD.
But I understand that you use the 'PD.command' file coming from the
Adam' s installer.
This file open the terminal and start pd for you.
If you want to use flag you have two solutions:
-first one: forget that file and familiarise yourself with the terminal.
you can start pd in typing:
[Shintaro-Miyazakis-Computer:~] miyazaki% /usr/local/pd/bin/pd
I know Adam' s installer put the PD directory under local (it could be
somewhere else!)
then you can add flags on the same line like:
[Shintaro-Miyazakis-Computer:~] miyazaki% /usr/local/pd/bin/pd
-midiindev 0,1,2,3,4,5,6 -midioutdev 0,1,2,3,4,5,6 -and_so_on
-the second solution is to add the flags in the .pdrc file (a flag per
line).
pd reads the .pdrc file on start up:
> reading startup file: /Users/miyazaki/.pdrc
On osx this is a invisible file so to access it you must use your
terminal and the command 'pico' which open the file like a text editor:
[Shintaro-Miyazakis-Computer:~] miyazaki% pico /Users/miyazaki/.pdrc
then you can edit the file.
Additionally instead of typing the whole path to pd
(/usr/local/pd/bin/pd).
you can create a file called .tcshrc that your terminal will read on
start up (you have to specify that on your terminal preferences).
In this you will create an alias to pd like that:
alias pd '/usr/local/pd/bin/pd'
According that PD is under /local
Then you can type 'pd' in your terminal to start it up like this:
[Shintaro-Miyazakis-Computer:~] miyazaki% pd
Having said so, I have noticed that you are using PD as a non-root user.
That may become difficult to install externals, to run PD in -rt.
(realtime) and also to have rights on some files.
I advice you to start the PD installation by creating you a root
account.
I strongly advice you to buy the book "MAC OSX the Missing Manual" (O'
Reilly).
It covers the basic command line of Unix. This helped me a lot.
Also have another read of the PD documentation, it is a bit hard at the
beginning but it becomes clearer after a few other reads.
Good Luck.
Alex
> On Thursday, May 22, 2003, at 08:33 pm, Shintaro Miyazaki wrote:
> Hi alex
>
> thank you for helping me out..
> I tried what you said but, nothing happend.
> I mean what is supposed to be to happen?
> I wrote as you can see here midiindev blablabalbalba..
> in the Terminal.
>
> Last login: Thu May 22 20:25:54 on ttyp1
> /Users/miyazaki/Desktop/Pd.command; exit
> Welcome to Darwin!
> [Shintaro-Miyazakis-Computer:~] miyazaki%
> /Users/miyazaki/Desktop/Pd.command; exit
> reading startup file: /Users/miyazaki/.pdrc
> could not open midi input device number 1: Invalid device ID.
> using default input device number: 0
> using default output device number: 1
> nchan 2, flags 3, bufs 8, framesperbuf 256
> -midiindev 0,1,2,3,4,5,6,7,8,9
>
> put msg
> put 1 msg 0 1
> put msg
> put 1 msg 0 1
> put msg
> - mididev 1, 2, 3, 4, 5, 6, 7, 8, 9
> -midiindev 0,1,2,3,4,5,6,7,8,9
> invalid command name "0"
>
> and then I tried if something happens if I play around my keyboard. In
> the testtonepatch.
> nothing happend, maybe I am handling the terminal in a wrong way. Do I
> have to type something other in before typing midiindev bla bla bla?
>
>
> cheers
> miyazaki s
>
> <testtone.pd>
>
>
>
>
> Am Donnerstag, 22.05.03, um 09:12 Uhr (Europe/Zurich) schrieb Alex:
>
>> if your MIDI device is correctly installed and your keyboard plugged
>> into it.
>> You may have to tried some other configurations.
>> Mine is -midiindev 0 -midioutdev 5
>> To find it I did:
>> -midiindev 0,1,2,3,4,5,6,7,8,9 and then I went down until finding the
>> right port number like this:
>> -midiindev 0,1,2,3,4,5,6,7,8
>> -midiindev 0,1,2,3,4,5,6,7
>> and so one. (same with midiout)
>>
>> It may not be a clever way to do it but that is how I did.
>>
>> Hope this helps.
>> Alex
>>
>>
>>
>> On Thursday, May 22, 2003, at 02:36 am, Shintaro Miyazaki wrote:
>>
>>> pd -midiindev 1 -midioutdev 2