Waveform overview does not support pixmaps

Bug #1496952 reported by Hendrik
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Mixxx
Confirmed
Low
Unassigned

Bug Description

Please add support for custom hot cue marker/pixmaps in the overview like the waveform solution below.
The reason is when i define custom hot cue marker for the waveform, i don't see any differences in the overview. Only normal hot cues.

I think this is a first step to fixing similar bugs/wishes.

<Mark>
     <Control>hotcue_X_position</Control>
        <Pixmap>custom_marker.png</Pixmap>
     <Text>HOTCUE X</Text>
 <Align>Y</Align>
 <Color>#</Color>
 <TextColor>#</TextColor>
</Mark>

Edit: Oh sorry, colored hot cue marker in the overview are possible.
I edit the topic to "support pixmaps in the overview".

Hendrik (index82)
description: updated
summary: - Waveform overview does not support custom marker
+ Waveform overview does not support pixmaps
Revision history for this message
Be (be.ing) wrote :

How do you imagine that Mixxx would enable users to set pixmaps for individual hotcues? IMO it seems like this would clutter the GUI and not add much more functional value than colored markers. What do you want to do with pixmap markers?

Revision history for this message
Hendrik (index82) wrote :

Thank you for your comment.

Only skin developers could set individual pixmaps for the marker. Nothing more.
The designer is free to use it or not. Like the solution for the waveform.

The reason why: I wanted to set individual pixmaps as visual helpers.
Most controllers have 4 or 8 hot cue buttons only.
The rest can be used as flags to remind yourself of the critical places in a track.
This is the functional value.

My upcoming skin has optional:
1 cue point marker
8 hot cue marker
6 fade-in marker
6 fade-out marker
8 (section) begin marker
8 (section) end marker

Now, i see colored bars only, without their meaning. Bad for beginners.
?field.comment=Thank you for your comment.

Only skin developers could set individual pixmaps for the marker. Nothing more.
The designer is free to use it or not. Like the solution for the waveform.

The reason why: I wanted to set individual pixmaps as visual helpers.
Most controllers have 4 or 8 hot cue buttons only.
The rest can be used as flags to remind yourself of the critical places in a track.
This is the functional value.

My upcoming skin has optional:
1 cue point marker
8 hot cue marker
6 fade-in marker
6 fade-out marker
8 (section) begin marker
8 (section) end marker

Now, i see colored bars only, without their meaning. Bad for beginners.

tags: added: cue
jus (jus)
tags: added: skin
Changed in mixxx:
status: New → Confirmed
importance: Undecided → Low
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/8223

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.