It is with great joy we present to you the final release of MusE 4.0.
A great many things have been added and improved since the last stable
release, nine months ago. To give a rather useless metric about the
amount of work that has gone into MusE 4.0, our code repository has
had more than 700 commits since the release of MusE 3.1.1!
Here is an extremely condensed list of the most important changes since 3.1.1:
* The core feature of 4.0 is the redesigned user interface with a huge
amount of quality of life improvements.
- Tabbed UI with Docks for common utility editors like Marker List,
Mastertrack List and Event List.
- All new dark theme with a lot of graphical improvements including lots
of icons reworked in vector format.
- Many new toolbars for quick access to common operations.
- A lot of menu operations now list their related keyboard shortcut.
- Many new keyboard shortcuts.
* We now have an AppImage for easy installation on all distributions, both
for releases and the bleeding edge development version.
* Many many other fixes and improvements.
For the complete list of changes see:
https://github.com/muse-sequencer/muse/blob/4.0.0/src/ChangeLog
The homepage:
https://muse-sequencer.github.io/
Download:
https://github.com/muse-sequencer/muse/releases/download/4.0.0/muse-4.0.tar…https://github.com/muse-sequencer/muse/releases/download/4.0.0/MusE-4.0.0-x…
Demos page:
https://github.com/muse-sequencer/muse/wiki/Demos
Forum:
https://linuxmusicians.com/viewforum.php?f=61
On 4/24/21 4:36 AM, Will Godfrey wrote:
> On Tue, 20 Apr 2021 08:11:18 -1000
> "David W. Jones" <gnome(a)hawaii.rr.com> wrote:
>
>> On April 20, 2021 5:46:46 AM HST, Will Godfrey wrote:
>>> Has anyone tried compiling Rosegarden for the Raspberry Pi4?
>>> If so, what is the absolute minimum required to get it up and running?
>>> I would expect it to be extremely slow to compile :(
>> Hmm. Couldn't you cross-compile - compile for ARM/PI 4 on your Intel?
> I looked at that. It's a hell of a lot of work, just to compile one application
> - I really don't have time for that :(
>
Seems to me like that sort of thing (setting it up) would be a one-time
hell of a lot of work, but if you're going to be compiling Rosegarden
for ARM/PI to keep your RG PI version current... Maybe the RG devs have
clues on doing that?
--
David W. Jones
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://dancingtreefrog.com
"My password is the last 8 digits of π."
On 2021-04-23 14:57, robertlazarski wrote:
Better to keep replies on list, to help others with a similar problem
and to get insight from other people.
> I finally found my interface in qjackctl -- setup. I restarted it and
> instead of a separate shell for jack, I used qjackctl to start jack. I
> see these two processes:
>
> robert 7019 7014 0 09:33 ? 00:00:00 /usr/bin/jackd -dalsa
> -dhw:USBPre2 -r48000 -p1024 -n2
> root 7174 1 0 09:36 ? 00:00:00 /usr/bin/jackd -T
> -ndefault -T -d alsa
That looks like you had another instance of jackd running already as
root that you did not stop. You generally do not ever want to run jackd
as root, so kill that 7174 process.
And still did not really answer the original question. If you start
jackd manually from a terminal as you did, qjackctl will detect the
running instance and connect to the already running jackd. Did you
start qjackctl before or after you started jackd from the terminal?
> However, now jltcdump somehow is on hw:0
I think there is a vocabulary problem. What do you mean that ltcdump is
"on" hw:0?
Jack applications have ports
Jackd will also assign ports to hardware interfaces.
You use a jack control application (such as qjackctl for GUI, or
jack_connect for CLI) to connect ports together to transfer audio data
between hardware interfaces and applications, and between applications.
You need to start jackd before starting any jack aware applications
(other than control applications like qjackctl or catia) or you may end
up with jackd starting up with the last used configuration as default.
> From jltcdump.
>
> Acquire audio card Audio0
> creating alsa driver ...
> hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
> configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2
> periods
> ALSA: final selected sample format for capture: 32bit integer
> little-endian
> ALSA: use 2 periods for capture
> ALSA: final selected sample format for playback: 32bit integer
> little-endian
> ALSA: use 2 periods for playback
> JACK server started
I'm confused, you write "from jltcdump" but that output is what jackd
displays when it starts up. Was that output really displayed on the
terminal after you started jltcdump?
I think you need to get back to a known beginning configuration first.
Kill jltcdump, stop jackd from qjackctl, quit qjackctl, and look for any
processes with "jack" in the name and kill those.
After you are sure that there are no more jackd processes running, start
qjackctl, click the "Setup" button, and check the interface, sample
rate, period size, etc. there.
If you need to make any changes then hit apply or OK or whatever accepts
the changes and goes back to the main window; if the settings are
already what you want you can click the cancel button to go back to the
main window, then click the "Start" button to start the jackd server.
Click the "Connect" button and the connections window should open, with
only "system" shown in both the Readable Clients/Output Ports and the
Writeable Clients/Input Ports windows.
Now run jltcdump from a terminal, and you should see a new entry for
jltcdump show up in the Writeable Clients window. Click the arrow to
expand the entry and you should see input1 as an available port for
jltcdump.
Click the arrow to expand system in the Readable Clients window and you
should see capture_1 and capture_2 ports available (assuming you have a
typical two channel audio interface; if you have more input channels on
your audio interface you should see a number of capture ports
representing the available inputs assuming you did not restrict the
number of ports when starting jackd).
Now you can connect the appropriate output port from the hardware driver
(capture_1 is usually the left channel on a two channel interface) to
the input port on jltcdump. Click the appropriate capture port, then
click the input1 port on jltcdump, then click the Connect button in the
bottom left corner of the window. The audio data from that input port
of your interface should now be sent to jltcdump (indicated by qjackctl
drawing a line between the two ports).
--
Chris Caudle
This is a public service announcement, since I suspect that many here will
not be aware of this development.
David Hilowitz (0) recently "ported" (1) his new sample library playback
engine Decent Sampler to Linux. It is available as a Linux VST3 plugin and
as a standalone application (2) David's work was substantially inspired by
the work in the Pianobook community (3), where people build often-complex
sample libraries originally to "save" real pianos but increasingly covering
new territory (such as the Winter Voices project (4)).
I am a little disappointed that David chose to define a new sampler library
format rather than use SFZ, given the developments with sfizz over the last
several months. However, both DecentSampler and SFZ are text formats, and
there are gratis implementations for them both. In theory, DS -> SFZ
conversion could be automated, though the other way around may be more
problematic.
Yesterday I downloaded 36 Decent Sampler libraries from the Pianobook
website, and although they are not all quite as awesome as I had hoped for,
some of them are amazing and all of them make a valuable addition to the
sample library situation for Linux audio/music workflows. There are also
some gratis and some non-gratis libraries for Decent Sampler on the Decent
Sampler website.
It would be lovely if Decent Sampler was libre as well as gratis, and I
hope we see quality SFZ libraries either gratis or reasonably priced,
because that format offers some features missing from Decent Sampler. But
for now, I personally consider this a wonderful step forward for
Linux-based musicians.
(0) https://www.youtube.com/channel/UCCoAJ5JYKYTMubpTIsWi70w
(1) I put ported in quotes because I believe that DS is implemented using
JUCE, and so this mostly just involved changing the build flags :)
(2) https://www.decentsamples.com/product/decent-sampler-plugin/
(3) https://www.pianobook.co.uk/
(4) https://www.pianobook.co.uk/library/winter-voices/
I have a lot of hardware, including several Tentacle Sync units that send
LTC audio to cameras. I need to connect this audio to Linux for some MTC
coding in C/C++ of midi events for "live in the studio" performances.
I am a little rusty in my Linux Audio skills. I seem to have this interface
ready to go with Jack but I get no sound of the LTC from my internal
speakers with or without Jack. I am running OpenSuse leap 15.
I have two shells open, one with a Jack Session and one with jltcdump. The
jack command does change the display on the interface. I couldn't get
qjackctl to recognize the usb interface, only the default intel sound
devices. Audacity doesn't see the device. Any ideas?
Shell 1:
[linux-fesf(root)]
/root> cat /proc/asound/cards
0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xed128000 irq 141
1 [USBPre2 ]: USB-Audio - USBPre2
Sound Devices USBPre2 at usb-0000:00:14.0-1, high
speed
[linux-fesf(root)]
/root> jackd -d alsa -d hw:USBPre2
jackdmp 1.9.12
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2017 Filipe Coelho.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
no message buffer overruns
no message buffer overruns
no message buffer overruns
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
audio_reservation_init
Acquire audio card Audio1
creating alsa driver ...
hw:USBPre2|hw:USBPre2|1024|2|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 24bit little-endian in
3bytes format
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 24bit little-endian in
3bytes format
ALSA: use 2 periods for playback
Shell #2, does nothing.
[linux-fesf(robert)]
/home/robert> sudo /usr/local/bin/jltcdump
## SMPTE | audio-sample-num REV| unix-system-time
##u-bits time-code | start end ERS| start
end
#Start: sample: 0 tme: 0.000000000
A couple of weeks ago, getting progressively more annoyed with soundcoud, I
opened a Bandcamp account. I like the idea of free streaming but accepting
contributions for downloads, and Bandcamp's cut doesn't seem excessive.
My first posting there is a themed album with a mixture of revised compositions
and completely new ones. It is also 100% Yoshimi & Rosegarden.
You can find it here:
https://willgodfrey.bandcamp.com/album/misty
Enjoy :)
--
Will J Godfrey
https://willgodfrey.bandcamp.com/http://yoshimi.github.io
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
