Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

3 participants
7448 discussions

by Patrick Shirkey

Hi, Does anyone here know why I am seeing this error while loading a kernel module: Unknown symbol __stack_chk_guard (err 0) Unknown symbol __stack_chk_fail (err 0) I can't find anything online that explains the cause of the error in relation to loading kernel modules. -- Patrick Shirkey Boost Hardware Ltd

10 years, 4 months

Ring buffers again

by Will Godfrey

As well as the jack ring buffer, I've looked at several others now, and their example code. The most significant thing that seems to be different about them (from a usage point of view) is the way they handle overflows. However, if the buffer size is defined as an exact multiple of the data type/structure and only complete structures are pushed or popped, would I be right in thinking that you would only need to check on an all/none basis? Have I missed something that could cause a partial data transfer? -- Will J Godfrey http://www.musically.me.uk Say you have a poem and I have a tune. Exchange them and we can both have a poem, a tune, and a song.

10 years, 4 months

Re: [LAD] Call for testing (final): ALSA driver for some firewire devices

by Takashi Sakamoto

Hi Daniel, I notice that I cannot help you without enough logs with which I can realize what happens. At lease, 'verbose' options for aplay/arecord, '#' nodes in /proc/asound/cardX and dmesg. Additionally, would you please add 'LANG=C' when you get output from software. I cannot read Spanish language... > hi, it does not work. Try in following steps: 1. $ arecord /tmp/test.wav -D hw:UFX1604 -c 16 (I expected you receive 'Available formats' output) 2. $ arecord /tmp/test.wav -D hw:UFX1604 -c 16 -f (here the format, maybe S32_LE) (I expected you receive 'rate is not accurate' output) 3. $ arecord /tmp/test.wav -D hw:UFX1604 -c 16 -f (the same above) -r (got rate) (I expected it will run correctly.) I hope you to do these test when killing pulseaudio. The way is here: https://wiki.ubuntu.com/PulseAudio/Log Regards Takashi Sakamoto o-takashi(a)sakamocchi.jp

10 years, 4 months

io GNU/Linux LiveDVD/USB ... You have an update available :)

by Manu Kebab

Hi all, I've uploaded a new iso of "io GNU/Linux", a LiveDVD/USB focused on multimedia (Debian based). Kernel 3.14.4 (64-bit only, 32-bit to come), Jack2 as default sound server, e18 as desktop environment and more nice stuff... For more infos: packages list, screenshots, video, howto etc... Please visit: -> http://manu.kebab.free.fr/iognulinux.html -> https://sourceforge.net/projects/io-gnu-linux/ Enjoy :) MK

10 years, 4 months

Re: [LAD] open ALSA device

by Martin Lohberger

i already have a ladspa-plugin that process my audio data. this works fine without any problems. Due to an adaption of the functionality of my system, i want to add a function that determines if the system works properly. This function should send an audio signal, that is recorded afterwards. And this should also work while no application (aplay, skype etc.) uses alsa. Due to this I want to know if it's possible to use a plugin or an other virtual device that "keeps the floor". 2014-05-20 12:59 GMT+02:00 Martin Lohberger <elektm.alsa(a)gmail.com>: > i already have a ladspa-plugin that process my audio data. this works fine > without any problems. > Due to an adaption of the functionality of my system, i want to add a > function that determines if the system works properly. This function should > send an audio signal, that is recorded afterwards. And this should also > work while no application (aplay, skype etc.) uses alsa. > > Due to this I want to know if it's possible to use a plugin or an other > virtual device that "keeps the floor". > > > 2014-05-20 12:07 GMT+02:00 Fons Adriaensen <fons(a)linuxaudio.org>: > > On Tue, May 20, 2014 at 10:59:46AM +0200, Martin Lohberger wrote: >> > Does somebody of you have experience with ALSA-Devices that get never >> > closed? >> > >> > I want to run a LADSPA-Plugin all the time, even if the application >> above >> > is not running. >> >> Or float in the air if the floor below your feet is >> taken away ? >> >> > Does sombody have an idea how to solve this problem? >> >> A plugin, by definition, needs to be plugged into something else. >> What is it supposed to do without 'the application above' ? >> >> If you want an alsa device which includes a plugin this can >> probably be done using an ~/.asoundrc. >> >> -- >> FA >> >> A world of exhaustive, reliable metadata would be an utopia. >> It's also a pipe-dream, founded on self-delusion, nerd hubris >> and hysterically inflated market opportunities. (Cory Doctorow) >> >> >

10 years, 4 months

Re: [LAD] AES67 + JACK

