Requests to help a long time user/purchaser to us MM5
Posted: Fri Dec 22, 2023 9:30 am
MM5 is head and shoulders above MM4 in terms of functionality and cool features. Here are my 4 critical show stoppers keeping me on MM4. Please help me transition to a significantly better product.
1. When type in a list, search the list vice assuming user wants to do a search. Two separate use cases here: (1) jump to position in list; (2) search library. How about a global behavior setting? This missing functionality is very impactful for large libraries; we have to scroll, scroll, scroll to find the list item we want to click on. HUGE waste of time.
2. Cannot convert Track # "01" to "1". How about a global behavior setting (auto apply on add/re-scan and list displays) or give us the MM4 script equivalent? Auto increment per Album is a HUGE waste of time.
3. Column layout applied recursively to all sub-nodes rather than having to redo each time we click on a sub node. HUGE waste of time.
4. Location node limited to list of folders (Windows Explorer emulator). Because of this limitation, we have to create a collection using a hard-coded path value to get a list of tracks in a location. How about a global behavior setting (operating system file system emulator seamless with every other node in the product)? We have a workaround but it is clumsy to say the least.
1. When type in a list, search the list vice assuming user wants to do a search. Two separate use cases here: (1) jump to position in list; (2) search library. How about a global behavior setting? This missing functionality is very impactful for large libraries; we have to scroll, scroll, scroll to find the list item we want to click on. HUGE waste of time.
2. Cannot convert Track # "01" to "1". How about a global behavior setting (auto apply on add/re-scan and list displays) or give us the MM4 script equivalent? Auto increment per Album is a HUGE waste of time.
3. Column layout applied recursively to all sub-nodes rather than having to redo each time we click on a sub node. HUGE waste of time.
4. Location node limited to list of folders (Windows Explorer emulator). Because of this limitation, we have to create a collection using a hard-coded path value to get a list of tracks in a location. How about a global behavior setting (operating system file system emulator seamless with every other node in the product)? We have a workaround but it is clumsy to say the least.