On Wed, 2014-01-29 at 10:33 -0400, Paul Brossier wrote: > Hi all, > > On 29/01/2014 05:51, Richard Shann wrote: > > I was forgetting about this libaubio problem when I suggested we > > create the release. Unfortunately, I am at a loss to say how we > > should proceed - there is no response so far on the aubio site. We > > could treat it as libsmf, so that we have our own copy of the aubio > > code (we only need to build the library) for use where the external > > version is unavailable. Or we could bracket the aubio-specific parts > > of Denemo with #ifdef _HAVE_AUBIO_ (this would mean no microphone > > input and no opening audio tracks for transcription). > > Sorry I did not document the API changes. I will submit a patch soon to > update denemo to aubio 0.4.0.
That would be great - thank you very much > > > Incidentally, I read that the new aubio version, besides a change of > > API uses the "waf" build system instead of autotools, which is > > apparently causing problems of its own. > > Please let me know any problem it may cause. What I read was on the Debian site; my immediate problem was that "waf" yielded no hits when I looked for a package to install on my (Debian stable) distro. So I guessed I couldn't build the new aubio. But this may just be my misunderstanding of what's involved. Incidentally, I couldn't navigate to the aubio mailing list https://lists.aubio.org/ (I got an "Untrusted Website" page, with no way forward), hence the message I left on the announcement page. Thanks for the prompt reply - glad to hear about the development. It'll be interesting to see how the new code works with that demo of the note onset detection https://vimeo.com/82292569) Richard > > Best, Paul > > > > > > Richard > > > > On Tue, 2014-01-21 at 12:12 +0000, Richard Shann wrote: > >> On Sun, 2014-01-19 at 15:10 +0100, Federico Bruni wrote: > >>> 2014/1/19 Andreas Schneider <[email protected]> If you don't > >>> use that old version of Denemo shipping with the distribution, > >>> you could remove that package and libaubio2 with it. > >>> libaubio-dev contains the development files needed to compile > >>> Denemo, and it's version 0.4.0 as it depends on libaubio4. That > >>> also means > >> > >> ??? I am looking at aubio version 0.4.0 on its website - it says > >> it was released on 17th December, i.e. brand-new. It uses a new > >> API, which Denemo does not support yet. I have asked on the aubio > >> forum if any guidance for upgrading could be given, but now I am > >> having difficulties navigating the aubio site :( so I don't know if > >> there is any response. > >> > >> > >> > >> > >> > >>> that libaubio4 is the one Denemo gets compiled with. > >>> > >>> unfortunately, ardour3 depends on libaubio2, so I cannot remove > >>> it > >> > >> I have also had a dig around on the ardour site, as it would seem > >> amazing that they had re-jigged for aubio 0.4.0 in three days, > >> they list > >> > >> aubio 0.3.2 http://aubio.org/pub/ > >> > >> as a dependency. So I really do not understand what is going on. > >> The aubio website indicates that all the new API has been under > >> wraps before Dec 17th. > >> > >> Richard > >> > >> > >>> > >>> > >>> _______________________________________________ Denemo-devel > >>> mailing list [email protected] > >>> https://lists.gnu.org/mailman/listinfo/denemo-devel > >> > >> > >> > >> _______________________________________________ Denemo-devel > >> mailing list [email protected] > >> https://lists.gnu.org/mailman/listinfo/denemo-devel > > > > > > > _______________________________________________ Denemo-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/denemo-devel
