Csound build,10.4 PPC

studiorat

Hi,
I know there's a few guys here have a suss on C++ and the like. I may need your help.
Trying to put together a front end thingy for Csound 5.10 at the moment.
Am trying to put qutecsound on (I'd say install but it seems a bit more complicated than that).

Anyway is anybody familiar with the Mac Terminal? I'm trying to fing the right code to get qutecsound going. Have qt, and python on already...

Ta.

Maybe worth crossposting this to one of the computer fora if possible.

iamhunted

i mightnt usnderstand your question correctly but are you asking how to start an app via terminal? Cd to the folder with the app in it type the app's name with './' before it

studiorat

That's what I thought. But I'm actually trying to figure out which one is the app.

There is something called os-build.sh or similar. sh is a shell right? And I thought I needed to run that.

But I've tried that with a sudo command but can't seem to get it going. I don't really know if that's what I should be trying to run in the first place!!!!

splitrmx

Did you already go through the building instructions?

"Building
To build QuteCsound you need Qt and its development libraries from Trolltech, Csound, and libsndfile (though you can optionally build without the latter). Naturally you need a compiler like gcc (for *nix), mingw for Windows or Xcode for OS X.
QuteCsound uses qmake to build, so you generally only need to do:

$ qmake

$ make

On OS X, you need to run "qmake", which generates an XCode project, which you can then build within XCode."

PaulBrewer

What IS all this Devil's Talk ?
Explain ...

kfoltman

studiorat wrote: »

Hi,
I know there's a few guys here have a suss on C++ and the like. I may need your help.

Why would ANYONE outside of academic setting WANT to use Csound? (-:

Half-kidding. Csound has its uses and strong points. Like if you want to experiment with cymbal sound simulations based on gazillion of sine waves with individually controlled envelopes, or play with physical modeling. And it's open source. But in most cases it is a royal PITA comparing to, say, Reaktor.

studiorat

splitrmx wrote: »

Did you already go through the building instructions?

"Building
To build QuteCsound you need Qt and its development libraries from Trolltech, Csound, and libsndfile (though you can optionally build without the latter). Naturally you need a compiler like gcc (for *nix), mingw for Windows or Xcode for OS X.
QuteCsound uses qmake to build, so you generally only need to do:

$ qmake

$ make

On OS X, you need to run "qmake", which generates an XCode project, which you can then build within XCode."

I did, and it was bloody greek to me, reading through it again it is starting to make sense, just a bit mind. Foolishly I thought Terminal would actually build the project. I guess I need to dig out my old OS disks and install X-Code. It doesn't seem to be available for download, but I could be wrong.

kfoltman wrote: »

Why would ANYONE outside of academic setting WANT to use Csound? (-:

Funny you should mention that...

kfoltman

studiorat wrote: »

I did, and it was bloody greek to me, reading through it again it is starting to make sense, just a bit mind. Foolishly I thought Terminal would actually build the project. I guess I need to dig out my old OS disks and install X-Code. It doesn't seem to be available for download, but I could be wrong.

Can't help you with the MacOS X and X-Code thing (I'm a PC guy, Windows and Linux to be precise), but maybe there's a way to generate a standard Makefile that you can build using make and gcc. Assuming gcc is installed - I don't know whether or not it is installed by default in MacOS X.

However, maybe, just maybe, you can skip the whole frontend stuff? (I mean Qutecsound)

How about using a text editor and command-line version of Csound? You won't have an editor with syntax highlighting. You won't have user-friendly launching. But that shouldn't be a problem. It's nothing when compared to having to learn all the GENs and opcodes you need

studiorat

One of the reasons I was going for quteCsound was that it allows me to run the script without a compiling it each time. I don't know if just a text editor and command line version will allow me to do that. We both know there'll be enough mistakes along the way.

kfoltman

studiorat wrote: »

One of the reasons I was going for quteCsound was that it allows me to run the script without a compiling it each time. I don't know if just a text editor and command line version will allow me to do that. We both know there'll be enough mistakes along the way.

I've just installed it out of curiosity. It seems to do a lot more than editing and launching. It has an editor for custom "control surfaces" where you can put sliders, values, oscilloscopes etc., seems to be nice for realtime control.

However, the Windows version 0.4.1 seems to have a very annoying problem: copy-paste doesn't work in text editor. Maybe it works in the Mac version. Also, portaudio doesn't seem to like the ASIO driver I'm using. Again, shouldn't matter for Mac.

I think they have a MacOS X binary on their Sourceforge download page, see: http://sourceforge.net/projects/qutecsound/files/QuteCsound/ (the 0.4.1 tab, QuteCsound-0.4.1-OSX-Intel-incQt.tar.gz or QuteCsound-0.4.1-OSX-Intel-noQt.tar.gz - probably depending on if you already have Qt installed or not).

splitrmx

studiorat wrote: »

Foolishly I thought Terminal would actually build the project.

OSX is basically a form of unix, and the terminal window is a command line interface, ie, a method to run commands on OSX (like a text version of the icons and folders etc). For example if you wanted to delete a file in OSX you could drag it to the trash can as people normally do, or you could open the terminal, and type some commands to remove the file (like rm filename).

Like somebody else suggested, there is probably a binary or "already compiled and built" version of the software you're looking for that you can just download and run as normal. This downloading the source and then compiling it yourself is usually for bearded sandal wearing nerds who have stuffed penguins on their desk.

Also, I'd recommend trying out Max/MSP if you're looking at CSound, apparently it's better documented and easier to get running on OSX, there's a demo version you can download from their website (search for Cycling 74)

studiorat

Thanks for the info guys. Oddly enough I was cutting and pasting code for a score on Csound yesterday, on a Windows machine, so that's a bit odd.

I was talking to a guy today and he downloaded it for an Intel Mac and it just installed and ran no problem. I downloaded the PPC version from source forge and couldn't find any .mpkg or .app files. Only some script to run in x-code apparently. Maybe I'll have another go at it again. I really don't want to get into building the thing myself...

@ Splitrmx, thanks for the recommendation. I'm using Pure Data a little at the moment. Does Max/Msp do something with Csound or something? I was going to stick with PD for the moment...

kfoltman

studiorat wrote: »

I was talking to a guy today and he downloaded it for an Intel Mac and it just installed and ran no problem. I downloaded the PPC version from source forge and couldn't find any .mpkg or .app files. Only some script to run in x-code apparently. Maybe I'll have another go at it again. I really don't want to get into building the thing myself...

That's seriously odd. Are you sure you've unpacked the right version and looked in the right directory (and not in the source directory again)? The binary is supposed to be already built. Definitely worth another try.

studiorat

Update!

was trying to download 0.4.2 So I went back to 0.4.1 without qt and downloaded that. And sure enough the thing fired up first time! oh maxi-joy!

It doesn't seem to be the most stable thing in the world right now, but at least it's a start. It's working and I've run a few little things on it. Hopefully I can track down what ever seems to be shutting the app down along the way.

Thanks for the help chaps.