Track comments not appearing in Track Inspector...

[FMiguelez]

Hello.

In DP8.06, I just noticed that whatever comments I see in the tracks in the TO, do not appear in the comments field of the Track Inspector.

Shouldn't they be equivalent and the Track Inspector mirror whatever there is in the tracks?

Also, typing comments in the TI will not update the comments in the TO. I wonder why this is?

Thanks!

[FMiguelez]

Can anyone please confirm this?

[bayswater]

Not entirely confirmed. Works for me. But I had to reselect the track to get it to show up, and click in the comments box.

[FMiguelez]

Thank you.

I will do as you say tomorrow to see if it works like that.

But even then, I think this is some kind of bug, because reselecting and clicking on the comments field should not be necessary, otherwise it defeats its purpose.

Just like the Channel Strip updates on its own to reflect the currently selected track, the Track Inspector should behave the same way, correct?

Little but annoying bug.

[bayswater]

Just like the Channel Strip updates on its own to reflect the currently selected track, the Track Inspector should behave the same way, correct?

Correct. It is not working properly.

[Shooshie]

Yeah, that's another one that needs fixing.

Folks, it's sort of our obligation here to send these in to MOTU. I knew this was going to happen when they finally went 100% Cocoa, for that required rewriting a lot of code. Such rewrites invariably mean that little loose ends like this get missed. When anything fails to function as it used to, don't assume that MOTU made that a decision. Assume that it was a back-door patch in the old code that got missed in the new code. That's how this stuff works.

On the bright side, Cocoa environments are much easier to fix and to expand on than the old code. It tends to be more modular, and overall much more accessible. Old coders would argue with that, because they were comfortable in the old coding environments, but I think most people agree that changes in the new code are easier in the long run.

So, when you find something, post it here, get confirmation, then report to MOTU. And if everyone who reads it and confirms it on their own will also report to MOTU, we'll get more attention and possibly faster fixes.

Shooshie

[FMiguelez]

Point well taken.

What's the best way to make MOTU aware of these things? Their regular tech support tickets?

I've been adding to a text file all the anomalies and little bugs I've discovered as I discover them.
So far they are 3 or 4 little things, but I'll be glad when they fix them. I'll post them in MOTUNation and I'll contact MOTU about them.

[Shooshie]

Point well taken.

What's the best way to make MOTU aware of these things? Their regular tech support tickets?

I've been adding to a text file all the anomalies and little bugs I've discovered as I discover them.
So far they are 3 or 4 little things, but I'll be glad when they fix them. I'll post them in MOTUNation and I'll contact MOTU about them.

I used to make a list, explain each one as precisely as I could explain it so that they will be able to duplicate it without fail, then I'd send it to MOTU in a single (big) letter in the US Mail. I've made a large number of reports via the tech support tickets, and sometimes those get a response. Other times they never seem to get opened.

To be sure that I've done the best I can, I'll do the tech support ticket, then call them up. I haven't sent them a snail-mail letter in a long time, but I'm always thinking about starting that again. Might get more attention that way. I don't know.

Shoosh