MOTUnation.com

Yep, sorry to say 7.2 is buggy.

I can't open old projects on my desktop. New projects seem fine.

My laptop won't even open 7.2 and crashes on start-up - until I trash the au prefs each time I want to open it.

Happy to say 7.12 opens everything (even 7.2 files) and works almost perfect. With the exception of being able to rebuild the busses. Bundles still not working right for me.

Anyhow, whatever 7.2 can't open - 7.12 will - even older (supposedly) corrupted files I had been unable to open for years. (Yay!)

7.2 looks fantastic though.

Can't wait till 7.22

Keep up the good work MOTU!

7.2 is buggy? Not here FWIW.

I've had a bit of weirdness with bundles as well when using VE Pro. But I guess I don't run into it so often that it drives me crazy, and it's easy enough for me to fix. I love the new themes, and I've had a much more stable experience with it, moreso than 6.03, which served me quite well, but 7.2 is pretty darn phenomenal.

miditime wrote:Yep, sorry to say 7.2 is buggy.

I can't open old projects on my desktop. New projects seem fine.

My laptop won't even open 7.2 and crashes on start-up - until I trash the au prefs each time I want to open it…

[…]

...Keep up the good work MOTU!

Miditime, while I've got nothing personal against you whatsoever, I've just noticed that you have a lot of technical problems. Looking at your list of posts, the problems you report made my head hurt by the time I got as far back as 2008, so I didn't go any further. That's understandable in some cases; some people have gotten bad hardware, or software corruption, or just bad luck, and their cases make them appear to be singled-out by MOTU or Apple, or whomever. But I have a question for you:

Do you ever get things running smoothly?

I've had problems too, along the way. Things don't always "just work" here, but most of the time I'm able to work smoothly without interruption, corruption, or disruption. I hate saying it sometimes, but "things just work." So, I'm really wondering what's happening to cause you and certain others so much trouble. I've done a lot of research into these problems in the past, but I can't devote myself to it fully now. I'm just curious to see if there are any immediate similarities. Could you post your system/software/hardware setup so we can see what's at work? That still won't necessarily pinpoint any problems, but it may help us see patterns in those reported.

Again, I'm not trying to single you out or embarrass you or anything. I'm just astounded that you seem to have had so much trouble and so little success with DP. Or is it just that you post when something happens, and not when things are running smoothly? (which is also ok) I haven't had but maybe one or two crashes since DP 7.0 came out, and I could understand what caused those (but I don't remember what it was now). That was back in DP 7.01, I think. Anyway, I have had no crashes in DP 7.2, and everything is working. Even things that I gave up on long ago (Tap Tempo, for example) seem to be fixed in DP 7.2.

I wish you the best in finding a solution to your problems. It's no fun to work when things keep happening that make it impossible to get to the goal. But if you get the chance, let us see what you're using. Technically, this should be in the other forum, but I don't plan to hijack the thread; I just want to see your system specs. Then we can talk about it in another thread if it appears there's something to say.

Shooshie

miditime wrote:Yep, sorry to say 7.2 is buggy.

I can't open old projects on my desktop. New projects seem fine.

My laptop won't even open 7.2 and crashes on start-up - until I trash the au prefs each time I want to open it.


Keep up the good work MOTU!

Sounds like you have some unique issues with your hardware and DP7.2.
What are your system specs?
People here are usually eager to help solve problems like this.

FWIW, I'm finding DP7.2 to be the most solid version yet.
Not buggy here.

going well here too!

