The raw input

​

Our Malbec example has a lot of numbers:

"chem": {"pH": 3.35, "TA_gL": 6.5, "tannins_mgL": 1800, ...} "aromas": {"terpenes":0.2, "pyrazines":0.1, ...} "geo": {"altitude_m":1100, "MGST_C":18, ...} "morph": {"berry_mm":12, "skin_pulp":0.28, ...} "sensory": {"body":8, "finish_sec":36, ...}

​

This is a giant table of grape features: chemistry, aromas, soil, climate, berry shape, and tasting scores. It’s precise, but not immediately usable for creating music or analyzing patterns.

Think of it as the raw ingredients in a recipe: you know the numbers, but you don’t yet know how to mix them into a meal.

 

The blueprint​

​

The blueprint translates those numbers into various musical concepts, such as the following:

• Mode → which musical scale to use (Ionian, Dorian, etc.)

• Key center → the tonal anchor

• BPM → how fast the music should play

• Meter plan → time signature and rhythm complexity

• Staccato / density / syncopation → how “choppy” or “dense” the notes are

• Octave tilt → whether the melody is brighter or darker

• Aroma layers → extra musical layers representing flavors/aromas

• Form → structure of the musical sections (Appearance, Nose, Palate, Finish)

• Space / reverbs / vibrato → gives depth and expressiveness

​

In other words, the blueprint is a map from grape features → actual music parameters.

Without the blueprint, you couldn’t just “play the grape” as music. With it, you have a ready-to-use musical score blueprint: tempo, scale, note patterns, dynamics, layers - all derived from the chemical, sensory, and geographic traits.

So in Malbec’s case, instead of juggling pH 3.35, tannins 1800, color intensity 16.5, you now have a musical DNA: Dorian mode, 120 BPM, 4/4 time with irregularities, aroma-inspired harmonics, and expressive form sections. That’s what you actually need to turn it into a rich musical track.

Below you may see a clear, visual ELI5-style diagram of how Malbec’s raw numbers become a musical blueprint.​​