I'm pleased to announce the release of guitarix2-0.41.0
A virtual guitar amplifier for Linux running with jack (Jack Audio
Connection Kit)
released under the GNU General Public License as published by the Free
Software Foundation;
either version 2 of the License, or (at your option) any later version.
This is a major release.
It introduce some new features and fix several bugs
Changelog:
* Add Slovak translation by Jozef Riha
* Fix issue #104 lv2 plugins contains executable stack, patch by
Alexander Tsoy
* Fix issue #105 Compile error on 0.40.0
* Fix issue #109 cannot initialize a variable of type 'char ' with an
rvalue of type 'void '
* Fix issue #110 error: unknown type name 'va_list'
* Add NSM support
* Add midi out for tuner
* Add low/high cut filter before tuner
* GxTuner set to use same precision then the tuner in guitarix
* Use tab-box for LV2 plugs with to much controls
* Disable GxVibe, because it is broken
* Fix several Bug's and hopefully don't introduce to much new one's
You could get it here:
https://sourceforge.net/projects/guitarix/
or here:
https://github.com/brummer10/guitarix
regards
hermann
Linuxaudio.org presents: New Session Manager Version 1.4.0
## Summary
The theme for this release is to fix known bugs and issues with both the
original Non-Session-Manager ("nsmd") server as well as its GUI (our
"nsm-legacy-gui"). Problems and inconsistencies that have piled up for
years were finally cleaned up (full changelog below).
Users do not need to take any action (besides updating), the session
save-format remains unchanged. Client programs, or rather their
developers, do not need to change or adjust anything; all changes are
"under the hood".
We have no self-hosted website yet, but plan to establish one in the
future. Until then the project can be found on Github:
https://github.com/linuxaudio/new-session-manager/https://github.com/linuxaudio/new-session-manager/releases/tag/v1.4.0
## Full Release Announcement:
New Session Manager (NSM) is a tool to assist music production by
grouping standalone programs into sessions. Your workflow becomes easy
to manage, robust and fast by leveraging the full potential of
cooperative applications.
It is a community version of the "NON Session Manager" and free in every
sense of the word: free of cost, free to share and use, free of spyware
or ads, free-and-open-source.
You can create a session, or project, add programs to it and then use
commands to save, start/stop, hide/show all programs at once, or
individually. At a later date you can then re-open the session and
continue where you left off.
All files belonging to the session will be saved in the same directory.
Check your distributions in a few days for New-Session-Manager 1.4.0
You can find the source release on Github:
https://github.com/linuxaudio/new-session-manager/releases/tag/v1.4.0
Bullet Points
* Drop-In replacement for the non-session-manager daemon nsmd and tools
(e.g. jackpatch)
* Simple and hassle-free build system to make packaging easy
* Possibility to react to sensible bug fixes that would not have been
integrated into original nsmd
* Stay upwards and downwards compatible with original nsmd
* Conservative and hesitant in regards to new features and
behaviour-changes, but possible in principle
* Keep the session-manager separate from the other NON* tools Mixer,
Sequencer and Timeline.
* Protect nsmd from vanishing from the internet one day.
* The goal is to become the de-facto standard music session manager for
Linux distributions
Changes since new-session-manager v1.3.2 (2020-06-20)
Add documentation and manpages.
Highlight: Provide updated API-Document (core documentation) on
https://linuxaudio.github.io/new-session-manager/api/index.html
Legacy-GUI:
Overhaul look and feel.
Rewrite labels and buttons with unambiguous descriptions.
Protect text-input dialog windows from empty strings, like "Add New
Client" or "New Session"
Scale icons, support more icon formats.
Show all icons and buttons when attaching to a running nsmd session
Various small fixes.
Always show correct session name, no matter how the session was loaded
or how the GUI was started
nsmd:
NSM_API_VERSION_MINOR from 0 to 1 (1.0 -> 1.1)
Repair nsmd to correctly send client data when running headless and a
GUI announces later.
ClientId generation now prevent collision with existing IDs.
nsmd command line option --load-session to directly load one
(Berkelder, Rik)
Better detection of clients that failed to launch leads to faster
session startup (by 5 seconds)
Users get informed by client-label if an executable is not present on
the system or permission denied
Fixed reply for listing sessions from a plain "Done." to proper reply
path with empty string as terminal symbol "/reply", "/nsm/server/list",
""
Fix operation reply to last treated client instead to reply to sender
(Picot, Mathieu / houston)
/nsm/gui/session/name send consistent session name/relative-path pair
to the annouced GUI, no matter how the session was loaded.
nsm.h
:optional-gui: support to nsm.h, for other applications to include and
use. (Meyer, Hermann / brummer )
This is a joint release from multiple people under the linuxaudio.org
"brand".
https://github.com/linuxaudio/new-session-manager
Greetings,
dvzrv, falktx and nils
Anyone got any idea what extra arrangements/controls will be in place for this
in November.
What's the accommodation situation most likely to be?
--
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.
Can anyone recommend a distro that still supports these well.
I had to d a reinstall a couple of years ago (debian) and although it was
never exactly quick before, it's been dog slow ever since :(
--
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!
Speaking about Ambisonics, I have one question regarding the different
orders you might want to use, which I couldn't found to be answered in
the (not too much) media I read and watched about this topic:
Which border do I have to reach in my project that I should consider
switching to higher (second, third or more) order ambisonics? Is it the
number of output channels? Or is it: Always use the highest order you
can afford?
According to this video <https://www.youtube.com/watch?v=f4oE3i2tjyA>(,
which I haven't watched the whole length,) at 23:14 ff it's about
frequency response and compensation - and there it seems to be better
using lower order.
It would be interesting making a direct comparison between first and
third order to hear if it's worthwhile. But without the equipment… So,
this question goes to the pros (hoping not to start a flamewar…)
There is another video <https://www.youtube.com/watch?v=kFuKaKbfxls> I
found. Without ever being able to hear higher order ambisonics I wonder
if such things as fifth order is more or less something like "look, what
I can do" comparing the time and effort with the actual improvement in
audio quality… Sorry, if I step on someone's feet…
Greets!
Mitsch
Hi there,
I'm new to the list. Composer/musician using Supercollider, I just moved from MacOS to Ubuntu 18.04. I was under the impression that the Edirol FA101 firewire audio interface should be working on Ubuntu, but I find it hard to figure out where to begin. The device is connected with an adapter to a Thunderbolt port on my Dell laptop. cat /proc/asound/cards does not show the device unfortunately.
When I do lspci -tv in terminal, the Thunderbolt port seems to be recognized:
+-1b.0-[02-3a]----00.0-[03-3a]--+-00.0-[04]----00.0 Intel Corporation JHL6340 Thunderbolt 3 NHI (C step) [Alpine Ridge 2C 2016]
| +-01.0-[05-39]--
| \-02.0-[3a]----00.0 Intel Corporation Device 15db
Can anyone point me in some direction for a solution to this?
Thanks!
Robert
★
Robert van Heumen
software developer, composer, sound designer, improvisor
west28.nl[1]
--------
[1] west28.nl
Hi all
I am looking for some info on which client should one use in order to
enable a 2nd sound card on the jack server or any of the jack client
computers.
I can see in zita's website that zita clients seems to be an improved
versionnnnnn of alsa_in & _out clients, but I would like for other people
to comment on that as well.
Where I am completely in the dark is where audioadapter stands in all this
...
Best regards,
Athanasios