> Dear list,
>
> After I installed Csound 5.10 with the new API on my computers, all
> the front ends (Csound5, CsoundGUI, MacCsound) except blue do not
> work anymore like explained in the release notes. I do now wonder how
> to work with Csound, as really every interface crashes. I reinstalled
> then the version 5.09 but the crashes remain. It is on Mac OS 10.4,
> both on my Intel and PPC based computers. Forgive me the newbie-
> question, but how could I interact with Csound and make it render
> things without any working interface? Or how can I at least make
> version 5.09 run again?
>
> Best,
>
> Jan Jacob

Sounds like you have a mixture of systems.  I do not have a working M

----- Original Message -----

From: Jan Jacob Hofmann

To: Csound List

Sent: Sunday, April 12, 2009 11:05 AM

Subject: [Csnd] Using Csound frontends with API 2.0

Dear list,

After I installed Csound 5.10 with the new API on my computers, all the front ends (Csound5, CsoundGUI, MacCsound) except blue do not work anymore like explained in the release notes. I do now wonder how to work with Csound, as really every interface crashes. I reinstalled then the version 5.09 but the crashes remain. It is on Mac OS 10.4, both on my Intel and PPC based computers. Forgive me the newbie-question, but how could I interact with Csound and make it render things without any working interface? Or how can I at least make version 5.09 run again?

Best,

Jan Jacob

sound         |         movement          |          object         |          space

sonic architecture       |        site: http://www.sonicarchitecture.de  

spatial electronic composition     |    2nd order ambisonic music  

Jan,

Did you install all components of the OS X installers (Csound library,
Csound Apps, and SupportLibs) ?

Definitely try running Csound from the commandline so that we can see any
error messages about shared libraries not loading.  (I also recommend using
QuteCsound instead of Csound 5.app or csound5GUI).


To get a (mostly) clean reinstall, try this before running the installer.

1. Delete the following files from /Library/Receipts :  CsoundApps.pkg,
CsoundLib.pkg, SupportLibs.pkg.

2. Delete the entire folder /Library/Frameworks/CsoundLib.framework

3. Delete these apps from /Applications : Csound 5, Csound 5 Wish, the
"Csound 5 frontends" folder containing csound5GUI and Winsound.

4. From the commandline,
  cd /usr/local/bin
  sudo rm atsa brkpt cs csb64enc cseditor csound cstclsh cswish cvanal
dnoise envext extract extractor het_export het_import hetro linseg lpanal
lpc_export lpc_import makecsd mixer pv_export pv_import pvanal pvlook scale
scot scsort sdif2ad sndinfo srconv tabdes

(everything from "sudo rm" to "tabdes" should be entered as one line)


This will still leave the support libraries and a couple of other
miscellaneous items on your system, but I would rather not advise you on how
to remove those as your system may be different than mine.

Also, rather than copying the opcode libraries from 5.1 to 5.2 (which will
break newer front ends), I think you can probably get MacCsound to work by
relinking the symlink at /Library/Frameworks/CsoundLib.framework/Resources.

Execute these commands on the commandline:
  cd /Library/Frameworks/CsoundLib.framework/
  sudo rm Resources
  sudo ln -s Versions/5.1/Resources Resources

This change will cause problems if you try to build any Csound front ends
from source code.  It may also interfere with QuteCsound's ability to find
the manual.  To fix that, you could do this

  cd /Library/Frameworks/CsoundLib.framework/Versions/5.1/Resources/

If there is no "Manual" directory here, then

  ln -s 
/Library/Frameworks/CsoundLib.framework/Versions/Current/Resources/Manual
Manual

(That should all be on one line with a space before the final "Manual").

Please let us know if you are able to get the Csound front ends working
again.

Anthony Kozar
mailing-lists-1001 AT anthonykozar DOT net
http://anthonykozar.net/

victor wrote on 4/12/09 8:50 AM:

> You can try qtcsound or use command-line Csound.
> 
> Another solution is to copy the plugins directory:
> 
> from /Library/Frameworks/CsoundLib.framework/Versions/5.1/Resources/Opcodes to
> /Library/Frameworks/CsoundLib.framework/Versions/5.2/Resources/Opcodes
> 
> then MacCsound should work again, but command-line csound will be broken.
> 
> I don't know why uninstalling it and then installing 5.09 is not working. But
> I guess
> it's because OSX is not allowing you to downgrade. Not sure of a solution.
> 
> Victor
> ----- Original Message -----
> From: Jan Jacob Hofmann
> To: Csound List 
> Sent: Sunday, April 12, 2009 11:05 AM
> Subject: [Csnd] Using Csound frontends with API 2.0
> 
> 
> Dear list,
> 
> 
> After I installed Csound 5.10 with the new API on my computers, all the front
> ends (Csound5, CsoundGUI, MacCsound) except blue do not work anymore like
> explained in the release notes. I do now wonder how to work with Csound, as
> really every interface crashes. I reinstalled then the version 5.09 but the
> crashes remain. It is on Mac OS 10.4, both on my Intel and PPC based
> computers. Forgive me the newbie-question, but how could I interact with
> Csound and make it render things without any working interface? Or how can I
> at least make version 5.09 run again?

       Dear Mr Kozar,

I'm currently working with Csound MacCsound and 5.10 (but in reality with
5.08 Csound float) after copying the contents of the folder 5.1 folder 5.2. 

But I ask you kindly to have an explanation of this passage that appears in
this forum. 

