ardour/livetrax
13
0
Fork 0
Code
87f79b3891
livetrax/gtk2_ardour/themes/dark-ardour.colors

510 lines
32 KiB
Plaintext
Raw Normal View History

add 22 modifiers to dark.colors and start using the first one (for crossfade alpha)
2014-12-15 09:05:25 -05:00
<?xml version="1.0" encoding="UTF-8"?>
add theme name to each color theme file
2016-05-30 12:17:30 -04:00
<Ardour theme-name="dark">
new version of dark.colors
2014-12-14 16:14:47 -05:00
<Colors>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<Color name="alert blue" value="2E41E6ff"/>
<Color name="alert cyan" value="20b2b2ff"/>
<Color name="alert green" value="3dcc4cff"/>
<Color name="alert orange" value="e58b05ff"/>
<Color name="alert red" value="f10000ff"/>
<Color name="alert ruddy" value="bb2828ff"/>
<Color name="alert yellow" value="bba900ff"/>
<Color name="bg" value="3d3d3dff"/>
<Color name="bg darker" value="373737ff"/>
<Color name="bg darkest" value="101010ff"/>
<Color name="contrast clock" value="4BCD2FFF"/>
<Color name="contrast less" value="5697B3FF"/>
<Color name="contrast selection" value="5da3c1ff"/>
<Color name="contrast1" value="0xf10000ff"/>
<Color name="contrast2" value="CCA336ff"/>
<Color name="black" value="000000ff"/>
<Color name="white" value="ffffffff"/>
<Color name="gray 10" value="202020ff"/>
<Color name="gray 20" value="333333ff"/>
<Color name="gray 30" value="505050ff"/>
<Color name="gray 40" value="666666ff"/>
<Color name="gray 50" value="7f7f7fff"/>
<Color name="gray 60" value="a5a5a5ff"/>
<Color name="gray 70" value="bbbbbbff"/>
<Color name="gray 80" value="ccccccff"/>
<Color name="gray 90" value="e5e5e5ff"/>
<Color name="meter color0" value="008800ff"/>
<Color name="meter color1" value="00aa00ff"/>
<Color name="meter color2" value="00ff00ff"/>
<Color name="meter color3" value="00ff00ff"/>
<Color name="meter color4" value="fff000ff"/>
<Color name="meter color5" value="fff000ff"/>
<Color name="meter color6" value="ff8800ff"/>
<Color name="meter color7" value="ff8800ff"/>
<Color name="meter color8" value="ff0000ff"/>
<Color name="meter color9" value="ff0000ff"/>
<Color name="midi meter 52" value="e8faa1ff"/>
<Color name="midi meter 53" value="f2c37dff"/>
<Color name="midi meter 54" value="ffac44ff"/>
<Color name="midi meter 55" value="f48352ff"/>
<Color name="midi meter 56" value="f85813ff"/>
<Color name="widget bg" value="4F4D4Dff"/> <!--generic button; slightly different than bg color-->
<Color name="widget blue" value="526d94ff"/>
<Color name="widget blue darker" value="20242aff"/>
<Color name="widget gray" value="595755ff"/>
<Color name="widget green" value="617552ff"/>
<Color name="widget green darker" value="3C403AFF"/>
<Color name="widget orange" value="904010ff"/>
<Color name="widget ruddy" value="7c3a3aff"/>
new version of dark.colors
2014-12-14 16:14:47 -05:00
</Colors>
Various color tweaks. This commit changes some color names, nuke your theme. This isn't quite ideal yet, but takes some steps towards where I think things should go aesthetically: Make automation tracks/regions colors correspond to their parent's type. Make selected MIDI notes outlined in red like most everything else, and scrap separate min/mid/max fill colors for selected MIDI notes. Color automation ghost MIDI notes based on original note color. Try to kill 90's looking brightish gray gradients in general.
2014-12-16 00:05:45 -05:00
<ColorAliases>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="active crossfade" alias="gray 90"/>
<ColorAlias name="arrange base" alias="bg"/>
<ColorAlias name="audio automation track fill" alias="bg"/>
<ColorAlias name="audio bus base" alias="widget blue darker"/>
<ColorAlias name="audio master bus base" alias="black"/>
<ColorAlias name="audio track base" alias="gray 10"/>
<ColorAlias name="automation line" alias="alert green"/>
<ColorAlias name="automation track outline" alias="bg darker"/>
<ColorAlias name="big clock active: background" alias="black"/>
<ColorAlias name="big clock active: cursor" alias="contrast clock"/>
<ColorAlias name="big clock active: edited text" alias="contrast clock"/>
<ColorAlias name="big clock active: text" alias="alert red"/>
<ColorAlias name="big clock: background" alias="bg darkest"/>
<ColorAlias name="big clock: cursor" alias="contrast clock"/>
<ColorAlias name="big clock: edited text" alias="contrast clock"/>
<ColorAlias name="big clock: text" alias="contrast clock"/>
<ColorAlias name="border color" alias="black"/>
<ColorAlias name="cd marker bar" alias="gray 30"/>
<ColorAlias name="clipped waveform" alias="alert red"/>
<ColorAlias name="clock: background" alias="bg darkest"/>
<ColorAlias name="clock: cursor" alias="contrast clock"/>
<ColorAlias name="clock: edited text" alias="contrast clock"/>
<ColorAlias name="clock: text" alias="contrast clock"/>
Add missing theme elements, and fix some thinkos
2020-01-12 19:04:32 -05:00
<ColorAlias name="comment button: fill" alias="widget bg"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="control point fill" alias="alert green"/>
Add missing theme elements, and fix some thinkos
2020-01-12 19:04:32 -05:00
<ColorAlias name="control point outline" alias="alert green"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="control point selected fill" alias="alert orange"/>
<ColorAlias name="control point selected outline" alias="alert red"/>
<ColorAlias name="covered region" alias="gray 30"/>
<ColorAlias name="crossfade editor base" alias="gray 80"/>
<ColorAlias name="crossfade editor line" alias="black"/>
<ColorAlias name="crossfade editor line shading" alias="widget blue"/>
<ColorAlias name="crossfade editor point fill" alias="alert green"/>
<ColorAlias name="crossfade editor point outline" alias="alert blue"/>
<ColorAlias name="crossfade editor wave" alias="white"/>
<ColorAlias name="crossfade line" alias="black"/>
<ColorAlias name="edit point" alias="alert blue"/>
<ColorAlias name="entered automation line" alias="widget orange"/>
<ColorAlias name="entered gain line" alias="widget orange"/>
<ColorAlias name="entered marker" alias="widget orange"/>
<ColorAlias name="feedback alert: fill" alias="widget bg"/>
<ColorAlias name="feedback alert: fill active" alias="alert red"/>
<ColorAlias name="feedback alert: led active" alias="alert red"/>
Fix more default theme colors
2020-01-13 13:42:17 -05:00
<ColorAlias name="foldback knob" alias="widget bg"/>
<ColorAlias name="foldback knob: fill" alias="widget bg"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="foldback knob: arc end" alias="alert blue"/>
<ColorAlias name="foldback knob: arc start" alias="widget blue"/>
<ColorAlias name="frame handle" alias="bg darker"/>
<ColorAlias name="gain line" alias="alert green"/>
<ColorAlias name="gain line inactive" alias="bg darker"/>
<ColorAlias name="generic button: fill" alias="widget bg"/>
<ColorAlias name="generic button: fill active" alias="alert red"/>
<ColorAlias name="generic button: led active" alias="alert green"/>
<ColorAlias name="ghost track base" alias="gray 20"/>
<ColorAlias name="ghost track midi outline" alias="black"/>
<ColorAlias name="ghost track wave" alias="gray 10"/>
<ColorAlias name="ghost track wave clip" alias="gray 10"/>
<ColorAlias name="ghost track wave fill" alias="white"/>
<ColorAlias name="ghost track zero line" alias="gray 70"/>
<ColorAlias name="grid line major" alias="white"/>
<ColorAlias name="grid line micro" alias="gray 50"/>
<ColorAlias name="grid line minor" alias="gray 50"/>
<ColorAlias name="gtk_arm" alias="alert red"/>
<ColorAlias name="gtk_audio_bus" alias="widget blue darker"/>
<ColorAlias name="gtk_audio_track" alias="bg darker"/>
<ColorAlias name="gtk_automation_track_header" alias="bg"/>
<ColorAlias name="gtk_background" alias="bg"/>
<ColorAlias name="gtk_bases" alias="bg darkest"/>
<ColorAlias name="gtk_bg_selected" alias="contrast selection"/>
<ColorAlias name="gtk_bg_tooltip" alias="contrast less"/>
<ColorAlias name="gtk_bright_color" alias="widget blue"/>
<ColorAlias name="gtk_bright_indicator" alias="alert red"/>
<ColorAlias name="gtk_clip_indicator" alias="alert red"/>
<ColorAlias name="gtk_contrasting_indicator" alias="alert green"/>
<ColorAlias name="gtk_control_master" alias="bg darker"/>
<ColorAlias name="gtk_control_text" alias="gray 90"/>
<ColorAlias name="gtk_control_text2" alias="alert ruddy"/>
<ColorAlias name="gtk_darkest" alias="bg darkest"/>
<ColorAlias name="gtk_entry_cursor" alias="alert red"/>
<ColorAlias name="gtk_fg_selected" alias="bg darkest"/>
<ColorAlias name="gtk_fg_tooltip" alias="gray 10"/>
<ColorAlias name="gtk_foldback_bg" alias="bg darker"/>
<ColorAlias name="gtk_foreground" alias="gray 90"/>
<ColorAlias name="gtk_light_text_on_dark" alias="gray 80"/>
<ColorAlias name="gtk_lightest" alias="white"/>
<ColorAlias name="gtk_midi_channel_selector" alias="widget blue"/>
<ColorAlias name="gtk_midi_track" alias="widget green darker"/>
<ColorAlias name="gtk_monitor" alias="alert orange"/>
<ColorAlias name="gtk_mono" alias="gray 90"/>
<ColorAlias name="gtk_mute" alias="alert yellow"/>
<ColorAlias name="gtk_not_so_bright_indicator" alias="contrast1"/>
<ColorAlias name="gtk_processor_fader" alias="widget gray"/>
<ColorAlias name="gtk_processor_fader_frame" alias="gray 50"/>
<ColorAlias name="gtk_processor_frame_selected" alias="contrast1"/>
<ColorAlias name="gtk_processor_postfader" alias="widget green"/>
<ColorAlias name="gtk_processor_postfader_frame" alias="widget green"/>
<ColorAlias name="gtk_processor_prefader" alias="widget ruddy"/>
<ColorAlias name="gtk_processor_prefader_frame" alias="widget ruddy"/>
<ColorAlias name="gtk_send_bg" alias="bg darker"/>
Fix thinko in aux-fader color.
2019-11-01 11:35:53 -04:00
<ColorAlias name="gtk_send_fg" alias="widget blue"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="gtk_solo" alias="alert green"/>
<ColorAlias name="gtk_somewhat_bright_indicator" alias="contrast2"/>
<ColorAlias name="gtk_texts" alias="gray 90"/>
<ColorAlias name="gtk_track_header_inactive" alias="bg"/>
<ColorAlias name="gtk_track_header_selected" alias="widget ruddy"/>
<ColorAlias name="image track" alias="gray 80"/>
<ColorAlias name="inactive crossfade" alias="contrast1"/>
<ColorAlias name="inactive fade handle" alias="gray 70"/>
<ColorAlias name="inactive group tab" alias="bg"/>
Add missing theme elements, and fix some thinkos
2020-01-12 19:04:32 -05:00
<ColorAlias name="invert button: fill" alias="widget bg"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="invert button: fill active" alias="alert blue"/>
<ColorAlias name="invert button: led active" alias="alert green"/>
Fix more default theme colors
2020-01-13 13:42:17 -05:00
<ColorAlias name="latency button: fill" alias="widget bg"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="latency button: fill active" alias="alert ruddy"/>
<ColorAlias name="latency button: led active" alias="alert ruddy"/>
<ColorAlias name="layered button: fill" alias="widget bg"/>
<ColorAlias name="layered button: fill active" alias="alert ruddy"/>
<ColorAlias name="location cd marker" alias="alert cyan"/>
<ColorAlias name="location loop" alias="alert green"/>
<ColorAlias name="location marker" alias="contrast clock"/>
<ColorAlias name="location punch" alias="alert ruddy"/>
<ColorAlias name="location range" alias="alert green"/>
Add missing theme elements, and fix some thinkos
2020-01-12 19:04:32 -05:00
<ColorAlias name="lock button: fill active" alias="widget bg"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="lock button: led active" alias="alert red"/>
Add missing theme elements, and fix some thinkos
2020-01-12 19:04:32 -05:00
<ColorAlias name="lua action button: fill" alias="bg"/>
<ColorAlias name="lua action button: fill" alias="widget bg"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="marker bar" alias="gray 30"/>
<ColorAlias name="marker bar separator" alias="bg darkest"/>
<ColorAlias name="marker drag line" alias="contrast clock"/>
<ColorAlias name="marker label" alias="black"/>
<ColorAlias name="marker track" alias="gray 80"/>
<ColorAlias name="master monitor section button active: fill" alias="widget ruddy"/>
<ColorAlias name="master monitor section button active: fill active" alias="alert yellow"/>
Add missing theme elements, and fix some thinkos
2020-01-12 19:04:32 -05:00
<ColorAlias name="master monitor section button normal: fill active" alias="widget bg"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="measure line bar" alias="white"/>
<ColorAlias name="measure line beat" alias="widget blue"/>
<ColorAlias name="meter background bottom" alias="gray 20"/>
<ColorAlias name="meter background top" alias="bg"/>
<ColorAlias name="meter bar" alias="bg darker"/>
<ColorAlias name="meter color BBC" alias="alert orange"/>
<ColorAlias name="meter marker" alias="widget orange"/>
<ColorAlias name="meter marker music" alias="widget orange"/>
<ColorAlias name="meterbridge label: fill" alias="bg"/>
<ColorAlias name="meterbridge label: fill active" alias="gray 20"/>
<ColorAlias name="meterbridge label: led" alias="alert red"/>
<ColorAlias name="meterbridge label: led active" alias="alert red"/>
Add missing theme elements, and fix some thinkos
2020-01-12 19:04:32 -05:00
<ColorAlias name="meterbridge peakindicator: fill" alias="widget bg"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="meterbridge peakindicator: fill active" alias="alert red"/>
<ColorAlias name="meterbridge peakindicator: led" alias="alert red"/>
<ColorAlias name="meterbridge peakindicator: led active" alias="alert red"/>
<ColorAlias name="meterbridge peaklabel" alias="alert red"/>
<ColorAlias name="meterstrip dpm bg" alias="bg darkest"/>
<ColorAlias name="meterstrip dpm fg" alias="gray 80"/>
<ColorAlias name="meterstrip ppm bg" alias="bg darkest"/>
<ColorAlias name="meterstrip ppm fg" alias="gray 80"/>
<ColorAlias name="meterstrip vu bg" alias="contrast1"/>
<ColorAlias name="meterstrip vu fg" alias="black"/>
<ColorAlias name="midi automation track fill" alias="widget green darker"/>
<ColorAlias name="midi bus base" alias="black"/>
<ColorAlias name="midi device: fill" alias="widget bg"/>
<ColorAlias name="midi device: fill active" alias="bg"/>
<ColorAlias name="midi device: led active" alias="alert green"/>
<ColorAlias name="midi frame base" alias="gray 30"/>
<ColorAlias name="midi input button: fill active" alias="alert green"/>
<ColorAlias name="midi input button: led active" alias="alert red"/>
<ColorAlias name="midi meter color0" alias="midi meter 52"/>
<ColorAlias name="midi meter color1" alias="midi meter 53"/>
<ColorAlias name="midi meter color2" alias="midi meter 53"/>
<ColorAlias name="midi meter color3" alias="midi meter 54"/>
<ColorAlias name="midi meter color4" alias="midi meter 54"/>
<ColorAlias name="midi meter color5" alias="midi meter 55"/>
<ColorAlias name="midi meter color6" alias="midi meter 55"/>
<ColorAlias name="midi meter color7" alias="midi meter 56"/>
<ColorAlias name="midi meter color8" alias="midi meter 56"/>
Add missing theme elements, and fix some thinkos
2020-01-12 19:04:32 -05:00
<ColorAlias name="midi meter color9" alias="midi meter 56"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="midi note inactive channel" alias="black"/>
<ColorAlias name="midi note max" alias="alert green"/>
<ColorAlias name="midi note mid" alias="alert yellow"/>
<ColorAlias name="midi note min" alias="alert orange"/>
<ColorAlias name="midi note selected" alias="widget ruddy"/>
<ColorAlias name="midi note selected outline" alias="alert red"/>
<ColorAlias name="midi note velocity text" alias="contrast1"/>
<ColorAlias name="midi patch change fill" alias="contrast selection"/>
<ColorAlias name="midi patch change outline" alias="gray 90"/>
<ColorAlias name="midi select rect outline" alias="alert red"/>
<ColorAlias name="midi sysex fill" alias="contrast1"/>
<ColorAlias name="midi sysex outline" alias="contrast2"/>
<ColorAlias name="midi track base" alias="widget green darker"/>
Add missing theme elements, and fix some thinkos
2020-01-12 19:04:32 -05:00
<ColorAlias name="mixer strip button: fill" alias="widget bg"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="mixer strip button: fill active" alias="bg darker"/>
<ColorAlias name="mixer strip button: led active" alias="alert orange"/>
<ColorAlias name="mixer strip name button: fill active" alias="bg darkest"/>
<ColorAlias name="mixer strip name button: led active" alias="alert orange"/>
Add missing theme elements, and fix some thinkos
2020-01-12 19:04:32 -05:00
<ColorAlias name="monitor button: fill" alias="widget bg"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="monitor button: fill active" alias="alert orange"/>
<ColorAlias name="monitor button: led active" alias="alert ruddy"/>
Add missing theme elements, and fix some thinkos
2020-01-12 19:04:32 -05:00
<ColorAlias name="monitor section button: fill" alias="widget bg"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="monitor section dim: fill" alias="widget bg"/>
<ColorAlias name="monitor section dim: fill active" alias="alert orange"/>
<ColorAlias name="monitor section dim: led active" alias="alert green"/>
<ColorAlias name="monitor section knob" alias="widget bg"/>
<ColorAlias name="monitor section knob: arc end" alias="alert blue"/>
<ColorAlias name="monitor section knob: arc start" alias="widget blue"/>
<ColorAlias name="monitor section mono: fill" alias="widget bg"/>
<ColorAlias name="monitor section mono: fill active" alias="alert blue"/>
<ColorAlias name="monitor section mono: led active" alias="alert green"/>
Add missing theme elements, and fix some thinkos
2020-01-12 19:04:32 -05:00
<ColorAlias name="monitor section processors present: fill" alias="alert orange"/>
<ColorAlias name="monitor section processors toggle: fill" alias="bg"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="monitor section processors toggle: fill active" alias="bg"/>
<ColorAlias name="monitor section solo model: fill" alias="widget bg"/>
<ColorAlias name="monitor section solo model: fill active" alias="bg"/>
<ColorAlias name="monitor section solo model: led active" alias="alert orange"/>
<ColorAlias name="monitor section solo option: fill" alias="widget bg"/>
<ColorAlias name="monitor section solo option: fill active" alias="bg"/>
<ColorAlias name="monitor section solo option: led active" alias="alert orange"/>
<ColorAlias name="mono panner bg" alias="bg darkest"/>
<ColorAlias name="mono panner fill" alias="widget blue"/>
<ColorAlias name="mono panner outline" alias="bg"/>
<ColorAlias name="mono panner position fill" alias="contrast less"/>
<ColorAlias name="mono panner position outline" alias="bg"/>
<ColorAlias name="mono panner text" alias="black"/>
Add missing theme elements, and fix some thinkos
2020-01-12 19:04:32 -05:00
<ColorAlias name="mouse mode button: fill" alias="widget bg"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="mouse mode button: fill active" alias="alert green"/>
<ColorAlias name="mouse mode button: led active" alias="alert orange"/>
<ColorAlias name="mute button: fill" alias="widget bg"/>
<ColorAlias name="mute button: fill active" alias="alert yellow"/>
<ColorAlias name="mute button: led active" alias="alert yellow"/>
<ColorAlias name="name highlight fill" alias="alert blue"/>
<ColorAlias name="name highlight outline" alias="bg darker"/>
Add missing theme elements, and fix some thinkos
2020-01-12 19:04:32 -05:00
<ColorAlias name="nudge button: fill" alias="widget bg"/>
<ColorAlias name="nudge button: fill active" alias="widget bg"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="nudge button: led active" alias="alert orange"/>
<ColorAlias name="nudge clock: background" alias="bg darkest"/>
<ColorAlias name="nudge clock: cursor" alias="contrast clock"/>
<ColorAlias name="nudge clock: edited text" alias="contrast clock"/>
<ColorAlias name="nudge clock: text" alias="contrast clock"/>
Add missing theme elements, and fix some thinkos
2020-01-12 19:04:32 -05:00
<ColorAlias name="page switch button: fill" alias="widget bg"/>
<ColorAlias name="page switch button: fill active" alias="alert green"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="patch change button: fill" alias="widget bg"/>
<ColorAlias name="patch change button: fill active" alias="widget blue"/>
<ColorAlias name="patch change dim button: fill" alias="gray 20"/>
<ColorAlias name="patch change dim button: fill active" alias="widget blue"/>
<ColorAlias name="patch change dim button: text" alias="widget blue"/>
<ColorAlias name="piano roll black" alias="contrast selection"/>
<ColorAlias name="piano roll black outline" alias="gray 70"/>
<ColorAlias name="piano roll white" alias="gray 70"/>
<ColorAlias name="pinrouting custom: led active" alias="alert ruddy"/>
<ColorAlias name="pinrouting sidechain: led active" alias="alert green"/>
<ColorAlias name="play head" alias="contrast1"/>
<ColorAlias name="plugin automation state button: fill active" alias="alert orange"/>
<ColorAlias name="plugin bypass button: led active" alias="alert orange"/>
<ColorAlias name="pluginlist filter button: fill active" alias="widget bg"/>
<ColorAlias name="pluginlist hide button: led active" alias="alert cyan"/>
Fix more default theme colors
2020-01-13 13:42:17 -05:00
<ColorAlias name="pluginui toggle: fill" alias="widget bg"/>
<ColorAlias name="pluginui toggle: fill active" alias="widget blue"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="processor automation line" alias="bg darker"/>
<ColorAlias name="processor auxfeedback: fill" alias="contrast2"/>
<ColorAlias name="processor auxfeedback: led active" alias="alert green"/>
<ColorAlias name="processor control button: fill" alias="gray 10"/>
<ColorAlias name="processor control button: fill active" alias="gray 20"/>
<ColorAlias name="processor control button: led active" alias="widget blue"/>
<ColorAlias name="processor control knob" alias="contrast selection"/>
<ColorAlias name="processor control knob: arc end" alias="alert blue"/>
<ColorAlias name="processor control knob: arc start" alias="widget blue"/>
<ColorAlias name="processor fader: fill" alias="widget blue"/>
<ColorAlias name="processor fader: fill active" alias="widget blue"/>
<ColorAlias name="processor fader: led active" alias="alert green"/>
<ColorAlias name="processor postfader: fill" alias="widget green"/>
<ColorAlias name="processor postfader: fill active" alias="widget green"/>
<ColorAlias name="processor postfader: led active" alias="alert green"/>
<ColorAlias name="processor prefader: fill" alias="widget ruddy"/>
<ColorAlias name="processor prefader: fill active" alias="widget ruddy"/>
<ColorAlias name="processor prefader: led active" alias="alert green"/>
<ColorAlias name="processor sidechain: fill" alias="alert orange"/>
<ColorAlias name="processor sidechain: led active" alias="alert green"/>
<ColorAlias name="processor stub: fill" alias="gray 20"/>
<ColorAlias name="processor stub: fill active" alias="gray 20"/>
Add missing theme elements, and fix some thinkos
2020-01-12 19:04:32 -05:00
<ColorAlias name="punch button: fill" alias="widget bg"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="punch button: fill active" alias="alert ruddy"/>
<ColorAlias name="punch button: led active" alias="alert red"/>
<ColorAlias name="punch clock: background" alias="bg darkest"/>
<ColorAlias name="punch clock: cursor" alias="alert ruddy"/>
<ColorAlias name="punch clock: edited text" alias="alert ruddy"/>
<ColorAlias name="punch clock: text" alias="contrast clock"/>
<ColorAlias name="punch line" alias="alert ruddy"/>
<ColorAlias name="range drag bar rect" alias="gray 50"/>
<ColorAlias name="range drag rect" alias="alert ruddy"/>
<ColorAlias name="range marker bar" alias="gray 20"/>
<ColorAlias name="record enable button: fill active" alias="alert ruddy"/>
Add missing theme elements, and fix some thinkos
2020-01-12 19:04:32 -05:00
<ColorAlias name="record enable button: led active" alias="alert red"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="recording rect" alias="alert ruddy"/>
<ColorAlias name="recording waveform fill" alias="white"/>
<ColorAlias name="recording waveform outline" alias="gray 20"/>
<ColorAlias name="region list automatic" alias="contrast less"/>
<ColorAlias name="region list missing source" alias="alert red"/>
Fix more default theme colors
2020-01-13 13:42:17 -05:00
<ColorAlias name="region list whole file" alias="gray 90"/>
Add missing theme elements, and fix some thinkos
2020-01-12 19:04:32 -05:00
<ColorAlias name="route button: fill" alias="widget bg"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="route button: fill active" alias="bg darkest"/>
<ColorAlias name="route button: led active" alias="alert orange"/>
Add missing theme elements, and fix some thinkos
2020-01-12 19:04:32 -05:00
<ColorAlias name="route rec button: led active" alias="alert red"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="rubber band rect" alias="gray 70"/>
<ColorAlias name="rude audition: fill" alias="widget bg"/>
<ColorAlias name="rude audition: fill active" alias="alert ruddy"/>
<ColorAlias name="rude audition: led active" alias="alert red"/>
<ColorAlias name="rude isolate: fill" alias="widget bg"/>
<ColorAlias name="rude isolate: fill active" alias="contrast2"/>
<ColorAlias name="rude isolate: led active" alias="alert red"/>
<ColorAlias name="rude solo: fill" alias="widget bg"/>
<ColorAlias name="rude solo: fill active" alias="alert ruddy"/>
<ColorAlias name="rude solo: led active" alias="alert red"/>
<ColorAlias name="ruler base" alias="bg darkest"/>
<ColorAlias name="ruler text" alias="gray 50"/>
<ColorAlias name="secondary clock: background" alias="bg darkest"/>
<ColorAlias name="secondary clock: cursor" alias="contrast clock"/>
<ColorAlias name="secondary clock: edited text" alias="contrast clock"/>
<ColorAlias name="secondary clock: text" alias="contrast clock"/>
<ColorAlias name="secondary delta clock: background" alias="bg darkest"/>
<ColorAlias name="secondary delta clock: cursor" alias="contrast2"/>
<ColorAlias name="secondary delta clock: edited text" alias="contrast2"/>
<ColorAlias name="secondary delta clock: text" alias="contrast2"/>
<ColorAlias name="selected midi note frame" alias="alert ruddy"/>
<ColorAlias name="selected region base" alias="alert ruddy"/>
<ColorAlias name="selected time axis frame" alias="alert ruddy"/>
<ColorAlias name="selected waveform fill" alias="alert orange"/>
<ColorAlias name="selected waveform outline" alias="bg darkest"/>
<ColorAlias name="selection" alias="alert red"/>
<ColorAlias name="selection clock: background" alias="bg darkest"/>
<ColorAlias name="selection clock: cursor" alias="alert ruddy"/>
<ColorAlias name="selection clock: edited text" alias="alert ruddy"/>
<ColorAlias name="selection clock: text" alias="contrast clock"/>
<ColorAlias name="selection rect" alias="gray 90"/>
<ColorAlias name="send alert button: fill" alias="contrast selection"/>
<ColorAlias name="send alert button: fill active" alias="alert cyan"/>
<ColorAlias name="send alert button: led active" alias="alert red"/>
<ColorAlias name="send bg" alias="alert cyan"/>
<ColorAlias name="shuttle" alias="widget bg"/>
<ColorAlias name="shuttle bg" alias="black"/>
<ColorAlias name="shuttle text" alias="white"/>
<ColorAlias name="silence" alias="contrast2"/>
<ColorAlias name="silence text" alias="gray 90"/>
<ColorAlias name="solo button: fill" alias="widget bg"/>
<ColorAlias name="solo button: fill active" alias="alert green"/>
<ColorAlias name="solo button: led active" alias="alert green"/>
<ColorAlias name="solo isolate: fill" alias="widget bg"/>
Add missing theme elements, and fix some thinkos
2020-01-12 19:04:32 -05:00
<ColorAlias name="solo isolate: fill active" alias="widget bg"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="solo isolate: led active" alias="alert ruddy"/>
<ColorAlias name="solo safe: fill" alias="widget bg"/>
Add missing theme elements, and fix some thinkos
2020-01-12 19:04:32 -05:00
<ColorAlias name="solo safe: fill active" alias="widget bg"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="solo safe: led active" alias="alert ruddy"/>
<ColorAlias name="stereo panner bg" alias="bg darkest"/>
<ColorAlias name="stereo panner fill" alias="widget blue"/>
<ColorAlias name="stereo panner inverted bg" alias="widget blue darker"/>
<ColorAlias name="stereo panner inverted fill" alias="contrast less"/>
<ColorAlias name="stereo panner inverted outline" alias="alert ruddy"/>
<ColorAlias name="stereo panner inverted text" alias="black"/>
<ColorAlias name="stereo panner mono bg" alias="bg darkest"/>
<ColorAlias name="stereo panner mono fill" alias="bg"/>
<ColorAlias name="stereo panner mono outline" alias="alert orange"/>
<ColorAlias name="stereo panner mono text" alias="black"/>
<ColorAlias name="stereo panner outline" alias="bg"/>
<ColorAlias name="stereo panner rule" alias="bg"/>
<ColorAlias name="stereo panner text" alias="black"/>
<ColorAlias name="stretch clock: background" alias="bg darkest"/>
<ColorAlias name="stretch clock: cursor" alias="contrast clock"/>
<ColorAlias name="stretch clock: edited text" alias="contrast clock"/>
<ColorAlias name="stretch clock: text" alias="contrast clock"/>
<ColorAlias name="sync mark" alias="contrast clock"/>
<ColorAlias name="tempo bar" alias="gray 20"/>
<ColorAlias name="tempo curve" alias="widget blue"/>
<ColorAlias name="tempo marker" alias="widget orange"/>
<ColorAlias name="tempo marker music" alias="widget orange"/>
<ColorAlias name="time axis frame" alias="black"/>
<ColorAlias name="time axis view item base" alias="widget gray"/>
<ColorAlias name="time stretch fill" alias="contrast less"/>
<ColorAlias name="time stretch outline" alias="widget gray"/>
<ColorAlias name="tracknumber label: fill" alias="bg"/>
<ColorAlias name="tracknumber label: fill active" alias="gray 20"/>
<ColorAlias name="tracknumber label: led active" alias="alert red"/>
Add missing theme elements, and fix some thinkos
2020-01-12 19:04:32 -05:00
<ColorAlias name="transport active option button: fill" alias="widget bg"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="transport active option button: fill active" alias="alert green"/>
<ColorAlias name="transport active option button: led active" alias="alert orange"/>
Add missing theme elements, and fix some thinkos
2020-01-12 19:04:32 -05:00
<ColorAlias name="transport button: fill" alias="widget bg"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="transport button: fill active" alias="alert green"/>
<ColorAlias name="transport button: led active" alias="alert orange"/>
<ColorAlias name="transport clock: background" alias="bg darkest"/>
<ColorAlias name="transport clock: cursor" alias="contrast clock"/>
<ColorAlias name="transport clock: edited text" alias="contrast clock"/>
<ColorAlias name="transport clock: text" alias="contrast clock"/>
<ColorAlias name="transport delta clock: background" alias="bg darkest"/>
<ColorAlias name="transport delta clock: cursor" alias="contrast2"/>
<ColorAlias name="transport delta clock: edited text" alias="contrast2"/>
<ColorAlias name="transport delta clock: text" alias="contrast2"/>
<ColorAlias name="transport drag rect" alias="gray 50"/>
"revert" back to previous loop rect in editor color
2019-12-07 12:28:56 -05:00
<ColorAlias name="transport loop rect" alias="alert green"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="transport marker bar" alias="widget bg"/>
Add missing theme elements, and fix some thinkos
2020-01-12 19:04:32 -05:00
<ColorAlias name="transport option button: fill" alias="widget bg"/>
<ColorAlias name="transport option button: fill active" alias="widget bg"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="transport option button: led active" alias="alert orange"/>
<ColorAlias name="transport punch rect" alias="widget ruddy"/>
Add missing theme elements, and fix some thinkos
2020-01-12 19:04:32 -05:00
<ColorAlias name="transport recenable button: fill" alias="widget bg"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="transport recenable button: fill active" alias="alert ruddy"/>
<ColorAlias name="transport recenable button: led active" alias="alert red"/>
<ColorAlias name="trim handle" alias="alert blue"/>
<ColorAlias name="trim handle locked" alias="alert ruddy"/>
<ColorAlias name="trim knob" alias="widget bg"/>
<ColorAlias name="trim knob: arc end" alias="alert blue"/>
Fix more default theme colors
2020-01-13 13:42:17 -05:00
<ColorAlias name="trim knob: arc start" alias="widget bg"/>
Add missing theme elements, and fix some thinkos
2020-01-12 19:04:32 -05:00
<ColorAlias name="vca assign button: fill" alias="widget bg"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="verbose canvas cursor" alias="contrast clock"/>
<ColorAlias name="video timeline bar" alias="gray 20"/>
<ColorAlias name="waveform fill" alias="white"/>
<ColorAlias name="waveform outline" alias="black"/>
<ColorAlias name="zero line" alias="gray 50"/>
Add missing theme elements, and fix some thinkos
2020-01-12 19:04:32 -05:00
<ColorAlias name="zoom button: fill" alias="widget bg"/>
Theme-ing: Use sensible names instead of color 1..N Colors are assigned one of 6 major groups: *Alert colors: Typically mute/solo/feedback/selections etc ... these should follow Ardour convention, only the saturation should change with themes. *BG colors (empty spaces...) *Contrast colors: Should contrast nicely against BG. Typically clocks, markers, panners and such. *Black/White/Grays: you can expect these to work with "any" BG. Good for borders, separators, etc. *Meter colors: Typically green->yellow->red or similar. Should follow Ardour conventions. *Widget colors: slight variations of the BG color. This is where the creative choices are made. NOTE to theme-ers: Widgets should choose one of the colors based on FUNCTION. If you want a red widget, choose "widget red", not "alert red" or "meter color9"
2019-10-10 19:24:57 -04:00
<ColorAlias name="zoom button: fill active" alias="alert green"/>
<ColorAlias name="zoom button: led active" alias="alert orange"/> </ColorAliases>
basic code to use SVModifier plus one definition in dark.colors
2014-12-14 23:34:59 -05:00
<Modifiers>
More consistent canvas base colours. General ideas: audio is blueish, MIDI is greenish, automation track colour is a slightly darker version of its parent track colour, canvas base is the same as the Gtk base.
2015-01-08 14:56:47 -05:00
<Modifier name="audio bus base" modifier="= alpha:0.3"/>
<Modifier name="audio track base" modifier="= alpha:0.3"/>
allow automation line fill opacity to be theme-able
2017-01-12 16:07:30 -05:00
<Modifier name="automation line fill" modifier="= alpha:0.3"/>
More consistent canvas base colours. General ideas: audio is blueish, MIDI is greenish, automation track colour is a slightly darker version of its parent track colour, canvas base is the same as the Gtk base.
2015-01-08 14:56:47 -05:00
<Modifier name="automation track fill" modifier="= alpha:0.3"/>
<Modifier name="covered region base" modifier="= alpha:0.7"/>
add 22 modifiers to dark.colors and start using the first one (for crossfade alpha)
2014-12-15 09:05:25 -05:00
<Modifier name="crossfade alpha" modifier="= alpha:0.1803"/>
Use color modifiers for dynamic region styles.
2014-12-16 20:37:16 -05:00
<Modifier name="dragging region" modifier="= alpha:0.9"/>
Increase editable region alpha slightly. Previously the region was nearly invisible when editable which is problematic ("oops, I made a new region"). The distinction isn't quite as profound as it probably should be, but I don't want to mess with the other region colours too much.
2015-03-06 16:43:34 -05:00
<Modifier name="editable region" modifier="= alpha:0.25"/>
next modifier
2014-12-15 10:02:20 -05:00
<Modifier name="gain line inactive" modifier="= alpha:0.7725"/>
Various color tweaks. This commit changes some color names, nuke your theme. This isn't quite ideal yet, but takes some steps towards where I think things should go aesthetically: Make automation tracks/regions colors correspond to their parent's type. Make selected MIDI notes outlined in red like most everything else, and scrap separate min/mid/max fill colors for selected MIDI notes. Color automation ghost MIDI notes based on original note color. Try to kill 90's looking brightish gray gradients in general.
2014-12-16 00:05:45 -05:00
<Modifier name="ghost track base" modifier="= alpha:0.640782"/>
More consistent canvas base colours. General ideas: audio is blueish, MIDI is greenish, automation track colour is a slightly darker version of its parent track colour, canvas base is the same as the Gtk base.
2015-01-08 14:56:47 -05:00
<Modifier name="ghost track midi fill" modifier="= alpha:0.3"/>
next modifier
2014-12-15 10:21:08 -05:00
<Modifier name="inactive crossfade" modifier="= alpha:0.4666"/>
Increase transparency of Loop rectangle so tempo lines are visible Should fix bug#6163
2015-02-15 20:52:20 -05:00
<Modifier name="loop rectangle" modifier="= alpha:0.5"/>
Revert "hotfix z-stacking" This reverts commit 03f0229bcfc35916f81c6187948df3ea3b79a976. Mitigate the fallout from said overly aggressive revert: preserve the alpha values to not break the color configuration for when the lines are fixed.
2015-01-11 21:41:17 -05:00
<Modifier name="marker bar" modifier="= alpha:0.5"/>
Implement grid line colors ( was: measure lines ). This restores measure lines to a brighter color than beats.
2018-02-27 17:39:49 -05:00
<Modifier name="grid line" modifier="= alpha:1.0"/>
next modifier
2014-12-15 10:32:17 -05:00
<Modifier name="midi frame base" modifier="= alpha:0.4"/>
Meter-like note colours, but still mostly green. The previous colours made low velocity notes almost invisible. This fixes that and attempts meter-like colours where yellowish is high, but without going all the way into red for a generally consistent range of colors.
2015-01-08 18:34:18 -05:00
<Modifier name="midi note" modifier="= alpha:0.8"/>
Various color tweaks. This commit changes some color names, nuke your theme. This isn't quite ideal yet, but takes some steps towards where I think things should go aesthetically: Make automation tracks/regions colors correspond to their parent's type. Make selected MIDI notes outlined in red like most everything else, and scrap separate min/mid/max fill colors for selected MIDI notes. Color automation ghost MIDI notes based on original note color. Try to kill 90's looking brightish gray gradients in general.
2014-12-16 00:05:45 -05:00
<Modifier name="midi note velocity text" modifier="= alpha:0.4666"/>
next modifier
2014-12-15 10:32:17 -05:00
<Modifier name="midi patch change fill" modifier="= alpha:0.6274"/>
Various color tweaks. This commit changes some color names, nuke your theme. This isn't quite ideal yet, but takes some steps towards where I think things should go aesthetically: Make automation tracks/regions colors correspond to their parent's type. Make selected MIDI notes outlined in red like most everything else, and scrap separate min/mid/max fill colors for selected MIDI notes. Color automation ghost MIDI notes based on original note color. Try to kill 90's looking brightish gray gradients in general.
2014-12-16 00:05:45 -05:00
<Modifier name="midi sysex fill" modifier="= alpha:0.4666"/>
More consistent canvas base colours. General ideas: audio is blueish, MIDI is greenish, automation track colour is a slightly darker version of its parent track colour, canvas base is the same as the Gtk base.
2015-01-08 14:56:47 -05:00
<Modifier name="midi track base" modifier="= alpha:0.3"/>
Various color tweaks. This commit changes some color names, nuke your theme. This isn't quite ideal yet, but takes some steps towards where I think things should go aesthetically: Make automation tracks/regions colors correspond to their parent's type. Make selected MIDI notes outlined in red like most everything else, and scrap separate min/mid/max fill colors for selected MIDI notes. Color automation ghost MIDI notes based on original note color. Try to kill 90's looking brightish gray gradients in general.
2014-12-16 00:05:45 -05:00
<Modifier name="mono panner position fill" modifier="= alpha:0.8"/>
New region opacity rules. (final part of 973e9a)
2019-09-29 11:58:53 -04:00
<Modifier name="opaque region base" modifier="= alpha:1.0"/>
next modifier
2014-12-15 10:43:39 -05:00
<Modifier name="panner fill" modifier="= alpha:0.7882"/>
More consistent canvas base colours. General ideas: audio is blueish, MIDI is greenish, automation track colour is a slightly darker version of its parent track colour, canvas base is the same as the Gtk base.
2015-01-08 14:56:47 -05:00
<Modifier name="piano roll black" modifier="= alpha:0.2"/>
<Modifier name="piano roll white" modifier="= alpha:0.2"/>
Fix display of MIDI notes/regions while recording. Make record rect transparency configurable. Factor out some copy-paste streamview code.
2014-12-17 18:40:38 -05:00
<Modifier name="recording rect" modifier="= alpha:0.25"/>
Various color tweaks. This commit changes some color names, nuke your theme. This isn't quite ideal yet, but takes some steps towards where I think things should go aesthetically: Make automation tracks/regions colors correspond to their parent's type. Make selected MIDI notes outlined in red like most everything else, and scrap separate min/mid/max fill colors for selected MIDI notes. Color automation ghost MIDI notes based on original note color. Try to kill 90's looking brightish gray gradients in general.
2014-12-16 00:05:45 -05:00
<Modifier name="selected midi note" modifier="= alpha:0.7529"/>
next 2 modifiers
2014-12-15 10:46:15 -05:00
<Modifier name="selection rect" modifier="= alpha:0.4666"/>
final modifier
2014-12-15 10:47:51 -05:00
<Modifier name="silence" modifier="= alpha:0.4784"/>
Various color tweaks. This commit changes some color names, nuke your theme. This isn't quite ideal yet, but takes some steps towards where I think things should go aesthetically: Make automation tracks/regions colors correspond to their parent's type. Make selected MIDI notes outlined in red like most everything else, and scrap separate min/mid/max fill colors for selected MIDI notes. Color automation ghost MIDI notes based on original note color. Try to kill 90's looking brightish gray gradients in general.
2014-12-16 00:05:45 -05:00
<Modifier name="stereo panner inverted" modifier="= alpha:0.7882"/>
<Modifier name="stereo panner inverted bg" modifier="= alpha:0.7529"/>
More consistent canvas base colours. General ideas: audio is blueish, MIDI is greenish, automation track colour is a slightly darker version of its parent track colour, canvas base is the same as the Gtk base.
2015-01-08 14:56:47 -05:00
<Modifier name="time axis view item base" modifier="= alpha:0.7"/>
Increase editable region alpha slightly. Previously the region was nearly invisible when editable which is problematic ("oops, I made a new region"). The distinction isn't quite as profound as it probably should be, but I don't want to mess with the other region colours too much.
2015-03-06 16:43:34 -05:00
<Modifier name="transparent region base" modifier="= alpha:0.6"/>
fix color and alpha of timestretch rect
2015-02-06 22:46:43 -05:00
<Modifier name="time stretch fill" modifier="= alpha:0.5"/>
Various color tweaks. This commit changes some color names, nuke your theme. This isn't quite ideal yet, but takes some steps towards where I think things should go aesthetically: Make automation tracks/regions colors correspond to their parent's type. Make selected MIDI notes outlined in red like most everything else, and scrap separate min/mid/max fill colors for selected MIDI notes. Color automation ghost MIDI notes based on original note color. Try to kill 90's looking brightish gray gradients in general.
2014-12-16 00:05:45 -05:00
<Modifier name="verbose canvas cursor" modifier="= alpha:0.4666"/>
fix XML syntax error
2014-12-14 23:36:11 -05:00
</Modifiers>
another metric ton of color work
2014-12-08 18:19:11 -05:00
</Ardour>
Copy Permalink