6 Commits

Author	SHA1	Message	Date
Psychotoxical	fde7ab432f	feat: split AutoDJ into a standalone playback feature (#1124) ... * feat(playback): add transition-mode helper Centralise the crossfade/AutoDJ/gapless mutual exclusivity in one place instead of the scattered setter combinations across the toolbar, mini player and settings. AutoDJ stays encoded as crossfade + trim-silence, so the persisted flags and the audio engine are unchanged. * feat(queue): split AutoDJ into its own toolbar button + playlist submenu - AutoDJ becomes a standalone toolbar button (Blend icon) next to crossfade, driven by the shared transition-mode helper. The crossfade right-click popover drops the mode switch and keeps only the seconds slider. - Save + load playlist collapse into one Playlist button opening a small submenu, freeing up toolbar space. - queueToolbarStore gains a position-preserving rehydrate migration (legacy save/load -> playlist, autodj inserted after crossfade) with unit tests. - Toolbar customizer and all 9 queue locales updated to match. * feat(mini-player): standalone AutoDJ button, shared transition helper Mirror the queue toolbar: AutoDJ gets its own Blend button, the crossfade popover keeps only the seconds slider. The mini player now drives all three transitions through a single additive `mini:set-transition-mode` event handled by the shared helper, replacing the per-flag mini events. Drop the now-dead crossfade-mode CSS. * feat(settings): segmented track-transition picker, regroup playback Replace the crossfade toggle + inner crossfade/AutoDJ switch with a single Off | Gapless | Crossfade | AutoDJ segmented control (mirroring the Normalization picker above), driven by the shared transition helper — the mutual exclusivity now reads at a glance. Crossfade keeps its seconds slider; AutoDJ shows its content-driven explainer. The block is regrouped under "Track transitions" and "Queue behaviour" headings. Drops the now unused crossfade/gapless description and not-available i18n keys across all 9 locales and adds the new transition strings. * fix(queue): open the playlist submenu inward The playlist submenu inherited the crossfade popover's right:0 anchor and, sitting on the left of the toolbar, opened out under the main container. Anchor it left:0 so it stays inside the queue panel. Update the toolbar test for the new playlist submenu (save/load moved off the toolbar). * feat(settings): box playback sub-sections into panels Wrap Normalization, Track transitions and Queue behaviour each in their own bordered panel with an accent uppercase header (new reusable .settings-group classes), so the sections read as distinct blocks instead of one wall of text. Drops the thin divider that separated them. * docs: changelog, credits and what's new for AutoDJ standalone Fold the standalone-AutoDJ changes into the existing AutoDJ entry in the changelog and the in-app What's New, and add the credit (#1124).	2026-06-18 13:31:38 +02:00
cucadmuh	a6ee0668c8	feat(crossfade): AutoDJ — content-aware silence-trimming crossfade (#1122) ... * feat(crossfade): add "trim silence between tracks" toggle New persisted setting `crossfadeTrimSilence` (default off; existing installs rehydrate off via the persist default-merge). Surfaced in Settings -> Audio and in the crossfade popovers of the queue toolbar and the mini-player. Crossfade buttons now separate the two actions: left-click toggles crossfade on/off, right-click opens the settings popover (seconds + trim). Shared the mini popover positioning into useMiniAnchoredPopover (now backing both volume and crossfade). Mini bridge carries crossfadeSecs/crossfadeTrimSilence and gains mini:set-crossfade-secs / mini:set-crossfade-trim-silence. The actual silence-trimming playback behaviour is wired in a follow-up; this commit only persists the user intent. i18n added across 9 locales. * feat(crossfade): trim silence between tracks (waveform-driven) Wire the actual silence-aware crossfade behind the (default-off) crossfadeTrimSilence toggle. Detection is derived on the fly from the cached 500-bin waveform + track duration — no new analysis pass or cache fields. - waveformSilence.ts: computeWaveformSilence(bins, duration) → lead/trail silence + content bounds, using the peak curve, a low absolute cut and a per-side cap. Unit-tested. - A-tail (JS): handleAudioProgress advances the crossfade early, at contentEnd - crossfadeSecs, when the current track ends in real trailing silence, so the fade overlaps music. Guarded once per play generation. - B-head: audio_play gains an additive optional start_secs; the freshly built source is try_seek'd past the next track's leading silence before append, then seek_offset/samples_played are re-anchored so position is content-relative. Non-seekable / cold sources degrade to today. - Pre-buffer: crossfade next-track download + B-head probe moved to crossfadePreload.ts with a fixed ~30 s budget before the track needs to play (widened by trailing silence so the early advance keeps the budget). Also fired right after a seek into the window so jumping near the end still buffers in time. Checks: tsc, vitest (store suite + new units), cargo test/clippy for psysonic-audio. * feat(crossfade): recommend hot cache for trim; probe B-head regardless Add a "for reliable results, enable the Hot playback cache" note to the trim-silence toggle description across all 9 locales — hot cache keeps the next track on disk so it starts instantly past its lead silence. Fix: the leading-silence probe (B-head) now runs even when hot cache is on; only the redundant byte pre-download is gated on !hotCache. Without this, enabling hot cache (the recommended setting) would have skipped the probe and disabled leading-silence trimming. * feat(crossfade): content-driven smart crossfade overlap Smart crossfade derives the per-transition overlap purely from the waveform envelopes — max(A outro fade, B intro rise) clamped 0.5–12s — instead of the fixed crossfadeSecs ("work by fact"). The JS early advance arms the computed overlap and audio_play applies it through a new crossfade_secs_override (capping only this swap's fade); plain loud→loud endings fall back to the engine crossfade at crossfadeSecs. * feat(crossfade): "Crossfade | Smart crossfade" mode switch in UI Replace the standalone "trim silence" toggle with a Crossfade / Smart crossfade segmented control in settings and both crossfade popovers (queue toolbar + mini-player). Classic Crossfade shows the seconds slider; Smart crossfade is content-driven with no duration to set. Adds smartCrossfade / smartCrossfadeDesc strings to all nine locales and the "smart crossfade" search keyword. * feat(crossfade): don't double-fade a track that already fades out Decouple the outgoing track's fade-out from the incoming fade-in. When A carries its own recorded fade-out (outroFadeA ≥ 1s and ≥ B's intro rise), planCrossfadeTransition now sets outgoingFadeSec = 0; the engine then skips A's TriggeredFadeOut so A keeps full gain and its recording carries it down while B rises underneath — no more double attenuation that made A vanish early and B blare in. Hard-cut endings still get an engine fade over the overlap. audio_play gains outgoing_fade_secs_override (Some(0) = ride A's own fade), threaded via SinkSwapInputs.outgoing_fade_secs; the JS advance arms it alongside the overlap. * feat(crossfade): rename the smart crossfade mode to "AutoDJ" User-facing rename of the content-driven crossfade mode from "Smart crossfade" to "AutoDJ" across the settings segmented switch, the queue and mini-player popovers, all nine locales, and the settings search keywords. The underlying store flag (crossfadeTrimSilence) is unchanged. * feat(crossfade): standard ~2s blend for hard loud→loud meetings When AutoDJ trims a track's protective trailing silence and the loud ending butts straight into a loud intro, neither edge fades, so the old 0.5s anti-click floor sounded like an abrupt cut. Use a standard ~2s equal-power crossfade for that case (both edges analysed, nothing fades); real fade-outs/buildups keep their longer content-driven span, and the bare floor only survives when an envelope is missing. * fix(crossfade): keep B's fade-in across the B-head start-offset seek EqualPowerFadeIn::try_seek jumped straight to unity gain for any seek ≥100ms, which also hit the initial start-offset seek that skips the incoming track's leading silence — so a crossfaded track with trimmed lead silence popped in at full gain instead of fading in. Only skip the fade-in for mid-playback seeks (sample_count > 0); a seek before any audio has played keeps the fade-in. * feat(crossfade): gate AutoDJ early fade on next-track readiness The early, content-driven advance now fires only when the next track's audio is actually available — in the engine RAM preload slot (enginePreloadedTrackId) or local on disk (offline library, favourite-auto or hot-cache ephemeral) — via isCrossfadeNextReady(). Analysis alone is not enough: a cold, still-buffering stream would fade in over silence. When B isn't ready the gen guard stays unset so it re-checks on later ticks; if B never readies, the plain engine crossfade handles the transition (graceful degrade) instead of a broken fade. A RAM preload copy suffices — the full track need not be cached to disk. * feat(crossfade): suppress engine auto-crossfade for AutoDJ + eager preload With the hot cache off the readiness gate alone wasn't enough: the engine's progress task autonomously fires its crossfade audio:ended ~crossfadeSecs before the end, independently of JS, and would start a still-buffering next track and fade over it — an audible jump. - Engine: add autodj_suppress_autocrossfade flag (audio_set_autodj_suppress); the progress task treats it like crossfade-off, so the early timer never fires and audio:ended only comes from real source exhaustion / watchdog. - JS drives the transition: set the flag when a content fade is pending (wantEarly) and clear it for plain loud→loud / non-AutoDJ, so the normal engine crossfade is preserved there. When the next track never readies, A plays out and we degrade to a clean sequential start instead of a jump. - audio_preload gains an `eager` flag; the crossfade/AutoDJ pre-buffer passes it to skip the 8s start throttle so the RAM slot fills before the fade. * docs(changelog): AutoDJ content-aware crossfade (PR #1122) Add the 1.49.0 Added entry and the cucadmuh credits line for AutoDJ.	2026-06-18 02:15:20 +03:00
Psychotoxical	f9df918c72	feat(themes): community Theme Store + semantic-token refactor (#1009) ... * feat(themes): add semantic tokens for the theme-store contract (B0 P1) Additive: define --highlight, --accent-2, --bg-deep, --bg-elevated and --text-on-accent on the :root base as --ctp-* mappings. They resolve per-theme automatically and nothing consumes them yet (zero behaviour change) — groundwork for replacing direct --ctp-* use in components. * refactor(themes): components consume semantic tokens, not --ctp-* (B0 P2) Replace every direct --ctp-* reference in component/layout/track CSS and TSX inline styles with the readable semantic token (--bg-app, --accent, --highlight, --text-on-accent, …). --ctp-* now survives only as the Catppuccin palette layer the base maps from, and as the deliberate categorical rainbow in Composers/Genres/artistsHelpers (left untouched). This is the readable contract surface for the community theme store. Divergences (theme set a semantic var != its --ctp- source) are corrections — the element now uses the theme's real semantic colour. * feat(themes): add player-bar title/artist color tokens New optional --player-title / --player-artist, defaulting to --text-primary / --text-secondary so nothing changes unless a theme overrides them. Lets a theme give the now-playing readout its own colour as a plain token. * refactor(themes): token-only theme library (flatten, whitelist, one file per theme) Turn every built-in theme into a single self-contained [data-theme] var block of semantic whitelist tokens (plus the internal --ctp-* palette layer): - Flatten all themes: drop structural override rules, @keyframes, and global-token overrides (radius / shadow-elevation / transition / spacing / font / focus-ring). Signature player-bar readout colours are preserved via the new --player-title / --player-artist tokens. - Normalize the var blocks to the semantic whitelist: drop the alternate token vocabulary (nav-active / scrollbar / bg-input / success / border-default / ...); rename --success -> --positive and --border-default -> --border where no whitelist equivalent was set. Migrate the few components that read those tokens to the whitelist equivalents. - Split multi-theme files so each theme ships as its own file, making the built-in set 1:1 with the per-theme store packaging. Kept as-is (built-in, not flattened): the two colour-blind-safe accessibility themes, plus the two curated core skins. * chore(themes): remove seven themes retired after the token refactor These themes leaned on heavy structural overrides and were dropped rather than flattened. Full removal each: the CSS file(s), the index.css import, the Theme type union, and the ThemePicker entry. * feat(themes): granular tokens — track lists Wire track rows to per-region tokens: row hover (--row-hover), the now-playing row + indicator (--row-playing-bg / --row-playing-text), track title/artist/ number/duration text, column-header text, row dividers, and the resize-handle active colour. Covers the desktop tracklist, the shared song-row (Tracks hub / search), and the mobile tracklist. Drop a baked border fallback. Visual no-op. * feat(themes): granular tokens — cards Wire album and artist cards to per-region tokens (--card-hover-border, --card-title, --card-subtitle, --card-placeholder-bg). Visual no-op. * fix(themes): drop undefined/baked colour aliases Replace the undefined --bg-surface (resolved to nothing — broken placeholder backgrounds and filter input) with --card-placeholder-bg / --input-bg, and the baked-hex aliases --color-error / --color-warning with --danger / --warning so themes can actually recolour them. * feat(themes): Spectrum demo theme + trim unused cascade tokens Add a loud built-in demo theme that gives each region its own hue (sidebar green, player pink, lists cyan, cards gold, menus red, controls blue) so the per-region granularity is obvious when you switch to it. Drop two unused cascade tokens (--sidebar-text-active, --row-active-bg) and the unused on-media block (those media surfaces stay static by design). * style(themes): make Spectrum demo brutally loud Full-saturation neon per region (toxic green sidebar, magenta player, cyan lists, acid-yellow cards, blood-red menus, electric-blue controls, purple scrollbar) so the per-region separation is unmistakable. The earlier soft tints were too subtle to read. * feat(themes): name the granular demo theme Braindead * feat(themes): granular per-region tokens — cascade layer + sidebar Add an optional per-region token layer (semantic-cascade.css) so a theme can recolour individual regions — sidebar hover, player controls, list rows, menus, inputs, on-media surfaces — independently of the global tokens. Every token defaults to its base token (or a media-safe literal), so this is a visual no-op until a theme overrides one; it only adds control points. Wire the sidebar region as the first consumer and drop the baked grey fallbacks (--bg-tertiary, etc.) that no theme could reach. * feat(themes): granular tokens — controls, menus, scrollbar Wire inputs, buttons, sliders, the custom-select, context menus, submenus and modals to per-region tokens, and tokenise the scrollbar. Complete B0 by dropping the last direct --ctp-* references in the input/button/progress/ scrollbar utility CSS. Fix three undefined-token bugs that fell back to nothing (so no theme could reach them): --surface-2 (context-menu hover had no highlight), --bg-surface (submenu create-input had no background), and the baked grey fallbacks in the custom-select. Every other new token defaults to today's value — a visual no-op that only adds override points. * feat(themes): granular tokens — player bar Wire the desktop player bar's transport controls, time toggle, and overflow menu to per-region tokens (--player-control, --player-time-toggle-*, etc.). Fix the undefined --surface-hover/--surface-active grey fallbacks on the time toggle. Visual no-op; defaults match today's values. * chore(themes): remove empty theme stub files Six theme CSS files were reduced to comment-only stubs by the flatten sweep but their files and @import lines remained. Five are empty structural companions of now-flattened themes (morpheus, p-dvd, aero-glass, luna-teal) and two are orphans of cut themes (order-of-the-phoenix, pandora). Removed the files and their imports. * feat(themes): runtime injection foundation for the theme store Plumbing for installed community themes ahead of the in-app store UI, nothing user-visible yet: - installedThemesStore: persisted (localStorage) record of installed community themes incl. their CSS text, so an active community theme is available synchronously at startup (no flash, fully offline). - themeInjection: reconcile <head> <style data-installed-theme> elements with the store; lightweight defense-in-depth sanitize on top of CI. - themeRegistry: jsDelivr registry client with a 12h localStorage cache and stale-on-error fallback. - App: inject installed themes before applying data-theme, in both webviews. - themeStore: widen the Theme type to accept dynamic installed ids. * feat(themes): dedicated Themes settings tab Move theme selection and the day/night scheduler out of Appearance into a new dedicated Themes tab — the future home of the community Theme Store. Appearance keeps grid columns, visual options, UI scale, font and seekbar. - ThemesTab: theme picker + scheduler (relocated verbatim). - AppearanceTab: drop the two relocated sections + now-unused imports. - Register the tab in settingsTabs (Tab union, resolveTab, search index) and Settings (tab bar, render, label map). - i18n: settings.tabThemes in all 9 locales. * feat(themes): community Theme Store browse + install Add the Theme Store section to the Themes tab: - Fetch the jsDelivr registry (12h cache, stale-on-error fallback). - Search by name/author/description + filter by light/dark + refresh. - Per-row CDN thumbnail, name, author, description and actions: Install / Apply / Update / Uninstall. Installing fetches the CSS, persists it (localStorage) and the runtime injection applies it; uninstalling the active theme falls back to the matching core. - Rating slot left reserved (deferred). - i18n: themeStore* keys in all 9 locales. * feat(themes): slim bundle to fixed cores + flat Themes tab Remove the 86 store palettes (incl. braindead) from the app bundle — the CSS files, their index.css imports, the Theme union and the picker data — leaving only the six fixed cores (Catppuccin Mocha/Latte, Kanagawa Wave, Stark HUD, Vision Dark/Navy). Everything else installs from the store. Themes tab is rebuilt flat (no collapsible accordions): - "Your Themes": one card grid of the fixed cores + installed community themes; click to apply, uninstall on community ones (active theme falls back to the matching core). Catppuccin prefix on Mocha/Latte; a CVD-safe pill on the colour-blind-safe Vision themes. - Scheduler day/night options include installed themes. - Theme Store: alphabetical order, thumbnail lightbox, and a submit hint above the search linking to the themes repository. - Nav order: Servers, Library, Audio, Themes, Appearance, Lyrics, … - ThemePicker accordion removed; fixed-theme data moved to fixedThemes.ts. - i18n for all new strings across 9 locales. * feat(themes): reset removed-from-bundle themes to a bundled fallback After slimming the bundle to the six fixed core themes, a profile upgraded from an older build may have an active or scheduler theme that is now store-only and not installed — it has no [data-theme] block and would render as unstyled :root. Reset any theme/themeDay/themeNight that is neither bundled nor installed to a bundled fallback: Mocha for the main + night slots, Latte for the day slot. Runs synchronously in runPreReactBootstrap, rewriting the persisted selection in localStorage before React mounts (no flash; Zustand rehydrates after first paint). No auto-install and no network — the fallback is always a bundled theme, so it works offline. * feat(themes): floating back-to-top button on the Themes tab The Themes tab can get long (theme grid + scheduler + full store list), so add a floating back-to-top affordance that appears once the page is scrolled and smooth-scrolls to the top. It is portalled into the route host and positioned absolute against it — the main scroll viewport sets contain: paint, which would otherwise make position: fixed resolve against the scrolling box and drift with the content. Reusable component (scroll viewport id + threshold props); i18n common.backToTop added in all nine locales. * feat(themes): accessibility + state polish for the Theme Store - Reuse the shared CoverLightbox for the thumbnail preview instead of a second inline dialog — gains a visible close button and a focus-managed, portalled dialog, and drops duplicated markup. - Theme cards expose aria-pressed so assistive tech announces the selected theme, not just the visual check. - Transient store messages get live-region roles (loading/empty/install failure = status, fetch error = alert). - Thumbnails degrade gracefully when offline/missing (hide the broken-image glyph; the thumbnail button no longer stretches with the row, so its background can't show as letterbox bars). * feat(themes): larger store-row thumbnails (120x75 -> 200x125) The list previews were too small to make a theme out; bump the display size (same 1.6 aspect). Thumbnails are now served at 720x450, so the larger display stays crisp. * fix(themes): bust thumbnail cache on registry change jsDelivr serves theme thumbnails with a 7-day max-age, so when a thumbnail is updated the webview keeps showing its cached old image (the path is unchanged). Append the registry's generatedAt as a cache-busting query to the thumbnail URLs (list + lightbox); it changes on every themes push, so a registry refresh makes the webview re-fetch and reflect the current CDN image instead of a stale one. * docs(themes): changelog + credits for the Theme Store Add the 1.48.0 "Themes — community Theme Store" changelog entry (PR #1009) and the matching line in the Psychotoxical credits. * fix(themes): address PR review (uninstall hygiene, validation, polish) Uninstall/scheduler & validation: - uninstallTheme() repairs every selection slot (active + day + night), not just the manual one, and is shared by both uninstall buttons (dedup). - Validate theme CSS at install time and skip persisting CSS that won't inject (no more "installed/active but renders nothing" with no feedback). - Harden the runtime validator: exactly one rule, scoped exactly to the theme's [data-theme='<id>'] selector (no unscoped/foreign selectors), no at-rules, url() only data:, no expression()/javascript:, size-capped. Tokens & polish: - Fix three dangling undefined tokens (--surface-2 x2, --bg-surface). - Finish the warning/success token sweep (--warning / --positive, themeable). - Apply the active theme synchronously before React mounts (no first-frame flash) and inject installed themes up front. - One-time, dismissible notice when the slim-bundle migration reset a theme. - Update badge uses semver, not string inequality. - Offline/stale indicator in the store; cross-window theme sync; drop the now dead REMOVED_THEME_REMAP and Card.mode field. Tests: themeInjection (validator + sync), themeRegistry (cache/force/stale/ malformed), uninstallTheme (slot repair), migration notice. i18n in all nine locales. Full suite green (1755 tests). * test(bootstrap): cover startup theme apply + cross-window sync The review fixes added applyThemeAtStartup / installCrossWindowThemeSync to bootstrap.ts (a hot-path file) without tests, dropping its coverage to 68.3% and failing the frontend hot-path coverage gate (>=70%). Add unit tests for both (and the no-op / malformed-storage paths); bootstrap.ts is back to ~98%.	2026-06-07 02:47:33 +02:00
Frank Stellmacher	6cc227d761	fix(artist-info): id-gate fetchers, share ArtistCard, square hero (#739) ... * fix(artist-info): id-gate fetcher tuples, reuse ArtistCard on ArtistDetail The cache-mismatch bug PR #732 fixed in `NowPlayingInfo.tsx` had the same shape inside `ArtistCard` on the NowPlaying page: `useNowPlayingFetchers` returned `artistInfo` for the previously-current artist for one render after `artistId` changed, and `CachedImage` persisted that mismatched blob under the new `artistInfo:<new-id>:hero` key in IndexedDB — sticky "previous artist" image on every subsequent track. Apply the same `{ id, value }` tuple pattern from PR #732 inside the hooks themselves so every consumer is safe by construction: - `useNowPlayingFetchers`: gate `artistInfo`, `songMeta`, `albumData`, `discography` on id-match at the return. Late-arriving resolves for a stale id can no longer overwrite the displayed value. - `useArtistDetailData`: same for `info`. Required because the `ArtistDetail` bio card now uses `CachedImage` via the shared `ArtistCard` (previously raw `<img>`, no persistence hazard). Unify `ArtistDetail`'s inline "About the Artist" block onto the same shared `ArtistCard` so there is one source of truth for hero / bio / similar rendering. New optional props: `onNavigate?` (omitted on `/artist/:id` since the user is already there), `coverFallback` (coverArt fallback when artistInfo has no hero image), `hideArtistName` (avoid duplicating the hero name), `hideSimilar` (ArtistDetail has its own similar-artists section). Tests cover the gating contract for both hooks (incl. stale-resolve race) and the `ArtistCard` prop matrix. * fix(artist-image): square queue info hero, drop artist-avatar glow - Queue Info bar's artist hero was rendered in a 16:10 wrap with `object-fit: cover`, so portrait photos lost top/bottom equally while landscape ones lost the sides — perceived as cropped even on roughly square sources. Set the wrap to 1:1 so the crop is symmetric and matches the typical square framing of artist photography. - `ArtistDetail` extracted the cover's accent colour on every image load and rendered a 36px / 8px-spread `boxShadow` ring around the avatar. Drop the glow, the state, the one-shot reset effect, the prop-passing through `ArtistDetailHero`, and the now-orphaned `extractCoverColors` import on this page. `extractCoverColors` itself stays in place (still used by `useFsDynamicAccent`). * docs(changelog): artist-info image fix extension + UI tweaks (PR #739)	2026-05-17 00:43:05 +02:00
cucadmuh	3cc172723d	fix(ui): split album and track artists (OpenSubsonic) (#696) ... * fix(ui): split OpenSubsonic album and track artists in header and player Album detail header uses albumArtists from album or child songs; player bar, mobile player, and mini player use structured track artists with per-id links. Adds deriveAlbumHeaderArtistRefs helper and OpenArtistRefInline. Fixes #552 * docs: changelog and credits for OpenSubsonic artist links (PR #696)	2026-05-14 21:56:39 +03:00
Frank Stellmacher	4b4cf42167	refactor(styles): split components.css into per-section files (#657) ... components.css (14205 LOC) → 84 per-section files in src/styles/components/ + an index.css that imports them in original cascade order. Same approach as the theme.css split: top-level sections are detected by single-dash or 3+ dash header decoration (/^\/\* ─(?: |─{2,})/), 2-dash sub-sections stay inside their parent. Concatenating in @import order reproduces the original byte stream (+1 trailing newline, cosmetic). Each section is now self-contained — touching Tracklist, Modal, Hero, Sidebar, etc. only opens one focused file. Generated via /tmp/split-components-css.mjs.	2026-05-13 19:10:11 +02:00