DP 5.01-- User reports

Timeline · Post by **Timeline** » Mon May 29, 2006 8:28 pm

Well done good start. Would be nice to add confirms over time.

Frodo · Post by **Frodo** » Mon May 29, 2006 8:51 pm

Yeah-- it's only a start, but let's hope the joint effort leads us to some workable solutions....

Shooshie · Post by **Shooshie** » Mon May 29, 2006 10:47 pm

Frodo wrote:
Matcher wrote:...And here's motu's tech support's answer:

2. This is the limit for Pitch Bend. The range goes from -8064 to 8064.

Everyone can make their own conclusions about this.
There are two issues with this--

1. I know for a fact that the tech rep is incorrect(with all due respect to MOTU), but let's just say for the heck of it that he IS correct...

2. Then, the info in the manual is entirely wrong, and there has been nothing offered in the way of accurate info to correct it.

We know the range is -8192 to +8191 as stated in the manual. These numbers can indeed be typed in, but can't *always* be drawn in or edited with the pencil tool to full range on my system. Neither can I access the full range by using the pitch bend wheel even when my controller is set "wide open".

When you can't draw the full range of a controller, switch to a different continuous data ruler scale. Clicking on the left-hand scale of that bottom panel of the MIDI Edit Window will change the view from Controller scale only, to Pitch Bend Scale only, and to Combination scale. The combination scale works best for me when drawing controllers to their extremes. I'm not sure if it will take pitch bend to its negative extreme, but I rarely adjust pitch bend beyond a slight waver. If you have trouble getting pitch bend to its extreme, select the whole range that you want to adjust, and use the CONTROL-DRAG (proportional drag) to adjust them until the extreme range is reached.

Shooshie

Frodo · Post by **Frodo** » Tue May 30, 2006 12:48 am

Shooshie wrote:When you can't draw the full range of a controller, switch to a different continuous data ruler scale. Clicking on the left-hand scale of that bottom panel of the MIDI Edit Window will change the view from Controller scale only, to Pitch Bend Scale only, and to Combination scale. The combination scale works best for me when drawing controllers to their extremes. I'm not sure if it will take pitch bend to its negative extreme, but I rarely adjust pitch bend beyond a slight waver. If you have trouble getting pitch bend to its extreme, select the whole range that you want to adjust, and use the CONTROL-DRAG (proportional drag) to adjust them until the extreme range is reached.

Shooshie

Thanks Shooshie-- clever as usual. But I'm still seeing a range limit unless I can type the numbers in. Forutnately, a full pitch bend range has so many increments that to set just the peak number manually at least yields the right pitch. I don't use the extreme pitch bend "as pitch bend" that often (maybe on some R&B synth bass here and there) but when the pitch wheel is assigned to other controller functions such as velocity x-fade or expression, etc. I use this with VSL's Vienna Instruments which makes libreral use of controllers and keyswitches. In those cases, it's important to have DP receiving the proper incremental numbers to execute the best the expressive options available to the user, whether that means stretching the pitch (uncommon in orchestral writing) or controlling the speed of a trill or tremolo in semi-real-time.

Matcher · Post by **Matcher** » Tue May 30, 2006 2:42 am

Also, I'd like to see the continuous data ruler scale's white line that indicates the rough value of the current location of a tool (pencil for ex.) to display the correct values that can be seen in the upper left corner in the MIDI editor. Now, I can see the value is 8064 even before the white line hits 80 on the meter.

I don't mean to rant, but this stuff makes dp feel like a fake watch with all the small details put in just to impress at a glance, but when you try to make put them to use, you wish you had the real one.

Dubnick · Post by **Dubnick** » Tue May 30, 2006 4:24 am

Hey everyone - relatively new DP user, getting familiar with it between projects in PT 7.1. I skipped the initial upgrade from 4.61 to 5, but installed 5.01 the other day. So far so good, but I had a question regarding the BTD issues, and please excuse me if this has been answered before, where the BTD issues in 5 exclusive to those using MOTU interfaces? I haven't bounced to disk from DP yet, and if it's an issue regardless of interface in 5, I'll just revert to 4.61 for a while. Thanks.

danny · Post by **danny** » Tue May 30, 2006 7:32 am

