Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

2 participants
7502 discussions

by Kjetil S. Matheussen

David Robillard: >> Let's just fix the interaction between pulse and jack and be done with >> it. > > That is one solution. > >> It's harmful to suggest that it things are less than they are > > Read the user posts in this thread, or ths post that started it. Things > are as they are. Pretending everything is fantastic when it's not > doesn't help either. > Well, in my opinion, everything really is fantastic right now. Pulseaudio interacts perfectly with jack, pulseaudio doesn't screw up jack in any way (as far as I can remember observing), and all programs using jack, alsa or pulseaudio make sound, simultaneously, without any notable latencies issues with alsa programs. Maybe I was lucky, and I'm probably not a newbie either, but at least I'm not _pretending_ everything is fantastic: it really is. A person coming directly from win/mac probably wouldn't have succeeded though, since jack needed to be configured and I had to manually install the pulseaudio jack sink, edit various files in /etc/, plus perhaps doing other stuff I don't remember anymore.

15 years, 11 months

how i think the gpl works under german jurisdiction

by Jörn Nettingsmeier

standard ianal disclaimer applies. at the risk of starting another zillion-mail thread, here's how i understand the gpl to work under german laws (which should be almost the same in most other countries): a) there is a difference between the license and the copyright. what many people fail to grasp is that the original copyright holder (if it's actually a single person or closed group) is not bound by the license - s/he can choose to distribute the product under any terms s/he sees fit. the license applies only to people re-distributing the product. so it does not make sense to accuse an original author of not providing makefiles, scripts etc, for original code. specifically so in the light of the famous "AS-IS", "WITHOUT FITNESS FOR ANY PARTICULAR PURPOSE" paragraph. ripping out makefiles from re-distributed code is another issue. b) there is a difference between license and evangelist lingo and the actual *contract* that is agreed upon by licensor and licensee. the GPL cannot be viral in the sense that any code that incorporates GPL automatically becomes GPL as well. what happens instead is this: * you use GPL code in your product so as to make your product a "derived work". * by including the GPL code, you are accepting the GPL (as stated in the license). the original author has issued a standing offer for a contract (the GPL), and your use of the code indicates your acceptance. thus, a contract is formed between the original author of that code and yourself (through "konkludentes handeln" or "implied agreement by action" in german legalese, no signing of papers or verbal exchange needed here). * you fail to comply with the GPL by not releasing your product under the same terms. * this means you are violating the license of the included GPL code and are re-distributing the included GPL code without permission. so this is a *breach of contract*, and anything that follows is about the original author's copyright, not your own, or how you license your code. you are now liable to a copyright infringement suit, a cease and desist and possible damages. from this point on, there are two ways to remedy the situation: * you can stick to the original contract and comply with the GPL in the future. since this happens to mean your code has to become GPL as well, it is what causes the myth of the "viral" GPL. * you can rip out the GPL code and continue to use your old licensing terms (after you have settled the infringement suit). all this means that if somebody uses GPL'd code without releasing under GPL him/herself, s/he is in breach of contract with the original author(s). it *does* *not* *mean* that you can now assume the entire package is up for grabs under the terms of the GPL. best, jörn

15 years, 11 months

Running pulseaudio with jack

by Patrick Shirkey

Hi, For those of you who are not subscribed to LAU, yesterday I had time to run a test to see how easy and stable it was to run pulseaudio with jack on Fedora 11. I had a few problems at first but after upgrading to pulseaudio-0.9.16 (latest dev version) I was able to successfully connect Pulseaudio to Jack and play tracks with Totem. It was still a little unstable as I was able to bring pulse down a few times while using the gnome-volume-control applet. However jack was not affected by pulse dying. I did this on a standard Fedora kernel with a 2 core intel and 4 GB RAM. My system load without any audio playing it was around 10%. While playing a track with Totem through PA into Jack was around 20%. This could be due to the visuals that were running at the same time. I was able to listen to a complete 30 minute dj mix without any dropouts while still using my system as usual. I am going to run a full day test of audio playback today. I hope that this has conclusively proven that pulseaudio and jack can exist together and that we are very close to having a complete desktop solution. I don't think any distros are currently shipping pulseaudio-0.9.16 but they will in the next release cycle. IMO all that is needed to complete the system is a sane default configuration which we can all agree on and officially recommend to the packagers. - We have now have a couple of scripts on the net that can be used to load module-null-sink/source to PA, starts jack and then load module-jack-sink/source to PA. These can be added to qjackctl easily but not system wide as several video apps have hooks to load jack if it is not already running. I am doing this now as it is the quickest solution. - The dbus method for jack2 is also useful if it can be given the above logic instead of or aswell as the current which is to disable PA while jack is running. - Another option is that PA listens for jack and handles the sink/source loading internally and automatically. - The final option I can see is a seperate app that can replace jackd, that loads the null sink/source, starts the real jackd and then loads the jack-sink/source. It would also have to take care of the reverse when jack is stopped. I think it would be good if we can get some consensus on the officially endorsed approach. Cheers. -- Patrick Shirkey Boost Hardware Ltd

