28 Feb
2013
28 Feb
'13
4 a.m.
On Wed 27/02/13 5:33 PM , "Len Ovens" len(a)ovenwerks.net sent:
I noticed when running my software that the playback variables are set correctly through
Alsa calls, but the record ones are not. It's just the first time the (Presonus)
Audiobox has not initialized properly
on probably a dozen systems I have tried it on. I'm assuming the kernel should be the
same between a server and a desktop. I works fine on the same 12.04 desktop/Unity version.
I wasn't sure if we
needed to run modules or set something a certain way to tap audio capability in a server
system. Again, doesn't have to be a sever system at all. I just thought it might be
closer to what I am after to
begin with.
On Wed, February 27, 2013 10:46 am, Grekim Jennings wrote:
This would be for the sole purpose of audio, and GUI-less ones at that. I also like the
idea of being able to carry a studio on a flash drive...sort of amazing. Another machine
would have Ardour etc. I
came across the "server core" terminology from the Lubuntu alternate downloads
area. So, my impression was a server system is a bit more raw and basic than a desktop
system and going with a "core"
version of that would be almost as basic as it gets. I know there are distros tuned for
audio, but I honestly don't like all the extra stuff I don't need.
How difficult or even possible is it to start
with a server core system> and make it useable for a audio? I don't need a
GUI/desktop for this.
Not sure what you mean by a "server core". It could be starting
with coreserver SW installed. Or be specific HW. Adding Audio Apps to a machine
setup as a server is not hard, though a new install would be easier. The
onlyreason to keep the server SW in place is if you want to use the machine
both ways. In that case I would suggest setting up another run level
justfor audio. That would make it easy to turn off some of the system
serviceswhile doing audio or reconfigure some of the core defaults. On the
otherhand, if you want the machine to run as a server while also using it to
doaudio work, one of your two uses will suffer. Either the server side
willbe slower or the audio side will need more latency.
I installed
Lubuntu server core to a usb flash
drive. I added myself to
Ok, this looks like just adding audio SW. Take a look at the
ubuntustudiometas with whatever SW installer you use. (synaptic would be easiest I
tihnk) You most likey do not want the -desktop, icons or settings, just
the audio related ones. Though it may be just as easy to choose the
appsyou want.
the audio group, but my usb Audiobox does not
seem to be working,> although it is recognised with aplay -l. Should
it work without any> additional steps?
Working? Meaning what? Does lubuntu use pulse like most of the other
*buntus? Have you set your USB card as the default sound device with
pavucontrol? Which application are you playing audio on? If the machine
you are using has an internal card, that would be the default, not your
USB card. Are the levels raised in the alsa mixer? Not muted?
So what are you trying to achieve? And how? It would
be easy to tell
thesethings if I was there in person, but I am not and so to help you we
needas many details as possible.
Thanks for the help :) See above about the goal here. But again, I crave simplicity and I
like to build a system around a specific task and not have one machine do everything.
I suppose I
could build an Arch system, but I
was pleasantly surprised> by the performance
of Ubuntu 12.04 (desktop)
with the particular> software I want to run and thought I would try
an even more basic> setup. Thanks!
Pretty much all the Linux setups use alsa these days. There is not much
difference from one to the next at that level. You should be able to
getsound with any of them.
--
Len Ovens
www.OvenWerks.net
1 Mar
1 Mar
6:24 a.m.
On Wed, February 27, 2013 7:00 pm, grekimj(a)acousticrefuge.com wrote:
On Wed 27/02/13 5:33 PM , "Len Ovens"
len(a)ovenwerks.net sent:
>
> On Wed, February 27, 2013 10:46 am, Grekim Jennings wrote:
> > How difficult or even possible is it to start
> with a server core system> and make it useable for a audio? I don't need
> a
> GUI/desktop for this.
> Not sure what you mean by a "server core". It could be starting
This would be for the sole purpose of audio, and
GUI-less ones at that. I
also like the idea of being able to carry a studio on a flash drive...sort
of amazing. Another machine would have Ardour etc. I
came across the "server core" terminology from the Lubuntu alternate
downloads area. So, my impression was a server system is a bit more raw
and basic than a desktop system and going with a "core"
version of that would be almost as basic as it gets. I know there are
distros tuned for audio, but I honestly don't like all the extra stuff I
don't need.
I have done something similar to this, but I started out even more basic
than your server distro. I had an older pentium machine At 300Mhz that I
have in the past used as a server for a webserver and email as well as
firewalling/routing. I t had Slackware back then. I had a small hard drive
as well 3G or so. Just some spare parts I had sitting around. I thought I
would like to see if I could set up a really minimal audio box. Problem
one: won't boot from a USB stick... BIOS too old :) Problem two: The CD
drive is not very good. The CD drive does seem to handle 200M CDs though.
Hmm, as you might imagine there are not very many distros that fit on 200M
anymore. But there is Ubuntu's netboot.
(
http://archive.ubuntu.com/ubuntu/dists/quantal/main/installer-i386/current/…
) I found there mini.iso, only 28M which fit my small CD and booted on
that machine.
The idea of mini.iso is to install just enough to give you command line
access (like ubuntu server) and some tools to install whatever you want.
There are even some premade ideas where you can install the metas to make
one of the Ubuntu family distros. Or of course you can have a custom meta
for installing on a lot of machines that are the same for something like a
kiosk use.
Anyway, as you should have noticed from what I have said so far, this is
not plug and play, you have to know what you want. You have to have a
clear idea of what you want to use the final system for. In my case, I
wanted to see what I could do with the command line for recording
multi-track audio.
I based my install on Jack2 (dbus version so I could use things like
jack_control, though I am not sure jack is absolutely needed), Nama (CLI
DAW) which handles various plugins to effect the the audio and the plugins
to go with it, jack tools (a cli meter, jack connection tool, etc), ALSA
and the tools to go with it, a low latency kernel. Probably other stuff,
but that is the basics.
But first :) Mini comes with a number of command line tools. It is good
to know what the standard unix CLI tools are and how to use them. If you
are not used to using ed or vi to edit files... install nano or joe right
off. If you are a long time CLI user you may prefer emacs. Learn how to
use apt. This is your installer, there is aptitude as well, but apt is
generally faster. Have an understanding of VTs. The important thing to
know here is that what you do in one vt is not inherited by the next. For
example, to use dbus with more than one VT, The environmental variables
created by dbus when it starts have to be imported into each VT
session.... so learn bash (or csh, or perl... etc.) scripting. I said all
that to say learn how to work in a command line environment. There are
lots of tutorials on this... at least there were when I first started
using linux ;)
Anyway, I got as far as using about 4 VTs, one for an audio player, one to
run jack in and control it, one with alsamixer, one with a CLI audio
meter, one with a jack transport control... Oh BTW, splitvt is handy for
time you want two screens of info at the same time. I was able to use
jackdbus and tools. I did not worry about pulse in this case as I had no
need for it in my scenario. Then the PSU died and that was the last of my
CLI experiments. I need to find some more throw away systems to play with
so I can try some more things.
Memory is still important, I didn't have enough really. (< 256M I think)
Anyway, jack couldn't lock as much memory as it needed for RT. It is a
project I would like to continue when I have the extra system to play
with.
--
Len Ovens
www.OvenWerks.net
1:48 p.m.
On 03/01/2013 12:23 AM, Len Ovens wrote:
On Wed, February 27, 2013 7:00 pm,
grekimj(a)acousticrefuge.com wrote:
Len, thanks for the great ideas. I didn't even think of different
tty's
for running a couple of instances of nano (which I like quite a bit). 3
would be ideal for me. As far as RT goes, I'm not there with my coding
and it's not essential to what I need to do since I'm not doing any
audio directly in to out. The Audiobox USB has a little blend knob in
the front to balance the cue mix with the incoming live signal. For the
studio I'm using the RME 9632. But, no sure how practical the hdsp
mixer will be in non-gui format.
On Wed 27/02/13 5:33 PM , "Len Ovens"
len(a)ovenwerks.net sent:
> On Wed, February 27, 2013 10:46 am, Grekim Jennings wrote:
>
>> How difficult or even possible is it to start
>>
> with a server core system> and make it useable for a audio? I don't need
> a
> GUI/desktop for this.
> Not sure what you mean by a "server core". It could be starting
>
This would be for the sole purpose of audio, and
GUI-less ones at that. I
also like the idea of being able to carry a studio on a flash drive...sort
of amazing. Another machine would have Ardour etc. I
came across the "server core" terminology from the Lubuntu alternate
downloads area. So, my impression was a server system is a bit more raw
and basic than a desktop system and going with a "core"
version of that would be almost as basic as it gets. I know there are
distros tuned for audio, but I honestly don't like all the extra stuff I
don't need.
I have done something similar to this, but I started out even more basic
than your server distro. I had an older pentium machine At 300Mhz that I
have in the past used as a server for a webserver and email as well as
firewalling/routing. I t had Slackware back then. I had a small hard drive
as well 3G or so. Just some spare parts I had sitting around. I thought I
would like to see if I could set up a really minimal audio box. Problem
one: won't boot from a USB stick... BIOS too old :) Problem two: The CD
drive is not very good. The CD drive does seem to handle 200M CDs though.
Hmm, as you might imagine there are not very many distros that fit on 200M
anymore. But there is Ubuntu's netboot.
(
http://archive.ubuntu.com/ubuntu/dists/quantal/main/installer-i386/current/…
) I found there mini.iso, only 28M which fit my small CD and booted on
that machine.
The idea of mini.iso is to install just enough to give you command line
access (like ubuntu server) and some tools to install whatever you want.
There are even some premade ideas where you can install the metas to make
one of the Ubuntu family distros. Or of course you can have a custom meta
for installing on a lot of machines that are the same for something like a
kiosk use.
Anyway, as you should have noticed from what I have said so far, this is
not plug and play, you have to know what you want. You have to have a
clear idea of what you want to use the final system for. In my case, I
wanted to see what I could do with the command line for recording
multi-track audio.
I based my install on Jack2 (dbus version so I could use things like
jack_control, though I am not sure jack is absolutely needed), Nama (CLI
DAW) which handles various plugins to effect the the audio and the plugins
to go with it, jack tools (a cli meter, jack connection tool, etc), ALSA
and the tools to go with it, a low latency kernel. Probably other stuff,
but that is the basics.
But first :) Mini comes with a number of command line tools. It is good
to know what the standard unix CLI tools are and how to use them. If you
are not used to using ed or vi to edit files... install nano or joe right
off. If you are a long time CLI user you may prefer emacs. Learn how to
use apt. This is your installer, there is aptitude as well, but apt is
generally faster. Have an understanding of VTs. The important thing to
know here is that what you do in one vt is not inherited by the next. For
example, to use dbus with more than one VT, The environmental variables
created by dbus when it starts have to be imported into each VT
session.... so learn bash (or csh, or perl... etc.) scripting. I said all
that to say learn how to work in a command line environment. There are
lots of tutorials on this... at least there were when I first started
using linux ;)
Anyway, I got as far as using about 4 VTs, one for an audio player, one to
run jack in and control it, one with alsamixer, one with a CLI audio
meter, one with a jack transport control... Oh BTW, splitvt is handy for
time you want two screens of info at the same time. I was able to use
jackdbus and tools. I did not worry about pulse in this case as I had no
need for it in my scenario. Then the PSU died and that was the last of my
CLI experiments. I need to find some more throw away systems to play with
so I can try some more things.
Memory is still important, I didn't have enough really. (< 256M I think)
Anyway, jack couldn't lock as much memory as it needed for RT. It is a
project I would like to continue when I have the extra system to play
with.
6:32 a.m.
On Wed, February 27, 2013 7:00 pm, grekimj(a)acousticrefuge.com wrote:
This would be for the sole purpose of audio, and
GUI-less ones at that. I
also like the idea of being able to carry a studio on a flash drive...sort
of amazing.
BTW, there are a number of full audio based ISOs that fit easily on a USB
stick and run as is, GUI and all. I mention UbuntuStudio only because I am
the most familiar with it, but there are others.
--
Len Ovens
www.OvenWerks.net
9:31 a.m.
On 02/28/2013 04:00 AM, grekimj(a)acousticrefuge.com wrote:
I noticed when running my software that the playback variables are set correctly through
Alsa calls, but the record ones are not.
Which software and variables are you referring to?
It's just the first time the (Presonus) Audiobox has not initialized
properly
This would be for the sole purpose of audio, and
GUI-less ones at that. I also like the idea of being able to carry a studio on a flash
drive...sort of amazing. Another machine would have Ardour etc. I
came across the "server core" terminology from the Lubuntu alternate downloads
area.
I think you're confusing "server core" and the "lubuntu-core"
package.
Lubuntu doesn't have a server edition.
So, my impression was a server system is a bit more raw and basic than
a desktop system and going with a "core"
version of that would be almost as basic as it gets. I
know there are distros tuned for audio, but I honestly don't like all the extra stuff
I don't need.
lubuntu-core is indeed a very minimal Ubuntu install with a minimal LXDE
desktop environment. It's my current preferred way to set things up,
first do a minimal Ubuntu install and then install the lubuntu-core
package and move on from there.
I installed Lubuntu server core to a usb flash
drive. I added myself to
Ok, this looks like just adding audio SW. Take a look at the
ubuntustudiometas with whatever SW installer you use. (synaptic would be easiest I
tihnk) You most likey do not want the -desktop, icons or settings, just
the audio related ones. Though it may be just as easy to choose the
appsyou want.
the audio group, but my usb Audiobox does not
seem to be working,> although it is recognised with aplay -l. Should
it work without any> additional steps?
Working? Meaning what? Does lubuntu use pulse like most of the other
*buntus? Have you set your USB card as the default sound device with
pavucontrol? Which application are you playing audio on? If the machine
you are using has an internal card, that would be the default, not your
USB card. Are the levels raised in the alsa mixer? Not muted?
on probably a dozen systems I have tried it on.
I'm assuming the kernel should be the same between a server and a desktop.
What did you actually install? What is the output of uname -a on the
machine on which the Presonus doesn't work?
Jeremy
1:36 p.m.
On 03/01/2013 03:31 AM, Jeremy Jongepier wrote:
On 02/28/2013 04:00 AM, grekimj(a)acousticrefuge.com
wrote:
Quite possibly. I went through about 6
links to get to the download,
see below.
This would be for the sole purpose of audio, and
GUI-less ones at
that. I also like the idea of being able to carry a studio on a flash
drive...sort of amazing. Another machine would have Ardour etc. I
came across the "server core" terminology from the Lubuntu alternate
downloads area.
I think you're confusing "server core" and the "lubuntu-core"
package.
Lubuntu doesn't have a server edition. Which software and variables are you referring to?
It's just the first time the (Presonus) Audiobox has not initialized
properly
I installed the 32-bit mini iso on this page:
https://help.ubuntu.com/community/Lubuntu/Documentation/MinimalInstall
I can't give you a uname because I wrote over it with a minimal Debian
Squeeze (laptop + system tools packages) But, after working for a few
boots on one machine (booting Debian from the flash drive), I tried the
Debian/flash drive in my studio computer and got the message on boot:
"error: incompatible license." And then it goes to grub rescue. And
when I go back to the original computer I get the same error. Bummer.
on probably a dozen systems I have tried it on.
I'm assuming the
kernel should be the same between a server and a desktop.
What did you actually install? What is the output of uname -a on the
machine on which the Presonus doesn't work?
Jeremy
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
3:20 p.m.
On 03/01/2013 01:36 PM, Grekim Jennings wrote:
I installed the 32-bit mini iso on this page:
https://help.ubuntu.com/community/Lubuntu/Documentation/MinimalInstall
That's about lubuntu-core which is not a server core install.
Jeremy
4220
days inactive
4221
days old
linux-audio-user@lists.linuxaudio.org
6 comments
4 participants
participants (4)
-
Grekim Jennings -
grekimj＠acousticrefuge.com
-
Jeremy Jongepier -
Len Ovens