Originally Posted by: michi

Hello Peter,

of course we'll help you to fix this issue! Please send an email to , I'll sort this out for you straight away.

Best, Michael

Thanks, Michael—just sent you the email!

Peter

Originally Posted by: michi

Hello Peter,

You'd see the expire date of your new protection plans in your personal user area MyVSL - My Keys.

I hope that helps!

Best, Michael

Well, it "helps" insofar as I now know that I shouldn't have bought the plan as soon as your reminder came in. :-) My current plan doesn't run out until 10 Nov. But because I acted promptly on the reminder from VSL, I just unintentionally threw away a month of my old plan. In other words, because I bought my new plan on 5 Oct, it will expire two years from Oct 5. Had it been clear from your reminder that the plan expires two years from the purchase date, I would have waited until 10 Nov to buy it. For the record, here's what your reminder said:

"Please purchase another Vienna Protection Plan with a new license before the expiry date to keep your VSL licenses protected without interruption."

I took "protected without interruption" to mean that my coverage would simply be extended from its current expiration date—that's how it works with iLok, with Waves Protection Plan, even the dreaded Pro Tools service and updates contract. Why would I have bought a plan a month early if it meant I was throwing away a month of value, a month I had already paid for?

Can this be fixed, and can you extend my new plan until Nov 10, 2020? I mean... I realize we're talking about a tiny amount of money! But it feels wrong. In any case, I humbly suggest that you clarify that each plan expires two years from the purchase date in future emails.

Thanks,

Peter

Forgive me if this is duplicative of an existing thread. But this same question just came up for me, and since the existing thread is long and a bit confusing, I want to lay out the question slightly differently, and I don't want it to get lost in the shuffle. This does concern the same ambiguity that prompted someone to start the earlier thread.

I received my Vienna Protection Plan expiration warning today. I have two covered license keys; my current plans expire on 02 Nov 2020. I acted on the reminder, and purchased my new two year plans today. I have not yet activated them. Which of the three following statements is true:

1. My new plans will expire on 05 Oct 2022 (two years from today, the purchase date), even though I have not yet activated them.
2. My new plans will expire two years from the day I actually activate them on my licenses.
3. My new plans will expire on 02 Nov 2022 (two years after the expiration date of my existing licenses), even if I activate them before 02 Nov 2020.

It must be the case that only one of the above statements is true—can you please clarify, which one is it? :-)

Thanks,

Peter

Thanks, Paul. It's a really useful feature in DP and PT—hope it will be implemented! One other folder-related request: I'd love to see a slightly greater decree of indentation of the channel title when a channel is placed inside a folder. Currently in Channels View, it's hard for me to tell at a glance which channel names are folders and which are instrument or plug-in channels. I realize screen real estate is a concern; I'm just suggesting a very slight increase in the indentation of plug-in channel titles.

PL

Originally Posted by: Paul

Hi Peter, 

That's not possible in VE Pro (yet). You need to create a folder and then drag the selected channels in there. 

Best, 
Paul

Originally Posted by: Dietz

No other reason than "Nobody took the time to implement it", to be honest ... 

Love the honesty! Thanks.

PL

Originally Posted by: Dietz

The feature would be _perfectly_ useful, and as a matter of fact it is on my personal wish-list since a very long time (... since the days of legacy Vienna MIR, actually). For one reason or the other it never found the way into the engine`s code, which is a real pity.

That said, I have to point out that sometimes the better-sounding solution is _not_ what looks nice on a MIR Venue`s stage, and I find my Icons looking in other directions than the Main Mic surprisingly often. :-)

Thanks for the reply! And indeed, visual perfection does not necessarily mean audio perfection—but it can be a great place to start from.  Curious, though—is there any technical reason that that shortcut couldn't be implemented?

PL

Is there a way to do this? E.g., in DP or PT (finally!) you can select a set of tracks, r-click on them, and choose to create a track folder populated by those selected tracks. I realize that word is "channel" in VEP7, not "track," but same idea—is that currently possible in VEP7?

Thanks,

Peter

FYI I just got a response to a direct email from me that asked the same question. The answer is that there is no shortcut for this at present, but the request has been forwarded to the developer team. If anyone else would find this useful, I'd say, chime in!

Cheers,

Peter

Hi,

A friend who's new to MIR just asked an interesting question. The fact that we can rotate instruments so that they face in any direction we want is cool. But Is there a keyboard shortcut that allows us to automatically point instruments at the Main Microphone, say, option-clicking on the end of the directional indicator? If not, can there be? :-) Apparently Virtual Sound Stage 2 has that feature.

Thanks,

Peter

My working method involves assigning many of my sounds in VEP to different VEP output channels. Is there a way (as there is in Pro Tools and DP) to determine which outputs have already been assigned? If not, would you consider making that change? This could be done by displaying the already-assigned outputs in the dropdown menu in bold, or in some other color. Anyway, is there a way to already determine this? 

Thanks,

Peter

I'm gonna reply to myself and say, great idea, me!! :-) Seriously, can we get the ability to sort MyVSL by date? Really would be very helpful.  Thanks.

Peter

Sorry—I realize I asked this question last August, and Paul, you gave me a good workaround—clicking on the existing file name in the destination folder will fill the file name field with that name. But I'll use this opportunity to point out that, since I vaguely remembered asking this, before I posted today I did try searching for "Save As" in the forums—no results came back. Also, I looked at MyThreads; the ordering of threads seemed vaguely like it was oldest first, but on closer examination, I discovered that it's kind of random. Can you allow us to sort "MyThreads" by date? (I did ultimately find my old thread in one of the middle pages.)

