User Tools

Site Tools


cuecolor_proposals

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
cuecolor_proposals [2020/01/24 17:38]
hlzhs Add migration section and information about default colors
cuecolor_proposals [2020/01/25 13:39] (current)
be.ing
Line 25: Line 25:
 ==== Migration ==== ==== Migration ====
  
-Colors with the "no color" state in the database schema currently in master will be set to the new default color. Ideally, this would be "​white"​ since white is not an actual ​color (and thus transports the previous "no color" state) and also looks good in all skins.+Colors with the "no color" state in the database schema currently in master will be set to the new default color. Ideally, this would be color that looks good in all skins.
  
 If a user does not want to use the cue color feature but dislikes the default color and wants to restore the exact cue button color as in previous versions of Mixxx, the color-mass-replace tool can be used to replace the default color with the previous button color of the skin in use manually. If a user does not want to use the cue color feature but dislikes the default color and wants to restore the exact cue button color as in previous versions of Mixxx, the color-mass-replace tool can be used to replace the default color with the previous button color of the skin in use manually.
Line 38: Line 38:
  
 === Cons === === Cons ===
-  * By default, the look of hotcue buttons with previously uncolored hotcues will change (e.g. red hotcue buttons in the LateNight skin will turn white), but the original look can be restored using the mass-color-replace tool (see above).+  * By default, the look of hotcue buttons with previously uncolored hotcues will change (e.g. red hotcue buttons in the LateNight skin will turn to the new default color), but the original look can be restored using the mass-color-replace tool (see above).
   * Would not maintain "no color" state from Rekordbox. However, Rekordbox always shows "​memory cues" (what Mixxx calls "hot cues", although Rekordbox has a different meaning for "hot cue") as orange. That is regardless of the color palette the user has chosen in Rekordbox'​s preferences;​ changing that color palette does not automatically change the colors of cues. It seems that no useful information would be lost if Mixxx converts Rekordbox'​s "no color" to orange when importing to Mixxx. It is not clear why the "no color" state exists in Rekordbox; it may only exist to support legacy CDJs that did not support cue colors. Mixxx currently has no way to export to Rekordbox'​s metadata format, doing so would be technically challenging,​ and no one has expressed interest in working on it.   * Would not maintain "no color" state from Rekordbox. However, Rekordbox always shows "​memory cues" (what Mixxx calls "hot cues", although Rekordbox has a different meaning for "hot cue") as orange. That is regardless of the color palette the user has chosen in Rekordbox'​s preferences;​ changing that color palette does not automatically change the colors of cues. It seems that no useful information would be lost if Mixxx converts Rekordbox'​s "no color" to orange when importing to Mixxx. It is not clear why the "no color" state exists in Rekordbox; it may only exist to support legacy CDJs that did not support cue colors. Mixxx currently has no way to export to Rekordbox'​s metadata format, doing so would be technically challenging,​ and no one has expressed interest in working on it.
   * Would not maintain "no color" state from VirtualDJ. However, VirtualDJ can also read Serato tags, so importing exporting to VirtualDJ'​s metadata format would not be required for interoperability with Mixxx if Mixxx can export to Serato tags. To import metadata from VirtualDJ, Mixxx would either need to assume the color of VirtualDJ'​s "no color" cues or read [[https://​www.virtualdj.com/​manuals/​virtualdj/​interface/​decks/​decksadvanced/​pads.html|VirtualDJ'​s nonColoredPoi setting]] to determine how VirtualDJ would show them. Without Mixxx maintaining a "no color" state, cues imported from VirtualDJ and exported back to VirtualDJ (potentially through Serato tags) would lose the "no color" state and not change colors when the user changes the nonColoredPoi setting in VirtualDJ.   * Would not maintain "no color" state from VirtualDJ. However, VirtualDJ can also read Serato tags, so importing exporting to VirtualDJ'​s metadata format would not be required for interoperability with Mixxx if Mixxx can export to Serato tags. To import metadata from VirtualDJ, Mixxx would either need to assume the color of VirtualDJ'​s "no color" cues or read [[https://​www.virtualdj.com/​manuals/​virtualdj/​interface/​decks/​decksadvanced/​pads.html|VirtualDJ'​s nonColoredPoi setting]] to determine how VirtualDJ would show them. Without Mixxx maintaining a "no color" state, cues imported from VirtualDJ and exported back to VirtualDJ (potentially through Serato tags) would lose the "no color" state and not change colors when the user changes the nonColoredPoi setting in VirtualDJ.
cuecolor_proposals.txt ยท Last modified: 2020/01/25 13:39 by be.ing