MacOS 15.3.1 (ARM) - Crashes on Midi Input

[Ken Ledeen]

Entirely reproducible.

Non-fatal

Traceback (most recent call last):

File "/Applications/Frescobaldi.app/Contents/Resources/app/frescobaldi/midiinput/__init__.py", line 85, in analyzeevent

self.noteevent(event.type, event.channel, event.note, event.value)

File "/Applications/Frescobaldi.app/Contents/Resources/app/frescobaldi/midiinput/__init__.py", line 100, in noteevent

self.print_or_replace(note.output(self.widget().relativemode(), self._language))

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/Applications/Frescobaldi.app/Contents/Resources/app/frescobaldi/midiinput/elements.py", line 31, in output

return pitch.output(language) + (('='+ly.pitch.octaveToString(self._pitch.octave)) if QApplication.keyboardModifiers() & Qt.Modifier.SHIFT else '')

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~

TypeError: unsupported operand type(s) for &: 'KeyboardModifier' and 'Modifier'

[Federico Bruni]

I think it's fixed on master. I'll double-check tonight.

Ben has just opened a PR to fix another long standing bug. As soon as that is merged I'll make a new release.

--
Frescobaldi homepage: http://www.frescobaldi.org/
Mailing list: http://groups.google.com/group/frescobaldi
Issue tracker: https://github.com/frescobaldi/frescobaldi/issues
---
You received this message because you are subscribed to the Google Groups "Frescobaldi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to frescobaldi...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/frescobaldi/03c28bcd-8faa-47f0-a6ca-b595ead33da0n%40googlegroups.com.

[Ken Ledeen]

Hi,

Was this released?  4.0.2 maybe?

Sent from my iPhone

On Apr 30, 2025, at 10:47 AM, 'Federico Bruni' via Frescobaldi <fresc...@googlegroups.com> wrote:



To view this discussion visit https://groups.google.com/d/msgid/frescobaldi/536245a2-500b-42df-a17a-83aa78cce2b9%40email.android.com.

[Federico Bruni]

Yes, 4.0.2 has been released today

To view this discussion visit https://groups.google.com/d/msgid/frescobaldi/BFDB5A72-36F3-47E8-90E0-0F26CD89E428%40nevo.com.

[Ken Ledeen]

Many thanks ... I got it.  no more crashes on Midi input - but so far, no midi input at all.  I know the midi connection is fine because Pianoteq sees the keyboard.  I stopped pianoteq just t be sure that wasn't a problem.  I'll try some more things, and share the results.

THanks again for a great piece of code.

To view this discussion visit https://groups.google.com/d/msgid/frescobaldi/f2652092-c12f-4393-93a2-70143c2ade23%40email.android.com.

[Ken Ledeen]

I did some more checks ---  no problem getting midi input to Logic Pro.  It's just Frescobaldi that doesn't see it.  I believe all the parameters are consistent with Logic Pro - so no reason why it wouldn't work/

[Stanton Sanderson]

I am experiencing the same problem (no mini outpour). I can drag a midi file to qsynth app icon and it plays. Have not found a way of playing midi in the Frescobaldi app. (Mac Sequoia, ARM m3)

Stan

> To view this discussion visit https://groups.google.com/d/msgid/frescobaldi/CAHBGdwVaWuUNvZ12GHohhHE9s%2BOoN%2B7apbBQWg2PO6Q7q7SgXw%40mail.gmail.com.

[Helly, John]

Aloha.

I confirm that 4.0.2 does not send any midi to Qsynth.  I juat tested 3.3.0 and it plays fine.  I shut it down and opened 4.0.2 with the same *.ly file and get nada.

J.

----------------------------------------------------------------------------------------------------------------------
John Helly / San Diego Supercomputer Center / Scripps Institution of Oceanography 
https://www.sdsc.edu/~hellyj / 808 205 9882 / 760 8408660

To view this discussion visit https://groups.google.com/d/msgid/frescobaldi/EC75719A-2BCF-4D98-87AB-2DC7068655DD%40gmail.com.

[Helly, John]

To be more complete:

Mac Studio 2023

M2 Max

Sequoia 15.3.2

Qsynth 0.5.6

Fluidsynth 2.3.4

/opt/local/share/sounds/sf2/GeneralUser_GS_v1.471.sf2

J.

