-
Hi and welcome to the Studio One & Studio Pro User Forum!
Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by Fender. Learn more in the Welcome thread!
Sound Variations for EW Opus Not Working.....
- Thread starter Jeff
- Start date
Details would be good, but since I'm very involved in this topic and know both the responsible developers from Studio Pro and EastWest OPUS, I can say this: Opus currently seems to have an issue related to Sound Variations that will either be fixed in the next update or may already have been fixed in the last few days.
Just to make things clear, I highly recommend EW products, they were one of very few iloc/AMD9000 series issues who helped out at the release of the 9000 series when iloc would not run with a 9000 series CPU. It wasn't a regression is was bug that needs to be fixed as it is a time saver for large scores using EW Opus.
Hello. I am just getting started with orchestral composition, DAWs, etc.
I tried to get 'articulation switching' to work on Thursday and tried everything (Studio Pro and Opus). It simply didn't work. Tried switching octaves up and down and no switching happened. After hours of trial and error, I finally saw this post and thought that everything was maybe only due to a bug and not me being unable to figure it out. Any ideas if the bug has already been fixed?
I tried to get 'articulation switching' to work on Thursday and tried everything (Studio Pro and Opus). It simply didn't work. Tried switching octaves up and down and no switching happened. After hours of trial and error, I finally saw this post and thought that everything was maybe only due to a bug and not me being unable to figure it out. Any ideas if the bug has already been fixed?
They just have launched 1.64 version , in the log list of changes it is included the fix for fender studio / studio one.
www.soundsonline.com
I will try it tomorrow. Hope this helps and finally this bug is fixed.
Download EastWest Software & Instrument Updates | PC/Mac
Get software updates for EastWest VST plugins, Play, NKS Support Installer. Available for Mac & Windows.
www.soundsonline.com
I will try it tomorrow. Hope this helps and finally this bug is fixed.
Just downloaded the newest version and the articulations work. My existing articulations (I created when there was still the bug) now appeared as question marks (the labels for staccato, legato, etc. were transformed into question marks). But when I assign new articulations, they now appear correctly and also play back correctly. As I am just getting started, it is not an issue for me to redo all (10) of them manually. I guess for some people it could be really a hassle if they have to reassign a lot of articulations.
Hi Lukas ! As other has already reported , at least for me , it is working perfectly well again , with new articulations, or using the already created in a midi track.Please report back
I know you are so busy , and i hope the op also doesn't matter if in a way I will "hijack" the thread but since we are discussing East West libraries and Studio one I've got a question to you regarding Orchetrator and Studio one, if you don't mind and you have the time and will to have a look at it.
In Cubase it is working perfectly well, so if you drag and drop the hand icon your preset will create midi tracks with the selected orchestration preset, all of them, the only caveat is to be certain that in preferences in cubase in midi section, in the import options to select the option "midi tracks" instead of Halion or another specific... Tested and working solid.
Here is a video in case you want to see it perfectly described :
In Studio one ( not upgraded yet, still in ver 7 ) it also works, you drag the hand icon and it creates the tracks with the correct names etc...
BUT i doesn't assign any intrument at all, it just creates midi tracks (with correct midi data on them) but without any instrument assigned..
It is not the end of the world, you can manually assign them one by one but it is tedious.
I deeply search and try any option in studio one but nothing seemed to work , or i wasn't able to find the appropiate one, is there any hidden feature or menu to solve this ?
Or maybe a macro is needed to assign correctly the instrumet to midi tracks, and that's the main reason why I am asking this to you particulary since you are the ultimate studio one's GURU of Macros !!
Or maybe I have to contact EastWest to ask them to create what is needed to work as well as in Cubase.
Thanks in advance for you time, hoping you can throw some light about this issue ...
For your information if you UPGRADE OPUS TO VERSION 1.66 .... VST3 could not work at ALL on studio one 7.2.3 ... vst 2.4 is working fine.
After creating a ticket at EW , they suggested a FULL plugin rescan , that solves the problem.
And by the way thanks to @Jeff and @Olorin for your prior kind answers, it is clear that studio one by its nature and core programming is not able to use orchestrator completly as intended. It is not the end of the world but Cubase can and as always has the lead in midi...
After creating a ticket at EW , they suggested a FULL plugin rescan , that solves the problem.
And by the way thanks to @Jeff and @Olorin for your prior kind answers, it is clear that studio one by its nature and core programming is not able to use orchestrator completly as intended. It is not the end of the world but Cubase can and as always has the lead in midi...
Last edited:
@Gus: Sorry, I missed this reply in June.
Yes, it seems that Cubase assigns the resulting MIDI tracks to Opus automatically, but how is it supposed to know which instrument you want to use? It doesn't necessarily have to be Opus. It could just as well be Kontakt, HALion, HyperSonic, SampleTank, or any other multitimbral sample player.
In Studio One, everything shown in the video can be done with just a few clicks. It's even easier if you have my Scoring Tools add-on (paid) or my Navigation Essentials add-on (free)
It's true that this requires two or three extra clicks, but I'm not sure that's significant enough to start talking about Studio One's nature and core programming.
A six-minute video in which the actual content doesn't start until the 2:00 mark is far from perfect, to be honest
Yes, it seems that Cubase assigns the resulting MIDI tracks to Opus automatically, but how is it supposed to know which instrument you want to use? It doesn't necessarily have to be Opus. It could just as well be Kontakt, HALion, HyperSonic, SampleTank, or any other multitimbral sample player.
In Studio One, everything shown in the video can be done with just a few clicks. It's even easier if you have my Scoring Tools add-on (paid) or my Navigation Essentials add-on (free)
It's true that this requires two or three extra clicks, but I'm not sure that's significant enough to start talking about Studio One's nature and core programming.
@Lukas
First of all, thank you so much for taking a little bit of your precious time to answer this question and try to help me and others with this, I do really appreciated it. And also want to appologise if my previous post was received or you had the perception of a veiled critic to Studio one, which was not at all, nor even my intention, on the contrary , the only thing I tried to say was that i was presuming the possible solution of this, if there is any, had to be related not to a macro, option, or even your tool, but something related to the core nature of how this great daw is conceived and programmed: simplicity and great workflow had to had a tradeoff ... a tradeoff that i conscilusly paid when i chose this great daw instead of Cubase.
So , i download your free tool, and follow and did your steps but i am so sorry to say that it didn't worked. I really wish it had ! I don't have sonuscore library and maybe for this librarie your solution works, but in EW orchestrator, the only thing you do is assing the opus orchestrator (the same of the reference track) to x number of instrument tracks, and assign a different midi channel to each of them but this has nothing to do with what cubase does automatically, which is assigning the tracks to each articulation (specific from the EW library instrument and then loading them correctly) used in that preset used in the orchestrator reference instrument track.
If I use your assing midi channel button in your tool to the new created tracks after draging them from orchestrator (it still miss some tracks ) the orchestrator in the reference track do not work properly... it only sounds the first instance of the preset, not the entire preset ..... so at the end, you have a repeated orchestrator track loaded into different instrument tracks with yes some of them sounding correctly, some of them not, and a broken reference track with no instrument assigned....
I don't know what import option midi track does exactly in Cubase to assign perfectly well every instrument and articulation to its particular instrument track, but it seems that to have this in studio one, a "core" functionality has to be implemented in future updates or releases , or as I said in my previous post, maybe EW has some info to share about his opus engine to help integrating this function completely to Studio one ... but for now, it seems that this is not possible to do this automatically. As I said , you can always assing them manually, it is not the end of the world... and as @Jeff pointed out, EW at least names correctly the tracks created so it is easy to assing manually the appropiated articulation, it seems it is not the case in kontakt Sonuscore.
Sorry for this long post, and once again thanks Lukas to help and try your best to give this a try ! Hope one day we can have this working properly.
First of all, thank you so much for taking a little bit of your precious time to answer this question and try to help me and others with this, I do really appreciated it. And also want to appologise if my previous post was received or you had the perception of a veiled critic to Studio one, which was not at all, nor even my intention, on the contrary , the only thing I tried to say was that i was presuming the possible solution of this, if there is any, had to be related not to a macro, option, or even your tool, but something related to the core nature of how this great daw is conceived and programmed: simplicity and great workflow had to had a tradeoff ... a tradeoff that i conscilusly paid when i chose this great daw instead of Cubase.
So , i download your free tool, and follow and did your steps but i am so sorry to say that it didn't worked. I really wish it had ! I don't have sonuscore library and maybe for this librarie your solution works, but in EW orchestrator, the only thing you do is assing the opus orchestrator (the same of the reference track) to x number of instrument tracks, and assign a different midi channel to each of them but this has nothing to do with what cubase does automatically, which is assigning the tracks to each articulation (specific from the EW library instrument and then loading them correctly) used in that preset used in the orchestrator reference instrument track.
If I use your assing midi channel button in your tool to the new created tracks after draging them from orchestrator (it still miss some tracks ) the orchestrator in the reference track do not work properly... it only sounds the first instance of the preset, not the entire preset ..... so at the end, you have a repeated orchestrator track loaded into different instrument tracks with yes some of them sounding correctly, some of them not, and a broken reference track with no instrument assigned....
I don't know what import option midi track does exactly in Cubase to assign perfectly well every instrument and articulation to its particular instrument track, but it seems that to have this in studio one, a "core" functionality has to be implemented in future updates or releases , or as I said in my previous post, maybe EW has some info to share about his opus engine to help integrating this function completely to Studio one ... but for now, it seems that this is not possible to do this automatically. As I said , you can always assing them manually, it is not the end of the world... and as @Jeff pointed out, EW at least names correctly the tracks created so it is easy to assing manually the appropiated articulation, it seems it is not the case in kontakt Sonuscore.
Sorry for this long post, and once again thanks Lukas to help and try your best to give this a try ! Hope one day we can have this working properly.