Hi,
I tried really hard to figure this out on my own... I have a patchbay
profile that is supposed to connect PulseAudio JACK Sink-01 to ecasound.
But, it doesn't do it; when the computer boots, the connection I see in
Jack is PA Jack Sink to system. I always have to manually remove that
connection, and manually connect it to ecasound (so my ecasound crossover
network works with mpv media player or whatever uses PA).
The patchbay profile does work to connect Pianoteq to ecasound; just not
Pulse Audio Sink to ecasound. Any ideas? I have gotten a little familiar
with the scripts used, like pacmd and pajackconnect. I tried to customize
pajackconnect, adding a new start_ecasound function that made this
connection, but so far have not gotten that to work...
Thanks,
John
spectmorph-0.3.2 has been released.
Overview of Changes in spectmorph-0.3.2:
----------------------------------------
* Added new unison effect.
* New instruments: pan-flute, synth-saw.
* UI improvements:
- support operator folding (to preserve screen space)
- provide scrollbar if morph plan window height is large
- repair operator move
* VST plugin crash fixed.
* No longer depend on BEAST/Rapicorn
- use libsndfile for sound file I/O, added WavData API
- refactoring, move libnobse code into SpectMorph
* Add icon/.desktop file for smjack
* Added debian package support.
* LPC/LSF morphing code updates - but now disabled by default
What is SpectMorph?
-------------------
SpectMorph is a free software project which allows to analyze samples of
musical instruments, and to combine them (morphing). It can be used to
construct hybrid sounds, for instance a sound between a trumpet and a flute; or
smooth transitions, for instance a sound that starts as a trumpet and then
gradually changes to a flute.
SpectMorph ships with many ready-to-use instruments which can be combined using
morphing.
SpectMorph is implemented in C++ and licensed under the GNU LGPL version 3
Integrating SpectMorph into your Work
-------------------------------------
In order to make music that contains SpectMorph, you currently need to use
Linux. There are four ways of integrating SpectMorph sounds into music you
create:
- LV2 Plugin, for any sequencer that supports it.
- VST Plugin, especially for proprietary solutions that don't support LV2.
- JACK Client.
- BEAST Module, integrating into BEASTs modular environment.
Note that at this point, we may still change the way sound synthesis works, so
newer versions of SpectMorph may sound (slightly) different than the current
version.
Links:
------
Website: http://www.spectmorph.org
Download: http://www.spectmorph.org/downloads/spectmorph-0.3.2.tar.bz2
There are many audio demos on the website, which demonstrate morphing between
instruments.
--
Stefan Westerfeld, Hamburg/Germany, http://space.twc.de/~stefan
Dear Linux Audio Community,
Linux Audio plays a major role in hearing aid research in the north-west
of Germany. The HoerTech gGmbH - a small non-profit research institute
for hearing aid system technology is offering again a developer
position. More details about the job are here:
http://www.hoertech.de/en/h%C3%B6rtech/career.html
Best regards,
Giso
DrumGizmo version 0.9.13 now available!
Get it at http://www.drumgizmo.org/
DrumGizmo is an open source, multichannel, multilayered, cross-platform
drum plugin and stand-alone application. It enables you to compose drums
in midi and mix them with a multichannel approach. It is comparable to
that of mixing a real drumkit that has been recorded with a multimic setup.
Included in this release is:
* Diskstreaming support, so you no longer need huge amounts of memory
to run it, even with the big drumkits.
* A completely new and redesigned plugin UI.
* And for the hardcore FreeBSD users: OSS support!
We know a lot of you have been waiting for diskstreaming to be
implemented, so please help us out by giving it a thorough test. We're
interested in hearing about your experiences with it, especially on low
memory setups with slower HDD's. Any comments and / or bug reports can
be directed to us on IRC, Freenode, #drumgizmo. Or feel free to ask at
the official DrumGizmo forum[1].
For the full list of changes, check the roadmap for 0.9.13 [2].
And now, without further ado, go grab 0.9.13!!! [3].
Important note to package maintainers:
Since version 0.9.11 we copy vst source files into the build tree while
building the vst plugin. This mean that should you wish to make a
tar-ball available with the build directory after the build has finished
this must either be stripped of said files or not be made public.
[1] https://linuxmusicians.com/viewforum.php?f=55
[2]
http://www.drumgizmo.org/wiki/doku.php?id=roadmap:features_roadmap#version_…
[3] http://www.drumgizmo.org/wiki/doku.php?id=getting_drumgizmo
On Tue, April 18, 2017 12:36 pm, Claus Lensbøl wrote:
> Hi Chris
I hope you do not mind, but I have taken the liberty of replying also to
the linux-audio mailing list. The question was originally asked there,
and many others are more experienced than I with netjack, so keeping
replies there is better to get the most accurate information, as well as
to benefit others who may have similar questions and search the mailing
list archives for possible solutions.
> I have on my master node (Ubuntu Studio 16.10), let the system start
> jack, and the loaded the netmanager as:
> jack_load netmanager
I see here a confusion possibly on my part. Your original email stated
that you wished to " set up a Raspberry pi as an output for jack"
Which is why I asked explicitly:
>>> So I'm trying to set up a Raspberry pi as an output for jack.
>>
>> Meaning that the R-Pi has the audio hardware, i.e. R-Pi is master?
By that do you mean the Rasberry pi has the only audio output? In that
case the Rasberry pi should be the master, the Rasberry pi must start jack
first with the ALSA driver (assuming R-Pi uses ALSA for the audio
hardware, I am not directly familiar with the details of that hardware).
After the master (the device with the audio hardware) has started jack
successfully then you use jack_load to load the netmanager.
> At this point I can on the Pi start jack as:
> jackd -R -d net
That would allow using software on the R-Pi to play audio on your Ubuntu
computer.
> , and have it connect to the master (where I, on the master, can see
> the Pi using qjackctl).
> This is where I get into the problem where running (on the Pi):
> jack_load audioadapter
You have configured the R-Pi as a slave of the Ubuntu computer, you do not
usually load audioadapter on the slave.
Well, I guess that is not entirely accurate. You would not load
audioadapter on the slave if you wanted one machine to have audio output,
and the other machines to be connected by network to that single audio
output.
What are you trying to accomplish? Which machine will generate digital
audio data, and which machine should output audio?
Are you perhaps attempting to have both the local audio device on your
Ubuntu computer play audio, and also the R-Pi available to play audio? In
that case what you are attempting may be the correct way. If you do not
need to use an audio interface on your Ubuntu computer then make it slave
only (use net as the driver instead of ALSA, use ALSA as the driver for
the R-Pi).
> , results in:
> could not load audioadapter, intclient = 0 status = 0x 1
Look also at the jackd status messages. I attempted to load audioadapter
on a machine where the only audio interface was already in use by jackd
and got this on the console where I executed jack_load:
$ jack_load audioadapter
could not load audioadapter, intclient = 0 status = 0x 1
But also saw these additional messages from jackd:
../linux/alsa/JackAlsaAdapter.h:225, alsa error -16 : Device or resource busy
That makes sense on my machine, the audio interface is already exclusively
used so audioadapter could not use the device.
Perhaps on your R-Pi there are informative messages as well.
> I think I was assuming that I could not play music from the Pi using
> jack_play when the Pi had another master, but I should be able to test
> that out tonight.
That previous suggestion was based on the assumption that the Pi was the
master since you stated you wanted the Pi to be the audio output.
I was assuming that the Pi would be the jack master, since typically in an
audio production setup where jack is often used you do not want the audio
to be resampled, so you have just one master, a single device with the
audio output.
>>> What I've done is to follow this guide:
>>> https://github.com/jackaudio/jackaudio.github.com/wiki/WalkThrough_User_Net…
Definitely check the output of jackd when using jack_load.
Section 6. has this note:
By default this client will open the same number of input/output ports the
net driver has opened and will use the sampling rate the net backend is
currently using.
Perhaps the netbackend is using a sampling rate not compatible with the Pi
audio hardware. Perhaps there is a mismatch with the number of ports, I
do not know from that description if the number of ports on the netjack
slave must match the number of physical audio channels available or not.
Did you try the suggested:
jack_load audioadapter -i "-h"
That may give information on the correct number of ports to use.
If you really do want to use the audio adapters of both devices (Ubuntu
computer and Pi) perhaps zita-net2jack (zita-n2j) will work better for
you:
http://manpages.ubuntu.com/manpages/xenial/man1/zita-njbridge.1.html
--
Chris Caudle
Hi
So I'm trying to set up a Raspberry pi as an output for jack. I've had
it working with pulseaudio, but have to much latency with pulse.
What I've done is to follow this guide:
https://github.com/jackaudio/jackaudio.github.com/wiki/WalkThrough_User_Net…
I can get the pi registered and connected and all, but when I try to
load the audioadapter I get:
$ jack_load audioadapter
could not load audioadapter, intclient = 0 status = 0x 1
I have no idea what to do from here or what my problem is. I tried
getting the audio connected with alsa_out, but never got any output.
Any ideas? :)
It should be noted that I am running the PIs headless, and without and
x-server (plain raspbian, and control over ssh), which I am now
wondering might be an issue?
--
Kind regards
Claus Lensbøl
Finally installed a new system, Linux Mint 18, based on Ubuntu. I am
not sure therefore I ask, it seems there are two parallel versions of
jack being developed or in the least,m there are two of them out there
which could, or could not be candidate for installation, possibly known
as jackd and jackd2. If there's only one, then all right. In any case,
which jackd should be installed on a 2017 brand new 64-bit system ?
Thanks.
Hi
A new release of GxPlugins.lv2 is out.
GxPlugins.lv2 is a set of mostly analogue guitar pedal simulations as
LV2 plugins, simulated with the guitarix ampsim toolkit.
They contain the following plugs:
GxBottleRocket.lv2 - -> tube based preamp pedal
GxHotBox.lv2 - -> tube based preamp pedal
GxVBassPreAmp.lv2 - -> transistor based Bass preamp
GxSuppaToneBender.lv2 - -> transistor based Fuzz pedal
GxHyperion.lv2 - -> transistor based Bass Fuzz pedal
GxVoodoFuzz.lv2 - -> transistor based Fuzz pedal
GxSaturator.lv2 - -> saturation plugin
GxVintageFuzzMaster.lv2 - -> transistor based Fuzz pedal
GxSuperFuzz.lv2 - -> transistor based Fuzz pedal
GxVmk2.lv2 - -> transistor based preamp
GxUVox720k.lv2 - -> transistor based solid stage preamp
GxSlowGear.lv2 - -> volume swell plugin
GxGuvnor.lv2 - -> transistor based overdrive pedal
GxToneMachine.lv2 - -> transistor based Fuzz pedal
GxSD1.lv2 - -> Op-amp based overdrive pedal
GxQuack.lv2 - -> envelope controlled wah pedal
I hope they may be useful for the one or the other.
Build instruction and screenshots may be found here:
https://github.com/brummer10/GxPlugins.lv2
the release zip file is located here:
https://github.com/brummer10/GxPlugins.lv2/releases
regards
hermann
On Fri, April 14, 2017 1:26 pm, Antony Gelberg wrote:
> I have noticed that the lockups seem to *start* when I do
> something that might cause a bit of processor / disk IO e.g.
Is it just underruns because the machine can't keep up? What number of
frames per period are you using, and how many periods per buffer?
Does ulimit -r show that you can set a high enough real time priority?
> only happens when jack(dbus) is also running
Did you ever try jackd only without the pulse-sink loaded?
--
Chris Caudle
Hi all, Ubuntu Xenial 16.04 LTS, kernel 4.4.0, kxstudio. I have a problem
with my Lexicon Lambda soundcard (new to me, purchased second-hand).
Every now and then, it seems to lock up when I have Jack and Ardour
running. syslog contains many lines like:
15 Apr 10 10:35:01 cubase kernel: [ 1072.193677] usb 3-3: 1:2: cannot get
freq at ep 0x1
16 Apr 10 10:35:01 cubase kernel: [ 1072.195991] usb 3-3: 2:2: cannot get
freq at ep 0x82
I found a post https://www.spinics.net/linux/fedora/alsa-user/msg01899.html
suggesting that this device flouts the USB spec, and sure enough:
antony@cubase:~$ lsusb -s3:8 -v |grep -E
"(bNumInterfaces|bInterfaceNumber)" |sort|uniq
Couldn't open device, some
information will be missing
bInterfaceNumber 0
bInterfaceNumber 1
bInterfaceNumber 2
bInterfaceNumber 4
bInterfaceNumber 6
bInterfaceNumber 7
bNumInterfaces 6
I seem to have to hard-reset the card, kill and restart pulseaudio (8.0)
and jackd (1.9.11). My concrete questions are:
Am I wasting my time with this card?
Are the errors purely cosmetic (and something in software is locking up?)
Antony
--
http://www.linkedin.com/in/antgelhttp://about.me/antonygelberg