by Christoph Kuhr

On 17.05.2014 22:15, linux-audio-dev-request(a)lists.linuxaudio.org wrote: > If you happen to have AVB-enabled network cards around, feel free to > hack. I might contribute again in the future (either AVB or AES67, not > sure), but unfortunately don't have any spare time left right now. Hi, my efforts of integrateing some AVB in Linux also waits for some free time. But regarding AVB, there has be an unofficial statement by Cisco: No AVB by Cisco... I suspect this could be somewhat of a show stopper for most manufacturers. AES67 instead gets more popular... Regards, Ck

10 years, 4 months

open ALSA device

by Martin Lohberger

Does somebody of you have experience with ALSA-Devices that get never closed? I want to run a LADSPA-Plugin all the time, even if the application above is not running. Does sombody have an idea how to solve this problem? greets

10 years, 4 months

AES67 + JACK

by Reuben Martin

I'm just now reading about this recent standard. Is this on anybody's radar for possible integration with jack / netjack? It looks like it would provide a very direct and standardized means of bridging jack with proprietary audio transports. Personally interested because it could eventually allow easy integration of Linux based software with a Dante network. -Reuben

10 years, 4 months

Re: [LAD] ladspa: dlopen failed for tap ladspa plugins

by Zlobin Nikita

No dependency on libm. $ ldd /usr/lib/ladspa/tap_echo.so linux-vdso.so.1 => (0x00007fff9dffe000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f9472f16000) /lib64/ld-linux-x86-64.so.2 (0x00007f9473523000) > Okay, seems there is a problem with the libm > (math library). > > Type that and send me the result: > ldd /usr/lib/ladspa/tap_echo.so > > If there is a line like: > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f9d59562000) > > type: > readelf -a /lib/x86_64-linux-gnu/libm.so.6 | grep powf > > and send me the result too. > > If there is no "libm" line, then there is indeed a problem > and we'll try new things. > > How did you install /usr/lib/ladspa/tap_echo.so? > Did you compile yourself? > > Please, answer all my questions so I can help you correctly. > > On 05/18/2014 12:17 PM, Zlobin Nikita wrote: > > Sorry, i did not know about dlerror(). > > Output: > > dlopen failed: /usr/lib/ladspa/tap_echo.so (dlerror: > > /usr/lib/ladspa/tap_echo.so: undefined symbol: __powf_finite) > > dlerror? (null) > > > >> In my code I call dlerror to print the error. > >> What is printed? > >> And can you send me the strace log so I have a look > >> at what's going on? > >> > >> On 05/18/2014 11:15 AM, Zlobin Nikita wrote: > >>> I don't see any changes. In my code following check fails: > >>> if (pvPluginHandle) > >>> Shortly - dlopen returns NULL, so futher struggle is useless. > >>> > >>>> try that: > >>>> > >>>> #include <stdio.h> > >>>> #include <dlfcn.h> > >>>> int main (int argc, char ** argv) > >>>> { > >>>> > >>>> //LADSPAPluginSearch(describePluginLibrary); > >>>> char plugpath [] = "/usr/lib/ladspa/tap_echo.so"; > >>>> void * pvPluginHandle = dlopen(plugpath, RTLD_NOW | RTLD_LOCAL); > >>>> if (pvPluginHandle) dlclose (pvPluginHandle); > >>>> else printf ("dlopen failed: %s (dlerror: %s)\n", > >>>> > >>>> plugpath, dlerror()); > >>>> > >>>> printf("dlerror? %s\n", dlerror()); > >>>> > >>>> return 0; > >>>> > >>>> } > >>>> > >>>> compile with: > >>>> gcc -Wall bug.c -ldl -o bug > >>>> > >>>> then run: > >>>> ./bug > >>>> > >>>> what happens? > >>>> If it fails, can you run: > >>>> strace ./bug 2>&1 > strace.log > >>>> and send me the strace.log file. > >>>> > >>>> and also tell me what "gcc --version" says, > >>>> and what "uname -a" says. > >>>> > >>>> Thanks. > >>>> > >>>> On 05/18/2014 07:07 AM, Zlobin Nikita wrote: > >>>>> Fons: i tried with existing path. > >>>>> Library path is valid - i checked it with ls (doing it for ladspa dir > >>>>> before to get libraries list). > >>>>> > >>>>> Code - includes are omited, line with main() declaration is numbered > >>>>> > >>>>> 30: int main (int argc, char ** argv) > >>>>> { > >>>>> > >>>>> //LADSPAPluginSearch(describePluginLibrary); > >>>>> char plugpath [] = "/usr/lib/ladspa/tap_echo.so"; > >>>>> void * pvPluginHandle = dlopen(plugpath, RTLD_NOW | RTLD_LOCAL); > >>>>> if (pvPluginHandle) dlclose (pvPluginHandle); > >>>>> else printf ("dlopen failed: %s\n", plugpath); > >>>>> return 0; > >>>>> > >>>>> } > >>>>> > >>>>> hermann: thanks, will look > >>>>> > >>>>>> On 05/17/2014 10:15 PM, Zlobin Nikita wrote: > >>>>>>> Backtrace of scanning crash (gdb output) is in attachement (too long > >>>>>>> lines > >>>>>>> in email message are automatically wrapped - don't know, is it good > >>>>>>> to > >>>>>>> violate this). > >>>>>> > >>>>>> You should provide some code, it's hard to help you without seeing > >>>>>> what > >>>>>> your program really does. > >>>>> > >>>>> _______________________________________________ > >>>>> Linux-audio-dev mailing list > >>>>> Linux-audio-dev(a)lists.linuxaudio.org > >>>>> http://lists.linuxaudio.org/listinfo/linux-audio-dev

