DP 7.2 is swell but

[mrbillet]

I heard this update contributed to the deaths of baby dolphins in the Gulf of Mexico. I hope they fix this for 7.5

[MIDI Life Crisis]

The dolphins were making my audio squeak. It's a feature that they are gone.

[FMiguelez]

He's not the only person who's said something ignorant in this forum. I've done it several times. Each time it's because I gambled and stated an opinion before really KNOWING what I was talking about. Almost every time I've done that in life I've regretted it, because there is ALWAYS someone reading your post who knows more about something than you do, and if you get it wrong you'll be called out on it. I've had it done to me. You'd think I'd learn by now.

You mean like me and my post in that LASS thread?

[James Steele]

Besides there is still no individual coloring of the soundbites which would make much more sense. Right-click menus? Matter of taste, keyboard shortcuts are still the fastest with or without them. Search? A welcome feature but it never was on my wish list. OSC? I don't have an iPhone or iPad and am not planning to. All I'm saying is that the update did not affect my workflow in any way that's why I call it cosmetic.

And if you were the sole user in the world, than it would make sense. But just because YOU won't use a new feature that a great many users WILL, doesn't mean that the work that went into those features DIDN'T HAPPEN! So call it cosmetic if you like, but objectively you'd be wrong. Whether you use it or not is not a litmus test for the existence of a feature.

"Individual coloring of soundbites?" How would that make much more sense? Much more sense than what? More sense than soundbite color being an indicator of which track you're working on? Reminds me of that joke: "What is an elephant? It's a mouse designed by committee." Hey... to each their own. By the way... that sounds like a "cosmetic" feature.

[michkhol]

FWIW... MOTU does not announce to the world when they have tinkered under the hood with the audio engine and much of the stuff that's "under the hood" and the sorts of things that need to be done to get DP ready to become. 64-bit app. I sometimes am told a few tidbits in confidence from MOTU people about the amount and scope of work that is going on. I'm not at liberty to say much without betraying their trust-- which is something I could never do. But what I will say is that there is FAR more going on than meets the eye, and to look at DP 7.2 and see just "themes" is like looking at an iceberg from the surface.

As a professional programmer I realize exactly how much work should be done on that path, I also realize that the resources to do that will always be limited. For instance for 64 bit GUI you need excellent Objective-C programmers and you have to pay them extremely well, otherwise Apple or Adobe will snatch them. I also do know that themes implementation take a great deal of work especially if it was not designed for that from the very beginning. I think the work started from version 6 after the big outcry about the GUI. Themes (or skins) are not anything new these days, the fact that there is still no MOTU-made public skin editor proves that it was indeed an afterthought. In programming world afterthoughts are resource hogs and I only wish more work were done under the hood instead.

[michkhol]

And if you were the sole user in the world, than it would make sense. But just because YOU won't use a new feature that a great many users WILL, doesn't mean that the work that went into those features DIDN'T HAPPEN!

Please point me to where I said that. As far as I remember I was telling quite the opposite, to put it mildly.

"Individual coloring of soundbites?" How would that make much more sense? Much more sense than what? More sense than soundbite color being an indicator of which track you're working on? Reminds me of that joke: "What is an elephant? It's a mouse designed by committee." Hey... to each their own. By the way... that sounds like a "cosmetic" feature.

I will not argue on that, you will not hear it anyway. "To each their own"

[shaman]

"Individual coloring of soundbites?" How would that make much more sense? Much more sense than what? More sense than soundbite color being an indicator of which track you're working on? Reminds me of that joke: "What is an elephant? It's a mouse designed by committee." Hey... to each their own. By the way... that sounds like a "cosmetic" feature.

I work in audio postproduction and sound design. Mostly I use Protools, and I use individual region color feature to quickly find sounds related to an specific action. For example in an ambient track, a dark color for a deeper ambient and a soft color for a light ambient. Some times I need to have differents kind of sound in a same track, and is easier to see colors than reading region names.
This is an example of my workflow, when you use a DAW, you use its tools and the workflow that the DAW offers to you.
Please, note that I am NOT doing any criticism to DP, so don't throw me any stone.

[MIDI Life Crisis]

As a professional programmer...

Say no more, that splains' it (the crits, that is).

Many professionals tend to be somewhat more critical of the work in their field than the people who are simply users or observers as they [the pros] generally observe from a much more critical perspective. This is not an insult nor a bad thing, but you see it all the time.

FIlm reviewers, music critics, sportscasters, news people, politicians, tupperware salesmen, guitarists, auto mechanics, academics, astronomers: you name the profession and you will find that many of "those in the know" will have a somewhat "less forgiving" view of a particular product or performance.

For that reason, it can be hard to see the forest for the trees. What you see as programming and business practice irregularities (I'm assuming those descriptions as I am ignorant of both) we end users see and experience something quite different. Even from user to user (obviously) the experience is vastly different.

We can never climb into another persons head and truly get their perspective, but we can deduce something of their perspectives based on the intensity of their involvement in a particular field.

[goner]

Themes (or skins) are not anything new these days, the fact that there is still no MOTU-made public skin editor proves that it was indeed an afterthought. In programming world afterthoughts are resource hogs and I only wish more work were done under the hood instead.

Aren't most X.x software updates afterthoughts?

[James Steele]

FWIW... MOTU does not announce to the world when they have tinkered under the hood with the audio engine and much of the stuff that's "under the hood" and the sorts of things that need to be done to get DP ready to become. 64-bit app. I sometimes am told a few tidbits in confidence from MOTU people about the amount and scope of work that is going on. I'm not at liberty to say much without betraying their trust-- which is something I could never do. But what I will say is that there is FAR more going on than meets the eye, and to look at DP 7.2 and see just "themes" is like looking at an iceberg from the surface.

As a professional programmer I realize exactly how much work should be done on that path, I also realize that the resources to do that will always be limited. For instance for 64 bit GUI you need excellent Objective-C programmers and you have to pay them extremely well, otherwise Apple or Adobe will snatch them. I also do know that themes implementation take a great deal of work especially if it was not designed for that from the very beginning. I think the work started from version 6 after the big outcry about the GUI. Themes (or skins) are not anything new these days, the fact that there is still no MOTU-made public skin editor proves that it was indeed an afterthought. In programming world afterthoughts are resource hogs and I only wish more work were done under the hood instead.

You can throw down the "as a professional programmer" card all you wish, but you have absolutely no way of knowing how much work is being done under the hood. None whatsoever. But what is certainly convenient in these debates is that people who DO know, are legally enjoined from laying it out for you in public for you to prove that you're flat out mistaken. The trump card to your "as a professional programmer" speculation can't be played when the only people who DO know what they're talking about can't say a word in a forum without serious consequences for themselves.

[James Steele]

"Individual coloring of soundbites?" How would that make much more sense? Much more sense than what? More sense than soundbite color being an indicator of which track you're working on? Reminds me of that joke: "What is an elephant? It's a mouse designed by committee." Hey... to each their own. By the way... that sounds like a "cosmetic" feature.

I work in audio postproduction and sound design. Mostly I use Protools, and I use individual region color feature to quickly find sounds related to an specific action. For example in an ambient track, a dark color for a deeper ambient and a soft color for a light ambient. Some times I need to have differents kind of sound in a same track, and is easier to see colors than reading region names.
This is an example of my workflow, when you use a DAW, you use its tools and the workflow that the DAW offers to you.
Please, note that I am NOT doing any criticism to DP, so don't throw me any stone.

"Regions." Is this different than soundbites? I've suggested directly to MOTU color coding time ranges in the TO.