I’m sorry, but I didn’t see another thread at the time. I only saw this announcement.
I don’t know if your 2nd sentence is a criticism of my question.
I was only asking a question, not complaining or anything. It was a simple question.
That said, I don’ know why “congratulations” would have been in order?
As for a “thank-you”, well, since a Mac version doesn’t do much good to a Windows user, that’s also a questionable response. And I posted that question: “will there be a Windows version eventually?”
Forgive me for asking a simple question and not responding according to your expectations.
If I was Michel_Edward I would take this as an unnecessary slap. People are going to post what they want to post. Michel’s post was not snarky, just an honest question. I had the same initial question.
First I think it’s great you made this App and present it free.
Than I wanted to ask something, that I wasn’t able to do earlier. And I’m afraid it’s hard to explain.
I use the sample Modeling strings N like them very much. Especially because they are relatively small. Many of the articulations are triggered by velocity CC. For example spiccato is triggered, when playing a short note at 127. Also note-transition ist controlled via velocity. If the second (overlapping) note is played loudly, the transition is short. When played very softly, it’s a portamento.
So here is my question: is it possible to map articulations to velocity? So when I notate spiccato, the corresponding note ist played at velocity 127. And when I notate portamento just the opposite?
Is it possible with this editor to create custom playback techniques that match to add-on switches?
I’m asking because Dorico currently does not seem to be able to do this and it would be great if using your editor was a workaround for this problem.
No, not at the moment. If you import into the editor an expression map which includes playback techniques not found in the library file, it will create techniques to allow you to work with the expression map. But those techniques will not be exported in a way that Dorico can import them.
Exporting playback techniques in a Dorico-importable format is a feature I might add in the future.
You probably know that Dorico will display playback technique IDs in expression maps for any techniques not found. And you can then add the playback techniques manually, naming them strategically to match the IDs.
Writing a Windows version is as much as starting over, with probably little to save since this is mainly a data model. I’d suggest instead doing what the Dorico team did and rewrite it to use Qt, that way it shouldn’t be too difficult a port, you can stay on your Mac, and if you don’t have a PC somebody else could compile & test on Windows. I’d also suggest putting it up on Github.
Plus, it would look very ‘Dorico Like’ dressed up in Qt. Edit: I’m up to my ears in projects but I could help with Windows and Qt rewrite, I don’t imagine the app is too large so it shouldn’t be a big effort I’d think.