Page 4 of 5

Re: Fixed/Not fixed/Broken in DP 7.1

Posted: Sun Jan 24, 2010 9:53 pm
by Grigri
@ songsmith, may I ask a few question?

Have you the pre-fill buffer uncheck in the studio settings? When it's on, there is a big load on the CPU when the project is stopped...

And can I ask you how many tracks is the project, what sample rate and what buffer size?

Have you try to activate only the DP plugins?

Thanks

David

Re: Fixed/Not fixed/Broken in DP 7.1

Posted: Sun Jan 24, 2010 9:57 pm
by sdfalk
Shooshie wrote:Good luck with the other DAW.
I'll second that good luck..
I've done some pretty extensive testing with it at my place of employment with plenty
of plugins, (stock and others) and under large track counts, plenty of crashes.
If you've run the demo and had it functioning properly, then fine.
I'm just saying be careful.

Re: Fixed/Not fixed/Broken in DP 7.1

Posted: Mon Jan 25, 2010 6:07 am
by audios
Phil O wrote:
audios wrote:The only way i find out if DP has an update is through this forum.
DP 7.1 has automatic update checking. It's under the Help menu.

Phil

Always had that option checked. This version (7.1) is the first time I have seen that option available in "HELP" Hope it works. Not in any previous versions. Guess someone was listening at MOTU

Re: Fixed/Not fixed/Broken in DP 7.1

Posted: Mon Jan 25, 2010 8:09 am
by Phil O
songsmith wrote:Guys and gals, I don't know what is going on with DP.
I can't say what the problem is, but I can say that I'm not seeing this in activity monitor. I just opened a project to see if I get the same results and Activity monitor reports DP 7.1 at around 4% while idle for this project. It jumps up to about 30% while playing. I wouldn't be too eager to jump ship before doing some more troubleshooting. It could end up being something simple.

Phil

Re: Fixed/Not fixed/Broken in DP 7.1

Posted: Mon Jan 25, 2010 9:01 am
by songsmith
Grigri wrote:Have you the pre-fill buffer uncheck in the studio settings? When it's on, there is a big load on the CPU when the project is stopped...

And can I ask you how many tracks is the project, what sample rate and what buffer size?

Have you try to activate only the DP plugins?
This screenshot will show you my settings and the number of tracks.
Image

It appears that pre-fill buffer is on (the default choice, I assume). It looks like I'm running about 20 tracks. My session is 24-bit, 44.1 kHz. As I've mentioned in my posts, I've run my tests with only MOTU plug-ins and also with no plug-ins enabled. Most of the recent tests were with no plug-ins.

Now that you've pointed out the pre-fill buffer, I think I see what the bug is probably doing... It's just a guess, of course, but my theory is that DP did something to one of the files on import that causes the pre-fill buffer to loop. That would explain the CPU overload. Hope that helps.

By the way, are you the Magic Dave that just asked for my crash logs? Note that I've had an unread MOTU Tech Link out since 1/6 and a variety of posts about crashes in this forum for more than a week. Lots of other users are posting their crash logs and trying to make sense of them. I'm glad to hear from someone from MOTU, and of course I think MOTU is very late in responding to me. I've lost many hours to this troubleshooting that could have been helped by MOTU tech support earlier on.

Re: Fixed/Not fixed/Broken in DP 7.1

Posted: Mon Jan 25, 2010 9:49 am
by Phil O
When I originally posted this, it was my intent to generate a list of things found to be fixed or not (I was hoping the fixed would outweigh the not):
Phil O wrote:Thought I'd start a thread where we could list things that we have found to be fixed, not yet fixed, or broken in this version.
If something is reported as such and you can confirm or invalidate the report, that would be helpful. If we could keep opinion, rants, and suggestions in another thread, that would also be helpful.

Thanks,
Phil

BTW, I was hoping someone could confirm this:
Phil O wrote:[fixed] It seems the problem of preferences not remembering file formats has been fixed. I don't know if that was a 7 fix or a 7.1 fix as I went directly from 6.03 to 7.1.

Re: Fixed/Not fixed/Broken in DP 7.1

