search

ahlstromcj / sequencer64

A major reboot of Seq24. Current release 0.97.0 (2021-05-13), native JACK MIDI, Song recording, playlists, and a Windows/Qt version. For fresher code, see the Seq66 project. Note that trigger and mute-group-in-MIDI-file formats have evolved! Back up your work!
GNU Affero General Public License v3.0
235 stars 29 forks source link

Using MIDI System Real Time messages to Start (FAh) & Stop (FCh) Seq64 not working #206

Open pnberry50 opened 4 years ago

pnberry50 commented 4 years ago

I would like to use the MIDI Start (FAh) & Stop (FCh) messages to start and stop Seq64 but it is not working. I have correctly selected my MIDI input source in the Options -> MIDI Input window. I have used (Linux) amidi --port=hw:3,0,0 --dump to make sure I am sending the correct commands but no joy. I cannot start Seq64 with the Start command and the Stop command does indeed stop Seq64 but it also resets the Seq64 patterns and I cannot restart the patterns until I manually click the stop button. Interestingly, the MIDI Start and Stop commands change the icons on the Play and Pause button correctly: I send Start and the icon changes to the pause icon and I Send Stop and the icon changes to the play icon - that works. Am I missing something or is this feature broken?

ahlstromcj commented 4 years ago

I've been looking into this using "sendmidi" (a github project for sending MIDI messages) to send 0xFA, FB, and FC to the "seq64 in" port created when running "seq64 -m" (the opposite of "seq64 -a"). What I have found is that the first event sent makes it through fine, but the next one is held in the ALSA buffer, and doesn't appear in seq64 until the next event is sent. So I am looking into that, it's puzzling right now. More later, sorry to take so long to get to this.

-------- pnberry50 21:05 Thu 21 May --------

I would like to use the MIDI Start (FAh) & Stop (FCh) messages to start and stop Seq64 but it is not working. I have correctly selected my MIDI input source in the Options -> MIDI Input window. I have used (Linux) amidi --port=hw:3,0,0 --dump to make sure I am sending the correct commands but no joy. I cannot start Seq64 with the Start command and the Stop command does indeed stop Seq64 but it also resets the Seq64 patterns and I cannot restart the patterns until I manually click the stop button. Interestingly, the MIDI Start and Stop commands change the icons on the Play and Pause button correctly: I send Start and the icon changes to the pause icon and I Send Stop and the icon changes to the play icon - that works. Am I missing something or is this feature broken?

-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/ahlstromcj/sequencer64/issues/206

-- Nadia Comaneci, simple perfection. -- '76 Olympics

pnberry50 commented 4 years ago

I should also mention I am using Seq64 just with ALSA, no JACK. As a test I tried it with jackd running but that did not change anything. When I invoke se64 I am not using any options.

ahlstromcj commented 4 years ago

Why did you close it? Just curious, I still want to track it down, and I found some other issue that bugs me. Thanks!

On Sun, May 24, 2020, 17:37 pnberry50 notifications@github.com wrote:

Closed #206 https://github.com/ahlstromcj/sequencer64/issues/206.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ahlstromcj/sequencer64/issues/206#event-3368332825, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB45LKEOY62UEG5ATTYREHDRTGHSPANCNFSM4NHOSUUA .

pnberry50 commented 4 years ago

Hello,

I closed it because I am bumbling amateur (sorry about that).

I really appreciate that you are tracking this issue and I really appreciate using Seqencer64.

Paul

On Sun, May 24, 2020 at 4:08 PM C. Ahlstrom notifications@github.com wrote:

Why did you close it? Just curious, I still want to track it down, and I found some other issue that bugs me. Thanks!

On Sun, May 24, 2020, 17:37 pnberry50 notifications@github.com wrote:

Closed #206 https://github.com/ahlstromcj/sequencer64/issues/206.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ahlstromcj/sequencer64/issues/206#event-3368332825, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AB45LKEOY62UEG5ATTYREHDRTGHSPANCNFSM4NHOSUUA

.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/ahlstromcj/sequencer64/issues/206#issuecomment-633320503, or unsubscribe https://github.com/notifications/unsubscribe-auth/APQ4XV4UWACM4WIVIHE5TM3RTGZHBANCNFSM4NHOSUUA .

ahlstromcj commented 4 years ago

I partially fixed this issue (and some unreported issues) in the midi_control branch. However, after a couple of MIDI control events (Start, Stop, or Continue), sending an event doesn't act until the next event comes in. The event isn't even received from ALSA. For example, once the issue kicks in, sending a Start does nothing. Then sending a Stop causes the Start to be processed.

The setup is this: (1) Run "seq64 --User --verbose" which will update the configuration to use the virtual (manual) ports; (2) In another window, run

sendmidi dev "seq64 in" start (or stop, or cont)

You can watch the command-line window and the GUI to see what happens.

Note that sendmidi is a separate project on Github. Download it and run the "LinuxMakefile" to build it as per the site instructions.

This bug does not occur in Seq66, which is essentially the same ALSA code!

ahlstromcj commented 3 years ago

Thanks. Be sure to try out the relatively new Seq66 project on GitHub. It's come a long way in the last few months. I finally bought a LaunchPad Mini and got it working as a controller and as a display for song status.

-------- pnberry50 20:34 Sun 24 May --------

Hello,

I closed it because I am bumbling amateur (sorry about that).

I really appreciate that you are tracking this issue and I really appreciate using Seqencer64.

Paul

On Sun, May 24, 2020 at 4:08 PM C. Ahlstrom notifications@github.com wrote:

Why did you close it? Just curious, I still want to track it down, and I found some other issue that bugs me. Thanks!

On Sun, May 24, 2020, 17:37 pnberry50 notifications@github.com wrote:

Closed #206 https://github.com/ahlstromcj/sequencer64/issues/206.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ahlstromcj/sequencer64/issues/206#event-3368332825, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AB45LKEOY62UEG5ATTYREHDRTGHSPANCNFSM4NHOSUUA

.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/ahlstromcj/sequencer64/issues/206#issuecomment-633320503, or unsubscribe https://github.com/notifications/unsubscribe-auth/APQ4XV4UWACM4WIVIHE5TM3RTGZHBANCNFSM4NHOSUUA .

-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/ahlstromcj/sequencer64/issues/206#issuecomment-633359352

-- Don't you wish you had more energy... or less ambition?