Hi everybody,
I’ve got a basic sound file, but it’s got some rests in it.
orchidea.solve analyzes and processes only the first part and stops at the first rest.
What to choose so that the rests don’t interrupt the analysis? And get the processing of the whole source file
Thank you in advance,
Cheers~
Jerome
HI Jerome, it should not do this. Please send me the file to check.
Best
C
Hi Carmine,
Here’s the .wav via wetransfer
I’ve the same behavior with the new version.
Best, Jerome
ok thanks, ill have a look
c
Hi Carmine,
I’ve find a way out !
I use [orchidea.solve.maxhelp] for my tests :
I’ve used FullSOL… and the solution is “special” but sounds.
Best,
Jerome
Hi Jerome
it works fine with me. I attach here the parameters I used (in a TXT format) and the result of a (non refined) orchestration.
Hope it helps
C
dynamic_orchestration.txt (8.3 KB) connection.txt (97.6 KB)
Hi carmine,
Thank you so much for these infos.
I can see you use dynamic orchestration. It works for me too in this mode. Not when the onsetthreshold is equal to or greater than 1 where the orchestration becomes static again, and I only have the first sound. On the other hand my solutions always stop at 03:38 while the target lasts 04:08, regardless of the number of segments generated. I can see that you can go all the way…
Thank you very much for this information, I’ll dig that !
Best regards,
jerome
Hi carmine,
Orchidea - configuration file, this : dynamic_orchestration.txt
is really interesting and usefull.
I’d like to know how can I generate this report automatically, it’s great to submit the choice you make with parameters.
Many thanks in advance,
Best regards,
Jerome
hi Jerome
this is not technically a “report” but more a configuration script.
You are free to create as many as you want and then “load” them in orchidea.solve: once you do this all parameters will be set as in the script and you will be able to run the orchestration.
Please let me know
Best
C