Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

7501 discussions

Re: [LAD] [LAU] Linux Audio 2012: Is Linux Audio moving forward?

by Patrick Shirkey

On Wed, October 10, 2012 11:33 pm, Ben Loftis wrote: > > I'd pose a different question: > > Is OSX/Win Audio moving _backward_? > > If OSX continues to move towards iOS, and Win continues to move towards > Metro, and Thunderbolt stalls, and screens get smaller, and expansion > ports get scarcer, then Linux might become the de-facto "pro" multimedia > platform simply because the other choices have become too dumbed down. > > Of course _most_ users will be happy with the ease and power of the > tools that will be available on iOS/Metro. And _most_ users is where > the money is, so Apple/Microsoft are chasing the right users. But there > will be some serious users that need a powerful production system with > big screens and big peripherals, and for these users, Linux might > become the standard. > Looking at the recent trade shows it seems that Linux/Unix is the already the hardware standard. I didn't spot hardware running on Apple or M$ OS's but plenty of Linux and Unix platforms. Unfortunately it costs $4000 for a booth here so I probably won't be able to do any promotions at the next event. -- Patrick Shirkey Boost Hardware Ltd

12 years, 8 months

Re: [LAD] [LAU] Linux Audio 2012: Is Linux Audio moving forward?

by Patrick Shirkey

On Thu, October 11, 2012 5:41 am, Dan MacDonald wrote: > Patrick wrote: > >> >> Looking at the recent trade shows it seems that Linux/Unix is the >> already >> the hardware standard. I didn't spot hardware running on Apple or M$ >> OS's >> but plenty of Linux and Unix platforms. >> >> > Which trade show was this? "Integrate" is the biggest A/V trade show in Australia. It's just a baby compared to US or EU offerings though. > I'm unaware of any hardware vendors advertising > or even officially supporting Linux other than RME kinda but their support > seems little more than half-hearted as they apparently don't provide any > support for their drivers which they say on their website are 3rd party so > did they even have any involvement in them at all? Focusrite provide specs > but no Linux drivers or support so I wouldn't count them either. > Just walking around you can see who is using Unix/Linux and who is not. Granted most of it is embedded or SoC but they are definitely not Apple or Mac OS's on the clear majority of the hardware solutions. Unfortunately for us in the proprietary world it's not "cool" to talk about where you get your firmware/software from so no one is promoting that information. When it comes to desktop solutions no one is representing Linux at the trade shows here. Afaik noone is doing anything explicit for Linux Multimedia solutions at any of the US or EU trade shows either. Given that there are several companies on these lists who do go to the trade shows it seems that we are all missing a big opportunity for promotion of the general platform by not capitalising on the "We heart Linux" bandwagon. > I know its not audio related but even HP who's support for Linux is > arguably better or at least on a par with their support for the other two > OS still don't advertise or claim to officially support Linux - even > though > they do. Sad state of affairs - even now in 2012 when we can all safely > say > Linux isn't going away the big corps still like to pretend it doesn't > exist. > Valve just announced that the Linux port for Steam will go live with 15 titles. Intel, AMD and ARM all promote Linux heavily. The entire top level of the movie industry runs on Linux. Harrison is building Linux Hardware Solutions. RME provides Linux support or standards compliant devices. What is missing is a concerted effort to advertise and promote the advances that have been made. We can't rely on the magazine and mainstream news media publishers to do it for us as they are clearly not interested. So we have to do it ourselves which either means paying the publishers for space or blanketing the web with information. Given that we are unlikely to crowd fund advertising the latter is more viable. Considering that we have several thousand LAU people who also just happen to be handy with a computer and the internet that actually works in our favour. Marketing companies spend millions of client dollars on SEO and manage to get a lot done with just a few dedicated people. We have thousands of users and each one of us can build a website or post links in forums and social media to the landing pages that we want to promote. Our sites all link up to each other anyway so it just needs some effort from people around here to spread the links and evangelise the platform. Having some killer content won't go amiss either. Perhaps the professional companies round here have some AV content that they would like to share more widely for promotional purposes? We are actually looking for some content we can turn into a show reel. So if you know of anything that would be suitable please let us know. -- Patrick Shirkey Boost Hardware Ltd

12 years, 8 months

