Hey hey everyone,
I've got problems connecting Midish to Yoshimi. Keyboards with and without
active sensing from the mid 80s to the past year work fine. But when I try to
connect Yoshimi from within Midish, I get no sound. LinuxSampler works though.
The midish procedure
dnew 4 "yoshimi" wo # Add Yoshimi to Midish device list
onew "Yoshimi" {4 0} # name first channel Yoshimi
Create a filter to route all events from my keyboard to Yoshimi.
Typos aren't possible, since it's all done by Midish procedures and has been
tested about 10 times.
Does Yoshimi need any special MIDI input beyond noteon/noteoff perhaps?
Ta-ta
----
Ffanci
* Homepage: https://freeshell.de/~silvain
* Twitter: http://twitter.com/ffanci_silvain
* GitHub: https://github.com/fsilvain
Background.
I often use my 'office' machine (64 bit dial core Intel - debian 8) to do
experimental work on audio software as I don't want to take risks with my DAW.
Sometimes I use a KA6, other times the motherboard sound depending on what I
want to check. However, I've got into the habit of leaving the KA6 plugged in
anyway.
Recently I've noticed that if I have jack running through the motherboard
audio, I get exactly 1 Xrun approximately every 11 minutes. This doesn't
happen if the KA6 is not plugged in, nor does it happen if I route jack's audio
through it.
If this was some USB issue I would have expected it to be there when routing
through the KA6 as well.
Any ideas?
As an aside, I can run the KA6 at 1/2 the buffer size of the motherboard audio
and still get no Xruns, when the latter is getting quite croaky.
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
Saw something I didn't expect while debugging my production box; in
/proc/asound/cards, an entry named FCA202, which was my Behringer FCA202
firewire interface. Since when does ALSA do Firewire interfaces?
I'm tracking a very intermittent freezup bug of some sort, and thought
perhaps this ALSA driver was interfering with JACK and its Firewire side,
and have blacklisted the driver involved (snd_oxfw) just in case. It will
take a lot of testing to come to an opinion whether or not this eliminated
the problem.
But meanwhile, does this mean that I have the option of using
JACK-->ALSA-->FCA202 as well as JACK-->Firewire-->FCA202?
Anyone know which perhaps I should prefer for high performance at low
latency? I'm running 96KHz and liking it a lot...
In case it helps: kernel 4.1.3 Liquorix, Debian Testing, 64-bit, up to
date.
--
*Jonathan E. Brickman jeb(a)ponderworthy.com
<http://login.jsp/?at=02e47df3-a9af-4cd9-b951-1a06d255b48f&mailto=jeb@ponder…>
(785)233-9977
<%28785%29233-9977>Hear some of our music at http://ponderworthy.com
<http://ponderworthy.com/> !Music of compassion; fire, and life!!!*
Hi all,
The Center for Computer Research in Music and Acoustics (CCRMA) at
Stanford University is a multi-disciplinary facility where composers and
researchers work together using computer-based technology both as an
artistic medium and as a research tool
(https://ccrma.stanford.edu/about). We are (still) currently looking for
a great person to help lovingly take care of and feed our servers,
workstations, and multichannel audio setups.
The right person will be working with and helping a diverse community of
interdisciplinary students (ranging from undergrads to DMAs and PhDs,
studying Music, EE, CS, and many other fields), researchers, and faculty
from all over the world. Our computers mostly run GNU/Linux but there
are Macs in the studios and even a couple of Windows machines in the
NeuroMusic lab. We do complex multichannel audio setups in our studios
and for concert diffusion (3D sound in up to 25.8 channels), we maintain
all our own servers and backups, and we package our own software (and
other developers' open source free software) in repositories so that
anyone can install it easily. All this is quite a lot of work and we
need help!
Qualities sought: curious, tenacious, responsible, self-motivated,
tech-savvy, willing to learn, artist- and wizard-compatible, strong team
player who can work independently.
Full details about the job are here:
https://stanfordcareers.stanford.edu/job-search?jobId=66452
-- Fernando
Hi Guys, Galls. I've put some work on guitar synth on GuitarSynth
(https://github.com/geraldmwangi/guitarsynth-dpf). There is a new
parameter per synth called overlay input. What it does is it multiplies
the synth signal with a scaled version of the input audio. That way the
synth sound is attenuated by the guitar sound, making it more
'guitarish' sounding. I would like to hear your thoughts on it. Remember
when testing to turn up the gain of the synth in question, as well the
input gain on the soundcard/alsamixer.
Work on the polyphonic pitch detection is come to a halt, since I'm
wrapping up my PhD, but don't sigh: I'm still reading into the matter
and have some ideas..
Gerald /JimsonDrift
I thought I'd give Non-Sequencer a spin...
Am I missing something, or is there no quantize (before or after
recording) in this sequencer at all?
The UI is very good looking and a little different (different is good),
but if there's a quantize method in here, I'm missing it...
Hi
I'm trying to spy on the SYSEX being send between the proprietary
Arturia software (Midi Control Center) running inside virtualbox and my
beatstep pro.
When I enable the device in virtualbox, it seems to disappear from the
linux file system, /proc/asound/card2 ceases to exist and the beatstep
pro disappears from qjackctl's alsa tab.
Is there a way to monitor the trafic traveling to/from the beatstep pro
or to/from virtualbox?
Cheers
--
Atte
http://atte.dkhttp://a773.dk
Hi folks, hi Rui,
there is an issue with rtirq on Arch Linux and Ubuntu.
The order of sound devices not always is correct. It happens using
different kernels, for Ubuntu seemingly only when using systemd, with
the last version of rtirq. Arch does use systemd.
The issue is described here:
https://bugs.launchpad.net/ubuntu/+bug/1482347
Users should check the rtirq status after startup.
Regards,
Ralf
PS: I dropped a AUR4 note too:
https://aur4.archlinux.org/packages/rtirq/
