No announcement yet.

Midi manipulation input+reaction output

  • Filter
  • Time
  • Show
Clear All
new posts

  • Midi manipulation input+reaction output

    Talked that with goebish soon ago and he had quite a positive sight of the idea. I'd like this thread to be used to discuss the comfort and conveniance that a midi input port + reaction midi output would be best alike before anything has beggun.
    An asio accelerator could be used too i guess, but i just had the idea. Asio deffenately accelerates visual reaction over accelerating audio.
    Some ressources: VST plugin dev kit (might countain some useful informations)
    Somehow, AVS could even become a VST plugin to have an easier linkage between itself and midi controls. Tne SDK is suppaused to explain midi how-to too.

    Flstudio and some other digital audio workstations has the ability to transmit midi signals to other applications or midi hardwares. Inside FLstudio, you can create dashboards with emulated midi hardwares, you can use the peak controller to create a midi signal from the input's velocity, or the formula controller to create advanced LFOs from math operators.
    These signals could be transmitted to AVS inside winamp via REWIRE... I'm much thrusting the idea to use rewire but i'unsure if they share the sdk fully... still here is their link
    Using any midi input inside AVS would allow to have at least 128 controllers assigned to sliders or to variables. Inside something like dynamic distance modifier, one could call CC12 to replace X and change the movement from a LFO or from a hardware midi controller engine live. The steinberg SDK includes the asio sdk. Creating an asio input implies the ability to use a soundcard's own asio drivers, asio4all, or steinberg's asio. Using asio drivers may allow the use of a DSP acceleration card too.
    Such cards precompute the audio process before submitting it to the processor allowing a smoother creative session. And it probably could accelerate AVS's graphics if it would use ASIO.
    The reaction midi output is to send back the resulting values to the DAW (digital audio workstation) so that it can alter the music from the images resulting from the AVS programmable codes. Say we'd get something X=sin(x/cc12); we could anyhow insert something ______;outCC12; so that the DAW would recieve the new value resulting from the rest of the chew session. Using those controlls will allow hand-manipulated rotations, x-y controlls from mouse, color switching at a chosen time, will also allow to save the DAW's n and the AVS preset's configuratio into sister projects and recall the common project later.
    Having AVS as a VSTeffect plugin would allow the presets to be saved with the DAW's project files and the linkages to be kept into one single file. There are a few branches of a plan that could be chosen to use. The branches chosen have to be chosen concidering realisability, ease, and investments.
    This link is the FLstudio SDK Must be a registered user to download it. You may buy FlStudio using this link The basic version is about 50$ and allow a forum registeration. The full version is about 150$ and contains most great functions and plugins except the hq plugins that can also be bought from that link. Developping AVS strictly for FlStudio would be the best as it can later be turned VST and that FL has some very innovative ways of controlling and using plugins. Plus, the FL team will make a pleasure to distribute AVS with FL if it is made stable and very compatible! FL has its own Asio input, like most DAW so that would prevent coding an asio input directly inside AVS, or if avs is to be still used inside winamp. So lets see what branches are the most worthy right here!!!

    So that's the base of imformations i may share currently.

    Post your ideas about comfortability and workflow below!!

    So done, we all will have a clear sight over the most clever development plan and will get more interrested developpers, that way done, get a new AVS with those abilities sooner!!