DG -
WHy are your posts in BOLD and CAPS?
Of course, maybe you are just that sort of guy, but I can't help wondering.
-
Hi DG,
Sorry for this, I really did not mean to start an argument. Please accept my sincere apologies.
Once again thanks for the insight and help and I do sincerly apolgize to you if in any way I offended you.
Sorry!
Dave
-
I strongly disagree. I have had all sorts of trouble with the UI on VE. It's cost me countless hours of lost time because buttons stop working, or they show up in odd places, and some don't show up at all. My guess is that there's some sloppy coding behind the way the UI works. When I added the SE Plus articulations to my SE library, I had to reprogram my ENTIRE template because a bunch of UI buttons quit working when I loaded my old template. It's defiinitely buggy.@William said:
There is no "problem with the user interface." Except in your mind.rgames
-
I'm a LOGIC/VSL power user in a professional way and I can confirm that the two level UI thing give me headache every day. Is it the same on Windows? There no way i'm gonna go back to Kontakt cause VI is the best sample playback plugin for doing keyswitching. But there is really a problem with this windows things. I work 10 hours/day with this tool, I'm waiting for longtime that VSL will repair this non-sense. Excuse my english. Doc you have all my support! I wish VSL will listen to this.
-
I add my voice to the community, this is very annoying problem we suffer every minute.
As old programmer, I see this problem will not cost VSL development team more than few lines of code to set the focus to the host main window. Please update the tool ASAP and after that see how to solve the problem of the two step UI.
-
@Emperor said:
DG
Please let one of your programmers share this discussion with us.
We have some suggestions regarding the UI.
Thanks.
Huh? I don't have any programmers. What are you talking about?
Ah, I see. You think I work for VSL. Nope, not a chance. They can't afford me. [;)]
Look guys, I'm not saying that the current system isn't a problem for you. I'm just trying to point out (within my limited understanding) why it works the way it does.
DG
-
Perhaps if you work with templates the switching between DAW and VI or VE may be less of an issue as you don't have to do it much!
When you have an evolving project that may not suit a straight orchestral line-up so are creating matrixes and patches from scratch then the current set up add a considerable, and at times very frustrating, overhead.
Along with 64 bit support this is right up there as a feature request.
Julian
-
Sorry for the previous irritating post - I was myself irritated by the tone of this, as it seems to blame the wrong equipment.
This has got to be a problem WITH LOGIC because I have never had anything remotely like this happen even once in standalone multiple instance Forte racks. In fact nothing has ever gone wrong with the program at all.
-
I agree with Docmidi about this situation, I also find it frustrating using Logic 8 and VI/VE, I also understand what DG is saying ...but I do think that this problem should be dealt with as soon as possible. I know a lot of musicians who are turned off VSL because of this problem... Cheers Ian
-
Can I just make a request?
Previous version of the Plug-in, if I open the interface, it take me back in the instruments articulation list [or last edit page] so If I want to change articulation, I don't have to browse/open directory of articulation list again...
For example, If i load patch Solo violin universal, then later I want to add portamento, open the plug in, I wish to have the solo violin directory ready so I just load the portamento next to the legato... don't have to click bunch of arrows...
Current version is NOT, it don't remember where the previous patch I load, please bring it back [or do I missing something]?
thanks
Sonny
-
-
Hi DSStudio, Yes I remember when the VI interface use to work like you suggest. The other bothersome thing is when one tries to save a custom matrix, the VSL Custom directory is no longer present. I have to Start from the Root directory and work my way back to the folder with the custom matrix's. This all seemed to change about the time the Ensemble was released. This whole interface thing has been very frustrating to me ever since I switched from the PC using Sonar and Cubase 4 to the Mac using Logic and Cubase 4. The workflow using the VI interface with the MAC is broke and workflow efficiency has been severely hampered. I have bit my tongue on this one for some time but felt compelled to chime in. If VI wasn't sooo good sounding compared to the competition, I would can the entire $20,000 library!!! The way I see it, VI need to place some design emphasis on customers that are using the Mac environment / single machine. It seems that the PC world has the definite edge here (interface & memory) even though Mac has the most powerful machine.
-
I agree with you William that it works fine in a VST rack. I've tried various combinations over the past 10 months trying for the best configuration. The issue as I see it is related to the Mac implementation and how the VI interface reacts with Logic or Cubase sequencers. I sure hope that the VI folks get this thing tightening up sooner than later. I was hoping the VE would have solved the issue but I have not been able to run two VE instances on the same machine within the sequencer without either Logic or Cubase locking up about 1/2 way through song creation -- hitting the memory wall with very little samples loaded. Running the VI has seemed to be the most stable in both sequencers, which in Cubase, allows freezing the tracks and dumping all the memory for a given instance. In Logic, I freeze but cannot dump all the memory (Logic limitation) -- therefore need to use the optimize in VI. I guess at some point I'm going to have to break down and buy a few more machines. I purchased the Mac Intel 8-core last fall instead of the three Rack PCs I had originally planned to purchase. Sweetwater talked me out of it and I have not been happy every since. Win a few -- loose a few..... Take Care..
-
I run VE2 standalone on XP64 and suffer many interface bugs. FWIW, I had exactly the same problems with VE3 standalone when I tried it. So the standalone version does not, in fact, work ok.
It only happens with large memory usage (e.g more than 3 GB), so it's probably a case of sample memory overwriting the memory space used by the UI elements. The fact that it happens at the 3 GB mark hints to me that it has to do with some sloppy coding regarding the switch from 32-bit to 64-bit. But I'm no programmer...
I can confirm the issue with multiple instances of VE - I could never get them to work. Major pops and clicks in the audio with only a few tracks running. CPU usage increases very rapidly with two instances - it's much lower with the same number of voices on a single instance.
rgames
-
Hang on a minute. there are multiple different problems being discussed here. I think that they should be separated pout. Please correct me if I've got this wrong:
-
GUI window requiring too many clicks to avoid break in workflow. I think I've given the reason why, but I agree that for some people it would be good if it worked the same as a normal plug, without losing the advantages of the separate memory space.
-
Running out of memory on OSX. This is because there are no 64bit audio apps on OSX. There will be as soon as Apple gets its act together. Be patient. VSL, or any other cross-platform developer, can't do anything about this without the co-operation of Apple.
-
Pops and clicks with large amount of memory usage. This is system specific. My current template is 14GB or so, and I don't have this problem. Make sure that you have done the registry "hack" to increase the number of Instruments from 60 to 100 and turn off your paging file.
-