ReaMenus - the better menu set

[Kundalinguist]

I use keyboard shortcuts for much of my work in Reaper. But when going to the menus, what I like is that this system gives me an instant bearing; a sense of direction relative to the task that I have in mind. Subsequently, I don't mind that they are nested menus when I only use them to find something. Doing so is now that much quicker. And again, the aesthetic is valuable, too.

[Thuneau]

I just wanted to say "Great Job". These menus are making Reaper a little easier to use and give it a more polished/pro look.
+1 on making them the default set in the next major version.

[musicroom]

Originally Posted by JHughes

Attached is ReaMenus #003.zip (18.4 KB) for those with issues.

Thank you for adding this attachment "003". I am trying to download 004 and I am still getting version 002. ????

Can someone help?


Thanks

[musicroom]

Originally Posted by musicroom

Thank you for adding this attachment "003". I am trying to download 004 and I am still getting version 002. ????

Can someone help?


Thanks

Never mind - I downloaded the file fine using another browser. Some reason, Chrome was downloading 002 no matter what.

[liteon]

just realized i don't know know how to change the menus...
but nicely done!.. :-)

here are some notes (ReaMenus #004):
- i think the "disabled text" entries above a menu section can be bit confusing. i guess since none of the software that i've seen/used have such (e.g. photoshop, flash, corel, ms office etc)
- cannot find the theme change entry in the options menu. might have missed that.
- file menu "open project template" has also an entry "save project template"
- the edit menu should include the take, group, item processing actions as well imo


---

[Mike21]

Turned a rather cumbersome set of menus into something a lot more intuitive and user friendly. I'm a relative newcomer to Reaper and DAWs in general but the menu strudture was one of the primary "ughs". I agree, this should be incorporated as the default, or at least a built-in choice for newbies like myself.

Thanks again, great work!

[bobby yarrow]

This is very nice work, thank you!

Meanwhile, the change in the main tool bar includes 2 icons that are a mystery to me, "full view" and "bus view" if I remember right. They don't seem to do anything in my projects. What's the feature that I'm not using?

[Mike Stop Continues]

Originally Posted by bobby yarrow

This is very nice work, thank you!

Meanwhile, the change in the main tool bar includes 2 icons that are a mystery to me, "full view" and "bus view" if I remember right. They don't seem to do anything in my projects. What's the feature that I'm not using?

The Main toolbar was an accident in the previous version of ReaMenus (#003). You can restore it to the default or customize it as you see fit. I'm sorry very about that!

[Mike Stop Continues]

Originally Posted by liteon

- i think the "disabled text" entries above a menu section can be bit confusing. i guess since none of the software that i've seen/used have such (e.g. photoshop, flash, corel, ms office etc)

FL Studio employs this feature. The reason to have them on the top is that even the items on the top of them menu need to be organized.

Of course, on this and anything else, if more voices call for change, I'll change it. Perhaps it will only take a little while for you to warm up to them.

Originally Posted by liteon

- cannot find the theme change entry in the options menu. might have missed that.

Options->Display->Themes

That's one triple-deep set that I am most definitely not happy with. I'm still waiting on some more votes about the placement of options -- if they should be only in the context menus to which they apply, then the Options menu will be freed up and I can break the Display sub-menu open. On the other hand, how often do you change REAPER's display settings? Themers don't even use that them menu when it's so easy to ctrl+shift+PgDn

Originally Posted by liteon

- file menu "open project template" has also an entry "save project template"

The same thing with Insert->Track from template->Save track template...

The conundrum left me feeling like it was probably better to keep the template functions together than to split them up. Remember that those handy menus also list the templates (in most places--reaper problem with their generative lists).

Again, if some more people don't find this way more intuitive, we'll keep it this way. I'm inclined to join with the community preference.

Originally Posted by liteon

- the edit menu should include the take, group, item processing actions as well imo

I've never found my mouse far from a track when I was editing a track, far from an item/take when I was editing an item/take, or far from whatever was being grouped. One of the main philosophies of ReaMenus is to bring as much into the context menus as possible, so that you rarely ever have to go to the main menus. After all, that isn't where the action is.

[AdamWathan]

Originally Posted by Mike Stop Continues

FL Studio employs this feature. The reason to have them on the top is that even the items on the top of them menu need to be organized.

Of course, on this and anything else, if more voices call for change, I'll change it. Perhaps it will only take a little while for you to warm up to them.

I agree with the idea to remove the labels personally. All the related functions being grouped together is enough to make it obvious what is going on in that area of the menu. The greyed out labels do throw me off quite a bit and make me think there is some disabled option or something at first glance, they also add a significant amount of length to the menus.

The same thing with Insert->Track from template->Save track template...

The conundrum left me feeling like it was probably better to keep the template functions together than to split them up. Remember that those handy menus also list the templates (in most places--reaper problem with their generative lists).

Again, if some more people don't find this way more intuitive, we'll keep it this way. I'm inclined to join with the community preference.

I agree with removing them if possible, however in my tests it can't be done. As soon as you remove that option from the submenu, the submenu no longer actually displays the list of project templates :/

[Mike Stop Continues]

Originally Posted by AdamWathan

I agree with the idea to remove the labels personally. All the related functions being grouped together is enough to make it obvious what is going on in that area of the menu. The greyed out labels do throw me off quite a bit and make me think there is some disabled option or something at first glance, they also add a significant amount of length to the menus.

I infer that you mean all the labels, not just the top ones, right?

Is there anyone who specifically wants the LABELS? If not, there will be no gray labels in #005.

[jazzmandan]

Originally Posted by Mike Stop Continues

Is there anyone who specifically wants the LABELS? If not, there will be no gray labels in #005.

I like em, keeps things organized, which is really the overall objective, right?

[nicholas]

Originally Posted by Mike Stop Continues

I infer that you mean all the labels, not just the top ones, right?

Is there anyone who specifically wants the LABELS? If not, there will be no gray labels in #005.

Personally I like them, I think they add clarity to the menus and help act as a sort of roadmap.

[AdamWathan]

Here's a version with no labels in just the top menus because I couldn't be bother to do all of them... Test the waters with it, I think even the guys who like the labels are going to find they can navigate just fine without them and that the organization is implied just fine without them.

http://dl.dropbox.com/u/3616293/ReaM....ReaperMenuSet

[Sound asleep]

Originally Posted by nicholas

Personally I like them, I think they add clarity to the menus and help act as a sort of roadmap.

I like them as well, but i'm not 100% in love with them. i think if they weren't capitalized then they'd have to go, it's a shame that they must be the same color as disabled text. I do find it annoying how much they look like disabled text, but i'd rather have them in than out.

on another note...

one thing i noticed was in the file menu the 'save project as template' option was hidden inside of the 'open project template' folder. which is confusing, and took me a little to find. i find it is better suited at the bottom of the 'save...' section.

[Sound asleep]

Originally Posted by AdamWathan

Here's a version with no labels in just the top menus because I couldn't be bother to do all of them... Test the waters with it, I think even the guys who like the labels are going to find they can navigate just fine without them and that the organization is implied just fine without them.

http://dl.dropbox.com/u/3616293/ReaM....ReaperMenuSet

Originally Posted by Sound asleep

I like them as well, but i'm not 100% in love with them. i think if they weren't capitalized then they'd have to go, it's a shame that they must be the same color as disabled text. I do find it annoying how much they look like disabled text, but i'd rather have them in than out.

on another note...

one thing i noticed was in the file menu the 'save project as template' option was hidden inside of the 'open project template' folder. which is confusing, and took me a little to find. i find it is better suited at the bottom of the 'save...' section.

I stand corrected, upon trying the version without labels, i prefer the menus with the labels omitted i think. it's cleaner, the menus are shorter, and the divider lines i find are sufficient to categorize stuff. especially as you get to know the menus and know where to expect stuff. plus you don't get any disabled text confusion.

[nicholas]

Originally Posted by AdamWathan

Here's a version with no labels in just the top menus because I couldn't be bother to do all of them... Test the waters with it, I think even the guys who like the labels are going to find they can navigate just fine without them and that the organization is implied just fine without them.

http://dl.dropbox.com/u/3616293/ReaM....ReaperMenuSet

Thanks for this Adam. I find that even without the labels these menus are still better than the standard REAPER ones ... but still prefer them with labels for the clarity and understanding they bring.

[BenK-msx]

Originally Posted by Mike Stop Continues

I infer that you mean all the labels, not just the top ones, right?

Is there anyone who specifically wants the LABELS? If not, there will be no gray labels in #005.

personally i like the labels in most places but maybe the ones in file and edit main menu are not that necessary and couple of others could be dropped but overall i think for a newcomer they help alot and for an oldy don't irritate or slow you down, so best keep em?

and also is there a consensus on whether the extension stuff should be integrated to rest of menus instead of/as well as being in its own extension menu?

[nicholas]

Originally Posted by BenK-msx

and also is there a consensus on whether the extension stuff should be integrated to rest of menus instead of/as well as being in its own extension menu?

Interesting question.

As far as functionality is concerned, it makes perfect sense to integrate them ... but as long as the SWS, S&M, etc. extensions have their own identity and are distributed as a separate entity from REAPER, financed separately by donations, etc. there could perhaps be issues with that.

[Sound asleep]

Originally Posted by nicholas

Interesting question.

As far as functionality is concerned, it makes perfect sense to integrate them ... but as long as the SWS, S&M, etc. extensions have their own identity and are distributed as a separate entity from REAPER, financed separately by donations, etc. there could perhaps be issues with that.

ya, i think it would be cool, but maybe we shouldn't do that, particularly if it's going to be packaged with reaper.

maybe we'll need to have two sets of menus one with and one without headings. i think once all the kinks are out, i'm going to make a headingless menu piece by piece over time. or if someone else does, i'll love you forever and ever.

[BenK-msx]

Originally Posted by nicholas

Interesting question.

As far as functionality is concerned, it makes perfect sense to integrate them ... but as long as the SWS, S&M, etc. extensions have their own identity and are distributed as a separate entity from REAPER, financed separately by donations, etc. there could perhaps be issues with that.

i think the case for (yet another) optional set with integrated extension stuff would be the logical answer. if a little 'bitty'.

it could be bundled with the extensions by the extension people (e.g."you've got the actions now get the menus!!")
i'd guess to integrate the extension actions to what mike has done here is not so hard, and would be pretty easy to then update either by the extension guys or their enthusiastic forum worker monkeys.

given that reamenus is a seperate entity which 'requires' the extensions at the mo i don't think its problematic. if it were to 'go native' then thats another tale

[nicholas]

Originally Posted by Sound asleep

maybe we'll need to have two sets of menus one with and one without headings.

That suggestion makes perfect sense to me.

Mike, can I suggest that if you leave the headers in for now, when you get this to a stage where any kinks are ironed out and you're ready to go with "the real deal", then someone could go through it and produce a headingless (new word ) version.

If you don't get any other volunteers, I'd be more than happy to do that.

[Mike Stop Continues]

Originally Posted by nicholas

Interesting question.

As far as functionality is concerned, it makes perfect sense to integrate them ... but as long as the SWS, S&M, etc. extensions have their own identity and are distributed as a separate entity from REAPER, financed separately by donations, etc. there could perhaps be issues with that.

Much of the SWS functionality is already spread throughout the SWS menus. If it came down to ReaMenus being put into the core, I would definitely pull all the SWS stuff out.

As far as integrating the entire extensions menu into the other menus, it CAN be done. On the question of should it be done (some of that stuff is pretty esoteric), we'd need some more votes.

The thing is, I can't actually REMOVE that menu, nor the 100% redundant Insert menu (every function is a duplicate). I could only empty it.

As far as the LABELS, so far we have 3 votes for and 3 votes against by my count.

[BenK-msx]

perhaps the more obvious extension options could be integrated,e.g im looking at all the 'items' related stuff and thinking that could just go in the item context (maybe in its own 'extension' submenu to differentiate from native options?)- leaving the more wacky in the space left in the extension menu.

i know its a call on what the majority figure is best - but thats my thought

[nicholas]

Originally Posted by Mike Stop Continues

As far as the LABELS, so far we have 3 votes for and 3 votes against by my count.

... and I suspect that whatever comes out of this thread will reflect the opinions mostly of hard core REAPER tragics (like me ) rather than the broad user base, most of whom don't spend time hanging around forums.

That's what makes the two menu solution so appealing ... I suspect that the majority in this thread will probably come out in favor of no text, whereas more occasional users (who aren't even aware of this debate) would probably prefer the text.

Like I say, if it helps, when you're nearly ready to go "live" I'd be more than happy to spend the time editing out the text headers for you, so that you can present to the world a "standard" and "streamlined" version (or whatever you care to call them) ...

[JHughes]

I say leave the labels, as removing them is a possible optimization best saved for last. If they were narrower they could take up much less room, and if they were a different color it might help. I suppose that's a feature request.

But removing them now before everything else has been fleshed out is a rush to judgment and puts the cart before the horse IMO. There is plenty of room now, it's not like there is overcrowding and room needs to be freed. That after all was the very first problem you solved!

You have to be careful because I think some of these suggestions if implemented (like removing submenus) leads you right back to the original menuing system. A good point was made earlier that hotkeys are the solution to submenus. I'm no power user but the submenus have not yet served as an impediment to me. And the labels clarify things and are very logical, which frees my brain from stress.

The best solution then has already been mentioned, to have a choice of menus with and without labels, but I don't see all this as Mike Stop's responsibility. He will have his hands full keeping up with new menu items with every revision.

If you build it, they will come, and then complain about it. lol

[AdamWathan]

I'm going to edit out the rest of the labels when I have time just for my own use, I'm happy to post it when it's done for anyone who would prefer it labelless.

I do agree though that while on development it definitely doesn't hurt to leave them there while everything gets finalized, and it definitely will help new users.

What might be really neat is just a general preference in Reaper for "display labels in menus" that could e checked or unchecked based on preference. We'd only need one menu set then

Idea for the redundant "insert" menu, why not retitle it and bring some somehow related functions out of the other menus to put there instead?

[JHughes]

Originally Posted by AdamWathan

I'm going to edit out the rest of the labels when I have time just for my own use, I'm happy to post it when it's done for anyone who would prefer it labelless.

You and nicholas can race!

Originally Posted by AdamWathan

What might be really neat is just a general preference in Reaper for "display labels in menus" that could be checked or unchecked based on preference. We'd only need one menu set then

That's a perfect idea!

[musicroom]

Mike - again thank you! I already really liked Reaper on its' own, then added SWS extensions (very cool) and now these improved menus - wow! Makes for a very strong DAW workflow!! I feel like I am discovering new features - ok I am discovering new features which leads me to this:


What are "Window Sets" "Track Sets" and "Arrange Views"???

I know what Screen Sets and Snapshots are... but...

I searched the Reaper and SWS manual and didn't find reference to these.





Thanks to anyone that answers this.

[tonecarver]

Originally Posted by Mike Stop Continues

I infer that you mean all the labels, not just the top ones, right?

Is there anyone who specifically wants the LABELS? If not, there will be no gray labels in #005.

I like the labels too. I vote to keep them in.

[vicenzajay]

Originally Posted by jazzmandan

I like em, keeps things organized, which is really the overall objective, right?

Like them....they help set off each category nicely

[musicroom]

Originally Posted by tonecarver

I like the labels too. I vote to keep them in.

+1 for labels.

[Sound asleep]

if the insert menu is redundant and renamable then that idea previously mentioned to edit the name and fill it with something else sounds pretty good. the question is, what? maybe another menu that can be removed?


also,

I mentioned it once before, but then thought i was mistaken, but i wasn't...

ya, when you right click a track in mixer view there used to be a 'bypass FX chain' option which was checkmarked, so you could quickly bypass and unbypass the chain, and this was the real bypass that removes the stuff from cpu drain, so i found it very useful.

anyways it's not there anymore, there is a bypass fx chain 'one way' button in the bottom folder but the toggle option is missing.

so, that and the save as template being in open template drop down folder rather than with other save options are the only issues i've come across so far.


I like how the menus are also distributed separately. maybe we could split the work of making the headingless version.

[nicholas]

Originally Posted by musicroom

What are "Window Sets" "Track Sets" and "Arrange Views"???

I believe that "Windows Sets" and "Track Sets" most likely refer to the two types of Snapshots - Track View snapshots (per project) and Windows Snapshots (global).

The term "track sets" is sometimes anbiguously used to refer to "visibility snapshots" - track layout selections that can be saved and recalled in the SWS Track Manager and Snapshot Manager.

Arrange View is a term that basically refers to REAPER's main view .

[nicholas]

Originally Posted by JHughes

You and nicholas can race!

Nay, I'm more than happy to leave this one in Adam's capable hands.

[musicroom]

Originally Posted by nicholas

I believe that "Windows Sets" and "Track Sets" most likely refer to the two types of Snapshots - Track View snapshots (per project) and Windows Snapshots (global).

The term "track sets" is sometimes anbiguously used to refer to "visibility snapshots" - track layout selections that can be saved and recalled in the SWS Track Manager and Snapshot Manager.

Arrange View is a term that basically refers to REAPER's main view .

Thank you my friend!!!

[nicholas]

Just one more small thing ...

The envelopes context menu seems to be missing the toggle command to show envelope in lane, also to hide envelope.

Don't know about anybody else, but I use these all the time, especially show in lane.

[vicenzajay]

Originally Posted by nicholas

Just one more small thing ...

The envelopes context menu seems to be missing the toggle command to show envelope in lane, also to hide envelope.

Don't know about anybody else, but I use these all the time, especially show in lane.

This is extremely important to me as well...

[EvilDragon]

I say make two versions, one with and one without the labels. And it might be a good idea to lowercase them, to comply to "Custom Actions:" in the Actions menu. Yeah, all labels should be formatted like "Label:"


BTW, #004, you still have Auto-Color in media item and MCP context Also, one more thing: in MIDI editor menus, "sysex" should be "SysEx", to hint that it's short from "System Exclusive"

Also, I like the idea of separation of Save/Load type of actions to next sub-level. You could do the same with Selected items.

[technogremlin]

Maybe a few ideas to have the labels stand out more as a 'label':

[LABEL]

--- LABEL ---

:: LABEL ::

Or maybe a combination:

--[ Label ]--

I like the one with the double colon best, looks clean but certainly not as a menu entry. I'm using that one for my own menu set