[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Denemo-devel] Removing instrument tuner

From: Nils
Subject: Re: [Denemo-devel] Removing instrument tuner
Date: Fri, 15 Jan 2010 13:24:35 +0100

On Thu, 14 Jan 2010 22:48:46 -0600
Jeremiah Benham <address@hidden> wrote:

> I started looking at the audio input code because I wanted to start thinking 
> about how music games could use pitch detection via microphone. While looking 
> at the code it seems easy allow denemo to be compiled without the instrument 
> tuner. I bring this up because it was mentioned once that it should be 
> removed. I can put #ifdef _WITH_INSTRUMENT_TUNER_ around the code. Then if it 
> is desired to compile --with-instrument-tuner then the feature can be 
> enabled. By default it will be disabled. Should I procede with this? If the 
> code was to be removed completely should a new project be created from the 
> code? All of this does not seem like it would be hard to do. 
> Jeremiah

Independent of what is the default value I think it should be possible to 
deactivate anything except the core if you want. So a portaudio and aubio 
switch would be good, too. And deactivation of the assoziated menu options.

Which default value is a personal question of workflow and taste. The only 
general statements you can make is: everything except core (even lilypond) off 
OR everything on.

Or just a "random" set of features and good documentation (starting IN the 
build system e.g. a configure summary) what is possible, too.
For me this would be: Lilypond, Fluidsynth, Jack on. Rest off.

I don't know how distributions decide what they include in their binary 
versions of Denemo and how optional dependencies work and even how it works for 
some apps that you don't have to recompile to "unlock" new features but just 
have to install the missing lib instead.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]