only crash I can get ( and its replicatable on my main rig ) is changing frame rates from 25 to 24.. ( must send those LOG's in )

I've had the same session open for 4 days on my laptop - it even travelled with me from Amsterdam back to the UK.. just opened the Laptop up and carried on working,,,

it might not be recommended behaviour - but I think it illustrates where 7.2 is at for me..

it does how ever occasionally lose waveform preiviews - which takes an ice age or so it seems when recalculating - time to get coffee when that happens..

Funny thing: if you want a list of problems, some real and some imagined, just post "DP is working better than ever!" Immediately you'll see a LOT of posts saying, basically, "no, it's not." I guess that's the opposite effect to posting "DP is falling apart!" and getting a page or two of "works for me! Maybe it's your system." Doesn't seem possible, however, to keep the two opinions separated. One almost generates the other. I'm not knocking legitimate problem reports, btw. I'm just not sure I understand the process that causes people -- myself included -- to have to state the backlash reaction.

In almost every version of DP I have been able to report "works great for me," no matter what I was working on. Only in a few versions have I had to tread carefully and save after every move. But for the record, DP 7.2 is working very well for me. I'm really enjoying the new features as well as the bug fixes for old ones. Yep, as far as I can tell it's all working great!

Shoosh

I've had ongoing "hanging quit" problems with DP since 6, most of which (if not all) can be attributed to the way DP interacts with my audio interface. Sometimes, after pulling a Force Quit, I am unable to get DP open again without constant crashing. So ... I came upon an old-school solution from the days of Classic: I trashed the "MOTU Audio Systems Prefs" and "Preferences" files from my User>Library>Preferences>Digital Performer™ folder, fired up DP, opened a New File and set up my Preferences the way I wanted. Then, I went back to the User>Library>Preferences>Digital Performer™ folder, made duplicates of those fresh new "MOTU Audio Systems Prefs" and "Preference" files and squirreled them away in my DP 7 Documents in their own sub-folder. Now, any time I have difficulties opening DP, I just duplicate those uncorrupted pref files and use those duplicates to replace the ones in my User>Library>Preferences>Digital Performer™ folder. It does the trick for me.

I'm actually pretty happy with 7 and with 7.2 in particular. I feel like MOTU dropped the ball in a major way with 6, but it's heartening that they're putting this much effort into 7, and I really dig the GUI changes in 7.2 (the black/blue transport readout makes a huge difference). Possibly the only thing I could suggest for DP 8 or a future 7 update is that they somehow come up with a way to allow you to draw in precise ramps for automation ala Vision DSP, since I'm a control freak and I like that caliber of precise control over automation, but that's a personal preference.

Armageddon wrote:I'm actually pretty happy with 7 and with 7.2 in particular. I feel like MOTU dropped the ball in a major way with 6,

MOTU had to update DP, and they did it in the best way they could. They're still tweaking the massive change that took place in the GUI of DP6, but basically you're still using version 6; just with Themes, Shortcuts Window, and a lot of internal changes (and some big features, too) There's no way you can say they "dropped the ball in a major way with 6," because it was a leap forward in nearly every facet of the app. It paved the way for 64 bit. It dealt with design conflicts that made Consolidated Windows inefficient, while giving single-window mode more vertical space. [there's a discussion about that in the AmpGUI thread] It put the user in control of how they view information about tracks, and made it possible to control tracks and transport from every edit window. There are so many advantages that it would take pages to write them all. DP6 was NOT a dropped ball. The GUI was just too white for most of us, and Themes finally officially solved that. Once you get accustomed to where they relocated the buttons (a necessity due to the design conflicts of old and new directions) the new GUI got very efficient.

The only ball that was dropped was stability, briefly. By version 6.02 things were very stable for most people. Now they're probably the most stable they've ever been, including the old Classic days.

Armageddon wrote:but it's heartening that they're putting this much effort into 7, and I really dig the GUI changes in 7.2 (the black/blue transport readout makes a huge difference). Possibly the only thing I could suggest for DP 8 or a future 7 update is that they somehow come up with a way to allow you to draw in precise ramps for automation ala Vision DSP, since I'm a control freak and I like that caliber of precise control over automation, but that's a personal preference.

What kind of automation are you talking about that doesn't allow for precise ramps? Are you familiar with the drawing tools?

I don't mean to be on your case in this post; I just really get the feeling we're in separate realities. DP 6 contained the massive improvements that were needed to move us toward the future of DP, and all automation I know of allows for precise control through drawing tools, change-data menus, or just dragging control points, depending on what you need.

Shooshie

Shooshie wrote:MOTU had to update DP, and they did it in the best way they could. They're still tweaking the massive change that took place in the GUI of DP6, but basically you're still using version 6; just with Themes, Shortcuts Window, and a lot of internal changes (and some big features, too) There's no way you can say they "dropped the ball in a major way with 6," because it was a leap forward in nearly every facet of the app. It paved the way for 64 bit. It dealt with design conflicts that made Consolidated Windows inefficient, while giving single-window mode more vertical space. [there's a discussion about that in the AmpGUI thread] It put the user in control of how they view information about tracks, and made it possible to control tracks and transport from every edit window. There are so many advantages that it would take pages to write them all. DP6 was NOT a dropped ball. The GUI was just too white for most of us, and Themes finally officially solved that. Once you get accustomed to where they relocated the buttons (a necessity due to the design conflicts of old and new directions) the new GUI got very efficient.

The only ball that was dropped was stability, briefly. By version 6.02 things were very stable for most people. Now they're probably the most stable they've ever been, including the old Classic days.

As I'm sure you remember from months and months of bellyaching from the gang, 6 didn't work out well for some people. I'll warrant that it put a lot of innovations on the table and paved the way for what we have now, but, as far as I'm concerned, it was a transitional version. I'll also agree that 6.03 worked out quite a few of the kinks, but, by then, most users were already moving on to 7.x. If I made it sound like DP 6 was unusable, I apologize -- it worked for me with a few caveats and workarounds, but I think MOTU put most of its refinements (especially with pre-rendering) into 7, which I have zero complaints with so far.

Shooshie wrote:What kind of automation are you talking about that doesn't allow for precise ramps? Are you familiar with the drawing tools?

I don't mean to be on your case in this post; I just really get the feeling we're in separate realities. DP 6 contained the massive improvements that were needed to move us toward the future of DP, and all automation I know of allows for precise control through drawing tools, change-data menus, or just dragging control points, depending on what you need.

