BrainModular

[large]Usine 5.50 poly + special launching price[/large]

Usine 5.50 poly include a new technology called poly.
All sub-patches can now be duplicated according a poly parameter.
For example, you can build a single sample player and decide to duplicate it 8 times to obtain 8 independents sample players with their own interface.

See this manual page for more info.

This version contains many improvements of the interface, the audio engine and new modules.

[large]Easine[/large]
We also present a new product called Easine, witch is a simplified version of Usine, especially designed for installations and netbook computers.
Easine is included in the Pro version package.
See this page for more info.

[large]improvements[/large]
- [patching] polyphony for sub-patches
- [module] new Draw Objects module more powerful and faster
- [module] mapper data up to 256 value
- [module] new X-1 module
- [module] new BLOC DURATION module
- [touch screen] contact surface informations now available in all interface modules
- [library] new grain engine FX
- [library] new Reverse FX
- [keylearn] allows now multiple keypressed at the same time
- [midi learn] soft take over implemented: option in the setup.
- [interface] trace OSC out messages
- [interface] new color selector window

[large]Save 30€ on the ultimate Usine version (Pro) for [s]120[/s]€ 90€
One year of free updates.[/large]



[large]fixed bugs[/large]
- all reported bugs fixed

hi olivier

thank s for all the work and time you(and the "boys") putting into usine!

i really like the easine fork...installations galore!!


thanks again and best wishes,
marco / iococoi

thank you!!!!

Awesome work Senso!!

the poly function sounds great !
Thanks a lot

I will try it as soon as possible. The Poly function, it is like a dream
Be sure i will use it.

thank you all what an incredible job !

[quote=""Senso""]Usine 5.50 poly + special launching price

Usine 5.50 poly include a new technology called poly.
All sub-patches can now be duplicated according a poly parameter.
For example, you can build a single sample player and decide to duplicate it 8 times to obtain 8 independents sample players with their own interface[/quote]
What in HOLY HELL!?!?
I JUST got done spec'ing that exact same feature as a VST-which-hosts-VSTs and utilizes my initial protocols to implement PolyTimbral and round-robin controller reassignment for PolyFlow multi-output routing automated switching for downstream fx parameter expression control (e.g. if you fiddle with a delay effect on the second note played in quick succession, the first note sounded's echoes will get twiddled, too - depending upon the buffer/interpolation alUsine 5.50 poly + special launching price

Usine 5.50 poly include a new technology called poly.
All sub-patches can now be duplicated according a poly parameter.
For example, you can build a single sample player and decide to duplicate it 8 times to obtain 8 independents sample players with their own interfacegorithm implementation specifics).

It's all been part of my ginormous project (and far too much to rant about atm as I'm trying to learn how to construct OWL Ontologies - don't ask) the PolyFlow idea was first sketched out a family of shells for various DSP classifications which could use such a feature but only last night did it occur to me (not being a developer) that if one makes a VST then it is the Host and you can use data pipelines to shuttle whatever protocol you want to and from an external (to the DAW hosting the VST-hosting-VST) hub applet and hijack DAW-to-VSTs MIDI (and transform it on the fly) and use an actually modern protocol to send hi-rez, scalable, control messages straight to VST automation, skipping straight past MIDI crap, and re-label VST short names, parameter value unit names and values and configure their control curves/hi + low value zones as a filter, etc.

You scare me. I would have been no more surprised if you'd showed up in my bedroom last night playing a Skid Row solo. I couldn't be happier. You've no idea how much time and effort you saved me trying to actually re-learn newer versions of Usine well enough to get these crazy diagrams I drew with a Livescribe pen to work the way I imagine they could work using native Usine models without driving my coder partner nuts with late night calls to demand he come over and learn the Usine SDK. If I had champagne I'd be toasting you and shouting out the window like it was 1999.

Submitted on rekkerd.

And yet on audiofanzine by nay-seven

Submitted also on CDM

is the name "polyphony" really adapted ? poly is ok, but the function doesn't seem to be only related to sound ? A bit confusing imo, or I miss something ?

yes you're right, I'd prefer the term "Poly" which is more general?

very cool update. the poly system is a great addition. keep up the good work.

Hello,

Very nice Update, the polyphony is in the blood of my patch (by definition...)

Thanks a lot for your work Olivier.

Best

Thanks!

great !!

youpi for the polyphony!

Brilliant!

Thank you so much!!!

Thomas

WOW! This is REALLY intriguing - looking forward to seeing the implications of this for midi sequencing!

Killzzzz

Great update! Thank:D