Session 23 - 14.11.20

[Stephane Boussuge]

Here's the video files from this session.

The score files are already inside Opusmodus in score examples documentation section in Utility panel.

This is the scores : Craft for alto and piano. and the score Duet for violin and piano.

 

All the best to all of the Opusmodus community !

 

SB.

 

ZoomIntoOM-Videos141120.zip

[Rene]

Thank you very much, Stéphane, for your interesting sessions!

[edesert]

Yes - thank you so much for doing these sessions, Stéphane, its always very inspiring and they have done so much to increase my zone of comfort with this software.

 

Peter

[DanielJean]

Thank you so much Stephane for your tremendous support with these sessions.

[NagyMusic]

Thanks so much, Stephane. It's been fantastic watching your sessions and learning more about Opusmodus. I have a quick question about the first part of your presentation, namely about the piece Craft.

 

Whenever I evaluate setf mel, I get every so slightly different melody. I even adjusted the setf path function by including the new '(octave) variable:

(setf path (tonality-series modes :map '(octave) :root roots)) 

 

Although, after watching your explanation in the video, I'm not sure if using 'octave affects the output or not.

 

I attached the screenshots of three separate compilations; each produces an almost exact melody with only a few different notes. Is that because of the built-in randomness, in tonality-series or tonality-map?

 

I understand that there's a way always to get the same output by using :seed. Would you happen to have any suggestions on how to implement it in the given context, especially when the init-seed is already used?

 

Many thanks!

 

Zvony

 

[Stephane Boussuge]

Yes, it is because the randomness in tonality-map process call randomly the parameter up or down in the :closest option.

 

You can fix this by setting up or down explicitly:

 

(setf path (tonality-series modes :map '(octave) :root roots :closest '(up))) 

S.