I did one 3 hour session with 5.01 so far, and it was perfectly uneventful (that's good)!

midilance · Post by **midilance** » Tue May 30, 2006 8:17 am

rentadrummer wrote:
tommymandel wrote:I haven't found it in the manual, but just noticed that on pp.790-792, the graphic illustrations of the Masterworks EQ's Filter Types I, II, III and IV, are totally black in mine.
I haven't gotten through the entire manual yet, but when I checked the illustrations on those pages they are almost totally black, just as you said. I found a few other pages where the illustrations were also very dark and wonder if it's that way in all the manuals or some are printed better than others.

Actually, if this printing problem is due to a screw-up at the printing company they should make good to Performer and reprint the manuals.

Jim · Post by **Jim** » Tue May 30, 2006 9:24 am

Shooshie wrote:
Jim wrote:My problem w/5.01 thus far:

CPU meter can be hovering around half when I start a project, but then after working with volume automation only for a while, the CPU meter goes up to around 90%, starts spiking red frequently, and the audio quality degrades (sounds like dropouts).

Closing and re-opening the project fixes this temporarily, as does Quitting and re-launching the application. Then about fifteen minutes later, I have to repeat.

This is on my G4 PB 1Ghz/1GRAM w/Traveler attached, doing a 48/16 project on an OMF import from an Avid Symphony.
Oh great. Sounds like a memory leak. Damn! When is MOTU going to start beta-testing their stuff? Maybe they need to look for NEW beta testers. Their current testers just aren't catching the bugs. MOTU? You listening? Please give it some thought. We paid users really do feel like full-time beta testers. It shouldn't have to be like this. We accept a certain amount of this because we love the software so much, but you could do so much more in the market if you'd just make DP solid again.

Shooshie

This really stinks. I can't get any real work done on 5.01. Good thing that I don't need any of the new DP5 features, because it looks like I'm going to have to go back to 4.61 to be able to utilize DP at all on my PowerBook.

Two steps forward and three steps back. So much for the optimization that was our number #1 feature request.

Dubnick · Post by **Dubnick** » Tue May 30, 2006 9:41 am

This may be obvious, and I'm definately no DP expert (new to DP from PT), but if you have any plugs running, there is an off chance that one of the plugs is causing the memory leaks/cpu spikes. Since PT upgraded to v7, there are a few supposedly PT 7 optimised plugs, including Digi's own Pultec bundle that caused the very same type of cpu spike issues while others were just fine. Shot in the dark and it may be totally obvious, but you might want to make sure you absolutely eliminate the possibility of a plug's interaction with DP5.01 before viewing it as being directly related to DP alone and/or the volume automation.

Tim · Post by **Tim** » Tue May 30, 2006 10:57 am

midilance wrote:
Actually, if this printing problem is due to a screw-up at the printing company they should make good to Performer and reprint the manuals.

Maybe they did make good, with a refund.

Jim · Post by **Jim** » Tue May 30, 2006 5:08 pm

Dubnick wrote:This may be obvious, and I'm definately no DP expert (new to DP from PT), but if you have any plugs running, there is an off chance that one of the plugs is causing the memory leaks/cpu spikes. Since PT upgraded to v7, there are a few supposedly PT 7 optimised plugs, including Digi's own Pultec bundle that caused the very same type of cpu spike issues while others were just fine. Shot in the dark and it may be totally obvious, but you might want to make sure you absolutely eliminate the possibility of a plug's interaction with DP5.01 before viewing it as being directly related to DP alone and/or the volume automation.

Thanks. I'll try to chase this down. Since many others don't seem to be having this problem, it may be Sound Soap... I just got it last week for this job I'm doing, and this was my first DP project with it.

Frodo · Post by **Frodo** » Tue May 30, 2006 7:02 pm

FYI-- in case you haven't seen this:

New Patch for DP 5.01:

MotuTechSupport wrote:If you install the DP 5.01 maintenance update and experience problems accessing DP5's included instruments (such as BassLine, Model12, Modulo, nanosampler, PolySynth, and Proton), run the patcher at the link below, which corrects a few minor Mac OS X permissions issues involving these plug-ins. After you run this patch, you should be able to successfully access all of DP5's included instrument plug-ins.

DP 5.01 instruments patch:
http://downloads.motu.com/dp/dp_5.01_instr.zip

The DP 5.01 update currently posted on the MOTU downloads page has been updated to include this patch.

If you have already downloaded and installed the DP 5.01 update, and are not experiencing issues accessing DP instruments, you do not need to download this patch or reinstall DP 5.01.
_________________
Josh Hetrick
MOTU Tech Support

techsupport@motu.com
http://www.motu.com/techsupport

Shooshie · Post by **Shooshie** » Tue May 30, 2006 7:22 pm

Jim wrote:
Shooshie wrote:
Jim wrote:My problem w/5.01 thus far:

CPU meter can be hovering around half when I start a project, but then after working with volume automation only for a while, the CPU meter goes up to around 90%, starts spiking red frequently, and the audio quality degrades (sounds like dropouts).

Closing and re-opening the project fixes this temporarily, as does Quitting and re-launching the application. Then about fifteen minutes later, I have to repeat.

This is on my G4 PB 1Ghz/1GRAM w/Traveler attached, doing a 48/16 project on an OMF import from an Avid Symphony.
Oh great. Sounds like a memory leak. Damn! When is MOTU going to start beta-testing their stuff? Maybe they need to look for NEW beta testers. Their current testers just aren't catching the bugs. MOTU? You listening? Please give it some thought. We paid users really do feel like full-time beta testers. It shouldn't have to be like this. We accept a certain amount of this because we love the software so much, but you could do so much more in the market if you'd just make DP solid again.

Shooshie

This really stinks. I can't get any real work done on 5.01. Good thing that I don't need any of the new DP5 features, because it looks like I'm going to have to go back to 4.61 to be able to utilize DP at all on my PowerBook.

Two steps forward and three steps back. So much for the optimization that was our number #1 feature request.

Jim, there may be hope. I got a PM from Josh at MOTU about a new patch for 5.01. Apparently there were some installer issues, and it left some permissions hosed. So, they've got a new installer. It might be worth your while to D/L the current installer and run it. I don't know if you have to UN-install DP first, and start with DP5, or not, but I think I'd probably do that. In fact, I'm GOING to do that very soon, having heard more stories. I think everyone is having issues that are resulting from the permissions mess.

Shooshie

Shooshie · Post by **Shooshie** » Tue May 30, 2006 7:23 pm

Never mind... Frodo posted the PM I got. I've been washing dishes and had this thread open for a couple of hours, so I haven't seen the recent posts.

Shooshie