Hi list,
I have been search the archives and the web a bit and it seems there is
no easy way to route html5 audio playback from firefox through jack on
Debian testing.
Is this still the case or has there been recent development that might
enable it? What would have to be done to make it work? This
functionality is the last piece in my puzzle to finally get rid of
flash.
thanks for pointers,
P
Hi there!
ShowQ is a unique cue-player for Linux-Audio-Users. I use it as a core
application for my theater activities.
Even in the linux-community it's not a very well known application,
although there's no other linux-program (I know) if you need a
one-shot-audio-player with features like f.e. programmable fade-in,
fade-out, no matter if you want it time-based or triggered by space (or
another key).
It can do a lot more - ShowQ has MIDI-support. Although I never tested
this feature, it should be possible to control any application with
MIDI-support. QLC(+) f.e. - or maybe some video-players do support MIDI
- I don't know...
Yeah, of course, ShowQ is not a drop in replacement for QLAB, but
speaking about audio it fits quiet perfectly in my setup.
ShowQ is in the Debian (and Ubuntu?) repositories, it's written in C++
and of course released under the terms of the GPL. Although this app is
quiet useful for technicians like me, the development stopped years ago.
I am not a coder, but I do my best to keep this project alive. On the
Debian bug-tracker I write bug-reports for ShowQ, hoping that on one
hand it's useful for other users to work around problems, on the other
hand that someone fixes them.
Last time I reported a bug Jaromír Mikeš the Debian-maintainer of ShowQ
wrote that he is not able to fix the bugs and he would like to kick
ShowQ. Of course, he also would like to package an alternative if there
would be some he could package.
I don't know any - so my linux-based theater setup is about to be killed
one day when ShowQ wouldn't compile on my debian machine, anymore.
So, what do I want from you?
Test ShowQ! Maybe it's the app you've been missing for a long time!
And if you're a coder with C++-skills, check out my bugreports on
https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=showq
- maybe you've got the clue...
OR: Got an alternative to ShowQ? You're welcome!
Greets!
Mitsch
Hello there LAU,
I'm trying to update the old demos on the ZynAddSubFX site and I thought
it would be great to replace the old demos with songs from the LAU community.
Can anyone post some links to some of their favorite tracks that make
good use of Zyn?
Ideally they'd be on something like soundcloud so they could be
gathered onto a playlist on the project page, but if not it should be
fun to hear what people have been making.
--Mark
Hi, I set up my laptop to initiate Calf Plugin (Fluidsynth) and Qjackctl
at login.
When I then login, I get no sound from various apps. The
preferences->Sound->test sound
also produces nothing. Running Totem, just hangs - no output and the
progress bar stays at 0.
I've now disabled Calf and Qjackctl at login and it all works again. Can
anyone explain
what is going on?
Output from aplay -l:
$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
(this is with it working, but it looked the same when not working)
Thanks,
Bill
--
+----------------------------------------+
| Bill Purvis |
| email: bill(a)billp.org |
+----------------------------------------+
Hi everyone,
I just released a set of Yoshimi patches, including some instruments and
patchsets (performance or combin to some hardware users).
You can download them here:
https://freeshell.de/~silvain/software/jg_yoshimi_patches-0.1.tar.bz2
My first ten instruments and 3 patchset! At this point: a HUGE thank you to
Will Godfrey for the tireless and tremendous work he's put into Yoshimi over
the past few years and in particular the efforts he's put into the new
commandline interface over the past few weeks. It's simply amazing! Still a
little rough, but with complete access to all parameters. Will: you're a
jewel! <3
I can only say, that Yoshimi is a treasure trove of sonic possibilities. I've
never seen such humungous and complex oscillator block before.
Enjoy and I'd love some feedback. :)
Best wishes,
Jeanette
Please don't reply off-list. On the list there are several subscribers
who maintain an Ubuntu flavour, that AFAIK by default combines jackdbus
and pulseaudio, they could help you much better than I could do, since
I categorically refuse pulseaudio.
On Tue, 27 Sep 2016 11:29:34 +0100, Bill Purvis wrote:
>Thanks Ralf, but it was all working with jack in place before I set
>this up. Pulseaudio is latest version from LAU so I don;t see why
>there should be a problem.
You should mention what pulseaudio version, jackd version etc. you are
using, since "latest version from LAU" is not really useful. Perhaps
mentioning the distro and it's release could be also helpful. I never
used pulseaudio and never ever will use it, I don't have it installed,
so I only could provide a link:
http://www.jackaudio.org/faq/pulseaudio_and_jack.html
Regards,
Ralf
Hi,
today we have published the video of another single of John Option:
Lifestyle obsession.
As usual we published the song under the terms of the Creative Commons
License (CC-BY-SA) and we produced it only with free software:
Ardour, Hydrogen, Jack, Qsynth, CALF, and many other
great free audio software that we used under Debian GNU/Linux.
Here you can listen the single and see the video (made with kdenlive):
https://youtu.be/6gm-3G-ZJmI
As for the previous songs we published in our website[1] the single
recording tracks and the complete Ardour session. All this material is
published under the terms of the Creative Commons license Attribution
Share alike so that anyone can use our tracks to produce a remix of our
song or even a new song that have to be published under the same license.
You can find all about our project here: http://johnoption.org
If you feel like I'd love to read your feedback, because the
encouragement of the people who listen to us and appreciate the
philosophy of our project is the only fuel for us to continue. And if
you like to be updated about our next release, please subscribe to our
YouTube channel or any other social network you like (see link to our
profiles on our website[1]).
Best regards,
Max-B
1. http://johnoption.org
--
IM: massimo(a)jabber.fsfe.org - GnuPG Public Key-Id: 0x5D168FC1
[this message has been sent to the alsa-users ML too]
Hello,
in the last two weeks I've been working on two MIDI related personal
projects.
MidiMemo is an automatic MIDI recorder; the concept is similar to the one
of JACK Timemachine and the autorec feature of Pianoteq: you don't need to
remember to hit record everytime, since it automatically connects to every
available and readable ALSA MIDI port and records every incoming event. New
hardware/software devices are automatically connected too without the need
for user interaction. As soon as MidiMemo receives a midi event it will
start a new "stream", there is a configurable minimum time after which it
will actually remember the stream, otherwise it will be discarded; another
configurable "last event limit" time will allow you to set how much time
MidiMemo will be waiting for new events before closing and saving the
stream. Each stream can be inspected, with a full list of the recorded
events that can be filtered and, eventually, exported to a .MID file, even
with a time conversion.
There are still some bugs (a strange export problem with sysex messages I'm
trying to solve) but it works fine for "normal" playing.
https://github.com/MaurizioB/MidiMemo
MidiGraph is a graph inspector for ALSA sequencer, and it is intended for
developing or debugging purposes. It displays every available client and
port, even those that are not normally listed using aplaymidi/arecordmidi
or QJackCtl, with detailed information about every port (type and
capabilities) and connection.
https://github.com/MaurizioB/MidiGraph
Both of them are written in Python 2.7, and require PyQt4 and pyalsa.
I'm still developing them, there's no setup yet and some bugs and features
still need work.
I hope you will find them useful, and I'd be glad to have some feedback.
Cheers,
MaurizioB
>>* Would you guys have any idea what I can have a look at?
*>
> Sounds like a pam_limits.so not getting loaded. I'd compare the contents
> of /etc/pam.d/ on 16.10 with the one on 16.04.
All right, interesting - so downloaded the source code of lightdm in
16.04 to compare the pam config files and they look a lot different.
So I guess lots of work is being done there - what I find interesting
is that the 16.04 version of the lightdm conf does not include
pam_limits.so.
Files are below.
16.10:
#%PAM-1.0
auth requisite pam_nologin.so
auth sufficient pam_succeed_if.so user ingroup nopasswdlogin
@include common-auth
auth optional pam_gnome_keyring.so
auth optional pam_kwallet.so
auth optional pam_kwallet5.so
@include common-account
session [success=ok ignore=ignore module_unknown=ignore default=bad]
pam_selinux.so close
#session required pam_loginuid.so
session required pam_limits.so
@include common-session
session [success=ok ignore=ignore module_unknown=ignore default=bad]
pam_selinux.so open
session optional pam_gnome_keyring.so auto_start
session optional pam_kwallet.so auto_start
session optional pam_kwallet5.so auto_start
session required pam_env.so readenv=1
session required pam_env.so readenv=1 user_readenv=1
envfile=/etc/default/locale
@include common-password
16.04:
#%PAM-1.0
# Block login if they are globally disabled
auth required pam_nologin.so
# Load environment from /etc/environment and ~/.pam_environment
auth required pam_env.so
# Use /etc/passwd and /etc/shadow for passwords
auth required pam_unix.so
# Check account is active, change password if required
account required pam_unix.so
# Allow password to be changed
password required pam_unix.so
# Setup session
session required pam_unix.so
session optional pam_systemd.so
Hi all,
Is testing Ubuntu 16.10 these days, noticed something interesting.
Since upgraded to 16.10 Yakkety, modifications in /etc/security/limits.conf
are not taken into consideration when logging in the graphical interface.
Reported the bug already to Ubuntu, but if I could find a workaround in the
meantime...
/etc/security/limits.conf:
@audio - rtprio 99
@audio - memlock unlimited
I tried the same settings in /etc/security/limits.d/audio.conf, to the same
results.
After logging in Unity, opening a console, the limits are not set:
blablack@ideaon:~$ ulimit -l -r
max locked memory (kbytes, -l) 64
real-time priority (-r) 0
Reloging to my user DOES apply the limits:
blablack@ideaon:~$ ulimit -l -r
max locked memory (kbytes, -l) 64
real-time priority (-r) 0
blablack@ideaon:~$ su blablack
Password:
blablack@ideaon:~$ ulimit -l -r
max locked memory (kbytes, -l) unlimited
real-time priority (-r) 99
Switching to a console (ctrl+alt+f1) and logging in would apply the limits
as well.
The exact same setup used to work fine on Xenial 16.04 before upgrade.
I think it's something with Pam and Lightdm (or at least a lot of googling
is pointing me in that direction).
Would you guys have any idea what I can have a look at?
Thanks in advance,
Aurélien