LMMS / LMMS/lmms

VeSTige preset issue

Open
#8,491 14 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
C++
Stars
10.4k
Forks
1.3k
Avg merge
2d 13h
Merged PRs (30d)
7

Description

### System Information

Windows 11 64-bit, Acer Nitro V 15, Intel Core i9-13900H, 16 GB RAM, NVIDIA GeForce RTX 4050, Laptop GPU

### LMMS Version(s)

1.3.0-alpha.1.102+g89fc6c960-mingw-win64

### Most Recent Working Version

_No response_

### Bug Summary

Hi,

I wanted to report a potential bug in VeSTige.

So I was using Ninjas2 to slice my sample, and when I was done I saved it as a preset to use in future projects, so I went on ahead and tried using it once I opened the project, but no sound was triggered from the sample once the midi got to the piano keys.
So I click on the sample (or VeSTige) and then the preset I saved wasn't loading, so I find my preset selected Ninjas2 and it was okay at first.

But the moment I hit "ctrl + s" it saves, and I reopen to double check, nothing played again, so I started the process from scratch to redo the sample slicing and saving the preset (Clicking both the small and big floppy disk on VeSTige, because I'm unable to save the sample properly without having the settings change after I save it, but it still doesn't work. Also I'm using a WAV file for the sample too), but when I try to load it, the same happens again.

Image

(Also this could be user error, but when ever I slice the sample, save it, close it, open it again, it only plays one note with the entire sample (and this is from VeStige) and the rest are silent)

Let me know how I can fix it or if it's a bug.

### Expected Behaviour

- Load the slicer
- Load sample
- Slice sample
- Sample gets saved as preset (small floppy disk near the piano keys on Vestige window)
- Saving the track settings so they don't change (big floppy disk near the plugin selection section on Vestige window)

Expected Behavior:
Can go into another project, find the Preset, load it, use it, save it. (If I want to make changes, I can save it, re-open it, and expect it to still play and have the midi trigger the sound)

Image

### Steps To Reproduce

Steps:
- Open a project
- Clear track
- Add VeSTige
- Open Ninjas2 (Make sure it's downloaded: https://github.com/clearly-broken-software/ninjas2/releases )
- Import WAV file into Ninjas2
- Slice WAV file
- Test to see if anything plays from the piano keys (both on Ninjas and VeSTige)
- Save preset (small floppy disk on VeSTige)(give it a name)
- use midi to test note/sound trigger
- Save the settings for the track and sample (big floppy disk on VeSTige)
- Save the Project and close it
- Open it back

And the preset should be gone once you click the track with VeSTige.

### Logs

Click to expand

  

### Screenshots / Minimum Reproducible Project

_No response_

### Please search the issue tracker for existing bug reports before submitting your own.

- [x] I have searched all existing issues and confirmed that this is not a duplicate.

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the issue through the VeSTige entry point using Ninjas2 and a WAV sample, following the listed preset and project save steps. Compare the small preset save, track settings save, and project reload behavior, then verify that the preset remains available and MIDI triggers all sliced samples after reopening.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.