It's not as easily/readily playable as others like 8dio. It's difficult to get the most out of the Hollywood series. Their player is outdated and the instruments use 90s naming convention (NV VB VB anyone?).Ĭ). East West wants you to buy separate licenses for each slave machine.ī).
Greatful for any thoughts or advice.Ok, so I've been a CC member for 3 years and I've just cancelled my yearly plan.Ī). If you save a working version of viola 2 and then reload it either in sonar or the standalone browser, it always works. Reload the file with the nonfunctional viola 2and it doesn't work (ie. If you reload viola 2 from the play browser either in sonar or the standalone, it works. If you save the nonfunctional viola 2 to another file, it won't work in Sonar or in the standalone version of Play. Nothing can make viola 2 produce any sound except reloading viola 2 fresh from the Play browser. Unpredictably it will stop working sometimes while editing, sometimes when simply when simply playing a track that uses viola 2. This is a bit hard to describe but let's say viola 2 is working in Sonar. If you load the same instrument from the browser or a file in Sonar containing a working version of the same instrument, into the standalone version of Play, it works perfectly.
It behaves the same as it does in Sonar, namely the midi signals are registering on the input but there is abolututely no output. If you take the non-working instrument file you saved in sonar and load it into the standalone version of Play it will not play. This is true even in the stand alone version of Play. This is true if you are do so in the original sonar project or start a new one. If you save an instrument that stops working in Sonar as another file and reload it, it still does not work. I noticed that once an instrument stops working, the only way to fix it is to reload it again from the browser in Play. I have adjusted buffers and voices and sampling rates, no effect. It seems to be something other than a disk issue. Thanks in advance to anyone who might help.
If I can't find a fix then the EW package may not be useable for me. Any solutions or advice that more knowledgeable or experienced people might provide would be most welcome as I am at a loss and very frustrated / disappointed. Sadly, I very excitedly started to replace the strings in several compositions only to discover this problem. This does happen with other strings in HS too - mostly Legato. I have increased the midi playback buffers to 1500 mS (this had little effect). The voices never get higher than 30 and the maximum setting for the instrument (a legato viola) is 256. The cpu and memory usage is always very low. I noted that when this problem happens, the Midi signal sill shows up on the input meter but the output meter shows nothing. Ion even the sound is lost, the only way to regain it is to reload Play. The composition will work fine many times In a row and then the next time the track is silent. This can happen at random times with tracks that are completed. The only remedy is to delete the play and reload it. One minute it works the next, adding a note causes the instrument to become silent.
The problem is dropouts, loss of sound while adding notes.
#EAST WEST HOLLYWOOD STRINGS GOLD 64 BIT#
I am using 64 bit Windows 10 on a Intel core i7-4770k GHz with 16 GB of ram with a 2TB 7200 rpm Hd. I am using Sonar Platinum Kingston and EW Play 4.3.1. I decided to try the EastWest Cloud Composer subscription and was looking forward to adding Strings from Hollywood Strings to my compositions.
0 kommentar(er)
