*sold*

[headquest]

... SLIGHTLY more complex (in terms of steps) in live5 ... select the plugin to replace ... hit 'delete' key ... drag a new plugin into its place from the browser menu ...

Hi Rob,

A quick tip - if its a synth you want to replace you don't need to do that in fact. You can simply drag the new synth straight from the browser and onto the track, at which point Live will delete the old synth and insert the new one in one single step. You can't get simpler than one single step

[hitman8081]

i myself just upgraded to orion platinum for a 100 bucks but i saved 50 so it was a good deal. i used to have constant crashes in orion but since changeing drivers, crashes have been minimal. the things i realy like about orion is how good it sounds, the wasp and the native fx are fabulous. almost hard to believe the quality of orions fx for being native fx i havent found one "filler" effect yet.

the pianroll is realy great, toxic is AWSOME, and the thing that i REALY LOVE about orion is how orion handles paterns. composition is very important in producing music that sounds profesional. orions got it right. when producing a good tune if you know what your doing you should have countless variations of melody lines, beats, pads, basses, fx ect.

it just doesnt cut it to play the same patern over and over at diffrent intervals. and thats why i love orion because it works the way ideas and compositions come together in songs. plus it has multiouts fl does not. yes orion crashes.
(sometimes alot) is buggy, and can be sloppy to use but its all about the finished product.

belive you me, if i had the cash i would buy ableton in a heartbeat but i dont so orion is "good enough" for my needs. i admit sometimes i say f**k it after orion crashes and install fl studio but every time i install fl studio, it sounds horrible and weak, makes it very hard to create paterns because patern compositon is linear in orion while paterns in orion are accesable in orion at all times, making ideas able to 'flow" naturaly and easily. orions a very good host to create a finished product but it suffers from bugs, stability, and composistional annoyances. orion needs to become stable, elimate the bugs and add a freeze function because face it sooner then later its going to become impossible to create a profesional tune in orion (and fruity) with out having to sacrifice quality and the finshed product

imo i feel its already like that but very soon if freeze is not implemented in eaither host, the songs that are produced in orion and fl studio are going to become extremely cpu based and will soound the part the more and more as time goes on.

[speccyteccy]

plus it has multiouts fl does not.

FL DOES have multi-outs both as a standalone host and as a plugin. Multi out instruments are also supported. Maybe you're talking about FL's lack of support for multi-out FX?

[Kriminal]

Matbe he means multi audio outs from soundcard???

[pHz]

... SLIGHTLY more complex (in terms of steps) in live5 ... select the plugin to replace ... hit 'delete' key ... drag a new plugin into its place from the browser menu ...

Hi Rob,
A quick tip - if its a synth you want to replace you don't need to do that in fact. You can simply drag the new synth straight from the browser and onto the track, at which point Live will delete the old synth and insert the new one in one single step. You can't get simpler than one single step

thanks for that ... i happily stand corrected ... id just never considered even trying it that way TBH and the manual remains on a dusty shelf somewhere in pristine condition ...

slainte rob

[Kriminal]

With regards to replacing a synth, i spoke ro Rich, he says its possible, so it may well make its way into next version. im waiting on a new beta today for some other new stuff and fixes.

Thanks for the info.

[hitman8081]

Matbe he means multi audio outs from soundcard???

multiouts for microtonic

[jens]

Tell me, cos im really interested, how do you do it in another host?

e.g. in eXT and Tracktion you right-click the vst/vsti and select 'replace' from the context-menu - why should it be more complicated (or at least if the programmer is neither a moron nor a sadist )?

[jens]

I was gonna say, what if you have lots of automation done in the song, most parameters will not match, how does it cope with that. I imagine that could cause a few probs...

well, in eXT you send CC-envelopes to a plugin and then map the CCs to the desired plugin-parameters. So if you change the vsti-later the envelope automatically gets rerouted to the new instrument and all you have to do is to re-map it (so it's just a few simple-clicks.

[Kriminal]

I was gonna say, what if you have lots of automation done in the song, most parameters will not match, how does it cope with that. I imagine that could cause a few probs...

well, in eXT you send CC-envelopes to a plugin and then map the CCs to the desired plugin-parameters. So if you change the vsti-later the envelope automatically gets rerouted to the new instrument and all you have to do is to re-map it (so it's just a few simple-clicks.

yeah, im sure its easy enough to copy/paste automation from one param to another, but i can also imagine it may cause mayhem, or at the very least one hell of a noise

[jens]

With regards to replacing a synth, i spoke ro Rich, he says its possible, so it may well make its way into next version. im waiting on a new beta today for some other new stuff and fixes.

Thanks for the info.

that's the right attitude from both of you!


(instead of saying 'where's the prob?')

[Kriminal]

Tell me, cos im really interested, how do you do it in another host?

e.g. in eXT and Tracktion you right-click the vst/vsti and select 'replace' from the context-menu -

i know, i was told many posts back, and its on its way.

Personally, i think if you have got as far as writing a whole song and adding FX and automation etc, and then you decide to change the synth, you need to check your head. You should know a lot earlier on if that sound fits or not.

[jens]

I was gonna say, what if you have lots of automation done in the song, most parameters will not match, how does it cope with that. I imagine that could cause a few probs...

well, in eXT you send CC-envelopes to a plugin and then map the CCs to the desired plugin-parameters. So if you change the vsti-later the envelope automatically gets rerouted to the new instrument and all you have to do is to re-map it (so it's just a few simple-clicks.

yeah, im sure its easy enough to copy/paste automation from one param to another, but i can also imagine it may cause mayhem, or at the very least one hell of a noise

nonono - unless the CCs are remapped the envelopes simply won't do anything - they are still there but aren't controlling any parameter.

[Kriminal]

With regards to replacing a synth, i spoke ro Rich, he says its possible, so it may well make its way into next version. im waiting on a new beta today for some other new stuff and fixes.

Thanks for the info.

that's the right attitude from both of you!


(instead of saying 'where's the prob?')

Well, its a good example of...'if you dont ask, you dont get' and someone actually took the time to explain it properly, and i thought it sounded quite cool, as does Rich, so it will prob happen.

Most ppl tend to say 'it cant do this or that' and leave it, they dont mail the dev or ask at the forum, in which case nothing gets sorted, which is a shame.

[Kriminal]

nonono - unless the CCs are remapped the envelopes simply won't do anything - they are still there but aren't controlling any parameter.

ah, i see