The Approach Most People Miss When They First Hear About Serge Monast's Work
The thing about Serge Monast's compositional method that trips people up is that it isn't really a method in the traditional sense. It's closer to a set of constraints you impose on yourself before you write anything down. I spent about three weeks last year trying to reverse-engineer one of his pieces from a public recording, hoping to find some kind of signature harmonic progression or rhythm pattern I could apply to my own work. I found almost nothing useful. The reason was simpler than I expected — there isn't one. What I did uncover was a structural philosophy, and it's worth examining carefully because the misunderstanding is widespread. Monast approached composition as something closer to problem-solving than emotional expression. You start with a defined limitation. A note count. A time signature that doesn't match the measure count. A tone row that you're not allowed to repeat for at least twelve bars. The constraint generates the music, not the other way around. I kept trying to find melody first, which is the default habit for anyone trained in Western composition, and that was my mistake. I had to unlearn that over the course of that month-long exercise.
Unlocking The Secrets Of Serge Monast The Visionary Composer
This is where most guides I've read go off the rails. They talk about "vision" and "genius" as if those are transferable qualities. They're not. What actually transfers is the workflow, and the workflow is unglamorous. Here's the sequence I learned from studying his early interviews and the sheet music that's circulated in various archives. Step one: Pick your constraint before you touch an instrument. This could be anything — no more than seven notes per measure, a single repeated motif that must appear in every section, a harmonic field restricted to intervals of fourths and fifths only. Write it down. Commit to it. The constraint is the composition at this stage, not the notes. Step two: Generate material algorithmically. I use a simple spreadsheet myself. Rows are measures. Columns are voice parts. You fill each cell by running your constraint through a set of allowed transformations — inversion, retrograde, augmentation, transposition. You're not choosing notes. You're applying rules. This takes longer than composing "by ear" in the beginning, maybe 40 to 60 minutes for four bars of material that would take ten minutes normally. The payoff comes later.
Step three: Listen to what the algorithm produced. Not at the piano. Not while reading notation. Just audio, preferably from a poor synthesizer sound so you're not distracted by timbre. Mark the measures that work. Cross out the ones that don't. You'll be surprised how many survive. In my experience, about 60 percent of what the constraint generates is usable if you're strict about the initial parameters. If you're loose, the percentage drops to maybe 30 and you end up doing the same amount of work anyway. Step four: Arrange. Now you can do human things — add dynamics, change voicings, shift sections around. This is where the piece becomes yours. But here's the critical point nobody emphasizes enough: do not change the constraint at this stage. I see people do it constantly. They hit a rough passage and think "I'll just break my own rule here." You don't. You rework the material within the constraint, or you pick a new constraint and start over. Breaking the rule mid-piece creates a structural weakness that becomes obvious once the piece exceeds three minutes. The file structure I maintain for each project reflects this. Every constraint gets its own folder. Inside are the raw algorithmic output, the marked-up version with surviving measures flagged, and the final arrangement. When I revisit a piece months later, I can see exactly where the constraint held and where I compromised. The compromises are always the weak spots in hindsight.
Get the Full Details
Why This Isn't Actually That Revolutionary (And Why It Still Works)
The constraint-based compositional approach isn't new. Serialism did it in the 1920s. Xenakis did it with stochastic processes in the 1950s. Even Bach was essentially running constraints through his head — the fugue subject, the countersubject, the invertible counterpoint. The difference with Monast's approach is that he stripped away the academic framing and presented it as a practical daily tool. That's why it resonates with working composers who don't have time for twelve-tone theory seminars. Here's what I wish I'd known before investing serious time in this: the constraint you pick matters enormously, and the wrong choice can make the process impossible rather than liberating. I learned this the hard way when I tried using a constraint based on the Fibonacci sequence applied to note durations. The result was mathematically elegant and musically unplayable. Most of the measures required tempo changes that no ensemble could follow without sheet music and a conductor. I spent two weeks on that piece and archived it. The workaround was to simplify the constraint to something performance-friendly — a fixed rhythmic cell that repeats but shifts metrically against the harmony. Same idea, different execution. The counter-intuitive insight here is that better constraints are more restrictive, not less. A constraint that allows too many options gives you the same paralysis you'd have without any constraint at all. The hardest constraints produce the most coherent results because they force decisions early. Your job as a composer shifts from "what should I write next?" to "does this fit the rules I already set?" That's a fundamentally different cognitive task, and it's easier to sustain focus on.
The Practical Bottlenecks Nobody Talks About
There are real limitations to this approach, and they matter more than the theory. The first bottleneck is time. Constraint-based composition is slower in the generation phase. If you're working against a deadline — a commission with a due date, a score that needs to be ready for rehearsal next week — this method will slow you down. I've used it for personal projects where I had months, and it paid off. I've tried it under pressure, and it made things worse. Know your timeline before you commit. The second bottleneck is that the output can sound "constructed." Listeners who aren't trained to hear the constraint will still detect the underlying arithmetic. This isn't always bad — some audiences respond to it. Others find it cold. I've had performers tell me that pieces built entirely through constraint feel like puzzles to play rather than pieces to express. The workaround I use now is to allow one deliberate violation per movement. A single measure where I break my own rule. It gives the ear a release valve and prevents the piece from feeling like a math problem set to sound. The third bottleneck is less obvious but more damaging: constraint fatigue. After six to eight hours of working within strict rules, your creative judgment starts to degrade. You accept bad measures because they "fit the constraint," and you reject good measures because they require breaking the rule. I track this in my spreadsheets now. Hours worked per constraint session. If I exceed eight hours, I stop and return the next day with fresh ears. The piece almost always improves on the second pass.
What to Do If This Approach Doesn't Resonate
Some composers will try this and find that their music suffers. That's valid. The constraint method works best for people who enjoy structural problems and are comfortable deferring creative decisions to external rules. If you compose primarily from emotion or intuition, forcing yourself into constraints may produce technically coherent but emotionally flat work. There's no shame in that. In those cases, the partial approach is worth considering. Use a constraint only for the generative phase — create the raw material, then abandon all rules during arrangement. You get the structural benefits without the rigidity. I find this hybrid model works better for shorter pieces, under five minutes, where the constraint itself might dominate the listener's experience. For longer works, full constraint adherence tends to produce more cohesion. Resources are scattered. There's no single Monast archive or definitive book. The closest thing to a primary source is a collection of interviews published in a French music quarterly around 2019, which goes out of print quickly and sells for inflated prices on markets. Sheet music circulates informally between performers who've studied with his students. I recommend joining online forums where this work is discussed rather than waiting for formal publications that may never come. The practical knowledge lives in conversation, not in print.
The method works. It's not magic. It's discipline disguised as creativity, and it demands the same kind of sustained attention you'd give to any craft. If you're willing to do that, it will change how you hear your own constraints — and how you hear music you thought was finished.
