MDP2 fails to open an MD Pro-X layout

Question

MIDI Target Manufacturer(s): Other/Unlisted Maker

I opened an old layout in MDP PROx to verify it. I did not make any changes, but saved it. I mailed it to an interested user. He was unable to open it. He stated he was using MD Pro 2 (2.131) on IOS 10.3.3. The message is “…was created with a higher version of MD…”.

Is there any version of MDP Pro2 that can open a layout saved in MDP PROx?

Comments

It would work but that version of MIDI Designer Pro 2 is older and we bumped version before change to MIDI Designer Pro X

---

Which version is required? 3.2 and later?

---

2.3300, latest version is required. Apple should allow users to download arbitrary versions, but they do not. So at this point, you need Pro X.

---

The same issue occurs with attempting to load a file saved in Pro X Next on an iPad!!! I tried to load a file saved in Pro X Next 10.3.0 into Pro X 10.2.3. I get the message:
"Problem loading, rolling back. Layout created with newer version of MIDI Designer. Please update."


Does this mean no file will be able to open in an older version, including an older X version, and all users will have to update everytime a new version is released?

I design in Next to see if there are any issues with the Beta release. But then I save and try to open the layout in MDP Pro X. I no longer can do that. when I design in Next I account for the fact some new functions will not work with the latest Pro X.

How does MDP know which version a .mididesigner file was saved in? Can somethiing be done? There must be some clue in the file itself that could be overridden! I compared the first few lines of Next and ProX files and they appear to be identical.

---

When a feature or bug fix is added that means a layout cannot be backward compatible, then you are prevented from opening that layout in a prior version.  This version control is in the meta data - not typically visible to the user.

I think the item in Next 10.3 is the five byte checksum, and I think Dan is still pondering on an approach that will not require the bump on the production side.  Unfortunately, saving production from the version bump might mean the Next layout is temporarily orphaned - until the next feature that requires a version bump.

---

Send the layout to Support, we can hack the version number so it can be opened in earlier versions