After importing mid file, no audio can be heard

[Joysn71]

Hello,
new to MusE. Imported a MIDI file and I can see the tracks.
I added a ACE FluidSynth plugin which I use in Ardour.
The ports of the MIDI tracks changed to 1:ACE FluidSynth LV2-0.

How:

• can I open the FluidSynth plugin to specify the soundfont to be used?
• can I make audio to go out to some Jack port so that I can route it to where I want, e.g. some speakers?

In qpwgraph, MusE does not show up, even though I configured MusE to use "JACK Audio" as audio backend.
I dont understand the "Advanced routing" dialog.
When I select 1:ACE FluidSynth LV2-0 as source, I can not connect it with some destination.

How is this supposed to work?

--
MusE 4.2.1
Debian Trixie, Pipewire 1.4.1

[Joysn71]

After playing around a little bit more, I noticed the following:

When I open MusE, qpwgraph shows MusEs MIDI connections to Ardour using jack midi ports, and MusE connects its out ports to the analog audio device. But when I import a MIDI file, all connections are gone.

I then added a synth track using FluidSynth, added a soundfont, and afterwards imported the MIDI file.
Then a output track was added as well, and finally I was able to hear the music.

So, I am using MusE in the wrong order... at least this is my conclusion now

[garvalf]

well I can't really say for sure, but you can also load ace fluidsynth right from MusE, instead of from Ardour, which will add some load on your system because you're using 2 DAW. It's also possible to run fluidsynth from Carla (see kx studio link below), a "VST" host (which can also load LV2 and CLAP plugins).

From within MusE, you can access to the fluidsynth plugin interface by right clicking on the "Synth" port, it will display "show generic synth Gui" / "show native synth GUI".

To route to and from DAW, vst hosts, midi instruments, I'm using Claudia, which is from the kx studio repository: https://kx.studio/Repositories

[Joysn71]

The issue with ACE FluidSynth plugin in MusE is that the generic GUI does not offer the SF2 file selection box, the native GUI entry is disabled due to lack of a native GUI in ACE FluidSynth. But I could use MusEs own FluidSynth plugin, which works fine.

[Impostor]

So, I am using MusE in the wrong order... at least this is my conclusion now :)

If you import a midi file, you get the choice of adding it to the current project, or opening a new project for it.
The latter choice will only contain midi channels, because it is a perfectly valid usecase to only work with midi inside MusE.
In the former case extra midi channels will be added to the current project.

It is up to you to link those midi channels to synth tracks if you so desire. In the latter case you'll need to create them (and an audio output track).

I dont understand the "Advanced routing" dialog.

I never use that. All internal audio and midi routing can be done via the mixer strips, and for external audio connections I use qpwgraph. For midi connections you may need to open the "midi ports/soft synths" menu to enable and/or reorder the ports.

[garvalf]

The issue with ACE FluidSynth plugin in MusE is that the generic GUI does not offer the SF2 file selection box, the native GUI entry is disabled due to lack of a native GUI in ACE FluidSynth. But I could use MusEs own FluidSynth plugin, which works fine.

yes that's true, I've just tested it now. ACE FluidSynth isn't working in Carla either. It looks like "Fluidsynth-DSSI" can be another option but I'm used to the "Fluidsynth mess" plugin which is fine.