Research tells me that QSynth seems to be the only currently
available/usable GUI for FluidSynth, but I get big xruns whenever I try and
use it. FluidSynth itself doesn't cause me problems (I know because I'm able
to use the FluidSynth-DSSI plugin fine in Rosegarden etc). The problem is
that I want to use FluidSynth with Ardour3, but Ardour3 doesn't support DSSI
plugins yet. So the only solution I have is to find a standalone interface
for FluidSynth and then to link up using Jack. I looked at the old GUI
'FluidGUI' but it seems to be so old that it won't properly install on
recent versions of Ubuntu.
So does anyone know of:
1) A GUI for FluidSynth other than QSynth and FluidGUI?... or
2) An application other than the above 2 which would allow me to load
soundfonts?
Thanks in advance.
- Dan
I was very excited to find a video of the
complete
Tristan and Isolde on YouTube recently,
complete with
English subtitles.
I used the youtube-dl utility to grab the video,
but
when I began playing the copy on my hard-drive
with
totem, to my horror, the English subtitles
were
not there! To repeat, the subtitles are on
youtube.com but not in the .webm file that
I
downloaded with youtube-dl.
Can someone coach me how to download a version
with the English subtitles? Or are there subtitles
in my downloaded version and totem is just not
playing them?
Thank you for your help.
P.S. On the totem menu under View, there
is a
command called Subtitles
but this prompts me for
another file.
Is there a subtitle file in addition
to
the video file that I need to download from
youtube? Thanks again.
Hi all!
I found this old discussion about the Zoom R16 in the archive of LAU.
http://linuxaudio.org/mailarchive/lau/2012/3/14/188926
Strangely, in that archive there is a missing reply from Mr. Brett McCoy.
(You can find the missing one a the bottom of this archive:
http://linux-audio.4202.n7.nabble.com/Zoom-R16-td7748.html )
Mr. McCoy claims to have enabled the Zoom R8 (yes, there is quite a
difference between r16 and r8) as a multi-input soundcard for ardour and
also as a control surface in 12.04 64bits.
There is no information as to which driver is being in use in his post. And
searching the web only leads me to various WIP to get the R16 running on
linux.
My question is, has anyone got any news about this device and a possible
drivers?
Specifically to Mr. Brett McCoy: what driver did you use to make jack aware
of your r8?
Thank full for any hints, yours,
--
Set Hallström
AKA
reSet Sakrecoer
http://sakrecoer.com
Len:
> I was looking at the X(R)18. Which acording to Sweetwater has 16 i/o
> but on the Behringer site says 18/18. I would hope the manufacture
> is the right one. Actually, the sweetwater site says 16 USB channels
> in one place and 18 io half a page away... so I can see both numbers
> at the same time. :P
Fons:
> just a quick remark on USB and Behringer. At my new workplace our
> boss, in a fit of enlightment and for reasons only known to himself,
> decided to buy a cheap Behringer mixer with a USB interface. Nobody
> here needs it and it remained in its box for months.
> Some week ago I had some spare time and decided to have a look at
> it. Connected the USB to my Linux workstation and connected some
> headphones to the mixer. Result: with all faders down and just
> the HP volume turned up there was a high level 50/100 Hz in the
> headphones. Removing the USB connection was enough to stop it.
Patrick:
>> That is not bad considering that only a few years ago the idea of an
>> affordable plug and play digital hardware mixer on Linux was just that,
>> an idea.
Fons:
> It's not a digital mixer, nor did I suggest it was.
Just re-editing and recapping this, as I too was confused.
Fons was not talking about the XR18 or any of Behringer's new digital range.
mH
been pushed to the guitarix git repository. Those are simulations of the
following pedals:
Fuzz Face JH1
Fuzz Face Fuller Mods
Fuzz Face Roger Mayer
Foxey Lady
Colorsound Tonebender
Sustainer+Muff (Big Muff Pi)
Screamig Bird
Hornet
High Frequency Brightener
LPB-1 Booster
Hogs Foot
They are generated from schematic files, with our Ampsim Toolkit.
http://sourceforge.net/p/guitarix/blog/2015/03/j-hendrix-fuzz-face/
Schematic files (gschem) been included in the tools directory.
regards
hermann
Hi all,
My dual Delta 1010 setup is on its last legs and I'm thinking (again) of
retooling with a Saffire Pro 40. I've been bitten in the past by upgrades
like this which is why I'm still on the 1010s, but there's only so many
times I can repair them before I have to admit defeat.
Is anyone out there actively using a Saffire Pro 40 in a serious setting?
Is it reliable for low latency, with all channels working at once? Does it work
with any recent ffado, or do you need specific versions, patches or anything
else?
I've read plenty of vague comments about which firewire chipsets might be
good or not, but are there known-good PCI Express firewire cards that are a
sensible price and work well?
I'm really hoping for "Yes, I've been using one for a year and it's rock
solid," rather than "I've googled and it claims to be supported," or "Yes,
it's fine if you pull the latest beta7 branch from git and only use Acme
2000 firewire interfaces." Sorry to sound unduly cautious or skeptical ;)
In short, if I bite the bullet, retire my Delta 1010s and buy a Pro 40, are
the drivers and tools now at the stage where I reasonably expect to be up and
running again in a day rather than still fighting problems a week later?
Cheers,
bjb
Hello!
There were lot's of Berliners at LAC 2015 and after talking to some of them
we thought it would be nice to start a linux audio user group here in
Berlin.
This is an open call to all Berlin based Linux Audio users and developers!
Let's meet, talk and share knowledge :)
So far we have a mailing list[1] and an empty twitter account[2] (thanks to
Sam :))
Our first meeting will probably be held at C-Base in the next weeks.
We have no agenda yet, everyone is welcome, but me and Sam are more focused
on electronic music stuff.
Any suggestions on the date?
[1] (as soon as the DNS starts working properly we send you the link to
subscribe)
[2] http://twitter.com/LAudioBerlin
Cheers!
--
Bruno Gola <brunogola(a)gmail.com>
http://bgo.la/
Hi!
I already told you about Sebkha-Chott several times on this list,
usually speaking about our releases (always under GNU/Linux, from the
beginning to the end).
Actually, Sebkha-Chott also uses GNU/Linux on stage to manage sound,
lights and video of the whole show (see details below).
I usually don't post shows list or tour schedule here (maybe I should),
but this time it's a big and international festival, so it might be that
some of you will be interested in it.
So Sebkha-Chott will play at Brutal Assault Festival #20 in Jaromer
(Cz), for the third time, but for the first time, we will use the
GNU/Linux live setup they have on tour. The final schedule is not known
yet, but it will be between 5th and 8th of August. If some of you live
near Cz, are metalheads, that's the place you should be (if you ask me,
this year's line-up is really great, the best I've known since I know
this festival).
http://www.sebkhachott.net/15-years-of-sebkha-chott-kourt
Here it is (please note the video and lights part of the system won't
probably play at Brutal Assault due to very tight changeover schedule).
*Description of Sebkha-Chott's live setup*
*Distribution*
All machines, including RPI, are running Debian systems, mostly Jessie.
http://www.debian.org
*Session Handling*
Session handling is managed through ladish and on some control machine
small shell scripts.
http://ladish.org
*Audio*
/Routing/
All the routing is managed through ladish, jack is configured with the
restrict self-connect option.
/Mixing/
The mixing/processing of any audio signals coming from the instruments
on stage or from "virtual sources" inside the machines (synths,
samplers) is done through a bunch of Non-Mixer (probably not uptodate)
instances, running independently one from the other. All these
Non-Mixers finally ends up in the FOH mix or on of the three monitors
mix (which goes to in-ear monitors system). We highly recommend
Non-Mixer for this type of setup, as you don't need a timeline, and
Non-Mixer is really lightweighted, OSC controllable, and flexible.
Ecasound might have done the job too, still.
http://non-mixer.tuxfamily.org/
/Live Looping/
The "instrumental line-up" contains 2 basses, 2 guitars, 3 vocals and a
drumkit, each of them goes to a single looper (for the drums, we only
loop a stereo submix). We use Sooperlooper (probably not uptodate, and
(uglily) patched so that Jack Transport Synchronization with SL as a
master works with it and is recalled when at session load).
http://essej.net/sooperlooper/
/Synths/
Additionnally to the physical instruments, 5 synths are running, 3 of
them polyphonic, 2 of them monophonic. We use Alsa Modular Synth
(probably no uptodate) for this. You might get the patches on github
(see below)
http://alsamodular.sourceforge.net/
/Samplers/
A virtual drumkit is also used, with really-non-drumistic sounds. We use
tapeutape (patched not uptodate version) for this purpose.
http://hitmuri.net/index.php/Software/Tapeutape
/Clic/
We use Klick to send clic in every monitor.
https://github.com/dsacre/klick
*Lights*
Lights are controlled using QLC+. We use four profiles projectors and 4
LED "barres", which are split into 8 RGB segments each, each segment
mightbe controlled independently from the others.
http://qlcplus.sourceforge.net/
*Video**s*
Videos and Moving images are displayed on three V-form screens. Those
videos are displayed using a self-developped software called PytaVSL
(derivating from VSL, a set of pd patches we used on a children show)
and based on Pi3D. This runs on RPIs (old ones, not the big beasts you
might get for 30$!!!).
This lays on a mapped-layers principle, each of them might be mapped
with images or videos, the content can be changed with OSC control, and
you can move or change properties (including visibility/inivisibility)
of a layer using OSC too.
By now, PytaVSL is not recommended for anyone except us (or you will
have to put your hands in it, and you'll see then we're no real devs!!!).
https://github.com/orlammd/pytaVSLhttps://github.com/tipam/pi3d
*Controls*
/MIDI/OSC Routing/
The whole thing is controlled via a centralized OSC/Midi router. We use
Mididings for this purpose, and we highly recommend it, it's a really
good piece of software which makes everything possible in such a setup.
The version we used has been patched to be able to route/filter/manage
OSC messages too. I propose this dirty patch to Dominic and I know he
has worked on this, but I couldn't tell what's the current state of the
software, as we do not use an uptodate version on this neither!
/PedalBoards/
We use DIY pedalboards to trig the sequencers, loopers, and to change
instruments sounds (including synths). These pedalboards are made of a
"règle de maçon", push-buttons and a Teensy2.0 programmation board. It
basically sends an OSC message /pedalBoard/button #number when you press
a button. These messages are then managed by Mididings. There are two
pieces of software for this, one on the board, one on the receiving
computer.
https://github.com/AMMD/Poly_PedalBoard
/Touchscreen Interfaces/
All the mixers, the LASDPA plugs, and in some case the synths are
controlled using touchscreen interfaces. We've developped a programm for
this purpose called Ghislame. Initially developped in C++/Fltk, we
ported it to python/kivy and finally it now uses a JS engine. Initial
versions controlled more things (loopers, synths, mixers, lights), but
in a quite weighted way. Current version (JS) only controls Mixers and
Plugs, but does it much more fluently.
One of these touchscreen interfaces is placed at FOH, so that mix of the
show might be done from FOH. The other ones are sprayed on stage so that
musicians might control their monitoring and some other things easily.
https://github.com/jean-emmanuel/oschtmlguihttps://github.com/AMMD/kvGhislamehttps://github.com/AMMD/Ghislame
/Visual Monitoring/
Several small laptops are placed on stage with LiveDings (Mididings
frontend) and slgui (SooperLooper GUI) running on them.
*Sequencers*
/Midi Sequencing/
seq24 in a really really patched version is used to sequence MIDI. It's
used in matricial mode, and the patches we've done acts on many things:
arbitrary number of beats in a measure, abitrary number of measures in a
sequence, n-tuples, 16x13 matrix (instead of 8x2), play/stop
controllable by Program Changes, and other crappy things. I really don't
recommend our patched version which contains many bugs we learned to
prevent! It's the very first software we've been patching, and....
wel.... seq24 is synced to Jack Transport as a slave. As far as I know
this doesn't work anymore with more recent version of seq24, and as a
result, our version is not uptodate. We will certainly change about this
when we'll have time. We attend much from Non-Sequencer on that point! ;)
/OSC Sequencing/
Over the Midi Sequencing, OSC sequencers are running. One controls the
lights, one controls the videos, another one might send messages to
audio machines (including seq24), and one runs over them all and might
send the BIG SEQUENCE messages!
We use a self-developped software called pyOSCseq. This sequencer can
run looped sequence (as any other sequencer) but also can send on-shots
sequence (many uses in theater context).
https://github.com/jean-emmanuel/pyOSCseq
/Jack Transport/
Jack Transport is used to synchronize every tempi/triggers and so on.
Sooperlooper is Jack Timebase Master, and the other pieces of software
that might be sync to are slaves. Considering that Sebkha-Chott'music is
composed of many sequences in many metrics and tempis, with highly
contrasted way of passing from one to the other, this point was a very
critical point at the beginning of our work with machines (in 2008).
--
ORL
AMMD - Freak & Free Arts Coo[r]p
www.ammd.net - 095 234 72 48
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
this is something that has annoyed me endlessly for years, and i still
haven't found a solution.
the issue is minor (that's why i haven't asked before), but annoying
nevertheless.
so:
i'm using qjackctl with the "system tray icon" enabled.
when i close the application window, qjackctl keeps running and is
accessible via the system tray.
cool. that's what i want.
however, every single time i close the main qjackctl window, a balloon
pops up in my notification area, telling me that the "program will
keep running in the system tray" and how to really shut it down.
the first time i read this, this information was informative (i
suppose, it has been years). but no longer.
i already know that the program will keep running. that's why i'm
using the system tray. there's no need to tell me again and again
(even within a single session!).
there *must* be simple way to "not show this message again", without
completely disabling tray notifications. but how?
btw, this is on Debian/sid with xfce4.
fgasdmr
IOhannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJU0eVfAAoJELZQGcR/ejb4SY0P/3NphEAkGRawvdm4espj7i1J
CIIGtUFTyvsKwFXEqXtAdlHz3/mt9pv1H17LEWdIxOfJ+ziY5dOC1HbAnNSPXmte
91AGmrFCNC8uKSrvCx+kySJEiU4AbNaSY0g8ORKMvOuCPAdO//9qXFBcSRaPX5eb
rT7xtGKK+NYTmFSiPIypjW0ttGabtIjJE+Pg8e674rep+Q63ovxPBTBzkVcvJt4J
udTKPc8+V7vZvC0Q0y4/vwiih5l0+7RypNxuapm+KY8zSgSkGUc2Wug2XMPhaLid
Zmej+Kn/72PZflC5p7uo9JOZkXcShO7SX6296oaFqhFdtxlkUxmggZf/D6eeIGhA
91bACU/+GVgfXE8QUXX0XaifvstBaEwUMdpLIB9lLhC6sdROpl6hHFz/JMJSJYqt
pX0oFI1YNzaT65E0BzOfQa4yxuyNO4BoYZ/C7wg4WtSMd/zHaiK5z9K0nxh1ruDM
5BNgeYNtvQ++FO3V0/eVkOwqab6hdS8/MfLRbro/BmJbNsg4MTDUxHZiL1AzXhIz
6l/SbMsdExY3NgbDQiVmfoW6P9MGDrBO/7n6DZj6g7O5lmtEdR9jhPKpFN3ApJzr
+yVkxrcppph9eNMMUtAWnXh+XBGuuvfdrhakHoAZIaDGa3P7f6GsBjufyrysKGT1
SRBESzDoiLj+5K3rCOYr
=ertZ
-----END PGP SIGNATURE-----