Re: [LAD] [LAU] Linux Audio 2012: Is Linux Audio moving forward?

by Louigi Verona

Now that I am a little less zealous about free software (which is a different discussion anyway), I might just try Renoise out. I am rather tired of tracker interface. Does Renoise have a piano roll? On Wed, Oct 10, 2012 at 9:11 PM, James Mckernon <jmckernon(a)gmail.com> wrote: > On Wed, Oct 10, 2012 at 9:24 AM, Louigi Verona <louigi.verona(a)gmail.com> > wrote: > > Hey fellas! > > > > Would like to present an article I've written. Mostly wrote it to start a > > conversation and hear what others have to say on the subject. > > > > > http://www.louigiverona.ru/?page=projects&s=writings&t=linux&a=linux_progre… > > > > You can comment here or on my textboard (which does not require > > registration). > > > > > > -- > > Louigi Verona > > http://www.louigiverona.ru/ > > > > _______________________________________________ > > Linux-audio-user mailing list > > Linux-audio-user(a)lists.linuxaudio.org > > http://lists.linuxaudio.org/listinfo/linux-audio-user > > > > A smart article - as another 'electronic musician' (by your > definition) using Linux, I'm always interested in your thoughts and > essays on the topic. I agree that things can sometimes look a little > bleak for those hoping to create highly sequenced, > synth-and-effects-based music on Linux, but there are ways and means. > > Incidentally, I wonder if you've ever used Renoise? Not F/OSS, but > runs perfectly well on Linux, and is in some respects sympathetic to > the F/OSS ideology (saves to a simple, open file format, for example). > Anyway, it's the strongest candidate I've found for making sequenced > electronic music per se in LInux. Right now I'm working towards a > workflow of using Renoise as a sequencer to drive simple synthdefs in > Supercollider. > > Cheers, > J > -- Louigi Verona http://www.louigiverona.ru/

12 years, 8 months

Re: [LAD] [LAU] Linux Audio 2012: Is Linux Audio moving forward?

by Louigi Verona

Hello Ben! I'd like to answer your question: Is OSX/Win Audio moving _backward_? In the most general sense my answer would be a no. It is like being in a process of building a house and looking at your neighbour who has already built a house and saying - "hm, his building process seems to be going backward." But I think it is more accurate to say that his building process simply stopped, because the house is already complete. Since day one I have always underlined that I do not think Linux can technically compete with Windows and Mac OS in that many things. Freedom is what gives Linux its benefits. But technical superiority is questionable. It strongly depends on what distro you use, what you do with it, etc. And even if in theory it can be shown that Windows and Mac OS are in many ways technically inferior, the number of users hammering at it surely made it work - not in theory, but in practice. Windows Audio, as opposed to Linux Audio, has all pieces in place - it has sequencers, it has tens of thousands of plugins, hundreds of them high quality, it has software for djs and live performers, just like Linux it has all sorts of very cool experimental applications, which continue to be developed and absolutely no problems with hardware. Mac OSX is even better in the realm of audio. I have many friends who are professional musicians and who use Mac, I've performed with them and I have seen great things that Mac Audio can do - it is incredible. And now, when these platforms have everything a modern musician requires and, while there is always room for improvement and new ideas, there are hardly any pressing needs, they can experiment with Metro, with small screens and with anything they want. They are on a firm base and if needed, all of it can be expanded to anything you want. This is my opinion. Why we stick with Linux? Each has his reasons. Linux is free. Linux surely has some unique workflows, possibilities and apps. But to me the problem is that I can do great ambient on Linux, but I have a difficult time putting together anything else. Doing a house tune, which is a pleasure on Windows, is a very difficult thing on Linux, I've written about it many times. So my dream is to see Linux fulfil the need of a non-experimental electronic musician. On Wed, Oct 10, 2012 at 4:33 PM, Ben Loftis <ben(a)harrisonconsoles.com>wrote: > > I'd pose a different question: > > Is OSX/Win Audio moving _backward_? > > If OSX continues to move towards iOS, and Win continues to move towards > Metro, and Thunderbolt stalls, and screens get smaller, and expansion > ports get scarcer, then Linux might become the de-facto "pro" multimedia > platform simply because the other choices have become too dumbed down. > > Of course _most_ users will be happy with the ease and power of the tools > that will be available on iOS/Metro. And _most_ users is where the money > is, so Apple/Microsoft are chasing the right users. But there will be some > serious users that need a powerful production system with big screens and > big peripherals, and for these users, Linux might become the standard. > > -Ben > > > > > ______________________________**_________________ > Linux-audio-user mailing list > Linux-audio-user(a)lists.**linuxaudio.org<Linux-audio-user(a)lists.linuxaudio.org> > http://lists.linuxaudio.org/**listinfo/linux-audio-user<http://lists.linuxaudio.org/listinfo/linux-audio-user> > -- Louigi Verona http://www.louigiverona.ru/

