The current discussions re: RME cards and ProTools going Linux reminded
me of a question that I wanted to refresh the list with. That is,
building a DAW from scratch. Ok, I'm not talking about creating your own
mobo, but to purchase a pre-made one, a processor, cards, yada..yada.
I haven't seen this disussed recently, and was curious what others have
done, and what others have used, to build-it-yourself.
Can we start with mobo's? Any recommendations, horror stories, successes
are most welcome.
I recently built an AMD64 PC using a DFI K8M800 board, but it was for
MythTV. I had absolutely no problems with the hardware. The problem was
getting 64bit apps/drivers. I had to build most of it myself. It is
getting _much_ better out there for the 64bit world, though.
As I said, that was for MythTV. For audio, my latest is P4 machine is
running FC2 -- with no problems lately. But, this is an older PC.
Stories? recommendations?
hi all!!
my name is criscabello and i´m from brasil. please excuse my poor english.
at first, i'd like to thank all of you linux audio developers who made
it possible for us to work with free plataforms. all of us,
brazilians, are very pleased with the result of all your work.
let me explain.
i work in a government project called "pontos de cultura" (points of
culture), and it is based in the distribuition of media stations with
free software to some places who are in a state of digital, or social,
exclusion at this time (but not much longer, we hope). this project
has a national scope, and in the beggining of 2005 will be distribute
more than a hundred (100) media kits, with projections of distributing
another thousand (1000) in the next two years!
last saturday our group had a meeting with our minister of culture,
gilberto gil, to showcase some softwares for media production (like
ardour, audacity, hydrogen, jack, alsa driver, cinerrela, kino,
etc...), and he was totaly convinced about the possibilities of our
free software media production kit. He also understood the power of
collaboration based work and open source development - this article
from wired magazine
(http://www.wired.com/wired/archive/12.11/linux.html) says more about
the minister.
oficialy, gil represents our nation, and his opinion represent all
Brazilian's voices!
at the end of our meeting, we recorded one of his songs using ardour,
gil is a popular singer in brazil (and the world) and this was his
first recording using free software. during the session the only thing
in my mind was: thank you so much paul davis and all the developer
communities!
you all can listen to the song (and sample and remix it if you like,
it is distributed under a creative commons license) from here:
in ogg format: http://banto.hipatia.info/maquina-de-ritmo.ogg
in mp3 format: http://www.pirex.com.br/pirexmp3/maquina-de-ritmo.mp3
this e-mail is to tell everyone that this is just the beginning, we
have much work to do together (can you imagine the demands from all of
these people working with our free platform?). and i'm so glad for
this momment.
thank you so much.
criscabello
ps. please foward this message for the developments lists.
>>For example many of the cheaper onboard AC97 sound chipsets have no
>>hardware mixing and no hardware volume control - they rely on the
>>Windows kernel mixer. Since the equivalent technology on Linux is not
>>as mature we have problems. And since the crappiest hardware is
>>disproportionately affected, and requires the most work, many of the
>>issues don't get fixed.
>>
>>
>I see what you are saying.
>
>Today, most mobos contain onboard audio (like the Realtek ALC850, 650).
>Are there any that don't?
>
>Any other audio-centric hw gotchas that one should look out for when
>choosing a mobo?
It doesn't really matter if the mobo comes with built in audio. You can usually set a jumper or set the BIOS to disable it. You won't find many boards anymore that don't have audio built in.
>Reuben Martin wrote:
>
>>>Can we start with mobo's? Any recommendations,
>>>horror stories, successes are most welcome.
>>>
>>>Stories? recommendations?
>>>
>>>
>>
>>I built my own from scratch. I would actually recommend it as opposed to
>>prebuilt boxes because you can pick and choose hardware that will have
>>good linux support. I bought a VIA chipset mobo, AMD Athlon-XP, and an
>>RME audio card. Gentoo distro. No horror stories. (Well, I found I had a
>>bad memory stick when I was building it, but otherwise no complaints)
>>
>what mobo did you get?
ASUS A7V333. This was more than two years ago though when it was the latest and greatest. There are more up-to-date mobos than this one now. For people looking for mobos for AMD procoessors, I would recommend VIA chipsets over Nvidia. The support is more mature for VIA. AMD chipsets are also good, but not very common. If you want a 64 bit AMD processor, I would wait for 64 bit support to mature a bit more. Give it another year or so.
-Reuben
Hello,
I'm back with my soundsystem setup :)
I've switched to the Audioslack after having heavily tested
the DeMuDi 1.2.0 .
Audioslack lacks a lot of software, but the main softs i need are there
and uptodate.
I had to compile TerminatorX, but it was not very difficult.
so the subject of this message is to relate a strange behaviour of
ecasound.
finally, due the unstability of AMS I have used the Mario advice : split by frequencies range the ecasound input to 4 output.
the input is TerminatorX. Everything goes well as long as, i think, an audio
signal is received by ecasound. When the sample stop in TerminatorX,
jack is struggling with xruns and if I don't play another sample in
TerminatorX in a short time, ardour disconnect from Jack and everything crash !
This behaviour hapens both with DeMuDi and AudioSlack.
The lonely trick I've found is to permanently connect my lonely capture
channel output to the ecasound input :-( but I need this channel in
order to connect my TB303 and I don't want it to be processed by
ecasound.
Is this something logical from ecasound or it should worth a bug report
?
Regards
Philippe
Hi folks,
Gscore 0.0.7 "bond" it out there.
You can get it there : http://gscore.org/
It's still an early aged musical score editor, but it allow you to write
scores in ABC.
The next release will focus of the ABC import, and also support of other
file formats.
You'll need scons to build it (http://www.scons.org).
Enjoy, happy downloading.
Sébastien.
Hello,
my radio programme about free software and contemporary composing, the LAD
in Karlsruhe and the "Wizards od Os"-Conference in Berlin
"- wo die Quellen offen liegen -
Freie Software und aktuelle Musik"
will be broadcasted on German State Radio
SWR2 on Nov 1st at 11 pm.
It includes interviews (from the LAD 2004) and music by
Ivica Ico Bukvic
Martin Rumori/Daniel Teige
Thomas Grill
Torsten Anders
Ludger Brümmer
Michel Koenders
Orm Finnendahl
I have to apologize to Fernando and Kjetil for not having included your
interviews and music, but I had to choose from more than 3 hours of
material, where I had - for a German programme - to concentrate on German
native speakers. Thank you again very much for you contribution ... sorry.
Best regards,
Michael
Marek,
You (and others, you're not alone) would save us (readers) a lot of time
if you would try some major trimming of posts to which you respond. The
original post I'm concerned with is attached. Here is how I would trim
it. If anybody needs more information it is in the previous posts.
Well, actually, I wasn't sure specifically what to leave in the original
post (the one you replied to) as I wasn't sure exactly what you were
responding to. So, I assumed your response was somewhat general and
just left the last few paragraphs of the previous post.
Trimming, or better, aggressive trimming, helps us all save time.
regards,
Randy Kramer
PS: Copying to the list for the edification of all -- if the shoe fits
...
On Tue, 2004-11-30 at 13:20, Marek Peteraj wrote:
> On Tue, 2004-11-30 at 03:17, Mark Knecht wrote:
> > FYI - There are 48700 registered users of the DigiDesign forums...
>
> So how big would the number of sold units be? I believe that a *lot* of
> those customers had at least one problem, registered and asked on their
> forums. Dobule or triple the number.
>
> The samller card manufacturers usually deal with smaller numbers.
>
> 1000 and growing is a very interesting number to me.
> *sigh* Wish i was a card manufacturer.
BTW, let's compare:
Digi002 fw interface 8 analog i/o
ProTools recording sw, plugin bundle, and perhaps other software tools
1199euro
Fireface, 10 analog i/o
no software (usually worth another 1000 euro)
1300euro
No wonder there's 50.000 users on their forums.
Marek
I am having a lot of trouble getting Jack working under SuSE 9.1
It is very hard to keep track of the problem because the symptoms seem to
change every now and then for no reason I can fathom, and because I have had
other problems configuring soundcards in the past most (but not all) of which
seem to have mysteriously sorted themselves out for no apparent reason.
Therefore I will just give you for now a snapshot of the problem in its
current (though fairly typical) manifestation for the sake of brevity.
First of all you might need to know the following:
1. The problem has occurred with both the kernels I have used, each compiled
from different (non-suse) sources.
2. I have 2 soundcards: an on-motherboard i810 and an Audigy 2. Only the
Audigy 2 seems to work at the moment, although I would prefer it if both did.
In the past various Linux installers have got them mixed up and caused a lot
of pain and silence, including suse 9.1. Why suse 9.1 turned round and got
it right the second time is completely beyond me.
3. I have been very careful to avoid arts-jack conflicts while
troubleshooting.
4. The Agnula DeMuDi live CD got Jack working with the Audigy 2 card and I
was able to make silly noises with it and route signals to my heart's content
on the very same hardware. This is a variant of the Knoppix method for
proving that on any given machine Windows is useless and not the machine.
SuSE isn't useless, but it's been damn annoying in many ways.
OK. So now to tell you what has been happening between me and Jack today:
1. I start qjackctl. As always, MIDI works but sound doesn't, and I get the
following output:
15:35:56.092 Statistics reset.
15:35:56.331 Startup script...
15:35:56.332 killall artsd
15:35:56.385 MIDI connection graph change.
15:35:56.900 Startup script terminated successfully.
15:35:56.901 JACK is starting...
15:35:56.901 /usr/bin/jackd -R -t500 -dalsa -dhw:0 -r48000 -p512 -n2
15:35:56.905 JACK was started with PID=16459 (0x404b).
jackd 0.94.0
Copyright 2001-2003 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:0|hw:0|512|2|48000|0|0|nomon|swmeter|rt|32bit
control device hw:0
configuring for 48000Hz, period = 512 frames, buffer = 2 periods
Couldn't open hw:0 for 32bit samples trying 24bit instead
Couldn't open hw:0 for 24bit samples trying 16bit instead
Couldn't open hw:0 for 32bit samples trying 24bit instead
Couldn't open hw:0 for 24bit samples trying 16bit instead
JACK: unable to mlock() port buffers: Cannot allocate memory
cannot lock down memory for RT thread (Cannot allocate memory)
cannot lock down memory for RT thread (Cannot allocate memory)
15:35:57.107 MIDI connection change.
15:35:59.117 Could not connect to JACK server as client.
15:36:10.502 Could not connect to JACK server as client.
2. I try sudo qjackctl and I get the following output:
15:41:35.712 Statistics reset.
15:41:35.938 Startup script...
15:41:35.939 killall artsd
15:41:35.996 MIDI connection graph change.
15:41:36.508 Startup script terminated successfully.
15:41:36.508 JACK is starting...
15:41:36.509 /usr/bin/jackd -R -t500 -dalsa -dhw:0 -r48000 -p512 -n2 -s -S -i2
-o2
15:41:36.513 JACK was started with PID=16502 (0x4076).
jackd 0.94.0
Copyright 2001-2003 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:0|hw:0|512|2|48000|2|2|nomon|swmeter|soft-mode|
16bit
control device hw:0
configuring for 48000Hz, period = 512 frames, buffer = 2 periods
15:41:36.715 MIDI connection change.
15:41:38.729 Server configuration saved to "/home/robert/.jackdrc"
15:41:38.730 Statistics reset.
15:41:38.805 Client activated.
15:41:38.806 Audio connection change.
15:41:38.809 Audio connection graph change.
3. I run qjackctl again as a normal user and I get the following output
(different from before for some reason I can't fathom):
15:50:13.168 Statistics reset.
15:50:13.415 Startup script...
15:50:13.416 killall artsd
15:50:13.472 MIDI connection graph change.
artsd: no process killed
15:50:13.985 Startup script terminated with exit status=256.
15:50:13.986 JACK is starting...
15:50:13.986 /usr/bin/jackd -R -t500 -dalsa -dhw:0 -r48000 -p512 -n2 -s -S -i2
-o2
15:50:13.990 JACK was started with PID=16590 (0x40ce).
jackd 0.94.0
Copyright 2001-2003 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
cannot create shm segment /jack-engine (Permission denied)
cannot create engine control shared memory segment (Permission denied)
cannot create engine
15:50:14.003 JACK was stopped successfully.
15:50:14.004 Shutdown script...
15:50:14.004 artsd &
ALSA lib pcm_hw.c:549:(snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: Broken
pipe
ALSA lib pcm_hw.c:549:(snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: Broken
pipe
15:50:14.193 MIDI connection change.
15:50:14.513 Shutdown script terminated successfully.
15:50:16.202 Could not connect to JACK server as client.
In each case I have tried to start a jack application (e.g. Hydrogen) and got
a warning that I would get no sound. What's more, the warning was in each
case correct and I did indeed get no sound.
To add to all this, earlier today I tried changing the sound server settings
in the KDE control centre and every time I did anything X froze completely
and I had to CTRL-ALT-BKSP out of it. However I seem finally to have
succeeded in getting arts to choose jack rather than alsa as the audio
device, but I don't really have a clue how I did it, and I have no less or
more audio functionality than before.
Erm... Any ideas on how to get jack being nice with my Audigy driver and the
jack clients?
Many thanks
Robert
P.S. I have just joined the list, but I have already used the archives on a
number of occasions and so I would like to thank all of you for making this
resource so useful.
P.P.S. Nice one Brazil. The Brazillian popular music repertory as a public
archive: that stuff is far more important than the Louvre. It should become
the flagship UNESCO World Heritage Website or there's no justice in the
World. Yeah. I know there actually isn't much justice in the world, but I
can still believe in it can't I?
--
Robert Persson is powered by Linux.