10 years, 4 months

Re: [LAD] ladspa: dlopen failed for tap ladspa plugins

by Zlobin Nikita

Oops, wrong email destination. Sorry, i did not know about dlerror(). Output: dlopen failed: /usr/lib/ladspa/tap_echo.so (dlerror: /usr/lib/ladspa/tap_echo.so: undefined symbol: __powf_finite) dlerror? (null) > In my code I call dlerror to print the error. > What is printed? > And can you send me the strace log so I have a look > at what's going on? > > On 05/18/2014 11:15 AM, Zlobin Nikita wrote: > > I don't see any changes. In my code following check fails: > > if (pvPluginHandle) > > Shortly - dlopen returns NULL, so futher struggle is useless. > > > >> try that: > >> > >> #include <stdio.h> > >> #include <dlfcn.h> > >> int main (int argc, char ** argv) > >> { > >> > >> //LADSPAPluginSearch(describePluginLibrary); > >> char plugpath [] = "/usr/lib/ladspa/tap_echo.so"; > >> void * pvPluginHandle = dlopen(plugpath, RTLD_NOW | RTLD_LOCAL); > >> if (pvPluginHandle) dlclose (pvPluginHandle); > >> else printf ("dlopen failed: %s (dlerror: %s)\n", > >> > >> plugpath, dlerror()); > >> > >> printf("dlerror? %s\n", dlerror()); > >> > >> return 0; > >> > >> } > >> > >> compile with: > >> gcc -Wall bug.c -ldl -o bug > >> > >> then run: > >> ./bug > >> > >> what happens? > >> If it fails, can you run: > >> strace ./bug 2>&1 > strace.log > >> and send me the strace.log file. > >> > >> and also tell me what "gcc --version" says, > >> and what "uname -a" says. > >> > >> Thanks. > >> > >> On 05/18/2014 07:07 AM, Zlobin Nikita wrote: > >>> Fons: i tried with existing path. > >>> Library path is valid - i checked it with ls (doing it for ladspa dir > >>> before to get libraries list). > >>> > >>> Code - includes are omited, line with main() declaration is numbered > >>> > >>> 30: int main (int argc, char ** argv) > >>> { > >>> > >>> //LADSPAPluginSearch(describePluginLibrary); > >>> char plugpath [] = "/usr/lib/ladspa/tap_echo.so"; > >>> void * pvPluginHandle = dlopen(plugpath, RTLD_NOW | RTLD_LOCAL); > >>> if (pvPluginHandle) dlclose (pvPluginHandle); > >>> else printf ("dlopen failed: %s\n", plugpath); > >>> return 0; > >>> > >>> } > >>> > >>> hermann: thanks, will look > >>> > >>>> On 05/17/2014 10:15 PM, Zlobin Nikita wrote: > >>>>> Backtrace of scanning crash (gdb output) is in attachement (too long > >>>>> lines > >>>>> in email message are automatically wrapped - don't know, is it good to > >>>>> violate this). > >>>> > >>>> You should provide some code, it's hard to help you without seeing what > >>>> your program really does. > >>> > >>> _______________________________________________ > >>> Linux-audio-dev mailing list > >>> Linux-audio-dev(a)lists.linuxaudio.org > >>> http://lists.linuxaudio.org/listinfo/linux-audio-dev

10 years, 4 months

Jump to page:

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-dev