We really should get our shit together

[kaslmineer7999]

we really should stop doing all this cool stuff like slew limiter and what not and get back to the basics.

the only really good sampler in lmms is a midi triggered sampler with only basic features,
it doesn't even have phase inversion.
the sample track thing is really just horrible

we don't have complex routing for plugins in stuff like this for example

we can't use plugins that aren't only stereo in and stereo out

the sample rate is fixed to 44.1 (even though my interface is 48)

there isn't even VST3 support or PDC. (and basically no support for LV2, and no "DAW-native" scripting language here like all DAWs i heard about)

there isn't even a MONO sidechain or aux ports or anything of the sort, or even midi ports for plugs

We should really just slow down everything else and get that type of stuff i described to work before we move on.

note: you can invert the phase with a plug-in that comes with it, but it's a ladspa plugin from swh called inverter, why we need that?????? every software i used has a phase inverter embedded into the track someway or other

[kaslmineer7999]

even FruityLoops 3.0 from 2001 beats this program

[JMii63]

which version of LMMS are you using? Stable (and alpha-1 i believe) is 6 years old. Also it's a FOSS program and those are (in most cases) not industry-grade.

[yohannd1]

I think most of their points apply to even alpha-2 but I agree with your counterpoint here - this project is worked on by volunteers, there's no financially backed team working full-time on this.

[kaslmineer7999]

@yohannd1 I know it's open source and whatever, but if development time is so 'scarce', focus on the fundamentals like PDC, plugin support, routing, etc, instead of making some cool new random plugin or whatever

[yohannd1]

This might not be everyone's priority, though - it certainly isn't mine, for example. I have been mostly working on UI-level improvements & code documentation/refactoring, plus some occasional bug fixes.

[codellmusukwa67-bit]

Yea I get what you are saying but this is a Open source project it has no funds backing the project, programmers contribute in their free time, I have been looking into vst3 through third party open source projects I think it's time I start firstly working on a standalone instantiater

[Jee-Bee]

TLDR: (as a wise men once said) Stop whining, start coding

First, I'm no way involved with LMMS other than that I follow it on the sideline.
That Said, I follow multiple, small, and larger Open source projects. So i think i know some general workflows that exist in most not well supported Projects. What do I meant with wel suported. Basically all projects that where all users work on voluntary basis, Where no / little financial support is, no large organization support it (Red Hat, IBM, Google etc help a lot projects, but still a small minority, and mainly what is important to them...).

Quite often is there a discrepancy in what users (some) users like to see, and what in eyes of the developers is required for a project to go further. I talk in this part mainly about the core developers. Around them, there are always a bunch of developers that are able to do some (small )improvements / features / bugs that they like - but they care (most of the time) less about the general codebase.
For the core developers are other things like following at least as important

• Supported libraries
• maintainability
• Efficiency (incl memory leaks, etc)
• Usability (incl Consistency)
• Off course bugs
• and Security

The developers have to pick their battles for creating an as best experience with the amount of time they have. If you have as a developer 10 hours a week spare time for your project, what are you going to do...

It is really easy to write a comment as what you did! But there in all projects i have seen, not a single one have gained an advantage from it. I don't know if you have children (or nephews etc). What is the last time that you saw a parent after is his child did something wrong You stupid , you already 8 years old - and you still cannot . What a piece of crap are you. Next time i bring you to an orphan home. If you don't do that, why expect that it helps over here...
Besides that, I understand completely the features you are missing. A lot of users do, but on the other hand you over throw some of you requested features.

In situations like these. There are few options:

• I you have let's say $100 000. Give that and for sure you request will be there before the next release. I'm sure about that
• Give what you have. It don't matter if you give them a few dollars and may be a little help by adding a feature request (or search for feature request that request the same and upvote those).
• Start programming your self

And the last part is equally important as the first option!! Just start adding features your self. Choose what features are most easy to start with, or start with most important one. It don't matter, as long as you just start improving it is good beginnning. Bulling over here is really easy, better is try to improve it and ask for help when the feature change don't work as you intended to work. Just be nice!
It helps everybody

[kaslmineer7999]

bro is threstening to drop child at orphange after he cooked with code being 8 year old nephew lore from south park

[messmerd]

the sample track thing is really just horrible

