BUMP

I have several concerto projects, each with dozens of VI player setups (not VI Pro). What must I do to have the player show all of the active, licensed instruments? Please don't tell me I have to manually change every one of them.

OK I now have licenses updated on three iLoks and Directory Manager lists the correct physical storage locations for the sample files.  The player GUI shows nothing available. How do I proceed from here?

Paul,

I have the vivolume files on my local storage disk. I also still have all the original dat files on the same local storage. Can you please confirm that the dat files can all be deleted? Thanks in advance.

Ray

I upgraded from VEP6 and the process went to normal term. When I start VEP7 from the task bar, it hangs for more than 4 minutes (the longest time I've watched it). Then if I end process in task manager, and simply try another start, it comes up normally. Is there a log file somewhere I can look at? Or is there a quick fix known here?

I'm using v5.3.13408 and the patch listings have disappeared from the players in

an existing project. The previously assigned patches show up with a brown

background and the keyboard is entirely grayed out. There is no audio produced.

When I pull down "show licenses" under the version number, i get a list of all

active licenses supposedly available. I've run the maintenance routine for the

e-licenser. What to do next?

******************

This was due to a bad SATA connector on the motherboard.

 Just glancing at your setup, I'd say you'd have no problem at all.

 I unchecked the option as you suggested and that fixed the problem. Thanks for the assistance.

 I don't see a DAW listed, but for one thing, you can try Cubase 6, use note expression and get rid of the cross fade.

Two, you could put the accented note on a separate track, assuming that's where you're having the problem.

Three, you'd have to do some elemental work with a wave form editor - kind of time consuming.

regards,

Ray

 I never received a reply from anyone at Vienna, so I'm not sure what if anything is being done on this. You advertise that if I just open a metaframe file, then go have coffee and return, all of my instruments will be loaded and waiting. What I'm telling you is that is most certainly not the case here. Everytime I open a metaframe, I have to go back in each instrument instance, purge all the samples and reload.

Are you aware of the problem?

Is there anything being done to create and issue a program fix?

 I have a profile built to load DVZ Strings. The load process works, but just never seems to complete. I always have to purge and reload most of the sample libraries. I realize they're a competitor, but would it be possible to make a VEP program change that would allow the profile to complete loading?

 My version of eLicenser is 5.4.8.13. I'm working in Vista 64 bit without any problems. I just happened to check for an update and found out about the current support arrangements changing. There isn't much version documentation on the new support site, and its not exactly clear if there will be any support in the future. I'm wondering if there is any compelling reason to attempt an LCC update. This process frankly creeps me out because it seemed I always had a day or two of problems getting things to run afterward. Somewhere in the middle, we'd take a break and go through a couple bottles of Jaegermeister. That would give us the vision and drive to reach a working solution. Anyway, unless there is some real benefit to an upgrade, I'd prefer not to invite  software trouble. Second, we're just wondering if VSL might  be thinking of adopting a different security vendor in the future. Its OK if you don't want to answer that one. Thanks in advance.

 I downloaded the demo and installed it for use in 64 bit SONAR 7 producer. When I started the plugin scan to make them available in SONAR, I got one message after another telling me I had fewer starts left. By the time the scan got to the equalizer, I had 1 start left, then none, and the scan process stopped responding. Isn't there a way this thing can just work for 7 days or something like that?

I tried sweeping a cello loop and was somewhat successful in notching out the noise, but not without significant impairment of the underlying cello sound. When I have some time, I'm going to see if Z-noise is more effective.

It just means the directory manager must list the library you intend to update. If its already there you can continue without any problem.

As an example, insert a cello section patch of a sustained no vibrato note. I think D5 is the highest note in the instrument range, and I start hearing the offending noise around G4. I honestly hadn't noticed it before. One of my customers pointed it out. She said she heard something odd in the strings of a concerto I'd finished. I put up a patch, and she zeroed right in on it. I think its more noticeable at higher dynamic levels and volume, which makes me think its a resonance that was recorded with the samples.

I had a piece that required using a cello section in the upper octave of the instrument range. I hadn't worked VSL that high before and was a little surprised when I started hearing a new noise in the samples. It's a hissing sound that notched out partially in the 300-360 range. I checked other OS 1 and 2 samples and the noise is a common occurence in most of them. I'd appreciate hearing from anyone that's been successful in filtering out this noise.

If the licenses are visible, and your matrix is populated, you might be out of RAM on your 1 GB machine. Try rebooting, load your host, and assign a single patch to a blank matrix. If that doesn't work, and Christian doesn't have any other ideas, you might need to install another 1GB memory.

Hi Eric,

I've occasionally lost connectivity in SONAR 5 this way. I kept staring at the interface that showed a matrix and all the patches I thought should be there, but nothing would play. I finally thought I'd start over, and when I went to the matrix screen, I would see the interface indicating I had no licenses installed. Check if that's the case. If it is, CM will work with you to make sure your firewall and/or av app is configured correctly.

Hi Mike,

First, in order for any of this to work efficiently, you'll need to have 4gb ram installed on the slave running VSL patches.

Second, you'll need to edit your boot.ini file to add a logon option for the 3gb system version. Your boot.ini file will end up looking something like:


[boot loader]
timeout=3
default=multi(0)disk(0)rdisk(0)partition(1)\\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\\WINDOWS="Microsoft Windows XP Home Edition 3GB" /noexecute=optin /fastdetect /3GB
multi(0)disk(0)rdisk(0)partition(1)\\WINDOWS="Microsoft Windows XP Home Edition" /noexecute=optin /fastdetect

Third your host application and the vst dll files need to be large address aware. You'll need to edit their command lines, and that can be done easily with LAATIDO, a utility Mattias wrote. I haven't checked, but it was last available at: http://www.musikbanken.se/laatidosetup.exe

More reading on this can be found in this forum under the sticky topic that has Mattias' name on it.

Hi Mike,

I had the same problem when I first started using the strings matrices. I moved them from a 2.6 gHz machine to a 3.4 gHz machine with no improvement, so I don't think its your chip. Your OS is taking 500Kb or more, so you're probably getting close to your RAM limit. If you're using the supplied matrices, start over with your own, using only the patches you need. This should give you some extra room to load samples. If your motherboard has two more memory slots available, I'd strongly suggest you install 2x1gb additional memory and enable the 3gb switch. You should then be able to run all of your string sections on a single slave.

Sorry - I just went back through this thread and am finding it seems to be really irritating some people for some reason. The original question was about selling or donating VSL products. The original answer was that you can't do that because the EULA says you didn't buy a product; you just purchased a license to use it. What I'm adding here is that several US Appeals Courts have decided you are in fact buying a product, and that a copyright holder can't prevent you from reselling (or donating) your software by EULA limitations of your first sale rights. OK? You all have a nice day.

It has to do with requirements for a valid contract. One of those requirements is that the terms and performance of the contract (in this case, the EULA) must be legal actions. If a contract contains a requirement that is illegal under federal law, or within any state jurisdiction, that requirement is void. It wouldn't matter when you agreed to the clickwrap.

If you were to research this issue, you would quickly find numerous U.S. cases that illustrate just how divided it is. Many courts have upheld section 109 first sale rights. But there are a few that have been decided in favor of the copyright holder. I think its safe to assume this won't be resolved for at least several years.

Regarding dbudde's original question and cm's answer, everybody in the USA is governed by federal law outlined in section 109 of the Copyright Act. You can read some understandable background at:

http://en.wikipedia.org/wiki/First-sale_doctrine

Simply put, just because VSL says their EULA removes your first sale rights, doesn't make it so. The problem is that the issue hasn't been resolved by the Supreme Court, and there have been conflicting judgements in the various Circuit and Appeals Courts where this has been argued. So, if you want to sell your old copies, you can because existing federal law voids the EULA provision that appears to forbid you from doing so. However, since VSL doesn't care about federal law in the USA, they would remove authorizations if they discovered the software had been sold. Or they might file a lawsuit for damages. They would make the whole experience as painful and expensive for you as possible. So for a few hundred bucks of software, it isn't worth the battle. Someone that has the time and money will eventually get this settled. But that probably isn't any of us.

Eventually this will reach the Supreme Court and get resolved. EULAs are getting more restrictive and even pre-emptive, and the most greedy companies will provoke action. For example, the agreement for Vista allows Microsoft to install their "malware" software with the OS. If it finds any software on your PC it doesn't like, it can remove it without asking.

For now, keep your old files. When the issue is resolved, its likely the courts will find that you purchased the software; that it was a sale under the terms of the UCC and not a lease or a right to use. You'll then get back your first sale rights.

Hi Elksman,
You should search this forum for Mattias Henningson's threads on the 3GB switch. I think most of your questions will have answers here. You can also contact Mattias directly at www.musikbanken.se , or look up his article in the June/July 2006 issue of virtual instruments (www.virtualinstrumentsmag.com).

You'll need to make a simple edit to your boot.ini file to boot up with the switch active. Mattias also has a small app you can download that checks the LAA status of any exe your using, and can set the necessary header bit.
Several of us have used this material with good results.

Best of luck.

Regards,
Peregrine

You should be able to get a P4 or D9xx for very little, and it should perform just fine for a slave machine. I expect you could get a board/chip combo for less than $250 U.S. that will clock over 3GHz. If it isn't too big a cost difference, faster memory is always better than slower.

BTW - since the new chips arrived, we can buy the old P4 machines off the shelf, configured like this, for about $500 or less.