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

Replacements for .ds files? #24

Closed
SirBothersome opened this issue Jul 30, 2016 · 4 comments
Closed

Replacements for .ds files? #24

SirBothersome opened this issue Jul 30, 2016 · 4 comments

Comments

@SirBothersome
Copy link
Contributor

SirBothersome commented Jul 30, 2016

So I'm about 90% finished with a new acoustic library, and I've got a fairly decent amount of source material for the Electro Library. Since the essentials are coming close to being covered, I was wondering. Was there any interest in replacing the plethora of random/weird/useless-but-fun/esoteric .ds sound files with similar content? I don't want to waste any time making stuff we don't need. Thanks

@DeRobyJ
Copy link

DeRobyJ commented Aug 24, 2016

Actually I use those .ds files in a lot of projects, and replacing them would break those projects, I'd have to manually replace them :(

@tresf
Copy link
Member

tresf commented Aug 24, 2016

replacing .ds sound files with similar content?

Depends what you mean by "similar". If the samples are of equal length and similar sound, we can write an upgrade script.

Undoubtedly at some point we have to break backwards compatibility, but the strategy for doing so must be carefully thought of. Making thousands of tracks in our LSP instantly become unplayable is a bit of a problem and offering a sample pack downloads would be a lot easier if we employed an installation technique that unburdened the user from this task.

For example, if we add a new file extension .sspz -- a new hypothetical sample pack archive format -- to LMMS (and register the file association with the OS to auto-open with LMMS) we could have a process which imports the sample pack into LMMS WORKING DIRECTORY configured in the DAW and allows a smoother transition to a brand new internal library.

Then we can update the code on our LSP and also within LMMS to warn when old projects borrow from a dated sample pack, etc.

@SirBothersome
Copy link
Contributor Author

SirBothersome commented Aug 24, 2016

For example, if we add a new file extension .sspz -- a new hypothetical sample pack archive format -- to LMMS (and register the file association with the OS to auto-open with LMMS) we could have a process which imports the sample pack into LMMS WORKING DIRECTORY configured in the DAW and allows a smoother transition to a brand new internal library.
Then we can update the code on our LSP and also within LMMS to warn when old projects borrow from a dated sample pack, etc.

I like that idea,

Depends what you mean by "similar".

By similar, I originally meant, "found sounds", niche samples, and other kooky sounds, but I do think I could replicate some of the .ds sounds

@SirBothersome
Copy link
Contributor Author

Closing. This can be discussed on discord.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants