Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

7513 discussions

Start a nNew thread

[linux-audio-dev] steve's next plugin?

by Paul Davis

http://www.nytimes.com/2003/05/20/science/20OBSE.html?ex=1054008000&en=82a1…

22 years, 3 months

[linux-audio-dev] Re: Sblive on LAD (was: SBLive again)

by Lukas Degener

Linium wrote: >Hi, > >I saw your request about the crackling noise you get with the sblive card. > >I have such a beast too, and in the past i had problem with full-duplex at >44.1 khz. > >The Sblive work internally at 48khz and work very well at this samplerate >under Alsa, but at 44.1 khz some noise appeared. >May be it is the same problem ? try 48 khz and see if it solves it. > >Note: i don't know if this issue has been adressed now by the Alsa team, so >may be i am writting for nothing... but who know ? :) > >Linium > Just let me say thanks to Linium and others: The problem seems to have disapeared after i made jack use 48khz instead of 44.1khz I have to do some more testing, but it seems i can now drive my apps in full-duplex without major problems. Why the different behaviour of alsa and jack? I guess that was because the app i mainly used for testing (ams) would set the sample rate to 48khz when using alsa and accept the preset rate (44,1khz) when used with jackd. which lead me into the false assumption that there could be something wrong with jack. Glad that's solved! :-) Lukas

22 years, 4 months

[linux-audio-dev] Re: [Alsamodular-devel] subharmonics

by Alfons Adriaensen

On Wed, May 21, 2003 at 03:03:58PM +0200, Matthias Nagorni wrote: > On Wed, 21 May 2003, Lukas Degener wrote: > > > Matthias, is there a special (e.g. technical) reason for limiting the > > range of the sub-harmonics param to [1/1,1/16] ? > > Actualy i could use up (down?) to 1/32 or better 1/64. Will i experience > > any bad surprises if i change this in the code? > > No surprises. Go ahead ! I just thought 4 octaves down were sufficient, > but if you have a good subwoofer and patient neighbours... ;-) Be careful ! If like me you have vintage DC300A ready to deliver a kilowatt, and your system is fully DC coupled, watch out for the funny smell from you speakers..... FA

22 years, 4 months

[linux-audio-dev] new plugins

by Alfons Adriaensen

Hi list, Two new plugins are available at <alsamodular.sf.net>, together with the moogvcf plugin announced earlier. These are: cs_phaser: Similar the CSOund's phaser1 : a series of up to 30 first order allpass filters with modulation and feedback, cs_chorus: The three voice chorus from Sean Costello's "stringphaser" CSOund orchestra. Note: all three plugins (vcf, phaser anc chorus) may be used to generate singing birds :-) Enjoy ! Fons Adriaensen

22 years, 4 months

[linux-audio-dev] SBLive again

by Lukas Degener

Hello, please excuse me posting to both lad and jack-dev, i wasn't sure which one fits better. I am experiencing again what i may call "static crackling noises" when jackd with my sblive. They apear every now and then and go away after some time. The reason why i send this to the jack-dev list too, is that this does not happen when i use the same application (ams in this particular case, but also other jack clients like freqtweak or muse show this behaviour) without jack, i.e. directly interfacing the alsa layer. So could it be that jack does something which sort of provocates this crackling, something that does not happen when using alsa "directly" ? And yes, i am using a VIA chipset, first (on my old mobo) the KT133 and now (new mobo) the KT266. Reading through all kinds of web forums i have found this issues been discussed in length but without a clear result apart of statements like "Don't use SBLive!" or "Don't use VIA mobos!" (maybe both are right, but neither does much to make me feel better :-) ) Does anybody actualy _know_ what the reason for this noises is? Is there anything i can do? Would it help to tweak pci latency timers? I read somewhere that this solved the problem for someone using Win98, but i have to admit that even after reading two HOWTOs on this, i'm not realy understanding what this exactly does. Here are some additional observations i made, maybe this is of help: - After juggeling pci slots a bit, my sblive now uses irq 10 and does not share it with any other device. That did noticable improve the situation, i.e. crackling does apear less frequently. - As described above, the noise starts every now and then (i haven't yet found something that would proofable trigger it). First there are a few clicks and pops, then it becomes more "dense" and soon it sounds like some high frequent crackling. (dropped frames i suppose, lots of them). This lasts till jackd reports an x-run, and that's where it stops abruptly. (So there are situations when xruns become your friend :-) ) BTW, any idea how i could get more "run-time" info on what happens in my machine when this crackling starts? Is there a way to "see" irq activity? - The problem does not seem to be related to system load, it happens even in situations where jackd reports less than 5 percent cpu usage. - Sometimes when i create realy loud noises in ams, which result in hard-clipping somewhere in the signal chain, this sounds quiet similar. But i guess this hardly is related? Hope this wasn't too much of a redundant question. Kind Regards, Lukas

