MOTUnation.com

When opening a DP main eq one used to be able to adjust level trip pots while hearing changes. Now, turning trim pot shows nothing until mouse is unclicked, then, level and changes are shown. This is on the DP eq, not Masterworks.

Also, when opening Masterworks limiter, depending on complexity of mix, portions of eq graphic are blanked out grey and unattainable.

Not sure if this stuff is only on my system or what.

Please add any comments and other similar issues to this post.


Thanks

Hey T:

Good idea for a thread. I'm still sorting through a few issues but I'm trying to determine which of these might be unique to 5.12 and 10.4.10 before listing them.

Frodo wrote:Hey T:

Good idea for a thread. I'm still sorting through a few issues but I'm trying to determine which of these might be unique to 5.12 and 10.4.10 before listing them.

Kewell. It could be meaningful for sure.

As a point of comparison, in case it is helpful to any MOTU staff reading this report on anomalies, this is exactly the problem that I have with Novation BassStation and V-Station (native vs. Powercore). As I bought/installed AFTER the DP 5.12 and OS 10.4.9 updates, I cannot know if these are problematic plug-ins or if there are some issues with particularly CPU-hungry plug-ins, as Altiverb would sometimes exhibit similar behaviour if I was pushing the limit.

MasterWorks EQ isn't a CPU hog, so I am surprised, but maybe if you have a whole bunch of open plugs on unfrozen tracks...? Have you checked your CPU meters when this problem occurs just to see? I would guess that graphics repaints are not the highest priority, when the CPU is being slammed, but this could also be affected by your work priority setting under the audio configuration dialog?

Just some guesses. I'm not sure if I've opened up MasterWorks EQ on any sessions that I did on Sunday (I upgraded to 10.4.10 Saturday and worked too late to do any tracking last night once home). I'll make it a point to open up an MW EQ plug tonight to see if I observe similar behaviour.

My issues were not with the MW eq but the limiter. The EQ was the MOTU eq that changed its work philosophy.

Hey Gary--

Not to go OT, but your sig appears in some of your posts but not in others.... odd... I was curious as to whether you had an Intel or PPC (and I see you are on a PPC).

I would otherwise check on my G5 for quirks for you except that it's still running 10.4.8 and DP 5.11. Honestly, I've grown quite paranoid about the alleged *new and improved* OS and app updates.

There is one graphical pain that crops up once in a while where a MIDI note that was recording doesn't appear in any of the Edit windows, but this was something that dates back to DP 2.7.

As for work quanta, etc., I've seen more obvious deterioration to graphical behavior than I have with sonic or CPU improvements.

However, one of the most significant improvements I made to my G5 was to dump the stock graphics card. It was replaced with a Radeon X800XT workhorse and made a huge difference.

All that aside, it seems very strange that the low-profile DP EQ would give you problems. Have you considered doing a disc repair or even reinstalling fresh copies of *just* your MAS plugins?

Have not done any of that but i did put in a new graphics card for my 30" display in the last few months. The eq issue can't be graphics related though as far as I know. Maybe I just need to wind down the PPC and think new but I have so many PPC slot cards like scsi, UAD and such i can't tear myself away for the funds required.

I always post my spects on the first post of a thread BTW.

Thanks bud.

One issue that I am seeing sporadically is the "disappearing DP". It kind of just vanishes, like Gandalf at an orc-party.

The only thing that I can vaguely point to is "busy" projects, ones with lots of little files. Not many VIs though, or at least they are disabled. I *think* that I can make it better by deleting tracks, compacting the project, removing the undo history. But nothing really specific that I can name.

I have all the latest X4X 1.1 updates installed, permissions repaired, and so forth.

Other than this "minor" issue it has been pretty stable for me.

Timeline wrote:Also, when opening Masterworks limiter, depending on complexity of mix, portions of eq graphic are blanked out grey and unattainable.

I get the grey screen thing with the MasterWorks Limiter thing. Although as soon as I change a parameter it magically appears.

Mr_Clifford wrote:

Timeline wrote:Also, when opening Masterworks limiter, depending on complexity of mix, portions of eq graphic are blanked out grey and unattainable.

I get the grey screen thing with the MasterWorks Limiter thing. Although as soon as I change a parameter it magically appears.

Yes buffers can help that but it's the VI load that really sets grey outs in motion.

I start all my tracks simply with no vi's at 1x64k and if I add a VI I immediately have to bump it to three time that. to keep from getting cpu spikes and placards. I'm constantly trying to buffer my loads as I build a track WHICH WOULD NOT BE NECESSARY IF MOTU WOULD JUST ADD DM TO THE F___ing MIXER!!!!

Sorry, I regress...

auptown wrote:One issue that I am seeing sporadically is the "disappearing DP". It kind of just vanishes, like Gandalf at an orc-party.

Wow. I can relate to that in more ways than one!!

You're sailing along fine and then POOF! No warning, no crash report, nothing. Just a puff of smoke. You sit and stare at the screen as if it's going to reappear. Then, depending upon which day of the week it is you either start crying or speaking some foreign language with startliing fluency.

Sorry for misinterpreting your post. I'm still a bit confused but will re-read it when I get home and see if it makes sense to me then. I haven't used the limiter for awhile now, but will bring it up anyway just to see if I get the same behaviour. I'm just not clear on what you mean by DP EQ, if it isn't MasterWorks or Parametric EQ which are part of the standard MAS plug-ins.

Timeline wrote:IF MOTU WOULD JUST ADD DM to the Mixer

DM? sorry, is that Dynamic Memory or something like that? Thanks

Frodo wrote:...Just a puff of smoke.

That's it exactly. It happens so silently and suddenly that sometimes I stare at the screen and wonder if I have just woken up from a dream of working on a mix. I guess DP is really making OSX mad to be banished so unceremoniously.

auptown wrote:

Frodo wrote:...Just a puff of smoke.

That's it exactly. It happens so silently and suddenly that sometimes I stare at the screen and wonder if I have just woken up from a dream of working on a mix. I guess DP is really making OSX mad to be banished so unceremoniously.

It just happened to me a minute ago. I'd dumped several instances of VIs and a bunch of patches and was in the process of loading back in just 1 VI with just 1 patch. Falling somewhere between crash-on boot and crash-on-quit, I'm going to call this one crash-on-load.