MOTUnation.com

bayswater wrote: Even the things that appear to be bugs or bad coding, like the keyboard issue, or slow graphics, or more CPU load are not happening to everyone (none of them happening here). A few people reported that window sets don't resolve consistently. That happened to me in 7.24 but doesn't in 8.

That's what is SO weird... some users feel crippled with DP8 and some others are loving it...
That will certainly not make matters any easier for MOTU's engineers to figure out these bugs some are experiencing. I wouldn't like to be in their shoes!

I'm will get DP8 after I finish my current projects and after they iron out these bugs you guys are talking about. I will also change master computers, so everything will be fresh and done in a few consecutive days...

DP 8 and Rewire in Plogue Bidule are working perfectly fine here and I believe are working with other apps such as Jbridge. I have no reason for Reason, but attributing those issues to DP8 seems... unreasonable.

Or is it impossible the issues are (as mentioned above) system related or even a dormant bug in Reason?

I've done several projects in DP8 now and once I got past the 32 bit bridge, have had zero problems.

FMiguelez wrote:That's what is SO weird... some users feel crippled with DP8 and some others are loving it...
That will certainly not make matters any easier for MOTU's engineers to figure out these bugs some are experiencing. I wouldn't like to be in their shoes!

I hope everyone with problems submits crash logs and tech reports to MOTU so they can see the system configurations that consistently have problems.

Hi FMiguelez,
(Boy this is getting funny...) I never talked about a perfect DAW my man. Just fairly pointed out a major and surprising flaw in DP8.
I know, they'll get around it and yes, I've gone back to 7.24 for the moment.
Salud!

Antonio wrote:Hi FMiguelez,
(Boy this is getting funny...) I never talked about a perfect DAW my man. Just fairly pointed out a major and surprising flaw in DP8.
Salud!

The comment was directed at you guys in general who sounded like MOTU is the only "sin" company who ever dared releasing a less-than-perfect .0 version, not necessarily at you in particular.

But don't worry, Antonio. As you know, if MOTU's history repeats itself, as it always does, we will have a MUCH BETTER DP8.01 version very very soon, one that I'm sure will make you proud and happy.
I expect DP8 to be just perfect by 8.2 or so.

And remember: Don't be surprised if these revisions include not only getting rid of bugs, but also cool new features they will probably add as they work on DP more.

[EDIT]
Antonio, I see what you mean now. I did call your name specifically at the end of that post. Since you wrote your post in the context of my discussion with Guitar Gaz, and commented on it, I guess I took it in that same context. I did not mean to misrepresent your words.

Salud, compadre!

I think I may have figured out why DP8 wasn't working very well for me, and it may explain the disparity between users on this forum who have no trouble with an upgrade of DP8, and those that do.

The key word here is "upgrade"...

Since I noticed varying reports here on the performance of DP8 and how it could affect an existing DP7 installation, a couple weeks ago I duplicated my boot drive and installed DP8 on that. It didn't work very well: jerky scrolling, key commands missing, overall pretty awful.

Today I decided to try again and it was a little better but not so great. Some of the key commands were missing. I noticed missing bounce settings and exported a small movie with a new soundtrack. Not so bad, but not up to speed either.

So, I quit DP8 and opened up the install of DP7 that was already on the copy of my boot drive to check if anything was affected. It required the installation disc to be inserted and the key code entered, the usual MOTU copy protection. Once DP7 opened, everything was intact and it ran just fine.

Here's the kicker: I quit out of DP7 and opened DP8. Golly gee, my key commands all worked fine. All my bounce setting were there. Scrolling was perfect. I went through an entire workflow without a hitch.

My conclusion is that a DP8 upgrade does not function correctly unless the existing install of DP7 is authorized. This would make sense if certain files of the DP7 install were inaccessible to DP8 in some way, like the key bindings for the key commands, for instance.

I dunno, just a hunch here. I still need to do another workflow test but it's possible this is what is going on with the mysterious separation between users that have DP8 running with no problem, and those that don't.

While this is interesting, I don't think it works for me - I still have DP7.24 and have been running that anyway - so unless I have missed something it won't work for the crashes concerning Rewired Reason. Also Lorne at Motu has replicated the crash and it seems related to a CoreMidi problem triggered by Reason/Rewire. They are investigating. But thanks for the thought.

