8.03 is Bugging

[Todzilla]

Not only does it revert back to showing only mixer channels that correspond to tracks selected (a behavior they mercifully corrected in version 8, only to revert it back for this bug fix releases), but when I double click on an audio track in the tracks window, it takes me to a random spot in the track listing for editing soundbites. I have to vertically scroll to find the track I had double clicked on.

Can't wait for the bug fix release that fixes this bug fix release...

[Agent of Random]

Not only does it revert back to showing only mixer channels that correspond to tracks selected (a behavior they mercifully corrected in version 8, only to revert it back for this bug fix releases)

Not a bug...they changed it back because everyone on this forum complained about the new behavior.

[NazRat]

Not a bug...they changed it back because everyone on this forum complained about the new behavior.

Not everyone complained. I'd say it was about 50/50, but apparently one side of the 50/50 carried more weight.

[Todzilla]

Obviously, I'm biased, but I don't understand the value of limiting the mixer layout based on track selection.

And can I assume the arbitrary nature of soundbite zoom placement when double-clicking on a track area is a bug?

Otherwise, this software is so close to nirvana, it pains me to see any back sliding.

[David Polich]

Obviously, I'm biased, but I don't understand the value of limiting the mixer layout based on track selection.

And can I assume the arbitrary nature of soundbite zoom placement when double-clicking on a track area is a bug?

Otherwise, this software is so close to nirvana, it pains me to see any back sliding.

"Mixer layout follows track selection" should be really easy to understand.
Let's say you have a small (21") monitor, no second monitor. IN DP8.01, when
you selected some tracks, then pressed Shift+M, you'd get the entire mixer,both audio and MIDI tracks, all aux, and all master faders,
stretching all the way across your monitor and then out of view. I suppose
this is the equivalent of having your whole hardware mixer in front of you,
if you have a hardware mixer.

But let's say I just want to access the kick, snare, hat, and overheads
tracks, I don't want to look at anything else. Before 8.02, I'd select them
in the TO window, press Shift+M, and then - get the entire mixer, not just the selected tracks. Sorry, this just pissed me off, it's never what I wanted, it's completely inconvenient. I just want to look at the tracks I
selected. So do a lot of other people. I'm so glad MOTU fixed this back to the old way.

My answer to you is simple - if you want to look at all your tracks, then select all of them in the TO window and press Shift+M, and there they are.
I can't see why this is that difficult or problematic, seriously. Whereas,
the "new" way introduced in 8.0 is problematic.

Regarding soundbite placements - I never look at them, so I'm not the person
to comment on that.

[Gravity Jim]

Not a bug...they changed it back because everyone on this forum complained about the new behavior.

Not everyone complained. I'd say it was about 50/50, but apparently one side of the 50/50 carried more weight.

As shocking as it may seem, this forum is not the only source of user information MOTU has, and it is not even representative of their user base (no forum is, as all of them become dominated by the most tenacious personalities). MOTU must have heard a lot of requests for a return to the old behavior... as much as they've had on their plate the past year, do you really think they would have addressed it without an overwhelming number of requests?

[Phil O]

So seriously (no rants please), do you think I should hold off until 8.04 before I dive in?

Phil

[Timeline]

I'm waiting longer than that Phil. To many crashes and it seems you have to add quite a bit of ram to properly vet 64bit

[NazRat]

As shocking as it may seem, this forum is not the only source of user information MOTU has, and it is not even representative of their user base (no forum is, as all of them become dominated by the most tenacious personalities). MOTU must have heard a lot of requests for a return to the old behavior... as much as they've had on their plate the past year, do you really think they would have addressed it without an overwhelming number of requests?

There must have been some reason they changed the behavior with DP8 in the first place. You think it might have been from a more representative DP user base. It certainly wasn't any pressure from motunation that I can see. Yet, I am certainly shocked and stunned by all the changes.

[mikehalloran]

I'm waiting longer than that Phil. To many crashes and it seems you have to add quite a bit of ram to properly vet 64bit

