MetaGrid Pro 1.6.7 Hot Fix released

News & Updates
1

MetaGrid Pro 1.6.7 Hot Fix Released

This update brings the following fixes:

• Button Snapshots now work as expected across all systems.

• Fader Titles display correctly on all platforms.

• Stability Improvements with multiple crash fixes based on user reports.

• The add-ons grids are now correctly imported from the Presets.

FYI, we are working with Steinberg to finalize our MIDI Remote integration which will be solved through MetaServer / MIDI Remote device updates.

Thanks for your feedback—keep creating!

1 Like
2

Unfortunately, I am getting periodic crashes on my iPad with 1.6.7.
More so than 1.6.6. I think 1.6.5 was the last version that was able to stay loaded all day long without quitting abruptly.
When 1.6.7 crashes, I am having a hard time restarting the app on my iPad unless I first quit Metaserver and then relaunch Metaserver after MGP is on the refresh screen.

Is anybody else having these sorts of issues?

3

Yes, same here. Cannot even launch on one of my iPads. One iPad connects, but the other one keeps crashing. Test Flight is down too.

4

Once I was able to get MGP to relaunch and then reinstall my backup, I was finding that when switching to the finder, messages, etc…that no grid was loading and I had to keep re-selecting the grid in the grids manager for most of my profiles. It would take a few times of switching apps and then it would remember them. Very strange.

1 Like
5

Just restoring from iTunes backup now. :crossed_fingers:

6

Things are working okay here now. The restore didn’t go as expected i.e. MGP was completely missing. I recommend just deleting the app and re installing from the app store.

I recommend periodically backing up all your Workspaces.

7

Fader titles are not displaying correctly here.

8

In the mean time while you guys are figuring this out, if there is a way to make it so that the faders are still usable even if it can’t find the title, that would be great. It wouldn’t be such an issue if it weren’t for the fact that it causes 4 out of 8 of my faders to be completely broken.

9

Good advice…always do incremental backups. I always name it MGP with todays date like. MGP022825.

I just now had to try to open MGP 4 times in a row and the 4th time, it completed the connection process and started working.

1 Like
10

We are so sorry to hear it - we have analyzed the crash logs from the App Store - just five crash instances of one type - that indicates that iOS is killing MGP for some reason. Can you please make sure if you are sharing the crash logs with the developers?

11

@dylanmixer What’s wrong with the faders? Any description of the issue?

12

The same issue as since day 1 of the MIDI Remote update. Some fqc fader titles fill in, some don’t. The ones that don’t, render the fader as a blank block, making that fader unusable. So at any given time, I can only use about 3-4 of my quick controls.

This post said it was fixed. It is not. Apologies if I misunderstood.

13

I have both Make sure Share iPad Analytics and Share with App Developers both switched ON.

Do I need to manually send them to you?
In the analytics data section I can see multiple files in the Metagrid Pro category.
4 from yesterday, 23 from February 27th.
Are those crash logs…or do those get generated even if the app does not crash?

14

@MetaGrid_Admin if you want I can maually email each of the 30 or so .ips files I am seeing in my iPad. Is that necessary for me to send them to you?

15

@Ben-Z We have received the logs - investigating this - seems to be an performance issue - the fix should be out with a day or two.

16

Fantastic—
So that I know in the future—- when MGP crashes in my iPad, do you automatically receive the crash report/.ips file?
Or do I need to manually email it to you?
Thank you!!

17

We started to receive the crash logs from your device - no need to send the crash logs manually now.

18

Can you please confirm that this is still a known problem and is being worked on? Or is my case unique?

19

@dylanmixer - it is a known issue - it is a Steinberg API issue with QC/insert handling. We have written to Cubase PM - after the initial answer from the devs to check if the users are on the latest Cubase, they got radio silent despite our multiple enquiries.

20

Thank you for the update.