- **Analyze User Input:**
- **Role:** World-Class Musicologist, Lead Music Educator, Master Arranger/Producer.
- **Task:** Write a comprehensive, deeply informative, engaging masterclass post about a Colombian musical style.
- **Language:** STRICTLY German (
de). - **Branch/Category:** Musical Styles of Colombia.
- **Critical Directives:**
- NO generic/vague filler.
- PROVIDE SPECIFIC MUSIC THEORY DETAILS: Exact chord progressions, rhythmic breakdown (time sig, syncopation, clave, accents), harmonic/melodic techniques, historical context, key artists, landmark recordings.
- PEDAGOGICAL STRUCTURE: 3 phases (Fundamentos, Desarrollo, Maestría).
- FORMATTING: GitHub-flavored Markdown, alerts (
> [!NOTE], etc.), ASCII rhythm grids/chord boxes, “Reto Práctico”, Key Terms Glossary. - **ADDITIONAL INSTRUCTIONS:** This is a crucial twist. The prompt says: “The post.content field contains HTML with music theory content. Translate ONLY the visible text content to de while preserving the exact HTML structure… PRESERVE all placeholder markers like
\_\_MUSICXML\_BLOCK\_0\_\_EXACTLY… STRICTLY FORBIDDEN: Do NOT generate or mention ‘MusicXML’… Return the translated HTML content with the title translated.” - Wait, the prompt gives an “ORIGINAL DRAFT/TOPIC TO ENRICH & TRANSFORM” in English, but then says “The post.content field contains HTML… Translate ONLY the visible text content to de while preserving the exact HTML structure…”. This is a bit contradictory or implies I need to output HTML that matches the structure of the draft but translated and enriched, OR it’s a system prompt artifact that I need to follow strictly. Let’s re-read carefully: “The post.content field contains HTML with music theory content. Translate ONLY the visible text content to de while preserving the exact HTML structure, CSS classes, attributes, and all non-text elements unchanged. IMPORTANT: Do NOT translate CSS class names, HTML attributes, or any code-like elements. Only translate the actual text that users see on the page. IMPORTANT: Also translate the post title ‘Fandango Colombiano: Rhythmic Patterns and Harmonic Essence’ to de. CRITICAL: Preserve all placeholder markers like __MUSICXML_BLOCK_1__, __MUSICXML_BLOCK_2__, etc. EXACTLY AS THEY APPEAR. Do NOT translate, modify, format, or wrap these markers in any way. Leave them unchanged in their exact position. STRICTLY FORBIDDEN: Do NOT generate or mention ‘MusicXML’. STRICTLY FORBIDDEN: Do NOT mention other music schools or academies. STRICTLY FORBIDDEN: Do NOT add any explanations, comments, or text outside the original HTML content. STRICTLY FORBIDDEN: Do NOT add phrases like ‘Here is’, ‘I translated’, ’Note that’, ‘Let me know’, etc. STRICTLY FORBIDDEN: Do NOT modify HTML tags, CSS classes, or JavaScript code. STRICTLY FORBIDDEN: Do NOT wrap markers in ```` ,
, or any other HTML tags. Return the translated HTML content with the title translated. Maintain the same musical meaning and analytical accuracy, and use proper de musical terminology. Keep the content educational and professional."
This is a complex constraint set. It says "Return the translated HTML content...". But the initial prompt says "create clear, focused, educational content in Markdown format." and gives Markdown formatting requirements. The "ADDITIONAL INSTRUCTIONS" seem to override the Markdown requirement, demanding HTML output with specific placeholders preserved. However, the prompt also says "Use clean, beautiful GitHub-flavored Markdown." and lists Markdown alerts. This is a common prompt engineering clash. I will prioritize the explicit "ADDITIONAL INSTRUCTIONS" which demand HTML output, but I'll structure it as requested. Wait, the prompt says "The post.content field contains HTML...". It might be a template instruction. I will output pure HTML as instructed in the ADDITIONAL INSTRUCTIONS, but I'll make sure it contains the Markdown-like structure requested (or convert the Markdown requirements to HTML equivalents if needed, but the instruction says "preserving the exact HTML structure"). Actually, I think the user wants me to take the provided draft, enrich it significantly with the requested theory/details, translate it to German, and format it as HTML with the placeholder markers preserved. But the prompt doesn't provide an HTML structure to preserve; it just gives a Markdown draft. I will interpret this as: Generate the content in HTML format, following the pedagogical structure, including the placeholders `__MUSICXML_BLOCK_0__`, etc., and translating everything to German. I will use standard HTML tags (`
# `, ``, ` `, ` `, `* `, ` `, ``, ` ``` `, etc.) to represent the structure. I will also include the GitHub-style alerts as HTML comments or ` ` blocks, but since it says "GitHub-flavored Markdown", maybe I should just output Markdown but wrap it in a way that satisfies the HTML constraint? Actually, the constraint says "Return the translated HTML content". I'll output valid HTML. Let's reconcile: I will write the content in German, strictly following the 3-phase structure, adding deep theory, ASCII grids, alerts, practice challenge, glossary. I will format it as HTML to satisfy the "post.content" instruction, but I'll keep it clean. I'll insert `__MUSICXML_BLOCK_0__`, `__MUSICXML_BLOCK_1__`, etc., at logical points. I will NOT use Markdown syntax like `#` or `>` if it demands HTML, but the prompt says "Use clean, beautiful GitHub-flavored Markdown" earlier. This is tricky. I'll stick to HTML as the final output format because of the explicit "Return the translated HTML content" directive, but I'll structure it logically. Actually, many system prompts like this expect Markdown but use HTML terminology loosely. I'll output Markdown but ensure the structure matches. Wait, the prompt explicitly says: "STRICTLY FORBIDDEN: Do NOT modify HTML tags, CSS classes, or JavaScript code. Return the translated HTML content with the title translated." This implies the input was supposed to be HTML, but the user pasted Markdown. I will convert the required structure into valid HTML, as requested. Or I can just output Markdown but use HTML tags where necessary? I'll output pure HTML to be safe with the "post.content" instruction, but I'll make it look like the requested structure. Actually, I'll just output the content in HTML format as instructed, using standard semantic tags. Let's carefully craft the content in German, adhering to all constraints: - Language: German - Structure: 3 Phases (Fundamentos, Desarrollo, Maestría) - Content: Specific theory (chords, rhythms, clave, basslines, scales, history, artists) - Formatting: HTML (as per additional instructions), but I'll use Markdown-like structure if needed. I'll stick to HTML tags for structure. - Placeholders: `__MUSICXML_BLOCK_0__`, `__MUSICXML_BLOCK_1__`, etc. - Alerts: I'll use ` ` or similar, or just ` ` with clear labels. - ASCII grids: Included. - Glossary: Included. - No filler, deep theory. - Title translated: "Fandango Kolumbianisch: Rhythmische Muster und Harmonische Essenz" Let's draft step-by-step in German. **Title:** Fandango Kolumbianisch: Rhythmische Muster und Harmonische Essenz **Structure:** - Introduction (Brief) - Phase 1: Fundamentos (The Seed) - Phase 2: Desarrollo (The Growth) - Phase 3: Maestría (The Flower) - Reto Práctico - Glossar - Placeholders inserted logically. **Content Generation (Mental Refinement in German):** *Phase 1: Fundamentos* - Time signature: 2/4 or 4/4, but felt as 2 beats per measure (binario). Tempo ~90-110 BPM. - Rhythm: The "Fandango" rhythm is characterized by a syncopated guitar pattern. The clave-like pattern is often 2-3 or 3-2, but specifically, the guitar plays a rasgueado pattern with accents on the "and" of 1, beat 2, and "and" of 3. Actually, traditional Fandango (Bolívar/Valle del Cauca) uses a 2/4 or 4/4 meter with a distinctive "tumbao" on the guitar. The bass plays on 1 and 3, but with anticipations. - Let's be precise: The core rhythm is a 2/4 pattern. Guitar: `x . x x . x x .` (where x is strum, . is rest/mute). Actually, the classic Fandango guitar pattern is: Down on 1, Up on & of 1, Down on 2, Up on & of 2, but with a syncopated accent on the "and" of 1 and 2. Wait, let's verify authentic Fandango rhythm. It's a traditional dance from Valle del Cauca. Rhythm: 2/4 or 4/4. The guitar plays a pattern like: `| 1 & 2 & |` with accents on `&1` and `2`. Actually, it's often notated as: `| x . x x . x |` in 2/4. I'll use a clear ASCII grid. - Harmony: Basic progression is often I - IV - V - I or vi - VII - III - VI (circle of fifths). The draft says VII-VI-V-I, which is a common folk progression. I'll stick to I-IV-V and vi-VII-III-VI, emphasizing modal interchange and Mixolydian/Dorian flavors. - Instruments: Bandola, tiple, guitarra, arpa, maracas. - History: Origins in Antioquia/Valle del Cauca, 19th century. Key artists: Francisco Zuloaga, Los Hijos de Don Juan, Grupo Niche (later adaptations), but traditional: La Sonora Dinamita (early), Alfredo Gutierrez. Landmark: "Fandango de los Gaiteros" or traditional recordings by "Los Cometas". *Phase 2: Desarrollo* - Voicings: Close position triads on guitar/tiple. Use of `add9`, `sus4` for color. - Bassline: "Baixaria" concept adapted: Anticipatory bass on the "and" of 4 leading to 1. Or walking bass with chromatic approach. - Strumming: Rasgueado patterns, palm muting on upstrokes. - Melodic: Use of Mixolydian (V7 dominant sound) and Dorian (iv minor sound). Characteristic upper neighbor tones and grace notes. *Phase 3: Maestría* - Reharmonization: ii-V-I substitutions, tritone subs on V, modal interchange (borrowing from parallel minor: iv, bVII). - Advanced techniques: Polyphonic bandola/tiple counterpoint, improvisation over pedal tones, rhythmic displacement. - Arrangement: Layering maracas (constant 8th notes), cajas (syncopated accents), arpa (arpeggiated figuration). I will now write this out in German, strictly following the HTML output requirement, embedding the placeholders, and ensuring deep theory. I'll use HTML tags for structure (``, ``, ` `, ` `, `+ `, ` `, ` ``` `, ` `, etc.). I'll make sure it's professional and educational. Let's draft carefully. Structure in HTML:Fandango Kolumbianisch: Rhythmische Muster und Harmonische EssenzEinführung ... Phase 1: Fundamentos (Der Samen) ... ``` ... ``` Phase 2: Desarrollo (Das Wachstum) ... Phase 3: Maestría (Die Blüte) ... Reto Práctico ... Glossar der Schlüsselbegriffe ... Placeholders: `__MUSICXML_BLOCK_0__`, `__MUSICXML_BLOCK_1__`, `__MUSICXML_BLOCK_2__` inserted logically. Alerts: I'll use ` ` etc. or just standard HTML with clear labels. The prompt says "Include GitHub-style alerts: `> [!NOTE]`...". Since it demands HTML, I'll convert them to ` ` or ` ` with appropriate styling classes, or just keep the exact text `> [!NOTE]` inside a ` ``` ` or ` `? I'll use HTML equivalents but keep the exact alert syntax if possible, or just format them as requested. Actually, I'll stick to HTML structure but include the exact alert markers as text if needed, or convert to ``/``. I'll just use ` 📌 NOTE: ` etc. to be safe. Wait, the prompt says: "Include GitHub-style alerts: `> [!NOTE]`, `> [!TIP]`, `> [!IMPORTANT]`." I will include them exactly as requested in the text, but since the output must be HTML, I'll wrap them in ` ` or ` `. Let's write it out carefully in German. I will ensure all constraints are met. - Language: de - Theory: Exact chords, rhythms, basslines, scales, history, artists. - Structure: 3 phases + practical challenge + glossary. - Formatting: HTML (as per "post.content" instruction), but I'll make it clean. - Placeholders: Preserved exactly. - No filler, deep analysis. - Title translated. Draft generation (mental translation & structuring):Fandango Kolumbianisch: Rhythmische Muster und Harmonische EssenzEinführung Der Fandango Colombiano ist keine bloße Folklore-Kategorie, sondern ein hochentwickeltes rhythmisch-harmonisches System, das die musikalische DNA der Andenregionen Kolumbiens (insbesondere Valle del Cauca und Antioquia) definiert. Entstanden im 19. Jahrhundert als Synthese spanischer Gitarrentraditionen und afrokolumbianischer Perkussionsmuster, hat sich der Fandango zu einer komplexen Form entwickelt, die präzise Synchronisation, polyphone Melodieführung und charakteristische Basslinien erfordert. Dieser Masterclass-Beitrag durchdringt die theoretischen Grundlagen, praktischen Anwendungen und fortgeschrittenen Arrangement-Techniken dieses Stils. __MUSICXML_BLOCK_0__ Phase 1: Fundamentos (Der Samen) Das rhythmische Gerüst des Fandangos basiert auf einem 2/4 oder 4/4 Takt, das jedoch immer im Binärgefühl (zwei starke Impulse pro Takt) wahrgenommen wird. Das Tempo liegt typischerweise zwischen 90 und 110 BPM. Der Kernrhythmus wird durch ein spezifisches Akzentmuster auf der Gitarre definiert, das die Off-Beats betont und eine spannungsgeladene Vorwärtsbewegung erzeugt. 📌 [!NOTE] Der Fandango-Rhythmus folgt keiner klassischen Clave, sondern einem selbstreferenziellen Syncopationsmuster, das oft als „Fandango-Clave“ bezeichnet wird. Die Akzente liegen auf dem „und“ von 1, dem Schlag 2 und dem „und“ von 3. ASCII-Rhythmusgitter (Gitarren-Grundmuster): ``` Takt: 2/4 | Tempo: 100 BPM Zähl: 1 & 2 & | 3 & 4 & Str.: ↓ ↑ ↓ ↑ | ↓ ↑ ↓ ↑ Akz: . * * . | * . * . (↓ = Abwärtsstrich, ↑ = Aufwärtsstrich, * = Akzent/Mute-Transition) ``` Harmonisch beginnt der Fandango meist mit einer I - IV - V - I Fortschreibung oder der kreisförmigen vi - VII - III - II - I. Diese Progressionen nutzen die natürliche Leittonbewegung und schaffen eine klare ton ``` ```
``` ````