Fixed/Not fixed/Broken in DP 7.1

[Twitch_12]

I have had a few experiences in the past where some CC's would be reseting every time I hit play. Usually it was due to another track earlier in a large session that had written CC for the same channel. With event chasing on, DP will see the last CC setting for a given channel and then jump to that setting even if you are on a new a new track. Also, you might have a corrupted session. If all else fails, I would try loading into a new session.

Good to know it's not a bug. Interestingly, I only have 1 MIDI track in this sequence but the project file was generated last week on 7.02 so it sounds like a fresh project file should clear it up for me.

Thanks.

[songsmith]

"Upgraded" to DP7.1 from 7.02, and this is my experience...

1) Opening my 7.02 project file is slower to load.
2) Pressing the spacebar doesn't to do anything, then it hesitates, stutters, then plays, then stutters.
3) Stopping playback. Check the mixer window. Check the inserts, notice the new Tuner. Open it. Looks pretty. Close it.
4) Back to the Sequence window, press play again... spinning rainbow.
5) In a few seconds the fan kicks on. Note to self -- there's something happening that isn't apparent on screen, but my computer is working hard.



6) Force Quit DP 7.1 - immediately the fan starting winding down.
7) I go back and launch 7.02.
Opening my 7.02 project file is quicker.
9) Press play and the project slowly gets in gear and starts playing (before installing 7.1 this was not slow).
10) Everything is sluggish... starting, stopping, etc.
11) Go to the mixer window and notice that the Tuner plugin is available as an insert. Guess I have the new plug-in whether I'm using 7.1 or not.
12) Notice that the fan starts kicking on (this is also not normal)
13) Decide to close the project without saving it.

I guess know I need to uninstall this update completely and go back to 7.02 if I want my original snappiness. This is just crazy.

[Shooshie]

My usual way of making a selection in the tracks window is not working...

In previous version I'd select a few bars at the top of the tracks window then click once on one of the tracks from my long list to isolate something eg 2 bars of snare
Then command R to repeat a bunch of bars.

In 7.1 all seems ok until I get to the Command R and it remains greyed out.

Yeah, I noticed this too. It's not just the repeat command, it seems that most / all commands requiring a time range selection in TO are greyed out unless you have all tracks selected. (Using the time ruler to select and not modifying your selection by clicking on track names)

The work around I found was to switch to SE, it seems the problem doesn't occur in SE.

Is it possible that your Selection Mode for the Tracks Overview has changed? Go to Preferences/Tools, then look for the drop-down menu at the top of the page with three options: Range selections only, Phrase and Event Selections Only, and All) "All" is the most flexible.

With your indulgence, I'd like to paste in a selection from the Tips Sheet. I simply cannot imagine MOTU changing the way DP handles selection in the TO window, so if you feel like it, you can read this and see if it changes anything. I don't have 7.1 installed yet, so I can't comment directly.

From the Tips Sheet:
••••••••••••Secrets of the Tracks Overview Window••••••••••••

[deleted by Shooshie, since the poster solved his problem. You can find it on the first page of the Tips Sheet. Just search for "Secrets".]

[Twitch_12]

I created a new project file with 7.1 and both problems I was experiencing have disappeared.

The time range selection in TO now behaves as it normally does and the chasing problems I was experiencing have also vanished.

I supposed it's a good idea to start fresh with a new project file (and possibly even trash your preferences) when beginning to use 7.1.

To be fair, I don't think I've ever used a DAW that didn't occasionally behave strangely when loading project files generated from a previous version.

So far I think this is a great update and the frequency of the 7.x updates are definitely a refreshing change from what I had experienced with Logic 7 - 8. I hope MOTU keeps this up. I for one, would gladly pay a premium for a DAW that is evolving quickly (in terms of bug fixes and features).

Now, if only MOTU could bring the OS X patch lists into the 21st century making them easily customizable for virtual instruments and IAC in addition to external hardware. I'm sure a lot of film composers would appreciate being able to create and label their own patch lists for internal instruments. Ahhh.. maybe someday...

[Shooshie]

Now, if only MOTU could bring the OS X patch lists into the 21st century making them easily customizable for virtual instruments and IAC in addition to external hardware. I'm sure a lot of film composers would appreciate being able to create and label their own patch lists for internal instruments. Ahhh.. maybe someday...

