*sold*

[Kriminal]

Actually the lockup while editing a note was more or less my first experience too, after buying OP (because guys like BONES and others are very enthusiastic about it and the pattern-based paradigm fits my workflow). So far every session with OP I've had at least 1 crash. That means after 1 week of using it, I consider it another learning experience, but not a stable tool to create songs with.

Can you give step by step deatils of how this occurs, with sys spec too, and i will try to reproduce it, and also report it to the beta forum

cheers.

[Shane Sanders]

Not to mention that fact you still can't change your mind about what VST you want to use without copying and pasting your entire pattern set and then wasting time re-inputting the arrangement in song mode. Good Lord!!! What a joke.

Or selecting "Receive MIDI input from..." and choosing another instrument. Not to mention that "copying and pasting your entire pattern set" requires no more effort than copying a single pattern. I do it very frequently and don't find it in any way annoying or time-consuming. But we wouldn't want to cloud this discussion with facts, now would we?

Jeez.It's this kind of thing that makes me just shake my head in some kind of resignation at how you tirelessly defend this ill-conceived program. Because who in their right mind would want to leave a CPU-hogging instance of a synth and all the FX applied to it in a song merely to use it as the source of MIDI information which will be controlling another CPU-hogging instrument of some kind? They both (and all their child processes like FX) would still be eating up valuable space in the mixer (which spreads itself like cancer across your screen with multi-out plugins like Battery). Read what I wrote, because the point was that you simply can't replace one synth with another like you can in most other hosts. You have to copy all its patterns (yes I know that is one click), then you have to paste them into the new synth. THEN YOU HAVE TO go into your song arrangement and input all the duplicate patterns (A1-H8) for each pattern that you are trying to replace. You might even have to move the newly added synth 'lane' up in the list to get it visualy near what you are replacing since Orion only lets them be name nice descriptive things like B6 or whatever! Oh yes, Orion is all about the scrolling and screen noise with every instrument and effect taking up more space as you add them. One has to squint like an old grandma to even read that crap in a large song. LOL. THEN YOU HAVE TO delete the synth you don't want. THEN YOU HAVE TO go back to that God awful giant mixer and re-label the new synth so that you can make sense of it later on down the road. THEN YOU HAVE TO scroll back across a massive green tundra of channels that are an inch wide at some point to adjust the volume of the new synth... Unbelievable. I can't believe I ever got any work done in it.

[Shane Sanders]

Actually the lockup while editing a note was more or less my first experience too, after buying OP (because guys like BONES and others are very enthusiastic about it and the pattern-based paradigm fits my workflow). So far every session with OP I've had at least 1 crash. That means after 1 week of using it, I consider it another learning experience, but not a stable tool to create songs with.

Can you give step by step deatils of how this occurs, with sys spec too, and i will try to reproduce it, and also report it to the beta forum

cheers.

It mostly happens when CPU usage is at a decent level (at least 50%) and one is moving note lengths around as the playback head passes through something you are touching. It's completely unpredictable but it eventually happens. I don't think I've ever had an Orion session that didn't crash at least a few times due to this phenomenon.

[Kriminal]

Jeez.It's this kind of thing that makes me just shake my head in some kind of resignation at how you tirelessly defend this ill-conceived program. Because who in their right mind would want to leave a CPU-hogging instance of a synth and all the FX applied to it in a song merely to use it as the source of MIDI information which will be controlling another CPU-hogging instrument of some kind? They both (and all their child processes like FX) would still be eating up valuable space in the mixer (which spreads itself like cancer across your screen with multi-out plugins like Battery). Read what I wrote, because the point was that you simply can't replace one synth with another like you can in most other hosts. You have to copy all its patterns (yes I know that is one click), then you have to paste them into the new synth. THEN YOU HAVE TO go into your song arrangement and input all the duplicate patterns (A1-H8) for each pattern that you are trying to replace. You might even have to move the newly added synth 'lane' up in the list to get it visualy near what you are replacing since Orion only lets them be name nice descriptive things like B6 or whatever! Oh yes, Orion is all about the scrolling and screen noise with every instrument and effect taking up more space as you add them. One has to squint like an old grandma to even read that crap in a large song. LOL. THEN YOU HAVE TO delete the synth you don't want. THEN YOU HAVE TO go back to that God awful giant mixer and re-label the new synth so that you can make sense of it later on down the road. THEN YOU HAVE TO scroll back across a massive green tundra of channels that are an inch wide at some point to adjust the volume of the new synth... Unbelievable. I can't believe I ever got any work done in it.

It took you longer to type that than the actual process of doing what you described....

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

[Kriminal]

Actually the lockup while editing a note was more or less my first experience too, after buying OP (because guys like BONES and others are very enthusiastic about it and the pattern-based paradigm fits my workflow). So far every session with OP I've had at least 1 crash. That means after 1 week of using it, I consider it another learning experience, but not a stable tool to create songs with.

Can you give step by step deatils of how this occurs, with sys spec too, and i will try to reproduce it, and also report it to the beta forum

cheers.

It mostly happens when CPU usage is at a decent level (at least 50%) and one is moving note lengths around as the playback head passes through something you are touching. It's completely unpredictable but it eventually happens. I don't think I've ever had an Orion session that didn't crash at least a few times due to this phenomenon.

Ive tried this before, cos it was reported way back, and ive never been able to get Orion to crash by moving notes around. I tried transposing, moving back/forwrd, editing vel, and deleting adding, and it doesnt do anything here, never has.

Is there something im missing? (im not being a fanboy, im genuinely trying to help find the prob)

[Shane Sanders]

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

