Csound Csound-dev Csound-tekno Search About

[Csnd] file path argument to opcode (Mac)

Date2010-11-27 07:59
FromJim Aikin
Subject[Csnd] file path argument to opcode (Mac)
I've managed to create a hetro analysis file, and now I'm trying to
resynthesize my sample using adsyn. I'm having no luck, and the problem
seems to be that I don't know how to specify the file path as an argument to
the opcode.

I'm using QuteCsound 0.5. I've specified SADIR using the file selector
button in the Environment pane of the Configure window, but that didn't seem
to work, so I tried giving an absolute pathname. Here's the new error
message:

INIT ERROR in instr 1: ADSYN cannot load
Users/jimaikin/CsoundAudio/olive.het

Needless to say, the file olive.het is in that directory, so the problem may
be in how I've specified the path. If I don't specify a full path (which
should cause it to use the SADIR), the error message simply says, "cannot
load olive.het".

Browsing the Table Of Contents for the manual, I find no item that obviously
relates to the question of how one would specify an absolute pathname on the
common operating systems, nor is it obvious to me why giving a relative
pathname shouldn't work; so I'm stuck. Can anyone suggest how to get this to
work?

Thanks!

--Jim Aikin

Date2010-11-27 08:25
FromVictor Lazzarini
Subject[Csnd] Re: file path argument to opcode (Mac)
Looks like you are missing the initial '/'  as in /Users/jimaikin/ 
CsoundAudio/olive.het


On 27 Nov 2010, at 07:59, Jim Aikin wrote:

> INIT ERROR in instr 1: ADSYN cannot load
> Users/jimaikin/CsoundAudio/olive.het



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"

Date2010-11-27 17:17
FromJim Aikin
Subject[Csnd] Re: file path argument to opcode (Mac)
Thanks, Victor. That solved the problem.