Support for fading is being worked on in #5616 and #7900.
And sample caching is being worked on in #7497.

we don't have complex routing for plugins in stuff like this for example

we can't use plugins that aren't only stereo in and stereo out

there isn't even a MONO sidechain or aux ports or anything of the sort

These are all being worked on in #7459.

the sample rate is fixed to 44.1 (even though my interface is 48)

I believe this can be changed in the settings? Though maybe only for certain backends.

there isn't even VST3 support

There's some work-in-progress VST3 support in a development branch, but the work needs to be revived

basically no support for LV2

Support has been improving with several bug fixes and support for additional LV2 extensions in the past few years.
And an LV2 UI is being worked on in #7201.

no "DAW-native" scripting language

Earlier this year, someone was working on a text-based melody editor using the Alda scripting language, seen here.

[kaslmineer7999]

the 44.1 fixed thing can't be changed

[Monospace-V]

I will also mention that there is a "native" way to invert the signal, and that's the Stereo Matrix effect that comes with lmms. There have been requests for an "invert phase" button to be inbuilt to the sample track before, though, but you point out that there is no daw-native way to do this, and this is wrong. There have been requests for most of the features you've requested. I wish you'd as much as looked this up to learn about them being worked on before telling the developers to put even more effort into the program.

Bit of a rant ahead regarding your requests:

You talk about getting back to the basics and then bring up examples of supporting whole new external plugin standards, changing the way audio works fundamentally, etc.

LMMS as an open-source DAW is worked on by whomever wants to work on it. If a developer wants to work on a slew limiter distortion, and it works well, there is no benefit in not accepting the pr.
I also feel personally that a distortion is a pretty basic effect and every DAW should have one.

Developers work on what they wish to work on and think they can deal with. The developer who wrote the slew distortion plugin would never have bothered to work with any of the things you're mentioning. Many developers working on bugs and minor features now are not familiar or planning to get familiar with supporting VST3. There's developers starting to get familiar with certain parts of the program where it's pointless to ask to "slow everything down" for learning another part. There are efforts on some of the things you've mentioned, but it seems you haven't searched for the PRs or looked into what work is being done to support them- just made a discussion talking about a list of features you want while simultaneously arguing that they are more important than other features that exist or are being worked on actively.

Who are you talking to, then? Which of these handful of individual persons are you telling to "get [their] shit together" and work on something they don't bother about or want to that much, or that they don't have the time to learn from scratch for? There are several things being worked on, and it's easy to slow down on these big features as other priorities are easier to reach and there is discussion or learning to be taken on big features.

We have had developers working on these issues in their own time as they feel convenient.
However, every developer is a whole person working on LMMS of their own volition in their own time. A lot of them have things like school or jobs and limited time. When you make statements like "let's get our shit together" and point out individual (exceptional) plugins to say we "really should stop doing all this" and "slow everything down" on the things developers have chosen to put effort into and prioritize, you're talking to a bunch of people who are contributing what they care about and are capable of doing to a program they care about. These statements aren't useful and it is not necessarily reasonable to expect collective dev effort on things you point out just because you (or even a lot of people!) want these features.

Our more experienced devs, including the ones working on the features you've requested, are busy often (education, job, family) and have many many other things to do even in LMMS.

But every single one of our developers is just a user who cared enough to contribute to the code. Some of them even cared enough to learn the language from scratch so they could contribute to things they wanted development effort on.
Do you care enough to learn and contribute? Or do you only care enough to tell people to prioritize features you care about? You seem unfamiliar with even the nature of development.

[Monospace-V]

I want to mention I'm not expecting you to develop or contribute. There's a search button to look into the progress of various PRs and features, and if you want more information about progress you only have to discuss and ask. I do wish more users did this instead of creating whole new topics to list the features they want.

[kaslmineer7999]

stereo matrix is still a step dangit. why is phase inversion a plugin (even if daw native) instead of a function of the track itself

[Monospace-V]

stereo matrix is still a step dangit. why is phase inversion a plugin (even if daw native) instead of a function of the track itself

Because nobody has added the feature yet. You could. It's been requested a lot before.

[kaslmineer7999]

well I have no idea to write in cpp

[JJCUBER]

well I have no idea to write in cpp

Well, there's no better time to learn than now!