Hello Jean Roy,

give us a little time. Covering a whole musical piece is hard work - and there are MANY ways to achieve this goal. Jay Bacal and Guy Bacos couldn´t work more different, believe me.

As a comparison: Hundreds of thounsands of students studied Mozart, Beethoven, Bach, Debussy.... and even though all their music is now analyzed and has been explained and interpreted  thousands of times, each approach of every conductor, player, orchestra and hall will be different.

It´s a bit of a dilemma, but we´ll do our best with upcoming videos. In the end, it´s your musical knowledge, taste and talent that will lead you to your results.Especially if you want to create something new.

Best,

Paul

Hi Paul, 

I really appreciate this exchange!

I agree with you 100% but:

Every musician or conductors have begun much the same way... even if at the end, there are countless ways to interpret or conduct.

I will try an analogy to get my point across:

I conducted a choir for 15 years, at first I had to learn how to use a baton and the basic ways to conduct. I needed a base even though at the end, I had my own style.

But I had to see not only that I had to move the baton but make sense of how I moved it to get proper results.

Like Mr.Bacos video, I see that the baton can be moved but no clue as how to use it properly. I would at least need to see the midi files, when to do an articulation change and so on and correlates with what I hear. Then I can compare what I hear with what I see and then make inference to reach my proper goals.

This is what is lacking I beleive with VSL. I think one need to go through a good way to approach things even if in the end, I choose to develop my own workflow.  (There are bad and better ways to approach VSL.)

If one goes through a full process a couple of time,

one can at least see what is possible to achieve,

learn faster with less mistakes,

sees the major features with hand-on examples,

and achieve a good result the first time around.

And I think this is a key point. I'm sure that you would sell a lot more stuff if one could buy your products, goes through a "good" way to do things and achieve good results the first time around. I am not a professionnal but I am a serious hobbyst with over 25 years of experience with many synths and all kinds of music softwares.

I can attest that learning VSL was not an easy feat.

Lets face it; these softwares are very compicated and sometimes we don't even know what is possible to do with it.

VI Pro seems like a very nice tool to work with, if you get me through all the features with a real piece of music with actual midi files and all; even if it takes me a month to go through, the knowledge I'll get from that experience will bring me a great satisfaction and it will show in my music projects and all my friends will want to buy your products[:D]

There is too much difference between what we hear at first with these magnificient demos and what we can achieve at first.

Hoping it will help the process!

Jean Roy

And if I may add, full support for MIR!

Here are some other suggestions for GUI refinements:

 When clicking a dropdown list, it would be nice if clicking it a second time would close the list, rather than having to click elsewhere in the GUI to close it

Sliders can be reset to default by double clicking.  I suggest that it would be more consistent with common practice to Ctrl-Click.  It would also be nice to be able to reset spin button type controls, and double clicking is needed there to highlight the value for editing.

It would be a nice connivance to be able to copy by Ctrl-dragging, also a common convention.

There's currently no warning when you over write a preset.

When you save the Startup preset in Advanced view, VIp still starts in Basic view.

Bill

@jeancello said:

... I really think that a complete project workflow using VIPro with an in-depth explanation at every step would be of great help.

In other words, a mix of Mr. Bacal's demos with the midi and VSL preset plus a workflow approach like Mr. Kaufman did but at a bit more advance level.

(A bit like you did with SE demo but more in depth)

...

I'm just collecting experiences with VIPro...

Then I will prepare a small Tutorial which will produce a piece with VIPro with all the important (and special) steps just for this new Player "VIPro".

But let us get first the Final Version of this fantastic tool [H].

Beat

I'm definitely really hoping to get aftertouch added relatively soon and was sort of suprised it didn't make it into VIPro 2.  I hope it will be an option as a cell switching controller and in the performance controls. 

 I don't see how using aftertouch to switch cells could work.

Aftertouch is always at 0 until a key is pressed, then with pressure a value can be generated, but as soon as you let go of the key to play a new note, the aftertouch value will go to 0, so you'd always get the cell associated to value of 0. 

 The only way to make it work would be to hold a key down (out of range) with your other hand and control the pressure there, it  is difficult to get repeatable precise values from aftertouch, but a course 3 way switch might be achievable, with this two handed approach, but not useful enough to be on any priority list of new features. I certainly would never use it.

Aftertouch to be a CTRL Map source would be good option, though it would be good to have a range setting.

 I've never heard an artificially produced vibrato that sounded real.  What would be great would be to have progressive vibrato patches of varying delays.  I find the ones in Solo strings take just a little too long to get to vibrato.

Yes.  using it on another key was what I was thinking.  and of course aftertouch as a CTRL map would be much more useful and I would be happy with that. 

I am very lucky to have a kurzweil Midiboard and I can tell you the aftertouch is very controllable. and poly aftertouch gives me a lot more options so I can have one key basically act as a slider.   it also has an excellent feature called mono mode which is like auto voicing a little bit but to seperate midi channels.  each key pressed sends mono aftertouch on a seperate channel which can be useful.  one thing is it a way to enable poly aftertouch in only mono pressure supported synths.  of course with the draw back of many instances of the plugin you are using, usually only three or four will do.  I've tested it with VI pro by converting aftertouch to controller... it would be nice to not have to do that.