[VE PRO] Wishlist

[petera]

I think everyone will agree when I say VE Pro is the most rocking software released this year.I hope it's not impertinent to ask for some helpful fixes and functions to improve this genius software.

I am very glad the Vienna Team already indicated to...

• raise the number of VE Pro instances (currently there is a limit of 8 per server)
• improve the save-function, so that saving and loading of a song project will be much faster
  (see also http://community.vsl.co.at/forums/t/22843.aspx)
  

Now I have one more wish, but I think it is very small:

• Is it possible to save the position of the server windows? So that they open at the same position where they were when I closed them? But this is lowest prio, I think I am able to survive without it ;-)
  

Best regards,

Peter

[MS]

1. raise the number of VE Pro instances (currently there is a limit of 8 per server)

In the works.

2. improve the save-function, so that saving and loading of a song project will be much faster
(see also http://community.vsl.co.at/forums/t/22843.aspx)

Already done, should be about 3-4 times faster.

3. Is it possible to save the position of the server windows? So that they open at the same position where they were when I closed them? But this is lowest prio, I think I am able to survive without it ;-)

Each instance position is already saved. Do you mean to save the position of the actual server window itself?

[petera]

@Another User said:

Do you mean to save the position of the actual server window itself?

Yes, the position of this window itself:

Best regards,

Peter

[petera]

Hi Martin,

just one more question, then I will stop disturbing you at developing genius software ;-)

Do you have a rough estimation when we can celebrate a first update of Ve Pro? Only to know when I can buy champagne [:)]

Best regards,

Peter

[Paul]

Hi Peter,

you can go ahead and buy soon. And then enjoy the anticipation.

Apart from your wishes, there are some other things we´d like to see implemented.

Best,

Paul

[petera]

Thanks Paul,

my lucky creditcard is looking forward to every update it can catch. But please don't tell it my wife [:)]

Best regards,

Peter

[Paul]

Another reason to get some champaigne - and share the anticipation [;)]

Always a good move.

Best,

Paul

[Sergino Futurino]

 I would like the return of the dots in the instruments panning arches.

Is there any particular reason they are not there anymore?

[koassistant]

I hope that program change pass-trough will be integrated for the VST3 version. That would be an "out of the ballpark" hit.

[skatz]

Hey Martin, thanks for updating us, and for all the hard work on this great software. I posted a query in another thread about the possibility of adding some virtual IAC MIDI ports to VE Pro (ala Plogue Bidule, others) to allow for accessing of additional instruments inside each VE instance. You would still be limited to the same 32 channels of audio, but you could solve this issue of addressing more than 16-channels per AU/VST2/RTAS instance in one fell swoop without adding any more plugins or much CPU overhead. Is this a viable idea?

[brett]

I also vote for Program Change pass through to VST3

But here's another big one for me.  It seems that overall latency is not passed to the host for correct Plugin Delay Compensation when using insert effects that have a large delay.

For example, load up a cpu intensive plugin with a large delay like a multiband compressor into an insert slot within VE Pro, and hosts like cubase with plugin delay compensation cannot adjust for this additional latency upon playback.  This means that this VE Pro track is out of sync with the rest of the project.  Is this right?  Could you confirm this Martin?

Brett

[edit] thanks to another members question over at Cubendo, it seems that VEP does not even have plugin delay compensation within itself!  This means if you have a high latency plugin like a compressor on one track within VEP, it is now out of sync with a second track in VEP.  This restricts the sort of plugins you can use within VEP doesn't it.  Am I mistaken Martin, or is there a fix coming for this?

[MS]

@brett said:

But here's another big one for me.  It seems that overall latency is not passed to the host for correct Plugin Delay Compensation when using insert effects that have a large delay.

That is correct. If you think a little bit about it - it is not a very trivial task. VE Pro would basically have to report the latency of the "slowest" channel, then internally delay all the other channels - and report back this longest delay to the host. Thus, the playback latency when playing live - would be exactly that of the "slowest" channel. Not very nice imho. This is why we have chosen not to implement it so far.

In VE Pro, I would suggest to use effects which don't introduce such latencies. Vienna Suite is a good match.

[brett]

Thanks Martin.

[jvdieks]

a thing that would be nice is a midi controller learn function, like in live.. so you can choose what midi controller does what on each plugin. this would fill the automation gap

[DG]

@jvdieks said:

a thing that would be nice is a midi controller learn function, like in live.. so you can choose what midi controller does what on each plugin. this would fill the automation gap

 

Huh? That's been in Vienna Instruments since day 1. Over 4 years now, AFAIK. [;)]

If you are talking about plugs from other developers, then go and hassle them.

DG

[jvdieks]

nah.. there's a controller learn function in live and i think in sonar too... which for instance isn't in cubase, which is my main DAW. A lot of people that come from sonar complain about that with cubase. in live you can select a learn mode (for the DAW) and then select ANY controller, fader or plugin function, then turn a knob and that knob does that function. this overwrites the plugin's own learn function i think (well, to be honest i havn't used it that much so i'm not 100% sure about the last thing). so this way you can make a manual mapping on your controller for ANY controller in that host.

[troyturner]

I am using a VST plugin drum module called Jamstix 2. Jamstix has different "modes" that it uses, most of which apparently require sync with the host. These modes requiring sync do not pass any sound through VE Pro, the only mode that passes sound through VE Pro is "drum module" mode. Another user has noticed the same problem I am having when trying to use this plugin, on another thread. I contacted the author of the Jamstix program about this, and his reply was: "The problem is most likely that Ensemble Pro does not send VST song position information (VstTimeInfo). This is needed in any jam mode so Jamstix can synch up with the host. Best regards, Ralph" This being the case, I would humbly request that VST song position information be included in VE Pro. (I hope this isn't a really difficult thing). Thanks Troy Turner

[michael_12374]

- Display of free RAM in the status bar would be very helpful.

- brighter font color of the preset list (now it's black on dark blue)

- Server Window Option: Automatic load a specific metaframe save

- Server Window Option: Automatic minimize to taskbar after opening

[MaD]

@michael_12374 said:

- Display of free RAM in the status bar would be very helpful.

Yes! I just wanted to write about free ram as well. Maybe a used / free display if possible. Could be a pulldown menu or mouse over effect on server or instance window (where CPU usage is). Just display it somewhere besides VI.

The automated minimize and mframe load would be great, too. Anything to reduce clicking things. [:D]

[Ashermusic]

A few requests: 1. A re-sizable GUI. On my second 17" monitor if I have 2 or more instances open, you cannot see them. 2. The ability to hide certain tings. i,e, inputs after they are created. 3. The ability to create multiple inputs, open and adjust sends on multiple inputs, etc. rather than 1 at a time. 4. The ability to view multiple instances in one Mixer page.