Linux-audio-user

linux-audio-user@lists.linuxaudio.org

8 participants
20664 discussions

by Louigi Verona

Made with seq24, Petri-Foo, Qtractor, Hydrogen. http://www.louigiverona.ru/files/venom.ogg -- Louigi Verona http://www.louigiverona.ru/

12 years, 8 months

seq24 and JACK Transport

by Louigi Verona

Hey fellas! I am having problems with syncing seq24. As soon as I choose any JACK Transport option for it, it stops playing. I tried restarting it, I tired various combinations of those options so that seq24 will even start Hydrogen, but it will not send midi itself. Any advice? -- Louigi Verona http://www.louigiverona.ru/

12 years, 8 months

Re: [LAU] Poll - Was: Hey everyone, a simple question.

by Len Ovens

On Thu, March 21, 2013 9:59 am, Neil wrote: > That's why my talk about audio production at Ohio Linux Fest focused on > the > stuff that *didn't* go smoothly when I switched from Mac to Linux. It is interesting how people's experience shapes what they expect. Apple was always out of my price range and still is. I started out with an atari mega and various bought/shareware/freeware/DIYware. It had a nice sequencer and as I had only 4 tracks, putting MTC on one track gave me drums and keys up to 16 tracks as well as three analog tracks. Got interested in BBSs and set one up. only problem I couldn't do music at the same time. Got an old (even then) 286 MB and PS (no case) and put DRdos on it and ran maximus. A friend had windows (3.1 back then) ran two lines, when the second line connected, the first slowed down to 1/4... we're talking 3kbaud here, and had to use a mechanical timer to restart the system at least once a day. So when I went two lines I used OS/2 (IBM was giving 2.1 away in hopes of selling 3.0) I could go on holidays for two weeks and come back to a running system. One line had no effect on the other. Then the Internet started to show up. I wanted to do networking, but IBM wanted big money for network drivers for OS/2. Windows didn't really have it either. and this was still pre win95. I ended up with Linux about 93 or 94, Slackware pre 1.0. I ported my BBS over (hand coded the lot) and have been with it ever since. Apple is still over priced and windows has never really (for me) caught up, at least in the things that matter. I have experienced windows in various ways. 95 on my wifes machine, till it got infected, NT at work, saw lots of crashes, we used Linux to load/back it up though, win ME was broken and never fixed, win 7 is slow, even Ubuntu vanilla is faster. So Apple has priced themselves out of my interest. I can't afford the hardware, and most SW has to be bought. Windows still doesn't just work, you seem to need to buy a boat load of utilities to keep it infection free and keep it from slowing down, it really isn't a multi user system, but a multiuser hack on top of a single user kernel (last I checked). MS does not fix problems in a timely manner. The license seems to indicate that if I make music on their system they own a part of it. They seem to have a right to all the files on my disk too... not acceptable. (maybe the lic has changed?) Anyone with that kind of license would have a right to add access for themselves to my computer. So for me migrating to Linux has never been an issue, it is where I started, and every time I look at something else... switching looks really painful, better to make what I have work. -- Len Ovens www.OvenWerks.net

12 years, 8 months

Re: [LAU] Hey everyone, a simple question.

by Ralf Mardorf

PS: What software and hardware do you use to make music? Are you still using Linux software in addition to other software? -- Oops, drives spin up and down with GNOME 2 too, just the intervals are very looooooooooong.

12 years, 8 months

Running the guitarix LADSPA plugins on a headless system

by Jeremy Jongepier

I'm trying to figure out what is the best way to use the Guitarix-Amp and Guitarix-FX LADSPA plugins on a headless system (read Raspberry Pi). I've tried it with Ecasound but it already consumes more CPU than the guitarix application itself! So I'm obviously doing something wrong. Maybe this is because the Guitarix-Amp plugin has one input and two outputs, read something about Ecasound starting up multiple instances of the plugin in such a case which is not what I want. So any hints or tips on getting this to run smoothly? I can use either JACK or ALSA directly. I prefer using JACK, somehow using bare ALSA produces large amounts of xruns. Thanks in advance, Jeremy

