| Re: Re: [hatari-users] removal of --midi-in and --midi-out options |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-users Archives
]
- To: hatari-users@xxxxxxxxxxxxxxxxxxx
- Subject: Re: Re: [hatari-users] removal of --midi-in and --midi-out options
- From: "donittel2@xxxxxxxxxx" <donittel2@xxxxxxxxxx>
- Date: Fri, 28 Jul 2023 02:32:52 +0200 (CEST)
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bluewin.ch; s=fxzs-2048-20230414; t=1690504372; bh=rL+AM9cdF16hweq/BctAE4U7a5SyLKenlmW663pO0sk=; h=Date:From:Reply-To:To:Message-ID:Subject:MIME-Version; b=mBtzbi1AK8rYEzhBZalxTdLeDZ0YZsKBwbK2NQyodQnCsqfhaA3dZe5MIxzx71aTS ZlSWhd49/RlnuPyThx2wOK1fytQQggTiS67wz1j9X2n8B75Y/DtZExXiusyVO4Xxb2 tCbhXy0kJZ//2D8qMSpNFX7zTmoViW+on2R6pzJjeOxtrsPYLZMbOqBS6wLhgFzZlV 18PzUlJ5kx0SkxTc0eeQwM5g0ryDX5JytgtfBhNmqdwW2YkeNZdiqxE08YXTn4i5RR xm14Pra/GpBIl2NB1sqVRE3vI6W+PjZK0MKQlE7QQluKjuZUowWjGzPGKq2I1LviWp Iinw3DOadQAIQ==
you found the solution your self man !!
lg
Christoph, St.Gallen
----Ursprüngliche Nachricht----
Von : eric@xxxxxxxxxxxx
Datum : 28/07/2023 - 02:19 (MS)
An : hatari-users@xxxxxxxxxxxxxxxxxxx
Betreff : Re: [hatari-users] removal of --midi-in and --midi-out options
Allright, I see.
I forgot to mention that I was testing v2.3.1 and v2.4.1 on 2 different
linux distributions, so it seems the option disappeared because the
2.4.1 I used was compiled with portmidi.
So on archlinux, hatari is compiled with portmidi,
and on nixos without. good to know ;-)
I just compiled hatari without portmidi, and the option is there again ;-)
Problem solved, and thank you, this was solved really fast.
Eric
On 7/28/23 02:06, Eero Tamminen wrote:
> Hi,
>
> When Hatari is built with PortMidi, MIDI devices are defined by port
> names in the GUI (and config file). PortMidi expects data for those
> devices to be real MIDI data!
>
> Only when Hatari is compiled *without* PortMidi, there are --midi-in
> and --midi-out device file options (and Hatari does not care what data
> is transferred through them).
>
> Currently Hatari does not support both at the same time, it needs to
> be built separately for each use-case. As real MIDI device use-case
> is much more common, releases are built with PortMidi for Mac.
>
>
> - Eero
>
> On 28.7.2023 2.20, eric wrote:
>> First of all, thanks for hatari, it is a wonderful piece of software.
>>
>> The ability to run a .prg file directly, as well as MIDI support, are
>> very useful features to help debug.
>>
>> I noticed that these 2 options disappeared between hatari v2.3.1 and
>> v2.4.1
>>
>> --midi-in
>>
>> --midi-out
>>
>> I know I can chose real MIDI devices as input or output using the
>> GUI, but previously I was able to communicate between hatari and a
>> specific software, just using files
>>
>> (I was using --midi-in /tmp/midiIN --midi-out /tmp/midiOUT)
>>
>> Now with newer versions I found no way of doing this.
>>
>> Is there a workaround/a hack that I could use ?
>>
>> Thank you
>>
>> Eric
>>
>> https://www.theotherdays.net
>>
>>
>>
>
>