Quote:
Originally Posted by schwa
There is limited dynamic menu space available, partly for technical Windows reasons. I think the layout space is limited to 300 entries, and the track template space is limited to 100. Are there any limits that are causing a critical workflow issue?
|
Apologies for just getting back to you. Thank you for clarifying on what is happening within the menus. To answer your question, yes, the truncation actually presents workflow issues with large, intricate setups. There are some possible workarounds... so I am not sure I would consider it "critical" - but the issues the truncation creates causes major workflow issues for your film score/orchestral composer user base (even with the workarounds). Admittedly this is probably a small portion of your overall user base, but these are also the power-users that have come to utilize all of Reaper's strengths in a professional market.
For one truncation example, with OTR, I removed the various track prefixes/suffixes that allowed for much of the automation in the OTR template workflow by moving the prefix/suffix combinations into a custom theme's TCP and MCP layouts. This allowed users to not rely on the clunky track name method for automation, but rather allow for it to happen behind the scenes. However, due to the sheer number of TCP and MCP layouts included in the theme (most are used behind the scenes in the scripting), the Reaper menu truncates the layout options... so there is no TCP/MCP layout control from within Reaper. Not critical, but it limits any theme customization to custom-built menus.
Additionally, many orchestral composers are using large templates... typically in the 1000-3000 track range. To keep the processing down, track templates are utilized with a right-click->insert template command. But, having a large number of track templates causes the Reaper menu system to become truncated and unusable. Instead, users have to drag-and-drop from a folder into the Reaper project.
These are a couple of examples. They aren't grave issues, but they are certainly inconveniences for power users that rely on 1000+ template workflows. Hope this helps clarify.