can it now load EW play AU in the Ensemble server?
eldad
194,134 users have contributed to 42,912 threads and 257,923 posts.
In the past 24 hours, we have 4 new thread(s), 18 new post(s) and 77 new user(s).
Oh, I forgot. The machine has 4 gig and I indend to use them all 😊 Vepro is really tempting to spend a lifetime in building perfect templates... 😉@Paul said:
Hi mmueller,
glad it works now!
I missed the the tricky part with jbridge somehow....
"Real numbers" would be for example the amount of RAM in your computer, and the size of "big templates" - makes it easier for us.
Best,
Paul
It will not crash anymore when running EW Play AU and VE Pro Service Interface AU in the same host (Logic, DP, ...). For Play to work in an actual VE Pro instance, some work from EW's side is required.@eldad.guetta_10897 said:
can it now load EW play AU in the Ensemble server?
eldad
Hello,
I get double note (phasing) with LOGIC 9 and VEPRO... any idea why?
Also, last night session, I don't get a double note but when I play other EXS track, the sound from VEPRO will also play along... This beta is strange... I think I need to reverse to the old version!
Thanks for any help!
Sonny
@dsstudio said:
Hello,
I get double note (phasing) with LOGIC 9 and VEPRO... any idea why?
Also, last night session, I don't get a double note but when I play other EXS track, the sound from VEPRO will also play along... This beta is strange... I think I need to reverse to the old version!
Thanks for any help!
Sonny
Sounds like a routing error. Make sure that the MIDI input in Vienna Ensemble is set to Plugin MIDI, rather than Omni, assuming that you're not intending to use any external MIDI inputs.
DG
No MIDI handling was changed in this version. It sounds like a MIDI routing error indeed.@dsstudio said:
Hello,
I get double note (phasing) with LOGIC 9 and VEPRO... any idea why?
Also, last night session, I don't get a double note but when I play other EXS track, the sound from VEPRO will also play along... This beta is strange... I think I need to reverse to the old version!
Thanks for any help!
Sonny
Thanks for the update. However, I'm experiencing problems. Every time I try to open up Kontakt 2 within VE pro, it crashes. I can open up Kontakt 2 fine in Logic, and K2 use to work fine in older versions of VEpro (dont remember which version, but it was either the 2nd or 3rd build) but since updating to this build it no longer works. Was K2 support dropped? Whats interesting is if I open projects created with the older VE pro they open fine, but once I try to open the kontakt instance in VE pro (i.e. to add more instruments), it crashes VE pro.
I'm on a Dual 2.5 G5 w/ 7GB Ram OS 10.5.8. Logic 8.0.2
Thanks!
I am sorry but i am using Kontakt3.5 and 4.03 and no problems at all.
No eperiencing about Kontakt 2 in VePro, but due of the K3-4 improvements the version 2 have not reason to exist actually.
I suggest to you to update.
And as you can imagine VePro has a different architecture, so what you open in Logic not necessary work in VePro.
-A
@anton said:
No experiencing about Kontakt 2 in VePro, but due of the K3-4 improvements the version 2 have not reason to exist actually.I suggest to you to update.
This maybe true in some cases, but is not true in all. For example, Tonehammer recommends you use their libraries in KontaKt 2, and state that some of their patches do not work correctly in Kontakt 3 or 3.5! Even so, at the very least I should be able to open my old projects in VE pro, correct? Imagine trying to look at past work and it can no longer open!! I know this will happen eventually, but it should NOT happen from a maintenance update, especially when I haven't made any other changes to my OS, sequencer or DAW.
I know programming for all these variables is extremely difficult, but suggesting one should upgrade is not the answer, especially when in previous versions of VE pro K2 worked fine. You might say "stupid me" for updating when everything was working fine, but I HAD to update as the version of VE pro I was on had a MAJOR problem with the mac platform that caused the entire system to act slow!! (See thread here) http://www.kvraudio.com/forum/viewtopic.php?t=266341&postdays=0&postorder=asc&start=90
@anton said:
No experiencing about Kontakt 2 in VePro, but due of the K3-4 improvements the version 2 have not reason to exist actually.I suggest to you to update.
This maybe true in some cases, but is not true in all. For example, Tonehammer recommends you use their libraries in KontaKt 2, and state that some of their patches do not work correctly in Kontakt 3 or 3.5! Even so, at the very least I should be able to open my old projects in VE pro, correct? Imagine trying to look at past work and it can no longer open!! I know this will happen eventually, but it should NOT happen from a maintenance update, especially when I haven't made any other changes to my OS, sequencer or DAW.
I know programming for all these variables is extremely difficult, but suggesting one should upgrade is not the answer, especially when in previous versions of VE pro K2 worked fine. You might say "stupid me" for updating when everything was working fine, but I HAD to update as the version of VE pro I was on had a MAJOR problem with the mac platform that caused the entire system to act slow!! (See thread here) http://www.kvraudio.com/forum/viewtopic.php?t=266341&postdays=0&postorder=asc&start=90
Could you supply us with a report of that Kontakt 2 crash? Thanks.It will not crash anymore when running EW Play AU and VE Pro Service Interface AU in the same host (Logic, DP, ...). For Play to work in an actual VE Pro instance, some work from EW's side is required.@eldad.guetta_10897 said:
can it now load EW play AU in the Ensemble server?
eldad
What is required of them, and are they doing it? That is, do THEY agree that part of the problem is theirs, because from reading on their forum, absolutely all blame for this not working lies with VSL. Not that I agree with that, of course, but I'm trying to determine if this is a hopeless case, since EW seems to think, since Play "works" in all other DAWS (albeit in the real world there are bugs) that they don't need to do anything to help the VE Pro issues.
Can you please let us know if EW is in fact cooperating? Or are you experiencing a brickwall from EW on this issue?
Thanks
I have updated to this version VE PRO from the previous one but when I tried to add a solo cello to my vienna instruments orchestral cello the loading seemed to go into a loop and was well on the way to filling up 16gigs of ram when I pulled the plug on it. The solo cello was supposed to be 175megs. Is this a bug? Should I go back to the previous version? Is it something to do with the new feature save/load channel presets because this instance was made with the previous version of VE PRO?
This happens on a Mac Pro with 16gig of ram.
Thanks for any help!
Ross
I love the load/save presets/channelsets!! 2 odd behaviors with this version though.
1) crashed when opening matrixes created with earlier versions of Vienna Instr.
Problem solved by opening matrix in VI/VE and re-saving.
2) crashed when changing color.
Anybody else experiencing this?
MacPro 2.26 4 core (older) 16gb
Could you attach crash reports of this? They can help tremendously.@ddunn said:
I love the load/save presets/channelsets!! 2 odd behaviors with this version though.
1) crashed when opening matrixes created with earlier versions of Vienna Instr.
Problem solved by opening matrix in VI/VE and re-saving.
2) crashed when changing color.
Anybody else experiencing this?
MacPro 2.26 4 core (older) 16gb