Csound Csound-dev Csound-tekno Search About

Re: [Csnd] One last MIDI Csound question

Date2005-09-01 22:28
FromIstvan Varga
SubjectRe: [Csnd] One last MIDI Csound question
Art Hunkins wrote:

> It would be ***very*** helpful for there to be defaults for all these
> directory variables, so that most users wouldn't even have to bother with
> (or even know about) them. It is very confusing, especially considering the
> fact that Istvan's versions are the only Windows Csound (to my knowledge)
> that requires the user to supply these variables(??).

The Gogins releases also require OPCODEDIR/OPCODEDIR64, but the GUI
installer automatically sets environment variables. You may want to use
that instead if you have problems with setting the environment variables.
-- 
Send bugs reports to this list.
To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk

Date2005-09-01 22:29
From"Art Hunkins"
SubjectRe: [Csnd] One last MIDI Csound question
It would be ***very*** helpful for there to be defaults for all these
directory variables, so that most users wouldn't even have to bother with
(or even know about) them. It is very confusing, especially considering the
fact that Istvan's versions are the only Windows Csound (to my knowledge)
that requires the user to supply these variables(??).

How many times has this problem arisen recently?

Let's always keep the average user in mind. Certainly, by the time we get
out of beta, this issue will be addressed? (Either that, or we won't have
many average users.)

Art Hunkins

----- Original Message -----
From: "Istvan Varga" 
To: 
Sent: Thursday, September 01, 2005 1:41 PM
Subject: Re: [Csnd] One last MIDI Csound question


> This is probably the usual problem with OPCODEDIR/OPCODEDIR64 not being
> correctly defined, and for this reason the PortMidi plugin - as well as
> real time audio and many opcodes - is not loaded.
>
> Art Hunkins wrote:
>
> > Hi, William,
> >
> > I'm copying this response to the Csound listserv. Probably someone like
> > Istvan or Michael can give you a more authoritative answer to your
question.
> > (BTW, your questions are no "bother" to me; this is right up my alley.)
> >
> > My thoughts:
> >
> > 1) Do you have a MIDI input device installed? If you do, certainly the
> > flag -M0 should pick it up.
> >
> > 2) There is no -+rtmidi flag in my .csd. Are you using it in your
> > commandline? The flag may have the wrong format (formats are *very*
picky);
> > or, OTOH, I think that PortMIDI is the default and the flag can be
omitted -
> > at least in Windows, which IIRC is your OS.
> >
> > You did comment out (with ;) the non-operative CsOptions lines, didn't
you?
> > You only need the line designated as Csound5. (I included one -
currently
> > active - for CsoundAV, as well as another for flCsound. Those two need
> > semicolons to start; the Csound5 line of course needs its first
semicolon
> > removed.) Just checking!
>
> I would recommend commenting out all by default, as getting errors because
of
> the CsoundAV options can be annoying.
> --
> Send bugs reports to this list.
> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk

-- 
Send bugs reports to this list.
To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk

Date2005-09-01 22:36
FromSteven Yi
SubjectRe: [Csnd] One last MIDI Csound question
AttachmentsNone