nyquist-users — general discussion list for users of Nyquist

Re: [Nyquist-users] compiling nyquist and mailing list issues

[Raymond M. <la...@gm...>]

On October 3, 2010 10:13:59 am you wrote:
> I understand perfectly. My only point is that not everybody knows
> that, and it might make life easier for those who aren't Linux experts
> if these requirements were documented in the install instructions.
> Most people, I think, would have given up by now, if they don't have a
> background in Unix or Linux. There may be some people interested in
> using Nyquist who don't have that kind of background, like musicians
> or composers.

I think you misunderstand some of the purpose of Nyquist then. It can be used 
for experimenting with sound and programming of it.

Aside from the technically inclined, most musicians and composers will not 
know what to do with this program. Thus having to compile it is not a far 
stretch at all given the technical side involved. The average musician sure is 
not going to want to program in Lisp, if program at all.

Binaries would be nice, but this is not your average sound program for average 
people in my opinion. So compiling is not a big deal at all.

If you are desperate for a binary then inquire with your Linux distro 
providers to see if they will compile and distribute it. In fact this is what 
happens with many programs that are not available in compiled form (and there 
are quite a few common programs on a Linux system that are only available this 
way from the original developers) and probably the most reliable way for it to 
work on a specific platform besides doing it yourself.

Raymond

Re: [Nyquist-users] compiling nyquist and mailing list issues

[David <dfk...@gm...>]

I understand perfectly. My only point is that not everybody knows
that, and it might make life easier for those who aren't Linux experts
if these requirements were documented in the install instructions.
Most people, I think, would have given up by now, if they don't have a
background in Unix or Linux. There may be some people interested in
using Nyquist who don't have that kind of background, like musicians
or composers.

You don't happen to remember which version of PortAudio is the right
version? I installed the latest version available from the Ubuntu
repository, but it didn't help. That might be worth documenting, too,
if a particular version is required.

Thanks.

Re: [Nyquist-users] compiling nyquist and mailing list issues

[Raymond M. <la...@gm...>]

On October 2, 2010 06:50:29 pm David wrote:
> I got past the 'asound' problem, seems you need to have the
> "developer" version of ALSA  installed.
> 
> But now I'm getting another error, and it doesn't look like it's due
> to a missing package.
> 
> portaudio/pa_unix/pa_unix_hostapis.o:(.data+0x0): undefined reference
> to `PaAlsa_Initialize'
> collect2: ld returned 1 exit status

Incorrect libraries, wrong version of PortAudio, etc.

I already went through this myself and reported it in some posting, not sure 
where/when now.

> Here's a list of the packages I've had to install so far. As Raymond
> says, they should be standard in most Linux distros, but they weren't
> included in mine. If someone's using a distro aimed at small netbooks
> or end-users (as opposed to developers), they might not be included.
> 
> - gcc
> - g++
> - automake
> - libtool
> - libasound2-dev

Aside from the ALSA part, these are standard tools on Linux for doing 
development. The question is whether you have your system setup for it or not. 
A vanilla install of one distro for an end user is not necessarily intended 
for software development immediately. Since you are trying to use Nyquist, 
which does not come in binaries, then these are absolutely normal requirements 
that you have to fulfill.

And you will not have the development tools installed on a netbook or even a 
regular system by default unless you choose the option appropriately on 
install of Linux or set this up yourself. That is just the way it is and is 
completely expected by anyone doing software development or even just to 
compile a binary.

Raymond

Re: [Nyquist-users] compiling nyquist and mailing list issues

[David <dfk...@gm...>]

I got past the 'asound' problem, seems you need to have the
"developer" version of ALSA  installed.

But now I'm getting another error, and it doesn't look like it's due
to a missing package.

portaudio/pa_unix/pa_unix_hostapis.o:(.data+0x0): undefined reference
to `PaAlsa_Initialize'
collect2: ld returned 1 exit status

Here's a list of the packages I've had to install so far. As Raymond
says, they should be standard in most Linux distros, but they weren't
included in mine. If someone's using a distro aimed at small netbooks
or end-users (as opposed to developers), they might not be included.

- gcc
- g++
- automake
- libtool
- libasound2-dev

Sorry for all the trouble, but I'm sure I'm not the only one
experiencing all these problems. I googled for the error message I was
getting about asound and came up with about 2,000 hits. Seems it's
quite a common error (not just compiling Nyquist, but a lot of
things).

I tried googling for the latest error too, but couldn't find anything
that seemed relevant.

David.

Re: [Nyquist-users] compiling nyquist and mailing list issues

[David <dfk...@gm...>]

Just as an example, PureData (you're probably familiar with it, or
have at least heard of it) is distributed as a single package for all
variants of Linux and it seems to work for most people. I've installed
it under EasyPeasy, and it works. And for what it's worth, both
Audacity and STK are distributed as pre-compiled packages for Linux,
which I was able to install without any problem. I've also installed a
few other things that weren't included as part of the distribution,
too.

