Linux-audio-user October 2014

linux-audio-user@lists.linuxaudio.org

87 participants
74 discussions

How-to for simple recording for 3.5 hours?

by Jonathan E Brickman

Last Sunday I set up my laptop for a 3.5-hour recording session, Audacity crashed after 2.5 hours. Anyone know why this might have occurred, what to do about it, whether Audacity is in fact best for simple recording? Jonathan E. Brickman Ponderworthy Music | jeb(a)ponderworthy.com<mailto:jeb@ponderworthy.com> | (785)233-9977 | http://ponderworthy.com

9 years, 6 months

Re: [LAU] qjackctl prettyname (metadata) patch (was: Bridging alsa and jack midi)

by Rui Nuno Capela

On 09/28/2014 07:06 PM, Paul Davis wrote: > patch from svn diff attached > i see that your patch only reads the pretty-names (metadata) if exists at runtime and uses them as the "official" port-names instead. so, who or what does the pretty-name setup? that is, who or what sets the pretty-names of each port in the first place? i was thinking about the user using the qjackctl client/port aliases functionality already in place and use it eg. to run jack_set_property() on each renamed client/port alias on jack server start (as read from Qjackctl.conf file, on a per preset basis). what you think? -- rncbc aka Rui Nuno Capela rncbc(a)rncbc.org

9 years, 6 months

Re: [LAU] Bridging alsa and jack midi

by Len Ovens

On Fri, 26 Sep 2014, Philipp Überbacher wrote: > Alles klar. Well, mostly. I guess that alsa_midi only makes sense > when alsa is used as a backend, so I don't quite see why it is a server > option instead of a backend option. Anyway, using the -X alsa_midi as > server option works. That is not true at all, Audio and MIDI are separate and so it is very possible (even likely) that the backend for audio may not be relevant to MIDI. MIDI is handled by ALSA, but is not treated as a part of the same audio interface as the sound that goes with it. So the user who has a FW audio IF with no MIDI would not be able to use a USB MIDI along with it if this was in the backend only. Along the same lines is the FW user who does have MIDI in their FW IF wants to use a lot of the older SW that creates ALSA MIDI ports they are again stuck if it is only available in the ALSA back end. The only thing I would like to see different in a2jmidi is the naming. (I am not sure how jack1 works) a2j opens as one client called a2j that when expanded has the alsa client name followed by the actual port name. This is hard to read and use. It is also confusing to new users who ask where the port is just because a2j has not been expanded. I would guess the best thing (from a user POV) would be for a2j to open a new jack client for each ALSA client with the ALSA name. I am not sure what other consequences this would have though :) -- Len Ovens www.ovenwerks.net

9 years, 6 months

JACKDUB

by Patrick Shirkey

Hi, Some of you might be interested in a new project I have been working on: http://jackdub.channellinux.com/ It is a fully realtime automated music playback system built with various FLOSS tools. The system runs entirely in the cloud and doesn't even have a sound card. It's a work in progress so YMMV... Cheers -- Patrick Shirkey Boost Hardware Ltd

9 years, 6 months

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-user October 2014