Re: [hatari-devel] PortMidi issues

[Nicolas Pomarède <npomarede@xxxxxxxxxxxx>]

Le 26/12/2020 à 13:35, Eero Tamminen a écrit :
> Hi,
>
> On 12/26/20 12:49 PM, Nicolas Pomarède wrote:
> > Le 26/12/2020 à 01:09, Eero Tamminen a écrit :
> >
> > > It was very annoying to debug because *every*
> > > mouse move in their GUIs generates Hatari MIDI
> > > trace output (Nicolas?), so I just changed that
> > > particular error to LOG_WARN.
> >
> > this is because the 2 ACIA used for keyboard and midi are connected to 
> > a single MFP pin 4. So when you move mouse/press key or receive midi 
> > bytes, the OS will only get one interrupt for both and need to check 
> > each acia to see which one triggered the interrupt, hence the trace in 
> > the midi part when mouse is moved.
>
> Could the trace output somehow detect & drop mouse
> events from MIDI traces, to make them usable?

Hard to do, at the HW level the OS is really reading the midi's acia to 
check if the event comes from the midi or the ikbd, so it's normal that 
moving mouse is waking up the midi part too and in some other cases it 
might be needed to have traces here.
Better not moving mouse or touch keyboard when you want to debug midi.


> Fedora package doesn't have it:
> https://src.fedoraproject.org/rpms/hatari/blob/master/f/hatari.spec
>
> so I think we can drop it too.
>
>
> > also what about deb packages ? Do they require portmidi-devel on their 
> > own or not ?
>
> They don't:
> https://sources.debian.org/src/hatari/2.3.0+dfsg-1/debian/control/

it's not in mageia either, so ok, let's drop it now.

Nicolas