Shooshie

That one was really more of a suggestion, and one I think we've discussed here before. In Vision DSP, there's an "Exact" button you can switch on. Once this button is on, when you use your drawing tool to draw an automation ramp, a box pops up, in which you can type in the exact bar/beat/time you want the ramp to start and to end, what kind of ramp (parabola, straight, inverse, etc.) and what your start and end value will be, which Vision then generates to your precise specs. While I think you can do this in DP with MIDI data, I don't think you can do so with audio automation -- you have to draw it in and, for me, it's not always precise, even if you zoom all the way in with the Graphic Editor. I've also tried using a combo of drawing in the Graphic Editor, then trying to refine it in the Event Editor, which works out slightly better. I realize that most people don't need that level of precision, and even more people just prefer to do it via a HUI fader like a real mixing board, so such a suggestion would likely be a waste. It's just something I'd like to see.

A couple of times I had a freeze on quit problem in DP7.2 but I think it is my fault, I was in a hurry both times. What i did was to save my project then quit DP and shut down the computer; I think I did this to fast and perhaps DP was not done saving so it hung up or some thing. It did save the project fine. All I had to do was to force quit and that is no big deal. Other than that so far I am impressed at how well it is working.

Armageddon wrote:That one was really more of a suggestion, and one I think we've discussed here before. In Vision DSP, there's an "Exact" button you can switch on. Once this button is on, when you use your drawing tool to draw an automation ramp, a box pops up, in which you can type in the exact bar/beat/time you want the ramp to start and to end, what kind of ramp (parabola, straight, inverse, etc.) and what your start and end value will be, which Vision then generates to your precise specs. While I think you can do this in DP with MIDI data, I don't think you can do so with audio automation -- you have to draw it in and, for me, it's not always precise, even if you zoom all the way in with the Graphic Editor. I've also tried using a combo of drawing in the Graphic Editor, then trying to refine it in the Event Editor, which works out slightly better. I realize that most people don't need that level of precision, and even more people just prefer to do it via a HUI fader like a real mixing board, so such a suggestion would likely be a waste. It's just something I'd like to see.

Not sure exactly what you want. You can use Create Continuous Data, set for Audio Volume, Audio Pan, or any other continuous controller to create any set of points you want. The one below shows a curve starting and ending at the selection range, starting at -12dB and going to 00dB with points every 3 tics, and with a curve of +50. (as shown in the picture)


Or you can use the drawing tools to do pretty much the same thing, but without the exact accuracy of the dialog box:




I honestly don't know if these will do what you want or not, but I cannot imagine something that works any better. You can assign a command to the Create Continuous Data dialog so that it pops up easily when you need it. I guess you still have to type in the range of data that you want, but if you're asking for that level of precision, it can't exactly read your mind.

Does any of this work for you?

Shooshie

Shooshie wrote:I honestly don't know if these will do what you want or not, but I cannot imagine something that works any better. You can assign a command to the Create Continuous Data dialog so that it pops up easily when you need it. I guess you still have to type in the range of data that you want, but if you're asking for that level of precision, it can't exactly read your mind.

To be honest, I'd either completely blanked out on the "Create Continuous Data" window or I've just flat-out never used it -- I've always just tried drawing it in and hoping for the best. But that is more or less exactly what I was talking about, so I guess that about wraps it up for my DP suggestions. This is what happens when I attempt to figure everything out through trial and error, rather than actually finding out how to do things from the user's manual ... durrrrrrrrrrrrrr ...

My other dilemma with DP, how it interacts with my audio interface, is still ongoing. I'm going back and forth with a tech at TC Electronic who insists the Konnekt 24D works fine with DP 7.2/10.6.4 on his similar test MacBook Pro, and I was even given a link to the new Beta of the TC NEAR software (http://www.tcelectronic.com/files/Suppo ... 85_353.dmg -- Mac-only), but I suspect the only workable resolution is to simply get a different interface, which is a shame, because the Konnekt is rock-solid with everything else, and even works well with DP most of the time, unless I'm trying to open or close the program. Considering it's behaved the same through 2 different operating systems, 2 different versions of DP and two different hard drives of varying size and speed, I have to assume it's not gonna get fixed, or there's something on my machine it just doesn't like.

By the way, Shoosh, that's a really wild color scheme you have set up for DP there. I was tempted to tinker around with the new colors myself, but I think I'm used to the default white color arrangement they've had since 6.x, and, to be honest, the new transport display in 7.2 (black and blue) is pretty damn awesome.

Armageddon wrote:By the way, Shoosh, that's a really wild color scheme you have set up for DP there. I was tempted to tinker around with the new colors myself, but I think I'm used to the default white color arrangement they've had since 6.x, and, to be honest, the new transport display in 7.2 (black and blue) is pretty damn awesome.

It´s the AmpGUI Oxidized Theme.
Check the DP AmpGUI Themes out at http://www.ampguimods.com/page7/page7.html