Using MG Pro 1.6.18 with Cubase 15 on Windows 11. I just tried a few MIDI faders and the input is noticibly “lagging” as much as 2-3 seconds behind input from the fader. The MG fader can be moved instantly, while the cooresponding control in Cubase moves slowly to the new value in a few seconds. This didn’t happen previously, but since I haven’t used the faders in a while, I don’t know which update may have caused this. A mechanical fader via USB doesn’t display this problem. It was the same over USB or Wifi. It seems like a stream of data, such as cc data from a fader, is choked a bit. Perhaps a buffer gets too full or something like that. Regular macros and single commands are not visibly affected.
Are you on WiFi or USB?
I usually use Wifi, but I did test it with a direct USB connection also. There was no difference. Typical short commands are always essentially instant. But a “stream” of data like moving a cc fader shows a definite lag of a second or so. This didn’t happen in earlier versions, but I don’t use the faders all of the time and don’t know when this may have started.
OK, we will need logs from MetaGrid Pro and MetaServer - please send them to help@metagrid.app
I did send the log file from MG Pro, but even after adding the metaserver.ini file to the Metaserver folder, the log folder ramins empty. The issue is moving a MIDI slider results in a backlog of data to Cubase 15 in Win 11. If you move the fader up and down for 10 or 15 seconds, the movement in the VST continues for several seconds after releasing the control in Metagrid.
Investigating - will be back soon.
This issue has been fixed in the latest MetaServer for Windows.
The MIDI output path now limits excessive continuous-controller traffic so Cubase cannot accumulate a multi-second backlog during fader movement. We also removed synchronous per-event logging and other hot-path delays that contributed to the lag.
Please update to the latest MetaServer for Windows and let us know if you can still reproduce the issue.
This topic is being moved back to Needs Verification while the exact MetaServer Windows production build containing the MIDI-output correction is confirmed.
The reported continuous-controller backlog and hot-path logging changes still need an authoritative release-manifest link and a current regression result. If you can test with the current MetaServer Windows build, please share the exact version and confirm whether sustained fader movement over both USB and Wi-Fi stops promptly when the MetaGrid control is released.
The issue will be marked Fixed again after both the shipped build and regression evidence are recorded.