Release 0.32.3 is out,
Guitarix is a tube amplifier simulation for
jack (Linux), with an additional mono and a stereo effect rack.
Guitarix includes a large list of plugins[*] and support LADSPA / LV2
plugs as well.
The guitarix engine is designed for LIVE usage, and feature ultra fast,
glitch and click free, preset switching and is full Midi (learn)
and remote (Web-interface/ GUI) controllable (bluez / avahi)
Changelog:
* fix some rc-style bugs for KDE Qtcurve engine
* add 2 new rc-styles (flat and green)
* replace old outdated factory presets
* add some new plugin presets
* add jack midi out port to report state (CC messages) and control
multiple instances with one interface
* set engine.mute to default midi controller 120 (All Sounds Off)
* add new command-line options -L start with Live Play GUI
and -M start with engine muted
* fix some issues with remote control GUI and external plugs
Guitarix is free, open-source software, distributed under the terms of
the GNU General Public License (GPL) version 2 or later.
Please refer to our project page for more information:
http://guitarix.sourceforge.net/
Download Site:
http://sourceforge.net/projects/guitarix/
regards
hermann
_______________________________________________
On 01.02.2015 6:10, Brent Busby wrote:
> Artem Vakhitov <temcat(a)mail.ru> writes:
>
>> is it currently possible to convert Hydrogen drumkits to sf2? It
>> doesn't work for me on Mint MATE 17.1. I downloaded the script and its
>> associated .py files, checked for flac and sox being installed, and
>> tried to use the script on a drumkit. It created an output file but it
>> doesn't see to contain sounds. I received the following error in the
>> console:
>
> [...]
>
> I contacted the author a few months ago, and he said he'd restart
> development, but for now, I think it's been struck down with code rot.
Thanks Brett,
So I guess it's not possible (at least easily) for now.
Artem
When creating a track with name 'elephant' and then recording onto it,
regions are created with variations of the name 'elephant' (1.1, 2.1, etc).
If there are several takes until I'm satisfied, several regions are
created, and easily accessible from the regions list (View -> show
editor list).
Then I discover that I actually recorded 'giraffe'. I change names of
tracks and regions to avoid confusion. Unfortunately the regions list
does not update names accordingly - there regions are still filed under
'elephant'.
Is there a way to update names in the region list?
When copying and moving regions around, multiple and more or less
identical regions appear in the regions list. Can identical regions
somehow be ignored?
Is it possible to use the regions list to navigate to that region in the
session?
And lastly, does anybody have tips for good workflows regarding regions
and the regions list?
Any and all input appreciated!
Alf
When exporting a session ardour (3.5) crashed and everything (Ubuntu
Studio 14.04) froze.
I had to open an "emergency terminal" (ctrl-alt-f#) to kill and reboot,
and didn't manage to copy the error message. Still I believe I can find
it in some logs, but where to find the log?
Oh, and when Ardour loaded the session after reboot it was with this
> [ERROR]: could not reconstitute MementoCommand from XMLNode. object
> type = ARDOUR::AutomationList id = 21170
I suspect the reason for the crash was that I tried to give the export
file a new name not already on disk.
This should probably be in the Ardour forums, I know. I intend to
register there at some later time...
Alf
> From: Brent Busby <brent(a)keycorner.org>
> Ardour is doing 32-bit FP math to handle samples internally.
> And yet, when I change the volume on the master fader, even if I
> compensate for the volume change on my RME Multiface's physical volume
> knob for the headphone monitor, I'd almost swear I can hear some sort of
> change in the audio.
To compare two versions of the same audio, the two versions must be level
matched to within 0.1dB. Differences of just a few tenths of a dB can
sometimes be heard as a slight timbre difference, usually the slightly
higher level version sounds just a tiny bit brighter. That requires
matching level to almost 1%, or if using consumer style levels of 2V RMS
max output, matching to within 20mV at max output.
It is difficult to verify at the analog outputs, but should be relatively
straightforward to compare separate files. Finding the right software to
display to that level of precision might be tricky, I'm not sure.
> I'm probably just fooling myself
That is a possibility, but it is a lot more likely that you are not
actually compensating exactly for the level change with your headphone
level control.
Even if you manage to adjust your headphone level control to within 0.1dB,
a lot of analog level controls can't necessarily hold to within 0.1dB over
time due to changes in the resistance with temperature, or mechanical
friction and spring effects that drag the contact back slightly after you
let go.
> In a related question (which was the real reason I wanted to know), what
> kind of levels should we be shooting for in the master output anyway?
Everyone should read Bob Katz's original two part article on level and
metering recommendations:
http://www.digido.com/articles-and-demos12/13-bob-katz/22-level-practices-p…http://www.digido.com/how-to-make-better-recordings-part-2.html
tl;dr version: Use calibrated monitor levels and set the levels to sound
appropriate for the style of music you are mixing, like used for mixing
films.
--
Chris Caudle
In a stereo track I added a mono region.
This is only audible in the left channel and I'm not able to find out
how to make it output to both channels?
Alf
The main feature of this release is the revision of root directories and banks.
http://sourceforge.net/projects/yoshimi/?source=directory
As well as new features, this consolidates work that was started with version
1.2.0. In view of the number and depth of changes I thought it worth detailing
the entire setup, so apologies for the length!
In the first place, you no longer have the concept of a default root directory,
but a current one. This can by changed at any time without requiring a
re-start, so there is now no longer a need to display the (confusing) contents
of all roots at once. Also, roots now have ID numbers associated with them, but
no changes have been made to the actual directories to achieve this. Instead the
IDs are stored in the config file. The same ID system is used for banks, again
without making any file system changes.
At first run (and whenever new root directories are set) unknown roots and
banks are given these IDs. Once set they will not change no matter how many
more roots and banks are later added. You can however, manually change root
directory IDs in 'settings'. Bank IDs can be changed via the config file, and
in the near future the GUI will also be updated to manage this. With these IDs,
roots and banks can be grouped/ordered by function instead of alphabetically.
When using the GUI you will always know exactly which root and bank you fetch
an instrument from.
The significance of all this is that your MIDI sequencer can now reliably use
these ID numbers to select roots, banks and (already available) instruments.
That Rosegarden or Muse file you save today will be just as valid in the
future, unless you make the deliberate choice to change some IDs. Indeed, you
can now start with an 'empty' Yoshimi, and via MIDI, set roots, banks and load
instruments into parts (enabling the parts as you do so) swapping banks and
roots as necessary. While the MIDI file runs it can silently pull instruments
from any root/bank into any non-sounding part without disturbing the playing
ones.
In Yoshimi->Settings->CC you can enable or disable all these MIDI features, and
can define which CCs you want to use. Bank can be either MSB or LSB (as
before). Root can be any non-reserved CC but including the one not currently in
use for Bank. Also, Extended Program Change now has the same restrictions as
Root, and these three are all cross-checked against each other. As an example
you might set Bank to LSB and Root to 0 (MSB), effectively giving you extended
bank control compatible with all sequencers.
Also, different instances have their own config files so that you can have
(say) the main instance with current root(9), bank(23) while instance 4 has
current root(2), bank(6). You can call up instances by number and thus access
saved settings for that instance. As each instance has its own MIDI and audio
ports, they can behave more-or-less independently.
In doing all of this we have completely changed the way we manage the structure
internally, resulting in much greater efficiency, at the cost of only a
slightly slower startup. Swapping roots performs *no* file operations. Swapping
banks only fetches the directory list of the newly selected bank. Changing an
instrument doesn't have to search for a file, only load from its already known
location.
Following on from that, we now have a startup splash image that appears
instantly so you always know Yoshimi has started even if some later error
causes it to abort. The actual image may change - we have requests out for
artwork (all ideas considered).
So much for the high visibility stuff!
More work has been done on LV2, including integrating the new root and bank
controls.
The main window and the mixer panel are now fully in sync.
Ambiguities in instrument names have been resolved and Yoshimi will no longer
save unnamed or default instruments. If you load a Zyn (or older Yoshimi) file
that has unnamed instruments they will be given the name 'No Title'.
You are now prevented (with an explanation) from attempting to change a bank
entry in a non-writeable area. Previously it would seem you had done so, but the
changes would not (of course) have been saved to file - this goes back very
many years!
And... a few bug fixes - where do they come from?
--
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.
Hello all,
I'm currently getting to know ardour (3.5 on Ubuntu Studio 14.04) and
wondered if there's anyone on the list interested in being a one-day
guru, answering smart and silly questions alike?
I do usually look up the online manual before asking, but sometimes
normal searching gets me nowhere...
For now, 3 questions that's been bugging me:
1. Is there a way to click and drag or similar to navigate back and
forth along tracks? There's a click and drag "navigator" at the bottom
of the screen, but with many tracks I find it hard to move only
sideways, and not also up or down.
2. How to undo region deleting? Must be something obvious that escapes
my eye...
3. How to access session undo history, and restore things done in
previous sessions?
All the best,
Alf
