Hi all.
After previous discussions we decided to switch the meeting time to the second
Tuesday of the month. That is tomorrow on the 14th. If the weather is nice
(report said it might be rain) I suggest we'll stay outside, otherwise we'll
meet in the mainhall as usual. I'll be there from 20:30.
Location: c-base, Rungestraße 20
Cheers
/Daniel
DrumGizmo 0.9.16 Released!
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.
This is mainly a bugfix release. If you encountered timing issues when
using the humanizer features of 0.9.15, this is the release to get. It
also optimizes the resampling and a bunch of other stuff. For the full
list of changes, check the roadmap for 0.9.16 [1].
And now, without further ado, go grab 0.9.16 [2]!!!
[1]:
https://www.drumgizmo.org/wiki/doku.php?id=roadmap:features_roadmap#version…
[2]: http://www.drumgizmo.org/wiki/doku.php?id=getting_drumgizmo
i have no JACK_RC_FILE set nor is jack already running……...
> On Aug 2, 2018, at 17:28 , Paul Davis <paul(a)linuxaudiosystems.com> wrote:
>
>
>
> On Thu, Aug 2, 2018 at 11:25 AM, Fokke de Jong <fokkedejong(a)gmail.com <mailto:fokkedejong@gmail.com>> wrote:
> So, how can I make my client into a ‘normal’ client :-)
> What is mean is, i already have the .jackdrc file. I just don’t know how to make jackd use it.
>
> i don't see any way that it cannot be used ... if JACK is not running when you client starts (it is already a "normal" client) then jackd is started *using the contents of jackdrc* if it exists.
>
> so, either JACK is actually already running or you have JACK_RC_FILE set in your environment to point to some other location
>
Hi all,
After migrating to a freshly installed system, it seems jackd has decided not to honor my settings in $HOME/.jackdrc anymore.
I have a (minimal, no deskop) install of ubuntu 17.10 and jackd1
when I startt my jack client it prints:
creating alsa driver ... hw:MADIFXtest|hw:MADIFXtest|1024|2|48000|0|0|nomon|swmeter|-|32bit
but the contents of of ,jackdrc is:
/usr/bin/jackd -p512 -dalsa -r48000 -p64 -n2 -D -Chw:MADIFXtest -Phw:MADIFXtest
So I’m getting a period size of 1024 rather that 64.
copying .jackdrc to /etc/jackdrc also didn’t help.
Any idea why jack is refusing my settings?
This was working fine on my other system which should be more or less identical, but obviously i'm missing something rather crucial here…
thanks!
fokke