Samplitude 8 or Cubase SX3? Your opinions please...

[jens]

As far as this object oriented fight talk here. Yes, fully object oriented editing is damn convenient, but it also clutters up the editing process to extremes. Suddenly you have a new and variable set of parameters for every single object. This kind of flexibility gets in the way of workflow and speed.

It does not in any way get in the way. The object editor is hidden until you show it. So if you don't want to work with a segment as an object just don't, it works track based. If you do it's only a click away

exactly - sorry, Kingston, but your statement disqualifies you regarding competence

Try the Samplitude or the Tracktion demo (or both) and see for yourself what we're talking about...

[Kingston]

exactly - sorry, Kingston, but your statement disqualifies you regarding competence

Try the Samplitude or the Tracktion demo (or both) and see for yourself what we're talking about...

I've seen Samplitude in semi heavy usage, and a less of traktion (which I know is far simpler and easier) so I somewhat know what I'm talking about.

Roughly saying samplitude is extremely well suited for everything postproduction, it's heavy, flexible, powerful, but cluttered. For streamlined and intuitive music production look elsewhere.

Regarding competence I fear I never had any. My whole essence disqualifies me from anything of that sort.

[jens]

Regarding competence I fear I never had any. My whole essence disqualifies me from anything of that sort.

I wouldn't have mentioned it if above statetement of yours wasn't utter nonsense regarding other topics - it's quite the opposite usually, quite the opposite

[Kingston]

And I still stand by my statements.

As always, they are of the 'IMO' sort.

[Forever Sun]

There is one old niggle I have with cubase/nuendo and it's that effects are ALWAYS ON and consume CPU even if you are not playing anything.

Yes it is absolutely terrible lapse of reason not to implement dynamic plugin/CPU allocation. It makes a 3.8ghz seem a lot less than it actually is. Not just that but everything stays on even if you stop playback! For example, once I turned on a lot of effects for a final song render, took me two minutes to get to the export screen because everything had slowed down to crawl!! GODDAMN!


As far as this object oriented fight talk here. Yes, fully object oriented editing is damn convenient, but it also clutters up the editing process to extremes. Suddenly you have a new and variable set of parameters for every single object. This kind of flexibility gets in the way of workflow and speed.

And the FX in every Object in Samplitude are dynamically allocated. They consume CPU when the object plays only. Is this what you mean ? If this is so, you contradict yourself with those two paragraphs above.

The "variable set of parameters" isn't a problem. You set what you have to set in the object editor and leave it, out of view, out of your CPU usage.

[jens]

not sure if you really understood my post... - oh well it's probably my bad english -

I think usually you are very competent and you know what you are talking about...

about this special case: there's no need to discuss it any further as your 'argument' is simply non-existent...

(in reply to Kingston)

[Kingston]

And the FX in every Object in Samplitude are dynamically allocated. They consume CPU when the object plays only. Is this what you mean ? If this is so, you contradict yourself with those two paragraphs above.

No no no, sorry for the misunderstanding, my two paragraps weren't related. I was merely whining about the way cubase SX does it.

(as an ex logic user)

[Kingston]

not sure if you really understood my post... - oh well it's probably my bad english -

I think usually you are very competent and you know what you are talking about...

about this special case: there's no need to discuss it any further as your 'argument' is simply non-existent...

(in reply to Kingston)

no I did understand it quite perfectly. You're saying the object oriented model in samplitude doesn't complicate things. I think it does, it's another layer of complexity (or flexibility at best), even if the choice is down to user somewhat. I'm sorry but with samplitude UI the argument exists, it's far from the ideal you make it sound like.

I must've missed the talk about traktion earlier in the thread so my comments were only about samplitude.

[jens]

it doesn't matter actually but I haven't been speaking about Samplitude...

my post was just in reply to this 'competence'-thing...


oh and it's 'Tracktion'

[Kingston]

nevermind the competence bit. I was still explaining my original point about the complexity/flexibility issue, which you dismissed as non-existent.

[jens]

just one more hint about Samplitude:

part of the object-orientation paradigm is that children have always the properties of their parents until you change them.

[Forever Sun]

And the FX in every Object in Samplitude are dynamically allocated. They consume CPU when the object plays only. Is this what you mean ? If this is so, you contradict yourself with those two paragraphs above.

No no no, sorry for the misunderstanding, my two paragraps weren't related. I was merely whining about the way cubase SX does it.

(as an ex logic user)

And that's exactly the point. Since this particular feature you moan about in Cubase, is handled better in Samplitude through the Object Editing implementation. You've criticised the Object Editor and yet it seems it has the implementation you are looking for in Cubase. Hence you contradict yourself. No ?
Pulg-ins in Object editor consume CPU when the object plays only.

[ericj23]

And ericj23 if you can't see the obvious difference between what we are saying about objects then please stick to SX. Samp deserves better

frankly suck my cock - and you won't get paid bitch- thats just cheap - like you

i understand perfectly samplitudes editing - it is better than cubase - my point has always been that it isnt so much better to justify the cost of changing

ultimately if you want to start a pissing up the wall contest I can start talking midi - it may be improved in samplitude but it still aint anywhere near cubase goodor how about the intgration of external kit or play order tracks - or acid and rex implementation etc

im still sticking to my point - why bother changing ?
if it was free i could see that the stress of learning how a new program might work out
But samplitude has absolutely nothing in it that will make your music so much better - it just gives a slightly different way of getting there so why bother ?

If the guy is really set he can try the demo - i'm sure he already has

PS if you are trying to get a point across I wouldnt quote kylie minogue OK - a fondness for sex dwarfs isnt big or clever - and it is useful to imply the latter during any discourse

[Kingston]

This particular feature you moan about in Cubase, is handled better in Samplitude through the Object Editing implementation.

Yes indeed. But it's a feature that could be implemented to SX as well, invisibly to the user. I'm certainly not going to switch hosts just the get this functionality.

Samplitude has absolutely nothing in it that will make your music so much better - it just gives a slightly different way of getting there so why bother ?

This is sort of what I was going for as well.

[John_P]

Thanks for the feedback so far guys.

Looks like there's a lot of happy Samplitude users about.

I wonder why people curse Cubase so much, I mean it did do well in the KVR survey. I didn't notice Samplitude in any of the top 10, which is a mystery seeing as so many people worship it.

I am currently having a good look at the demo version of Samplitude 8. I will report back with my views.

In the meantime, please keep your opinions coming!

thanks again people!

John