Announcement

Collapse
No announcement yet.

Give us some colours on the UI :)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • mark_lyken
    replied
    + 1 For UI Colour Management.
    Would be great to be able to make it greyscale
    Current UI colours (literally) give me a headache!

    Leave a comment:


  • byrdinbbylon
    replied
    +1 on having different pad colors

    Leave a comment:


  • Steve
    replied
    We never removed Trim.

    Leave a comment:


  • Damien
    replied
    In no particular order of ‘wish’
    • Bring back the ‘Trim’ feature. It has been suggested to comply and fit into the time formats now existing. This was an improvement feature … but ‘Trim’ is so handy and useful for quick edit and chop back on file size when saving to SD Card.
    • The option to save the individual sliced samples as potentially as packet.
    • Colour isn’t a big factor but / if not colour then some small moving Game Boy type animations.

    Leave a comment:


  • shankiphonic
    replied
    Where would big successful companies be today if they had not given customers more color options?
    Oh, wait
    Click image for larger version

Name:	6AF1249D-6884-4C91-9BEE-12556A306B5E.jpg
Views:	69
Size:	43.4 KB
ID:	34468

    Leave a comment:


  • Damien
    replied
    +1

    - UI Colour Management
    - PAD colour choice
    - OS animations

    Leave a comment:


  • Andrie
    replied
    yesFuntional Colours!
    different colours for midi sequences and sample sequences empty and recorded: and give this colour out as midi feedback to for the sequences

    Leave a comment:


  • sc1640
    replied
    Me too - give us some choices please

    Leave a comment:


  • brownbroom
    replied
    I second the notion to be able to change the default pink/blue or at least have a greyscale option.

    Leave a comment:


  • euklides
    replied
    Would love to be able to change the colours. Absolutely allergic to the Flickr style cyan/magenta. Even just a monochrome mode would make me jump with joy. The blocky pixel font screams retro, so let's go all the way! Would look so cute next to my Cirklon.

    Click image for larger version

Name:	bannerBackgroundImage_ba8ixjt80ey51.jpg
Views:	114
Size:	158.1 KB
ID:	28924

    Leave a comment:


  • Klaustrophil
    replied
    Originally posted by shankiphonic View Post
    Why this is harder than it sounds.
    The programming to manage where colors are used can live in the firmware today, because it’s standard.
    For color customization to work, data describing your customizations needs to live in the preset, on the micro sd.
    The preset file format is xml. So it is, by definition, extensible. But that doesn’t mean it’s simple.
    This introduces an entirely new aspect to how the processor and the firmware would interact with the removable storage.
    It would need to be tested to ensure that setting seq 11 to cornflower blue doesn’t lead to unexpected audio or sequencer performance.
    Considering what is already known about the hardware, aka, the little engine that could, and the laundry list of audio and functional sequencer related wishes… do you want to potentially put a tax on the blackbox processor for this?
    I don't get your point. The requested feature is some kind of color coding for pads. In the end, this is a 3 byte value in the memory and it's already changeable as you can see in the current firmware. Reading an additional XML key once a preset is loaded will take exactly 0.042 ms longer and writing this value back for once per session or so will have roughly the same impact. Sure there can always break things when changing code, that's the hard part of coding.

    Despite that, don't I really see this feature request as an aesthetic gimmick. Using colors in a meaningful way can help a lot to recognize things so it increases the user experience, especially in live scenarios.

    Leave a comment:


  • Suspect Frequencies
    replied
    I’ve been able to follow this thread and visualize all the suggestions and discourse without pictures using only my imagination. Hardly useless.

    Leave a comment:


  • srirupa
    replied
    this thread is useless without pics

    Leave a comment:


  • shankiphonic
    replied
    Why this is harder than it sounds.
    The programming to manage where colors are used can live in the firmware today, because it’s standard.
    For color customization to work, data describing your customizations needs to live in the preset, on the micro sd.
    The preset file format is xml. So it is, by definition, extensible. But that doesn’t mean it’s simple.
    This introduces an entirely new aspect to how the processor and the firmware would interact with the removable storage.
    It would need to be tested to ensure that setting seq 11 to cornflower blue doesn’t lead to unexpected audio or sequencer performance.
    Considering what is already known about the hardware, aka, the little engine that could, and the laundry list of audio and functional sequencer related wishes… do you want to potentially put a tax on the blackbox processor for this?

    Leave a comment:


  • Flocon
    replied
    Aaron, any news about adding fonctionnal colors assignements into workflow elements for each screens?

    Leave a comment:

Working...
X