Standalone Midi Lag

Trevor being Trevor's icon

Hi there!

I am trying to export a Max for Live device I built to control a guitar pedal as a standalone app. I made the needed changes such as being able to detect and change midi outputs as well as configuring the standalone object. However, when I launch the app on Mac or Windows there is an odd delay before the pedal starts responding. It seems like I have send program change numbers up to around 25 and then I'll see the pedal jump to 17 and then quickly to 18, 19, 20...all the way to 25 and then the app seems to work as normal. Sometimes it doesn't respond no matter what I do. I did some testing using the print object and messages are being sent down the midiout right away so perhaps it at the OS level?

Any advice or guesses is always appreciated. I definitely update this thread if I get to the bottom of it.

Source Audio's icon

not enough informations.
overdrive on ?
midi loopback ?
java involved ?

Trevor being Trevor's icon

Overdrive is on, but I tried switching it off. No midi loopback or java involved.

This is essentially what I added to my Max for Live device to prepare it to work as a standalone. I made this simple patch to see if the same issue would occur. It works fine in Max, but not at all as a standalone. The original patch with much more going on, works after a strange delay using the same logic.

This is the current UI in presentation mode.

These are my standalone settings.

If you need more info, let me know!

Trevor being Trevor's icon

Oh! I noticed the problem occurs when I open up a Collective as well

Also I've been using this as a reference...
https://docs.cycling74.com/max8/vignettes/standalones?q=standalone


Source Audio's icon

Why do you use 2 menus to set midiout port ?
listed controllers affect midi input, not output.
Why do you use database ?
scanning database might disturb or slowdown
normal operation till fully completed.
and ... you are windows user, where midi isn't so
troublefree as on mac, in first place when several apps
try to use same midi ports.

Trevor being Trevor's icon

Finally had some time to test again today.

The controllers seem to play some role even though they should only affect midi input as you said. For example, I boot up the "working" standalone and select my Morningstar interface, but leave the controllers list alone. I start sending program changes up to about 20 and nothing happens. I then select the Morninstar interface from the controllers list and the pedal starts responding. HOWEVER, I then press Refresh Midi Info and only select my Morningstar interface again and leave the controller drop-down alone, everything still works.

I was not able to build a standalone that worked at all today. I tried turning off database in the standalone settings as suggested. Also, I said the problem occurs on Mac and on Windows so it's not an OS specific issue as far as I can tell. I'll keep trying, but still very unsure what the heck is going on. Any slightest ideas may help me get to the bottom of it and are appreciated.

Source Audio's icon

I overlooked wrong menu connection to midiout
in your screenshot.
you need middle one - symbol output.