Linux-audio-user September 2009

linux-audio-user@lists.linuxaudio.org

143 participants
148 discussions

by lanas

All, Until now I was naively thinking that The Source of any package was where 'It' was. Eg. To get, compile and install a package, the web page of the package's project was where to get it. A colleague at work started to seed some doubt. He's totally pro-Debian and one argument is that the Debian people are patching source packages to fix things. And they eventually submit their patches upstream. And some are sometimes rejected, for whatever reasons. Following that thought, then we can say that the Fedora/Red Hat people are no fools either and they also patch source packages to fix things. And they also submit to upstream. And it could be that some of these patches do not make into the upstream package for whatever reasons. And then the SuSE people, the Mandriva people, the 64Studio people ... Would this then mean that actually a distro can be better than another in a slice of time t ? That you would not find that Qjackctl or Ardour (only examples, no bugs in there .. :-) bug if you use distro x over distro y ? What are your opinions on this ? Are any of you believing that using a certain distro brings more stability regarding the applications ? This is not about the integration of all applications into the system/desktop but rather strictly on a software development/bug fix basis. Can one distro be better than another because of the fixes the maintainers of that distro do on the packages ? Cheers.

15 years, 11 months

Re: [LAU] naspro make error

by rosea grammostola

> > Uh, sorry, that's another one... I'm sending you the other missing > file... (you know, the build system won't be like that by release time > and we are waiting for lv2 core r4 to be released before solving all > of this). > > Sorry again for the hassle. > > Stefano > Thanks, solved. How do use naspro and zynjacku/lv2rack to be able to load lv2 and ladspa plugins? \r

15 years, 11 months

Re: [LAU] naspro make error

by rosea grammostola

Stefano D'Angelo wrote: > 2009/9/26 rosea grammostola <rosea.grammostola(a)gmail.com>: > >> Nedko Arnaudov wrote: >> >>> rosea grammostola <rosea.grammostola(a)gmail.com> writes: >>> >>> >>> >>>> Can someone tell me how to use naspro with lv2rack to be able to also use >>>> ladspa and dssi? >>>> >>>> >>> According to daste, you need naspro from the mercurial repo. I use the >>> hg version too. You also need git zynjacku. naspro and zynjacku talk >>> each other at runtime so the build order is not important. >>> >>> >>> >> Ok. thanks >> >> With the hg version I get this error: >> >> naspro/naspro-bridges-bad$ make >> make ladspa-bridge >> make[1]: Entering directory `/home/d/4home/svn/naspro/naspro-bridges-bad' >> cd ladspa && make && cd .. >> make[2]: Entering directory >> `/home/d/4home/svn/naspro/naspro-bridges-bad/ladspa' >> make[2]: Nothing to be done for `all'. >> make[2]: Leaving directory >> `/home/d/4home/svn/naspro/naspro-bridges-bad/ladspa' >> make[1]: Leaving directory `/home/d/4home/svn/naspro/naspro-bridges-bad' >> make dssi-bridge >> make[1]: Entering directory `/home/d/4home/svn/naspro/naspro-bridges-bad' >> cd dssi && make && cd .. >> make[2]: Entering directory >> `/home/d/4home/svn/naspro/naspro-bridges-bad/dssi' >> gcc -O2 -ansi -pedantic -Wall -fPIC -shared -ldl descriptor.c descriptor.h >> lv2api.c lv2api.h manifest.c pluglib.c pluglib.h \ >> -lnacore -lasound -o dssi.so >> lv2api.c:20:25: error: lv2_uri_map.h: No such file or directory >> lv2api.c:21:23: error: lv2_event.h: No such file or directory >> lv2api.c:42: error: expected specifier-qualifier-list before >> ‘LV2_Event_Feature’ >> lv2api.c: In function ‘_nadssi_lv2api_instantiate’: >> lv2api.c:59: error: ‘LV2_URI_Map_Feature’ undeclared (first use in this >> function) >> lv2api.c:59: error: (Each undeclared identifier is reported only once >> lv2api.c:59: error: for each function it appears in.) >> lv2api.c:59: error: ‘lv2_uri_map_feat’ undeclared (first use in this >> function) >> lv2api.c:60: warning: ISO C90 forbids mixed declarations and code >> lv2api.c:67: error: ‘struct instance’ has no member named ‘lv2_ev_feat’ >> lv2api.c:78: error: ‘struct instance’ has no member named ‘lv2_ev_feat’ >> lv2api.c:83: error: ‘struct instance’ has no member named ‘lv2_ev_feat’ >> lv2api.c:99: error: ‘struct instance’ has no member named ‘alsa_ev_parser’ >> lv2api.c:104: error: ‘struct instance’ has no member named ‘alsa_ev_parser’ >> lv2api.c:112: error: ‘struct instance’ has no member named ‘alsa_ev_parser’ >> lv2api.c: In function ‘_nadssi_lv2api_connect_port’: >> lv2api.c:140: error: ‘struct instance’ has no member named ‘lv2_ev_buf’ >> lv2api.c:140: error: ‘LV2_Event_Buffer’ undeclared (first use in this >> function) >> lv2api.c:140: error: expected expression before ‘)’ token >> lv2api.c: In function ‘_nadssi_lv2api_run’: >> lv2api.c:175: error: ‘LV2_Event’ undeclared (first use in this function) >> lv2api.c:175: error: ‘lv2_ev’ undeclared (first use in this function) >> lv2api.c:176: warning: ISO C90 forbids mixed declarations and code >> lv2api.c:186: error: ‘struct instance’ has no member named ‘lv2_ev_buf’ >> lv2api.c:187: error: ‘struct instance’ has no member named ‘dssi_evs’ >> lv2api.c:189: error: ‘struct instance’ has no member named ‘lv2_ev_buf’ >> lv2api.c:190: error: ‘struct instance’ has no member named ‘dssi_evs’ >> lv2api.c:192: error: expected expression before ‘)’ token >> lv2api.c:200: error: ‘struct instance’ has no member named ‘lv2_ev_feat’ >> lv2api.c:201: error: ‘struct instance’ has no member named ‘lv2_ev_feat’ >> lv2api.c:207: error: ‘struct instance’ has no member named ‘alsa_ev_parser’ >> lv2api.c:211: error: ‘struct instance’ has no member named ‘alsa_ev_parser’ >> lv2api.c:231: error: ‘struct instance’ has no member named ‘dssi_evs’ >> lv2api.c:234: error: ‘struct instance’ has no member named ‘dssi_evs’ >> lv2api.c: In function ‘_nadssi_lv2api_cleanup’: >> lv2api.c:259: error: ‘struct instance’ has no member named ‘alsa_ev_parser’ >> manifest.c:12:30: error: lv2_dyn_manifest.h: No such file or directory >> manifest.c:26: error: expected ‘)’ before ‘*’ token >> manifest.c:67: error: expected ‘)’ before ‘handle’ >> manifest.c:81: error: expected ‘)’ before ‘handle’ >> manifest.c:100: error: expected ‘)’ before ‘handle’ >> pluglib.c: In function ‘pluglib_load’: >> pluglib.c:59: warning: dereferencing type-punned pointer will break >> strict-aliasing rules >> make[2]: *** [dssi.so] Error 1 >> make[2]: Leaving directory >> `/home/d/4home/svn/naspro/naspro-bridges-bad/dssi' >> make[1]: *** [dssi-bridge] Error 2 >> make[1]: Leaving directory `/home/d/4home/svn/naspro/naspro-bridges-bad' >> make: *** [all] Error 2 >> >> >> >> I have this installed: >> >> i liblv2dynparam1-dev - lv2dynparam is a LV2 plugin interface extension >> i A liblv2dynparamhost1-1 - LV2 plugin interface extension - host >> i A liblv2dynparamplugin1-0 - LV2 plugin interface extension - plugin >> v lv2-plugin - >> i lv2core - The LV2 audio plugin specification >> > > Well, you miss LV2 URI map and LV2 event hedears... > > http://lv2plug.in/docs/index.php?title=URI_Map > http://lv2plug.in/docs/index.php?title=EventPort Thanks, where should I place the missing *.h files? \r

