193,964 users have contributed to 42,904 threads and 257,885 posts.
In the past 24 hours, we have 4 new thread(s), 13 new post(s) and 81 new user(s).
@Marcusmax said:
That's a pity but good to know they are aware of it. I would have thought it was relatively straight-forward, given that other important stuff like the state of instances etc. are all saved. I imagine it's more that this is a non-essential issue and therefore not on the list of priorities to sort out.
https://forum.vsl.co.at/topic/60413/open-vep7-showing-instrument-by-default/1?page=1
Ah ok, should have done a search! 😉
It's not great that people have flagged this consistently and it's still not fixed almost a year after that thread was created. I also really value VEP and would be lost without it but this is an annoying issue that definitely warrants attention.
@Marcusmax said:
Ah ok, should have done a search! 😉
It's not great that people have flagged this consistently and it's still not fixed almost a year after that thread was created. I also really value VEP and would be lost without it but this is an annoying issue that definitely warrants attention.
Yes. I agree. VEP functioned beautifully before iLok but it was VST2 only. Something broke and even the F4 and instrument view menu command don't work. I think I got one post from @Andreas8420 saying that they could see the problem and would look into it. That was last September. I understand that they are probably very busy but it would be nice to get some kind of update. I don't even know if the VSL forum is active like the VI Control forum. I will try VI Control. VSL's @Ben does answer posts there.
@Marcusmax said:
I just posted about this myself on Vi-Control. Here is the link:
Very cool that you started that VI Control thread. We need more people to join in. Still no update from @Andreas8420 .
Please, to the 930 people who have read this thread, if you have anything to say, please go to this link:
https://vi-control.net/community/threads/any-way-to-get-vepro-to-save-a-project-with-an-instrument-gui-open.153590/
@plowman said:
This is a long-standing issue with VEP. They are aware of it and have commented on it, though not lately. At one point they indicated that it was a challenging bug to fix. It must be, considering the amazing feats VSL has achieved in other areas.
Unfortunately, the state in which a VEP project is saved will not affect how it re-opens the next time.
This and the inability to use remote start/stop are the two biggest kludges I face with VEP. And I say that as an enthusiastic supporter of all things VSL.
@plowman if you have time could you post about this on the thread we are trying to start on VI Control. Thanks.
@plowman said:
This is a long-standing issue with VEP. They are aware of it and have commented on it, though not lately. At one point they indicated that it was a challenging bug to fix. It must be, considering the amazing feats VSL has achieved in other areas.
Unfortunately, the state in which a VEP project is saved will not affect how it re-opens the next time.
This and the inability to use remote start/stop are the two biggest kludges I face with VEP. And I say that as an enthusiastic supporter of all things VSL.
Hi! While we are aware that people are still affected by this issue, I am afraid our development is not going to pick up further investigations into this matter for the foreseeable future. Sorry for not having better news for you at this point. Best, Andreas
@Andreas8420 said:
Hi! While we are aware that people are still affected by this issue, I am afraid our development is not going to pick up further investigations into this matter for the foreseeable future. Sorry for not having better news for you at this point. Best, Andreas
That's very disappointing to hear. 😞
@andyog, my apologies for not responding. I just saw your note this morning, and now comes the news that the issue will not be fixed.
I recently worked on a template that had over twenty-five instances. This bug was a kludge in the extreme -- constant extra-clicking to open. And that was compounded by the slow UI. My Mac mini 2018 is an Intel, which doesn't help.
No line of products means more to me than VSL. I don't like posting my frustrations. Indeed, I am surprised there are not more cheers for these amazing libraries on this forum.
But this issue and the aforementioned inability to launch playback from within VEP interrupt the creative flow like a fly in the studio.
Sigh, reach for the mouse, reposition, click and carry on. I can't control the problem -- only my reaction to it.
Thanks for raising the visibility of the issue.
@Marcusmax said:
@Andreas8420 said:
Hi! While we are aware that people are still affected by this issue, I am afraid our development is not going to pick up further investigations into this matter for the foreseeable future. Sorry for not having better news for you at this point. Best, Andreas
That's very disappointing to hear. 😞
It is disappointing. VEP is one of the greatest music software programs ever made. It deserves high priority.
@plowman said:
@andyog, my apologies for not responding. I just saw your note this morning, and now comes the news that the issue will not be fixed.
I recently worked on a template that had over twenty-five instances. This bug was a kludge in the extreme -- constant extra-clicking to open. And that was compounded by the slow UI. My Mac mini 2018 is an Intel, which doesn't help.
No line of products means more to me than VSL. I don't like posting my frustrations. Indeed, I am surprised there are not more cheers for these amazing libraries on this forum.
But this issue and the aforementioned inability to launch playback from within VEP interrupt the creative flow like a fly in the studio.
Sigh, reach for the mouse, reposition, click and carry on. I can't control the problem -- only my reaction to it.
Thanks for raising the visibility of the issue.
Thanks for your really cool reply. It means a lot to me.
