Vienna Symphonic Library Forum
Forum Statistics

194,737 users have contributed to 42,932 threads and 258,002 posts.

In the past 24 hours, we have 6 new thread(s), 17 new post(s) and 106 new user(s).

  • Performance Set / Note Duratioin

    I know this was discussed a while back but I'm not sure of the definitive answer. I've got the performance set and love the legato winds. I just wish that there was a way to sustain the last notes longer. I remember a mention of free updates. My question is, do I need to purchase the Cube and then use the sustains? It seems on the legato instruments the first note you play is pretty long, but if you then do a run and sustain the last, it runs out quickly. Any solution short of buying the Cube (which I plan to as soon as the $$ permits)?

    Thanks,
    Jeff

  • I wonder if there will be a way with Gigastudio 3.0 to create some sort of Multi-loop so that when the legato comes in to play it can go back from a loop to the wav with the same velocity of the first note which is long like you said. It seems like it's possible. Anyone have further comments on this? [:)]

  • The long starting note is normaly a simple sustain note.

    If you don't have the cube, you could use two miditracks, with the same legato instrument.

    So if you need a longer note at the end or during your phrase. You could switch this long note on the second miditack. For some instruments it could be helpful to leave a short starting snipped of these long note on your first legato miditack, so you get the real legato transition to the following sustain note.

    The overlap you need, simply depends, how fast the attack of the following starting note is.

    It also depends, if the instrument is solo or part or a big orchestration.

    best wishes
    Herb

  • I think (I read it in a PDF file) that Giga 3.0 will have a VSL Tool-like utility. I know it will have some cool (more RAM) tools/plugins but don't know which one.

  • Well at least it is interesting that you got some information on Giga 3.0!!! [:D]
    Them guys are not giving any piece of information to anyone...

    This behaviour of Tascam might be very confusing to a lot of people out there who would like to decide on VSL running with Giga. But Tascam - are they alive? No responses, no support for months...

    Even the RAM question would be very appreciated to be answered from them, since working with VSL is a joy in real time. By now you need at least 3 systems to get full advantage of the lib in real time! And who can afford three systems (save running) AND the library (although the prize for the lib is very ok!)

  • recently peter alexander summed up all infos about upcoming GS on the NS-site. the main point, at least for me, was: it will not go above 1.5GB, but the buffersize will decrease to 64 kB/stereo. this seems to be confirmed more or less by nemesys-developers.
    no groundbreaking, but even good news - this would give you the option to load 3 times the amount of samples as with 2.5 - not so bad

    i don't want to reiterate myself too often and everybody who guesses i'm wrong (and i would love to be) is invited to do his own research: there is no way to go beyond the 2GB-barrier for process-threads on 32-bit operating systems, be it win, mac, whatever.
    secondly, systems which can use more than 4GB are in the high-end-segment and priceless (usually in this case the OS comes with a special built and configured server-hardware)
    so _if_ nemesys tries and succeeds to build a version (after 3.0) which can be run in two independent instances this will give us 6 times the amount of ourdays, assume the buffer-size can be reduced again to 32 kB/stereo it will be 12 times.
    besides then you will have to be very carefull selecting your hardware (has to be a bunch of disks or a high-performance-raid) and reached *the end of the flagpole* for 32bit-systems

    but assuming moore's law *) is also valid for VSL, you will _need_ such improvements [;)]

    christian

    *) Gordon Moore, co-founder of Intel, postulated 1997 data density (on chips, and therefore processor-speed) will double approximately every 18 months, this is expected to hold for at least another two decades

    EDIT: i just realized, i took part on hijacking this thread - sorry donimon - next time i'll open a new one

    and remember: only a CRAY can run an endless loop in just three seconds.
  • donimon - Herb gave you the answer you needed as far as legato goes I think.

    cm - If we still would continue to hi-jack this thread... It is possible for an application running on standard XP (or win2k server, advanced server or datacenter) to use more than 2GB. There is a switch that you can add in the boot options for these that extends the memory scope for each process to 3GB! But, and there is a but...the application has to be compiled with the right switches in order to be aware of when it can make use of the extra memory. I don't know if there are coding differences if you want to take advantage of this, but it surely would be cool for a top-of-the-line sampler... [H]

    /Mattias

  • mattias - AFAIK it is possible to go up to ~2.7 GB in a single thread (but the adressing-schema has to be changed = needs to be already programmed within the application) - search eg. for the keywords *2gb, SQL, windows2000* in the MSDN
    thank you for testing and posting the reg-keys, they are obviously a great entry-point for refining the research on tweaking
    christian

    and remember: only a CRAY can run an endless loop in just three seconds.
  • I'm in fact at the stage of getting a brand new system configured for me. The suppliers of the PC insisted when I asked that 1.5GB RAM is a very costly option compared to 1GB. But should I be insisting on 1.5 on a new Gigastudio system (or even 2?)? In what way could it be prohibitive to have only 1?

    Thanks for your help!

    Simon

  • last edited
    last edited

    @Simon Fox said:

    I'm in fact at the stage of getting a brand new system configured for me. The suppliers of the PC insisted when I asked that 1.5GB RAM is a very costly option compared to 1GB. But should I be insisting on 1.5 on a new Gigastudio system (or even 2?)? In what way could it be prohibitive to have only 1?

    Thanks for your help!

    Simon


    Yes. I would find another vendor. The cost of 1.5 gb vs 1 gb of RAM is really not so costly, unless they were going to build your system with "small sticks" and therefore screw up your ability to add RAM cheaply.

    My advice is this: In about 20 years of using computers, I have never regretted buying RAM. You will always be happy you have it.