greetings!
i'm using ardour 2.4.1 and jamin 0.95.0.
previously, when placing the jamin controller plugin in the Master channel, setting automation points, enabling the plugin, and setting the automation track to "play", jamin would track scenes automatically without trouble. now it does not do so -- i believe the failure coincided with a recent ardour upgrade, but am not certain of that.
so, i suppose, two questions:
1. is anyone currently using the jamin controller successfuly with ardour?
2. is there some ardour setting which now needs to be changed for it to work?
if anyone out ther has any clues about this, i'd be delighted to hear them... thanks in advance!
cheers!
--
.pltk.
Hi,
I just want to say that I'm discovering the nice feature of patchbay in
qjackctl. Thanks for the feature AND the documentation/ manual by
Simon W. Fielding and dev. Rui Nuno Capela .....
How on earth is it possible that you made such a feature and did explain
it after such a long time? I do not hope that there are more such
useful features of programs which are not explained yet...
....
Thanks for making qjackctl with patchbay ;)
Dirk
Hi,
I've a couple of midi files of different music styles. But it seems to
be hard to play those files with the right 'drum kits' which match the
drumpattern of the midi file as good as possible.
What's the best way to play those midi files?
Thanks,
~d
A little live mix of my songs I've done for a radio last friday ... a
couple of mishaps along the way (including the fact it's been recorded
in mono so there's bad drop whenever the sound goes to the right
channel) but I thought I'd drop it as a demonstration of what my tracker
can do. it's a lot more chilled than the set of the Linux Audio
Conference =)
The setup is 2 GP2x running littlegptracker through a mixer and a
micromodular processing the output.
<http://discodirt.10pm.org/audio/M-.-n_live_at_radio_tuxedo.mp3>
Feedback, question, criticism welcome :)
Marc.
Hi,
I got a little task here with ecasound on a x86_64 sabayon applepro. In
contrast to my laptop ecasound doesn't record more than one audiofile
(mp3/ogg). Jack+ecasound have the same versions and are compiled with the
same configuration options (see below).
Paradoxically it works when i stream to a .wav/.flac file or any jack client.
Below you see the conf files for ecasound.
This does work:
-a:1,2 -i jack_auto,xine \
-a:1 -f:16,1,44100 -o jack_auto,system:playback_1 \
-a:2 -f:16,1,44100 -o /home/collia/Desktop/Aufnahme/02.mp3 -chcopy:2,1
this doesn't:
-a:1,2 -i jack_auto,xine \
-a:1 -f:16,1,44100 -o /home/collia/Desktop/Aufnahme/01.mp3 \
-a:2 -f:16,1,44100 -o /home/collia/Desktop/Aufnahme/02.mp3 -chcopy:2,1
I've run the lame command which is defined in the ecasoundrc. It works.
My jackd environment (Ardour/Jamin/Rezound/Meterbridge/Baudline) works fine.
Is this an 64bit issue? Is it that i'm the only one with this problem?
$jackd --version
jackd version 0.109.2 tmpdir /dev/shm protocol 22
$ecasound --version
ecasound v2.4.6.1
$lame --version
LAME 64bits version 3.97
--
mailto: nicolai.beuermann(a)gmx.de
http://www.nico-beuermann.de
gnupg fingerprint: 56DA 4E32 3A4A 52AC B769 DFC2 BF3E 9805 09BB 4259
Is anyone using MIDI on a M-Audio 24/96 (ICE1712) card? I've had one for
several years and keep using my little USB adapter because the card just
doesn't work.
Well, it works fine for audio. And it pretends to work for MIDI as well.
But, after playing a few songs it has a tendency to hang my system.
Completely. When it hangs the keyboard is frozen; not even the power
button the computer responds. I have hit <RESET> and then deal with the
"not cleanly shutdown" stuff later.
When I first got the card I had some discussions on the alsa lists.
Nothing really happened with that so I assumed that a new version of
alsa and/or linux would solve things. Well, I've gone though more than a
few updates and I think this is the 3rd motherboard ... and still the
same problem.
So, anyone with success? Otherwise I'm going to assume that there is a
problem with the hardware on the card. But, really it does seem to me to
be a driver problem. I'd like to dump the USB interface to free up a port.
--
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bob(a)mellowood.ca
WWW: http://www.mellowood.ca
Ismael Valladolid Torres wrote:
> Thanks a lot for the kind support!
>
> On Thu, Apr 17, 2008 at 11:52 AM, Pieter Palmers <pieterp(a)joow.be> wrote:
>> IRQ sharing is not a good thing, so avoid it as you can. Again the "32" is
>> not easy to interpret correctly. Read the following page to understand it:
>> http://www.reric.net/linux/pci_latency.html
>
> Being the only device reporting a PCI latency value does mean that the
> firewire controller is the only one doing bus mastering in that system
> setup?
no, because most of your devices are PCI-express, and the pci-express
bus doesn't have the latency concept. However from a "programming" point
of view pci-express is backwards compatible to PCI, hence they report a
value (of 0), although it doesn't mean anything.
>
>> Can you please provide the following information:
>> 1) the output of the attached script (python listirqinfo.py)
>> 2) the full output of lspci -v
>> 3) the jack command line used (if you use qjackctl you can run the
>> following command in a terminal to get the last command line used: "cat
>> ~/.jackdrc"
>
> marcel@ubuntu:~$ cat ~/.jackdrc
> /usr/bin/jackd -R -p128 -dfreebob -r44100 -p512 -n3 -D
>
> Check out attached files for the rest of the info. Again, thanks a lot!
>
There is one problem with your setup: all interrupts run RT at priority
50. However, jack defaults to a priority of 20. This causes two
problems: first of all the 1394 interrupts don't have higher priority
than other interrupts, hence can be delayed too long. Second: jack has
lower priority than all interrupts, hence can be delayed too long. The
main problem usually is the graphic card.
Can you check whether the following helps:
1) change the IRQ priority (possibly as root):
chrt -f -p 99 `pidof "IRQ-11"`
2) run jackd with the following command line (not as root):
/usr/bin/jackd -R -P70 -p128 -dfreebob -r44100 -p512 -n3
This should improve the situation. If so, please configure Rui's rtirq
script as described in:
http://freebob.sourceforge.net/index.php/IRQ_Threading_and_Priorities
you might even want to set the RTIRQ_RESET_ALL option to 1 in the config
file described on that page.
Greets,
Pieter
On Wed, Apr 16, 2008 at 8:56 PM, Thorsten Wilms <t_w_(a)freenet.de> wrote:
> On Wed, 2008-04-16 at 04:28 -0700, Justin Smith wrote:
> > I just made a video of a synth that I wrote in c (except for some 4
> > point interpolation code adapted from pd, the audio code is all mine,
> > based on ideas presented in "the computer music tutorial" by Cecil
> > Rhodes), with a c++ fltk gui (the waveform editing widgets are all
> > custom made).
>
Really enjoyed the video. Am a fan of Xenakis, was introduced to it
by a friend.
The synth looks fun, cant wait to try it!
Cheers,
Chris
>
>
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user(a)lists.linuxaudio.org
> http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
>
Hi!
I have a kind of obscure problem regarding my Delta 1010. It worked fine until
last night. I did a system update that didn't touch alsa, jack, the kernel or
anything. the only packages that had something to do with sound at all were
libsoundtouch and ardour. But since that update, i have no analogue output
anymore. Since I don't have any equipment that has a digitial in i cannot test
that, but MIDI still works fine. I wondered before that everything worked
without an /etc/asound.conf file, so I wrote one. But as soon as i write
_anything_ in it (be it just "pcm.!default {type hw card 0}"), all the output i
get from any media player is that signed 16 bit little endian samples aren't
supported by the hardware. Without an asound.conf, i get no errors at all, but
also no output. envy24control also shows nothing, and jackd runs until i try to
output audio, then it crashes with "cannot access hardware"-messages. i've
already updated the kernel from 2.6.23 to 2.6.24, but that doesn't make any
difference.
I already reinstalled everything that has to do with alsa, but that also made no
difference.
I am using gentoo amd64, currently on 2.6.24-gentoo-r3, alsa 1.0.14.
I'd welcome any idea.
Greetings,
Thomas
