DP 6.01 released!

[hrw]

DP6.1 has been very solid for hours tonight meaning not one crash!. But i really don't find the VI performance better than DP5.13 in fact there might be even more pops and dropouts. i'm comparing the same project. Anyone got thoughts on this?

[BobK]

GUI is definitely easier on the eyes - the mixer is a light gray, and the open area in TO, etc is also a light gray now. Also in audio files, the background to the waveforms in TO and SE is a gray. In the mixer window, the solo, mute, rec and input button color is brighter. In the sends, the mute and prefader buttons are orange (easier to tell if the send is muted now).

Thanks for this, John. I'd included most of these things in my letter to MOTU, so it was good to see that they took some action. Your post encouraged me to check out 6.01 when I was just about to remove DP 6 from my system entirely: Earlier yesterday, I'd gotten info from Magic Dave on how to do that, and I just hadn't had time.

As for the solo, mute, rec buttons in the mixer: they don't seem much brighter to me, but the illuminated area of those buttons does appear to be a bit larger - I compared the mixer side-by-side to a screenshot of 5.13. This definitely helps, but I think they should make those colors more saturated, like the record, input monitor, and play-enable buttons for tracks in the SE. Actually, I think the latter are TOO saturated, day-glo-ish for my eyes, and the difference in color schemes between those two windows seems amateurish. Somewhere in between would be good - like in DP 5.13 or Pro Tools.

IIRC, the data fields in the Info Bar of the SE seem to have a bit more contrast than before, so are more readable.

While I'm glad to see these changes, I'll probably still take DP 6 off of my desktop computer and/or install it on a separate drive. If they bring back the green/yellow colors for meter levels, that might tip the balance for me in the direction of DP 6, at least in terms of GUI issues.

[MIDI Life Crisis]

It's ironic that all the other VIs are fixed except M5.

"All" others except M5? Ethno, MX4, and the non-bundled MAS plugs included? Not included?

So far. I did go theu the other VI (included and not) and they all seem to be drawing and functioning correctly. M5 is functioning correctly, but I may have to delete its plist to get the redraw to kick in. Maybe MOTU needs to fix it, I don't know yet.

[Shooshie]

are you guys experiencing this, it got broke when 6 came out and it's still broke in 6.01.

http://screencast.com/t/IZADXviGxrF

The GUI colors are SO much better. The light colors for audio tracks with the darkened background no longer gives my eyes a headache

Still one terribly disappointing thing for me...
I still can not edit cc64 MIDI data at all without the event list.

Once you move the bottom cc64 data "black dot" it jumps up to a MIDI value of (1) and can not be put back to zero (off) without editing the value in the event list. Major pain in the butt because this makes the sustain hold all notes after that. I have been editing a ton of piano MIDI, and I am forced to use DP5.13 because DP6.0 and now 6.01 is still broke in this regard. I get the same results in the graphic editor too.
Anyone else experiencing this?
Dan

Dan, that sucks. But I think there's an easy workaround. Set up and save a search for CC64 values =1 (or any way it takes to get the selection), then do a Controller Data Change which sets selected controller64's to 0. You could do a QuicKeys command that does both in series, and that would make it a quick fix. Hopefully they'll fix it soon. I don't like this one any better than I like the pitch-bend editing problem. Geez, MOTU! Can we get the numbers right, please?

PS: I haven't tried this workaround; I haven't installed the update yet. That's on my list of things to do.

[MIDI Life Crisis]

are you guys experiencing this, it got broke when 6 came out and it's still broke in 6.01.

http://screencast.com/t/IZADXviGxrF

While I cannot duplicate your experience, if I edit an event in the event window (the consolidated windows are active) it freezes DP. From the dock, I can navigate to various available windows in DP, but DP remains frozen. Quitting from the dock seems to be normal, but the OS reports the program quit unexpectedly.

[dpdan]

thanks Shooshie and MIDI life,