----------------------------------------------------------------------------------------------------------------------
John Helly / San Diego Supercomputer Center / Scripps Institution of Oceanography 
https://www.sdsc.edu/~hellyj / 808 205 9882 / 760 8408660

[Ken Ledeen]

Hi,

I've not seen anything in a while.  I have 4.0.2 running on a Mac Mini M4.  I have no problem with midi input to Logic Pro or to Pianoteq, but have had no success with midi input to Frescobaldi.  

Suggestions?

Many thanks in advance.

Ken

[Federico Bruni]

I would be curious to know if other macOS users who own a MIDI device
can confirm that MIDI input doesn't work.
Just to understand if it's a general problem for everybody or a
configuration problem in Ken's system.

Ken, perhaps a video screencast while you try to use midi input in
Frescobaldi would help.



Il giorno ven 23 mag 2025 alle 18:57:55 -04:00:00, Ken Ledeen

> https://groups.google.com/d/msgid/frescobaldi/CAHBGdwXPDZ0x6HPWiSW35RT5FXG2u%2BRtM6vFQ9QsZOobqzjMfQ%40mail.gmail.com.

[Ken Ledeen]

To confirm. I have the same problem-no midi input. Works for my other applications. Eg Logic Pro.


Sent from my iPhone

> On May 27, 2025, at 6:39 AM, Federico Bruni <fe...@inventati.org> wrote:
>
> I would be curious to know if other macOS users who own a MIDI device can confirm that MIDI input doesn't work.

[Stanton Sanderson]

Ditto. Have not found a solution. 2024 MB Air M3, OS 15.5 (Sequoia), QSynth plays the file if I drop it on it. MacPorts reports portmidi @2.0.4_0 (active) installed. The file is generated- I can drop it on Qsynth and it plays, the Frescobaldi midi window reports the file name, it appears to be playing, but no output. -Stan

> To view this discussion visit https://groups.google.com/d/msgid/frescobaldi/37DE4D7B-C776-40F7-A76B-A91E4D54B0B0%40nevo.com.

[Ken Ledeen]

Sorry --- I didn't notice that the original question was about my problem.  I've attached a screen capture to this email

--- no problem with Logic Pro or Pianoteq.  Perhaps I have a configuration issue with Frescobaldi.

 Frescobaldi Bug.mov

To view this discussion visit https://groups.google.com/d/msgid/frescobaldi/EF774E93-57E2-426D-B4EF-27659951D412%40gmail.com.

[Federico Bruni]

We are talking about MIDI input here, not MIDI output

Il giorno mar 27 mag 2025 alle 06:38:01 -05:00:00, Stanton Sanderson
<stan...@gmail.com> ha scritto:

[Stanton Sanderson]

Mea culpa. I realized that after I sent it- sorry for the noise. -Stam

[Eef Weenink]

Some info about Midi input on my Mac

I tested with IRig Keys input. 

Insert USB cable

In preferences set MID input + refresh

In Tools > Midi > Input 

In panel choose Start Capturing 

Runs fine as always. 

So probably no Frescobaldi but. 

Regards, Eef 

Macbook Pro 2015 (Intel) + OCLP + Sequoia 

Frescobaldi: 4.0.2

Extension API: 0.9.0

Python: 3.12.7

python-ly: 0.9.9

Qt: 6.9.0

PyQt: 6.9.0

qpageview: 1.0.0

OS: macOS-15.5-x86_64-i386-64bit

installation kind: standalone .app bundle

To view this discussion visit https://groups.google.com/d/msgid/frescobaldi/CAHBGdwVaWuUNvZ12GHohhHE9s%2BOoN%2B7apbBQWg2PO6Q7q7SgXw%40mail.gmail.com.

[Ken Ledeen]

 Frescoboldio Midi Input Problem.mov

I am returning to this issue.  I have downloaded and installed 4.0.3.  As the attached video shows, mini input works fine with other applications (Pianoteq, Logic Pro), but not with Frescobaldi.  I rebooted my computer, just to be safe.  I tried with Pianoteq running, and with it not running.  The midi input specified in Frescobaldi is the same as for Pianoteq - but the latter sees the input, and Frescobaldi does not..

My apologies for the size of the video file.

Any suggestions for how I might resolve this issue would be most appreciated.

Thanks

Ken

To view this discussion visit https://groups.google.com/d/msgid/frescobaldi/BL1P220MB08038967BC2CFAD373CD09358664A%40BL1P220MB0803.NAMP220.PROD.OUTLOOK.COM.