15 years, 11 months

interesting lwn coverage about latest rt patches

by Jörn Nettingsmeier

hi guys! lwn.net has a very nice article on the progress of -rt in the latest .31 kernel: http://lwn.net/SubscriberLink/345076/aab59b866d6f169d/ (this is otherwise subscribers-only coverage, brought to you by the "free link" feature - if you have some bucks to spare, check out lwn and consider subscribing, their s/n is quite exceptional.) best, jörn

15 years, 11 months

Re: [LAD] Impro-Visor created on sourceforge

by Chris Cannam

On Thu, Aug 6, 2009 at 2:23 PM, drew Roberts<zotz(a)100jamz.com> wrote: > On Thursday 06 August 2009 03:51:30 you wrote: >> The second question becomes broadly irrelevant here if we are >> prepared to accept Bob did convey his intention that the Impro-Visor >> code be GPL'd, but Arnout and I were responding to the blanket "use of >> GPL code makes it GPL" (which would imply the second question above). > > And this I certainly agree with. Use of GPL code does not automatically make > another program GPL. It just gives the author of that code a legal headache > if the new program is not GPL. Yes, exactly. Chris

15 years, 11 months

Re: [LAD] Kim did the switch to Linux

by Ralf Mardorf

Hi Alex :) I'll take the next bus and will reply to this mail only because of the 68000 issue. alex stone wrote: > [snip] > I owned several variations of boxes including > an Amiga (best midi timing on the planet), and my much cherished but > now dead Fairlight. > I started with the C64 and then used the Atari ST (not STe, not TT etc.). I don't know the Amiga, but the Fairlight. Amiga, Atari ST and Fairlight are based on the 68000. As I've written before, I won't argue for an OSS, I don't use privately and I've explained that there are cracks that do, what I've said. I stopped replying to this topic. The C64 and Atari ST don't have any noticeable jitter, I still have those computers, but reasons not to use them any more. Linux with my machine is a PITA for usage with external MIDI equipment. I don't know if this is fine for Windows on my machine, in January I installed Windows and some audio software, but until now I didn't test if I do have jitter with Windows too, I only tried to fix it for my Linux installs. But I was writing because of the averaged user, not because of my trouble. 64 Studio is the only good working alternative I know, other audio distros don't take care about special problems, e.g. that some systems will disconnect clients when using JACK1, for 64 Studio JACK2 is default. I'm able to configure my Suse etc. for rt-audio, an averaged user isn't able to do this. Maybe to be continued, better if not and I'm half off-line now ;). Ralf

15 years, 11 months

A question for power HW experts

by Fons Adriaensen

Hello all, I'm looking for a high performance (e.g. quad core) machine to be used for audio processing (and running Linux of course). Rack mount is preferred but not essential. What would you recommend to look at ? TIA, -- FA Io lo dico sempre: l'Italia è troppo stretta e lunga.

15 years, 11 months

students and copyright

by Fons Adriaensen

DISCLAIMER I don't want to discuss the merits of any particular case. If I refer to Prof. Keller it is only by way of example, and not to suggest he should justify himself on this list. Of course I'm still interested in his views on these matters. END DISCLAIMER Prof. Keller writes 'We employ the students ...'. That would certainly be the case for a post-graduate student who becomes a teaching or research assistant and who receives a stipend from the institute or any of its sponsors. The transfer of copyright is usually stipulated in the contract in this case (and in some cases, it has to be and is not automatic). It is certainly not correct for any normal student who would actually be paying the institute instead of the reverse. In market-economic terms such a student is a customer, not an employee. In that case it would seem morally wrong (to me) if the institute 'grabs' his copyright. And what would be the situation of (again, just an example) Prof. Keller himself ? Certainly he is an employee of his educational institute. Ciao, -- FA Io lo dico sempre: l'Italia è troppo stretta e lunga.

15 years, 11 months

ICMC anyone?

by victor

Hi everyone, changing a bit of the subject in this list, is anyone here going to the ICMC? I'll be in Montreal for a week from 17/08, it'll be nice to meet some of you there. Regards Victor

15 years, 11 months

dbus using up resources

by Patrick Shirkey

Hi, A recent observation has been made of the jack + pulse audio union that it uses up a lot of resources when running. It's not the first report that running pulse + jack causes things to overheat and lockup. The report was posted to the jack-devel list a couple of days ago. According to the original poster it is hald and dbus which are taking on the extra load. To me this sounds like an implementation bug in the jack or pulse code as neither hald or dbus should consume extra resources beyond their standard footprint. Does anyone have an idea of why this could be happening? It's probably a very simple oversight somewhere. I'm gonna spend some time now to test my system and see if I can reproduce it. Cheers. -- Patrick Shirkey Boost Hardware Ltd

15 years, 11 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