This is the initial release of XPolyMonk.lv2, a polyphonic version of
Xmonk.lv2.
XPolyMonk comes with 12 voices, full midi support and a integrated
virtual keyboard.
It use libxputty to create the interface:
https://github.com/brummer10/libxputty
The dsp part is heavily based on the FAUST `SFFormantModelBP` from
physmodels.lib
XPolyMonk is licensed under the BSD Zero Clause License, so you could do
with it what ever you like.
You'll find it's development source code here:
https://github.com/brummer10/XPolyMonk.lv2
and the release here:
https://github.com/brummer10/XPolyMonk.lv2/releases
Happy Xmas to all
hermann
Greetings !
My audio device has been an M-Audio Delta 66 + Omni I/O breakout box
that has served me well for many years. Alas, something is now causing a
severe problem with it. When I turn the unit on in the morning the clip
and input lights are solid red and green and remain so for up to five or
more minutes before they go off. Adding to that, my portable room heater
is now causing a terrible hum through my speakers. I tried another
heater, got the same results.
So, is the problem likely the Delta card ? I have a replacement for it
that I could swap out, but I thought I'd check with the experts first.
Or should I get an electrician to check out the wiring in my room ?
I can have sound or heat in my studio but not both at the same time. Grrr...
Season's Greetings to all LAU/LAD members !
Best,
dp
Hi
I have a laptop running debian 10. Sometimes it gets confused with a mini-jack in headphones and mutes audio. It seems to be something automatic that goes wrong, since 1) pulling the mini-jack makes the sound come out of the speakers just fine (putting it back in mutes audio again etc)and 2) a reboot fixes it.
I tried writing a script that un-mutes everything I can see and turns it up, but to no avail:
amixer set 'Master' 100% unmute
amixer sset -c 0 'Master' 100% unmute
amixer sset -c 0 'Headphone' 100% unmute
amixer set -c 0 'Speaker' 100% unmute
amixer set -c 0 'PCM' 100%
I'd like to know what's causing this and most importantly: any solution or work-around would be great!
I know it's a long shot, but maybe someone can recognize this and point me in a more constructive direction?
Cheers
--
Atte
http://latestyoutube.a773.dk | http://a773.dk
On Mon, 9 Dec 2019 15:34:02 -1000
Joel Roth <joelz(a)pobox.com> wrote:
> Hi,
>
> Do you have pulseaudio installed? If so removing it might help.
Yeah, I have pulse audio installed, might simply remove it and see how that goes. Thanks!
Cheers
--
Atte
http://latestyoutube.a773.dk | http://a773.dk
Hi Christoph,:
> ... And I thought if I don’t run the rt-kernel,
> I have to uncheck the realtime-setting in qjackctl, which may
> be a misconception (?).
It is. The standard kernel runs RT threads quite well. I've been
using it on at least 20 Arch machines all doing audio work, and
some of them quite heavy stuff with dozens of Jack clients and
64 channels in and out. No problems at all.
Many of the original RT patches have been incorporated in the
standard kernel for years now.
You may need the RT kernel if you use very short audio periods,
some people go as low as 16 frames.
Ciao,
--
FA
Hi Christoph,
Some extra info:
In case your system does allow real-time, it could be
that the maximum priority is set too low.
Zita-ajbridge will run the thread talking to the ALSA
device with a priority that is 10 higher than Jack's
callback threads. So if your jack is configured for
e.g. 80, and the system limit is 85, zita-ajbridge
will fail.
Ciao,
--
FA