Paul, you solved the issue for me by mail this afternoon. Thanks again. Haven´t had a look back here before.

Cheers Dirk

i can´t even open any vsl instruments or projects using vsl because of an elicenser failure.

big bummer. i can understand that steinberg won´t test there cubase/nuendo apps etc.  during beta stages of a new mac system. with the elicenser it´s a different game imo, because so many other developers are involved.

Is there a way to globally set VEpro streaming options for VIpro before loading the poject? Preferable systemwide and forever for this machine?

As soon this project is loaded, the macbook pro is completely unusuable because of no System RAM...

Any suggestions?

thanks karel. good to hear that it´s on your list. hope you´ll find a solution.

... before i can shut down the mac or put it to sleep? this bugs me almost every night...

the servers are set to autostart on mac-startup and i would love if they just shut down on shutdown.

i´m using vepro only on one mac, so if this has to do with networking, could there be a "no network" option for more convenience?

strange is that only the 32bit-server prevents the system from shut down, the 64 bit server ends as expected.

is it just me?

hi

i can confirm this exact kind of problem using Addictive Drums in VEpro on a multi monitor setup. i also use two of the ATI Radion HD 2600 XT...  it happenes all the time starting with a version around 4.0.464 last year, but got somewhat better through the versions of VE pro (or through osx upgrades). now it seems to mostly  happen only by resizing the ve-pro window to a size where the main space is smaller then the UI of Addictive Drums. if you resize it to be bigger, parts of AD´s UI stay white. and when hoovering over the white space buttons, faders or knobs become visible again if you meet them - but not their backround. but still occasionally the UI is completely cluttered as seen in the dezzo´s videos.

hi

i´m, having the exact same problem with steinbergs (discontinued) VirtualGuitar2.

would it be possible to add a similar fix for this?

thanks

i love this idea. if there´s a way to implement this please do so...

Hi,

i know VG2 isn´t distributed and supported anymore (by steinberg), but as it still works fine: if you reload a (logic-)project with VG2 inside of VEpro, nothing is loaded into VG2. sometimes you don´t even see any styles, but it never automatically reloads, what was saved. so if you still have a copy of VG2 around, it would be nice if you can have a look into the issue. thanks

it is fairly redundant yes, it´s just a "thought" (read the title) which could make things somewhat easier and help setting up VEpro more to the way many people will use it (at least in the 64 bit version). using an instance of VEpro for each instrument wouldn´t at all make things more comfortable and if you read my signature, you´ll see that i´m using logic, so vst3 is also no option. now please let this thread be what it is, a suggestion. if you don´t need this, don´t care. but thanks anyway for bumping this up all the time.

sorry, but i think you didn´t get the point. please read my initial post post carefully. setting midichannel to "1" means only incoming midi from channel "1" would be accepted and would be throughput to channel "1" of the instrument. now you setup another track in logic to send midi to another VEpro instrument. you will do that on channel 2. now you set up this next instrument on VEpre to midichannel 2 and it will recieve midi from channel 2 but only throughpass midi to the new instrument on channel 2. so you have to setup the new instrument to recieve on channel 2 only. it´s not too hard to set up (for me) but it may lead to confusions for other people. too many steps that don´t make sense. in stylus for example you´re forced to load a loop in the slot that is corresponding to the midichannel you´re sending from logic. no problem for me, but it could be much easier...

i´m ot sure what you mean? there´s no "all"- setting. in case you mean "omni" that´s something different.
as it is, the incoming midichannel is throughpassed to the instrument so you have to additionally adjust the instrument in order to recieve midi on that channel which isn´t straight forward and depending on the instrument may force to learn the instruments indepth settings for no reason. tell me if i´m wrong...

