>> Is pulseaudio useful? or can I remove it?
>>
>I've only used Pulseaudio in the context of a review of media players
>for Ubuntu 8.04. At that time and for that purpose it performed fine,
>but I don't know how it interoperates with JACK or other servers. AFAIK
>you can remove it, but you'll probably find that it's a dependency for
>many other apps. Boo-hiss for that factor. :(
>
>I'm learmning about Ubuntu 8.10 now as a matter of necessity. So far so
>good, but I've yet to muck about with the Pulseaudio stuff. Nothing
>against the software itself, but I don't need it, don't want it, and
>would like to cleanly remove it.
>
>Best,
>
>dp
I got rid of pulseaudio because it manhandled the sound in Dragon NaturallySpeaking.
However, in Intrepid and Jaunty, pulse is integrated into bootup commands.
You have to cleanly remove it with the following:
sudo apt-get purge pulseaudio
I just picked up an M-Audio Axiom 61 midi controller. Out of the box I can
cycle through patches in qsynth with it, and send pitch bend messages.
Another nice feature of this controller is that it has transport controls,
and a large selection of slider, and rotary controllers. I hooked it up to
aseqdump and it sends good messages over to my linux box. I'm wondering what
my options are for binding the midi messages from the transport control, to
the jack transport. If it matters, I usually use rosegarden/hydrogen for my
midi work. Controlling qsynth/fluidsynth with the sliders and knobs would be
nice as well.
Thanks,
Nathanael
Hello,
We'd like to announce a new release of jackctlmmc, a command line tool for
driving JACK transport using Midi Machine Code that you can download here:
https://sourceforge.net/project/showfiles.php?group_id=245788
or get the code here:
http://repo.or.cz/w/jackctlmmc.git
The program is still in its infancy but it should work for most MMC devices.
It currently supports the following MMC commands:
Play / Deferred Play - start transport
Stop - stop transport
Rewind - go to time 0
Goto: go to the specified SMPTE time
It's a pretty simple command line utility for now, but we'll be working on a
QT front end soon. To use jackctlmmc:
1) start the program on the command line: ./jackctlmmc -f <your device's
SMPTE frame rate> -t <jitter tolerance in milliseconds>
You can also specify -v if you want it to output messages in the console for
all MMC commands it's handling, which is useful for testing.
2) connect your midi port to jackctlmmc using either aconnect or JACK's
connect (you will have to specify JACK's midi driver as "seq" if you want to
connect using JACK).
For the goto command to work, jackctlmmc needs to know your device frame
rate which you can specify with -f, or use the default 30 fps. Some MMC
devices (like my BR900CD 8-track) are awfully spammy with their goto
messages, so we've implemented a jitter tolerance (specified in milliseconds
on the command line with -t, defaulting to 50) so jackctlmmc will ignore
goto commands that are already close enough to the current JACK transport
time.
There's still a lot of work to do on the application, but we've been getting
emails asking for progress updates, so we decided to do a quick release now.
Hopefully it's useful to people other than ourselves.
-- Alex
Greetings,
My new notebook is almost perfect, but I still need to automate a few steps.
I have a MidiSport 2x2 USB MIDI interface attached to the machine. I
installed the firmware and added the necessary info to the udev rules.
Alas, the device doesn't initialize at boot time. Success occurs if I
re-plug the device, but I'd like to skip that step.
Ditto for the rtirq script. Where do I put it so that it's autoloaded at
boot ?
Sorry if these are obvious questions. I'm new to the Tao of Ubuntu, and
I'm still learning here. :)
Btw, I have an Edirol UA25 coming to me soon. Any extra advice from LAU
folk regarding its configuration and use ?
Best,
dp
Hi,
I don't get the licence issue of VST on linux completely, help me out
with this.
- Building Ardour, Qtractor, LMMS with VST-support is illegal, right?
- And energyxt? Are they allowed to use VST technology?
- Installing JOST and using it, is illegal right?
- And FST and vst-dssi?
- And wineasio?
- using VST plugins on Linux?
- Installing Reaper on Linux?
Thanks in advance,
\r
Resending, the previous message got bounced for moderation due to the
1.5M debug log attachment.
On Sun, Nov 23, 2008 at 8:30 PM, Jack O'Quin <jack.oquin(a)gmail.com> wrote:
>> On Sun, 23 Nov 2008, Pieter Palmers wrote:
>
>>> The FFADO team is proud to announce the first release candidate for
>>> FFADO 2.0.
>
> I just tried the new libffado-2.0-rc1 with jack 0.113.3 (SVN) with my
> PreSonus FireBox on Ubuntu Hardy with the 2.6.24-21-rt kernel. The
> ffado-diag script says I have the old 1394 stack. Is that a problem?
> If so, how do I get the new one?
>
> The libffado.so got built and installed, but the JACK firewire backend
> could not find it, because ldconfig was apparently not run. So, I ran
> ldconfig by hand. Also, I notice there is no library versioning, yet.
> Is that intentional?
>
> After fixing that, I am still unable to start JACK. I tried resetting
> the bus via gscanbus, but it still does not come up. I am attaching
> the ffado-diag output and the ffado-jack.log.
(Only the ffado-diag.log is attached to this message.)
> $ jackd -Rv -P70 -d firewire -v6 -r48000 -p1024 -n3 2> ffado-jack.log
>
> getting driver descriptor from /usr/lib/jack/jack_freebob.so
> getting driver descriptor from /usr/lib/jack/jack_oss.so
> getting driver descriptor from /usr/lib/jack/jack_firewire.so
> getting driver descriptor from /usr/lib/jack/jack_net.so
> getting driver descriptor from /usr/lib/jack/jack_alsa.so
> getting driver descriptor from /usr/lib/jack/jack_dummy.so
> jackd 0.115.3
> Copyright 2001-2005 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
>
> JACK compiled with System V SHM support.
> registered builtin port type 32 bit float mono audio
> registered builtin port type 8 bit raw midi
> clock source = system clock via clock_gettime
> start poll on 3 fd's
> loading driver ..
> new client: firewire_pcm, id = 1 type 1 @ 0x806ea80 fd = -1
> new buffer size 1024
> registered port system:capture_1, offset = 4096
> registered port system:capture_2, offset = 8192
> registered port system:capture_3, offset = 12288
> registered port system:capture_4, offset = 16384
> registered port system:capture_5, offset = 20480
> registered port system:capture_6, offset = 24576
> registered port firewire_pcm:C6_dev0_MidiIn, offset = 4096
> registered port system:playback_1, offset = 0
> registered port system:playback_2, offset = 0
> registered port system:playback_3, offset = 0
> registered port system:playback_4, offset = 0
> registered port system:playback_5, offset = 0
> registered port system:playback_6, offset = 0
> registered port system:playback_7, offset = 0
> registered port system:playback_8, offset = 0
> registered port firewire_pcm:P8_dev0_MidiOut, offset = 0
> ++ jack_sort_graph
> ++ jack_rechain_graph():
> +++ client is now firewire_pcm active ? 1
> client firewire_pcm: internal client, execution_order=0.
> -- jack_rechain_graph()
> -- jack_sort_graph
> starting server engine shutdown
> stopping driver
> server thread back from poll
> unloading driver
> freeing shared port segments
> stopping server thread
> stopping watchdog thread
> last xrun delay: 0.000 usecs
> max delay reported by backend: 0.000 usecs
> freeing engine shared memory
> max usecs: 0.000, engine deleted
> --
> joq
>
--
joq
Hey LADs,
My machine sometimes locks up. No oops, no instant reboot, but mouse
doesn't move, usb keyboard lights go out and nothing responds. Magic
SysRQ doesn't seem to work though i haven't tried plugging keyboard in
via ps2 instead of usb.
I ran memtest86+ for 2 nights with no errors reported. I've done smart
tools self test on both hard drives, no errors.
Temps appear normal.
Sys Temp: +33.0°C (high = +1.0°C, hyst = +9.0°C) ALARM sensor
= thermistor
CPU Temp: +17.0°C (high = +80.0°C, hyst = +75.0°C) sensor = diode
AUX Temp: +117.0°C (high = +80.0°C, hyst = +75.0°C) ALARM sensor
= thermistor
cpu0_vid: +1.063 V
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +39.0°C (high = +82.0°C, crit = +100.0°C)
coretemp-isa-0001
Adapter: ISA adapter
Core 1: +40.0°C (high = +82.0°C, crit = +100.0°C)
coretemp-isa-0002
Adapter: ISA adapter
Core 2: +36.0°C (high = +82.0°C, crit = +100.0°C)
coretemp-isa-0003
Adapter: ISA adapter
Core 3: +38.0°C (high = +82.0°C, crit = +100.0°C)
Any idea what i can check next?
hddtemp /dev/sda
/dev/sda: ST380817AS: 25°C
hddtemp /dev/sdb
/dev/sdb: WDC WD3000JD-22KLB0: 31°C
My graphics card temp seems normal too, around 40 - 50 degrees
What else can i test, it seems to occur gaming under windoze as well,
but i'm not sure if random crashes are normal there. Is there tests
for cpu/NIC? Or is it hd/ram and i just haven't seen issues in those
tests. Could this be related to the RT kernel? Any way to get more
debugging info?
Loki
Greetings,
I need to make a headless rackmount mixer/router with some basic processing
capabilities that will have eight line-level inputs and four outputs; it
should be configurable (in real time) for routing one or more inputs to
one or more outputs, with mixing and optional equalization of the sources
(up to eight equalizers). The platform will use commodity PCI sound cards
and due to the need to use available materials, will be based on an
industrial form factor 2u rackmount ASUS Socket-7 PC with an AMD K6/300 CPU
and 256 MB ram. Sample rates will be 44.1 or 48 kHz (stereo) 16bit max.
At some point, it should be controllable using an arbitrary protocol over
UDP, and of course should not require any sort of GUI. For development
I am willing to live with remote shell execution, or in the extreme,
an X-window on a controlling host.
I am willing to drive all the sound cards from a single master xtal oscillator.
What can ALSA/LADSPA and plugins with an absolute trivial LADSPA host together
with 'jack' do for me in this regard? Will I need to combine the sound cards
as a single virtual card and if so, will I have the flexibility to route and
mix as described above? Latency should be less than 10ms or so through any
channel route if possible. Should I instead consider running a 'jackd' per card?
Will I be able to switch an equalizer into any 'graph' that I construct to
permit shaping any input before mixing and output?
As you can see, I am trying to build a device that I am sure could be purchased
from someone like Roland, but 'on the cheap'.
All replies appreciated.
Michael
in this regard? W
Hi
I hope for answers, even though my problematic application is not open
source, so here goes:
I haven't done any recording with ardour on this box, so I have nothing
to compare with, but my DAW, energyXT, seems to dislike playing back 10+
audio tracks at the same time. I'm wondering if there are any
measurements and adjustments (changing priorities of interrupts, or
setting something in the lo level disk io-something) that in general
would allow realtim jack clients to perform better when reading from the
disc?
Of course, since my DAW is closed source, it could simply just be that
it is poorly written, only the author would know :-(
Any input appreciated.
--
Atte
http://atte.dkhttp://modlys.dk
Greetings, fellow LAUyers,
To recap: I recently purchased a Hewlett-Packard G60-125NR notebook, a
machine based on an AMD Turion 2 GHz CPU, with 3G RAM, a 250G hard disk,
and an on-board nVidia 8200M (essential for my work). Sound comes from
an nVidia chipset based on the dreaded Intel HDA codec.
My experience so far has been illuminating. I first tried to install the
64-bit versions Ubuntu 8.10 and Arch Linux, both of which froze during
the installation procedure. Some research indicated that the likely
culprit was the Atheros wifi driver, so I tried the brokenmodules option
but still got no joy. I found reports that Mandriva and OpenSUSE 11.0
worked, and since OpenSUSE downloaded faster I gave it a whirl. The
brokenmodules option seemed to do the trick, and after a while I had a
new Open SUSE 11.0 (64-bit) installed on the machine. Alas, I couldn't
get the official nVidia driver to work, which left me with an
unsatisfactory vesa framebuffer display. A little more Googling revealed
that indeed some users were enjoying Ubuntu 8.10 on this hardware, so I
tried again, this time with the i386 installer. Voila, in short order I
had a new Ubuntu system installed, with working 3D acceleration from the
nVidia closed-soure driver.
On to the audio. Intrepid doesn't create an audio group by default, so I
had to do the dance to add that group and myself to its users. That got
me to realtime JACK performance, though I'm still suffering excessive
xruns at 17.4 ms latency (-p 256 -n 3 -r 44100). I don't plan to use
that chipset as a primary audio interface anyway (I'm in the market for
a USB interface now), so for the present time I'll live with it. Btw,
the audio device is on IRQ 19, probably not the optimal position.
I have one more permissions problem to resolve (access to /dev/nvidiactl
is forbidden to the normal user) then I believe I'll have my target
machine, i.e. a portable box that can run AVSynthesis (OpenGL + Csound).
Btw, I've already scrapped the GNOME desktop in favor of fluxbox (of
course), but I'd certainly like to hear from other Ubuntu users
regarding any other recommended streamlining. For instance, I'd like to
junk pulseaudio and compiz completely but I'm not sure how to do it.
One question: Should I go ahead and install the UbuntuStudio packages ?
I have the rt-kernel, it seems I could just go ahead and install the
rest. Any reasons not to do so ?
Best,
dp