MIDI Life Crisis wrote:DP 8 and Rewire in Plogue Bidule are working perfectly fine here and I believe are working with other apps such as Jbridge. I have no reason for Reason, but attributing those issues to DP8 seems... unreasonable.

Or is it impossible the issues are (as mentioned above) system related or even a dormant bug in Reason?

I've done several projects in DP8 now and once I got past the 32 bit bridge, have had zero problems.

The crash points to something about DP8 and Reason/Rewire plus CoreMidi - Reason hasn't changed and works perfectly with DP7.24 - so the thing that has changed is DP8 - but it is interesting that it doesn't seem to be Rewire itself. So thanks for this feedback.

bayswater wrote:Even the things that appear to be bugs or bad coding, like the keyboard issue, or slow graphics, or more CPU load are not happening to everyone (none of them happening here).

I spoke too soon. Now seeing the loss of keyboard control, and the corresponding commands in the menus are greyed out. I use all Apple keyboards pads, etc, so it's not a clash with 3rd party drivers. But I notice that it has only happened when I spent some time in the MIDI editor.

I am noticing a small bug where the record enable lights, input monitor light, and sometimes even automation enabled buttons do not show up as “on”, enabled, red etc, when in the mix window that is broken out from the consolidated window.
For ex: I will look in the tracks list, see the guitar is red and in record mode, but the broken out mix window shows no red as if the guitar is NOT record enabled.
Definitely a little bug.

Also, Scuffham amps, when used in a dp 8 file, cause dp 8 to crash on shut down. The owner has duplicated the problem on his end and says he is working on a fix.

I have (or rather had) the numeric keys above the querty assigned as shortcuts to change my different window sets and open various windows like transpose, duration etc.

When I try to change a numeric value in a UAD plug (like precision limiter) using the keyboard, DP8 responds with the shortcut and exits the uad window.
So a "1" (or whatever number) entered using the right side keypad calls up the shortcut assigned to the "1" that is above the letter "Q".
This was not happening in DP7.

I'm also losing the delete key and various other commands randomly.

On a side note I am loving the new plugs-especially Dyna squash. 2 or 3 instances in series on loops can certainly do A LOT OF DAMAGE
Cheers, Bolla

bolla wrote:I have (or rather had) the numeric keys above the querty assigned as shortcuts to change my different window sets and open various windows like transpose, duration etc.

When I try to change a numeric value in a UAD plug (like precision limiter) using the keyboard, DP8 responds with the shortcut and exits the uad window.
So a "1" (or whatever number) entered using the right side keypad calls up the shortcut assigned to the "1" that is above the letter "Q".
This was not happening in DP7.

I'm also losing the delete key and various other commands randomly.

On a side note I am loving the new plugs-especially Dyna squash. 2 or 3 instances in series on loops can certainly do A LOT OF DAMAGE
Cheers, Bolla

I too have been losing the delete key

bolla wrote:I have (or rather had) the numeric keys above the querty assigned as shortcuts to change my different window sets and open various windows like transpose, duration etc.

When I try to change a numeric value in a UAD plug (like precision limiter) using the keyboard, DP8 responds with the shortcut and exits the uad window.
So a "1" (or whatever number) entered using the right side keypad calls up the shortcut assigned to the "1" that is above the letter "Q".

I also have the the same number keys assigned to screen sets. I'm not having the same problem when I use the same keys to enter values. I don't have UAD on the same system as DP 8, so it may be that this problem is specific to UAD and when it takes control of the keyboard.

toodamnhip wrote:I am noticing a small bug where the record enable lights, input monitor light, and sometimes even automation enabled buttons do not show up as “on”, enabled, red etc, when in the mix window that is broken out from the consolidated window.
For ex: I will look in the tracks list, see the guitar is red and in record mode, but the broken out mix window shows no red as if the guitar is NOT record enabled.
Definitely a little bug.

Found it. Reported it. I hope MOTU can find it.

It took all day, working in an audio project, before this bug showed itself. It only happened when I was soloing tracks. The Sequence Editor showed the soloed tracks were play-enabled, and non-solo tracks were muted. But the Mixing Board showed no difference between them. Only a graphic element in the center column of the faders gave any clue at all to the muted status of the non-soloed tracks. Otherwise, there was no change between soloed and non-soloed tracks.

Shooshie