How do I use "VST" instruments that come in .mse files

[Jinx]

I've already said this (at least once) .... I don't just move the DLL. IF there's an instruments directory, I learned, my very first day using LMMS, that you have to move it, as well. So that's no surprise.

Oh, and just FWIW, the reason I put a lot of stuff in my home directory (C:/jim) is for backups. I don't want to have to be backing stuff up from all over the system, and having to grep out a lot of stuff I don't want (I already have to do that for some stuff, but it's not that much).

[Monospace]

Something Monospace said, makes me wonder.

How did you install LMMS, as admin or as a normal user?

With games on windows the solution is often to run as admin.

It worth a try, as long as you got LMMS from this site.

Gps, it's not possible to install LMMS without admin. Using the 7 zip method- well, I doubt anyone's done that before.
With games, I've found that if you download it officially only, admin is required.
I doubt Jim used 7Zip.

[musikbear]

stuff in my home directory (C:/jim) is for backups.

You need to make this folder:
C:\jim\lmms\samples\VSTinstruments
Place MDA-piano.dll in VSTinstruments
Open LMMS
pull in a Vestige
Click green folder
browse to
C:\jim\lmms\samples\VSTinstruments\MDA-piano.dll
Select it
Press a key

When you have done that. Report back how that test went
I will wait for your reply, on that specific test

[Jinx]

> You need to make this folder:
> C:\jim\lmms\samples\VSTinstruments

No, I don't. That is NOT what I have configured in Settings-->Directories.
Why would I want to put stuff where LMMS is NOT looking for it and won't
find it? That's just stupid.

> Place MDA-piano.dll in VSTinstruments

It's already there, except it's VSTplugins, not VSTinstruments. I've
never heard of any requirement for instruments to be in VSTinstruments
instead of VSTplugins. So please site link and paragraph in docs,
please. And don't say more about this until you do. Seriously, you go
and on about this, but have yet to back up your arguments with
documentation, whereas I have a working sytem, EXCEPT for MSE files that
claim to be VST (on the web site). Support your arguments; show a link
and pointer to the exact paragraph to back up your arguments. I'm not
kidding here. BACK UP YOUR ARGUMENTS with references.

> browse to C:\jim\lmms\samples\VSTinstruments\MDA-piano.dll

That directory does not exist. I have another directory configured in
LMMS as already discussed here ad nauseum.

would someone kindly explain how the specific path I have configured in
LMMS and use can cause the recognition of MSE VSTs vs VST VSTs to not
work?

Seriously, this endless tirade about my configured paths vs what others
use is getting seriously annoying. And if LMMS doesn't use the paths
that you configure, why was the ability to choose said paths put into the
code in the first place?

I'm not kidding here. I want answers. I keep getting told I need THIS
EXACT path setting. WHY do I need that exact setting? Where is it in
LMMS's code? And WHY is something like that hard-coded when there is a
setting for it? Is this a designed and built-in bug in LMMS?

I am at the point where I'm clearly seeing that I'm not getting an answer
as to why VST VSTs work, and MSE VSTs dont't work. I'm at the point
where anyone saying it won't work if something isn't in a specific
directory (regardless of what I have configured in LMMS) won't work, I'm
likely to blacklist notifications for this topic in my email client and
let it die. Sorry, but this round and round sh** has gone FAR beyond
highly annoying. No one is citing chapter and verse in docs,
somewhere/anywhere. No one is showing any resources to back their
arguments...just stating them as fact. A science/engineering mind like
mine expects documented sources for all claims, especially wild-*ss
claims that don't match the apparent realityaims that don't match the
apparent reality.


--
From my days in 16th Special Operations Wing Intelligence:

AN EXERCISE is a situation in which you stop what you're doing
in order to simulate doing what you were doing so you can show
someone else that you can simulate what you were doing as well
as you were doing it before you were interrupted.

[Monospace]

MSEs are, like I said, simply instrument samples for the VST dll to use. The dll should load the samples correctly, Jim. MSE files aren't VST, the same way .wav files aren't AudioFileProcessor files, just samples AFP loads.
They're supposed to work (in the sense the instruments should load). There is no good reason for why the dll shouldn't be able to load samples on your Windoez if it does on mine.
I already suggested downloading and unzipping (via 7Zip or the like) another version of LMMS (so you don't have to reinstall/uninstall/install), so we can pinpoint whether it's your specific copy of LMMS giving problems, or not. That way, we can figure out whether our course of action should involve changing LMMS' settings or be file-system oriented.
I apologize if we haven't been able to help enough.

[Jinx]

I did that earlier in this thread, making sure I used the version from lmms.io. Sorry, might have forgotten to mention that. No change.

[Gps]

> You need to make this folder:
> C:\jim\lmms\samples\VSTinstruments

No, I don't. That is NOT what I have configured in Settings-->Directories.
Why would I want to put stuff where LMMS is NOT looking for it and won't
find it? That's just stupid.

This vst is confirmed to work for me on Linux.
Mono space confirmed it works on Windows too.

It does not work for you, so there is something at your pc, causing an issue.
Musikbear, and me are wondering if it is because of your diffenrent file structure.

That why he is asking you to use the default file paths, to rule out that is causing the problem.
And yes you would need to change path in LMMS too, so they match.

[Jinx]

I have already commented (at least a few times) that I used the original default paths before, and none of these MSE files worked there, either. I customized my new default paths and nothing has changed...they still don't work. Will anything change now, if I go back to those original defaults, where they didn't work before? What will it change if I go back to those original default paths where, again, these same files didn't work before, either?

I understand that they're working under M$ for other people in those original default paths. But they have never worked for me, whether in the original default paths or my new custom paths. And yes, it probably is something in my computer. But attempting to change back to the original defaults, where we have already determined those files have never worked for me, is, as the saying goes, barking up the wrong tree.

What ELSE could it be that's different on my computer? Could it be some difference between normal Windows 10 and Windows 10 Home? And why do normal VSTs work fine? Shouldn't whatever's breaking the MSEs also break VSTs? Just tossing out ideas here. Maybe the anti-virus program I installed after the free subscription on the original ran out? Maybe how I had to remove Windows Offender (defender) when it kept deleting my stuff, thinking it was a virus or something? Shouldn't matter, but like I said, just tossing out ideas (that I suspect are mostly worthless, but at this point, what else do we have?).

Here's a thought.... Do I need to upgrade to a newer version of 1.2.2, where maybe someone forgot to change it to 1.2.3?

[musikbear]

I have already commented (at least a few times) that I used the original default paths before, and none of these MSE files worked there, either.

MSE-files does NOT work as VST.
I am attempting to get MDA-piano to work on your system.
All my advises has been for that
You have clearly stated, that MDA-piano and all other simple VST-plugins, does not work. That is first step. Before figuring out anything related to MSE-files, we need your system to be able to play MDA-piano, after you have fetched the dll via the green folder-icon

I used the original default paths before

When you did use the original default paths, could or could you NOT use simple VSTs ?

Here's a thought.... Do I need to upgrade to a newer version of 1.2.2, where maybe someone forgot to change it to 1.2.3?

No! 1.2.2 is the stable official release, and it works with VSTs

[Jinx]

> MSE-files does NOT work as VST.

Yeah, I know that. But they are LABELLED as VST on lots of web sites.
I'm not saying that's a good thing, just that it is how a lot of web
sites label them.

> I am attempting to get MDA-piano to work on your system.
> All my advises has been for that

> You have clearly stated, that MDA-piano and all other simple
> VST-plugins, does not work.

No, I did not. I said that MDA-piano and MSE files don't work. I also
made it clear that actual VST instruments DO work just fine.

> That is first step. Before figuring out anything related to MSE-files,
> we need your system to be able to play MDA-piano, after you have
> fetched the dll via the green folder-icon

Well, it doesn't work. And I already have a great piano using Keyzone
Classic's Steinway [grand] piano. So skip MDA-piano and let's try and
find out the real issue now, why don't MSE files work for me?

>> I used the original default paths before

> When you did use the original default paths, could or could you NOT use
> simple VSTs ?

I show the creation date for C:/VSTplugins as 11May21 at 1430,
so that's when I moved from the original defaults. And, for the
(who knows how many times now), VSTs worked both ways, and MSEs did not.

And as I've said repeatedly, yes, VSTs work whether I use the original
defaults or my new paths. It's MSEs that don't work for me (and never
have). VSTs are fine, no matter where I put them, as long as their paths
are configured in settings-->directories. MSEs have never worked for me
no matter where they are.

Here's a thought (that might be a useless one, I'll admit). There is a
samples directory under lmms's main directory (c:/jim/lmms). As samples,
could it be that the MSEs, which are samples, belong there, instead?

>> Here's a thought.... Do I need to upgrade to a newer version of 1.2.2,
>> where maybe someone forgot to change it to 1.2.3?

> No! 1.2.2 is the stable official release, and it works with VSTs

Remember, I was just tossing out potential issues. So that one is no
longer a potential issue, then. So we can remove that one from the list.


--
From my days in 16th Special Operations Wing Intelligence:

AN EXERCISE is a situation in which you stop what you're doing
in order to simulate doing what you were doing so you can show
someone else that you can simulate what you were doing as well
as you were doing it before you were interrupted.