I'd ignore that.

32bit limited you to 4G, no matter how much you really need. 64 bit allows you to use as much of the installed RAM as your plugins need.

I found that DP 8, in 64bit uses less RAM than 7.24 and is faster. I did not expect this and was pleasantly surprised. I was expecting to be looking for a new Mac about now.

Too many crashes? Says who? I have yet to experience one.

[Prime Mover]

Since DP8 was a nearly total re-write, there simply may have been some functions that didn't get completed in time. Having the mixing board respond to actions outside of itself requires extra coding. The behavior you describe is simply the result of no outside influence. Most likely, MOTU didn't choose to "do it differently", but it didn't get around to coding that feature in, and felt it was too minor an issue to hold up their release date.

By the way, you do realize you can turn it off?

32bit limited you to 4G, no matter how much you really need. 64 bit allows you to use as much of the installed RAM as your plugins need.

I'm not sure that's exactly true. I believe that DP8 was limited to 4GBs, and all of the plugins INDIVIDUALLY were limited to 4GBs, with the exception of Kontakt and similar VIs that had memory servers. I'm not completely certain of this, but I believe that plugins run in their own threads. They're subjected to maintaining the same bit rate as the host, but I believe they have their own memory management, and thus are allotted their own memory table with a 4GB limit.

I'm finding it VERY HARD to break the 32bit barrier (even though I'm completely 64bit now). In my mind, the big advantage to DP8 has actually been the Cocoa rewrite, not the 64bit barrier.[/quote]

Too many crashes? Says who? I have yet to experience one.

[Todzilla]

Obviously, I'm biased, but I don't understand the value of limiting the mixer layout based on track selection.

And can I assume the arbitrary nature of soundbite zoom placement when double-clicking on a track area is a bug?

Otherwise, this software is so close to nirvana, it pains me to see any back sliding.

"Mixer layout follows track selection" should be really easy to understand.
Let's say you have a small (21") monitor, no second monitor. IN DP8.01, when
you selected some tracks, then pressed Shift+M, you'd get the entire mixer,both audio and MIDI tracks, all aux, and all master faders,
stretching all the way across your monitor and then out of view.
Regarding soundbite placements - I never look at them, so I'm not the person
to comment on that.

Of course, I understand that. And when I remember to perform the extra select all command it gives me what I want. I saw the change in version 8.0 to default to the last mixer view and i really liked that. To see the behavior revert back bugs me. And as easily as fans of this behavior can chastise me for be too lazy to select all, I can chastise them for being too lazy to horizontally scroll to the tracks they want.

Eventually, this should be a toggleable preference.

The soundbite editing bug is just that, a bug. When you double click on a measure of audio in the tracks window, you should go to that specific soundbite, not some arbitrary area in the soundbites window.

[Kubi]

32bit limited you to 4G, no matter how much you really need. 64 bit allows you to use as much of the installed RAM as your plugins need.

I'm not sure that's exactly true. I believe that DP8 was limited to 4GBs, and all of the plugins INDIVIDUALLY were limited to 4GBs, with the exception of Kontakt and similar VIs that had memory servers. I'm not completely certain of this, but I believe that plugins run in their own threads. They're subjected to maintaining the same bit rate as the host, but I believe they have their own memory management, and thus are allotted their own memory table with a 4GB limit.

I'm finding it VERY HARD to break the 32bit barrier (even though I'm completely 64bit now). In my mind, the big advantage to DP8 has actually been the Cocoa rewrite, not the 64bit barrier.

Unfortunately, the 4G limit is indeed the limit for the total of DP plus all its plugins. The only plug-in I'm aware of that can break out of that 32bit jail cell is Kontakt, with its memory server, which is able to access RAM outside of the 4G all-in limit (and Kontakt memory server was always, uh, temperamental...) - or else one had to use VE Pro, basically hosting plug-ins in a totally separate app.

Definitely an issue I run into regularly with memory hogs like Omnisphere, or large sample setups.