Weird Grid Behavior (with vid)

I am finding that with the latest updates, you have to have Grid Editor 1.5.5 open in order for the Grid modules to transmit MIDI Data. Grid Editor has to be running but it can be in the background. Is that your issue....because that is what I am finding.

Same issue here, have updated today to 1.55, and my pbf4 module wouldnt send midi data to knot and then to my elektron devices anymore...however, clock and transport still working through knot. I noticed knot wasnt reacting to fader/encoder/button moves because the small white leds are not lighting anymore 😐 thus, resulting in grid not sending midi signal anymore.

Ok, i 've manually updated the latest firmware(today's release) and now it works again 🙂

We had a bug in the firmware, but we've just released a fix. Please open the Grid Editor — it will prompt you to update. Once it's updated, plug in your module and the firmware update will appear. Please install it.

Grid is now sending midi to knot, but is not recognised by editor 🫩🤷🏻‍♂️

Try connecting directly to your computer, or to another computer and NVM erase could help. https://docs.intech.studio/guides/troubleshooting/factory-reset/

Downgraded to editor 1.5.4 and Grid 1.23 sthing, works very well, but will give it a try asap 🙂

Same here, since I've updated. I tried everything, Newest version of the editor, oldest versions, firmware updates, Factory resets. It's totally unstable (sometimes gets MIDI, sometimes not, not recognized on the editor, or recognized but doesn't move ..). I don't know what to do next...

Did you erase NVME on grid editor ? worked pretty well for me

Yes. It works again. Then, I store my values, still works then, when turning off/on again it's unresponsive.

..weird

Okay, re tested mine today, same pb, not recognised anymore on grid editor..then decided to downgrade to 1.5.4 and 1.2.39, it works, midi wise, but at times, pbf4 would boot up on its own while playing 😣

The new firmware has improved the transport. As far as I know, today we’re expecting the final fix for the previous firmware fixes..

The last firmware fixed it for me!