A nice feature in most (all?) sequencers that I really miss in Ardour is
the count-in. Sure I can start my recordings at bar #2 and have the first
one as count-in but then I have to remember to make an empty pattern in
Hydrogen and/or drag tracks backwards/forwards in time or remember that
"no bar #7 isn't the start of the secod verse, it's bar #8".
Perhaps a bar #0 that does record (in case I'm a bit early on "one") but
doesn't send any jack transport info and can be hidden once I've recorded
everything that needs to start on the first beat.
Or should I be doing things differently?
- Peder
Hi,
i was wondering if anyone could give me a summary of how rtlimit works
[i myself still use the realtime lsm]. I'm in the process of moving my
old wiki stuff to a wordpress installation and have also created a page
about rtlimit, but it's still lacking content [i got jonathan's
announcement mails on set_rtlimit on it though].
I'm still missing the big picture: What exactly is rtlimit and how does
it work? Is it in the same vein as ulimit?
The page is here:
http://www.affenbande.org/~tapas/wordpress/?page_id=22
btw: this software doesn't have quite the ease of use as a wiki, but it
has a working user signup thingy, so people can leave comments, etc.
--
Palimm Palimm!
http://affenbande.org/~tapas/
Hi all,
I installed a new card : maudio delta 1010LT.
OS is Ubuntu linux 5.04
... kernel-image-2.6.12-2-multimedia-386
... kernel-patch-2.6-realtime-lsm
... modules snd_seq_midi snd_seq_midi_event snd_seq snd_rawmidi
... snd_timer snd soundcore realtime
I started jackd with qjackctl. The process is running :
... >> ps aux |grep jackd
... root 7867 0.6 5.5 28476 28868 ? SLsl 20:25 0:00 /usr/bin/jackd -R
-dalsa -r44100 -p512 -n2 -D -Chw:1 -Phw:1
but qsynth doesn't want to connect to it.
May be alsa is not correctly configured ?
May be qjackctl is not correctly configured ?
I don't know which walue I have to put in :
- interface :
hw:1 (Maudio Delta 1010LT)
or hw1,0 (ICE1712 multi)
- input device :
hw:1 (Maudio Delta 1010LT)
or hw1,0 (ICE1712 multi)
- output device :
hw:1 (Maudio Delta 1010LT)
or hw1,0 (ICE1712 multi)
Thanks for your help if you have an idea !!!
Here are the steps that I did :
- $alsamixer -c 1 to set inputs/outputs value
- $qjackctl (root) which seems to be ok for my part
... >> QJACKCTL STARTUP :
... 20:24:44.599 Patchbay deactivated.
... 20:24:44.872 Statistics reset.
... 20:24:44.942 MIDI connection graph change.
... 20:24:45.080 MIDI connection change.
... 20:25:02.610 Startup script...
... 20:25:02.610 artsshell -q terminate
... 20:25:02.956 Startup script terminated with exit status=256.
... 20:25:02.956 JACK is starting...
... 20:25:02.956 /usr/bin/jackd -R -dalsa -r44100 -p512 -n2 -D -Chw:1 -Phw:1
... 20:25:02.960 JACK was started with PID=7867 (0x1ebb).
... cannot write to jackstart sync pipe 4 (Bad file descriptor)
... jackd: wait for startup process exit failed
... jackd 0.99.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 = 44100
... creating alsa driver ... hw:1|hw:1|512|2|44100|0|0|nomon|swmeter|-|32bit
... control device hw:1
... configuring for 44100Hz, period = 512 frames, buffer = 2 periods
... 20:25:04.973 Server configuration saved to "/root/.jackdrc".
... 20:25:04.974 Statistics reset.
... 20:25:05.005 Client activated.
... 20:25:05.007 Audio connection change.
... 20:25:05.008 Audio connection graph change.
- $qsynth
... >> QSYNTH STARTUP :
... 20:34:47.382 qsynth1: Creating synthesizer engine...
... 20:34:48.416 qsynth1: Loading soundfont:
"/home/ben/Sound/soundfonts/ADC-TranceKit.SF2" (bank offset 0)...
... 20:34:48.425 qsynth1: Creating audio driver (jack)...
... 20:34:48.436 qsynth1: Failed to create the audio driver (jack). Cannot
continue without it.
... fluidsynth: error: Jack server not running?
... 20:34:49.934 qsynth1: Destroying synthesizer engine...
... 20:34:49.936 qsynth1: Synthesizer engine terminated.
Hello there. I would like to know which AMD mainboard and which sound
card is recommended for a small home recording outfit? Basic recording
projects will be vocals, guitar and keyboard. Although RME Hammerfall
and M-Audio Delta are ideal, the budget can't reach that level. I'm
looking at sound cards between high-end pro-audio at the top and
consumer grade at the bottom, somewhere half-way. I'm not a purist and
at the same time 2 channel inputs and 2 channel outputs are limiting
creativity. Four I/O will be comfortable and 8 I/O will be excellent but
not necessary.
Hard disk drives and controllers. My last experience with SATA was
unpleasant. Our local supplier is pushing mainboards with SATA support
as an alternative to SCSI. Issues were mostly at the controller side and
I never resolved them. Will SATA be any good?
Thank you in advance.
ainion
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.7.1 - Release Date: 6/13/2005
Dave,
Before my suggestion... just a quick note of moral support... Please
don't let it get you down too much. Think about all the may times
there's a (seemingly impossible) problem and how it always works out in
the end. And we all seem to learn so much from these things.
Ok... So... It's not the mother board... It's not the Power supply.
You're getting there. How about buying new ram, putting the old ram in
static safe packaging. If the problems go away... Then you only paid for
ram. Beats buying a whole system.
And as people mentioned, not all memtests detect bad ram anyways. So if
problems still occure with new ram, you now have extra ram. I have tons
of "parts" and many times have been able to use some later. If the (old)
ram proves good, maybe you can use it for a machine you're building for
a friend, (or your next machine). Same with Hard drives... replace...
test... and if problems still occure, you now have extra drives (I'm not
helping am I... hehe). You can save tons of money by building a system
from scratch. So extra drives and ram are good in that way.
Btw... I see they have "cases" for IDE drives to convert them into usb
drives. Don't know if you have a use for them, but I use them to back up
drives. This is good because they aren't connected to computer (so
electric storm can't fry your back up drive). I have two so that there's
always one that's not hooked up to the computer. Haven't tried the
IDE/USB "cases", so I can't vouch for them.
It's amazing what could cause a problem. My brother tore my sister's
machine apart and replaced "this" and "that" and after all, it was the
bad sound card that was causing (both) windows (and) linux to crash.
Prior to that, I had no clue a soundcard could cause 2 OS's to crash.
And now (for instance) if I hear a soundcard making weird sounds, I'll
know to watch for weird system behavior. So at least we learn things.
I've had 2 Maxtor drive fail on me. I will never buy Maxtor drives again.
Good luck
Rocco
QjackCtl 0.2.16 is finally out!
After laying around for a long time in the backyard (aka CVS:), the Qt
front-end to the one-of-a-kind JACK audio server daemon is finally made
public. Rejoyce!
As one can read from the changelog:
- ALSA sequencer client/port name changes are now properly detected on the
MIDI connections widget (as noted by Chris Cannam. Thanks).
- Long overdue transport buttons (rewind, backward and forward) finally
landed onto the main control window, at last :).
- Duplication (copy) of patchbay socket items was added.
- Do not ever try to start the JACK server if there's one already found
running, on which case the client-only mode of operation is then activated
(as kindly suggested by Orm Finnendahl, thanks).
- After several Mac OS X user requests, ALSA/MIDI sequencer support is now
an option, otherwise detected at configure time and conditionally compiled
in if, and only if, ALSA is found available (which has been a primordial
assumption on Linux systems:). Ah, and that just makes for the blind
inclusion of another backend driver option: coreaudio.
- Actual OSS device selection menu now featured on setup dialog; these
adds to the device selection button menus for the OSS driver settings.
- Delayed geometry setup of windows upon startup was added as an optional
workaround to subtle problems due to window decoration information not
being available at window creation time on some window managers (as patch
proposed by Dirk Jagdmann. Thanks).
- Fixed some minor but rather old bug that was quitting the application
abruptly, when one switches off the system tray icon while the main
application widget is hidden.
- Cancel is now an option when creating a new patchbay definition.
- Context menus are finally littered with icons.
- Minor configure and Makefile install fixes, as Debian and Mac OS X
specialties. Also, install does the right thing with target file modes
(thanks to Matt Flax and Ebrahim Mayat, for pointing these out).
You can get away with it from the usual place:
http://qjackctl.sourceforge.net/http://sourceforge.net/projects/qjackctl
Enjoy!
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
Hi,
Since I kept coming across the linux audio user discussions in my
continuing quest to make my soundcard work under linux, I thought I'd
join and start bugging you with questions.
I have the soundcard mentioned in subj.
I have a set of cambridge soundworks hooked up to the coax digital out
and a set of headphones to the headphones output.
It took me a while, but I got sound playing out of the coax digital
output. I did this by fiddling with a .asoundrc and alsamixer.
Finally I found a combo that worked. I had to lock my internal mixer
rate to 32000 and use that as the rate in .asoundrc.
I never tried setting the rate that low, since the rate I normally see
in conjunction with audio equipment and digital connections is 44100 or
48000.
I then tried getting sound of the analog outputs, and that took me ages.
I have no idea what I did, since it was nothing I hadn't done several
times previously, but suddenly I got sound out of the analog outputs.
I could use any matched set of alsamixer internal clock rate and
.asoundrc rate up to 192000.
I did a little victory dance.
Then I hit the volume button on my keyboard, which changes the volume
with kmix. The sound disappeared.
I could get sound out of the digital coax again (changing the default
device in .asoundrc), but no matter what I did, I couldn't get analog
sound back.
I tried rebooting, turning off the machine, etc. Nothing helped.
Then suddenly after a couple of days, I tried switching back to analog
output and it worked for no apparent reason. I thought I knew what I did
right this time (messing with the multi track rate reset button in
alsamixer - I still have no clue what this is for) and bravely hit the
volume button to see if I could break the sound again.
I could. And I couldn't get it back until a few days later when it
mysteriously reappeared. After the next reboot it was gone again.
Now I have my analogue sound and I am not keen to launch kmix no time
soon. Or to reboot.
I still have no idea what I am doing wrong, but I am very keen to see
the .asoundrc and alsamixer settings of someone with a Aureon 7.1
Universe card.
Another thing I'd like to do is to make alsa play on the digital and
analog outputs at the same time, instead of having to choose between two
different pcm devices in .asoundrc.
I have RTFMed as well as I could, exerimented and googled a fair amount.
I even tried modifying envy24control to work with ICE1724 cards, but
quickly got stuck.
Any clues, pointer or help is greatly appreciated.
Brian Meidell Andersen
Greetings:
It has not been a good week.
As I mentioned yesterday I swapped my hardware into an identical box
as my original machine. Yesterday everything seemed to have returned to
normal operation. I watched some movies, worked on some music, and so forth.
Today I powered up the box, logged on to the net, downloaded the
latest Csound CVS and started compiling. After a few minutes everything
froze again, the machine was locked tight as a drum. I had to pull the
plug to restart, but when grub came up my keyboard was frozen. I pulled
the plug again and got my keyboard back after restarting.
Now I'm running memtest again. I realized yesterday that I'd run it on
only one RAM stick so I thought I'd better check again. However, at this
point I'm starting to suspect a bad drive. But *two* bad drives in the
system ?? As I mentioned in an earlier message, the machine failure
occurred regardless of which drive I was using (RH9 on /dev/hdb, FC3 on
/dev/hda).
So I'm bummed again. Looks like it's time to bite the bullet and buy a
whole new system. :(
Best,
dp
Hi folks,
this weekend I got some further ideas for my newest arrangement, you can hear
them at
http://roederberg.dyndns.org/~arnold/file_share/sounds/heilig-v2-premaster-…
It isn't finished, vocals, bass and mastering are missing...
Vinyl rockz!
Arnold
--
There is a theory which states that if ever anyone discovers exactly what the
Universe is for and why it is here, it will instantly disappear and be
replaced by something even more bizarre and inexplicable.
There is another theory which states that this has already happened.
-- Douglas Adams, The Restaurant at the End of the Universe