>Also, rather than copying the opcode libraries from 5.1 to 5.2 (which will
>break newer front ends), I think you can probably get MacCsound to work by
>relinking the symlink at /Library/Frameworks/CsoundLib.framework/Resources.

>Execute these commands on the commandline:
> cd /Library/Frameworks/CsoundLib.framework/
>  sudo rm Resources
>  sudo ln -s Versions/5.1/Resources Resources

Only a few questions: 

1. I realized that with the command from terminal [sudo rm Resources] is
deleted the folder / Library / Frameworks / CsoundLib.framework / Resources:
then I wonder why this folder? 

2. instead the following command from terminal [sudo ln-s
Versions/5.1/Resources Resources] creates a link simboloco "to the 5.1
folder, right? 

3. These terminal commands to enable me to work with MacCsound, right? 

4. Resources canceled after then I will be able to use other frontends to
Csound5, working with the 5.10? 
The frontends will open? 

5. Or will I have to make another re-symlink from terminal to work with
frontends for Csound5 (Csound5GUI, Winsound, Csound5)? 

Thank you very much.

e
:confused:

-- 
View this message in context: http://www.nabble.com/Using-Csound-frontends-with-API-2.0-tp23009755p23240397.html
Sent from the Csound - General mailing list archive at Nabble.com.

Hello,

My answers are below.

kolox wrote on 4/26/09 4:54 AM:

> I'm currently working with Csound MacCsound and 5.10 (but in reality with
> 5.08 Csound float) after copying the contents of the folder 5.1 folder 5.2.
> 
> But I ask you kindly to have an explanation of this passage that appears in
> this forum. 
> 
>> Also, rather than copying the opcode libraries from 5.1 to 5.2 (which will
>> break newer front ends), I think you can probably get MacCsound to work by
>> relinking the symlink at /Library/Frameworks/CsoundLib.framework/Resources.
> 
>> Execute these commands on the commandline:
>> cd /Library/Frameworks/CsoundLib.framework/
>>  sudo rm Resources
>>  sudo ln -s Versions/5.1/Resources Resources
> 
> Only a few questions:
> 
> 1. I realized that with the command from terminal [sudo rm Resources] is
> deleted the folder / Library / Frameworks / CsoundLib.framework / Resources:
> then I wonder why this folder?

That command should not delete a folder since
/Library/Frameworks/CsoundLib.framework/Resources SHOULD be a symlink
already.  If you have installed Csound 5.10, then this symlink would
normally point to 

  /Library/Frameworks/CsoundLib.framework/Versions/5.2/Resources

This causes problems for MacCsound.

> 2. instead the following command from terminal [sudo ln-s
> Versions/5.1/Resources Resources] creates a link simboloco "to the 5.1
> folder, right? 

Yes, that command changes the symlink to point to

  /Library/Frameworks/CsoundLib.framework/Versions/5.1/Resources

The reason I suggested deleting the existing link first is that ln -s
sometimes behaves in a way that I do not understand if you don't delete the
link first.

> 3. These terminal commands to enable me to work with MacCsound, right?

These commands SHOULD let you work with MacCsound assuming the following:

    1.  You have installed Csound 5.10 "floats" for PPC, and
    2.  You have not modified the directory structure of Csound 5.10.

Because you have already copied the contents of the 5.1 folder to 5.2, you
would need to delete your CsoundLib.framework folder and reinstall before
these instructions would do you any good.

It is important to understand the reason that I am suggesting relinking the
Resources symlink.  It had been previously suggested that MacCsound can be
made to work by copying the contents of 5.1/Resources/Opcodes to
5.2/Resources/Opcodes within the CsoundLib framework.  However, this breaks
the 5.10 commandline Csound and all of the other front ends included with
Csound 5.10.

By relinking the symlink instead, I believe that you can get MacCsound to
work AND retain the use of the commandline Csound and probably the other
front ends.  This works for me on OS X 10.5 with a PPC version of Csound
5.10 installed.  My suggestion MAY break some other things like the csnd
Python module or TclCsound but many users do not need those.  (And I have
not tested whether they are broken with this change or not).

> 4. Resources canceled after then I will be able to use other frontends to
> Csound5, working with the 5.10?
> The frontends will open?

They SHOULD.  However, I remember that there were problems with some of the
frontends in the 10.4 versions of Csound 5.10.  Definitely, my suggestions
do not apply to the Intel version of Csound or the "doubles" version.

> 5. Or will I have to make another re-symlink from terminal to work with
> frontends for Csound5 (Csound5GUI, Winsound, Csound5)?

One thing that may break when you change the Resources symlink is the
ability of QuteCsound to find the manual.  I suggested creating another
symlink to resolve that issue but I haven't tested the solution.

As a final suggestion, I think all MacCsound users should give QuteCsound a
try.  It is being actively developed and works without fuss with the latest
version of Csound.  It is a very nice replacement for MacCsound and I highly
recommend it.

If you have any more questions or run into trouble, feel free to ask.

Anthony Kozar
mailing-lists-1001 AT anthonykozar DOT net
http://anthonykozar.net/

Hi,

On Mon, Apr 27, 2009 at 4:30 PM, Anthony Kozar
 wrote:
>
> One thing that may break when you change the Resources symlink is the
> ability of QuteCsound to find the manual.  I suggested creating another
> symlink to resolve that issue but I haven't tested the solution.
>

QuteCsound currently looks for the manual here by default:
/Library/Frameworks/CsoundLib.framework/Resources/Manual

But if needed, you can change this in the configuration dialog.


Cheers,
Andrés