Vienna Symphonic Library Forum
Forum Statistics

182,309 users have contributed to 42,218 threads and 254,754 posts.

In the past 24 hours, we have 2 new thread(s), 16 new post(s) and 42 new user(s).

  • VSL Tool 2.0 Beta 1 available ...

    Don't loose your time to read my post ... download it !!! [[:D]] [[:D]]

  • Guess it must be for Giga because it doesn't show up in my EXS24 Tools list.

    Evan Evans

  • Hi Evan!

    Yep, we finally made it, the official beta-version of our redesigned Performance Tool for GigaStudio is ready. Many new features and more to come with the finalized version!

    All GigaStudio-users: Have fun with it (you lucky Logic-guys, you have always had the convenience of this new design and functionality, I envied you for so long!)!!!!!

    Best, Paul


    P.S.:I wonder if the "old" Performance Tool will be a piece of "vintage"-software in the future....

    Paul Kopf Product Manager VSL
  • Hi Paul,
    thanks very much for sharing the Beta.
    Some comments:

    What does the "45 days left" mean ? Sounds like a trial.... Will we have to pay for the final version ?

    It almost works perfectly - and yes - we now have access to the legato-release samples [;)]

    Well - some grafical bugs (placement of the squares in alternation and repetition mode, "thru mode" text with wrong colour and wrong font - "thru mode" window to small - wrong height.... ) - but I'm shure this all we be fixed in the final release.

    P.S. Any release date for the final version ?

    Greetings,
    Sebastian

  • Hi Sebastian!

    Thanks for the feedback (I knew you would discover these little graphical bugs, but we really concentrated on makeing the tool work, and yes, of course they will be fixed!)

    The 45 days trial version is simply to remind you to get the finalized version, to make you even happier!
    And please donĀ“t worry: you DON`T have to pay for the finalized Performance Tool, of course not!

    the release date for the finalized tool: before X-mas 2003, depending on how fast Santa Claus can program....

    Best, Paul

    Paul Kopf Product Manager VSL
  • [:D] [H]
    Great news Paul.

    Greetings,
    Sebastian

  • I found a little bug : can't load the same .PAL file in the same project.

    Wish list :

    - Add a "New" menu in the File menu

    Thank you ... [[:D]] [:)] [[:D]]

    Mathieu Laprise
    Sonomax inc.

  • Everyone else noticed that the repetition mode built into the legato patches now works? [:D]

  • By loading a legato file etc. the folder last opened is showing, not like before the folder with all legato settings... Could be corrected as well by choosing a costumizable path where the user wants to have the files located!!!
    What do U think about that?

  • Also something for the wishlist: Is there any reason why having a keyswitch for 'bypass' should be a problem? It would be fantastic, because then in any given project a midi channel wouldn't have to be dedicated to, say, legato or repetition, but could also be used for normal samples...
    [:)]
    Just an idea,

    Thanks,

    Simon

  • Okay, I think I've installed it wrong. It (the Giga tool) didn't want to load the old Performance setting files, i.e. VL-14 Legato, etc.

    So I trashed those, trashed the tool, downloaded the beta again, and unzipped it. Should I reinstall those files from the old versions?

    Sorry if I'm being dense.

  • Simon ... nice idea !!! So you can alternate between samples (legato, non-legato).

    Good [:D]

  • last edited
    last edited
    Hi all!

    @Another User said:

    It (the Giga tool) didn't want to load the old Performance setting files, i.e. VL-14 Legato, etc.

    So I trashed those, trashed the tool, downloaded the beta again, and unzipped it. Should I reinstall those files from the old versions?


    Nick, strange, very strange. Yes, please reinstall the "old" Tool Files. Should work.

    Thanks a lot for the feedback, everyone!

    Best, Paul

    Paul Kopf Product Manager VSL
  • last edited
    last edited

    @Paul said:

    That would only make sense for the Alternation Tool, because all other samples only work with the corresponding mode of the Performance Tool (playing Legatos and Repetitions without our Tool is not really satisfying, is it?


    Hi Paul. No, I was thinking exactly the other way round: A channel set in the perf. tool for legato, in use for legato samples. And then you suddenly want 3 notes in the middle using non-legato patches, so you trigger the 'bypass' keyswitch (which you're going to add for us! [[;)]] ), change patch to the non-legato articulation you want, play the 3 notes, then switch back again and un-bypass. I know, lots of people avoid patch changes within channels. I like to use fewer channels so I can see what I'm doing, and add patch changes. For this way of working, a remote 'bypass' would be fantastic (and surely much easier to implement than midi-switching of mode...)

    Anyway, that was my idea: to be able to temporarily bypass the legato or repetition modes, allowing you to use NON-lagato/repetition samples briefly on that channel.
    Hope I've explained better...

    Thanks,

    Simon

  • Hi Simon!

    Yep, I get your point.

    Still, which non-legato/non-repetition notes do you want to play? thereĀ“s veryvery many single notes for each instrument.... We need more RAM!

    Rest assured, we are thinking of a sollution (maybe all variations of long notes? or one variation of each duration recorded?).

    This of course initiates a lot of work on GigaStudio and some consequences for each user: new mappings, new gig-files, more disk-space, less instruments loaded.....

    Thanks for the input!

    Best, Paul

    Paul Kopf Product Manager VSL
  • last edited
    last edited

    @Paul said:

    Still, which non-legato/non-repetition notes do you want to play? thereĀ“s veryvery many single notes for each instrument.... We need more RAM!
    [*-)]

    Hi Paul,

    I actually just meant using the system as it stands now: On a typical setup I have maybe 30 articulations loaded in one machine. Perhaps 13 of these performance elements (rep. or leg). So just by programming patch changes into the sequencer for that channel, I can switch to, say, a number of cresc./dim/sfz or whatever articulations for that instrument. I want to be able to use those in the middle of an otherwise legato (or rep.) line, without the perf. tool 'getting in the way'. At the moment, the only solution is to use another midi channel and put these notes onto there.
    So it really would be enough for bypass to be triggerable by a keyswitch. Nothing more for now! (oh, can 'bypass' and 'un-bypass' be different keyswitches, rather than a toggle? Could get in a mess otherwise if starting in the middle of a piece...).

    Thanks for your help! [:D]

    All the best,
    Simon

  • Hi Paul,

    I have noticed with my single computer setup, that the Performance Tool doesn't pass on tempo changes from my sequence.

    I am running Gigastudio, Overture 3 and MidiYoke. With the Performance Tool closed, Overture executes the tempo changes, but with the Performance Tool open, it doesn't respond to them and uses the first tempo it comes across.

    I'm running Win 98SE on a P4 2.66. If I run Overture from another computer, there is no problem, but this means I can't use MidiYoke which gives me access through Overture to 16X4 individual midi channels.

    If I open Overture first after Gigastudio and then try and open the Performance Tool, Performance tool comes up with the error "MMSYSTEM004 - The specified device is in use etc".

    This was the same for the earlier version of the Alternation Tool.

    Any thoughts on how to deal with this?

    Craig

  • duocart, although not familiar with overture i'm assuming your midi routing is: overture - midi yoke - performance tool - gigastudio.
    the error message *The specified device is in use* usually comes up, if a midiport (physical or virtual) is already used by another application and is not a multi-client device, so probably the in-/out-settings are not correct.
    also the performance tool not passing tempo changes is a hint more than one dedicated midi signal is passed over to the performance tool inport or to nemesysport.
    having the performance tool in your chain, you should have midi out on the performance tool set to nemesysport and the respective inport in gigastudio set to none. performance tool midi in should use midi yoke out and overtures midi out to be routed to midi yoke. finally make sure, any midi in of overture does not listen to *wrong* or *all* midi ports available on the system (a loop my occure otherwise)
    christian

    and remember: only a CRAY can run an endless loop in just three seconds.
  • last edited
    last edited

    @cm said:

    finally make sure, any midi in of overture does not listen to *wrong* or *all* midi ports available on the system (a loop my occure otherwise)
    christian


    Thanks Christian. That did the trick. I limited the input ports in Overture to none and the output to only Midiyoke ports 1-4.

    Craig

  • duoartc, is this Overture program the current iteration of the program Opcode released about 10 years ago? The one written by Don Williams, who also wrote Encore - which is essentially the same program?