I can't help wishing this type of thing were explained somewhere in the
manual, clearly and in detail, with reference to all of the major operating
systems. (Maybe it is, but I couldn't find it when I looked.) Too often, the
assumption of the manual seems to be, "Hey, you're studying computer science
in college -- you already know all this stuff, and if you don't know it yet,
you can ask your instructor."

--JA

Date2010-11-28 13:56
FromAndres Cabrera
Subject[Csnd] Re: Re: file path argument to opcode (Mac)
Hi Jim,

Maybe the manual is not the best place for this, as it is a reference
manual, but it certainly would be good to have it in the FLOSS manual,
which is written more in a tutorial style.

The problem with SFDIR in QuteCsound is a known bug...

Cheers,
Andres

On Sat, Nov 27, 2010 at 5:17 PM, Jim Aikin  wrote:
>
> Thanks, Victor. That solved the problem.
>
> I can't help wishing this type of thing were explained somewhere in the
> manual, clearly and in detail, with reference to all of the major operating
> systems. (Maybe it is, but I couldn't find it when I looked.) Too often, the
> assumption of the manual seems to be, "Hey, you're studying computer science
> in college -- you already know all this stuff, and if you don't know it yet,
> you can ask your instructor."
>
> --JA
> --
> View this message in context: http://csound.1045644.n5.nabble.com/file-path-argument-to-opcode-Mac-tp3282208p3282528.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> 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"


Date2010-11-28 17:06
FromJason Timm
Subject[Csnd] Re: Re: Re: file path argument to opcode (Mac)
Any hints getting csound to see a relative file path? i.e - file is in subfolder of present working dir = /somefolder/file.aif.

I've tried these combinations on Mac: ~/somefolder/file.aif, ./somefolder/file.aif, ../somefolder/file.aif. None work here.

_Jase
 

On Sun, Nov 28, 2010 at 8:56 AM, Andres Cabrera <mantaraya36@gmail.com> wrote:
Hi Jim,

Maybe the manual is not the best place for this, as it is a reference
manual, but it certainly would be good to have it in the FLOSS manual,
which is written more in a tutorial style.

The problem with SFDIR in QuteCsound is a known bug...

Cheers,
Andres

On Sat, Nov 27, 2010 at 5:17 PM, Jim Aikin <midiguru23@sbcglobal.net> wrote:
>
> Thanks, Victor. That solved the problem.
>
> I can't help wishing this type of thing were explained somewhere in the
> manual, clearly and in detail, with reference to all of the major operating
> systems. (Maybe it is, but I couldn't find it when I looked.) Too often, the
> assumption of the manual seems to be, "Hey, you're studying computer science
> in college -- you already know all this stuff, and if you don't know it yet,
> you can ask your instructor."
>
> --JA
> --
> View this message in context: http://csound.1045644.n5.nabble.com/file-path-argument-to-opcode-Mac-tp3282208p3282528.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> 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"



Date2010-11-28 17:12
Fromjpff@cs.bath.ac.uk
Subject[Csnd] Re: Re: Re: Re: file path argument to opcode (Mac)
> Any hints getting csound to see a relative file path? i.e - file is in
> subfolder of present working dir = /somefolder/file.aif.
>
> I've tried these combinations on Mac: ~/somefolder/file.aif,
> ./somefolder/file.aif, ../somefolder/file.aif. None work here.
>
> _Jase
>

Usually not starting with a / makes a file name relatove.

~ is short for /Users/....




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"

Date2010-11-28 17:19
FromVictor Lazzarini
Subject[Csnd] Re: Re: Re: Re: file path argument to opcode (Mac)
../blah/blah  certainly  works (it does here). I expect ./ to do so although that is not that useful. But note that ~ is a shell thing, so
it will not work elsewhere.

Victor


On 28 Nov 2010, at 17:06, Jason Timm wrote:

Any hints getting csound to see a relative file path? i.e - file is in subfolder of present working dir = /somefolder/file.aif.

I've tried these combinations on Mac: ~/somefolder/file.aif, ./somefolder/file.aif, ../somefolder/file.aif. None work here.

_Jase
 

On Sun, Nov 28, 2010 at 8:56 AM, Andres Cabrera <mantaraya36@gmail.com> wrote:
Hi Jim,

Maybe the manual is not the best place for this, as it is a reference
manual, but it certainly would be good to have it in the FLOSS manual,
which is written more in a tutorial style.

The problem with SFDIR in QuteCsound is a known bug...

Cheers,
Andres

On Sat, Nov 27, 2010 at 5:17 PM, Jim Aikin <midiguru23@sbcglobal.net> wrote:
>
> Thanks, Victor. That solved the problem.
>
> I can't help wishing this type of thing were explained somewhere in the
> manual, clearly and in detail, with reference to all of the major operating
> systems. (Maybe it is, but I couldn't find it when I looked.) Too often, the
> assumption of the manual seems to be, "Hey, you're studying computer science
> in college -- you already know all this stuff, and if you don't know it yet,
> you can ask your instructor."
>
> --JA
> --
> View this message in context: http://csound.1045644.n5.nabble.com/file-path-argument-to-opcode-Mac-tp3282208p3282528.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> 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"




Date2010-11-28 17:34
FromJason Timm
Subject[Csnd] Re: Re: Re: Re: Re: file path argument to opcode (Mac)
Attachmentstest.zip  
hm. this doesn't work here.



On Sun, Nov 28, 2010 at 12:19 PM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
../blah/blah  certainly  works (it does here). I expect ./ to do so although that is not that useful. But note that ~ is a shell thing, so
it will not work elsewhere.

Victor



On 28 Nov 2010, at 17:06, Jason Timm wrote:

Any hints getting csound to see a relative file path? i.e - file is in subfolder of present working dir = /somefolder/file.aif.

I've tried these combinations on Mac: ~/somefolder/file.aif, ./somefolder/file.aif, ../somefolder/file.aif. None work here.

_Jase
 

On Sun, Nov 28, 2010 at 8:56 AM, Andres Cabrera <mantaraya36@gmail.com> wrote:
Hi Jim,

Maybe the manual is not the best place for this, as it is a reference
manual, but it certainly would be good to have it in the FLOSS manual,
which is written more in a tutorial style.

The problem with SFDIR in QuteCsound is a known bug...

Cheers,
Andres

On Sat, Nov 27, 2010 at 5:17 PM, Jim Aikin <midiguru23@sbcglobal.net> wrote:
>
> Thanks, Victor. That solved the problem.
>
> I can't help wishing this type of thing were explained somewhere in the
> manual, clearly and in detail, with reference to all of the major operating
> systems. (Maybe it is, but I couldn't find it when I looked.) Too often, the
> assumption of the manual seems to be, "Hey, you're studying computer science
> in college -- you already know all this stuff, and if you don't know it yet,
> you can ask your instructor."
>
> --JA
> --
> View this message in context: http://csound.1045644.n5.nabble.com/file-path-argument-to-opcode-Mac-tp3282208p3282528.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> 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"





Date2010-11-28 17:44
FromVictor Lazzarini
Subject[Csnd] Re: Re: Re: Re: Re: Re: file path argument to opcode (Mac)
If the .. directory is taken to be the parent of the directory where the CSD is, then ../the/path/to/file.wav works.
eg.  the CSD is on the desktop and the file is in /Users/victor/audio/

then ../audio/myfile.wav  does work.

Victor


On 28 Nov 2010, at 17:34, Jason Timm wrote:

hm. this doesn't work here.



On Sun, Nov 28, 2010 at 12:19 PM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
../blah/blah  certainly  works (it does here). I expect ./ to do so although that is not that useful. But note that ~ is a shell thing, so
it will not work elsewhere.

Victor



On 28 Nov 2010, at 17:06, Jason Timm wrote:

Any hints getting csound to see a relative file path? i.e - file is in subfolder of present working dir = /somefolder/file.aif.

I've tried these combinations on Mac: ~/somefolder/file.aif, ./somefolder/file.aif, ../somefolder/file.aif. None work here.

_Jase
 

On Sun, Nov 28, 2010 at 8:56 AM, Andres Cabrera <mantaraya36@gmail.com> wrote:
Hi Jim,

Maybe the manual is not the best place for this, as it is a reference
manual, but it certainly would be good to have it in the FLOSS manual,
which is written more in a tutorial style.

The problem with SFDIR in QuteCsound is a known bug...

Cheers,
Andres

On Sat, Nov 27, 2010 at 5:17 PM, Jim Aikin <midiguru23@sbcglobal.net> wrote:
>
> Thanks, Victor. That solved the problem.
>
> I can't help wishing this type of thing were explained somewhere in the
> manual, clearly and in detail, with reference to all of the major operating
> systems. (Maybe it is, but I couldn't find it when I looked.) Too often, the
> assumption of the manual seems to be, "Hey, you're studying computer science
> in college -- you already know all this stuff, and if you don't know it yet,
> you can ask your instructor."
>
> --JA
> --
> View this message in context: http://csound.1045644.n5.nabble.com/file-path-argument-to-opcode-Mac-tp3282208p3282528.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> 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"




<test.zip>


Date2010-11-28 17:48
FromJason Timm
Subject[Csnd] Re: Re: Re: Re: Re: Re: Re: file path argument to opcode (Mac)
Aha! so "..test/folder/file.wav" in this example works.

many thanks Victor


On Sun, Nov 28, 2010 at 12:44 PM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
If the .. directory is taken to be the parent of the directory where the CSD is, then ../the/path/to/file.wav works.
eg.  the CSD is on the desktop and the file is in /Users/victor/audio/

then ../audio/myfile.wav  does work.

Victor


On 28 Nov 2010, at 17:34, Jason Timm wrote:

hm. this doesn't work here.



On Sun, Nov 28, 2010 at 12:19 PM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
../blah/blah  certainly  works (it does here). I expect ./ to do so although that is not that useful. But note that ~ is a shell thing, so
it will not work elsewhere.

Victor



On 28 Nov 2010, at 17:06, Jason Timm wrote:

Any hints getting csound to see a relative file path? i.e - file is in subfolder of present working dir = /somefolder/file.aif.

I've tried these combinations on Mac: ~/somefolder/file.aif, ./somefolder/file.aif, ../somefolder/file.aif. None work here.

_Jase
 

On Sun, Nov 28, 2010 at 8:56 AM, Andres Cabrera <mantaraya36@gmail.com> wrote:
Hi Jim,

Maybe the manual is not the best place for this, as it is a reference
manual, but it certainly would be good to have it in the FLOSS manual,
which is written more in a tutorial style.

The problem with SFDIR in QuteCsound is a known bug...

Cheers,
Andres

On Sat, Nov 27, 2010 at 5:17 PM, Jim Aikin <midiguru23@sbcglobal.net> wrote:
>
> Thanks, Victor. That solved the problem.
>
> I can't help wishing this type of thing were explained somewhere in the
> manual, clearly and in detail, with reference to all of the major operating
> systems. (Maybe it is, but I couldn't find it when I looked.) Too often, the
> assumption of the manual seems to be, "Hey, you're studying computer science
> in college -- you already know all this stuff, and if you don't know it yet,
> you can ask your instructor."
>
> --JA
> --
> View this message in context: http://csound.1045644.n5.nabble.com/file-path-argument-to-opcode-Mac-tp3282208p3282528.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> 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"




<test.zip>