Thanks,

Peter 

Hi Herb, Paul et al,

In almost all other Mac programs I can think of, when you execute a "Save As" command, the dialogue comes with the current name of your file already filled in; you can then just append a "2" or a "B" (or the date) to the name in order to quickly save it as a new version. But in VEP, the file name field comes up blank in the dialogs for both "Save Project As" and "Save Server Project As"; is there any particular reason for this, and would you consider changing it?

Thanks,

Peter

While it's great that we can filter our MyVSL page by file type, I'd love it if additionally we could choose to sort by date, so that all the most recent updates were at the top or bottom of the page. I know auto-update is built in to VEP 6, but because I'm updating on two different machines, I prefer to manually download the install files only once. Anyway, that would be a nice additional feature. Thanks.

Peter

This is somewhat related to an earlier thread of mine, but with a twist. As VEP 6 works now, Cmd-S saves the instance, and Opt-Cmd-S does a "save as" of the instance. Would you consider letting us choose via a preference whether or not those commands save the instance or the server project? The way I work (decoupled preserved instances), I almost always save server projects and almost never save instances. In VEP 5 those commands worked on the instance when you were in an instance window and the server when you were in the server window; VEP 6 gives us no option within the program to save the server project via a key command. If I have to choose one, personally, I'd rather have the commands apply to the server project. Possible to give us the choice in a later release?

PL

Thanks for the reply. Guess I don't quite understand the difference between "plug-in parameters" and "custom data" in Paul's earlier message. For my edification, can you clarify? (I'm not doubting you, I just like to understand this stuff.)

PL

Originally Posted by: Paul

As you are probably saving the file in the same folder as previous files anyway, I´d click on the file name of a previously saved project and add/change whatever you like. 

We´re focussing on bug-fixes and major improvements with VE PRO 6 right now, but I´ve noted your request as well. 

Hadn't realize one could do this! Nice workaround, but a tad dangerous—working at high speed, it would be easy to click on the wrong name, change THAT, and end up very confused in the future... :-)  Anyway, thanks for noting the request.

PL

OK, last comment about file saving! This has been a question I've had since the beginning of VEP. In virtually every other program I've used (music-related and non-music-related), when you want to perform a "Save As" operation, the "Save As" dialogue box comes up with the name of the current project in the "file name" slot. This allows you simply to add an incremental number (or today's date) on the end of the file name and save, rather than having to retype the whole file name. I'd find this a nice time-saver. Is there any reason it can't work that way with VEP projects and server projects?

Thanks,

Peter

Ah, yes—thanks. Nice touch, separating the menus—much clearer. 'Twould be nice if "save server project" and "save server project as" got their own key commands...

Thanks. And now... how do we do a "save as" of a VEP project (i.e., not a metaframe)? The floppy disk icon in the VEP header bar lets you "save the current project." But let's say I want to make a few small changes and save the current project (not the metaframe) with a slightly different name. Is there still a way to do that, as there always has been in earlier versions of VEP?

PL

 Interesting point. In fact, I always use VEP decoupled for that exact reason, i.e., that when I don’t, DP takes a very long time to save. It’s not like being asked one more time “Do you want to save” when you go to close the program (right after you've just saved) is that big a deal—it’s that it plants a seed of doubt in one’s mind that the project is really saved. I wonder, though—is there any way to build some sort of “software flag” into the code that gets thrown every time a change is made after a save? That way, when the user wants to quit, VEP wouldn’t need to compare the entire contents of a metaframe bit by bit to see if something’s changed—it would simply check the flag. I say that as someone who knows nothing about writing code. Which may be obvious! :-)

PL

Is there an easy way in VEP6 to save your metaframe, as opposed to the individual instance projects? As it happens, I use one huge instance for my orchestral library (performance with DP is much better that way). I'm finding that in VEP6 if I want to save the metaframe itself, I have to detach the project instance in order to get access to the metaframe window. I can imagine for people that have many instances in a metaframe this would be cumbersome.

Am I missing something? Is there any easy way to do what I'm asking in VEP6?

Thanks,

Peter

Very excited about the new VCA folders for VEP6! Was almost excited about the new option to turn off "ask to save changes on exit." BUT... then I discovered that the setting is absolute—i.e., if you deselect the "ask to save changes" option, it will allow you to close the metaframe without warning even if you've made a change since the last time you saved. Can this feature be modified to work the way it does in most programs? What I would like is the following:

• If there have been no changes to the metaframe since the last time I saved it, I should not be asked if I want to save when I close the server (since I've already saved).

• If there have been changes to the metaframe since the last time I saved it, I should be asked if I want to save when I close the server.

The way it works now, the preference setting is absolute: With the option deselected, if I make a change to a VEP instance and close the server, I'll lose that change without warning. All other programs I'm familiar with (and not just music programs) give you such a warning whenever (and only if) there have been changes since the last time you saved. Curious—is there any reason VEP can't work that way?

Thanks,

Peter

This may sound like a stupid question, but... do you have an actual instrument loaded? Sometimes I end up with empty instruments for various reasons. Selecting "reset windows" from the view menu consistently fixed the problem for me.

Peter

Leon—are you saying that all plug-ins instantiated in series on the same track of a DAW necessarily use the same core? That's useful info if so.

Peter