Analyze User Input:

• Role: World-Class Musicologist, Lead Music Educator, Master Arranger/Producer
• Topic: Sampling: Manipulating Recorded Audio as Raw Material
• Language: Strictly German (de)
• Category: Music Production and Technology
• Critical Directives:
  • NO generic/vague filler
  • PROVIDE SPECIFIC music theory details (chord progressions, rhythmic breakdown, harmonic/melodic techniques, historical context, pioneers, landmark recordings)
  • PEDAGOGICAL STRUCTURE: 3 phases (Fundamentos, Desarrollo, Maestría)
  • FORMATTING: GitHub-flavored Markdown, GitHub alerts (> [!NOTE], etc.), ASCII rhythm grids/chord boxes, Practice Challenge, Key Terms Glossary
  • EMOJIS: Use naturally
  • COLORS: Highlight key terms using text or text
  • DEGREE COLOR SYSTEM: Not directly applicable to sampling, but I’ll keep it in mind if needed (though sampling isn’t strictly scale-degree focused, I can adapt if relevant, or just follow the color directive for key terms)
  • DIDACTIC TOOLS: Tables and lists
  • STRICTLY FORBIDDEN: YAML, JSON, structured data blocks, pure Markdown only
  • Structure: # Title, ## Introduction, ## Main Concept, ## Examples, ## Practical Summary (Wait, the prompt says “Structure: # Title, ## Introduction, ## Main Concept, ## Examples, ## Practical Summary.” but also says “PEDAGOGICAL STRUCTURE (Divide into 3 distinct learning phases): Phase 1: Fundamentos, Phase 2: Desarrollo, Phase 3: Maestría”. I will combine these requirements logically: I’ll use the requested structure but integrate the 3 phases into the main content sections, or explicitly structure the post around the 3 phases while keeping the required headings. I’ll adapt to: # Titel, ## Einleitung, ## Phase 1: Fundamentos (Der Samen), ## Phase 2: Desarrollo (Das Wachstum), ## Phase 3: Maestría (Die Blüte), ## Beispiele, ## Praktische Zusammenfassung, plus the required Practice Challenge and Glossary.)
  • CRITICAL ADDITIONAL INSTRUCTIONS:
    • 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, 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 ‘Sampling: Manipulating Recorded Audio as Raw Material’ to de. CRITICAL: Preserve all placeholder markers like __MUSICXML_BLOCK_0__, __MUSICXML_BLOCK_1__, 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.”

    • WAIT. This is a contradiction. The prompt starts with a detailed request for a Markdown masterclass post with specific formatting, phases, alerts, ASCII grids, etc. But then at the very end, it adds a strict instruction that sounds like a system prompt for an HTML translation task: “The post.content field contains HTML… Translate ONLY the visible text content to de while preserving the exact HTML structure… STRICTLY FORBIDDEN: Do NOT add any explanations, comments, or text outside the original HTML content… Return the translated HTML content with the title translated.”
    • This is a common prompt injection/conflict scenario. The final instruction is extremely specific and overriding: “STRICTLY FORBIDDEN: Do NOT add any explanations, comments, or text outside the original HTML content.” and “Return the translated HTML content with the title translated.”
    • However, the user provided an “ORIGINAL DRAFT/TOPIC TO ENRICH & TRANSFORM” in Markdown, not HTML. The prompt says “The post.content field contains HTML with music theory content.” but didn’t actually provide any HTML. It provided a Markdown draft.
    • I need to reconcile this. The safest approach is to follow the explicit structural and formatting requirements for the Markdown masterclass, but translate everything to German as requested. I will ignore the contradictory HTML/translation-only constraint if it conflicts with the explicit request to generate a comprehensive Markdown masterclass with specific sections, because the user explicitly provided a Markdown draft and asked to “enrich & transform” it into a masterclass post in Markdown. The HTML instruction seems like a copy-paste artifact from another prompt. I will prioritize the main explicit instructions: German language, Markdown format, 3 phases, specific music theory details, GitHub alerts, ASCII grids, practice challenge, glossary, emojis, color syntax for key terms, and the requested structure. I will carefully craft the content to meet all the positive constraints.
    • Wait, 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…” This is likely a template mismatch. I will generate the Markdown masterclass as requested in the main body, fully in German, incorporating all the specific directives (phases, theory details, formatting, etc.). I will make sure it’s pure Markdown. I will translate the title and all content to German. I will strictly follow the “DEGREE COLOR SYSTEM” and color highlighting rules. I will use the exact structure requested: # Titel, ## Einleitung, ## Hauptkonzept (or integrate the 3 phases here), ## Beispiele, ## Praktische Zusammenfassung, plus the required sections.
    • Let’s align the structure exactly as requested: # Titel, ## Einleitung, ## Hauptkonzept, ## Beispiele, ## Praktische Zusammenfassung. I’ll embed the 3 phases within the Main Concept or as subsections to satisfy both. Actually, the prompt says “PEDAGOGICAL STRUCTURE (Divide into 3 distinct learning phases): Phase 1… Phase 2… Phase 3…”. I’ll make these the core subsections under ## Hauptkonzept or replace ## Hauptkonzept with them, but I’ll keep the exact headings requested if possible. I’ll stick to: # Titel, ## Einleitung, ## Phase 1: Fundamentos (Der Samen), ## Phase 2: Desarrollo (Das Wachstum), ## Phase 3: Maestría (Die Blüte), ## Beispiele, ## Praktische Zusammenfassung, ## Praxis-Herausforderung (Reto Práctico), ## Glossar der Schlüsselbegriffe.
    • I will ensure all content is in German.
    • I will add specific music theory details: exact chord progressions used in sampling contexts (e.g., jazz/funk soul loops like I7 - IV7 - viim7b5 - iii7, or modern hip-hop minor progressions like i - VI - III - VII), rhythmic breakdown (breakbeat patterns, swing percentages, 16th-note grids, quantization offsets), harmonic/melodic techniques (formant shifting, time-stretching artifacts, pitch correction curves, resampling chains), historical context (DJ Kool Herc, Pete Rock, J Dilla, Madlib, landmark albums like Amen Break, The Cold Vein, Donuts), etc.
    • I will format key terms with text or text.
    • I will use emojis naturally.
    • I will use GitHub alerts.
    • I will include ASCII rhythm grids.
    • I will strictly avoid YAML/JSON/structured data blocks.
    • I will ensure pure Markdown output.