_import suffix mystery

Wuzzup with _import files?
I feel like I’m doing something fundamentally wrong when I attempt to save my projects on the MPC One+. One example:

I uploaded a bunch of samples and saved them as a project file (.xpj). A few days later, I realized that I named some of them incorrectly, so I opened the file, edited the names as needed, pressed Menu, tapped the “Save” icon, and tapped the “Project” icon. When I went to work on the project a little more, I found the original project file AND a new file with the _import suffix added. When I opened the original file, none of the new names had been saved. When I attempted to open the _import file, I got a warning on my screen saying, “Caution! Loading a project will replace everything in memory. Do you want to continue?” If I continue, I get another warning: “Sample not found. Listing the first three…blah, blah, blah…Resolving the issue will remove all references for the sample.”
I’ve fallen down the same rabbit hole when I attempt to edit sequences I’ve created, or import new sounds to sets I’ve created. What basic step am I skipping or missing?

Apparently, this query is either so obtuse or so dumb that no one cares to respond. Wonderful forum, this is.

don't get mardy, sometimes people miss posts. Can you confirm which firmware version this is?

Thanks for replying! Sorry for my poor tone; I've been bummed by a lack of responses on a number of MPC user groups. My firmware is 3.4.3.

Update to firmware 3.5 and see if this fixes it, I suspect it will.

I updated my firmware to 3.5 a few weeks ago, but the mystery of the _import suffix remains. I have projects without this suffix and with it. I never named a project with that suffix; the MPC One added it. I have no idea what the difference is between the two file types. When I open the projects without the _import suffix, it opens showing the name WITH the suffix. And I still have these weird warnings (as described above) and problems saving my work. I would like someone to explain what the _import suffix means, why it's automatically added, and what to choose when I get the various warnings.

Coyote Loops! wrote:I updated my firmware to 3.5 a few weeks ago, but the mystery of the _import suffix remains. I have projects without this suffix and with it. I never named a project with that suffix; the MPC One added it. I have no idea what the difference is between the two file types. When I open the projects without the _import suffix, it opens showing the name WITH the suffix. And I still have these weird warnings (as described above) and problems saving my work. I would like someone to explain what the _import suffix means, why it's automatically added, and what to choose when I get the various warnings.

In my experience, filename_import is what it saves mpc2.x projects imported to mpc3.x

When you're opening the projects without the suffix the MPC is finding a reason to convert them to MPC3 projects. But you're saying the projects were originally created in V3.4.3?

The warnings are because the sample, named in the original file, can't be found. That's because you've renamed them since the original, so the MPC can't find them. Something is going awry when saving the _import version.

And you're saying this happens with every project you create from scratch in 3.5 too? It always converts it to xfilename_import next time you open it?

Do you have a template project you always start with? Try deleting that and making a new template project, maybe it got corrupted.

Thanks for the useful info. I've only had the MPC One+ since October 2024, so I think it's been running 3.4.3 since I got it. I do not have a template project; I just start from scratch with each new project. I can't say that it has happened in 3.5, since I've just been wrestling with my (older) first projects all this time (and BTW I just updated to 3.6). I'm going to start a new project with some outboard samples and see how it goes.