WNAMM12: Access Virus Ti OS 5 !!!!!!!!

  • too bad :( according to this news from http://www.sequencer.de/blog/?p=12345
    just Access Virus TI2, Polar 2Dark Star (built 2009/05) are supported for new features!!!


    If this is truly the case, this is the first time a software update has ever segregated the Ti lineup. In the past, all Virus Ti were able to accept the update and it was noted that Access had no plans to omit the older generation in favour of the newer one. We will see I guess.

  • ill the the filter parameters (labelled 1 & 2 IIRC) be accessible from the mod matrix?


    hopefully they will. pretty much all mod matrix destinations are used up right now and we need to make some space. throwing something out is not the big issue but predicting which people required legacy destinations in the past and want to use it in the future.
    marc


  • throwing something out is not the big issue but predicting what people required in the past and will use in the future.
    marc

    You could perhaps send all registered users a link to an automated survey form asking them which 3 or 4 destinations they think they would miss the least

  • Regarding the frequency shifter effects, all the destinations can be grouped as "frequency shifter effect destination" regardless of the specific effect: "frequency shifter effect - amount", "frequency shifter effect - shift" which can be used for cutoff requency, vowel index, etc. for every VC knob there. Regarding the filters, "realtime" access to each and every part of the envelope, especially attack and sustain is very helpful for me. For example, I already tend to randomize the envlope parts of the existing envelopes, to give the sound "human" feel.

  • Quote

    throwing something out is not the big issue but predicting which people required legacy destinations in the past and want to use it in the future



    If I had to do this I would write a small parser program which would extract which source, destination and combo' s are used inside one patch. Once that program is written, I would encapsulate that inside a bigger program which eats one midi file of patches and returns how many times which source, destination and their combo' s are used.


    After that, I would collect all patch banks which exist on the Access website, commercial banks, user banks, etc. ,categorize and analyse them using the above program.


    Finally, you obtain a lot of plain text files full of numbers on which several simple shell scripts are run which tell you, for example:


    -Which mod destinations are used most throughout the years and whether changes/trends occur after the introduction of new os versions.


    -Are some destinations used more in basses than in pads or other categories and is the category system used frequently int the first place? If so, what category of sounds is built most on the Virus?


    -Do people from Access music have habbits in using specific source/destination combo's and are these different from what commercial sounddesigners and/or artists outside Access use? Has this changed over the years?


    May other questions could be answered using the above approach and although this still makes it hard to predict what people will do in the future, it at least gives you some insight in what has been done in the past by various categories of users. Over 5000 patches is enough to justify a statistical approach.


    For writing a parser program, a functional language like Haskell and the parsec library could be used. For plotting statistics in graphs, perhaps good old gnuplot. All available fo free :)



    M.