22 years, 4 months

[linux-audio-dev] Static class data and dlopen()

by Alfons Adriaensen

This is not strictly a Linux Audio question, but I encountered this matter in the context of writing LADSPA plugins, so... Imagine you have a C++ class S which has some static data. Derive A from S and use A to create a plugin a.so Derive B from S and use B to create a plugin b.so When a host links (at runtime) with both a.so and b.so, then the static data from S will be created twice (I verified this to be the case). This is what I expected, but it may shock C++ purists, so my question now is this: Is this the 'official' behaviour when loading plugins, or is this something that could change with future version of g++ and the DL libs ? Fons

22 years, 4 months

[linux-audio-dev] Alsa /dev/sequencer stuff

by Ivica Bukvic

Hi all, I was wondering the following: In my app (RTMix) I will be soon implementing multiple midi-input device opens, so that the app can be controlled from as many of the midi controllers simultaneously as possible. One way of devising this was to design a separate thread for every open device (using raw midi /dev/midi etc., although I will be re-implementing that to use ALSA devices directly). However, this might not be the most elegant way of doing this, so what I was wondering is how does the /dev/sequencer correspond to this issue? I mean, does it work the same way like addressing the raw midi ports, are the message formats the same, and most importantly does one SINGULAR /dev/sequencer encompass all of the midi ports that are currently available? I would greatly appreciate any help on this issue, as well as some code examples. Thank you! Sincerely, Ivica Ico Bukvic, composer & multimedia sculptor http://meowing.ccm.uc.edu/~ico

22 years, 4 months

[linux-audio-dev] rtp-midi update ...

by John Lazzaro

[ My apologies if you see this more than once ... --jl ] Hi everyone, I've spent the last few months editing a document that attempts to resolve the "open issues" that were outstanding in the "RTP payload format for MIDI" we've been working on in the AVT working group in the IETF. I believe the I-D that I submitted today: http://www.cs.berkeley.edu/~lazzaro/sa/pubs/txt/current-rtp-midi.txt addresses them all (famous last words :-). So, if you have an interest in sending MIDI over IP networks using RTP (the IETF telephony and content-streaming protocol), but you've been waiting for a mature document before committing to reading through 100 pages of MUSTs and SHOULDs, now is a good time to download the I-D and send along comments and bugs. This document, updated to reflect new comments, will form the basis of the "Last Call" document I submit to the IETF in about a month or so. Thanks again, ------------------------------------------------------------------------- John Lazzaro -- Research Specialist -- CS Division -- EECS -- UC Berkeley lazzaro [at] cs [dot] berkeley [dot] edu www.cs.berkeley.edu/~lazzaro -------------------------------------------------------------------------

22 years, 4 months

Re: [linux-audio-dev] Re: final scratch + native instruments

by Patrick Shirkey

Martin Buechler said >Alas, don't know what OS it was, but if something remains unclear, I >might jump in my pants and go ask them. or you could just let them know about terminatorX and GDam... Nice to know they have open sourced their code though. I hope that means they have made enough money out of the product over the past year that they can afford to make it free and not that they are drawing straws to make enough money to survive. Perhaps they could have been more friendly to us rounds here and we could've promoed them a bit more to our business partners.... -- Patrick Shirkey - Boost Hardware Ltd. Http://www.boosthardware.com Http://www.djcj.org - The Linux Audio Users guide ======================================== Being on stage with the band in front of crowds shouting, "Get off! No! We want normal music!", I think that was more like acting than anything I've ever done. Goldie, 8 Nov, 2002 The Scotsman

22 years, 4 months

Re: [linux-audio-dev] change my email

by CK

I read: > so I'd like to unsubscribe then. how do I do it? stupid question maybe. http://www.linuxdj.com/audio/lad/subscribelad.php3#subscription HTH x -- chris(a)lo-res.org Postmodernism is german romanticism with better http://pilot.fm/ special effects. (Jeff Keuss / via ctheory.com)

22 years, 4 months

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