Hello,
Does anyone know of a good plugin that will generate subharmonics?
I would like to put a little more low frequency "oomph" into my bass
track. Preferrable LADSPA, but VST would work, too.
Thanks for any help!
-TimH
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
I am also looking to have a conversation about recording hardware, but
not quite the same as the PCI one.
Short story:
If I wanted to have a combination of two separate devices,
analog->ADAT unit and ADAT->Linux@computer, what would I buy?
Long story:
The way that I did quality recordings so far:
- use a quality preamp from mic to S/PDIF optical
- use a USB soundcard with (under Linux) working S/PDIF in
- jackd of course
- depending on hardware there might be a separate piece in front that
converts symmetric microphone level to line out, but right now my
first thing does both mic level and line level well
I really like how this is separating out the [analog part, A/D
converter] and the [thing that needs a Linux driver]. Now I can
change one or the other and don't get utter breakdown on software
changes. I have hardware pieces for which this works great... ish
except for some USB unreliability.
Now, the careful observer will notice that this is limited to 2
channels due to S/PDIF. While I could have more USB soundcards that
does not satisfy synchonization since the stupid things with S/PDIF
don't take world clocks. My attempts to link multiple jackds have
been, well I think everybody here knows that this exactly working
well.
So I want to get the concept of separating this out further. Now I
need:
- analog part is a few line in or mic level inputs to ADAT
- a "soundcard" that takes binary ADAT and gives me Linux-able input.
Ideally I would like this to be 24 bit capable (I don't need > 48
MHz but I'd like > 16 bit)
- once there I could add more sync ADAT takes a world clock
I wonder whether somebody has recommendations for these two parts.
Digital part with great Linux support, and what do I use for analog to
ADAT?
My computers still have native PCI, but... well to be honest PCI
sucks, USB sucks, Firewire is old. Is anything Thunderbolt out yet
that does ADAT to Thunderbolt with open source Linux drivers? Haha,
very funny. Can we make one?
Sorry for the long post. I hope the concept makes sense. I really
like this more modular setup that allows you to toss one thing at a
time and don't sit there with nothing on changes.
Martin
--
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <cracauer(a)cons.org> http://www.cons.org/cracauer/
Hi all,
Does anybody know if there are good octave plugins/standalone available on Linux?
My aim would be to use my guitar also as a bass guitar avoiding to buy one.
Anybody tried this solution do you think is feasible?
Does guitarix for instance provide a tool like this now (I'm using an non-updated version on my Linux squeeze box)?
Many thanks
Nicola
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Hi list,
today I got some time to play around with RME's Madiface (and its
ExpressCard) under Linux/Jack. The card uses Thomas' old hdspmixer with
correct display and routing abilities, it's simply awesome to have 64Ins
and 64outs on a Linux laptop!
However I didn't get beyond the following weird problem:
Starting PureData outputting 64 channels via jack as
pd -jack -channels 64
works and connects and outputs to the Madiface's hardware outs.
If I try to start other audio software (mplayer, alsaplayer) asking them
to output to the first two jack outputs (while Pd is also using them),
I get in qjackctl's message window
no ports available!
and in mplayer
cannot deliver port registration request
[JACK] not enough ports available
Failed to initialize audio driver 'jack'
and in alsaplayer
cannot deliver port registration request
cannot deliver port registration request
Segmentation fault
all followed by a massive xrun in qjackctls message window
**** alsa_pcm: xrun of at least 4995.700 msecs
Now if I start Pd with less outputs, for examples
pd -jack -channels 32
then mplayer is perfectly able to output on the the first two hardware
channels in parallel with Pd.
The weird thing: Jackd's 'max port' argument is set to 256, and the problem persists
also with 512 ports.
Am I missing something here?
Background info:
jackd version 0.124.1 tmpdir /dev/shm protocol 25
is started via qjackctl as
jackd -P89 -t5000 -dalsa -r44100 -p256 -n2 -D -Chw:Default -Phw:Default -i64 -o64
on kernel
3.14-2-rt-amd64 #1 SMP PREEMPT RT Debian 3.14.15-2 (2014-08-09) x86_64 GNU/Linux
Thank you for any suggestions!
Peter
Hi All,
I've been a reader on the list for a while, not a poster until now.
I am preparing to outfit a computer for songwriting in Linux.
I will be using the command line notation options, of which there are
rather
a few from Lillypond to muscript.
I am hoping that how I picture this will match the creative reality smiles.
My first question is this.
some high end soundcards that are supported in Debian? I know its been
updated, but I intend using squeeze for a start. Getting the floor solid
before say adding updated furniture.
While I know that four duplex cards are common, I want the best quality I
can find for the work.
say if you <hope this makes sense> wanted to connect a full sized piano
keyboard to the card?
Thanks in advance,
Karen
Ahoy!
Stepping up to Summer'15 release frenzy stage scene, in it's fourth and
hopefully last act,
Qtractor 0.7.0 (muon base beta) is out!
Qtractor [1] is an audio/MIDI multi-track sequencer application written
in C++ with the Qt framework [2]. Target platform is Linux, where the
Jack Audio Connection Kit (JACK [3]) for audio and the Advanced Linux
Sound Architecture (ALSA [4]) for MIDI are the main infrastructures to
evolve as a fairly-featured Linux desktop audio workstation GUI,
specially dedicated to the personal home-studio.
As a major highlight to this release, there's the advent of regular MIDI
controllers mapping/assignment to main application menu command actions,
just like normal PC-keyboard shortcuts, is being introduced (cf. main
menu Help/Shortcuts...).
Have a 'hotta' Summer'15 ;)
Enjoy.
Website:
http://qtractor.sourceforge.net
Project page:
http://sourceforge.net/projects/qtractor
Downloads:
http://sourceforge.net/projects/qtractor/files
- source tarball:
http://www.rncbc.org/archive/qtractor-0.7.0.tar.gz
- source package (openSUSE 13.2):
http://www.rncbc.org/archive/qtractor-0.7.0-18.rncbc.suse132.src.rpm
- binary packages (openSUSE 13.2):
http://www.rncbc.org/archive/qtractor-0.7.0-18.rncbc.suse132.i586.rpmhttp://www.rncbc.org/archive/qtractor-0.7.0-18.rncbc.suse132.x86_84.rpm
- wiki (help wanted!):
http://sourceforge.net/p/qtractor/wiki/
Weblog (upstream support):
http://www.rncbc.org
License:
Qtractor [1] is free, open-source Linux Audio [6] software,
distributed under the terms of the GNU General Public License (GPL [5])
version 2 or later.
Change-log:
- Complete rewrite of Qt4 vs. Qt5 configure builds.
- Revised MIDI Controlllers catch-up algorithm.
- Mixer multi-row layout gets a little bit of a fairness fix.
- Non-continuous MIDI Controllers now have their Hook and Latch options
disabled as those are found not applicable,
- As an alternative to PC-keyboard shortcuts, MIDI controllers are now
also assignable and configurable for any of the main menu command
actions, all from the same old configuration dialog (Help/Shortcuts...).
- Fixed missing Track and Clip sub-menus from Edit/context-menu that
were found AWOL ever since after the Lazy Tachyon beta release (> 0.6.6).
- An off-by-one bar position (as in BBT, bar, beat and ticks) has been
purportedly fixed as long as LV2 Time/Position atom event transfer goes.
- French (fr) translation line to desktop file added (patch by Olivier
Humbert, thanks).
- A new top-level widget window geometry state save and restore
sub-routine is now in effect.
- Improved MIDI clip editor resilience across tempo and time-signature
changes.
- Keyboard shortcuts configuration (Help/Shortcuts...) now lists
complete menu/action path where available.
- Fixed in-flight VST plugin editor (GUI) resizing.
- Added support to LV2UI_portMap extension, found really handy for the
cases where you have multiple plugins with different port configurations
and a single common UI to drive them all (pull request by Hanspeter
Portner aka. ventosus, thanks).
References:
[1] Qtractor - An audio/MIDI multi-track sequencer
http://qtractor.sourceforge.net
[2] Qt framework, C++ class library and tools for
cross-platform application and UI development
http://qt.io/
[3] JACK Audio Connection Kit
http://jackaudio.org
[4] ALSA, Advanced Linux Sound Architecture
http://www.alsa-project.org/
[5] GPL - GNU General Public License
http://www.gnu.org/copyleft/gpl.html
[6] http://linuxaudio.org
See also:
http://www.rncbc.org/drupal/node/917
Enjoy && keep the fun.
--
rncbc aka. Rui Nuno Capela
Jeremy, we shouldn't discuss this in the original thread.
There are latency test measurements in the mailing list archive. PCI and
PCIe cards show better results, IOW less MIDI jitter. There are also
explanations why USB suffers from more jitter.
The point of difference is, if the MIDI jitter is audible. It is! The
measurements might not provide correct results. To measure a system by
itself is a bad test and to measure a MIDI loop in addition is tricky.
Jakob (living in Augsburg) from a Linux mailing list (perhaps LAU or
LAD) years ago send me a board to loop through MIDI and that provides an
audio output, to record the MIDI signal to an audio track. I never had
time and interest to continued my MIDI jitter tests, so I still didn't
use it. I guess this would be a better test, then the latency test.
Howsoever, it's better to use PCI or PCIe, IIRC some USB interfaces
even fail(ed) the latency test that measures a MIDI loop. The USB
interface I own doesn't fail the test, but I'm anyway not satisfied and
use PCI and PCIe MIDI only.
That's it, I can't provide more information and I'm not willing to
search the mailing lists archives.
Regards,
Ralf