Hi
Long story short: I'm writing a osc2midi_clock script in chuck for
controlling sooperlooper from incomming osc messages. I have no
experience with midi clock so I had to play around with it. The
following seems to work (T for time messges (0xf8), S for start (0xfa),
x23 means "repeat 23 times"):
S Tx23 S Tx23 S etc.
It even works to the point that I can throw in clients at any time,
since the start messages resets the clock every quarter note. The two
clients I checked with are sooperlooper and renoise.
*However* the specifications I looked at are:
http://www.harmony-central.com/MIDI/Doc/table4.htmlhttp://www.blitter.com/~russtopia/MIDI/~jglatt/tech/midispec/seq.htm
They both suggests that it should actually be
S Tx24 S Tx24 S etc, with little or no time between S and the following T.
However here the clients (again sooperlooper and renoise) doesn't show
the test tempo 112 but somewhere between 116 and 117.
Anyone has any idea what the right way?
Also; I've been discussing this with Jesse Chappell (author of
sooperlooper) and he says that he looked at his code and thinks there's
a bug (which makes it work correctly with my wrong midi clock, since
that's actually written targetting sooperlooper). Now it would be very
interresting to look at other clients and masters of midi clock, however
not having worked with midi clock before, what would be the first
clients to cross check with?
--
Atte
http://atte.dkhttp://modlys.dkhttp://virb.com/atte
Hi Tom,
I just went fine with the instructions on the jack-faq-page (http://jackaudio.org/faq). Did you add these lines to your /etc/security/limits.conf ?:
------------------
@audio - rtprio 99
@audio - memlock unlimited
@audio - nice -19
------------------
Do not forget to add yourself to the group 'audio' and re-login. This in combination with the rt-kernel works great for me.
Regards, Thomas
> could someone point me in the direction to a guide on setting up rt-
> kernel on ubuntu jaunty. i'm having trouble getting qjackctl started
> in realtime mode despite the fact that i am running 2.6.28-3-rt #12-
> Ubuntu SMP PREEMPT RT. i've done this in other distros but i must be
> missing something here.
>
> thanks.
>
> t
____________________________________________________________
Text: GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://produkte.web.de/go/04/
For the past 6-8 months, I've been having issues with hard lock-ups on
my computer. Strangely enough, they occur the most, and are predictable,
when I'm playing back longer Flash videos in a browser (watching Leo
Laporte's live TV stream is a guaranteed show-stopper).
It all started when I got my new Echo MiaMIDI card. At first I thought
it was a bad card, but it ran just fine in another machine for about a
week or so, no issues. Now I'm trying to determine if there is some kind
of driver issue or maybe a driver conflict.
First off, I'd like to mention that every time I install a new Linux
distro, it's a major chore getting this card working, as it involves
compiling ALSA from source. I'm running the latest Ubuntu Studio at the
moment, and even though they included a driver for the Mia, it didn't
seem to load right, even though modprobe didn't complain, and restarting
the computer caused yet another lock-up. At the moment, I went ahead and
compiled the driver from 1.0.18a sources myself, along with the
firmware, installed that, and even though I've run into a few hiccups (a
lock-up during boot being one), the card is functioning at the moment.
I'm also skipping the proprietary NVidia driver for a period of time,
just to see if that (or a conflict with it) might be the cause.
I seem to remember a number of people having some interesting issues
using higher-end cards with PulseAudio. I'm beginning to wonder now if
Pulse might be my primary culprit. If that be the case, since I don't
really want it around anyway, does anyone have a pointer to any
instructions on how it might be removed from Ubuntu Studio 9.04?
If I do end up removing Pulse, that does leave me with a bit of an
issue, as the Echo drivers don't do any sound mixing from different
applications asking for the driver. So, I'll need a sound daemon of some
sort in order for the computer to continue to be usable.
Thank you very much for any help.
Regards,
Darren Landrum
(Nederlandstalig linux forum gedeelte op homerecording.be >>>
http://www.homerecording.be/forum/f43/ !)
Hi,
Thanks to the LAU mailinglist, I've discovered the possibilities of Linux
for producing music in the last two years. But it seems I'm a bit of a
special case in The Netherlands... most people seems to use Mac or Windows
for music production, even people who prefer Linux as their main OS...
To change it a bit, I helped people on Linux forums and wrote a dutch
tutorial for Qjackctl and Ardour. I also posted my enthusiasm and knowledge
on 'not-linux' forums... got a lot negative reactions, but not on
www.homerecording.be. The had a open mind for opensource software... and
after posting some posts there, they have decided to open a special subforum
for making music on Linux! :) (Windows and Mac can't say that...)
It would be cool if dutch speaking people will support this forum part by
taking a look at it reguarly and to post some messages, moreover to help
people with making music on GNU/Linux!
You can find the forum here:
http://www.homerecording.be/forum/f43/
CU there!
\r
hello,
I've been looking at ingen ( http://drobilla.net/software/ingen/ ). Had
some problems getting it to build, but the trick turns out to be to
install liblo and libsoup bfore you configure the build. It's a really
nice bit of software - a GUI modular synth that lets you design and save
simple patches which can then be used as building blocks for more
complex ones.
The main problem I'm having with it so far is that it doesn't seem to
understand alsa midi - only jack midi. This is difficult as I don't have
or know of any midi programs (particularly a virtual keyboard) which
produce jack midi signals.
Does anyone know of an easy way to convert alsa midi into jack midi and
vice versa?
andy
I'm trying to talk the guys I work with, into building an inexpensive
DAW for the analog studio that I currently work in.
Right now we're old school analog EVERYWHERE. The only digital gear in
the room are a few PCM 90's, and my Masterlink that I bring when I mix.
We have a 2" 16-track machine, which sounds AWESOME, but at $250 per
reel, a lot of our clients can't afford tape anymore.
We really only need 16 in and 16 out. So my thoughts are to build a
fairly powerful PC to run one of the multimedia flavored linux distros,
putting four Delta 44 cards in it, and running Ardour.
I am a free software user, but I haven't used it much for audio
production, and I'm not a super linux hacker or anything. Would
configuring a system like that be particularly difficult?
Once the DAW is up and running, we would only need to buy two 16
channel snakes to break in and out of our patch bay.
Best,
Rich...
Pursuant to the recent discussion of Hammond emulations on Linux:
I just got back from the Boom Boom Room in San Francisco, where I spent the night playing their house Hammond B3.
That is just one magical instrument. And, after playing the real thing for several hours with a full band and for a packed dancefloor, it's clear that nothing I've ever heard in emulation comes close to it. There's something about the way it moves air around that I really doubt could be duplicated.
The bass player enjoyed standing in front of the Leslie, and said, "When you get those swells going I get a nice back massage!".
Still, I'm going to try out Connie and am very intrigued by the idea of running Beatrix on a dedicated netbook. And also need to get AZR3 running on my netbook too. And motivated to finish writing the code for my Arduino-based swell pedal.
I think the Hammond might could be the original mad scientist instrument. Long before Robert Moog started building synths, the Hammond had lots of knobs and buttons and sliders for nerds to play around with.
-ken
I forgot to mention that I also played the Calf Monosynth DSSI synth live last night too. Nice synth sounds, runs well on my EEE netbook (where my favorite AMS patches are a bit too heavyweight).
Avec photo: http://www.restivo.org/blog/archives/on-the-hammond-again
-ken
Dear Jackers
I am wishing to send sound across a network in the way described in
the walkthrough:
http://trac.jackaudio.org/wiki/WalkThrough/User/NetJack.
To date I haven't heard anything though.
On the master machine I "# jackd -dalsa -P" without error. Then,
On the slave machine I "$ jackd -dnet" without error. Then,
On the master machine I "# jack_netsource -h hostname" without error.
I then "$ mplayer -ao jack soundfile" on slave without error or sound.
-v does not enlighten the situation.
Curiously, qjackctl on slave lists the transport state as stopped. That
doesn't sound too good to me, but I don't know what it means. Any
clues would be greatly appreciated.
Regards
Fog_Watch.
$ uname -r
2.6.26-gentoo-r3
$ jackd --version
jackd version 0.116.2 tmpdir /dev/shm protocol 24
# aplay /usr/share/sounds/alsa/Noise.wav
produces noise on the master machine, as expected.
--
Lose wait. Get Gentoo.