Posted: Mon Jan 25, 2010 9:54 am
by Grigri
Sorry Phil... you're right, it's not the right thread for fixing problem... :)

Songsmith, maybe you could start a new topic with your issue and find the solution?

BTW, I'm not magic Dave from Motu, just a longtime DP user and fan.

David

Re: Fixed/Not fixed/Broken in DP 7.1

Posted: Mon Jan 25, 2010 9:59 am
by Phil O
Grigri wrote:Sorry Phil... you're right, it's not the right thread for fixing problem... :)
That wasn't directed at anyone in particular. No apology necessary. I just wanted to avoid the rantfests that some topics have evolved into regarding DP 7.1. Also, James has started a new forum for DP troubleshooting. It should make things easier to sort through.8)

Phil

Re: Fixed/Not fixed/Broken in DP 7.1

Posted: Mon Jan 25, 2010 10:59 am
by zed
FIXED, FIXED and FIXED!

• MIDI graphic editor now remembers the selected tracks when you exit the editor and then come back to it. First time this has worked in all my years of using DP since version 4.5. You also have a preference to determine whether double-clicking on tracks in the Tracks overview adds that track to your MIDI graphic editor or if it soloed.

• You can now cut and paste tracks which include closed folders. There is no error message telling you of an incorrect track count anymore. It will paste the contents of what you copied wherever you paste it, including the contents of the closed folders. If you don't want to copy stuff from the closed folders, you just deselect the closed folder before you copy.

• Channel Strip size is now remembered by window sets. In previous versions it would open the window too small and you would manually have to expand the window to show all the channel strip items.

:-) :-) :-)

Re: Fixed/Not fixed/Broken in DP 7.1

Posted: Mon Jan 25, 2010 11:11 am
by zed
A couple more important FIXES...

• Selection of loops in the Tracks Overview now works as expected!!! Before, selecting bars in front of an audio loop would select and move a loop in a bar which you did not intend to move, and would NOT select the loop when you selected the loop contents unless you selected a little bit of the previous bar. This is all fixed now, and loops are selected in the bars they exist in. Thank momma!

• Last Preference window now remembered. I was doing a lot of troubleshooting using the Audio Plug-ins preference window, and every time I opened it the window would default to something else. With DP 7.1, it remembers that I was last in Audio Plug-ins and opens that window.

It seems that lots of minor annoyances have been addressed and fixed in this version. Bravo MOTU!

Re: Fixed/Not fixed/Broken in DP 7.1

Posted: Mon Jan 25, 2010 4:54 pm
by zed
Oh oh. I found something broken.

Copying tracks from clippings into a sequence introduces the word "copy" to the track. It took us years of begging to get this fixed, and it finally got repaired. But it's broken again, unfortunately. Hopefully not for too long.

Re: Fixed/Not fixed/Broken in DP 7.1

Posted: Wed Jan 27, 2010 11:43 am
by zed
This thread must have gotten lost somehow, because I am the last three posters and that was a couple of days ago. Has everyone stopped working with 7.1 except me?

Just did an interesting selection of tracks and movement of the data which suggests to me that SMART SELECTIONS have been improved further (probably connected to the proper selection of loops mentioned above).

It's getting easier to edit in DP. I like it. :-)

Re: Fixed/Not fixed/Broken in DP 7.1

Posted: Wed Jan 27, 2010 1:04 pm
by jandron
I tried 7.1 and went back to 7.02. It crashed on me every time I tried to save a project.

Re: Fixed/Not fixed/Broken in DP 7.1

Posted: Wed Jan 27, 2010 1:05 pm
by zed
jandron wrote:I tried 7.1 and went back to 7.02. It crashed on me every time I tried to save a project.
Yikes. That's not good. Sorry to hear that. :-(

Re: Fixed/Not fixed/Broken in DP 7.1

Posted: Wed Jan 27, 2010 9:16 pm
by Phil O
They've changed the way "zoom all the way out horizontally" works. It used to zoom WAY out. Now it zooms out to a level that makes the entire sequence just fill the screen. I think I like it a lot better this way. :)

I'll call this a [FIXED].

Phil