LinuxMusicians

Tim E. Real

Further fixes pushed to github master now. The behaviour is as follows: In the spirit of the original developer's wish to re-use Event List windows, if we find an existing Event List window which contains all of your selected parts, then we re-use it and simply raise it since it already contains you...

Tim E. Real

Hm, it needs more work. It works OK but the logic is still flawed. For example if you select 5 parts but an existing Event List Editor already contains just one of those parts, it will raise that window but you won't see all five parts, only the one part. So I need to find a way to have the Event Li...

Tim E. Real

Congratulations, you found a bug :) Fixed in github master now. Your name now thanked and immortalized in the ChangeLog. It wasn't me! (TM) The developer wanted to ensure that existing EventList Editor windows were re-used if they already contained the selected part(s), simply doing nothing more tha...

Tim E. Real

how do I view all the events in the entire song in the Event List view? Selecting all doesn't seem to work here, as it did with the Piano Roll and Score views. Hm. That's odd. If I recall, it's supposed to allow you to select multiple parts and then open the Event List and it should show all of the...

Tim E. Real

OK I dig what you're saying now. The Event List should be built-in to each editor window - no questions asked. Yeah, that's cool and makes sense. Wow, I bet if developers spamatica or even kybos (who added the tabbed feature) are viewing that picture they would be quietly chuckling along with me. Be...

Tim E. Real

Each of the editors can be opened in a completely new and separate window. See Edit > Open Editor in new window. The Event List can be detached as a separate floating window by clicking the small icon in the upper right of the Event List. The Global Setting > Editors tab lets you tell MusE to always...

Tim E. Real

Glad it worked. Actually, our built-in MESS Fluidsynth plugin allows us to tightly couple the fluidsynth API with MusE's needs, and do things that other plugin architectures might not be able to easily do. For example, soundfonts which have percussion sounds. MusE shows the names of the individual d...

Tim E. Real

I confirm that focus does not return to the arranger canvas. That, despite my cleverly named 'smart focus' feature (in Settings) which does return focus to a canvas after editing a box or control on its window's toolbar. (Without that, the focus remains in the boxes, controls, or in the great void.)...

Tim E. Real

Found the problem:
Your song's key signature is 4/1.
Is that desired? Four whole notes to a bar?
I changed it to 4/4 and the song plays.

MusE is failing with that '1' denominator.
Still, it shouldn't, and it probably should be fixed.

: Screenshot_20241001_132444.png (18.31 KiB) Viewed 773 times

Tim E. Real

Thanks very much for the test file! Congratulations, your file causes MusE's transport to freeze here, after a few seconds of play. And it may indeed cause a crash later, although that has not happened yet. In file midi.cpp, we are stuck in a loop: Audio::processAudioMetronome() { ... // STUCK IN TH...

Tim E. Real

[grayson.peddie.mm@epcotcenter ~]$ muse4 -f -style=Windows I noticed the -f. That's not a valid option and MusE should have simply printed out the available options in the terminal, and then quit without even attempting to start the main window. But it didn't even get that far. So the error seems t...

Tim E. Real

QTractor is probably the closest thing to our 'cousin', being probably the only other Qt DAW app.

My sincere apologies for forgetting Rosegarden

Tim E. Real

OK thanks for the reports and the Fedora 40 report as well.
Do this mean MusE works OK on Nobara/Fedora versions below 40? Has anyone tested?

Tim E. Real

Ouch. I feel your pain. Well, at least it can run.

What happens if you launch QTractor?
QTractor is probably the closest thing to our 'cousin', being probably the only other Qt DAW app.

Tim E. Real

Hm. Thanks for the tests. So it actually compiles OK but refuses to run OK, even without the LV2 GTK stuff compiled in. Hm. I am seeing a few posts about possibly on a Gnome3 distro, MusE wants to start with a GTK2 Qt style, but the distro is using GTK3, so it fails. The posts mention how to fix it ...

LinuxMusicians

Search found 694 matches

Re: Help getting audio out of built-in MESS FluidSynth plugin

Re: Help getting audio out of built-in MESS FluidSynth plugin

Re: Help getting audio out of built-in MESS FluidSynth plugin

Re: Help getting audio out of built-in MESS FluidSynth plugin

Re: Help getting audio out of built-in MESS FluidSynth plugin

Re: Help getting audio out of built-in MESS FluidSynth plugin

Re: Help getting audio out of built-in MESS FluidSynth plugin

Re: Return automatic focus to the arranger when the pianoroll is closed

Re: Import of "erratic Midi-Files"

Re: Import of "erratic Midi-Files"

Re: Nobara 40 and MuSE 4.2.1: Cannot Register Existing Type 'GtkWidget'

Re: Nobara 40 and MuSE 4.2.1: Cannot Register Existing Type 'GtkWidget'

Re: Nobara 40 and MuSE 4.2.1: Cannot Register Existing Type 'GtkWidget'

Re: Nobara 40 and MuSE 4.2.1: Cannot Register Existing Type 'GtkWidget'

Re: Nobara 40 and MuSE 4.2.1: Cannot Register Existing Type 'GtkWidget'