I commented out the warnings.

----- Original Message ----- 
From: "Art Hunkins" 
To: 
Sent: Tuesday, June 29, 2004 5:46 PM
Subject: Re: Latest WinCsound5


> I really appreciate all your effort in trying to get FLTK to work. Your
> efforts are invaluable. Too bad there isn't a developer with a particular
> interest in this area. I suspect that Gab (who would be great at this) is
> only giving limited time and input to the canonical effort.
>
> I also gather that not many Csounders are doing realtime performance
Csound.
> If they did, they'd *have* to use MIDI in and FLTK audio widgets, or
> something external to Csound. I only went to CsoundAV because MIDI and
FLTK
> didn't work in canonical
>
> I've attached the simplest possible test example of the WARNING problem.
> Actually, it's not even a real problem; the file runs perfectly well. It
> real-time performs a sine wave for 30 seconds with a counter widget to
> control frequency. As is, the FLsetVal_i opcode sets initial frequency to
> 200. This version creates one WARNING message.
>
> If you comment out the FLsetVal_i line, the note plays (silently!) with a
> default value of zero; hitting the counter will change to an audible
> frequency and you'll hear something. This version gives *no* WARNING.
>
> I suppose the "problem" *could* have to do with FLcount, which is what I
> always pair FLsetVal_i with. Indeed, all FLsetVal_i does is to feed an
> initial (ihandle) value to FLcount. However, I don't recall any other
> symptoms pointing in this direction.
>
> Please let me know when your recently made changes to the WARNING message
> will be available for me to try out. If there's a particular file you
might
> send along that I could substitute in what I have, or some editing I could
> do to my files, that might work too. In sum, whenever and whatever I could
> test I'd be happy to!
>
> Art Hunkins
>
> to----- Original Message -----
> From: 
> To: ; 
> Sent: Tuesday, June 29, 2004 1:42 PM
> Subject: Re: Latest WinCsound5
>
>
> You're right, only FLsetVal is in z1. I don't know why.
>
> I don't understand much about the FLTK opcodes or what their current state
> is; I'm only trying to get them to work because a lot of discussion on the
> lists has concerned them, and nobody else seems to be doing anything about
> them.
>
> You can run CsoundVST and do csound -z1 in the Csound command text input
> field, and it will scroll just fine (I just did that).
>
> Original Message:
> -----------------
> From: Art Hunkins abhunkin@uncg.edu
> Date: Tue, 29 Jun 2004 13:32:01 -0400
> To: gogins@pipeline.com
> Subject: Re: Latest WinCsound5
>
>
> When will these updates be available in your compiled Windows version? (I
> downloaded and they're not there now.) I'd like to try them with my files.
>
> In my current version of CS5, I ran using the -z and -z1 flags. One
> confusing thing is that FLsetVal_i is not listed as an opcode; FLsetVal,
> under -z1 only, is listed twice as follows:
> FLsetVal (null) kki
> FLsetVal (null) ii
>
> (If someone could come up with a scrolling window for this output, my
sanity
> would not be quite so compromised. Working with  and  on my
> keyboard is both hit-and-miss and nervewracking!)
>
> Documentation identifies only two init-time variables for FLsetVal_i;
these
> is little room for going wrong. A typical line of (my) code:
> FLsetVal_i 3, ip - where ip references an ihandle specified in the
> immediately previous FLcount statement (setting its initial counter value
to
> 3). Both these arguments are obviously of the right type.
>
> What you say about "exponents" and "ftable control" is Greek to me; as far
> as I know, I'm not involved with anything like that.
>
> I'm still puzzled by why FLsetVal_i isn't in the list of opcodes; but I'm
> probably *way* off track.
>
> Art Hunkins
>
> ----- Original Message -----
> From: "Michael Gogins" 
> To: "Art Hunkins" 
> Sent: Monday, June 28, 2004 9:05 PM
> Subject: Re: Latest WinCsound5
>
>
> > I added linefeeds.
> >
> > I added more information in the messages about what function prints the
> > WARNINGs.
> >
> > It looks from the code like the exponent can be 0 or -1 but not anything
> > else -- i.e. ftable control of the widget response is not implemented.
> > That's what the warnings seem to be about, so I left them in.
> >
> > If that's not your problem, then there are probably parameter mismatches
> in
> > some of the FLTK opcodes. Maybe you should check your code against
the -z1
> > printout.
> >
> > ----- Original Message -----
> > From: "Art Hunkins" 
> > To: 
> > Sent: Monday, June 28, 2004 11:24 AM
> > Subject: Re: Latest WinCsound5
> >
> >
> > > Hello, Michael,
> > >
> > > The PortAudio DLL works just fine now.
> > >
> > > I discovered where all my "WARNING: not implemented yet"'s are coming
> > from.
> > > One warning is generated by each FLsetVal_i in my orchestra. Needless
to
> > say
> > > FLsetVal_i is *working* fine - there's just the spurious message.
> > >
> > > This came to me after running an orch with 55 FLsetVal_i's!
> > >
> > > BTW, these warnings come without reference, and without CR/LF so they
> run
> > on
> > > one after the other. They are immediately followed by the 0db
amplitude
> > > message.
> > >
> > > I assume it's no big deal to eliminate the erroneous messages.
> > >
> > > Art Hunkins
> > >
> > > ----- Original Message -----
> > > From: 
> > > To: 
> > > Sent: Saturday, June 26, 2004 9:35 PM
> > > Subject: RE: Latest WinCsound5
> > >
> > >
> > > Oops - I changed the link style. I'll have to rebuild and upload
again.
> > Try
> > > renaming the DLL in the mean time to just what it says, and see if it
> > > works. This is a standard method of linking shared libraries by versio
n
> on
> > > Linux.
> > >
> > > Original Message:
> > > -----------------
> > > From: Art Hunkins abhunkin@uncg.edu
> > > Date: Sat, 26 Jun 2004 19:46:49 -0400
> > > To: gogins@pipeline.com
> > > Subject: Latest WinCsound5
> > >
> > >
> > > Hi, Michael,
> > >
> > > Just downloaded and ran your latest Windows compile.
> > >
> > > Get the error message "PortAudio.dll.0.0.19 not found."
> > >
> > > I imagine this is a typo, with the .0.0.19 being spurious. Right?
> > >
> > > Art Hunkins
> > >
> > >
> > > --------------------------------------------------------------------
> > > mail2web - Check your email from the web at
> > > http://mail2web.com/ .
> > >
> > >
> > >
> >
> >
>
>
> --------------------------------------------------------------------
> mail2web - Check your email from the web at
> http://mail2web.com/ .
>
>
>