Michael Gregorius

> And this is why I think , that it is not a bug: > prodaw_state.mp4 > > Used PRO DAW, PRO ReWire and VST soft.synths ... I don't understand...

The tests in the upgrade routine `DataFile::upgrade_loopsRename` do not work. For example when checking for the replacement of `beats/rave_hihat01.ogg` it's testing against `factorysample:beats/rave_hihat01.ogg` which doses not match and thus the...

Pull request #7235 fixes the problems that have been introduced by adding the BPM values to the names. @mirk0dex, I have removed the code with regards to the `factorysample:` prefix....

Yes, it might indeed be a shortcoming of some of the LMMS synths. In VSTs and other synths you often have the option to enable or disable phase reset for...

@firewall1110, if you check comment https://github.com/LMMS/lmms/pull/7230#issuecomment-2081367349 you will find that Lb302 renders in a deterministic way on the first render. Once the render is through the instance stays in an...

> `factorysample:` was needed in order to Not replace any custom user samples with the same name. Removing it could be dangerous. The problem is that the [example file](https://lmms.io/lsp/?action=show&file=3625) that's...

> Not sure about the whole `factorysample:` deal at this point. What I can tell you that every time I've seen a stock LMMS sample in a project's XML, it...

Thanks @mirk0dex! These files are exactly what I was asking for. :+1:

With pull request #7236 `factorysample:` prefixes are supported again.

With commit d1fa6ddac8c the "bassloopes" problem is fixed as well. So pull request #7236 should now close this issue.