Nyquist is the first thing I've actually had to compile myself. I'm
not sure which version of Nyquist is bundled with Audacity, but if
they can do it, I think it should be possible to distribute the
stand-alone version as a package as well. It's becoming less and less
common to have to compile things yourself, even for Linux systems. And
if it became available from either the Debian or Ubuntu repositories,
it might even expand your user base. (I only became aware of Nyquist
after installing Audacity and discovering that I could write plugins
for it in Nyquist!)

Thanks,
David.

Re: [Nyquist-users] compiling nyquist and mailing list issues

[Roger D. <rb...@cs...>]

  On 10/2/10 8:28 AM, David wrote:
> Just a suggestion, but why not provide pre-compiled install packages
> for Linux so users wouldn't have to compile it themselves?
I'm not very knowledgeable about Linux software distribution. One 
problem is that Linux has many variants and the differences really 
matter, so I believe that a pre-compiled package will only be good for a 
particular installation. There are some pre-compiled versions of Nyquist 
for Linux, but I assume not for EasyPeasy or Ubuntu. A common approach 
in these cases is to provide source and use configuration tools to 
explore the local environment, figure out the proper options, and build 
a working version of the program for that local environment. This has 
not been done for Nyquist. Instead, I've tried to make Nyquist as 
self-contained as possible, and to avoid system-dependent code as much 
as possible. Most of this work predated the widespread use of Linux, 
auto configure tools, and Linux distributions, so I'll readily admit 
that Nyquist is not using popular distribution methods and it could use 
an upgrade by someone that really understands this. Maybe it would be 
possible to take an existing distribution (I think Debian has a packaged 
version of Nyquist) and make it more universal.
> Maybe you
> don't have enough users on Linux to justify the work, I don't know.
> But it might save everybody time in the long run. And some users who
> don't have a programming background may not have the expertise to
> compile it themselves.
>
> At the very least, I'd update the install instructions in the Nyquist
> manual. For example, the 'setenv' command is only available in some
> Unix/Linux shells. On others, you have to use the 'export' command.
> It's not a big deal if you know Unix or Linux well enough, but it
> might be a problem for inexperienced users. And I'd also add a list of
> the tools needed to compile Nyquist; you can't assume that they will
> be automatically included in all Linux distributions, as Raymond seems
> to think.
In the words of Perlis, "One man's constant is another man's variable." 
Seriously, this is good information; I *do* update installation 
instructions based on problems and feedback, so thanks for the input.
> I'm using EasyPeasy, a trimmed-down version of Ubuntu for
> small netbooks, which doesn't include a lot of the development tools
> needed to compile Nyquist (although I can download and install them,
> of course).
I think you'll find it necessary to add lots of dev tools as you move 
away from "standard" apps like open office toward more experimental 
packages.
> As for the header file, it may be that newer compilers have the
> contents of stdio.h "hard-wired" into them, but in the old days, you
> had to include the header file or take the chance that the compiler
> would make some invalid assumptions about the functions declared in
> it. Personally, I think it's still better to include the header
> explicitly, even if it does compile without it on some systems. Maybe
> you could suggest this to the STK folk.
Probably this problem is solved in current STK, but I haven't upgraded.
> As for myself, I've downloaded the missing development tools, but I'm
> still getting a compile error about a missing library ('asound'). I'll
> try to figure it out, but if I can't, I'll post details later.
asound is ALSA. This is fundamental to any sound-related linux program 
(although you could have ALSA without the ALSA development tools needed 
to compile a program that uses ALSA)
> Thanks for your help.
>
> On Sat, Oct 2, 2010 at 1:33 AM, Roger Dannenberg<rb...@cs...>  wrote:
>>   There was a discussion here about some undeclared functions such as
>> "fopen" in Nyquist. My local copy of nyqstk/src/FileRead.cpp has been
>> modified by adding
>> #include<stdio.h>
>> before
>> #include<sys/stat.h>
>>
>> I think the change was put in by some Audacity folks to reduce some
>> warning messages, but apparently with some compilers (or some
>> configurations) a missing declaration is an error. This file comes from
>> STK, and I try to avoid changing STK code so that it will be easier to
>> upgrade, but in this case it really needs the include.
>>
>> I was signed up to get digests, and I guess it took almost a year to
>> make a digest's worth of stuff. If you're reading this in 2011, maybe
>> you should ask me to change your settings. (I just changed mine -- sorry
>> I wasn't getting messages more promptly.)
>>
>> Finally, Edgar, I manually put you on the list. I hope that works for
>> you. I have no idea why you weren't able to sign up yourself.
>>
>> While I'm writing, I'll mention that I'm going to do some work on
>> Nyquist between now and January to get ready for my class. Among other
>> things, Nyquist doesn't work on some systems without an upgrade of
>> PortAudio, and Nyquist Makefiles are not set up for 64-bit machines.
>> (Nyquist will not run on 64-bit instruction sets without a lot of work,
>> but I can at least provide Makefiles that generate 32-bit code even when
>> the native architecture is 64-bit.) I've done this and it seems to work
>> fine, but the changes are not in the release. There are a few other
>> things that are broken. Let me know (or remind me) if there are other
>> fixes I should look into.
>>
>> -Roger
>>
>>
>> ------------------------------------------------------------------------------
>> Start uncovering the many advantages of virtual appliances
>> and start using them to simplify application deployment and
>> accelerate your shift to cloud computing.
>> http://p.sf.net/sfu/novell-sfdev2dev
>> _______________________________________________
>> Nyquist-users mailing list
>> Nyq...@li...
>> https://lists.sourceforge.net/lists/listinfo/nyquist-users
>>

Re: [Nyquist-users] compiling nyquist and mailing list issues

[David <dfk...@gm...>]

Just a suggestion, but why not provide pre-compiled install packages
for Linux so users wouldn't have to compile it themselves? Maybe you
don't have enough users on Linux to justify the work, I don't know.
But it might save everybody time in the long run. And some users who
don't have a programming background may not have the expertise to
compile it themselves.

At the very least, I'd update the install instructions in the Nyquist
manual. For example, the 'setenv' command is only available in some
Unix/Linux shells. On others, you have to use the 'export' command.
It's not a big deal if you know Unix or Linux well enough, but it
might be a problem for inexperienced users. And I'd also add a list of
the tools needed to compile Nyquist; you can't assume that they will
be automatically included in all Linux distributions, as Raymond seems
to think. I'm using EasyPeasy, a trimmed-down version of Ubuntu for
small netbooks, which doesn't include a lot of the development tools
needed to compile Nyquist (although I can download and install them,
of course).

As for the header file, it may be that newer compilers have the
contents of stdio.h "hard-wired" into them, but in the old days, you
had to include the header file or take the chance that the compiler
would make some invalid assumptions about the functions declared in
it. Personally, I think it's still better to include the header
explicitly, even if it does compile without it on some systems. Maybe
you could suggest this to the STK folk.

As for myself, I've downloaded the missing development tools, but I'm
still getting a compile error about a missing library ('asound'). I'll
try to figure it out, but if I can't, I'll post details later.

Thanks for your help.

On Sat, Oct 2, 2010 at 1:33 AM, Roger Dannenberg <rb...@cs...> wrote:
>  There was a discussion here about some undeclared functions such as
> "fopen" in Nyquist. My local copy of nyqstk/src/FileRead.cpp has been
> modified by adding
> #include <stdio.h>
> before
> #include <sys/stat.h>
>
> I think the change was put in by some Audacity folks to reduce some
> warning messages, but apparently with some compilers (or some
> configurations) a missing declaration is an error. This file comes from
> STK, and I try to avoid changing STK code so that it will be easier to
> upgrade, but in this case it really needs the include.
>
> I was signed up to get digests, and I guess it took almost a year to
> make a digest's worth of stuff. If you're reading this in 2011, maybe
> you should ask me to change your settings. (I just changed mine -- sorry
> I wasn't getting messages more promptly.)
>
> Finally, Edgar, I manually put you on the list. I hope that works for
> you. I have no idea why you weren't able to sign up yourself.
>
> While I'm writing, I'll mention that I'm going to do some work on
> Nyquist between now and January to get ready for my class. Among other
> things, Nyquist doesn't work on some systems without an upgrade of
> PortAudio, and Nyquist Makefiles are not set up for 64-bit machines.
> (Nyquist will not run on 64-bit instruction sets without a lot of work,
> but I can at least provide Makefiles that generate 32-bit code even when
> the native architecture is 64-bit.) I've done this and it seems to work
> fine, but the changes are not in the release. There are a few other
> things that are broken. Let me know (or remind me) if there are other
> fixes I should look into.
>
> -Roger
>
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> Nyquist-users mailing list
> Nyq...@li...
> https://lists.sourceforge.net/lists/listinfo/nyquist-users
>

[Nyquist-users] compiling nyquist and mailing list issues

[Roger D. <rb...@cs...>]

  There was a discussion here about some undeclared functions such as 
"fopen" in Nyquist. My local copy of nyqstk/src/FileRead.cpp has been 
modified by adding
#include <stdio.h>
before
#include <sys/stat.h>

I think the change was put in by some Audacity folks to reduce some 
warning messages, but apparently with some compilers (or some 
configurations) a missing declaration is an error. This file comes from 
STK, and I try to avoid changing STK code so that it will be easier to 
upgrade, but in this case it really needs the include.

I was signed up to get digests, and I guess it took almost a year to 
make a digest's worth of stuff. If you're reading this in 2011, maybe 
you should ask me to change your settings. (I just changed mine -- sorry 
I wasn't getting messages more promptly.)

Finally, Edgar, I manually put you on the list. I hope that works for 
you. I have no idea why you weren't able to sign up yourself.

While I'm writing, I'll mention that I'm going to do some work on 
Nyquist between now and January to get ready for my class. Among other 
things, Nyquist doesn't work on some systems without an upgrade of 
PortAudio, and Nyquist Makefiles are not set up for 64-bit machines. 
(Nyquist will not run on 64-bit instruction sets without a lot of work, 
but I can at least provide Makefiles that generate 32-bit code even when 
the native architecture is 64-bit.) I've done this and it seems to work 
fine, but the changes are not in the release. There are a few other 
things that are broken. Let me know (or remind me) if there are other 
fixes I should look into.

-Roger

Re: [Nyquist-users] Compiling Nyquist on Linux

[Raymond M. <la...@gm...>]

On October 1, 2010 11:39:52 am you wrote:
> Correct me if I'm wrong, but if the include statement is missing from
> the CPP file, the compiler isn't even going to look for the header
> file. It doesn't matter where it is. Have you tried compiling what's
> in the zip file lately?

My point is that I do not think the original developer put this out without it 
working for him. But that does not mean it will work for everyone else, so it 
is a bug. And I did have a problem with some version of it not compiling until 
I took into account my own systems setup.

Plus, I have had this experience with some other projects. So regardless of 
the compilation taking into account header files, the missing functions could 
be in a completely different library that uses a different header on certain 
systems. I have actually seen this happen, even though it is non-portable, 
non-standard for whatever reason.

All you can do is fix it to run for yourself until the project developer in 
charge sees fit to make it work better. I was actually interested in helping fix 
some problems months ago, but since I did not receive responses to my own 
inquiries these have languished. AFAIK, the project owner is busy with other 
work and has not been able to get back to this.

So just understand, a function may be in a different lib with a different header 
than you expect depending on where it was originally compiled.

Raymond

Re: [Nyquist-users] Compiling Nyquist on Linux

[David <dfk...@gm...>]

Correct me if I'm wrong, but if the include statement is missing from
the CPP file, the compiler isn't even going to look for the header
file. It doesn't matter where it is. Have you tried compiling what's
in the zip file lately?

David.

On Fri, Oct 1, 2010 at 10:40 AM, Raymond Martin <la...@gm...> wrote:
> On October 1, 2010 09:57:55 am you wrote:
>> Actually, with all due respect, I beg to differ. I think the include
>> statement is missing from the source code. Once I added it, it
>> compiled without any errors (only warnings). I didn't have to add
>> anything to the include path or make any changes to environment
>> variables or compiler options.
>
> Yes, but the environment where it was originally compiled may have a different
> setup that somehow puts that in its path. I had other experiences trying to
> compile C++ code on Mandriva and the headers were in a different place than
> expected. Once the path was set to account for this it worked. So the original
> environment may have it set so that it does work, even though it may be
> technically incorrect in terms of portability (which can be a bug).
>
> Raymond
>

Re: [Nyquist-users] Compiling Nyquist on Linux

[Raymond M. <la...@gm...>]

On October 1, 2010 09:57:55 am you wrote:
> Actually, with all due respect, I beg to differ. I think the include
> statement is missing from the source code. Once I added it, it
> compiled without any errors (only warnings). I didn't have to add
> anything to the include path or make any changes to environment
> variables or compiler options.

Yes, but the environment where it was originally compiled may have a different 
setup that somehow puts that in its path. I had other experiences trying to 
compile C++ code on Mandriva and the headers were in a different place than 
expected. Once the path was set to account for this it worked. So the original 
environment may have it set so that it does work, even though it may be 
technically incorrect in terms of portability (which can be a bug).

Raymond

Re: [Nyquist-users] Compiling Nyquist on Linux

[David <dfk...@gm...>]

Actually, with all due respect, I beg to differ. I think the include
statement is missing from the source code. Once I added it, it
compiled without any errors (only warnings). I didn't have to add
anything to the include path or make any changes to environment
variables or compiler options.

As for installing the missing software, I'm not home at the moment, so
I can't do that "now". But I will later.

Thanks.

On Fri, Oct 1, 2010 at 9:36 AM, Raymond Martin <la...@gm...> wrote:
> On September 30, 2010 10:03:58 pm David wrote:
>> ...
>>
>> I'm no expert in C/C++, I haven't used it for a while, but I believe
>> the declarations for fopen(), etc., are in <stdio.h>. Once I added an
>> include statement for <stdio.h> the compile errors went away, although
>> I'm still getting some other errors:
>
> There are some difference on systems as to where certain headers/libs can be
> located. That seems to be the issue (not having the same setup as where the
> code was developed).
>
>>
>> cd liblo; ./autogen.sh --enable-static --disable-shared
>>
>> **Error**: You must have `autoconf' installed.
>> Download the appropriate package for your distribution,
>> or get the source tarball at ftp://ftp.gnu.org/pub/gnu/
>>
>> **Error**: You must have `libtool' installed.
>> You can get it from: ftp://ftp.gnu.org/pub/gnu/
>>
>> **Error**: You must have `automake' installed.
>> You can get it from: ftp://ftp.gnu.org/pub/gnu/
>> make: *** [liblo/config.h] Error 1
>>
>> Seems I need to install something else, but I'm not sure what package
>> these programs might be in. Any suggestions? I'd prefer to just
>> install a package, rather than have to compile from source. I'm kind
>> of lazy that way.
>
> Well, obviously you need to install autoconf, libtool, and automake, which are
> default tools in the GNU toolchain that are available for any Linux distro.
>
> Check your package manager (e.g., synaptic, etc.) and repositories it is set
> up for.
>
> Without those packages you won't be compiling any other C/C++ that need the
> same.
>
> Go do that now.
>
> Raymond
>
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> Nyquist-users mailing list
> Nyq...@li...
> https://lists.sourceforge.net/lists/listinfo/nyquist-users
>

Re: [Nyquist-users] Compiling Nyquist on Linux

[Raymond M. <la...@gm...>]

On September 30, 2010 10:03:58 pm David wrote:
> ...
> 
> I'm no expert in C/C++, I haven't used it for a while, but I believe
> the declarations for fopen(), etc., are in <stdio.h>. Once I added an
> include statement for <stdio.h> the compile errors went away, although
> I'm still getting some other errors:

There are some difference on systems as to where certain headers/libs can be 
located. That seems to be the issue (not having the same setup as where the 
code was developed).

> 
> cd liblo; ./autogen.sh --enable-static --disable-shared
> 
> **Error**: You must have `autoconf' installed.
> Download the appropriate package for your distribution,
> or get the source tarball at ftp://ftp.gnu.org/pub/gnu/
> 
> **Error**: You must have `libtool' installed.
> You can get it from: ftp://ftp.gnu.org/pub/gnu/
> 
> **Error**: You must have `automake' installed.
> You can get it from: ftp://ftp.gnu.org/pub/gnu/
> make: *** [liblo/config.h] Error 1
> 
> Seems I need to install something else, but I'm not sure what package
> these programs might be in. Any suggestions? I'd prefer to just
> install a package, rather than have to compile from source. I'm kind
> of lazy that way.

Well, obviously you need to install autoconf, libtool, and automake, which are  
default tools in the GNU toolchain that are available for any Linux distro.

Check your package manager (e.g., synaptic, etc.) and repositories it is set 
up for.

Without those packages you won't be compiling any other C/C++ that need the 
same.

Go do that now.

Raymond

[Nyquist-users] Compiling Nyquist on Linux

[David <dfk...@gm...>]

Hi!

I'm trying to compile the latest version of Nyquist under Ubuntu using
gcc 4.4.3 and I was getting some compile errors:

nyqstk/src/FileRead.cpp: In destructor ‘virtual Nyq::FileRead::~FileRead()’:
nyqstk/src/FileRead.cpp:55: error: ‘fclose’ was not declared in this scope
nyqstk/src/FileRead.cpp: In member function ‘void Nyq::FileRead::close()’:
nyqstk/src/FileRead.cpp:60: error: ‘fclose’ was not declared in this scope
nyqstk/src/FileRead.cpp: In member function ‘void
Nyq::FileRead::open(std::string, bool)’:
nyqstk/src/FileRead.cpp:77: error: ‘fopen’ was not declared in this scope
nyqstk/src/FileRead.cpp:89: error: ‘fread’ was not declared in this scope
etc.

Someone had the same problem back in February, but I think the cause
of the problem is different than what was suggested in a reply. Here
are the include statements in FileRead.cpp:

#include "string.h"
#include "FileRead.h"
#include <sys/stat.h>
#include <sys/types.h>
#include <string.h>
#include <cmath>

I'm no expert in C/C++, I haven't used it for a while, but I believe
the declarations for fopen(), etc., are in <stdio.h>. Once I added an
include statement for <stdio.h> the compile errors went away, although
I'm still getting some other errors:

cd liblo; ./autogen.sh --enable-static --disable-shared

**Error**: You must have `autoconf' installed.
Download the appropriate package for your distribution,
or get the source tarball at ftp://ftp.gnu.org/pub/gnu/

**Error**: You must have `libtool' installed.
You can get it from: ftp://ftp.gnu.org/pub/gnu/

**Error**: You must have `automake' installed.
You can get it from: ftp://ftp.gnu.org/pub/gnu/
make: *** [liblo/config.h] Error 1

Seems I need to install something else, but I'm not sure what package
these programs might be in. Any suggestions? I'd prefer to just
install a package, rather than have to compile from source. I'm kind
of lazy that way.

Thanks.

Re: [Nyquist-users] Errors while compiling Nyquist 3.03 and CVS HEAD

[edgar <edg...@we...>]

Raymond Martin wrote:

 > The problems you are having are related to C/C++ headers not being
 > found in the expected places. Those "f" functions are part of
 > standard C/C++ libraries. Those are probably not being located in
 > the right places. Maybe Nyquist has the "include" for the relevant
 > files looking at the wrong place or your distro is putting them
 > into a non-standard location. Had a similar problem on Mandriva
 > about a year ago, but it does it somewhat differently from your
 > I expect.
 >
 > Adjust the "include" paths.

Thanks, and yes, one of the reasons why it didn't work is definitely
my poor C/C++ knowledge. I should have identified "fopen" and friends
as standard C++ i/o functions myself, that's true, and I apologize
for my rather stupid quesion ... but:

If I'm adding:

#include <cstdio>

to the include section in "nyquist/nyqstk/src/FileRead.cpp" I can
compile Nyquist-3.03 as well as CVS HEAD without problems.

The reason seems not to be that the Ubuntu standard C/C++ includes
are not found, instead Nyquist seems to make assumptions which are
not fulfilled on my system.

I would be willing to do further investigations, but again would
need some assistance from a more experienced C/C++ programmer.

However, thanks to Raymond Martin's advice Nyquist is working again.

Thanks,

- edgar



P.S.:

I still do not get copies of the mails on this list. I had
un-subscribed/re-subscribed to this list several times in the past
few years, but with no effect. This is the only list of approx.
20 SF-lists I'm subscribed, which doesn't send me copies.

Maybe the maintainer of this list could please have a look at this?








-- 
The author of this email does not necessarily endorse the following
advertisements, which are the sole responsibility of the advertiser:

Re: [Nyquist-users] Errors while compiling Nyquist 3.03 and CVS HEAD

[Raymond M. <la...@gm...>]

On February 21, 2010 11:47:34 pm edgar wrote:
> Hi Roger and all others on the Nyquist users list
> 
> I'm sorry to tell but I'm unable to compile Nyquist (CMU version) on
> Ubuntu 9.10, neither Nyquist 3.03 nor CVS HEAD, both version produce
> exactly the same errors:
> 
> ... no errors in the lines before (I've looked very hard), but suddenly:
> 
> g++ -c nyqstk/src/FileRead.cpp -o nyqstk/src/FileRead.o
>      -DOSC -DCMTSTUFF -DPA_LITTLE_ENDIAN -O2 -Inyqsrc -Itran -Ixlisp
>      -Isys/unix -Icmt -Iffts/src -Inyqstk/include -Inyqstk
>      -Iportaudio/pa_common -Iliblo -Inylsf -DHAVE_LIBPTHREAD=1
>      -D_FILE_OFFSET_BITS=64  -DPA_USE_ALSA=1
>      -DSTK_NYQUIST -DUSE_VSPRINTF -DHAVE_CONFIG_H
> nyqstk/src/FileRead.cpp: In destructor 'virtual
> Nyq::FileRead::~FileRead()': nyqstk/src/FileRead.cpp:55: error: fclose was
> not declared in this scope nyqstk/src/FileRead.cpp: In member function
> 'void Nyq::FileRead::close()': nyqstk/src/FileRead.cpp:60: error: fclose
> was not declared in this scope nyqstk/src/FileRead.cpp: In member function
> 'void
> Nyq::FileRead::open(std::string, bool)':
> nyqstk/src/FileRead.cpp:77: error: fopen was not declared in this scope
> nyqstk/src/FileRead.cpp:89: error: fread was not declared in this scope
> nyqstk/src/FileRead.cpp:99: error: fseek was not declared in this scope
> nyqstk/src/FileRead.cpp:100: error: fread was not declared in this scope
> 
> ... continues ...

The problems you are having are related to C/C++ headers not being found in 
the expected places. Those "f" functions are part of standard C/C++ libraries. 
Those are probably not being located in the right places. Maybe Nyquist has 
the "include" for the relevant files looking at the wrong place or your distro 
is putting them into a non-standard location. Had a similar problem on 
Mandriva about a year ago, but it does it somewhat differently from your I 
expect.

Adjust the "include" paths.

Regards,

Raymond

[Nyquist-users] Errors while compiling Nyquist 3.03 and CVS HEAD

[edgar <edg...@we...>]

Hi Roger and all others on the Nyquist users list

I'm sorry to tell but I'm unable to compile Nyquist (CMU version) on
Ubuntu 9.10, neither Nyquist 3.03 nor CVS HEAD, both version produce
exactly the same errors:

... no errors in the lines before (I've looked very hard), but suddenly:

g++ -c nyqstk/src/FileRead.cpp -o nyqstk/src/FileRead.o
     -DOSC -DCMTSTUFF -DPA_LITTLE_ENDIAN -O2 -Inyqsrc -Itran -Ixlisp
     -Isys/unix -Icmt -Iffts/src -Inyqstk/include -Inyqstk
     -Iportaudio/pa_common -Iliblo -Inylsf -DHAVE_LIBPTHREAD=1
     -D_FILE_OFFSET_BITS=64  -DPA_USE_ALSA=1
     -DSTK_NYQUIST -DUSE_VSPRINTF -DHAVE_CONFIG_H
nyqstk/src/FileRead.cpp: In destructor 'virtual Nyq::FileRead::~FileRead()':
nyqstk/src/FileRead.cpp:55: error: fclose was not declared in this scope
nyqstk/src/FileRead.cpp: In member function 'void Nyq::FileRead::close()':
nyqstk/src/FileRead.cpp:60: error: fclose was not declared in this scope
nyqstk/src/FileRead.cpp: In member function 'void 
Nyq::FileRead::open(std::string, bool)':
nyqstk/src/FileRead.cpp:77: error: fopen was not declared in this scope
nyqstk/src/FileRead.cpp:89: error: fread was not declared in this scope
nyqstk/src/FileRead.cpp:99: error: fseek was not declared in this scope
nyqstk/src/FileRead.cpp:100: error: fread was not declared in this scope

... continues ...

nyqstk/src/FileRead.cpp:672: error: fseek was not declared in this scope
nyqstk/src/FileRead.cpp:673: error: fread was not declared in this scope
nyqstk/src/FileRead.cpp:686: error: fseek was not declared in this scope
nyqstk/src/FileRead.cpp:687: error: fread was not declared in this scope
nyqstk/src/FileRead.cpp:704: error: fseek was not declared in this scope
nyqstk/src/FileRead.cpp:706: error: fread was not declared in this scope
make: *** [nyqstk/src/FileRead.o] Error 1

affected functions in "nyqstk/src/FileRead.cpp":

destructor "virtual Nyq::FileRead::~FileRead()"
member function "void Nyq::FileRead::close()"
member function "void Nyq::FileRead::open(std::string, bool)"
member function "bool Nyq::FileRead::getWavInfo(const char*)"
member function "bool Nyq::FileRead::getSndInfo(const char*)"
member function "bool Nyq::FileRead::getAifInfo(const char*)"
member function "bool Nyq::FileRead::getMatInfo(const char*)"
member function "void Nyq::FileRead::read(Nyq::StkFrames&, long unsigned 
int, bool)"

In principle always the same five errors:

"fopen" was not declared in this scope
"fclose" was not declared in this scope
"fread" was not declared in this scope
"fseek" was not declared in this scope
"ftell" was not declared in this scope

Are there any devel packages I've missed to install?
"portaudio-dev" and "libsndfile-dev" are installed.

Please tell me if you need more information.

I'm still not sure wether I get copies of the mails on this list,
so in case of doubt write directly to: edgar-rft[at]web.de

But I will also look into the list archives the next few days
if there will be an answer on this post...

Thanks,

- edgar





-- 
The author of this email does not necessarily endorse the following
advertisements, which are the sole responsibility of the advertiser:

[Nyquist-users] PortAudio problems

[<la...@gm...>]

Hi,

I finally got Nyquist to output sound properly. It was partly my fault,
messing around with channels in the code when the version of PortAudio
distributed with Nyquist did not function. Forgot to change it back after
I got sound working.

Anyway, Nyquist works correctly when compiled against the latest stable
version of PortAudio. The version distributed with Nyquist is non-functional
on my system and probably others. When compiled against the latest stable
PortAudio, whether system wide or as a replacement for the distributed 
version, all is well.

I have filed a bug on the project for this.

Regards,

Raymond

[Nyquist-users] Example errors

[<la...@gm...>]

Hi,

I noticed that when reading in the demos examples file and attempting to load
it that it always causes errors. Some of these are due the REPL not being able
to deal with some kind of spacing or white characters in the file. A few
others seem to occur for attempted to set of global *variables*.

Also, in the online version of the manual in Introduction and Overview, 
Sequences the first example is missing commas between function parameters
of note:

play seq(note(c4 i), note(d4 i), note(f4 i), 
         note(g4 i), note(d4 q))

Regards,

Raymond

[Nyquist-users] Incorrect sound issues

[<la...@gm...>]

Hi,

Having gone through a little trouble to get sound out of Nyquist, compiling
against my system's PortAudio instead of the one distributed with the package,
it seems that I cannot get a simple sinusoid output from osc() or sine(). I
get a lower frequency combination tone, like a distorted telephone dial-tone.
The same thing occurs if I read in an audio sample file and play it, like in
the example demos (e.g., ex8()).

I tried a number of different sinusoid samples created in Audacity (all at 
440Hz & 1 sec: 48kHz/44.1Khz, 16/32bit, aiff,wav). All with similar results.
It seems like the sound is decimated/aliased or something.

The PortAudio syncwrite test app has no such problem, also compiled against
my system's libs.

I can try to fix this myself, but just wondering if anyone else has
experienced it before or could point to possible causes.

Thanks.

Raymond

[Nyquist-users] GUI code changes and backward compatibility

[Raymond M. <la...@gm...>]

Hi,

I am thinking about some code changes to the jNyqIDE GUI that might involve aspects
that are only available in Java 5+. Is this going to be a problem?

I know that Java 5+ is not supported on certain platforms (e.g., Win 98 and previous).
Perhaps the program should move to have minimal requirements that are more recent
for future versions.

What do you think?

Regards,

Raymond

[Nyquist-users] Audacity bug posted to wrong list - sorry

[<edg...@we...>]

Hi again,

Sorry, stupidly I posted the Audacity bug to the wrong list.

But nevertheless: If anybody here can confirm the bug
please write to edgar-rft [at] web [dot] de.

I still do not get copies from the mails to this list.

- edgr



-- 
The author of this email does not necessarily endorse the
following advertisements, which are the sole responsibility
of the advertiser:

_______________________________________________________________________
Sensationsangebot verlängert: WEB.DE FreeDSL - Telefonanschluss + DSL
für nur 16,37 Euro/mtl.!* http://dsl.web.de/?ac=OM.AD.AD008K15039B7069a

[Nyquist-users] Audacity_1.3.6-beta Nyquist bug if label tracks visible in the Audacity window

[<edg...@we...>]

Hi Nyquist list,

Audacity 1.3.6-beta Nyquist bug: As soon as a label track is visible in
the Audacity window, Nyquist plugins do not work correctly any more.

Bug reproduction: 

1. I create a Audacity waveform track e.g. via "Generate > Tone"

2. I mark a piece of the waveform and apply an Audacity Nyquist effect,
e.g. "Effect > Utility > Mixer > Cross Fade In" and it works correctly.

3. Now I add a label track via "Tracks > Add new > Label track".

4. If I now apply "Cross Fade In" again, the old piece of sound in the
Audacity waveform track doesn't get replaced by the new sound, instead
the new sound gets inserted at the beginning of the selection and
everything afterwards gets (optically) shifted to the right.

This bug can be observed with all Nyquist plugins, even with code typed
into the "Nyquist Prompt" window but only if a label track is wisible
in the Audacity window.

As soon as I remove all label tracks, Nyquist seems to work correctly again.

This bug was reported by a user in the german Audacity forum. I can
reproduce the bug under Windows XP Pro SP2. I still haven't tested the
bug with Audacity under Linux or Mac.

Can anybody confirm this behaviour?

- edgar








-- 
The author of this email does not necessarily endorse the
following advertisements, which are the sole responsibility
of the advertiser:

__________________________________________________________________
Deutschlands größte Online-Videothek schenkt Ihnen 12.000 Videos!*
http://entertainment.web.de/de/entertainment/maxdome/index.html

[Nyquist-users] Compile Problems on Fedora 9

[Steven J. <pl...@gm...>]

I just updated to Fedora 9 and ran into compilation problems with
Nyquist 3.01. Specifically various standard c functions were not
defined for the following files:

strncmp in nyqstk/src/FileRead.cpp

malloc, calloc and free in nyqstk/src/Stk.cpp

calloc and free in nyqstk/src/Modal.cpp

The fix is easy:

add #include <string.h>  to FileRead.cpp

add #include <stdlib.h> to both Stk.cpp and Modal.cpp


I apologize for cross posting,  I'm not sure my account to
nyquist-users is active.

[Nyquist-users] snd-biquad inadvertently renamed to snd-biquadfilt

[Roger D. <rb...@cs...>]

The latest release of Nyquist renames the snd-biquad function to 
snd-biquadfilt. This is a mistake, and I will fix it. In the meantime, 
you can put the following in nyinit.lsp or somewhere else before you try 
to evaluate snd-biquad (or many other filters such as lowpass2). -Roger

(setfn snd-biquad snd-biquadfilt)