Can you think of a DAW that does that? That would be a massive undertaking, requiring endless updates and would be subject to failing every time any VI developer put out an update. I'm not even sure it would be possible without all developers coming up with some kind of standard, and even then not likely. For example, Wallander Instruments' "WIVI" interface is its own self-contained environment, and DP is never aware of the nature of the instruments that come through a particular channel. I could go into greater detail, but I won't. Suffice to say that a "patch list" for DP isn't even congruent with the architecture of WIVI. The same is really true for Kontakt, Mach5.2, or any other VI that I know of, though some of those might possibly publish their available libraries in some form. Still, it's extremely unlikely. If some DAW can do that, I'd like to know how they did it.

Shooshie

[waterstrum]

FIXED!
The bug where you would try to rename a soundbite in the soundbites window and it would require a few extra keystrokes before recognizing your typing.
Thanks!

[NashvilleJoe]

sadly though, I had 2 crashes in 7.1 last night, so I'm back to 7.02 which I have not had a single crash in, all the way back to 7.0. Sending logs to MOTU today, but they all start like this.. QD, is that Quickdraw?

i reverted to 7.02 also- had my first crash during a vocal session- lost a take ; (- haven't had a crash in almost a year- i hate losing data. So i am back to 7.02 until the all clear flag is out !!

[waterstrum]

DP7.1 seems much more stable in my studio.

It seems to have fixed several bugs that were bugging me.

On the downside,
Waves Vocal Rider still sinks the boat and Stillwell plugs still take over the control.

On the upside,
So far, much better for stability.

Also,
The plug in chains thing is very cool.
I have favorite combos and it is excellent to be able to access them so fast.

A big "thumbs up" to MOTU!

[Twitch_12]

Can you think of a DAW that does that? That would be a massive undertaking, requiring endless updates and would be subject to failing every time any VI developer put out an update. I'm not even sure it would be possible without all developers coming up with some kind of standard, and even then not likely. For example, Wallander Instruments' "WIVI" interface is its own self-contained environment, and DP is never aware of the nature of the instruments that come through a particular channel. I could go into greater detail, but I won't. Suffice to say that a "patch list" for DP isn't even congruent with the architecture of WIVI. The same is really true for Kontakt, Mach5.2, or any other VI that I know of, though some of those might possibly publish their available libraries in some form. Still, it's extremely unlikely. If some DAW can do that, I'd like to know how they did it.

I'm not suggesting that DP somehow become aware of what instruments you have loaded in Kontakt (although, that would be nice and it is currently being done by Logic and the EXS). What I'm suggesting, is that MOTU come up with a method for you to edit, save and load patch lists that you can associate with any internal DP MIDI port in your sequence.

I'm doing this with Bidule right now. I have to use Cherry Picker and MidiOverLan (in loopback mode) but I'm able to create my own patch lists for for any of the 128 MIDI ports MidiOverLan provides.

All I have to do, is route a MidiOverLan Output to an "external" instrument in AMS. From there I can easily create my own device and patch list using Cherry Picker and it all shows up in DP. It works remarkably well but requires MIDIOverLan (in order to trick AMS into thinking these devices are actually external).

What's also cool, is that I can change the AMS configuration to load an entirely new set of patch lists in one click. This works out great when moving from project to project.

So, I'd say this is certainly not impossible, and in fact, I think necessary if the "Default Patch" and "Patch" columns are to remain a useful and relevant feature of DP as external MIDI hardware is disappearing at an ever increasing rate.

I used to have huge track layouts to accommodate the many instruments I would routinely use during the course of scoring a film. Now, I can have a super lean track list. I just grab a MIDI track, set the output to whatever instrument bank I'd like to address, and all my patches show up in the patch list, allowing me to quickly browse my own custom banks with meaningful names instead of "Patch 001", "Patch 002", etc.

I just wish it was possible for me to option click the Patch column to type in my own names instead of having to exploit MIDIOverLan in this way.

[bradswan]

7.1 sometimes crashing when I edge edit and when I select region in time ruler. Copy and pasting MIDI is out of skew. When I grab, for instance, a two bar phrase and paste it somewhere else, it gets pasted out of time, and yes I am copying in grid mode.
Back in 7.02 and working great.

[ironchef_marc]

Is it me or is DP 7.1 not chasing MIDI CC's?

I'm working on a cue, and I have CC #83 setup to control send level in Kontakt. Usually, I just twiddle a knob on my control surface and leave it at that.

DP 7.1 seems to be reseting all CC's when playback starts, which means I have to record the CC to the track. But it won't chase it. Kontakt only receives the CC when DP plays it.

Anyone else experiencing odd chasing behaviour?

I too am seeing problems with CC not chasing like MIDI volume in a track (not printed but in the mixer)

[songsmith]

I thought I'd check to see what happens if I run DP7.1 in "Safe" mode, which disables all plug-in that are not MOTU plug-ins. If there are any conflicts with plug-ins, this would tell me for sure. Also, I'm using Core Audio with my laptop speakers, so there are no hardware conflicts to worry about.

Here's what DP7.1 looks after ten minutes of "Safe Mode"...


The first sign that the problem was that the fan started kicking on. All I had to do was let DP 7.1 sit there for a while -- idle.

I'm going back to 7.02 and maybe version 6. I can't take these crashes anymore. I'm not your beta tester, MOTU! I have an album to record!

[Shooshie]

That's pretty indicative of what we call in the business... "a problem."

Ok, ok... I have no idea what we call it in the business. But it's definitely a problem.

Shoosh

[Armageddon]

I thought I'd check to see what happens if I run DP7.1 in "Safe" mode, which disables all plug-in that are not MOTU plug-ins. If there are any conflicts with plug-ins, this would tell me for sure. Also, I'm using Core Audio with my laptop speakers, so there are no hardware conflicts to worry about.

The first sign that the problem was that the fan started kicking on. All I had to do was let DP 7.1 sit there for a while -- idle.

I'm going back to 7.02 and maybe version 6. I can't take these crashes anymore. I'm not your beta tester, MOTU! I have an album to record!

I've been having this same problem in DP 6.02/03 and Tiger. Something simple like ... selecting a note after the project is loaded, that's enough to cause a SBBOD, my MacBook's fan to kick in and ten minutes of waiting to see if anything changes before me having to Force Quit and start over. Other times, the project will actually just load up and quit. Nothing has actually been done. It just loaded up the project file, loaded all the VIs/samples and decided to quit afterwards. In my case, I'm not sure it wasn't just that DP was overloaded (five instances of Kontakt, two instances of RealStrat, six instances of Amplitude Metal and one of Ampeg SVT, plus a linked stereo .sd2 file, all running at 48 kHz/24-bit) and decided to get cranky, but it's also happened on other projects. I even suspected pre-gen mode, but it also happens when I switch everything over to run in real time. For my part, I'm planning on attempting to upgrade to Snow Leopard, then, eventually, to DP 7, and ultimately, to put everything on a much faster computer with a faster hard drive (i.e. - a Nehalem iMac). I suspect that some of it has to do with the pre-gen partition DP makes on a slower hard drive, or that my MacBook 2 GHz isn't fast enough to process a multitude of VI tracks like that in DP 6, or that Tiger may even be too clunky to aid in the CPU/OS department. I've even tried running Clean My Mac and stripping all the fat off of my programs and plugs, but so far, all I've done is reclaim a GB or so of hard drive. To be fair, I encountered a multitude of problems like this (aside from the pre-gen stuff) in the ultra-stable DP 5.13, so I have to assume a lot of it is what I'm running it on. I'm hoping Snow Leopard helps speed up things, and maybe DP 6.03 will run a lot better.

[audios]

[not yet fixed] So far I've run across the "sleepy fader syndrome" in 7.1
and

Phil

+1. Really shows up after i have done "latch" automation on a project. The playback still reads the markers in the track but the fader sleeps at the bottom of the slider. If I open the same project in 7.02, no problem.

Also noticed that opening an instance of "Play" in the v-rack crashes DP7.1.

+1 on the "re-fresh" or "re-drawing" of waveform data in v7.1. If I open a pre-existing project done in v.5.13 on up to 7.02, it takes 5 minutes to "re-draw" the waveforms in a session with 30-40 tracks (mono or stereo). And, if i try to start to play the sequence, DP7.1 crashes until all waveforms are drawn.

That's all i have to report for the moment. Just loaded 7.1 on Thursday last week. But..... here's another small gripe. The only way i find out if DP has an update is through this forum. Why doesn't MOTU send out a blanket email to their registered users with a direct link for downloading the latest versions of registered software/drivers, etc..? Maybe you're listening MOTU?????