Gigapulse or MIR???

[Rob Elliott]

Reading Tascam brochure that ALex provided a link on - why would I want anything else - particularily if it is built to work seemlessly within Giga 3.0??

When I read of the features and benefits of GP I just want to spontaneously combust with excitment!!! [[:|]] Will MIR be ready by GP's release?

Herb or others, can you share with us the advantages of MIR over GP - at least as you see it. Many thanks.

Rob

[KingIdiot]

nevermind... you did ask here [:)]

[Dietz]

In a nutshell: The difference will be the integration. GP will integrate with Giga3, MIR will integrate with the products of the VSL.

Hope this is what you were after ... :-]

/Dietz - Vienna Symphonic Library

[Peter Roos]

@Dietz said:

...
Hope this is what you were after ... :-]
/Dietz - Vienna Symphonic Library

Yeah: both [:D] (or: all)

[peter0302]

My big question/hope:

Will MIR replace Gigastudio???

[Peter Roos]

Probably not, although it will be able to make Italian Espresso [[:|]]

Mind you: MIR is a convolving DSP and GigaStudio is a sample playback engine, quite different household appliances, IMO [6]

[peter0302]

It could be part of a bigger Vienna VST though, right?

[evan evans]

MIR and GigaPulse are like components.
EXS and GigaStudio are like components.

But MIR and GigaStudio are apples and oranges and cannot be compared. One is a ambience technology and the other is a software synth. Peter0302, did you mean to say GigaPulse???

Evan Evans

[paynterr]

As someone considering (in fact nearly 99% sold on buying the pro edition), I am wondering how MIR is designed to fit into the audio chain.
I am planning on getting the giga version of VSL and converting it to Halion using the perfect giga->halion conversion that comes free with Halion. This will give me VSL in a VST environment under cubase SX.
I am interested in learning more about MIR (if any details have been announced).
When will it be released... how computationally intensive is it? will it plug in as a VST fx? Will multiple instances of it be required? Or is there a single instance per 'room' or 'stage' with multiple inputs from various instruments.
Any hints and tips appreciated.
Regards
Richard

[Dietz]

Our concept is that the MIR is kinda "glorified" mixing engine, with multiple input streams, taking care of positioning, room information, directivity, and sonical adaptions. All this will be unified under one intuitive graphical interface, which "knows" a lot about the VSL-instruments and -ensembles fed into it, without further user interaction. - Underneath, an "expert" layer will allow experienced and/or experimental users the access to more detailed sets of parameters, of course. - A single instance of this engine is what will be needed for the whole task.

The whole engine will be very demanding computation-wise, so no final decision has been made wether this will be a completely native or a DSP-based solution. Given these facts, I think it is quite obvious that we won't spread any rumours about its architecture before we know _exactly_ what it will look like. I hope that the fog clears soon, but don't expect a market-ready product before summer (2004, that is :-] ...)

Anyway - thanks for your interest.

/Dietz - Vienna Symphonic Library

[eclect]

Do you plan automation? Surround?

[Dietz]

Yes, of course.

/Dietz - Vienna Symphonic Library

[eclect]

Great! Thank you.