Skip to content
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

Preset saving system bug #4927

Closed
RoxasKH opened this issue Apr 2, 2019 · 5 comments
Closed

Preset saving system bug #4927

RoxasKH opened this issue Apr 2, 2019 · 5 comments

Comments

@RoxasKH
Copy link
Contributor

RoxasKH commented Apr 2, 2019

The title really doesn't explain it very well. What i want to make devs notice, is that if you save a preset of an instrument that has one of its knobs linked to a controller in the project you saved it, if you then try to load it in a new project that has no controllers, just clicking on it in the sidebar will make LMMS freeze or crash and close itself.

I think it should be more clever if when you save a preset this way it autoremoves and don't save the information about the connection to a controller.
Or a better way would be to make the preset create a new controller with the same characteristics in the project where you load it and autoconnect the knob to it.

I'm on Windows 10 64-bit and i'm using LMMS 1.2.0 RC8

Here i upload an example, just put it in you presets folder and try to load it from the sidebar
Glitchy.zip

Thanks

@ghost
Copy link

ghost commented Apr 2, 2019

Confirmed. Automation track connections are also stored in the preset, they are unused but don't seem to crash LMMS.

@enp2s0
Copy link
Contributor

enp2s0 commented Apr 11, 2019

I've fixed the crashing issue with pull request #4937.

@01jw
Copy link
Member

01jw commented Apr 24, 2019

Should this be closed via #4939? Or are there still more issues that need addressing? The way I'm reading it, this issue should be closed as being resolved.

@enp2s0
Copy link
Contributor

enp2s0 commented Apr 24, 2019

My pr fixes the crash, but perhaps we should keep this issue open because we probably shouldn’t be saving controller connections in the first place, which my pr does nothing to fix.

On the other hand, this issue is directly about the crash, which has been fixed, so I’m in favor of closing it.

@01jw
Copy link
Member

01jw commented Apr 25, 2019

Yeah, I agree. This issue is describing a bug, and leaving it open to serve as an enhancement will likely cause confusion.

@noahb01 Feel free to create a separate enhancement request, since you likely know a lot more about what's going on. I'd agree that either 1) controller connections should not be saved or 2) controllers should be added when the preset is added.

@01jw 01jw closed this as completed Apr 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants