Originally Posted by: plowman

You're no one's crazy uncle. Because you discussed this on the forum, and because VSL replied, I am better informed. I now realize that signing up for this coverage takes a little calendar vigilance on the buyer's part. So thanks for posting. 

Thanks, plowman.

Originally Posted by: michi

Hello John, Please rest assured that you won't loose a single day of the protection period. Let's hope that your ViennaKey works flawlessly forever, but in case of a problem, there will always be a human member of our support team that takes care of your specific situation, and we won't "torture" you with missing time from a period overlap. We're always looking for the best solution for our customers! I hope that helps! Best, Michael

Michael,

Thanks for your kind assurance.

My point has never been that VSL is trying to torture me. To me the question is legitimate, but It sounds like no one else has ever brought it up before, so it's never been considered. Perhaps no one else thinks it important enough to bother with.  What's a few weeks out of two years. If so, I guess I'm the crazy uncle. 

I do rest assured that I can always count on the good graces of VSL staff. That has always been my normal experience.

Given that some might consult this thread in the future, it appears for the record that the answer to my question is this: Don't worry about the official renewal date becoming earlier by a few weeks every two years, VSL will take care of me.  Either that or always make sure I renew within as few of days of expiration as possible.

Originally Posted by: a.machat

I’m really sorry that our VPP process isn’t more convenient and I truly can understand that an automated renewal would be a nice feature. Because of the given setting by Steinberg’s eLicenser you get a new license with every new Vienna Protection Plan for your eLicenser USB Key to decide again which key should be protected (in case you have more than one or a new key).

Thank you for your understanding!

Best,
Alexander

Alexander, looking again at this last paragraph in your reply, I wonder if perhaps I am not also misunderstanding you. Are you saying the problem I identify, the abrupt loss of paid time if I renew right when I receive my first reminder, is an unfortunate necessity because of technical considerations having to do with USB keys and licenses?

Alexander, thanks for your kind reply. The system per se with reminders, etc., is fine. That is appreciated. 

But it seems the problem I'm bringing up has either not been understood or not addressed. I'll try again to explain. It does not have to do with any inconvenience in renewing, nor does it have to do with needing help remembering to do so.

It has to do with the (needless) loss I incur if I renew right when I receive a reminder, weeks before the expiration of my current license. On the day I purchase that renewal, VSL starts the clock on my new two-year plan. But since this is weeks before my current plan has expired, this causes me to lose the current plan's remaining weeks. As the customer, I literally take a loss when I renew unless I wait until the day my current plan expires.

What VSL should do is start the clock on my renewal the day my current plan expires and not before. It's only right that I should get the full two years of coverage on my current plan even if I renew right when I receive my reminder. Instead VSL abruptly stops my current plan before it expires and puts in place a new two-year plan on the day I purchase the renewal. I'm covered, to be sure. But I've taken a loss in covered time.

This makes no sense to me. I can't recall any company I've ever dealt with in any aspect of life that has ever set up renewals this way. It's not that I need automatic renewal, it's that I want all that I've paid for.

Let me reiterate, I'm a happy VSL customer overall. That's why I find this problem so unsettling. 

I received an email from VSL that my Protection Plan is up for renewal in a few weeks. I went to the appropriate page to purchase a renewal but some language I encountered there, that the renewal lasts two years from purchase made me wonder if by renewing a few weeks early I actually lost those weeks. Shouldn't the renewal be tacked on to the end of my current plan, I wondered?

So I contacted sales and got a prompt response (thank you!) that indeed the two-year renewal would start on the day I purchased it, not when my current plan expired. The concern I had turned out to be justified. If I renewed at any time before the end of my current plan I would simply lose the remaining time I had paid for two years ago. That surprised me, so I asked for clarification, and was told that this is how it works. The staff who helped me were helpful and prompt. All they could do was tell me the policy.

I am a longtime, happy VSL customer, but I find the policy surprising and unsatisfying. I am put in a position of either eating my remaining time or putting my renewal on a "to do" list and hoping that life doesn't get so crazy at that particular time that I am unable to get to it or, perhaps even forget it as it gets buried by other "to do's." 

I was told there would be a few days grace period, but it concerns me that the burden is put on me, the customer, and that an early renewal to "get it off my list" actually penalizes me. I find this puzzling.

I would be happy to hear further comment from VSL, and this is not an attempt to engender dissatisfaction in others. I'm just genuinely curious if I'm the only one who finds this particular policy unsatisfactory. I'm hoping VSL will review it and find a way for me to pay now, while I'm thinking about it, and have a full two years tacked on to the end of my current plan.

Originally Posted by: 145684

I'm running the latest versions of Logic Pro X and Synchron Player.
I'm not sure what I'm doing wrong, but I'm unable to map the Velocity XF function to my midi keyboard mod wheel.  I'm using a Nektar GX 61 keyboard. I haven't been able to find any tutorials on this, so just posting here.

Thank you in advance for your help.

On the exact screen you show in your picture, hover over the "CC2" above the Vel.XF fader. You will see a small down arrow to the immediate right. Click on it, and a dropdown menu appears. Select "Controller" then "0-15" then select number 1, which is the Mod Wheel. That assigns the proper controller.

If the little power button icon on the bottom left of the fader is blue, that means Vel X-Fade is turned on, you should be good to go. If it is ever not blue, then you need to activate Vel X-Fade by clicking on it until it turns blue. 

.

.

Wow, Sam, as soon as I selected the bottom item in the dropdown it restored all the items in the list.

Problem solv-ed. 

I am running dual identical 27-inch 4K displays scaled to 175% for 65-year-old eyes.

Hopefully this means the problem is display only and not that my Basic View fader assignments are going to require constant care and feeding. 

Thanks a bunch!

Edited to add: Using the Synchronize Control Map setting allowed me to quickly restore the Velocity Map fader to the Basic View of all my channels. At least I now know how to deal with it if the problem recurs. I reinstalled the recent VI Pro update just now, and everything looks normal with the fader assignments.

I went ahead and tried uninstalling Vienna Instruments Pro Standalone using the Windows uninstall for  (in case it should work), also reinstalled previous version 18624 (I typically keep a copy of the previous version). No effect. Same problem.

VI Pro 2 in VE Pro 7 on Windows 10 Home

I'll roll back. I did install all the recent updates yesterday, including VI Pro, so perhaps that's the culprit.

I can find the VI Pro Standalone, where do I find the plugin, which is what I was using, and how do I make sure I've completely uninstalled it? 

Let me know if you want me to send you a copy of the file.

Never had this happen before.

In VI Pro the Basic> Slider Assignment Dropdown is showing a truncated list of assignment options. Specifically it is no longer showing Velocity X-Fade as an option for any of the instruments in my Brass instance, even though it shows assigned to CC2 in Advanced> Control Map.

Synchronize Control Map had been on, and I did some editing of percussion instruments and then brass yesterday. I don't need Vel X-Fade for percussion. I suppose I might have removed the slider from one of them, though I don't remember doing so. So I turned off SCM in case this was responsible, but it doesn't make any difference, still no Velocity X-Fade (see attached image).

I also loaded some previous brass presets as part of my editing, but that shouldn't limit my options once I load the, should it?

I wondered if I had inadvertently started creating VI non-Pro channels, but that's not the case.

The Vel X-Fade slider is critical for my work, as you might imagine. Help!

Originally Posted by: bbelius

Manuals are now located here: www.vsl.info

Great news, had no idea the a manuals page had been opened up!

Thanks, Ben

A PDF manual for each VSL item purchased should be included among the available files in your user Download page on the VSL website. At the top there are buttons to filter what you see. Make sure you select the manuals button or it won't show.

I can't remember exactly how it's presented, but when you purchase any VSL item, if you do not currently have a key registered with VSL you are presented with the need to purchase a key for your purchase to work. If you no key it will not work. The same is true with Steinberg.

Again if I recall correctly, you may have to delete the key from your cart if you already have a key that's only registered with Steinberg. VSL has no way of knowing you have a key, and they are only trying to help first-time customers. One thing I do remember is a number of years ago when making my first VSL purchase I had to figure all that out.

Re: tutorials, many VSL product pages have a selectable tab called "videos" that includes videos from past and present. Here is the one for VE Pro 7: Vienna Ensemble Pro 7 Videos . From my experience VSL videos are not really designed as effective tutorials. They move very quickly, short and to-the-point, without slowed-down demonstrations or repetitions for people who might need it.

Originally Posted by: bbelius

Yes :)

Great, thank you, sir!

Thanks, Ben. I'm not clear on your answer. I take it that when you say "with everything" you mean including channel data. Am I correct?

When saving a VE Pro Server project, I'm curious if it includes the current state of all instance projects including channel data, or if it does not include the channel data, saving just the file reference for each instance?

When I make changes to the channels in an instance I tend to save not only the instance project but the server project as well, just in case. But should I be reserving server project saves only for those times I make changes to what instances are referenced in the project?

Problem mostly solved by re-creating the instance. It may also had something to do with VE Pro auto-adding bus channels to venues.

I've decided on my own that my next step will be to re-create the problem instance and see if it resets something I haven't yet noticed.

Can't figure this problem out. Here's the facts:

VE Pro 7 Server Project

6 Instances: VI Winds, VI Brass, VI SE Strings, SY Pianos, VI Perc, VI SE Vocals

Except for SY Pianos all use VI Pro channels and MIR Pro

All set up the same so far as I can tell, all working fine except the VI SE Strings

The VI Strings are getting a proper MIDI signal on each channel, but unlike the other instances the audio signals and volumes are almost nonexistent. If I push the Channel Volume, Master Volume, Vel-XFade, and Expression Sliders to the max I can get very low volumes, but if I set them at 90 (my normal default) you cannot hear a thing. Channels to group bus and group bus to output 1/2 look to be routed properly, the same as the working instances. MIR Pro settings are the same, placement on the Grosser Saal stage are similar to what I've always done with success. Nothing looks amiss in VI Pro, presets and patches fine and active.

I'm at a loss. Any ideas what to investigate next?

Thanks, I reinstalled that version (had been running it).

I may have figured it out. Somehow in my VSL reboot I was working in the 32 bit version of VE Pro Server instead of 64 bit. Not sure that was the problem, if I have any further issues I'll check back.

Edited to add:  After several hours, no problems since using 64 bit instead of 32 bit.

After a hiatus with VSL I recently started up again. Am using the current version of VE Pro 7.0.1056.

Everything works fine until I add a second instance, at which point it crashes, usually when I attempt to add an instrument to the new instance or try to load a MIR Pro venue. It is not generating crash dumps, although I do notice two text files in my AppData folder with the appropriate time stamp (about 9:58 PST June 25) , so I'm attaching them here.

Not sure what is happening.

Originally Posted by: songdiver

...it does not state that the file definitely is NOT infected...

I can´t install/use VI now because it is in quarantine.

Thanks for advice!

Ditto. Need to know for sure it's not infected before I can deal with it.

When I click to install the latest Vienna Instruments download for Windows (18860), Avast quarantines it, saying it is infected with FileRepMalware. Is this a false positive? I've had VSL files trigger an inspection before, but never a quarantine.

Haven't had a chance to use it yet, might not for a few days, but I appreciate that the VSL team has released an update to VI Pro that makes it retina-ready and flexible enough to handle various graphics-resolution platforms. And they made it a free download for those who already own it. Gotta appreciate that.