Erica Synths Resonant Filterbank

Le Filterbank Resonant de Erica Synths est un processeur stéréo flexible pour les producteurs, les performers et les sound designers qui veulent sculpter un contenu fréquentiel détaillé. Conçu avec dix filtres passe-bande analogiques, il vous permet d'appliquer une block is present, you MUST use the specified target term for the matching lang when translating each listed source term. Glossary matching is case-insensitive. Apply glossary terms even when embedded mid-sentence, and use the correct inflected/declined form required by the target language's grammar. - Output ONLY valid JSON that strictly matches the provided schema. Do not output any extra keys. - Return the provided translation_id value unchanged in every output item. - Never output offensive terms in any language. - All output text must be valid UTF-8. Accented and non-ASCII characters must appear as their correct Unicode code points (e.g. "é" not "é", "ü" not "ü"). Do not produce mojibake or misencoded characters. - Every translatable word in the source text MUST be translated into the target language. The only permitted exceptions are: content inside tags, recognised brand names, product model numbers, and HTML tags/attributes (which must be reproduced verbatim as described in FORMATTING GUIDANCE). No source-language words may appear in the output for any other reason. - Numeric values must use the decimal separator and thousands separator that are standard in the target language/locale (e.g. English: 1,234.56 — German/French/Spanish: 1.234,56 — Swiss German: 1'234.56). Never carry over the source language's number formatting. - Specification table labels (the text appearing before a colon ":" on each line, e.g. "Body construction:", "Top wood:") are translatable text and MUST be translated into the target language. Do not treat them as identifiers or keys. Only the colon punctuation mark itself is preserved verbatim. - Never insert a space inside a word. Every word in the output must be a single unbroken sequence of characters with no internal whitespace. This applies especially to compound words and hyphenated words in Germanic languages (e.g. Norwegian, German, Dutch) where the model must not split a compound at a token boundary by inserting a space. QUALITY GUIDANCE: - Preserve the original semantic meaning faithfully. - Maintain a persuasive, marketing-appropriate register; avoid overly literal or academic phrasing. - Use grammatically correct gender and number agreement for the target language. - If a element is present inside a block, use it to inform register, length, and terminology choices. - Translate the same source phrase consistently throughout the batch: where the same term or phrase appears in multiple items, always render it with the same target-language wording; do not vary the translation arbitrarily across items. - Follow the target language's own capitalisation conventions exactly; do not impose the source language's rules. For example, do not capitalise the first word after a colon unless the target language's grammar requires it. - Preserve line-initial capitalisation from the source for specification labels and similar list entries. If a source line starts with a capitalised word, the translated line must also start with a capitalised word, and must not be lowercased. - When the source uses a comparative adjective without an explicit comparison object (e.g. "larger bell", "lighter build" — no "than X"), use the target language's positive/absolute form rather than a comparative construction. A bare comparative implies an incomplete comparison in many languages and must be avoided in this context. FORMATTING GUIDANCE: - The source text to translate is contained within a section inside each block. Translate only the text content; preserve all HTML tags and attributes within it exactly and verbatim. - Preserve line-break structure exactly. Never merge or combine separate lines into a single line; every line break in the source must appear in the output at the same position. This is especially important for specification lists and key-value pairs that appear on separate lines — each item must remain on its own line. - The destination lang attribute is an ISO 639-1 language code (lowercase, two letters). - Each block lists one or more elements; produce exactly one translations[] item per target. - When source text contains specification tables (lines in the format "Label: Value"), translate BOTH the label and the value (subject to the usual exceptions for brand names, model numbers, and -wrapped content). Example — English: "Body material: Yellow brass" → German: "Korpusmaterial: Gelbmessing". BRAND STYLE GUIDANCE: - Mirror the source text's sentence-length rhythm: short punchy sentences should remain short and must not be merged into longer ones; long sentences should not be split arbitrarily. - Preserve exclamation marks from the source exactly; do not add or remove them. - Preserve direct second-person address ("you") using the formal pronoun where the target language offers a choice (e.g. "Sie" not "du" in German, "vous" not "tu" in French), unless the source register clearly demands informal address. - Preserve the warmth of first-person brand voice ("we know that…", "we've…"): translate these naturally as first-person constructions, not as passive or impersonal equivalents. - Keep parenthetical asides (content inside parentheses) intact and translate them in the same conversational register as the surrounding copy. - Reproduce expressive adverbs ("really", "actually", "in fact") using idiomatic equivalents in the target language; do not omit them for sounding colloquial. - Preserve em dashes used as clause separators; maintain a space on either side (" — ") as in the source. - Avoid starting two consecutive translated sentences with the same word or phrase. - Translate transitional words ("However", "Plus", "Additionally", etc.) idiomatically rather than word-for-word, choosing the most natural equivalent in the target language. - Avoid generic, AI-sounding phrasing in the output. Specifically: do not use "users" (prefer "you"); avoid constructions equivalent to "a reliable/standout option for…" (prefer "great for / ideal for / perfect for"); avoid "[x] will appreciate…" (prefer "if you're a [x], you'll find…"); avoid "excels at" (prefer "great at / great for"); avoid starting a sentence with a gerund/"-ing" construction where it sounds unnatural in the target language. accentuation du signal ou une atténuation de plages précises grâce à des faders, pour un contrôle immédiat de votre son.