Page 2 of 7
Re: MOTU - "BETA Testing" DP8
Posted: Sat Oct 06, 2012 1:15 pm
by labman
MIDI Life Crisis wrote:As posted earlier in another thread, I don't use consolidated windows and don't like them, but with the new rewrite, I thought I'd give it a try. Eh... no so much, but when I went to go back to disabling consolidated windows, ALL my windows disappeared and would not come back. .
We see something like that. DP8 window sets dont always reset to right size. Can hit the window set key multiple times and get differing results. And some just disappear when they should be there. And wont come back til reboot the DP file. Yes, very odd.
Re: MOTU - "BETA Testing" DP8
Posted: Sat Oct 06, 2012 2:34 pm
by Shooshie
Try restarting DP8. There is a bug which seems to do odd things to keyboard commands and menu items. Restarting it usually sets it right again, though it will keep happening. Eventually DP will forget its commands again.
Shooshie
Re: MOTU - "BETA Testing" DP8
Posted: Sat Oct 06, 2012 3:31 pm
by James Steele
I've never completely warmed to the Consolidated Window. I don't think it's necessarily logical... just don't have a comfort level with it and with a 30" and 24" monitor, I'm not really feeling pressed to start using it.
Re: MOTU - "BETA Testing" DP8
Posted: Sat Oct 06, 2012 7:01 pm
by bayswater
I have had the key command related problems, and the problem of screen sets not drawing windows to the original size with DP 7.24. It's intermittent, but has always been there. Clicking on the Finder and back to DP usually fixed it. Too bad its still happening. Maybe a OS X related problem?
The scrolling problem looks a bit like the "sluggishness" problems noted in another thread.
What about crashing?
Re: MOTU - "BETA Testing" DP8
Posted: Sat Oct 06, 2012 8:22 pm
by stubbsonic
A really minor lil' inconsequential bug:
Springamabob's Red LED doesn't go off when it is bypassed via the "footswitch".
I did have my first recording of audio do a little glitch where the track appeared to end and I hit stop, but after stopping the last couple measure of the audio recording were truncated (shortened). It was odd.
I haven't been working on anything yet in DP8. I know this isn't the official bug list (or is it?)
Re: MOTU - "BETA Testing" DP8
Posted: Sun Oct 07, 2012 6:10 am
by williemyers
Shooshie wrote:In retrospect,...It's a problem with keyboard/menu focus, ...
Shoosh, I've never heard the expression keyboard "focus" before, but if it means whether or not an app can "see" (and repsond to) the computer kybd., then I'm in agreement with you here! And, with others that have noted that the problem goes intermittently back in to 7, as well. I have also tried all of the work-arounds that were suggested - usually the click-on-the-desktop-then-click-back-in-a-DP-window thing would work...*usually*...
But the odd thing for me has been that sometimes, in order to do the above, I would have to click in the desktop area of my *2nd* monitor, then click back on my Tracks Overview window in my primary monitor, in order to get DP to "see" the kybd again. That always did work, but was a bit of a workflow buster. Hope MOTU will have a good look at this...
Re: MOTU - "BETA Testing" DP8
Posted: Sun Oct 07, 2012 6:16 am
by buzzsmith
I don't recall having any "focus" issues with DP 7 at all.
The exception being just a few plugins or VIs that steal it. Clicking away from that plug or VI window resolves it.
(On iPad right now so I can't list exactly which ones...)
Buzzy
Re: MOTU -
Posted: Sun Oct 07, 2012 6:57 am
by williemyers
buzzsmith wrote:I don't recall having any "focus" issues with DP 7 at all.
The exception being just a few plugins or VIs that steal it.
Buzz, but wouldn't those be "exceptions that prove the rule"? I don't recall selecting VI's (prior to DP7) causing DP to lose it's connection to the computer kybd?
Anyway as I said, it was a fairly intermittent concern in 7, but is pretty pervasive in 8.
Re: MOTU - "BETA Testing" DP8
Posted: Sun Oct 07, 2012 7:34 am
by buzzsmith
williemyers wrote:buzzsmith wrote:I don't recall having any "focus" issues with DP 7 at all.
The exception being just a few plugins or VIs that steal it.
Buzz, but wouldn't those be "exceptions that prove the rule"? I don't recall selecting VI's (prior to DP7) causing DP to lose it's connection to the computer kybd?
Anyway as I said, it was a fairly intermittent concern in 7, but is pretty pervasive in 8.
Don't know, Willie. I just (perhaps wrongly) attributed it to the VI or plug not being coded properly.
When I get the studio online later, I'll see which ones steal the keyboard with 7.22.
Grazie...
Buzzy
Re: MOTU -
Posted: Sun Oct 07, 2012 7:51 am
by labman
buzzsmith wrote:I don't recall having any "focus" issues with DP 7 at all.
The exception being just a few plugins or VIs that steal it. Clicking away from that plug or VI window resolves it.
(On iPad right now so I can't list exactly which ones...)
Buzzy
Agree wholeheartedly Buzzy.
It was/is not the same in DP7.
Our one engineer here, who designed spy planes in a former life, thinks that DP8 is having problems relating to standard OSX programming commands and structure. - whatever that means. lol
Re: MOTU -
Posted: Sun Oct 07, 2012 8:02 am
by williemyers
buzzsmith wrote:
Don't know, Willie. I just (perhaps wrongly) attributed it to the VI or plug not being coded properly.
Ah, now, there's a good thought that I hadn't considered... Do let us know what you find?
Re: MOTU -
Posted: Sun Oct 07, 2012 8:24 am
by williemyers
buzzsmith wrote:I don't recall having any "focus" issues with DP 7 at all.
And now that I think about it, the "DP losing kybd. focus" instances that I had in DP7.24, only occured with VI's and windows on my *2nd* monitor, that would cause me to lose focus with the primary monitor. My setup is; Control & Tracks Overview on the primary monitor - - Mixer, VI's, Graphic editor, etc. on the 2nd. It was when I would click on, say, a Kontakt VI on the 2nd that I would lose contact with Tracks on the first.

Re: MOTU - "BETA Testing" DP8
Posted: Sun Oct 07, 2012 10:12 am
by BobK
I haven't spent a lot of time with DP 8 yet, but so far I haven't had any of the issues you mentioned, Shoosh. I just ran through the list, and all is well. Maybe my working sessions haven't been long enough for them to show up - just now I was futzin' around for about 50 minutes.
I confirmed the Springamabob issue - hitting the 'footswitch' does bypass the effect, but not only does the LED stay lit, the 'Bypass' button doesn't turn red and the text doesn't change to 'Bypass on'. If instead you click on the 'Bypass' button to bypass the effect, the LED does turn off (and the effect is bypassed as expected).
I checked Analog Chorus, Analog Phaser and Analog Flanger, and they all behaved as expected: hit the footswitch and the 'Bypass' button turns red and changes to 'Bypass on'.
Re: MOTU - "BETA Testing" DP8
Posted: Sun Oct 07, 2012 11:01 am
by buzzsmith
2.66 GHz Quad-Core Intel Xeon (late 2009)
OS X 10.6.8
DP 7.22 <<<<<<< (Not DP8)
This is not definitive, more like an overview, but this is what I found spending about 30 minutes. I did not open
every plugin but randomly chose just a few from each manufacturer.
- Slate Digital FG-X: X When a preset is selected, it steals the keyboard.
Clicking back to any DP window resolves it. Changing presets present the same scenario.
Slate Virtual Channel: √
Slate Virtual Mixbuss: √
Slate Virtual Tape Machines: When first opened...√. Switch any switch and it disables the space bar play. X
Izotope Ozone 4: √
Antares Auto-Tune 5: √
Nomad Integral Studio Pack: √
UAD-2: √
Waves 8: √ (Unless you click on the far left Waves icon to get info. Then you have to dismiss that window.)
Synthogy Ivory (1.72): √
Music Lab-Real Guitar 2: √
XLN Audio-Addictive Drums: √
Miroslav Philharmonik CE: √
Kontakt 3: √
Kontakt 4-Player: √
Omnisphere: √
Stylus: √
Trilian: √
Arturia MiniMoog: √
Buzzy
Re: MOTU -
Posted: Sun Oct 07, 2012 12:21 pm
by Prime Mover
labman wrote:Our one engineer here, who designed spy planes in a former life, thinks that DP8 is having problems relating to standard OSX programming commands and structure. - whatever that means. lol
Actually, that was my first thought, too. Programming in carbon and non-cocoa is probably very different, and would involve a lot of "hacks" to try to get things working seamlessly with the standard cocoa framework. Although Cocoa is likely a lot simpler and more robust, it's very possible that that was a part of the program that had to be rewritten from scratch, and is likely a lot more susceptible to bugs.
And sadly, yes, I'm reporting the same keyboard problems. Also, I'm getting an annoying playback head flickering. Has anyone else reported this? As the playback head goes through the timeline (on any window) it sometimes color inverts the whole vertical area around it, momentarily, turning a white background black. However, it is only cosmetic, and causes no functional problems.
Hope the keyboard thing is rare, because I killed Waves 8 just 2 days ago, so there's no going back to DP7.