i think it would be nice to have the option to switch off multitimbral functionality in VEpro in the preferences or on a per channel basis. this would mean that the incoming midi would always passed through on midi channel 1 to the instrument, ignoring the channel of the incoming midi. at least in the 64bit version of VEpro, using multitimbral instruments doesn´t make much sense, as the memory-hit of the user-interfaces can be ignored. so the way one would prefer to work in order to unclutter things and don´t have to deal with additional inputs in VEpro is to open a new instance of an instrument for every sound needed.
right now there are three 64bit instruments for the mac. stylus, omnisphere (beta) and trillian (beta).
by loading a new instance of one of these you also have an additional step to assign the right channel in omnisphere. in stylus you don´t even have this option. here you have to take the respective part to load the loop you want. (there are only 8 parts, meaning if you already used 8 omnispheres in VE pro using channel 1-8 you don´t even have the chance to assign midi to a later added stylus. everything would be much easier and more intuitive for new users if we´d be able to switch off multimbrality as mentioned. another option would be another midichannel button. so the existing one would reflect incoming midichannel, the new one would reflect the throughput channel to the instrument (default=1). or you do it as in logic. on loading an instrument you choose between a stereo and a multitimbral instrument. i´d prefer a "M"-button next to the midichannelbutton. Highlighted means multitimbral on and midi is passed through on the same channel. and defaulted it´s off and midi is passed through on channel 1.
thanks ;-)

hi.
after 3 month+ and several updates of VEpro, logic, spectrasonics etc. i´m just trying again and get the same issues.
still sometimes on certain mulititimbral instruments i see the incoming midi in VEpro, i hear the internal prelisten audio (stylus in this case) but VEpro doesn´t throughput the midi to the instrument. i think the huge midi delay has gone though...

edit:

sorry, my fault (and a bit of a designflaw from stylus) - solved !
(the parts in stylus mixer don´t have a channelswitch (like omnisphere) so if you want a stylus play on channel4 you must choose the groove in part 4 obviously...)

thanks again, christian - it´s been running perfect for the latest updates. like 1MB/sec.
you care - i like this website. :)

i´ve heard from logicusers having the exact same problem. (using 10.5.8)
if ve-pro is active and they open an instance of play in logic it crashes immediately.
this doesn´t happen on my system though. (10.6.2)
may be this helps to isolate the problem which doesn´t seem to be host specific but rather an OS-version thing.

btw. i wonder why so many people in this forum report problems without any information about their working environment.

works fine here. it"hangs" like 15 sec on that jampack manager thingy and then starts fine.

for more streamlined information flow, wouldn´t it be an idea to split the forums into more accurate categories?
i feel VE pro would "earn" an extra forum. at least. ;-)

christian, wow cool. it IS much better now. though: today.
after reading your edit yesterday evening i still got an download speed average of 20KB/s.
right now i get 200-250 KB/s which is o.k.. enough for software downloads.
for instruments downloads it still might be a bit slow but i don´t care today. this doesn´t happen very often.

thanks for asking your provider :-)

hi cm.

thanks for answering, i only just see your posts.
so i searched the web a little and it seems like this is a known and probably a "political" issue between dtag and cogentco which is hard to believe. seems to be about to pay or not to pay for peering. hmmm.
in one statement from the dtag they say that many network carrier have issues with cogentco regarding peering, leading to the question wether a company providing a lot of content to many people all over the world should solely work with cogentco.
i will now call up the t-online hotline, but i don´t see any chance, that they can do anything for me. i´ll report back anyway...

remember UI-placement and sizes / save them with the project

with the previous beta of VEpro the UI of addictive drums started to be very corrupted.
as i´ve also had a couple of other graphics issues systemwide, i thought it to be merely an OS issue, even though it clearly started with the previous beta. workaround was to mousehoover over the interface and some elements would have been shown (faders etc.). best bet was to hit the unvisible AD-logo then most of the needed elements would become visible adhoc. this behaviour didn´t change with the latest beta. however it also didn´t change with MacOS 10.6.2 apart from the interface beeing completely black now instead of "colourful distorted". can you at vienna please look into this?

thanks a lot. can´t wait to test it.
but let me submit these 60MB downloads always take between 45 and 60 minutes to downlaod this is like 1998. i can´t stand it. is there something you can do? is there a special bandwith limit for software as opposed to instrument downloads? maybe add a couple of servers?
thanks

i don´t like the website, because the site is dogslow. and worse are the downloadtimes.
waiting 40 minutes for a 60MB VEpro-update download is unbearable these times.
that was 1998.
anyway, i like the company!

seems to be a problem with any multimbral instruments.
shouldn´t be that hard to reproduce.

http://community.vsl.co.at/forums/t/23126.aspx