Hello, I’ve been running Frescobaldi (2.0 up to 4.0.1) with Qsyntth/Fluidsynth installed by MacPorts on an Intel MacBook Pro and never had a sound problem. Could this problem be related to Rosetta (an Intel CPU emulator running on Apple Silicon)? I mean, synthesizer software compiled for Intel CPU and running inside Rosetta, while Fresobaldi is running natively on Apple Silicon, or vice versa?
Jun > 2025/04/07 18:06、Thomas Scharkowski <[email protected]>のメール: > > Hi, > > now I have tested Fluidsynth with Frescobaldi 4.0.1: > No sound. > > Back to Frescobaldi 3.3.0 both SimpleSynth and fluidsynth work. > > Anyone? > > Thanks, > > Thomas > > Mac M1 with MacOS 15.4 > >> Am 06.04.2025 um 17:22 schrieb Henning Hraban Ramm <[email protected]>: >> >> Am 04.04.25 um 22:57 schrieb Stanton Sanderson: >>> Same here with M2 Mac running 14.7.4- using qsynth (and refreshing the midi >>> preferences). I can drag the midi file to qsynth and it plays. I can go >>> back to Frescobaldi v3.3 and midi plays fine. >>> -Stan >>>> On Apr 4, 2025, at 3:45 PM, Thomas Scharkowski <[email protected]> >>>> wrote: >>>> >>>> Hi, >>>> >>>> I still get no Midi sound (with SimpleSynth). >>>> Any help appreciated. >>>> >>>> Thomas >>>> >>>> Mac M1 macOS 15.4 >> >> In a current songbook project, another contributor had problems with >> Frescobaldi 4 on MacOS and MIDI playback. >> >> We got it working with fluidsynth and QSynth from MacPorts, while the >> versions from HomeBrew didn’t work for him. >> >> I had the same setup running before (didn’t try HomeBrew). >> >> Generally, we must start QSynth before Frescobaldi or update the MIDI port >> in Frescobaldi’s preferences (same number, but needs a refresh). >> Same if I change the output device. >> >> Unfortunately, lilypond-devel and frescobaldi-devel on MacPorts are way >> behind, but the regular downloads work for us. >> >> Hraban >> > >
