| Neat! I'm looking forward to trying out once again on Linux tonight.
I'll be giving it another try on Cygwin today (yesterday I had the same
problems Bobby did with Top/ccsound.c, but that you fixed yesterday).
Things in San Francisco are great! I'll write to you more in private
email. ^_^
steven
On Tue, 2004-02-24 at 05:01, Michael Gogins wrote:
> I fixed the problem with realtime audio on Linux to some extent; it no
> longer segfaults, and I hear sound, but it's hissy. The problem was not
> parsing for device number on Linux/ALSA, which I fixed with the proper
> #ifdef (HAVE_LIBASOUND). If you update and reconfigure it should work better
> now.
>
> I'll add nreverb too, or you could.
>
> I'll also look into the opcode loading situation, and I'll remove any
> redundant code from CVS.
>
> As always, thanks for the quick feedback.
>
> How are things in San Francisco?
>
> ============================================
> Michael Gogins
> gogins at pipeline period com
> Irreducible Productions
> CsoundVST, an extended version of Csound for programming music and sound
> Available at http://sourceforge.net/projects/csound/
> ============================================
>
>
> ----- Original Message -----
> From: "stevenyi"
> To: "Csound Developers Discussion List"
> Sent: Tuesday, February 24, 2004 2:25 AM
> Subject: [CSOUND-DEV:4127] status update
>
>
> > Hi Michael,
> >
> > I did a sync with CVS and rebuilt csound5. dcblock was now built and put
> > into the /usr/local/lib/csound directory. Now I've gotten past dcblock
> > but nreverb seems to be missing.
> >
> > Trying out my fluidOpcodes opcode library loaded correctly but it did
> > not produce sound. I'm assuming it's because of some difference between
> > csound4's GLOBALS and csound5's ENVIRON struct. However, I'm looking at
> > the Makefile.am file and notice that both Top/dl_opcodes.c and
> > Top/load_opcodes.c are included in the sources for
> > libcsound_la_SOURCES. These two are mutually exclusive, last I had
> > looked (I had done work on load_opcodes.c to be more in line with your
> > original purposes for the corresponding API functions). I'm not sure
> > what happened when compiling if one of them redefined the functions the
> > other one did or what. There probably shouldn't be both of these files
> > included (unless you reworked them; apologies, I didn't check very
> > deeply).
> >
> > I tried compiling the other day with -lefence and without optimization
> > to see if I could get a back trace to see why the segfaults after trying
> > realtime and after showing user options but no luck (most likely my
> > fault though as I'm not all that familiar with using these tools). I'll
> > try to spend more time on this tomorrow.
> >
> > Thanks!
> > steven
> >
>
> |