Yoshimi continues to grow, and today we have V 1.3.4 out there.
There are times for big things, and times for great things, but today was the
time for (lots of) small things :)
Less about features, more about user 'comfort'.
Enjoy.
--
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.
Hi Len,
I didn't keep the Message-ID of the original thread.
On Sun, 29 Mar 2015 23:01:19 -0700 (PDT), Len Ovens wrote:
>Tracktion is not good enough to switch for me. The jack
>implementation is a bit odd. The one interesting thing it did do was
>to recognise my Yamaha DD11 channel 16 is really drums and map them to
>channel 10 when I recorded them.
Sequencers should provide a matrix to assign each drum voice to an
individual different note on any wanted MIDI channel. Some sequencers
do provide such a matrix.
I own a DD-11 too and it's owner's guide mentions that it provides 3
kicks, they are assigned to C1 (36), G#1 (44) and A1 (45). IOW 2 of the
3 bass drums are assigned to note numbers, that don't match with GM, so
just mapping to MIDI channel 10 not always does the trick. My RX21
provides a kick on A1 (45) only and my TG33 provides the bass drum on
C1 (36), G#1 (44) and A1 (45). G#1 (44) and A1 (45) on GM devices are
for Hi Hat and Tom, that is the way as my Roland MT-32 and my Alesis D4
factory drum kits provide it.
GM might be useful for some needs but for studio work a matrix is
needed.
IMO a drum kit by default should match as close as possible to GM, but
it's common practise to use drum samples from different devices, so a
matrix is needed anyway.
Regards,
Ralf
And finally, for the wrap of the pre-LAC2015@JGU-Mainz [1] release
party, no other than the 'crown jewel' of the whole Qstuff* bunch ;)
Qtractor 0.6.6 (lazy tachyon beta) is out!
Release highlights:
* LV2 and VST plugins GUI position persistence (NEW)
* MIDI clip editor record/overdub note rendering (FIX)
* VST plugin recursive discovery/search path (NEW)
* VST-shell sub-plugins support (FIX)
* also some old and new lurking bugs squashed.
Qtractor [2] is an audio/MIDI multi-track sequencer application written
in C++ with the Qt4 framework. 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.
Website:
http://qtractor.sourceforge.net
Project page:
http://sourceforge.net/projects/qtractor
Downloads:
http://sourceforge.net/projects/qtractor/files
- source tarball:
http://download.sourceforge.net/qtractor/qtractor-0.6.6.tar.gz
- source package (openSUSE 13.2):
http://download.sourceforge.net/qtractor/qtractor-0.6.6-16.rncbc.suse132.sr…
- binary packages (openSUSE 13.2):
http://download.sourceforge.net/qtractor/qtractor-0.6.6-16.rncbc.suse132.i5…http://download.sourceforge.net/qtractor/qtractor-0.6.6-16.rncbc.suse132.x8…
- quick start guide & user manual (see also: the wiki):
http://download.sourceforge.net/qtractor/qtractor-0.5.x-user-manual.pdf
- wiki (help really wanted!):
http://sourceforge.net/p/qtractor/wiki/
Weblog (upstream support):
http://www.rncbc.org
License:
Qtractor is free, open-source software, distributed under the terms
of the GNU General Public License (GPL [5]) version 2 or later.
Change-log:
- MIDI clip record/reopen to/from SMF format 0 has been fixed.
- LV2 and VST plugins GUI editor widget position is preserved across
hide/show cycles.
- Added application description as freedesktop.org's AppData [6].
- Added a "Don't ask this again" prompt option to zip/archive extrated
directory removal/replace warning messages.
- MIDI clip editor (aka. piano-roll) gets lingering notes properly shown
while on record/overdubbing.
- Current highlighted client/port connections are now drawn with thicker
connector lines.
- Fixing segfaults due to QClipboard::mimeData() returning an invalid
null pointer while on Qt5 and Weston.
- Return of an old hack/fix for some native VST plugins with GUI editor,
on whether to skip the explicit shared library unloading on close and
thus avoid some mysterious crashes on session and/or application exit.
- Force reset of plugin selection list when any of the plugin search
paths change (in View/Options.../Plugins/Paths).
- Recursive VST plugin search is now in effect for inventory and
discovery on path sub-directories (VST only).
- Non-dummy scannig for regular VST, non-shell plugins, were doomed to
infinite-loop freezes on discovery, now fixed.
References:
[1] LAC2015@JGU-Mainz - Linux Audio Conference 2015
The Open Source Music and Sound Conference
April 9-12 @ Johannes Gutenberg University (JGU) Mainz, Germany
http://lac.linuxaudio.org/2015/
[2] Qtractor - An audio/MIDI multi-track sequencer
http://qtractor.sourceforge.net
[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] AppData Specification
http://people.freedesktop.org/~hughsient/appdata/
See also:
http://www.rncbc.org/drupal/node/879
Enjoy && keep the fun.
--
rncbc aka. Rui Nuno Capela
On Sun, 29 Mar 2015, Ben Bell wrote:
>> starts at boot and stop at shutdown) Are you using jackd or
>> jackdbus? If you are using jackdbus, you may wish to try chmod -x
> Actually I just did the opposite and disabled jackdbus, because jackd I
> understand (I think ;).
There is no documentation for jack_control and if I recall jack_control -h
or --help do not work either but jack_control on it's own does. I think it
is just a python script so looking through the file with an editor or
pager would work too. I like jackdbus because the application that starts
it is not the only one that can manipulate things in it. I find it very
flexable. However using what you are used to is a great idea. You don't
need to learn two new things at the same time.
>> I am sure if you powered the d1010 down while the system was running
>> you would have similar problems or worse. Don't do that. I think if
> Again, that's a fair point and it's partly only because of the problems
> I'm having that I find myself doing it. With the Delta 1010 the external
> rack boxes could be powered down but of course the cards stayed powered.
I was not aware of that as the delta 66 box does not have a power switch
on the breakout box.
> I do still think that it ought to be possible to power the Focusrite down
> and get an error and a jack shutdown rather than hanging, but if not I'll
Actually, it is quite reasonable to expect an external audio IF should be
able to be connected or disconnected on the fly... but I think last time I
tried that with a USB interface (ALSA driver) things were difficult as
well. I was going to ask if you had tried the ALSA FW stack.
> On the click side of things, I've found a firewire debug setting and turned
> it up and can now see that the clicks correspond perfectly to kernel
> messages like this:
I do not know enough about fw to say. I don't recall now if you are still
using a desktop (as with the d1010s). If so I would try moving the FW
interface to different slots to see if this helps. Prioritizing the irq of
course helps too, but I am assuming you have already done so.
trying 32/3 instead 64/2 or any */3. This is just generally a good idea
with any "networked" audio IF such as FW, USB or AoIP.
--
Len Ovens
www.ovenwerks.net
Just noticed what appears to be a difference between Yoshi and Zyn when
using otherwise identical settings. I have an improv thing I do that
involves holding a low D (as a drone), sustain pedal down, the stock
Cathedral 1 reverb, using the Flanged Pad 1 instrument. Then I play a
bunch of descending scales, just letting the notes accumulate.
On Zyn, no matter how many notes I play, the low drone remains; if I
lift the sustain, the lower note is still playing.
On Yoshi, after a certain number of notes, the low drone stops; if I
lift the sustain, the lower not is NOT playing.
I put the Yoshi and Zyn screens side-by-side and it looks like the
settings are the same in each.
What's up with that?
--
David W. Jones
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://dancingtreefrog.com
it shows only one bank?
I go Instrument > Show banks, it shows me only a bank named "#42. yoshimi"
I go Instrument > Show instruments, it shows me a bank named "42.
yoshimi" - and that's it. Clicking arrow beside bank name does nothing.
Clicking Refresh banks changes nothing.
Oh, so now I have to select a bank, click Make Current, and then I can
see the banks?
Hmm, seems to me that it would be nice if there was a single "bank" that
listed everything. Finding an instrument now means first figuring out
which bank it might be in, making that bank the current one, then
looking through that bank hoping it contains the instrument I'm looking
for ...
I think the other way was less cumbersome.
Haven't time now to see what impact this might have one instruments in
my Rosegarden studio setup, will have to see how that works out.
Thanks for the update, still the neatest sound maker in the collection!
--
David W. Jones
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://dancingtreefrog.com
Maybe we could add a Search function - type in "Violin", hit Search, get list of all instrument names containing search phrase, regardless of "bank" number?
David W. Jones
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://dancingtreefrog.com
On Mar 24, 2015 10:35 PM, david <gnome(a)hawaii.rr.com> wrote:
>
> it shows only one bank?
>
> I go Instrument > Show banks, it shows me only a bank named "#42. yoshimi"
>
> I go Instrument > Show instruments, it shows me a bank named "42.
> yoshimi" - and that's it. Clicking arrow beside bank name does nothing.
> Clicking Refresh banks changes nothing.
>
> Oh, so now I have to select a bank, click Make Current, and then I can
> see the banks?
>
> Hmm, seems to me that it would be nice if there was a single "bank" that
> listed everything. Finding an instrument now means first figuring out
> which bank it might be in, making that bank the current one, then
> looking through that bank hoping it contains the instrument I'm looking
> for ...
>
> I think the other way was less cumbersome.
>
> Haven't time now to see what impact this might have one instruments in
> my Rosegarden studio setup, will have to see how that works out.
>
> Thanks for the update, still the neatest sound maker in the collection!
>
> --
> David W. Jones
> gnome(a)hawaii.rr.com
> authenticity, honesty, community
> http://dancingtreefrog.com
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user(a)lists.linuxaudio.org
> http://lists.linuxaudio.org/listinfo/linux-audio-user
