hi -

i am wondering if it is in any way possible to get the path/name of the .csd file inside csound? for instance, if the commandline is 'csound /home/jh/fun.csd', can i get in any way '/home/jh/fun.csd' (=argv[1])?

thanks -

        joachim


Send bugs reports to the Sourceforge bug tracker
           https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

do you mean system (which is at k-rate)?
but this can not return a string, and i would not know how to get the csd path from it anyway.
or did i misunderstand you?
thanks -
        joachim


Am 27.07.2012 22:33, schrieb peiman khosravi:

It seems like we could do with a system_k command that (a) returns a
string and (b) starts in the csd directory rather than root.

P

On 27 July 2012 19:53, joachim heintz <jh@joachimheintz.de

<mailto:jh@joachimheintz.de>> wrote:

    hi -

    i am wondering if it is in any way possible to get the path/name of
    the .csd file inside csound? for instance, if the commandline is
    'csound /home/jh/fun.csd', can i get in any way '/home/jh/fun.csd'
    (=argv[1])?

    thanks -

             joachim


    Send bugs reports to the Sourceforge bug tracker

    https://sourceforge.net/__tracker/?group_id=81968&atid=__564599

    <https://sourceforge.net/tracker/?group_id=81968&atid=564599>
    Discussions of bugs and features can be posted here
    To unsubscribe, send email sympa@lists.bath.ac.uk

    <mailto:sympa@lists.bath.ac.uk> with body "unsubscribe csound"

Send bugs reports to the Sourceforge bug tracker
           https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

yes but I meant we should have a modified version of this opcode that can return a string. And currently if you run it with the command 'pwd' it returns '/'. But if there was a way of initiating the system command in the directory of the csd (the same as doing 'cd /whatever/directory/in/which/the/csd/resides') then you could just get the path of the current directory with 'pwd'.

Best,
P

On 27 July 2012 21:49, joachim heintz <jh@joachimheintz.de> wrote:

do you mean system (which is at k-rate)?
but this can not return a string, and i would not know how to get the csd path from it anyway.
or did i misunderstand you?
thanks -
        joachim


Am 27.07.2012 22:33, schrieb peiman khosravi:

It seems like we could do with a system_k command that (a) returns a
string and (b) starts in the csd directory rather than root.

P

On 27 July 2012 19:53, joachim heintz <jh@joachimheintz.de

<mailto:jh@joachimheintz.de>> wrote:

    hi -

    i am wondering if it is in any way possible to get the path/name of
    the .csd file inside csound? for instance, if the commandline is
    'csound /home/jh/fun.csd', can i get in any way '/home/jh/fun.csd'
    (=argv[1])?

    thanks -

             joachim


    Send bugs reports to the Sourceforge bug tracker

    https://sourceforge.net/__tracker/?group_id=81968&atid=__564599

    <https://sourceforge.net/tracker/?group_id=81968&atid=564599>
    Discussions of bugs and features can be posted here
    To unsubscribe, send email sympa@lists.bath.ac.uk

    <mailto:sympa@lists.bath.ac.uk> with body "unsubscribe csound"

Send bugs reports to the Sourceforge bug tracker
           https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hi Joachim,

Another option that may be simpler is passing in the directory as a
macro when calling csound, something like:

csound --omacro:CURRENT_DIR=`pwd` testdir.csd

Running that with this csd:

<CsoundSynthesizer>
<CsInstruments>
sr=44100
ksmps=1
nchnls=2

instr 1
Sdir = "$CURRENT_DIR"
prints "CurrentDir is "
prints Sdir
turnoff
endin

</CsInstruments>
<CsScore>
i1 0 2
</CsScore>
</CsoundSynthesizer>

gives:

CurrentDir is /Users/stevenyi

(Note the embedding of the $CURRENT_DIR within quotes)

It's a workaround, but should work without problems until a pwd opcode is done.

Hope that helps!
steven

