Andy

Sorted, thanks

I am getting something similar but I have got the Opusmodus folder in my home directory. I get these two error messages:

So I'm very happy to be exploring new snippet structure but cannot seem to define my own instrument, based on the example in the help file I did this but get errors: SOLVED: I had to Evaluate my Def-Inst before it would play..

Wow this really is a huge deal for me. We can now have snippets as mini scores before we compile. Key sigs, time sigs, tempo and instrument defs all in a snippet. And multiple voices too. Thanks Janusz. 5 hours later. So this is a major change it seems to me and very useful. The whole workflow has had a boost. This, amongst other things, allows the creation of snippet libraries with granular control over the visual and functional aspects of the snippets. An ideas library is here. Of course it was possible before with mutiple .opmo files and def scores but this is much more useful (and convenient). I can have one .opmo file with a hundred snippets in it, all with different instruments and with correct notation and functionality and individual tempi. As a recent arrival to OpM I do remember my first reaction was ...Preference>Audition>...and then set a static set of preferences for playback?....this just felt limiting to be honest. Then I quickly realised that this was just a temporary thing and def-score was the way to define playback..and still is. But the Preference>Audition set up can effectively be ignored if one wishes now and Snippets are free! Good stuff.

Thanks Stephane but looks like the latest update has rather wonderfully added this feature.

But I'm not sure how the dual display is instigated?

Yes, great news and thanks Janusz.

OK understood, thanks.

Mmm so this relates back to my earlier question about libraries and storing ideas and multiple def-scores in a single document. To store an "idea" which can be viewed with a key signature in notation I have to save it as a def-score, but each composer document (.opmo) can effectively only have one idea in it, because each .opmo file uses only one def-score, as previously discussed. (I know it can have the code of an infinite number of def-scores, however only the last def-score will 'Evaluate and Audition and Notation" i.e it's not possible to highlight a def-score in a composer document as discovered in my last post) I'm confused to be honest..the whole structural thinking in Opusmodus is confusing me!

Is it possible to have a key signature with a snippet? Thanks

Thank you.

So I can have multiple def-scores in a file, but only one of them will be acted upon by "Evaluate and Audition and Notation"..always the last one?

If I use Menu> Evaluate and Audition and Notation on your code..it will always act on the second score, score2. How do I do that to the first score in your example? Thanks

Ah OK in that case I need help because when I evaluate a Composer document with multiple def-score's in it, it will always evaluate the last one in the document. If I have a def-score higher up, I cannot evaluate that one. To evaluate a def-score... it does not involve highlighting the parentheses so how does OM decide which one to evaluate? Thanks.

I think I am correct in saying there can be only one def-score per Composer document? Is that correct? Thanks