[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [sc-dev] [Approve?] Add 'Extensions' directories to compiler

Actually, as far as SynthDefs and recordings go, aren't those set in the language already? For using a different synthdef/ I'm just setting the synthDefDir classvar. It doesn't seem like you would need to move the server from wherever it already lives (in Applications for me, for example).

Though it does make sense then that I wouldn't be able to run scsynth from the command line (for NRT for example) with my synthdefs being stored somewhere else. Within the app though, calling NRT (with Score) doesn't have any problems finding the synthdefs.


Joshua D. Parmenter
Graduate Student, Music Composition

"...Some people think a composer's supposed to please them, but in a way a composer is a chronicler... He's supposed to report on what he's seen and lived." -Charles Mingus

sdwilson@xxxxxxxxxxxx wrote:
Sorry I should have been clearer. IIRC the issue was that the language app
couldn't write to the synthdefs directory, which caused problems while
initing Classes.

I didn't have time to sort it out, so I just installed SC in the user

I don't think it's necessary to move the server app to solve this.


well the server is a command line app and those typically in unix
operate on the current working directory.
the Server-boot method could be changed to 'cd' to
~/Library/Application Support/SuperCollider
or whereever.

	var <>dir = "~/Library/Application Support/SuperCollider";

	bootServerApp {
		if (inProcess, {
			"booting internal".inform;
			unixCmd("cd " ++ dir ++ "; " ++ program ++
			("booting " ++ addr.port.asString).inform;

On Dec 21, 2004, at 1:40 AM, sdwilson@xxxxxxxxxxxx wrote:

Actually it might be worth moving the synthdefs directory as well, and
possibly other things like recordings. I've seen issues when running SC
from a non-admin account.


sc-dev mailing list

sc-dev mailing list