15 years, 11 months

naspro make error

by rosea grammostola

Hi, Can someone tell me how to use naspro with lv2rack to be able to also use ladspa and dssi? BTW I get an error when building the modules: Configuration summary --------------------- Modules to be installed in: /usr/local/lib/NASPRO/modules Build LADSPA module: yes Build audacious module: no Build NDF module: yes configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating src/audacious/Makefile config.status: creating src/ladspa/Makefile config.status: creating src/ndf/Makefile config.status: executing depfiles commands config.status: executing libtool commands d@debian:~/4home/naspro-modules-0.1.1$ make Making all in src make[1]: Entering directory `/home/d/4home/naspro-modules-0.1.1/src' Making all in audacious make[2]: Entering directory `/home/d/4home/naspro-modules-0.1.1/src/audacious' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/d/4home/naspro-modules-0.1.1/src/audacious' Making all in ladspa make[2]: Entering directory `/home/d/4home/naspro-modules-0.1.1/src/ladspa' /bin/bash ../../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"NASPRO\ modules\" -DPACKAGE_TARNAME=\"naspro-modules\" -DPACKAGE_VERSION=\"0.1.1\" -DPACKAGE_STRING=\"NASPRO\ modules\ 0.1.1\" -DPACKAGE_BUGREPORT=\"naspro-devel(a)freelists.org\" -DPACKAGE=\"naspro-modules\" -DVERSION=\"0.1.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_LIBM=1 -I. -ansi -pedantic -Wall -Werror -Wno-strict-aliasing -Wno-attributes -DNACORE_CPU_LITTLE_ENDIAN -I/usr/local/include -g -O2 -MT ladspa_la-module.lo -MD -MP -MF .deps/ladspa_la-module.Tpo -c -o ladspa_la-module.lo `test -f 'module.c' || echo './'`module.c libtool: compile: gcc "-DPACKAGE_NAME=\"NASPRO modules\"" -DPACKAGE_TARNAME=\"naspro-modules\" -DPACKAGE_VERSION=\"0.1.1\" "-DPACKAGE_STRING=\"NASPRO modules 0.1.1\"" -DPACKAGE_BUGREPORT=\"naspro-devel(a)freelists.org\" -DPACKAGE=\"naspro-modules\" -DVERSION=\"0.1.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_LIBM=1 -I. -ansi -pedantic -Wall -Werror -Wno-strict-aliasing -Wno-attributes -DNACORE_CPU_LITTLE_ENDIAN -I/usr/local/include -g -O2 -MT ladspa_la-module.lo -MD -MP -MF .deps/ladspa_la-module.Tpo -c module.c -fPIC -DPIC -o .libs/ladspa_la-module.o libtool: compile: gcc "-DPACKAGE_NAME=\"NASPRO modules\"" -DPACKAGE_TARNAME=\"naspro-modules\" -DPACKAGE_VERSION=\"0.1.1\" "-DPACKAGE_STRING=\"NASPRO modules 0.1.1\"" -DPACKAGE_BUGREPORT=\"naspro-devel(a)freelists.org\" -DPACKAGE=\"naspro-modules\" -DVERSION=\"0.1.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_LIBM=1 -I. -ansi -pedantic -Wall -Werror -Wno-strict-aliasing -Wno-attributes -DNACORE_CPU_LITTLE_ENDIAN -I/usr/local/include -g -O2 -MT ladspa_la-module.lo -MD -MP -MF .deps/ladspa_la-module.Tpo -c module.c -o ladspa_la-module.o >/dev/null 2>&1 mv -f .deps/ladspa_la-module.Tpo .deps/ladspa_la-module.Plo /bin/bash ../../libtool --tag=CC --mode=link gcc -ansi -pedantic -Wall -Werror -Wno-strict-aliasing -Wno-attributes -DNACORE_CPU_LITTLE_ENDIAN -I/usr/local/include -g -O2 -module -avoid-version -shared -rpath /usr/local/lib/NASPRO/modules -L/usr/local/lib -lnaobj -lnacore -ldl -lpthread -lm -o ladspa.la -rpath /usr/local/lib/NASPRO/modules ladspa_la-module.lo -lm libtool: link: gcc -shared .libs/ladspa_la-module.o -L/usr/local/lib /usr/local/lib/libnaobj.so /usr/local/lib/libnacore.so -ldl -lpthread -lm -Wl,-soname -Wl,ladspa.so -o .libs/ladspa.so libtool: link: ( cd ".libs" && rm -f "ladspa.la" && ln -s "../ladspa.la" "ladspa.la" ) make[2]: Leaving directory `/home/d/4home/naspro-modules-0.1.1/src/ladspa' Making all in ndf make[2]: Entering directory `/home/d/4home/naspro-modules-0.1.1/src/ndf' /bin/bash ../../build/ylwrap scanner.l .h scanner.h -- : -L make[2]: *** [scanner.h] Error 1 make[2]: Leaving directory `/home/d/4home/naspro-modules-0.1.1/src/ndf' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/d/4home/naspro-modules-0.1.1/src' make: *** [all-recursive] Error 1

15 years, 11 months

Downsampling via .asoundrc

by Ismael Valladolid Torres

If I define my slave device in .asoundrc with rate 8000, shouldn't I hear audio output by any ALSA application downsampled to that rate? Here that's not the case and audio seems to be heard with whichever frequency the app is using. Find attached my .asoundrc. Cordially, Ismael -- Ismael Valladolid Torres Hey there! ivalladt is using Twitter. <ivalladt(a)gmail.com> http://twitter.com/ivalladt t. 0034912519850 Facebook: http://profile.to/ivalladt m. 0034609884094 (Yoigo) http://groups.to/lamediahostia Google Talk/Jabber/MSN Messenger: ivalladt(a)gmail.com Jaiku/Twitter/Skype/Yahoo!: ivalladt AIM/ICQ: 264472328 GnuPG key: DE721AF4

15 years, 11 months

Re: [LAU] Linux Compatible Audio Interface with ADAT?

by Zachary Klein

> ADAT _is_ 8 channels... (well, 4 if you use more then 96kHz)... I know that. My point was that even a single ADAT port is probably more than I'll need (I could probably make do with less than eight channels), so a card with three or four ports is kind of silly for me. I could justify getting an ADAT card and an ADAT mic preamp (like Behringer's ADA8000), but not if I'm spending $500 on three times that number of inputs I'll need. >And if I remember correctly, there is a "small" rme card with just one adat >io. That's exactly what I was trying to find out. The only ones I am aware of are the 9652 and the 9632, both of which sport multiple ADAT inputs. I'll scout a bit more on RME's stuff. Is it safe to assume that all RME's PCI cards are supported? I've only heard of the 9652 being used with Linux. Zachary Klein

15 years, 11 months

Re: [LAU] Musical Score Editors - some advice for beginners

by David Baron

> MuseScore is still being developed. > > Look at the sourcecode repository..... Nice to hear from you. It has been a while. Is there a new release/beta version around or are things mostly svn at this point. I would love to play with it some more. For the post topic, my comparisons as of now (released versions): complete? formatting? usability? nted almost good quite good uses cairo, fast graphics + pango can export to lilypond if preferred, no options now. author quite good about fixes, new features... mscore very lovely, good, but stability/UI too flexible issues uses qt4, some speed issues for large scores? author quite good about fixes, new features but this is a large and complex work. denemo claimed lilypond wierd, buggy Gtk-GUI feeder for lilypond--if one wants to try lilypond's markup, there is a kate plugin and a python-qt app-frescobaldi. noteedit good lilypond hokey, get's job done no longer maintained, KDE3, runs fine on KDE4 ignore error messages if you get em rosegarden also does scoring. I found it nearly impossible to use for this. It is one of the most complete DAW programs in linux but is now dated, stuck with KDE3, could not run on KDE4. Being converted to QT4? canorus is the other successor to noteedit. Was very incomplete last outing. Anyone heard from them lately?

15 years, 11 months

libflashplayer 64 with pulseaudio

by Patrick Shirkey

Hi, Just submitted a bug report to adobe labs about the library issue with libflashplayer on 64 bit platforms. http://bugs.adobe.com/jira/browse/FP-2811 If others wanted to report their experiences too we may get some action. Cheers. -- Patrick Shirkey Boost Hardware Ltd

15 years, 11 months

Re: [LAU] Hardware VST host?

by Michael Bohle

> On Tue, Sep 22, 2009 at 9:11 AM, Michael Bohle <opendaw(a)jacklab.org> wrote: > > > >> > >> Just wondering, could a hardware VST host be another solution for the > >> 'VST-problem' on Linux? > >> > > > > > > There is no VST problem on Linux - we have Jack, Hydrogen, Zynadd, LADSPA > and LV2. We don't need this shiny bloated closed source VST with all this > uncreative presets. > > Not all VSTs have equivalents on Linux, sadly, especially with regard > to virtual instruments. We have good instruments like Hexter and so on, enough for music production. If it is not enough for you, start to developing other virtual instruments. But don't look back to the proprietary shiny VST preset wonderland, we don't need this. Thats what I've learned in endless discussions with this list and now I believe this is true. Michael > -- Brett > ------------------------------------------------------------ > "In the rhythm of music a secret is hidden; > If I were to divulge it, it would overturn the world." > -- Jelaleddin Rumi > --- original Nachricht Ende ----

15 years, 11 months

Re: [LAU] Musical Score Editors - some advice for beginners

by Werner Schweer

The main purpose of MuseScore is to produce printed scores. Using external synthesizers is on the wish list but has low priority. The plan is to remove the current alsa midi output and replace it with JACK midi. MuseScore is a cross platform application available for Linux, Windows and Mac which complicates things a little bit. If alsa midi output does not work, you can export your score to midi and use an external midiplayer/sequencer. Am Donnerstag 24 September 2009 18:01:10 schrieben Sie: > Werner Schweer <ws(a)seh.de> writes: > > MuseScore is still being developed. > > I'm trying version 0.9.5 and I find it a really nice > application. Although I'm not that confindent with written music, I'm > willing to learn: and musescore has a great appeal in this regard. > > However, I'm not able to connect it with external MIDI synthesizers. I > see alsa midi ports but nothing seems to pass through them (tried > with kmidimon). If I select to use the MIDI out in the preferences the > song won't start at all, while with the internal synth all is working > good. > > Any hints on this problem? > > Best regards, >

15 years, 11 months

← Newer
1
2
3
4
5
6
7
8
...
15
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Linux-audio-user September 2009