12 years, 8 months

Re: [LAD] [LAU] Linux Audio 2012: Is Linux Audio moving forward?

by Paul Davis

On Wed, Oct 10, 2012 at 6:09 AM, Dan MacDonald <allcoms(a)gmail.com> wrote: > Hi LV! > > Nice and interesting write up of your experiences and opinions there. I > agree with most all of it except: > > "Saving projects is still a huge problem. In addition to LADISH we do now > have NSM, the Non-Session Manager, which seems like a workable solution, so > we'll see how this works out in the long run. > LMMS seems to be the only game in town for those who want to save full > projects by just clicking "Save" and not having to install and configure a > "session manager". I must admit, by the way, that I have not followed LMMS > recently." > > Saving projects is only tricky if you use the modular approach versus > instrument plugins hence this isn't really a problem for A3 and qtractor. > Aside from LMMS, MusE and sunvox have a few integrated instruments so they > don't have this problem either (if you stick to the built-in synths for > Muse only - sunvox doesn't handle plugins) and pretty soon MusE should gain > native VST support to further improve this situation. > > Your article has reminded me of my one and only JACK complaint/ feature > (yep - just one!!!) request which I filed a couple of years ago now but is > still to be addressed: > > http://trac.jackaudio.org/ticket/202 > > I'm surprised others haven't been asking for more descriptive 'device > busy' error messages from JACK as for many years this has been my only > issue with JACK - it doesn't start and you don't know what process is > preventing it doing so. Quite often I'll not bother doing the detective > work and just reboot but that is hardly ideal so I think this small > addition would make JACK (and qjackctl) and as a result Linux audio much > more user friendly. > > Your thoughts Mr Davis? > current jack1 (released months or years ago): if (snd_pcm_open (&driver->playback_handle, playback_alsa_device, SND_PCM_STREAM_PLAYBACK, SND_PCM_NONBLOCK) < 0) { switch (errno) { case EBUSY: current_apps = discover_alsa_using_apps (); if (current_apps) { jack_error ("\n\nATTENTION: The playback device \"%s\" is " "already in use. The following applications " " are using your soundcard(s) so you should " " check them and stop them as necessary before " " trying to start JACK again:\n\n%s", playback_alsa_device, current_apps); free (current_apps);

12 years, 8 months

Re: [LAD] [LAU] Linux Audio 2012: Is Linux Audio moving forward?

by Louigi Verona

Hey Dan! "Saving projects is only tricky if you use the modular approach versus instrument plugins hence this isn't really a problem for A3 and qtractor." True, but since there are very few plugins, most power of Linux Audio today is not in its plugin collection ;) On Wed, Oct 10, 2012 at 2:09 PM, Dan MacDonald <allcoms(a)gmail.com> wrote: > Hi LV! > > Nice and interesting write up of your experiences and opinions there. I > agree with most all of it except: > > "Saving projects is still a huge problem. In addition to LADISH we do now > have NSM, the Non-Session Manager, which seems like a workable solution, so > we'll see how this works out in the long run. > LMMS seems to be the only game in town for those who want to save full > projects by just clicking "Save" and not having to install and configure a > "session manager". I must admit, by the way, that I have not followed LMMS > recently." > > Saving projects is only tricky if you use the modular approach versus > instrument plugins hence this isn't really a problem for A3 and qtractor. > Aside from LMMS, MusE and sunvox have a few integrated instruments so they > don't have this problem either (if you stick to the built-in synths for > Muse only - sunvox doesn't handle plugins) and pretty soon MusE should gain > native VST support to further improve this situation. > > Your article has reminded me of my one and only JACK complaint/ feature > (yep - just one!!!) request which I filed a couple of years ago now but is > still to be addressed: > > http://trac.jackaudio.org/ticket/202 > > I'm surprised others haven't been asking for more descriptive 'device > busy' error messages from JACK as for many years this has been my only > issue with JACK - it doesn't start and you don't know what process is > preventing it doing so. Quite often I'll not bother doing the detective > work and just reboot but that is hardly ideal so I think this small > addition would make JACK (and qjackctl) and as a result Linux audio much > more user friendly. > > Your thoughts Mr Davis? > > On Wed, Oct 10, 2012 at 9:24 AM, Louigi Verona <louigi.verona(a)gmail.com>wrote: > >> Hey fellas! >> >> Would like to present an article I've written. Mostly wrote it to start a >> conversation and hear what others have to say on the subject. >> >> >> http://www.louigiverona.ru/?page=projects&s=writings&t=linux&a=linux_progre… >> >> You can comment here or on my textboard (which does not require >> registration). >> >> >> -- >> Louigi Verona >> http://www.louigiverona.ru/ >> >> _______________________________________________ >> Linux-audio-user mailing list >> Linux-audio-user(a)lists.linuxaudio.org >> http://lists.linuxaudio.org/listinfo/linux-audio-user >> >> > -- Louigi Verona http://www.louigiverona.ru/

12 years, 8 months

a little help with mutichannel alsa

by grekimj＠acousticrefuge.com

BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px; First, what I would like to do is pick which channel I send audio to on the RME 9632 card. My RME card is device 0. When I call this function: snd_pcm_open(&handle,device,SND_PCM_STREAM_PLAYBACK,0) And set device = plughw:0,0 I get playback across all the RME outputs. (Just using hw:0,0 without the "plug" prefix does not work for some reason which may or may not matter.) So, how do I access the subdevices/channels? When I run aplay -l I only see 1/1 subdevices. Shouldn't I be able to set my device to hw:0,0,1 or plughw:0,0,1 to access channel 2, for example? There's no .asoundrc. Do I need it for this? Finally, when attempting multichannel alsa, I assume I need to simply make an array of pointers to the same datatype as "handle" and run through initializing each handle separately. In the first time thought the loop, I can get handle[0] and all its parameters to initialize without errors. When I try to initialize handle[1] on a new device such as plughw:0,0,1 I get an error that the device or resource is busy. I feel like I've hit a brick wall here. Perhaps I am out of my league. But, it feels tantilizingly close to working. Thanks guys/gals!! Grekim

12 years, 8 months

soundtouch how to BPMDetect

by Alfs Kurmis

12 years, 8 months

Re: [LAD] Linux-audio-dev Digest, Vol 68, Issue 3

by Bart Brouns

Hi Alfs, Here are two bpm stretch examples: http://www.surina.net/soundtouch/soundstretch.html#examples All the best, Bart. On Sun, 2012-10-07 at 12:00 +0000, linux-audio-dev-request(a)lists.linuxaudio.org wrote: > soundtouch

12 years, 8 months

[ANN] Qtractor 0.5.6 - The Golf Tango release!

by Rui Nuno Capela

Hi there, Maybe some of you agree with me, that this has been the longest since last dot release and the new one with the least brand new features count being introduced. Aha no big deal I say, the uber-procrastinator is just roaring its ugly head once more, specially after a beloved summer vacation season. Whatever. Qtractor 0.5.6 (golf tango) is now released! One of the interesting dots, if not the most, is that LV2 State Files interface implementation, once in a gruesome SNAFU support status, is now officially over. For the laymen it means that any files, referenced by those LV2 plug-ins which implement the LV2 State Files interface, will get righteously bundled to an archive/zip session file (suffix or extension .qtz), all other cases remain untouched. That should add up some notches on the session portability and archival ranks and purposes. Besides, LV2 1.0.0 compliance status is now closed business. I hope. Moving on, slowly forward... Release highlights: * LV2 State Files support (NEW) * Unused files clean-up removal (NEW) * Edit/Insert empty range (NEW) * MIME Document types and icons (NEW) * Improved plug-in state resilience (FIX) * French and Japanese translations (NEW) Website: http://qtractor.sourceforge.net Project page: http://sourceforge.net/projects/qtractor Downloads: - source tarball: http://downloads.sourceforge.net/qtractor/qtractor-0.5.6.tar.gz - source package (openSUSE 12.2): http://downloads.sourceforge.net/qtractor/qtractor-0.5.6-2.rncbc.suse122.sr… - binary packages (openSUSE 12.2): http://downloads.sourceforge.net/qtractor/qtractor-0.5.6-2.rncbc.suse122.i5… http://downloads.sourceforge.net/qtractor/qtractor-0.5.6-2.rncbc.suse122.x8… - quick start guide & user manual: http://downloads.sourceforge.net/qtractor/qtractor-0.5.x-user-manual.pdf Weblog (upstream support): http://www.rncbc.org License: Qtractor is free, open-source software, distributed under the terms of the GNU General Public License (GPL) version 2 or later. Change-log: - The dedicated audio outputs setting for instrument plugins was not in effect as default global option for new MIDI tracks, now fixed, hopefully (thanks to danboid aka. Daniel MacDonald persistence). - An immediate Files widget cleanup option is now made available, as to select and remove all unused file entries. - MIDI track (un)solo/mute reset clip event sequence fixing; definite regression to MIDI track's occasional muting bug while clip editing and playback is rolling. - Apologies due on this one: shift/ctrl keyboard modifiers are back in business to change MIDI events currently selected in one single step while on MIDI clip editor (aka. piano-roll). Sorry. - Japanese (ja) translation added (by Takashi Sakamoto). - General time-scale bar, beat and tempo rounding fixing. - Keyboard shortcuts configuration (Help/Shortcuts...) now checks and warns for already assigned key sequences. - The View/Snap menu is now listed as fully accessible actions, making each snap-per-beat setting assignable to a keyboard shortcut (after a feature request by danboid aka. Daniel MacDonald, thanks). - Fixed MIDI resize tool, now applying symmetric proportional changes to pitch-bend event values [-8191, +8191]. - Fixed re-loading of LV2 Presets that are newly created/saved during current session; actually delete and remove a LV2 Preset if found in the file-system (as suggested by Jiri Prochaszka aka. Anchakor, thanks again). - Preset drop-down list is now sorted, on plugin properties dialog. - After a long absence, edit(blue) cursor vertical lines are back on the MIDI clip editor views (aka. piano-roll). - LV2 1.0.0 compliance phase II: LV2 State Files support completed. - Updated to newer LV2 External UI extension support (now maintained by Filipe Coelho aka. falktx). - Brand new editing tool: empty range insertion, split/moving clips or events forward the specified edit-head/tail interval, defaults to next measure or bar (cf. menu Edit/Insert/Range, Track Range). - Don't show the waiting cursor anymore when loading any plugins which might have a nice native editor (GUI) and options are set to show it. - MIDI clip editor now hopefully rid of random but persistent muting, a slight regression to editing while playback is rolling. - A MIDI file player's bug, evident while transport rolling in looped mode, has been fixed with yet another oneliner patch (kind by Jiri Prochaszka aka. Anchakor, thanks again). - LV2 plugins with a Qt4 GUI (guess what or whom?) are now guaranteed to some reasonable window type like Qt::Widget but not Qt::Dialog nor Qt::Popup, preventing those from standing always on top while on some window managers or desktop environments (a simple addition by Jiri Prochaszka aka. Anchakor, thanks). - MIME type icons support for session (*.qtr *.qtr), template (*.qtt) and zip/archive (*.qtz) are now being introduced. - LV2 State Files feature support is shamelessly getting real trial, now letting files referenced in LV2 plugin states to be seamlessly included when saving to a zip/archive file bundle (.qtz suffix). Added some virtual destructor stubs to shut up gcc 4.7 warnings. - Improved plugin state resilience, now finally with parameter name matching, specifically targeted on loading old sessions or plugin preset files (.qtx), preserving old saved plugin states as much as possible in face of rogue or discrete parameter index renumbering, due naturally on any plugin's life cycle ie. upgrades etc.;) - Added some more snap-to-beat divisors (Beat/14, /21 and /28) due on feature request ticket, while dropping highest, probably useless one (Beat/128). - New French (fr) translation added (by Yann Collette, thanks). - Slight late optimization on vertical zebra/grid lines drawing. Enjoy! -- rncbc aka Rui Nuno Capela

12 years, 9 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