KVR Audio

Kalamata Kid · Post by **Kalamata Kid** » Mon Jul 21, 2014 7:11 am

Hello,

Object Versus Track Oriented. Did I get this right? Or is it Object VS something else?
The Samplitude people say their DAW is Object Oriented. Is this so?
What is the opposite of Object Oriented. Are there several opposites?

Is Object VS Track Oriented a matter of work flow or something more basic or fundamental to functionality in DAW’s? Please help me understand the difference. This may make it easier to pick the DAW to use.

Are the following Object Oriented? If not what are they?
Logic I believe also claims to be Object Oriented?
Cubase
Live
Studio One
Sonar
Pro Tools
Reaper
Mu-Lab
BitWig
Bidule

deastman · Post by **deastman** » Mon Jul 21, 2014 7:23 am

I'd say it's a fairly meaningless term. All these programs deal in objects of one sort or another. And almost all DAWs are timeline-centric, with the exception of Ableton and similar programs with an emphasis on clip launching. I don't use Samplitude, so I can't speak to that one specifically.

SalemBeatsKVR · Post by **SalemBeatsKVR** » Thu Jul 24, 2014 3:59 pm

"Object-oriented" is usually a computer programming term.

I'm not exactly sure whether that's how the Samplitude devs meant it, though (You normally wouldn't bother an end user with computer programming details aside from saying "It's faster because [ABC...]" or "We can put updates out quicker because [XYZ...]").

They might have meant "item-based", but as deastman mentioned, most DAWs use some sort of item-based paradigm.

-Ki
Salem Beats

No_Use · Post by **No_Use** » Thu Jul 24, 2014 4:07 pm

Object oriented in the sense here means being able to do stuff directly on...uhm...the object.

What some DAWs call clips, items etc.

Sam's object editor

I think most DAWs nowadays have some kind of object oriented edit functions.
What's pretty unique in Sam is is the object based aux sends.

Kalamata Kid · Post by **Kalamata Kid** » Thu Jul 24, 2014 5:10 pm

I googled this (Should have done his before starting this thread, sorry)
https://www.google.com/?gws_rd=ssl#q=%2 ... afe=active
it seems many people use the term “object oriented” when it comes to DAW’s.

I believe I am beginning to understand the meaning of this term. Let’s say you want to edit something on the track. If the DAW is object oriented I will be able to edit directly on the track. The alternative is that to edit the track another window opens where I perform the edit. Is his accurate?

Hink · Post by **Hink** » Sat Jul 26, 2014 7:37 pm

Kalamata Kid wrote:Hello,

Object Versus Track Oriented. Did I get this right? Or is it Object VS something else?
The Samplitude people say their DAW is Object Oriented. Is this so?
What is the opposite of Object Oriented. Are there several opposites?

Is Object VS Track Oriented a matter of work flow or something more basic or fundamental to functionality in DAW’s? Please help me understand the difference. This may make it easier to pick the DAW to use.

Are the following Object Oriented? If not what are they?
Logic I believe also claims to be Object Oriented?
Cubase
Live
Studio One
Sonar
Pro Tools
Reaper
Mu-Lab
BitWig
Bidule

I suggest you look at some of Kraznet's videos, the link is to youtube vids about objects in Samplitude. I agree that I think most DAWs have something similar in workflow but samp takes it a lot further. In fact the Object Editor makes an incredible channel strip and some users actually use object editors to mix. Not just aux sends, you can freeze an object, you can automate within a object, you have elastic audio, fx, crossfade editor, eq's, it really is a beast.

Note that Samplitude's freeze is also a fantastic bounce to track, or with the OE a bounce to object.

ezelkow1 · Post by **ezelkow1** » Sat Jul 26, 2014 8:25 pm

not being proficient in every daw out there I do wonder if one has implemented an actual parallel to object oriented design where you can define an element and then have other parts of the track be instances of that object while inheriting global properties of it. I.e. you could define say 'synth' which has the properties of scale and note constraints, velocities, swing/groove, maybe some effects. Then you could generate various instances of it that would all have the same global properties but then you change the individual sounds, add other effects, etc. The most basic version of this is already implemented in some hosts like studio one where you can do a 'shared duplicate' so you can duplicate a clip but they all share the same notes, so when you modify one they all change

To some extent this is basically just a duplication of another track, however say you modify the scale of the parent object then all children's scales would change to match, etc. Maybe something like that could useful

OO doesnt really translate well into a musical paradigm since really every track/item/etc is meant to be an individual and not many really inherit things across each besides note parameters. Unless your doing some gigantic project with hundreds of tracks all inheriting properties of each other it wouldnt seem that useful. Maybe someone smarter than me could come up with useful scenarios

Kalamata Kid · Post by **Kalamata Kid** » Sat Jul 26, 2014 11:18 pm

It seems to me the Object is the same as Clip or Event
the terminology used by other DAW's. Is this correct?

I checked Hinks's suggestion above to check out

Which I did at least about half of it. It seems that the
object in Samplitude is full featured.

Hink · Post by **Hink** » Sun Jul 27, 2014 4:22 am

it's like clips as far as how they are in tracks but as you have discovered it's a bit deeper than most

Winstontaneous · Post by **Winstontaneous** » Sun Jul 27, 2014 7:51 pm

Kalamata Kid wrote:It seems to me the Object is the same as Clip or Event
the terminology used by other DAW's. Is this correct?

I checked Hinks's suggestion above to check out

Which I did at least about half of it. It seems that the
object in Samplitude is full featured.

Yes, it's similar to what other hosts call clips, events, or items but Magix' implementation is the most comprehensive I've seen in the audio world. It lets you define any item or combination of items as an Object, and use the persistent Object Editor to manipulate them. Also I think Object effects are only active while an Object is being played, which saves on CPU.

Most DAW "Item" editors I've seen (like Reaper's) are much less full-featured, and while all the video programs I've used (Sony Vegas, Apple Final Cut, Adobe Premiere) have some sort of item editor usable for audio, they don't let you arbitrarily group multiple items into new objects without defining as a new clip.

bermudagold · Post by **bermudagold** » Sun Jul 27, 2014 8:39 pm

I think there are two separate points being convoluted here.

The first is the ability to "objectify" an element of the arrangement, so that it can be manipulated independent of connected elements within the bounds of its own container. I think virtually all modern DAWs have this in some form of "clip" creation.

The second, which is the far more impactful idea, more related to the term "object oriented", is the idea of "objectifying" something to create persistence and inheritance. If I create a clip as an object and assign certain information and behavior to that object. Then anywhere else in my arrangement I can create a new clip based on that clip and have it "inherit" some or all of that clips information and behavior. Also, if I insert instances of that clip ("object") all throughout different areas of my arrangement,....when I make a change to that clip ("object"), those changes "persist" through every other instance of that clip in the arrangement. So all the other clips that are copies of that clip (instances of that object), or built off that clip, are automatically changed as well. This can have clear advantages in speed of workflow when it comes to editing. I believe Tracktion and Samplitude have different implementations of this second type. I dont know if they are the only ones.

Object VS Track Oriented VS ????