by
Jinx » Sun May 23, 2021 6:34 am
> Ok so the working-directory is
> C:\jim\lmms\
For LMMS, yes, that's true.
> For the file structure to be normalized -eg
> C:\Users\username\Documents\lmms\samples\VSTinstruments
> You need to make this folder:
> C:\jim\lmms\samples\VSTinstruments
Show me where VSTinstruments is in the Settings-->Directories, or
in the documentation on lmms.io. Provide the direct link to the
chapter/section, please.
> In that folder you can can have any subfolder you like f.i.
> C:\Users\username\Documents\lmms\samples\VSTinstruments\Synth1
> Inside Synth1, you should then have all the subfiles that synth1.dll
> depends on! That goes for your non-functional VST too
Well, once again, I only use Documents for Documents (otherwise, why call
it "Documents"). Again, what's actually DOCUMENTED in the documentation
AND in Settings-->Folders is VSTplugins, NOT VSTInstruments.ND in
Settings-->Folders is VSTplugins, NOT VSTInstruments.
> ALL FILES inside the Zip MUST be in a folder in that structure that it
> unpacks in!!!
Uh huh. I know that. Have for quite some time.
> But you can also have single VST-instruments dll directly in the folder.
> F.i. C:\jim\lmms\samples\VSTinstruments\MDA-piano.dll
What is F.i.? Never seen that one. Also, it's
c:/VSTplugins/mda-piano.dll, not what you're saying I have.
> That is also fine, but ONLY if the VST-instrument is a single dll-file,
> just like MDA-piano
> Oki do that, and test again
Do WHAT? My directory structures, as I have CONFIGURED IN LMMS, ARE
FINE. They work for VSTs that are actually .vst files.
So, I want you to answer this question before you go on about moving
stuff around. Why does LMMS let you configure where (i.e., the path to)
different things if none of what you configure will work, and you must,
instead, you the original "factory" settings whether you like it or not?
Answer that. Also, show me where (provide the link) in the documentation
on lmms.io it says that despite the fact that LMMS let's you configure
your own paths to specific stuff, using the Settings--->Directories
screen, that you can't actually use the configuration that you put in
there, and must instead use the "factory" default. Please provide the
direct link to that chapter/section in the documentation on lmms.io.
Don't ask me to move stuff around again until you provide those links to
prove to me that using what I've configured in LMMS will not work because
that section of the settings is only for looks, and is not actually
functional. Good luck with that.
> Remember to get MDA-piano and NOT MDA-epiano
Yep, that's what I have been testing all along, and have said so over and
over again.
This thread is going in circles at this point. I do believe the answer
for why .mse files aren't working has already been given. They may be
called VSTs by VST sites, but they aren't VSTs, they're sound sample
files. Why the .dll files don't make those work, I don't know, nor am I
going to try to fix that (let whoever calls .mse files VSTs fix those or
fix the description...MSE instead of VST).
So until I see some actual documentation from lmms.io, proving to me that
LMMS lists settings for directories, but those are only there for looks,
and don't actually do anything, I'm out of this thread. It's gone beyond
the absurd, and just keeps looping right back to the same idea, that LMMS
has settings for directories that aren't actually used, and you must
still, contrary to where you've told LMMS to look, still use other paths,
i.e., the ones originally defined. Link, please.
Oh, and since, apparently, those settings are only for looks, why are
they even there? Why would a group of open source devs put something
like that in there and not use it?