LinuxMusicians

Gps wrote: ↑Mon Mar 21, 2022 3:24 pm

tavasti wrote: ↑Mon Mar 21, 2022 7:08 am Take a look on this:
https://www.youtube.com/watch?v=wX1j_rxOwoM

No, this is not how arp should work

Watched to vid and that does not sound right.
I am assuming you already filed a bug report ?

I think the chord option is causing it.

There is bigger bug about arpeggiator open https://github.com/LMMS/lmms/issues/3880 , and discussed a bit in discord. And got feeling that nobody is going to fix it soon.

And no, it is not chord option that is problem. Actually what works is that have single note, and select chord (like major or minor), and put that arpegiating. But how about if you have chord progression which has major and minor chords? Can't do.

It is broken and unusable.

Interesting, so there issues when you use chords in the piano roll.

What can I say, I love LMMS but they definitely need more coders.

If I had anything to say about it, they would start by dropping MAC support.
Although I don't have anything against, macs, there are plenty DAW for mac os, who needs LMMS on a mac?

Then the windows support, if you are limited on the number of devs you have, spreading them out over 3 OS might not be a good idea.

Lets make things worse and fork LMMS, its the Linux way

When LMMS started there were, if I recall right only 3 daw for Linux, LMMS, Rosegarden and Ardour.
These days, and I like to think that is progress there are even proprietary DAW for Linux.

I am also in the Richard Stallman camp though, we want opensource software.
That why I like to watch what UNFA does.

Gps wrote: ↑Tue Mar 22, 2022 1:49 am What can I say, I love LMMS but they definitely need more coders.

If I had anything to say about it, they would start by dropping MAC support.
Although I don't have anything against, macs, there are plenty DAW for mac os, who needs LMMS on a mac?

Then the windows support, if you are limited on the number of devs you have, spreading them out over 3 OS might not be a good idea.

Lets make things worse and fork LMMS, its the Linux way

Indeed, more coders are needed. I like LMMS, but for many use cases is falls short. Biggest flaw is in audio handling, no recording at all and even audio editing options are very limited.

About forking, I don't see that making any sense. Is there something that can't be done because of multi-platform? Forking linux-only LMMS would make sense if
a) there would be many devs that are willing to jump that wagon
b) dropping win & mac support would make many things much easier

Mu assumption is that those conditions aren't true. Sure it is possible to start developing new features and fixes, and if it starts to pile up stuff that is not accepted because 'does not work on platform X', then it starts to look like seeds of forking. Sure forking can be soft, have linux-only branch, maintained possibly in same git or separately.

Yeah no audio editing is definitely a problem.

I do often watch people using any daw, and learn a lot from it.
It sometimes also makes me a bit jealous.

How easy it is in cubase to import a mp3, and then unlike LMMS, you do not have to start the mp3 from the beginning every time just to hear it.
You can even stretch or shrink the audio so it will fit the bpm.

https://www.youtube.com/watch?v=TWt-t5lBIPI

On the bright side, the LMMS devs know about the shortcomings of LMMS.

I already installed git, its a good first step.
Now I need,
qtbase5-dev qttools5-dev-tools qttools5-dev \ libqt5x11extras5-dev libxcb-keysyms1-dev libxcb-util0-dev.
The qt tools used for LMMS.

This is hope full though, a dependency page, for openSUSE.
https://github.com/LMMS/lmms/wiki/dependencies-opensuse

Rumors have it, that the windows version of LMMS gets compiled on Linux.

Just did a gitclone, and now might have to run some qt scripts.

Looking around git hub, found a old gist of mine , LMMS 2015, which I deleted.
Also saw dhewm3 there, that's for compiling/running Doom 3 on Linux.

Yeah, if I would be using LMMS only for my own use, I would try to fix some things. If patches aren't accepted, then I could use patched thing myself. Possibly it would mean something like doing short circuits so that things I need, work, but some other thing maybe broken.

Now I use LMMS to make videos about making music, and in such instructional videos can't use version which has features which don't work in public version, no-go.

tavasti wrote: ↑Wed Mar 23, 2022 8:53 am Now I use LMMS to make videos about making music, and in such instructional videos can't use version which has features which don't work in public version, no-go.

Or you could share your fork of LMMS and link to it in the description

Basslint wrote: ↑Wed Mar 23, 2022 10:01 am

tavasti wrote: ↑Wed Mar 23, 2022 8:53 am Now I use LMMS to make videos about making music, and in such instructional videos can't use version which has features which don't work in public version, no-go.

Or you could share your fork of LMMS and link to it in the description

No, I don't think I want to start maintaining and distributing LMMS builds for all platforms

tavasti wrote: ↑Wed Mar 23, 2022 10:32 am No, I don't think I want to start maintaining and distributing LMMS builds for all platforms

I meant just the sources, of course!

Because of me looking at the files I got through the git clone, I had to start LMMS and listen to my Vangelis Alpha cover for a sec.

Interesting I noticed something. One part of mine is an octave down, compared to the original.

The most shocking part about this is me hearing this.

The original just for information goes out of sync after about 20 seconds. LMMS need time stretching.
Its good enough to hear if I am in tune though, which I am.

Its 95 % finished. It still needs some bends / modulations like the original, which I still have to figure out how to do.

Also some fighting with some instruments to make a better mix.

Tomorrow probably an attempt at compiling LMMS.

I should have all dependencies, after copy pasting the command from the git hub.

Minor issue:
After starting YAST and searching for those files, I am 99% sure I have those files but they are named a bit different.

If not I am pretty sure, I will see compile errors.

to be continued...

Gps wrote: ↑Wed Mar 23, 2022 10:35 pm The original just for information goes out of sync after about 20 seconds. LMMS need time stretching.
Its good enough to hear if I am in tune though, which I am.

I think you can use automation for tempo, so that your own will change tempo same way as original.

That should work, but the problem is Vangelis not playing at a constant bpm

The one time I did not have this problem, was with a instrumental cover of Ice Cube - Ganster Rap made me do it.
( there is that not 4 to floor beat again ) Willing to bet, its because the original Gangster rap made me do it, is made on a computer too.

Progress

I just compiled LMMS 1.3.0-alpha 1.174+g4dc04a612
There is Carla as it should be. and a new synthesizer. Xpressive.

Carla is not listed as a dependency, but I went into yast and installed Carla-devel.

Pretty sure I need that.

Now the qt part to figure out.

Something is annoying me.
I Installed Kdevelop, in the vid the guy uses codeblocks.

Although I got a good C++ tutorial, thanks to the LMMS forum.

https://www.youtube.com/watch?v=vLnPwxZdW4Y

What most or all tutorial are skipping are those first lines. Most say dont bother about those when your starting coding, but I want to bloody know.

#include <iostream>

usingnamespace std;

It seems if I leave it out, my "program" is not working.

(my program)
cout << "the computer is mad"

I already figured out, that you cant like with BASIC run this code. You first need to make it a program and build it.

So now my question:
What are those two first lines, and if somebody can tell me what to google for, I am already happy.

I already tried to google, what is the smallest C++ program, but that did not help me one bit.

I am also having a bit of fun, it does help me big time, I ones learned BASIC.

For a bit of fun:
I am wondering about how many times I am gonna mess this up:
cout <<
cin >> ( and the fact cin is not always followed by >> )