-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Project crash on loading, controller loading error #4060
Comments
Removing the peakcontroller line in |
Reproduced on RC5
When saving, LMMS will delete every track in BB-editor because it's not needed, but it won't delete the peak controller, which won't be able to load! |
Temporary workaround for those wondering how @DeRobyJ was able to remove the lmms -d myproject.mmpz > myproject_xml.mmp For a Windows user, something like this, perhaps: "C:\Program Files\LMMS\lmms.exe" -d "%userprofile%\Desktop\myproject.mmpz" > "%userprofile%\Desktop\myproject_xml.mmp" Or Apple: "/Applications/LMMS.app/Contents/MacOS/lmms" -d "~\Desktop\myproject.mmpz" > "~\Desktop\myproject_xml.mmp" Or Linux: "~/Downloads/lmms-1.2.0-rc5-linux-x86_64.AppImage" -d "~\Desktop\myproject.mmpz" > "~\Desktop\myproject_xml.mmp" Then you can edit the xml file according to @DeRobyJ's instructions and it will open just fine again. |
What about 1.1.3 Does files saved with 1.1.3 also have this bug? |
Absolutely not, the RC's are the current versions of the software and all bugs should be tested and be reported according to them, not 1.1.3. Not to mention all these versions are official because they are released on github and shared through the official website. |
@musikBear we sent him here and asked him to open this bug report. It's a critical bug for |
Lines 1291 to 1294 in eb9b460
This crashes LMMS, even for release build. Defining QT_NO_DEBUG will suppress such crashes, but it isn't a real fix.LMMS should be able to cleanup broken connection after loading bad project files. |
Copying my two comments from #2948 here for completeness (with one slight adjustment in the code snippet). The problem with the file "0036 (lento)-01.mmpz" is caused by a non-existent effect that's referenced by a peak controller. The relevant section looks as follows: <controllers>
<Peakcontroller type="3" name="Controller 1" effectId="12959"/>
</controllers> However, there is no effect with that ID and the string "12959" only shows up in the peak controller section throughout the whole file. This leads to a When I change the code as follows the file can at least be loaded: void Song::restoreControllerStates( const QDomElement & element )
{
QDomNode node = element.firstChild();
while( !node.isNull() && !isCancelled() )
{
Controller * c = Controller::create( node.toElement(), this );
if (c)
{
addController( c );
}
node = node.nextSibling();
}
} Although I assume that the peak controller will not be connected in that case. But it might come in handy to save most of the project. |
Yes that will save old project, and there is nothing more to be done about it. |
#4060 (comment) fixes the crash, but it messes up controller connections. I think I can fix it. |
Pull request ready: #4391. |
Some projects saved with 1.2 beta versions will always fail to crash.
Affected projects trigger this assertion:
backtrace
The bug is OS-independent.
These are two affected projects:
crashing project.zip
By unpacking "pentatonica emitonica-01.mmpz" using this tool you can see that a peakcontroller is present but no peakcontrollereffect is found, as opposed to a good project that will show both the controller and the fx.
Here are the xml of one of the affected project, along with a sample .mmp file with peak controller present
goodvsbad.zip
The text was updated successfully, but these errors were encountered: