View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007657 | MMW v4 | Main Panel/Toolbars/Menus | public | 2011-04-12 20:46 | 2011-04-28 02:28 |
| Reporter | peke | Assigned To | |||
| Priority | high | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Target Version | 4.1 | Fixed in Version | 4.0 | ||
| Summary | 0007657: Column Browser: BPM is not Available | ||||
| Description | It could be useful to be able to show BPM in a tree node. This is especially useful for DJs and in party mode where time to select new song could be much faster. Note: Using BPM tree with InitialKey 0007181 will open MM to completely new experience. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1366 | ||||
|
|
I think that it could rather be something for an Addon. That said, we could implement such a node and make it hidden by default. I wonder though, wouldn't a Column Browser BPM column even more usable (and needed, since a script can't implement it). Btw, Peke, what would be the suggested granularity? Every integer would have a value? Or rounded e.g. to nearest 5? |
|
|
Actually you are right column browser would make things even more detailed in granularity and much better to navigate thrum. Personally that would put Column browser on my MediaMonkey layout perminately. Re Add-on: Not sure what are you referring to, but if you are thinking to make Auto-DJ add-on to mix tracks in MM then look at 0007181 (bug7181 folder on FTP for example mix). That example really show quality that can be accomplished with MM Auto-DJ and MM automatization thru addons like you pointed. |
|
|
Ok, the question is, should BPM in the Column Browser be listed as 120, 121, 122, or rather as 120, 125, 130, etc.? I guess that every single integer is preferable, since user can easily select multiple values in the Column Browser. |
|
|
I would make it more like: |Style(Genre)|BPM Groupng (Steps 10 or 15)|BPM (Step 1 as VPM can be up to two Decimals)| That Way we would get full granularity that is needed by DJ To Easy/Acurate find tracks. In case that 0007181 is added I would prefer: |Initial Key (TKEY)|BPM Groupng (Steps 5 or 10)|BPM (Step 1)| |
|
|
Ok, so we could add this Column Browser BPM field even for 4.0, since it should be very easy and without new strings. For 4.1 we could consider adding it as one more field: - BPM (Nearest 10) |
|
|
Fixed in build 1366. |
|
|
verified 1367 |
