Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

7513 discussions

by Patrick Shirkey

Hi, I spent some time today integrating jack support into xwax. I have it registering and creating ports but xwax uses file descriptors for it's i/o's and I'm not sure about the best method to integrate the jack callback system into that. Any pointers for seperating the i/o's from the processing engine so that we can keep alsa/oss support and also have jack too? Cheers. -- Patrick Shirkey - Boost Hardware Ltd. Http://www.boosthardware.com Http://lau.linuxaudio.org - The Linux Audio Users guide ======================================== "Anything your mind can see you can manifest physically, then it will become reality" - Macka B

18 years, 1 month

What hardware is actually used by freebob/ffado users?

by Pieter Palmers

[Appologies for the cross-posting] [Please DON'T use reply-to-all to reply on this email] Hi all, With this I'm hoping to gather some data that can help us in convincing the firewire device manufacturers that we are of some significance to their sales (I'm actually wondering if we are...). So I would like to ask everyone on these lists that has/considers/considered purchasing a firewire audio device if they would be so kind as to answer the following questionnaire. ** Those that have bought one or more firewire devices... * can you provide which device(s), preferably with their GUID (can be found out using gscanbus or sometimes on the device itself) * Do they work with linux? ** Those that considered buying a firewire device: * What device(s) did you consider buying? * What device did you go for in the end (if applicable)? * To what extent was the lack of Linux support a determining factor in your decision? ** Those that consider buying a firewire device: * What device(s) are you consider buying? * How important is Linux support for you? ** any comments? It would be nice if you would reply to this email with the answers inlined with the questions. Please don't reply-to-all but reply to pieterp(a)joow.be in order not to spam the mailing list with these answers. It would also be nice if you left the subject line intact such that I can auto-filter these messages. Again, sorry to bother you guys with this, but it's a bit difficult to convince manufacturers without some decent data. Thanks, Pieter Palmers ffado.org PS: If you know other freebob/ffado users that are not subscribed to these list please pass this mail on.

18 years, 1 month

swh plugins problem/addition

by Georg Holzmann

Hallo Steve, list ! I just noticed, that the "triple band parametric with shelves" LADSPA plugin generates a DC offset (tried version 0.4.15 and 0.4.14). The offset is not always the same: first when I create the plugin, there is no offset. Then I pressed play/stop (in ardour) and the DC offset was here - also the amount of the offset is somehow changing when I play with different parameters (but I did not find out a real correspondens). However, when I use the "Single band parametric" and the shelves alone I don't get an offest (which should be the same code ?). I also made some other small additions to your plugin collection: - single low and high shelving filters (see attached files): they are the same code as in "triple band parametric with shelves", because I often need only a single shelving filter - in the "single band parametric" the slider to change the frequency was linear, I changed this to logarithmic (file attached) Maybe you could include those plugins/changes in your collection, at least for me they are quite usefull. LG Georg

18 years, 1 month

jack_transport question

by Julien Claassen

Hi! I just tried to hack the small beginnings of basic jack_transport support in a midi-sequencer. All it should be capable of is jack_transport_start and stop. I just opened a client (jack_client_open(package,JackNullOption,&status), where status of of jack_status_t. and called jack_transport_locate(client,0) and jack_transport_start(client), before starting the midi-playback and when finished called jack_transport_close(client); Only it won't even locate me to 0, it somehow fails there. Is there anything special I have to consider? any special jack_function, subscribing me elsewhere, opening a seperate thread? Please, does anyone have any ideas on this? Kindest regards Julien -------- Music was my first love and it will be my last (John Miles) ======== FIND MY WEB-PROJECT AT: ======== http://ltsb.sourceforge.net the Linux TextBased Studio guide ======= AND MY PERSONAL PAGES AT: ======= http://www.juliencoder.de

18 years, 1 month

[IGNORE] Message for Ben Loftis

by Fons Adriaensen

Hi Ben, I tried to respond to your message, but there seems to be a problem: ben(a)glw.com Delay reason: Connection reset by peer: smtp.glw.com [66.222.83.247] This has been repeated a number of times now. To answer you question, when using floating point it doesn't make a difference if all signals are at around -40 dB. The ratios will be the same. Ciao, -- FA Follie! Follie! Delirio vano è questo !

18 years, 1 month

How to get correct midi timings from ALSA using the library only

by Carlo Florendo

Hi, (1) I've written a command line MIDI sequencer for lightweight systems and am successful in making it work using the ALSA queue API. However, one drawback of the API is its lack of callback functions. I wish to be able to track events as they are drained by the queue. (2) I know and have successfully worked on a work around whereby the application itself subscribes to the output port so as to see events as they are played. However, I wish to be able to make the sequencer or player work without the use of the ALSA queue nor the workaround in (2). Here's the pseudo-code of the relevant MIDI player routine: for (i = 0; i < number_of_events; i++) { usleep(event[i].delta_time_in_microseconds); output_and_drain_event(event[i]); } This routine gives a non-bearable latency on 2.4 kernels but not so much on 2.6 kernels. How could I get the app to <u|nano>sleep() in the most accurate way in userspace without using the ALSA queue nor the extra subscription to an output port? Or, is there a drain or output routine that supports callbacks? If so, I will be grateful if you could point them out. I seem not to find any output callback routine under the docs. Thank you very much. Best Regards, Carlo -- Carlo Florendo Softare Engineer/Network Co-Administrator Astra Philippines Inc. UP-Ayala Technopark, Diliman 1101, Quezon City Philippines http://www.astra.ph -- The Astra Group of Companies 5-3-11 Sekido, Tama City Tokyo 206-0011, Japan http://www.astra.co.jp

18 years, 1 month

[ANN] lash_wrap - A small LASH wrapper

by Florian Schmidt

Hi, i planned to write this for quite a while and finally got to it [though it's not 100% working yet - It's a small program. If experienced unix hackers might look over y use of waitpit i'd be happy :)]: lash_wrap It's a small program which can be used to "smuggle" non LASH apps into a LASH session provided they meet some requirements: - If they are jack clients, there must be a way of determining the jack client name at startup time - If they are ALSA seq clients the client ID must be known at client startup time or their alsa seq name must be uniquely determined - They must require a way to specify their state via the commandline (e.g. we can tell ardour to load a certain ardour session at startup) So here's how i would smuggle ardour2 into a LASH session: lash_wrap -j ardour -- ardour2 ~/sound/ardour/brazil/brazil.ardour The -j [--jack-name] option tells lash_wrap it must register the jack name "ardour" with LASH. the "--" seperates the options for lash_wrap from the commandline to start the program in question. If we wanted also all ALSA SEQ connections of ardour to be restored we could do: lash_wrap -a ardour -j ardour -- ardour2 ~/sound/ardour/brazil/brazil.ardour The -a [--alsa-name] option specifies a name which will be used to find out the client ID of ardour by regularly searching all ALSA clients until one named "ardour" is found. This ID is then passed to LASH. CAUTION!!!! YOU MIGHT LOSE WORK!! READ ON: - lash_wrap does not care for saving the state of the app in question. So before hitting "close" in your favourite LASH session handler, be sure to save the session in e.g. ardour manually. - if the passed jack or alsa client names do not match for whatever reasons, then connections won't be restored properly. You have been warned. Nonetheless this might be useful for people who otherwise use scripts to manage their audio sessions. Download it here: http://tapas.affenbande.org/lash-wrap Regards, Flo P.S.: Apps like rosegarden are a bit difficult to handle, because they use wrapper scirpts themself that exit immediately and confuse my little app [into thinking the app exited, thus LASH thinks rosegarden has quit, too] -- Palimm Palimm! http://tapas.affenbande.org

18 years, 1 month

Re: [LAD] 2.4 vs 2.6

by arisstotle.52613058＠bloglines.com

--- joq(a)io.com wrote: On 7/20/07, Paul Davis <paul(a)linuxaudiosystems.com> wrote: > > On Fri, 2007-07-20 at 15:31 +0000, arisstotle.52613058(a)bloglines.com > > wrote: > > > I've been working with the 2.6 series kernel now for some time with satisfactory > > > results ie (about 24 msec of latency and solid stability). I chose the 2.6 > > > series because its the latest, and I wouldn't have to patch as much to get > > > support for my hardware (firewire alsa realtime etc...). But I've been reading > > > more and more about how the 2.4 kernels can outperform 2.6 when patched properly, > > > any truth to this? > > > > no truth. its an old data point, no longer valid. that is, assuming we > > are talking about RT-patched 2.6 vs. RT-patched 2.4. if you mean vanilla > > 2.6 vs. RT-patched 2.4, the latter is still better. > > I'm not sure that is even true any more. No recent data, but I tested jackd > extensively in about the 2.6.7 to 2.6.11 time-frame, and found those vanilla > 2.6 kernels quite competitive with RT-patched 2.4 ones, at least on the > machines I was running at the time (all uniprocessors). > > The very early 2.6.x kernels were another story. :-) > -- > joq > _______________________________________________ > Linux-audio-dev mailing list > Linux-audio-dev(a)lists.linuxaudio.org > http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-dev > when you all say RT Patched you mean realtime module built, loaded configured and used by jack correct?

18 years, 1 month

APIC, IRQ's, and realtime

by arisstotle.52613058＠bloglines.com

I've been trying to get a kernel built that will run smoothly, but this is the problem I keep running into, I compile the kernel with SMP processor support, because my processor is a dual core (duh right?) but as some may know, this automatically builds in APIC support. This then leads to unruly IRQ assignments, in my case, a quick cat /proc/interrupts will almost allways show my soundcard being shared with a usb port. of of course, to tease me even more, no assignment on irq 5, i've tried the whole hop-scotch game with the pci slots, nothing works. Help? -Thanks again

18 years, 1 month

FULL audio-signal path

by Andrew Gaydenko

Hi, All! Say, we have such audio-chain: 1. analogue source (say, mic-amp), 2. sound card's line input (let sound card be rme hdsp9632), 3. JackRack (or some other JACKified LADSPA host) with the only LADSPA plugin, let last one be a simple aplifier, 4.1. sound card SPDIF output. 4.2. sound card analogue output, OK, ALSA-driver, HdspMixer, JACK-server and something else are somewhere inside this "user' POV" list. The questions are: - what is full strict list of "audio-entities" steps in such roughly-presented chain? - which formats (float/integer, bitdepth) are used on each step? - which format convertions between steps may be treated as lossless and whcih as "lossness"? And more generally: are there common rules for keeping sound quality intact? I mean only format-related probable issues rather hardware issues like jitter and such. Andrew

18 years, 1 month

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