In FLS all you have to do is click on an icon, navigate to the plug-in you want (from the standard list within FLS), and then it loads it for you. Everything else from the previous plug-in such as note data stays the same. That's it. It's just a simple swap.

[Kriminal]

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

In FLS all you have to do is click on an icon, navigate to the plug-in you want (from the standard list within FLS), and then it loads it for you. Everything else from the previous plug-in such as note data stays the same. That's it. It's just a simple swap.

so all the notes are put into the synth, all the patterns are inserted in the playlist, and all FX are on the mixer strip or however it works? Is the old one deleted?

sounds interesting.

[Shane Sanders]

Actually the lockup while editing a note was more or less my first experience too, after buying OP (because guys like BONES and others are very enthusiastic about it and the pattern-based paradigm fits my workflow). So far every session with OP I've had at least 1 crash. That means after 1 week of using it, I consider it another learning experience, but not a stable tool to create songs with.

Can you give step by step deatils of how this occurs, with sys spec too, and i will try to reproduce it, and also report it to the beta forum

cheers.

It mostly happens when CPU usage is at a decent level (at least 50%) and one is moving note lengths around as the playback head passes through something you are touching. It's completely unpredictable but it eventually happens. I don't think I've ever had an Orion session that didn't crash at least a few times due to this phenomenon.

Ive tried this before, cos it was reported way back, and ive never been able to get Orion to crash by moving notes around. I tried transposing, moving back/forwrd, editing vel, and deleting adding, and it doesnt do anything here, never has.

Is there something im missing? (im not being a fanboy, im genuinely trying to help find the prob)

Cool, well I wasn't thinking you were acting like a fanboy.

It's easier to make Orion choke when you have a section of an arrangement isolated for looping in song mode, but it doesn't have to be that way for it to happen. Believe me, I wish it didn't. I quit using Orion about 1.5 years ago because of this problem, with about 30 completed songs that I've since left behind except for a few. I went through 4 different computers with totally different hardware in the time that I used Orion, and that problem was consistently there throughout the whole experience.

[Shane Sanders]

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

In FLS all you have to do is click on an icon, navigate to the plug-in you want (from the standard list within FLS), and then it loads it for you. Everything else from the previous plug-in such as note data stays the same. That's it. It's just a simple swap.

so all the notes are put into the synth, all the patterns are inserted in the playlist, and all FX are on the mixer strip or however it works? Is the old one deleted?

sounds interesting.

Yeah. It leaves all that stuff alone. It just swaps the synths. So if you had a complex array of FX applied to the synth you are deleting, all that remains in place for the next synth. You can even copy a mixer channel's settings and paste it onto another one or save them like presets. I have a bunch of drum and bass channels saved that I've perfected for various kits that I use. I never have to spend time setting up that stuff just to start composing. I just load my VST, then load its mixer settings like a preset. In this way I'm able to keep instruments that I've learned a lot about very consistent sounding from song to song (having tested and checked the results on various systems like my car stereo).

[Ian B]

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

In FLS all you have to do is click on an icon, navigate to the plug-in you want (from the standard list within FLS), and then it loads it for you. Everything else from the previous plug-in such as note data stays the same. That's it. It's just a simple swap.

so all the notes are put into the synth, all the patterns are inserted in the playlist, and all FX are on the mixer strip or however it works? Is the old one deleted?

sounds interesting.

Hi Krim,
The only thing that changes is the vsti itself, the 'old' vsti is simply replaced with the 'new' one, all the notes, etc, are left as is. As Shane say's, it's a simple click on a icon, that's it.

I stopped using Orion/OPlat because of the constant crashes, even with native Orion synths, any automation was a hit and miss affair, more often than not, Orion fell over. I hate to say this, but this stability issue was the only time I ever agreed with Tee Lang Sun about anything.

[Kriminal]

Yeah. It leaves all that stuff alone. It just swaps the synths. So if you had a complex array of FX applied to the synth you are deleting, all that remains in place for the next synth. You can even copy a mixer channel's settings and paste it onto another one or save them like presets. I have a bunch of drum and bass channels saved that I've perfected for various kits that I use. I never have to spend time setting up that stuff just to start composing. I just load my VST, then load its mixer settings like a preset. In this way I'm able to keep instruments that I've learned a lot about very consistent sounding from song to song (having tested and checked the results on various systems like my car stereo).

You can copy/paste mixer strip settings here, but not what FX are there (just on/off and amounts for Sends etc). Also, i managed to get Rich to impliment saving EQ settings on mixer strip, so you can save/load those, very handy. Think im the only one with that version tho at moment.

I'll have another go at your prob later and get back to you, and i may inform Rich of the 'replace synth' thing, sounds quite good.

cheers

[pHz]

same in T2 and eXT ... right-click the plugin you want to replace ... click 'replace' from the context menu ... select the new plugin and its done ...

... 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 ...

(in all 3 cases ONLY thing that changes is the plugin itself ... everything else in that track ... MIDI ... audio ... effects settings ... etc ... stays in place)

slainte rob

(edited for clarity)

[papawillow]

Making Waves you just browse select a new vst / patch and its done,, it will even map the automation ,, the mapping is different of course ,, but sometimes there's a sonic suprise.

[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...

[headquest]

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

In Ableton you would simply drag and drop the new synth onto the track and it would automatically replace the old one. All the automation for effects, etc, will remain.

Also you would copy (Ctr+drag) the MIDI clip onto a balnk bit of screen, at which point a channel for it with all the right configuations will be automatically created. Then simply drag and drop the new synth and effects you want. If any of the effects are the same, even the clip envelope automation will be copied over. Nice!

You could do that with a single clip/loop in Session View, or if you have already done a complete arrnagement you could do it in the Arrangement view for the whole track.