12 years, 8 months

m-audio c400

by rosea.grammostola

Hi, Does the m-audio c400 work on Linux? Regards, \r

12 years, 8 months

Hey everyone, a simple question.

by Gabriel

I joined this list when I was a linux user, but since I did a gear upgrade I wasn't anymore able to use linux to do my music work. My question is, is it alright to ask for you guys opinions on my works even tough they were not 100% made in Linux ? All the best, Gabriel Roble Simão (Be.U)

12 years, 8 months

Re: [LAU] State of Linux - was - LightWorks for Linux Demo

by Len Ovens

On Wed, March 20, 2013 9:24 am, Dan MacDonald wrote: >> Speaking of which. Where is ALSA at? Where is firewire support? or >> bluetooth support? If there is one area I would like to see more >> developers that would be it. Jack supports more than ALSA with FW and >> pulse (much as it is hated) supports BT audio that alsa doesn't. >> > > I don't know about BT. I never use it so I'm not overly bothered about > ALSA > BT support but ALSA FireWire support is on its way apparently. I guess for BT devices, the question becomes are there any good quality BT headsets. The large majority have got to be celphone quality devices. > > Alex did a good write up on it last summer if you missed it: > > http://libregraphicsworld.org/blog/entry/the-state-of-firewire-audio-interf… That explains things pretty clearly all right. The rumors have been all the way from "it's coming" to "dead in the water". It seems it's coming. but not any time soon :) The next question is: While I can find lots of FW audio IFs for sale, I don't see FW ports on a lot of new motherboards (both desk and lap), Is FW going away? Are there new FW audio IF still coming out or are all those ones I see older designs? When will we see USB3 designs? (I know latency is no better, but there are other reasons it makes sense) -- Len Ovens www.OvenWerks.net

12 years, 8 months

Re: [LAU] State of Linux - was - LightWorks for Linux Demo

by Len Ovens

On Wed, March 20, 2013 8:07 am, Len Ovens wrote: > Speaking of which. Where is ALSA at? Where is firewire support? or > bluetooth support? If there is one area I would like to see more > developers that would be it. Jack supports more than ALSA with FW and > pulse (much as it is hated) supports BT audio that alsa doesn't. If there is one place I would like to see those who spend money on Linux coders put money into this would be it. I think the HW manufactures might be willing to talk to people who are in a business over a "hobbyist". If Harrison (for example) went to any of the Audio Interface makers and said we would like your IF to work with our product, that would get more response than an alsa developer who only talks through email or some user saying "why don't you have a linux driver?" What has happened instead? Pulse has BT support directly. The money/dev time has skipped alsa. What can we as musicians do to help here? PS is Harrison going to release a Mixbus based on A3? They have dropped the MB2 prices, but no coming soon messages. -- Len Ovens www.OvenWerks.net

12 years, 8 months

Re: [LAU] Python3 PyAlsa Build fails

by Christoph Kuhr

Hi, thanks for your help! > #ifndef Py_TYPE > #define Py_TYPE(ob) (((PyObject*)(ob))->ob_type) > #endif worked, with replacing *self->ob_type* by *Py_TYPE(self)* in any C-file. now I ran into another compilation problem, which I could not find any solution to: pyalsa/alsaseq.c:505:13: error: 'PyInt_Type' undeclared here (not in a function) pyalsa/alsaseq.c:508:3: error: 'Py_TPFLAGS_HAVE_GETCHARBUFFER' undeclared here (not in a function) pyalsa/alsaseq.c:509:5: error: 'Py_TPFLAGS_HAVE_CLASS' undeclared here (not in a function) pyalsa/alsaseq.c:510:5: error: 'Py_TPFLAGS_CHECKTYPES' undeclared here (not in a function) Do you have any suggestions? Regards, Ck

12 years, 8 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-user