Csound Csound-dev Csound-tekno Search About

[Csnd] About csound-x and csound environment

Date2009-11-07 13:39
FromDmitriy
Subject[Csnd] About csound-x and csound environment
I'm a bit confused posting about csound-x on this list, but maybe someone 
here uses (or tries to) it too and could help me.

Here's the situation:

I have installed:       Debian Sid
                CSound 5.11 from official repos
                Emacs 23.1 from official repos
                CSound-x 2.18 (stef-elisp-2.18)


Here's how i configured csound-x so far:

(add-to-list 'load-path "~/emacs/plugins/stef-elisp/")
(require 'stef-elisp)

;;;;;;;;CSound-x Environment
(setq cscsd-OPCODEDIR64 "/usr/lib/csound/plugins64-5.2/")
(setq cscsd-OPCODEDIR "/usr/lib/csound/plugins64-5.2/")
(setq cscsd-INCDIR "/win/mymusic/csound_includes/")
(setq cscsd-temp-csd-file "/win/mymusic/tmp/tmp.csd")
(setq cscsd-default-csd-directory "/win/mymusic/tmp/")

And when i try to 'process file' (from the CSD menu), i get following error 
message: 
Error opening plugin directory '~': ??? ?????? ????? ??? ????????


I searched through all files that stef-elisp consists of for that message 
(except the question marks part), but i didn't find it.

I searched through various sources of csound documentation and couldn't find 
any mention of this error (which i think is csound related, because error is 
showed in the Shell buffer).

I suspect that error is somehow related to csound invocation and the way it 
is performed in csound-x.


... Any help? Please?



Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date2009-11-08 16:00
FromStéphane Rollandin
Subject[Csnd] Re: About csound-x and csound environment
> I'm a bit confused posting about csound-x on this list, but maybe someone 
> here uses (or tries to) it too and could help me.

well I am the developper and as far as I am concerned this is the right
place for general questions about it.

now if the problem happens to be very specific to your
installation/system, then we may proceed via private mails.

> And when i try to 'process file' (from the CSD menu), i get following error 
> message: 
> Error opening plugin directory '~': ??? ?????? ????? ??? ????????
> 

this is a csound error message, and it seems to say that your plugin
directory is not valid. the following garbage is not related to csound-x
in any way I can fathom.

does (file-exists-p (cscsd-OPCODEDIR)) return t in Emacs ?
does (cscsd-OPCODEDIR) indeed return "/usr/lib/csound/plugins64-5.2/" ?
does (getenv "OPCODEDIR") also return "/usr/lib/csound/plugins64-5.2/" ?


best,

Stef





Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date2009-11-08 19:33
FromStéphane Rollandin
Subject[Csnd] Re: About csound-x and csound environment
> Here's how i configured csound-x so far:
> 
> (add-to-list 'load-path "~/emacs/plugins/stef-elisp/")
> (require 'stef-elisp)
> 
> ;;;;;;;;CSound-x Environment
> (setq cscsd-OPCODEDIR64 "/usr/lib/csound/plugins64-5.2/")
> (setq cscsd-OPCODEDIR "/usr/lib/csound/plugins64-5.2/")
> (setq cscsd-INCDIR "/win/mymusic/csound_includes/")
> (setq cscsd-temp-csd-file "/win/mymusic/tmp/tmp.csd")
> (setq cscsd-default-csd-directory "/win/mymusic/tmp/")

the environment variables (cscsd-OPCODEDIR, cscsd-SFDIR, etc..) need to 
be set via the customization tool in Emacs. this may be related to your 
problem.

try by simply keeping these lines in your .emacs

  (add-to-list 'load-path "~/emacs/plugins/stef-elisp/")
  (require 'stef-elisp)

then start Emacs, do M-x customize-group csound-x-applications-paths and 
record your settings there (don't forget to save the changes for all 
sessions)

the reason for this (you can ignore the following, it's just for 
information) is that these variables have to be synchronized with the 
actual environment variables of the Emacs process. the custom system 
takes care of that: when you change the Emacs variable, the 
corresponding environment variable is changed accordingly (to say it 
differently, csound-x controls the Emacs process environment for all 
csound-related stuff). if you set the variables directly with setq then 
the synchronization is not enforced and this may lead to the kind of 
problem you have (depending on the global values of the actual 
environment variables when Emacs starts)

hope this helps,

Stef




Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"