LinuxMusicians

I'm not able to find any useful information about the velocity of notes created with the draw tool in the drum editor. In the list of keyboard shortcuts, there are the shortcuts V/B/N/M, but they don't have any effect. All notes created are created with velocity 110. No shift, no control, no nothing.
Where can the 4 velocities be configured? Perhaps the are all set to 110? I found this in the configuration file, but it does not help:
Actually, these default values are weird and useless. Do I have to edit this file before starting MusE? Isn't there any dialog to set these values?

I'm new to MusE (3.1.0) and I must say that I have more problems with the basic editing functions than I have with the tracks and the routings. The lack of documentation and the "loveless" implementation of the really important functions make me think about another DAW. Btw; Reaper is not on the list because ... the drum edtitor is completely missing. 1:0 for MusE.

dailybug2 wrote: ↑Fri May 15, 2020 4:54 pm I'm not able to find any useful information about the velocity of notes created with the draw tool in the drum editor. In the list of keyboard shortcuts, there are the shortcuts V/B/N/M, but they don't have any effect. All notes created are created with velocity 110. No shift, no control, no nothing.

From the Manual (https://github.com/muse-sequencer/muse/ ... he-editors):

"Prior to drawing new drum notes, press:

Ctrl + Meta: Draw with velocity level 1.
Meta: Draw with velocity level 2.
No keys/buttons: Draw with velocity level 3.
Meta + Alt: Draw with velocity level 4.
"

You can also edit velocities in the midi controller graph area (below the notes).

The Manual can be found by pressing F1.

dailybug2 wrote: ↑Fri May 15, 2020 4:54 pm I'm new to MusE (3.1.0) and I must say that I have more problems with the basic editing functions than I have with the tracks and the routings. The lack of documentation and the "loveless" implementation of the really important functions make me think about another DAW. Btw; Reaper is not on the list because ... the drum edtitor is completely missing. 1:0 for MusE.

I think the MIDI editing in MusE is great! And that is coming from Reason which has really good MIDI editing tools.

Right now I am working with automation and that works beautifully for me.

So... problem solved, i assume?

One important feature is per-note velocity editing. This question would likely come up eventually
"On the velocity graph, how do I edit the velocities of individual notes that are all at the same position?"
See the square icon at the left of the velocity graph that looks like a mini vertical piano?
That's the "per-note velocity" button.
Click it to show only the velocity graph of the selected note in the piano - the current 'red' selected piano note.
This way you can edit the velocity graph of the individual selected note.
Same for Drum Editor velocity graph.
Click a drum note and click that per-note velocity icon to edit only that note's graph.

Thanks for the roses...
Tim.

Tim E. Real wrote: ↑Fri May 15, 2020 7:00 pm "On the velocity graph, how do I edit the velocities of individual notes that are all at the same position?"
See the square icon at the left of the velocity graph that looks like a mini vertical piano?
That's the "per-note velocity" button.
Click it to show only the velocity graph of the selected note in the piano - the current 'red' selected piano note.
This way you can edit the velocity graph of the individual selected note.
Same for Drum Editor velocity graph.
Click a drum note and click that per-note velocity icon to edit only that note's graph.

Hey, I just saw that small icon today and wondered what it was for! Perfect, thanks!

This is the layout for my current song. Ten instances of Surge, one of drumkv1 and one voice track. As well as FX plugins here and there. And my home cooked dark theme! I am reaching 34% in QJackCtl on a core i5 laptop, so there is room for even more complex arrangements!

Whenever help on a particular topic does not seem to be at hand, look to the closest obvious place - tooltips and WhatsThis context.
I always at least try to put some crucial info in them even if there's no time to write up a help section.
For the four drum editor velocity columns LV*, I put the key combos in the tooltips.

I see that Surge has 666 audio controllers Watch out for that last one, eh?

I know it can be a bit of a hassle with so many audio controllers. The popup menus are clumsy and slower with so many controllers.
I had one VST plugin which had 2048 audio controllers!
It really puts our system to the stress test.

I have long been trying to design a replacement for all those popup menus which potentially may have many items.
It would be more of a mini popup 'tree' widget than a popup menu.
However, the convenience and features of popup menus is a powerful thing to ignore and attempt to replace and duplicate in some other scheme.

Tip: FYI: Hold Ctrl when operating many of those popup menus and they will stay open! It's a great help with routing or patch auditioning.
In Global Settings you can turn that feature on permanently.

Click it to show only the velocity graph of the selected note in the piano - the current 'red' selected piano note.

Oops, sorry that should say the current 'yellow' note.

Thank you for the help! Also a big thanks to kybos for updating the manual/wiki!

Tim E. Real wrote: ↑Fri May 15, 2020 9:20 pm

Click it to show only the velocity graph of the selected note in the piano - the current 'red' selected piano note.

Oops, sorry that should say the current 'yellow' note.

Is the yellow key used for other things as well?
If not, shouldn't it be better hidden in the All-note mode? I must confess I was often not sure in which mode I am from the icon only, so the display of the yellow key could be an additional (and quite clear) mode indicator.
Just an idea...

Well, it shows which row is currently selected, just as a sort of convenience.
Whether to show it in 'all-note' velocity mode is an interesting question.
Probably the first thing to take care of is changing that icon. Yeah, I know, it is very unintuitive right now.
I avoided a 'real' button with borders and margins there due to space limitations and the various styles wanting to draw
their own 'bloated' button shapes.
Maybe I can replace it with one of my 'blue when off' icons for better clarity. Or try to add a real button somehow.

From the Manual (https://github.com/muse-sequencer/muse/ ... he-editors):
Prior to drawing new drum notes, press:
Ctrl + Meta: Draw with velocity level 1.
Meta: Draw with velocity level 2.
No keys/buttons: Draw with velocity level 3.
Meta + Alt: Draw with velocity level 4.

Ummhhh, yes, there it is. I was not aware that the Wiki is more detailed than the - outdated - PDF generated when building MusE from GIT. And I did not expect "Meta" to be involved; I'm using this excessively to contoll my desktop. Definitely the DAW should have preference here because there are sooo many functions to be covered.

Btw; the issue with "hold-controll-to-keep-the-popup-open" is fine once you know it. I found out this one by intuition.

We discussed the documentation.
(BTW It is not generated at build time, it is pre-built and simply installed.)
The PDF and HTML have not been updated in long time.
It is difficult to even update it because the tools necessary and the very tedious editing required.
I mentioned that I would have liked to easily edit it as I went along adding features,
but it was just too tedious to keep it up to date.

Whenever I added something new, I tended to put it in a README for safe-keeping until it could be added to the docs.
You'll see several READMEs with some important stuff.

So that's why kybos recently consolidated all the PDF and READMEs into the wiki.
It should be a bit easier to edit 'on-the-fly'.
But I do worry about how we are going to get it all back into a PDF manual format.

It occurred to me recently that I don't think the "Ctrl popup menu stay open" thing is mentioned anywhere
except in the Global Settings.

Tim E. Real wrote: ↑Tue May 19, 2020 5:32 pm So that's why kybos recently consolidated all the PDF and READMEs into the wiki.
It should be a bit easier to edit 'on-the-fly'.

I think this is the right approach. The wiki is the main source of info.

Why do you think a PDF i still important?

I have had an idea for a while that I would like to do. A how to: "How to make a synth pop hit using MusE". For the wiki?

Why do you think a PDF i still important?

Having a local manual at hand is important. Having none at all would be silly.
Also, I've seen several posts where people said their audio computers are purposely disconnected from the internet.

We provide both PDF and HTML for a reason: There is a Qt API for easy context-sensitive HTML help from within an app.
We are hoping to leverage that feature some day. The API does not work with PDF.

"How to make a synth pop hit using MusE". For the wiki?

I think there are a few links to demos on the website.
Contact Robert if you want to add a link or something.
Or, I suppose any one of us could add a link on the web page or wiki page as well.
The web site code is now a public github project and can accept pull requests.

Tim E. Real wrote: ↑Tue May 19, 2020 9:14 pm Contact Robert if you want to add a link or something.
Or, I suppose any one of us could add a link on the web page or wiki page as well.
The web site code is now a public github project and can accept pull requests.

So a stand alone tutorial in PDF format is acceptable? Or is putting it in the wiki better?

I want to give something back to MusE.

It would probably just be a link, so whatever you want to link to...