On Fri, Jul 27, 2012 at 4:59 PM, peiman khosravi
<peimankhosravi@gmail.com> wrote:
> there is one way around this if you're running from the terminal. Make a
> little script that you can call with an argument, which in turn calls csound
> with the csd path as a macro.
>
> See if I can make an example in a min.
>
> P
>
> On 27 July 2012 21:54, peiman khosravi <peimankhosravi@gmail.com> wrote:
>>
>> yes but I meant we should have a modified version of this opcode that can
>> return a string. And currently if you run it with the command 'pwd' it
>> returns '/'. But if there was a way of initiating the system command in the
>> directory of the csd (the same as doing 'cd
>> /whatever/directory/in/which/the/csd/resides') then you could just get the
>> path of the current directory with 'pwd'.
>>
>> Best,
>> P
>>
>> On 27 July 2012 21:49, joachim heintz <jh@joachimheintz.de> wrote:
>>>
>>> do you mean system (which is at k-rate)?
>>> but this can not return a string, and i would not know how to get the csd
>>> path from it anyway.
>>> or did i misunderstand you?
>>> thanks -
>>>         joachim
>>>
>>>
>>> Am 27.07.2012 22:33, schrieb peiman khosravi:
>>>>
>>>> It seems like we could do with a system_k command that (a) returns a
>>>> string and (b) starts in the csd directory rather than root.
>>>>
>>>> P
>>>>
>>>> On 27 July 2012 19:53, joachim heintz <jh@joachimheintz.de
>>>> <mailto:jh@joachimheintz.de>> wrote:
>>>>
>>>>     hi -
>>>>
>>>>     i am wondering if it is in any way possible to get the path/name of
>>>>     the .csd file inside csound? for instance, if the commandline is
>>>>     'csound /home/jh/fun.csd', can i get in any way '/home/jh/fun.csd'
>>>>     (=argv[1])?
>>>>
>>>>     thanks -
>>>>
>>>>              joachim
>>>>
>>>>
>>>>     Send bugs reports to the Sourceforge bug tracker
>>>>     https://sourceforge.net/__tracker/?group_id=81968&atid=__564599
>>>>
>>>>     <https://sourceforge.net/tracker/?group_id=81968&atid=564599>
>>>>     Discussions of bugs and features can be posted here
>>>>     To unsubscribe, send email sympa@lists.bath.ac.uk
>>>>     <mailto:sympa@lists.bath.ac.uk> with body "unsubscribe csound"
>>>>
>>>>
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I came up with this.

Put the script anywhere on your path then run it like this:

runCSD test.csd (full path if you like but not necessary)

Below is the content of the attached script. First you get the full path of the csd using $PWD/"$argv[1]" then give this to csound to define a macro.


#!/bin/csh

set CSDpath = $PWD/"$argv[1]"

csound -odac --omacro:PATH="$CSDpath" "$argv[1]"


And test CSD.

<CsoundSynthesizer>

<CsOptions>
-odac -d
</CsOptions>



<CsInstruments>


sr     = 96000
ksmps  = 100
nchnls = 6
0dbfs  = 1



instr 1
Spath    = "$PATH"
printf_i "'%s'", 1, Spath
endin

</CsInstruments>


<CsScore>
f1 0 4096 10 1
i1 0 1
</CsScore>


</CsoundSynthesizer>

Best,
P

On 27 July 2012 22:18, Steven Yi <stevenyi@gmail.com> wrote:

Hi Joachim,

Another option that may be simpler is passing in the directory as a
macro when calling csound, something like:

csound --omacro:CURRENT_DIR=`pwd` testdir.csd

Running that with this csd:

<CsoundSynthesizer>
<CsInstruments>
sr=44100
ksmps=1
nchnls=2

instr 1
Sdir = "$CURRENT_DIR"
prints "CurrentDir is "
prints Sdir
turnoff
endin

</CsInstruments>
<CsScore>
i1 0 2
</CsScore>
</CsoundSynthesizer>

gives:

CurrentDir is /Users/stevenyi

(Note the embedding of the $CURRENT_DIR within quotes)

It's a workaround, but should work without problems until a pwd opcode is done.

Hope that helps!
steven

On Fri, Jul 27, 2012 at 4:59 PM, peiman khosravi
<peimankhosravi@gmail.com> wrote:
> there is one way around this if you're running from the terminal. Make a
> little script that you can call with an argument, which in turn calls csound
> with the csd path as a macro.
>
> See if I can make an example in a min.
>
> P
>
> On 27 July 2012 21:54, peiman khosravi <peimankhosravi@gmail.com> wrote:
>>
>> yes but I meant we should have a modified version of this opcode that can
>> return a string. And currently if you run it with the command 'pwd' it
>> returns '/'. But if there was a way of initiating the system command in the
>> directory of the csd (the same as doing 'cd
>> /whatever/directory/in/which/the/csd/resides') then you could just get the
>> path of the current directory with 'pwd'.
>>
>> Best,
>> P
>>
>> On 27 July 2012 21:49, joachim heintz <jh@joachimheintz.de> wrote:
>>>
>>> do you mean system (which is at k-rate)?
>>> but this can not return a string, and i would not know how to get the csd
>>> path from it anyway.
>>> or did i misunderstand you?
>>> thanks -
>>>         joachim
>>>
>>>
>>> Am 27.07.2012 22:33, schrieb peiman khosravi:
>>>>
>>>> It seems like we could do with a system_k command that (a) returns a
>>>> string and (b) starts in the csd directory rather than root.
>>>>
>>>> P
>>>>
>>>> On 27 July 2012 19:53, joachim heintz <jh@joachimheintz.de
>>>> <mailto:jh@joachimheintz.de>> wrote:
>>>>
>>>>     hi -
>>>>
>>>>     i am wondering if it is in any way possible to get the path/name of
>>>>     the .csd file inside csound? for instance, if the commandline is
>>>>     'csound /home/jh/fun.csd', can i get in any way '/home/jh/fun.csd'
>>>>     (=argv[1])?
>>>>
>>>>     thanks -
>>>>
>>>>              joachim
>>>>
>>>>
>>>>     Send bugs reports to the Sourceforge bug tracker
>>>>     https://sourceforge.net/__tracker/?group_id=81968&atid=__564599
>>>>
>>>>     <https://sourceforge.net/tracker/?group_id=81968&atid=564599>
>>>>     Discussions of bugs and features can be posted here
>>>>     To unsubscribe, send email sympa@lists.bath.ac.uk
>>>>     <mailto:sympa@lists.bath.ac.uk> with body "unsubscribe csound"
>>>>
>>>>
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Of course you can change the csound command in the script to whatever you like.

P

On 27 July 2012 22:41, peiman khosravi <peimankhosravi@gmail.com> wrote:

I came up with this.

Put the script anywhere on your path then run it like this:

runCSD test.csd (full path if you like but not necessary)

Below is the content of the attached script. First you get the full path of the csd using $PWD/"$argv[1]" then give this to csound to define a macro.


#!/bin/csh

set CSDpath = $PWD/"$argv[1]"

csound -odac --omacro:PATH="$CSDpath" "$argv[1]"


And test CSD.

<CsoundSynthesizer>

<CsOptions>
-odac -d
</CsOptions>



<CsInstruments>


sr     = 96000
ksmps  = 100
nchnls = 6
0dbfs  = 1



instr 1
Spath    = "$PATH"
printf_i "'%s'", 1, Spath
endin

</CsInstruments>


<CsScore>
f1 0 4096 10 1
i1 0 1
</CsScore>


</CsoundSynthesizer>

Best,
P

On 27 July 2012 22:18, Steven Yi <stevenyi@gmail.com> wrote:

Hi Joachim,

Another option that may be simpler is passing in the directory as a
macro when calling csound, something like:

csound --omacro:CURRENT_DIR=`pwd` testdir.csd

Running that with this csd:

<CsoundSynthesizer>
<CsInstruments>
sr=44100
ksmps=1
nchnls=2

instr 1
Sdir = "$CURRENT_DIR"
prints "CurrentDir is "
prints Sdir
turnoff
endin

</CsInstruments>
<CsScore>
i1 0 2
</CsScore>
</CsoundSynthesizer>

gives:

CurrentDir is /Users/stevenyi

(Note the embedding of the $CURRENT_DIR within quotes)

It's a workaround, but should work without problems until a pwd opcode is done.

Hope that helps!
steven

On Fri, Jul 27, 2012 at 4:59 PM, peiman khosravi
<peimankhosravi@gmail.com> wrote:
> there is one way around this if you're running from the terminal. Make a
> little script that you can call with an argument, which in turn calls csound
> with the csd path as a macro.
>
> See if I can make an example in a min.
>
> P
>
> On 27 July 2012 21:54, peiman khosravi <peimankhosravi@gmail.com> wrote:
>>
>> yes but I meant we should have a modified version of this opcode that can
>> return a string. And currently if you run it with the command 'pwd' it
>> returns '/'. But if there was a way of initiating the system command in the
>> directory of the csd (the same as doing 'cd
>> /whatever/directory/in/which/the/csd/resides') then you could just get the
>> path of the current directory with 'pwd'.
>>
>> Best,
>> P
>>
>> On 27 July 2012 21:49, joachim heintz <jh@joachimheintz.de> wrote:
>>>
>>> do you mean system (which is at k-rate)?
>>> but this can not return a string, and i would not know how to get the csd
>>> path from it anyway.
>>> or did i misunderstand you?
>>> thanks -
>>>         joachim
>>>
>>>
>>> Am 27.07.2012 22:33, schrieb peiman khosravi:
>>>>
>>>> It seems like we could do with a system_k command that (a) returns a
>>>> string and (b) starts in the csd directory rather than root.
>>>>
>>>> P
>>>>
>>>> On 27 July 2012 19:53, joachim heintz <jh@joachimheintz.de
>>>> <mailto:jh@joachimheintz.de>> wrote:
>>>>
>>>>     hi -
>>>>
>>>>     i am wondering if it is in any way possible to get the path/name of
>>>>     the .csd file inside csound? for instance, if the commandline is
>>>>     'csound /home/jh/fun.csd', can i get in any way '/home/jh/fun.csd'
>>>>     (=argv[1])?
>>>>
>>>>     thanks -
>>>>
>>>>              joachim
>>>>
>>>>
>>>>     Send bugs reports to the Sourceforge bug tracker
>>>>     https://sourceforge.net/__tracker/?group_id=81968&atid=__564599
>>>>
>>>>     <https://sourceforge.net/tracker/?group_id=81968&atid=564599>
>>>>     Discussions of bugs and features can be posted here
>>>>     To unsubscribe, send email sympa@lists.bath.ac.uk
>>>>     <mailto:sympa@lists.bath.ac.uk> with body "unsubscribe csound"
>>>>
>>>>
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Ah, I actually missed that part in your email that you mentioned
omacro!  So we had the same  thought at the same time. :P  Your script
has some nice things, as using `pwd` will only work if run in the same
dir as the CSD.  I guess another solution might be to create a shell
script, something like:

#!/bin/sh
csound --omacro:CURRENT_DIR=`pwd` myProject.csd


and just call it runMyProject.sh.  That way, you could probably double
click it, or symlink it into the PATH, or wherever, and could use that
as a way to run the project with all the settings and things done.
Either way, some not so bad workaround options! :D

On Fri, Jul 27, 2012 at 5:45 PM, peiman khosravi

<peimankhosravi@gmail.com> wrote:
> But Steven's solution is far more elegant!
>
> P
>
>
> On 27 July 2012 22:42, peiman khosravi <peimankhosravi@gmail.com> wrote:
>>
>> Of course you can change the csound command in the script to whatever you
>> like.
>>
>> P
>>
>> On 27 July 2012 22:41, peiman khosravi <peimankhosravi@gmail.com> wrote:
>>>
>>> I came up with this.
>>>
>>> Put the script anywhere on your path then run it like this:
>>>
>>> runCSD test.csd (full path if you like but not necessary)
>>>
>>> Below is the content of the attached script. First you get the full path
>>> of the csd using $PWD/"$argv[1]" then give this to csound to define a macro.
>>>
>>>
>>> #!/bin/csh
>>>
>>> set CSDpath = $PWD/"$argv[1]"
>>>
>>> csound -odac --omacro:PATH="$CSDpath" "$argv[1]"
>>>
>>>
>>> And test CSD.
>>>
>>> <CsoundSynthesizer>
>>>
>>> <CsOptions>
>>> -odac -d
>>> </CsOptions>
>>>
>>>
>>>
>>> <CsInstruments>
>>>
>>>
>>> sr     = 96000
>>> ksmps  = 100
>>> nchnls = 6
>>> 0dbfs  = 1
>>>
>>>
>>>
>>> instr 1
>>> Spath    = "$PATH"
>>> printf_i "'%s'", 1, Spath
>>> endin
>>>
>>> </CsInstruments>
>>>
>>>
>>> <CsScore>
>>> f1 0 4096 10 1
>>> i1 0 1
>>> </CsScore>
>>>
>>>
>>> </CsoundSynthesizer>
>>>
>>> Best,
>>> P
>>>
>>>
>>>
>>>
>>>
>>> On 27 July 2012 22:18, Steven Yi <stevenyi@gmail.com> wrote:
>>>>
>>>> Hi Joachim,
>>>>
>>>> Another option that may be simpler is passing in the directory as a
>>>> macro when calling csound, something like:
>>>>
>>>> csound --omacro:CURRENT_DIR=`pwd` testdir.csd
>>>>
>>>> Running that with this csd:
>>>>
>>>> <CsoundSynthesizer>
>>>> <CsInstruments>
>>>> sr=44100
>>>> ksmps=1
>>>> nchnls=2
>>>>
>>>> instr 1
>>>> Sdir = "$CURRENT_DIR"
>>>> prints "CurrentDir is "
>>>> prints Sdir
>>>> turnoff
>>>> endin
>>>>
>>>> </CsInstruments>
>>>> <CsScore>
>>>> i1 0 2
>>>> </CsScore>
>>>> </CsoundSynthesizer>
>>>>
>>>> gives:
>>>>
>>>> CurrentDir is /Users/stevenyi
>>>>
>>>> (Note the embedding of the $CURRENT_DIR within quotes)
>>>>
>>>> It's a workaround, but should work without problems until a pwd opcode
>>>> is done.
>>>>
>>>> Hope that helps!
>>>> steven
>>>>
>>>> On Fri, Jul 27, 2012 at 4:59 PM, peiman khosravi
>>>> <peimankhosravi@gmail.com> wrote:
>>>> > there is one way around this if you're running from the terminal. Make
>>>> > a
>>>> > little script that you can call with an argument, which in turn calls
>>>> > csound
>>>> > with the csd path as a macro.
>>>> >
>>>> > See if I can make an example in a min.
>>>> >
>>>> > P
>>>> >
>>>> > On 27 July 2012 21:54, peiman khosravi <peimankhosravi@gmail.com>
>>>> > wrote:
>>>> >>
>>>> >> yes but I meant we should have a modified version of this opcode that
>>>> >> can
>>>> >> return a string. And currently if you run it with the command 'pwd'
>>>> >> it
>>>> >> returns '/'. But if there was a way of initiating the system command
>>>> >> in the
>>>> >> directory of the csd (the same as doing 'cd
>>>> >> /whatever/directory/in/which/the/csd/resides') then you could just
>>>> >> get the
>>>> >> path of the current directory with 'pwd'.
>>>> >>
>>>> >> Best,
>>>> >> P
>>>> >>
>>>> >> On 27 July 2012 21:49, joachim heintz <jh@joachimheintz.de> wrote:
>>>> >>>
>>>> >>> do you mean system (which is at k-rate)?
>>>> >>> but this can not return a string, and i would not know how to get
>>>> >>> the csd
>>>> >>> path from it anyway.
>>>> >>> or did i misunderstand you?
>>>> >>> thanks -
>>>> >>>         joachim
>>>> >>>
>>>> >>>
>>>> >>> Am 27.07.2012 22:33, schrieb peiman khosravi:
>>>> >>>>
>>>> >>>> It seems like we could do with a system_k command that (a) returns
>>>> >>>> a
>>>> >>>> string and (b) starts in the csd directory rather than root.
>>>> >>>>
>>>> >>>> P
>>>> >>>>
>>>> >>>> On 27 July 2012 19:53, joachim heintz <jh@joachimheintz.de
>>>> >>>> <mailto:jh@joachimheintz.de>> wrote:
>>>> >>>>
>>>> >>>>     hi -
>>>> >>>>
>>>> >>>>     i am wondering if it is in any way possible to get the
>>>> >>>> path/name of
>>>> >>>>     the .csd file inside csound? for instance, if the commandline
>>>> >>>> is
>>>> >>>>     'csound /home/jh/fun.csd', can i get in any way
>>>> >>>> '/home/jh/fun.csd'
>>>> >>>>     (=argv[1])?
>>>> >>>>
>>>> >>>>     thanks -
>>>> >>>>
>>>> >>>>              joachim
>>>> >>>>
>>>> >>>>
>>>> >>>>     Send bugs reports to the Sourceforge bug tracker
>>>> >>>>     https://sourceforge.net/__tracker/?group_id=81968&atid=__564599
>>>> >>>>
>>>> >>>>     <https://sourceforge.net/tracker/?group_id=81968&atid=564599>
>>>> >>>>     Discussions of bugs and features can be posted here
>>>> >>>>     To unsubscribe, send email sympa@lists.bath.ac.uk
>>>> >>>>     <mailto:sympa@lists.bath.ac.uk> with body "unsubscribe csound"
>>>> >>>>
>>>> >>>>
>>>> >>>
>>>> >>>
>>>> >>> Send bugs reports to the Sourceforge bug tracker
>>>> >>>
>>>> >>> https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> >>> Discussions of bugs and features can be posted here
>>>> >>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>> >>> "unsubscribe
>>>> >>> csound"
>>>> >>>
>>>> >>
>>>> >
>>>>
>>>>
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>> csound"
>>>>
>>>
>>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"