I had to reinstall Csound on my OS X 10.5.8 machine. The verion of Csound is
5.13 float.
Now when I push the run button in QuteCsound 0.6.0, I get many errors, like:

WARNING: not loading 'libambicode1.dylib' (incompatible with this version of
Csound (2.5/2.4)
WARNING: not loading 'libbabo.dylib' (incompatible with this version of
Csound (2.5/2.4)
WARNING: not loading 'libbarmodel.dylib' (incompatible with this version of
Csound (2.5/2.4)
WARNING: not loading 'libcompress.dylib' (incompatible with this version of
Csound (2.5/2.4)

Only when I press 'Run in Term' I get normal output.

What could this be?


Richard 

--
View this message in context: http://csound.1045644.n5.nabble.com/QuteCsound-behaviour-after-Csound-re-install-tp4897011p4897011.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"

What was the version that you had before 5.13? The errors indicate  
that plugin libraries csound is trying to load
are not compatible. This can happen if you have for some reason an old  
version lying around or the OPCODERDIR
environment variable is pointing to the wrong directory.

(By the way on OSX, there are no distinct  'float' and 'double'  
installers. Both frameworks are installed.
Qutecsound 0.6 uses the float one, but the doubles is also there.)

Victor

On 12 Oct 2011, at 22:19, zappfinger wrote:

> I had to reinstall Csound on my OS X 10.5.8 machine. The verion of  
> Csound is
> 5.13 float.
> Now when I push the run button in QuteCsound 0.6.0, I get many  
> errors, like:
>
> WARNING: not loading 'libambicode1.dylib' (incompatible with this  
> version of
> Csound (2.5/2.4)
> WARNING: not loading 'libbabo.dylib' (incompatible with this version  
> of
> Csound (2.5/2.4)
> WARNING: not loading 'libbarmodel.dylib' (incompatible with this  
> version of
> Csound (2.5/2.4)
> WARNING: not loading 'libcompress.dylib' (incompatible with this  
> version of
> Csound (2.5/2.4)
>
> Only when I press 'Run in Term' I get normal output.
>
> What could this be?
>
>
> Richard
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/QuteCsound-behaviour-after-Csound-re-install-tp4897011p4897011.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"
>

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie





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 do not know what version of Csound I had before..

Are you sure about the environment variable?
I tried displaying it and typed both:

echo $OPCODERDIR and
echo $OPCODEDIR

but they were empty (non existing)

Richard



--
View this message in context: http://csound.1045644.n5.nabble.com/QuteCsound-behaviour-after-Csound-re-install-tp4897011p4897263.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"

do you have a file called environment.plist in the .MacOSX directory  
(in the home dir), check with:

$ ls ~/.MacOSX/environment.plist

see what it contains, the OPCODEDIR could be set there.

Otherwise, did you install the QuteCsound that comes with the csound  
installation package?

I know there is a version of QuteCsound in their website that has  
csound included in. This could be another possibility.

What do you have in your /Library/Frameworks directory? You should  
have CsoundLib.framework and CsoundLib64.framework there.

Also check the version of Csound that prints in the console as you try  
to run it.

Victor
On 12 Oct 2011, at 23:20, zappfinger wrote:

> I do not know what version of Csound I had before..
>
> Are you sure about the environment variable?
> I tried displaying it and typed both:
>
> echo $OPCODERDIR and
> echo $OPCODEDIR
>
> but they were empty (non existing)
>
> Richard
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/QuteCsound-behaviour-after-Csound-re-install-tp4897011p4897263.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"
>

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie





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"

Well, aparantly I do not have the .MacOSX hidden folder.

But I did find the environment variables in QuteCsound, but they are all
empty.

What should the OPCODERDIR contain, where should it point to?

I will consider the other option of Csound included as well.

Richard

--
View this message in context: http://csound.1045644.n5.nabble.com/QuteCsound-behaviour-after-Csound-re-install-tp4897011p4899949.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"

Opcodedir should point to
/Library/Frameworks/CsoundLib.framework/Resources/Opcodes

On 13 Oct 2011, at 18:25, zappfinger wrote:

> Well, aparantly I do not have the .MacOSX hidden folder.
>
> But I did find the environment variables in QuteCsound, but they are  
> all
> empty.
>
> What should the OPCODERDIR contain, where should it point to?
>
> I will consider the other option of Csound included as well.
>
> Richard
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/QuteCsound-behaviour-after-Csound-re-install-tp4897011p4899949.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"
>

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie





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, one note, for OSX, if no OPCODEDIR or OPCODEDIR64 is set, it
should default (hardcoded into the binary) to
/Library/Frameworks/CsoundLib.framework/Resources/Opcodes and
/Library/Frameworks/CsoundLib64.framework/Resources/Opcodes64.  It
might be the case that there is neither set and the default location
is being used.

Hope that helps!
steven


On Thu, Oct 13, 2011 at 10:09 PM, Victor Lazzarini
 wrote:
> Opcodedir should point to
> /Library/Frameworks/CsoundLib.framework/Resources/Opcodes
>
> On 13 Oct 2011, at 18:25, zappfinger wrote:
>
>> Well, aparantly I do not have the .MacOSX hidden folder.
>>
>> But I did find the environment variables in QuteCsound, but they are all
>> empty.
>>
>> What should the OPCODERDIR contain, where should it point to?
>>
>> I will consider the other option of Csound included as well.
>>
>> Richard
>>
>> --
>> View this message in context:
>> http://csound.1045644.n5.nabble.com/QuteCsound-behaviour-after-Csound-re-install-tp4897011p4899949.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"
>>
>
> Dr Victor Lazzarini
> Senior Lecturer
> Dept. of Music
> NUI Maynooth Ireland
> tel.: +353 1 708 3545
> Victor dot Lazzarini AT nuim dot ie
>
>
>
>
>
> 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"

yes, that is right.
On 13 Oct 2011, at 22:17, Steven Yi wrote:

> Ah, one note, for OSX, if no OPCODEDIR or OPCODEDIR64 is set, it
> should default (hardcoded into the binary) to
> /Library/Frameworks/CsoundLib.framework/Resources/Opcodes and
> /Library/Frameworks/CsoundLib64.framework/Resources/Opcodes64.  It
> might be the case that there is neither set and the default location
> is being used.
>
> Hope that helps!
> steven
>
>
> On Thu, Oct 13, 2011 at 10:09 PM, Victor Lazzarini
>  wrote:
>> Opcodedir should point to
>> /Library/Frameworks/CsoundLib.framework/Resources/Opcodes
>>
>> On 13 Oct 2011, at 18:25, zappfinger wrote:
>>
>>> Well, aparantly I do not have the .MacOSX hidden folder.
>>>
>>> But I did find the environment variables in QuteCsound, but they  
>>> are all
>>> empty.
>>>
>>> What should the OPCODERDIR contain, where should it point to?
>>>
>>> I will consider the other option of Csound included as well.
>>>
>>> Richard
>>>
>>> --
>>> View this message in context:
>>> http://csound.1045644.n5.nabble.com/QuteCsound-behaviour-after-Csound-re-install-tp4897011p4899949.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"
>>>
>>
>> Dr Victor Lazzarini
>> Senior Lecturer
>> Dept. of Music
>> NUI Maynooth Ireland
>> tel.: +353 1 708 3545
>> Victor dot Lazzarini AT nuim dot ie
>>
>>
>>
>>
>>
>> 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"
>

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie





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 have set OPCODEDIR now in Qute's environment variables, but all the others
(SADIR, SSDIR, SFDIR, INCDIR etc) are also blank.
It looks I get slightly less error messages.

Does anyone have a screen dump of what these variables should be in OS X?,

Richard


--
View this message in context: http://csound.1045644.n5.nabble.com/QuteCsound-behaviour-after-Csound-re-install-tp4897011p4903540.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"

hello,
after quite some time I suggest some other thougts, that maybe will help

lines like 
WARNING: not loading 'libambicode1.dylib' (incompatible with this version of
 Csound (2.5/2.4)

usually mean that the opcodes in the opcodedir are newer than the csound that was linked into qutecsound. It means, probably, newer csound and older qutecsound exist together.

If you built qutecsound yourself, uninstall and clean the sourcesdr and build it again.
If it came with a package, try to unistall the package, look if qutecsound binary is still existing somewhere and delete it. Then reinstall.

Perhaps you have done it already many times and the problem is somewhere else, I don't know.

I am on linux and not osx, but I have had similar problems. (and it was actually easy to solve).

greetings,
tarmo

On Thursday 13 October 2011 00:19:50 zappfinger wrote:
> I had to reinstall Csound on my OS X 10.5.8 machine. The verion of Csound is
> 5.13 float.
> Now when I push the run button in QuteCsound 0.6.0, I get many errors, like:
> 
> WARNING: not loading 'libambicode1.dylib' (incompatible with this version of
> Csound (2.5/2.4)
> WARNING: not loading 'libbabo.dylib' (incompatible with this version of
> Csound (2.5/2.4)
> WARNING: not loading 'libbarmodel.dylib' (incompatible with this version of
> Csound (2.5/2.4)
> WARNING: not loading 'libcompress.dylib' (incompatible with this version of
> Csound (2.5/2.4)
> 
> Only when I press 'Run in Term' I get normal output.
> 
> What could this be?
> 
> 
> Richard 
> 
> --
> View this message in context: http://csound.1045644.n5.nabble.com/QuteCsound-behaviour-after-Csound-re-install-tp4897011p4897011.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"