at least I know it's not just me. It's so aggravating, because we need to hear the
difference immediately in the editing of the sustain pedal in order to be positive
that it's exactly what we want.

I just can't believe that DP "known originally" as a MIDI sequencer has broken
features that makes me go back to 5.13. Oh well.

I really do like the changes they made to the gui, I too wish the meters were the
same green color as before. A much better contrast, but they need to loose the black
background if they go back to green,.. I suspect they won't.

These broken MIDI editing features makes DP6 a waste of 200 bucks for me because
I can't make music with it. I have been emailing Dave Roberts these screencast things
so he can pass it on to the tech engineers.

Dave is a FIRST CLASS guy, and I am so honored to have access to him.

Thanks guys!
Dan

[Timeline]

You can modify the image files to get the green vu colors back I think.

[ghobish]

You can modify the image files to get the green vu colors back I think.

That can be done for the Meter Bridge, but not for the meters in the Mix Window.

[ghobish]

Yay.

[Frodo]

There remains the problem of putting in pitch bends as well-- extremes cannot be put in graphically or with a controller-- only numerically. This was something that was around in DP5.

What kind of extreme are you talking about?

This was something that another user reported, and it's similar to what dpdan was going through. With Dan it was about getting 1s down to 0s. With the pitch bend question, it was a matter of the accessing the max -8192 to +8191 instead of the DP initial limit of -8064 to 8064, where the max allowable range numbers below -8064 and above +8064 must be edited numerically when they won't register via controller data or graphical pencil entry. Those numbers were the result of an experiment in DP5 on this end by drawing in pitch bend data from one extreme to the other only to find that the extremes were trimmed after recording them. There was similar experiment done in DP6 but I don't have the specific numbers handy from that experiment. It was concluded that the same range trimming was taking place in DP 6.0 even if the numbers were different. I have not tried this in DP 6.01.

I've been looking for that particular thread and am having trouble finding it. If I run across it I'll post a link.

The experiment was simple. Open a MIDI track in the GE, choose the pencil tool and select Pitch Bend as the controller. Then draw in a ramp in the controller display area from highest to lowest-- or lowest to highest (it doesn't matter). Then check the numbers at the extremes. If the bottom number his higher than -8192 and if the top number is lower than +8191, then you'll have the root of the question of why it's not possible to reach those extremities without typing them in numerically.

I realize that this may be of no consequence to some and it may not even be that much of an impediment. But if you deal with such things regularly and repeatedly, what might have been done in a single step suddenly becomes several steps which, over the space of a single project, can add up to lots of extra time doing numerical edits that shouldn't have to be done.

[mikebeckmotu]

SoundToys plugins are now working! URS Channel Strip Pro still not passing audio, though I can see the meters working in the plugin.

[bradycline]

As one of the people sitting on the sidelines of the DP6 upgrade, I'm curious what these 6.01 changes actually look like. Specifically the GUI and the new Inspector.
Thanks!

[pcm]

Did anyone find any official notes on what this update allegedly fixed?

Thanks.

You're dreaming.

[Frodo]

Did anyone find any official notes on what this update allegedly fixed?

Thanks.

You're dreaming.

ZZZZZzzzzzzz.

[martian]

must be one of those pipe dreams


PS - maybe I should rephrase that - functionality is of paramount importajnce - after all no one is looking at the DAW when listening to your produce...

so whilst nice looking is nice looking - I feel that loosing important visual references - is soundbite names is a bit crap - and whilst I can inspect each clip individually I don't enjoy imitiating a hen pecjking here and there to find stuff....

wastes alot of time...

can zoom in - but again I DIDNT used to have to so why is it necessary now?

But I am enjoying the sability of 6 so far - and wav files appear to be more resistant to the usual BS -39 and other "resource" fork probs... ( SD2 is a poor format these days )

if you have any sway please ask for re instatement of better visibility for soud bite names,,,'

an adjust clip gain for a selected bunch of clips...

these would make my day... ( and any one else doing post audio )