LMMS • Forums

After removing both, I now re-installed both.

When checking wine (64bit) yast automatically added win-32bit. Don't know which version is used by lmms.

Lmms is 1.1.3, i now can confirm. I installed the one from packman.

The result of re-installation is: nothing changed.

Slightly off-topic: That's what I like about linkux, too. But at the same time it regularly makes my head fume and myself dizzy...

Just tried to start carla from command-line. Doesn't work either. Horrible messages. Let's not talk about it...


@musikbear

I'm so glad you mentioned that the avatar is no rule. I really felt a bit under the gun by it. Guess I took it too serious

Just to make sure, what the problem is. Found this pic on the net.
You don't have Vestige like in the picture on the left ?
Were the drag arrow starts. (not were it ends)
Under instrument plugins



If so we need to talk to packman.

http://wiki.links2linux.de/packman:faq_ ... _a_package

What if I have troubles with a package?

Simply send an E-Mail with the exact error description to the Packman mailing list: packmanATlinks2linux.de
If you do not know exactly which information about your system is needed? Point out at least your SUSE version and the package name and the version.

Replace AT with @.

Thanks for taking all those pictures for me.

No, I don't have Vestige there like you do.

I once downloaded a VST plugin named mdaPiano. When I try drag&drop the mdaPiano.dll into the song editor, a window pops up containing this message:
But that's no surprise though, since it couldn't work without the vestiges plugin.

I just sent an email to the packman mailing list. I'm curious what will happen now.

Now we wait for them to fix

I am expecting an answer soon.

No answer yet.

Here's a little update on what I tried in the meantime:

I recently got an issue with Mozilla, that I could fix by replacing libavcodec with the one from the packman repo (I was brought to this idea here in this thread). Then it came to my mind that maybe there are some libs or other stuff in my system that needed to be replaced with the respective packman versions. So I opened yast and chose the option "switch system packages with the version in this repository (packman)". It took a little while to complete. Some packages were upgraded, some even downgraded. Others were simply replaced. But in the end it changed nothing to VST in LMMS.

Crawling through the net I read at some place that one user had similar problems. Though it dates back to 2015. But he told that VST worked with an older version of wine, while the newest version (back then) caused problems. I was tempted to try the version he mentioned there (afair it was 1.7.x while mine was 1.8.x). But I shied away from it.
Instead I intalled the wine repo from http://download.opensuse.org/repositori ... Leap_42.2/ and re-installed wine from there. That lead to an upgrade to version 2.3-643.1-x86_64. Removed LMMS and re-installed it. But it, too, changed nothing.
There is also a version available named 2.3-643.1-i586, but that seems not appropriate to me for a 64bit system.

Which wine version are you running, Gps?

OffTopic: look, my avatar

EDIT: Now I gave it a try with the i586 version. But t no avail.

Everytime I de-install LMMS I get this messages in the log: Don't know how relevant this is.

EDIT2:
Now I see your wine version from your image on page 1. That's the same version I was running (without success) before I switched to the one from the Wine repo.

Nice Avatar.

I am a bit disappointed they have not responded yet.

I am expecting you to get an update on lmms ( and everybody else on 42.2 ) That's what happened when I had emailed them.
They did how ever also respond to my email.

Yeah. But the question arises, when you and me are running the same OS with the same versions of the progs, why do I have these problems, but you don't? Maybe there's just something wrong with my configurations at a place we don't oversee at the moment.

Have you done something with your wine before starting LMMS for the first time? Some sort of configuration thing, setting a working directory or downloading some dll's and inserting them by hand, or stuff like that?

EDIT:
Does your output from "lmms -v" differ from mine?
(i'm most interested in the numbers between the brackets in the second line)

Looks like its exactly the same.
I am pretty sure I did not do any setup on wine.
The first time I use vst in lmms though, I always see wine doing some set stuff.

I am also very interested in why there is a problem with lmms on youre site, but they only people who can help us, are the experts.

The openSUSE forum is another good place were we can try but, most there don't know what lmms is.
Another option might to install the lmms debug tools, but I do not know how to use them.

If I remember right, it took them 3-4 days to respond to me.

I ones had the same problem though on opensuse13.1 if I remember right.
I took some time, longer then I liked but it got fixed. ( week or two in total )
A few days after they said they fixed it, I got an update for lmms.

Ah, now I got it. You run Leap 42.1, while I am on 42.2. There's the difference. Ok, then it indeed seems that only the experts can tell.

At an other place I read to set a symbolic link from /usr/lib64/lmms to /usr/lib/lmms. I did it.
At another other place I read that you have to run winecfg and assign a drive letter (i.e. D: ) to the lmms directory. I did that, too.

So I keep waiting for the packman crew to answer.

Yes I am on 42.1.

I was hoping you would tell them it works fine on 42.1.
That might have made it easier for them to find the problem, but for now lest wait to lest say thuesday.

If you don't get a reply, I will see if I can get them to reply.

How to explain.
The packman guys are not an official help desk. The email we send goes directly to the people building the packages.
Great people but some times they need a friendly reminder.

A bit offf topic,
I have fun memories contacting them. At one point, one apologized to me, that it took him so long to fix it.
He had just become a dad, and was not getting the sleep he needed.