Simply listening to music with mplayer or xmms running through jack: I get
xruns approximately every 20 minutes--around the hour, 20min, 40min. Not exact
but +-2 second but around the third hour point.
Xmms running without the realtime option--this is an older application that
seems to want root priviliges to do this. Play is smooth except every 20
minutes.
Mplayer is fun -ao jack,alsa.
KMidimon is a MIDI monitor for Linux using ALSA sequencer and KDE4 user
interface.
Changelog
2009-08-10 0.7.1
* Optionally translate notes, controllers and program numbers into names.
* Support for GM, GS and XG standards, using .INS definition files.
* New context menu option: adjust column sizes.
* Fine grained event filters, in addition to the old coarse filters.
* Fixed unregistered bug: don't change the current sequence PPQ/Tempo when
applying the preferences dialog.
* New dialog showing information about the current loaded sequence.
* Display more SMF events: Sequence Number, Forced Channel, Forced Port and
SMPTE Offset.
* Playback speed control: tempo "zoom" slider allowing continuous scaling from
50% to 200%.
Copyright (C) 2005-2009, Pedro Lopez-Cabanillas
License: GPL v2
More info
http://kmetronome.sourceforge.net/kmidimon/
Sources
http://downloads.sourceforge.net/kmetronome/kmidimon-0.7.1.tar.bz2http://downloads.sourceforge.net/kmetronome/kmidimon-0.7.1.tar.gz
openSUSE RPM packages
http://software.opensuse.org/search?baseproject=ALL&p=1&q=kmidimon
Regards,
Pedro
On Tue Aug 4 14:09 , Arnold Krille sent:
>On Tuesday 04 August 2009 12:36:40 Jan Depner wrote:
>
>> There really isn't much we can add to it. In fact, I think we probably
>
>> want to remove a couple of things ;-)
>
>
>
>For example that 10ms delay so it gets (more) usable for live-foh usage? ;-)
>
>
Unfortunately, I don't think there's any hope for that. That's just
processing overhead. I was thinking more of the per band delays. I added those,
mostly just for fun and to learn how the processing worked. They make a minor
difference in the output but not enough to warrant keeping them.
>
>Arnold
>
---- Msg sent via CableONE.net MyMail - http://www.cableone.net
Florian Faber wrote:
> Peter Plessas wrote:
>
>> how can i tell aplay to use just single channel(s) of my HDSP card?
>> When doing:
>> aplay -D default:Card=DSP file.wav
>> i get playback on all 18 channels.
>
> You probably want to try jack.
Thank you, i would like to stick with also for the time being since this
is part of a script that should use as little other components as possible.
regards, P
For Round 5, I have updated pulseaudio to the latest dev version.
pulseaudio 0.9.16-test4-7-gaa74
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
- This time round I can successfully load the pulse
module-jack-sink/source and play totem through pulseaudio+jack.
System load when playing totem goes up to around 20% which seems kind of
high but nothing like it would need to lock things up.
However I after about 15 minutes the jack source and sinks disappeared
and running "pulseaudio -k" returns with
E: main.c: Failed to kill daemon: No such process
This seems to be related to looking at the "Sound Preferences" dialog.
As it has happened a couple of times now.
Restarting pulseaudio brings both sink and source back and I can resume
playing with totem.
So it would appear that there are some stability issues with the
pulseaudio jack modules, gnome-volume-control and or pulseaudio.
- Testing skype returns with "problem with audio playback" if the
outputs are set to pulse so that is fairly annoying.
Running from the commandline I get this when I make a test call:
======================================
$ skype
ALSA lib control.c:874:(snd_ctl_open_conf) Cannot open shared library
/usr/lib/alsa-lib/libasound_module_ctl_pulse.so
ALSA lib pcm.c:2171:(snd_pcm_open_conf) Cannot open shared library
/usr/lib/alsa-lib/libasound_module_pcm_pulse.so
ALSA lib pcm.c:2171:(snd_pcm_open_conf) Cannot open shared library
/usr/lib/alsa-lib/libasound_module_pcm_pulse.so
ALSA lib control.c:874:(snd_ctl_open_conf) Cannot open shared library
/usr/lib/alsa-lib/libasound_module_ctl_pulse.so
ALSA lib pcm.c:2171:(snd_pcm_open_conf) Cannot open shared library
/usr/lib/alsa-lib/libasound_module_pcm_pulse.so
ALSA lib pcm.c:2171:(snd_pcm_open_conf) Cannot open shared library
/usr/lib/alsa-lib/libasound_module_pcm_pulse.so
ALSA lib control.c:874:(snd_ctl_open_conf) Cannot open shared library
/usr/lib/alsa-lib/libasound_module_ctl_pulse.so
ALSA lib pcm.c:2171:(snd_pcm_open_conf) Cannot open shared library
/usr/lib/alsa-lib/libasound_module_pcm_pulse.so
======================================
Seems to be library related as pulse is installed in /usr/lib64/ by
default. Skype is looking for the 32 bit libs. Figure there must be a
workaround for that one.
I run "yum install alsa-plugins-pulseaudio.i586" then skype doesn't
complain about problem with audio playback.
Instead I get these messages:
============
socket(): Address family not supported by protocol
ALSA lib pulse.c:272:(pulse_connect) PulseAudio: Unable to connect:
Connection refused
============
So I remove alsa-plugins-pulseaudio.i586
Now I try linking the /usr/lib64 module library to the /usr/lib folder
ln -s /usr/lib64/alsa-lib/libasound_module_pcm_pulse.so
/usr/lib/alsa-lib/
This doesn't work either. I see the same "Cannot open shared library..."
messages in the terminal.
So it looks like we need a workable solution for running skype with
pulseaudio on a 64 bit platform.
===================================
* Skype
You can just visit Skype's site and click on the Fedora 7 package.
Select to open it with 'Package Installer (Default) and you are done.
Alternatively you can install the Skype repository. Open a terminal and
type:
su -c 'gedit /etc/yum.repos.d/skype.repo'
In that file copy the following lines:
[skype]
name=Skype Repository
baseurl=http://download.skype.com/linux/repos/fedora/updates/i586/
enabled=1
gpgkey=http://www.skype.com/products/skype/linux/rpm-public-key.asc
gpgcheck=0
Now you can easily install/update skype by typing:
su -c 'yum install skype'
su -c 'yum update skype'
===================================
Also tried "usermod -a -G pulse user" where "user" is the name of the
user who needs to use skype.
Still no luck.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Winner: Jack and Pulse Audio. Pulse still a little unstable but mostly
working nicely with jack.
Looser. Skype. If I want to use Skype I have to turn off jack. However
if I get a usb phone then my problem is solved as I could set it as the
Skype device and use my onboard device for jack+pulse audio.
Conclusion.
Pulse Audio and Jack will work together if running pulseaudio v 0.9.16
or greater.
Just remember to
1: pulseaudio -k
2: start jack
3: puseaudio -D -nF ~/jackd.pa
Or add the above commands to the qjackctl config panel.
Patrick Shirkey
Boost Hardware Ltd
Hi,
Going on holiday to Prague/ Tjech Republic. I would like to experiment a bit
with filming and stuff. Any suggestions for a real cheapo camera? (I take my
bike with me, so it would be nice if I could make a 'filming while biking
construction' ;) )
Thanks,
\r
Nice article. But colored by ideology.
I "switched" from Linux to Mac because...
-Now I have the freedom of choice what kind of apps I want to use (free software or pro apps)
-I have no more headache about bad RT Kernels and user permissions
-Only one audio system - core audio - and it is easy to handle
-It works rock stable and very intuitive
-a very good workflow covering all technics of modern multimedia production
-the audio apps are mature production tools with all features I need
-Ableton Live - more then a DAW
-I can work with video and audio together without crashes
-I'm more productive with a Mac environment
-I doesn't need to be an geek/nerd to use my computer but I can if I want
Only some points. Very subjective.
I'm not "against" Linux -I think it is a nice OS for audionerds with a good amount of time.
And for pure harddisk recording, developing and testing new concepts. Sooperlooper is an good example: first made for Linux, then ported to OS X and now the "mainstream-Daws" Live and Logic have loopers as new features in their latest versions.
regards,
Michael
----- original Nachricht --------
Betreff: [LAU] Kim did the switch to Linux
Gesendet: Mi, 05. Aug 2009
Von: Frank Barknecht<fbar(a)footils.org>
>
> Hallo,
>
> here's an excellent read about Kim Casone (of .microsound and this list,
> too)
> switching from Mac to Linux:
>
> http://createdigitalmusic.com/2009/08/04/linux-music-workflow-switching-from
> -mac-os-x-to-ubuntu-with-kim-cascone/
> (URL in one line)
>
> Great work, Kim!
>
> Ciao
> --
> Frank
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user(a)lists.linuxaudio.org
> http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
>
--- original Nachricht Ende ----
On Fri, Aug 7, 2009 at 11:55 AM, Danni Coy <danni.coy(a)gmail.com> wrote:
>
> I'm wondering if a cycle is a good display for such a thing... Maybe a
>>> vertical line would be more easy, with some mark/ timing tools or something.
>>> Or be able to set loop ranges in realtime...
>>>
>>
> The Author designed it as a tool for creating non-linear music. It is
> usually used in a live context where the person using it is a musician of
> some kind. Like a musical instrument it does take some skill to master. The
> great thing about it is that the computer interaction is so straight forward
> that you can sing or perform with an instrument and use freewheeling and not
> have the two interfere with each other. ( a foot controller is a must for
> two handed instruments)
>
>
>
> Stick with it - It takes a bit of practice. But gets fun very quickly. I
> generally use Freewheeling for sketching out an idea then I import the loops
> into Ardour and do polishing there.
>
Thanks for the enthusiatic responses.
What is a foot controller and what can you do with it (with fweelin and
other apps)? I'm a total noob on such things.
\r