You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dear Steven,
Here is a feature request of mine:
Current situation: I do use Cmask to generate score in External Sound Objects. This score usually yields lots of parameters generated by probability. The result is that in every outcome of the generated score the resulting amplitude is different. I usually do not use blue in real-time but the rendering of my pieces takes several hours. As the resulting amplitude is different every time, it needs several renderings until a rendering with more or less appropriate amplitude is generated.
Proposal: I do propose to offer an opportunity to fix the generated score as a stored text-file within that Sound Object. This generated score should also be reversible to the original score-generating commands that address Cmask,
Additional idea..but not necessary...just nice to have: Maybe the generated textfile would stay accessible and could be manipulated and tweaked by hand and then stored again.
Desired new behavior: This new feature would then result in an external sound Object where after pushing the "test-button" the resulting score may be stored if desired by checking another checkbox like "keep output" or "save output". The External Sound Object would then generate from now on always the same score up to the moment, where it is reverted to its original behaviour by some action like choosing a command like "revert to score-generation" from a context-menu. Then the code addressing Cmask or any other external executable would reappear.
This way the output of every External Sound Object could be tweaked up to the point, where the parameters of generated score meet the desired range and content and then saved. The result would be a rendering, that can be reproduced exactly.
The text was updated successfully, but these errors were encountered:
Dear Steven,
Here is a feature request of mine:
Current situation: I do use Cmask to generate score in External Sound Objects. This score usually yields lots of parameters generated by probability. The result is that in every outcome of the generated score the resulting amplitude is different. I usually do not use blue in real-time but the rendering of my pieces takes several hours. As the resulting amplitude is different every time, it needs several renderings until a rendering with more or less appropriate amplitude is generated.
Proposal: I do propose to offer an opportunity to fix the generated score as a stored text-file within that Sound Object. This generated score should also be reversible to the original score-generating commands that address Cmask,
Additional idea..but not necessary...just nice to have: Maybe the generated textfile would stay accessible and could be manipulated and tweaked by hand and then stored again.
Desired new behavior: This new feature would then result in an external sound Object where after pushing the "test-button" the resulting score may be stored if desired by checking another checkbox like "keep output" or "save output". The External Sound Object would then generate from now on always the same score up to the moment, where it is reverted to its original behaviour by some action like choosing a command like "revert to score-generation" from a context-menu. Then the code addressing Cmask or any other external executable would reappear.
This way the output of every External Sound Object could be tweaked up to the point, where the parameters of generated score meet the desired range and content and then saved. The result would be a rendering, that can be reproduced exactly.
The text was updated successfully, but these errors were encountered: