Digital Performer 9.52 released today

[kinnylandrum]

Did this start with a template? If so, maybe try a template created in 9.5.2.

Interesting idea. I'll try that. You mean I have to create a new template from scratch, not just copy an old one?

[bayswater]

There have been reports of templates becoming corrupt, or templates that had to be rebuilt with updates. I don't know if anyone has confirmed these things completely, but it seems worth try a new template built in 9.5.2.

[MIDI Life Crisis]

That makes sense. If there are added or changed features, then the template could (conceivably) simply not have the right data at the right spot with the correct parameters, yadda yadda yadda....

[toodamnhip]

Downloaded and installed. Opened current large mix file, Dp would only stutter. Terrible audio playback. Did a safe boot restart which cleans things up, tried again, no go. Only audio stutter. Buffers already maxed at 1024 so I even tried 512, no go. To me, 9.52 is a no go. I have to get back to work and have no time to debug. I will watch to see if anyone here similar has issues. I’m back to 8.07 for mixing large files, and 9.51 for MIDI mute work.

TDH... I am sorry you are having problems. I wonder if some of it is your workflow? It seems maybe MOTU needs to optimize automation. As I recall, don't you snapshot EVERY parameter of your plug-ins? And when you automate a parameter you don't just add automation for that one parameter but you sort of "brute force" snapshot ALL parameters of the plug-in, including the parameters that don't change? And this is with most of the plugs in your projects? Not trying to argue with you (I even deleted a rather rude response from a user) but it has seemed to me that your workflow is atypical and places a very large burden on DP with very large amounts of automation data, including much redundant automation data of parameters that aren't changing.

You got it man! And thanks for removing the trolls.
But remember, DP 9.5 was working fine as far as play back. So whats the difference in the latest update that causes me to have insufficient CPU power? Is DP 9.52 more a processor hog? I don’t know. No time to research this. Bummer that I am now cut off from 9.5 on this one large file, but I like 8.07 for its ability to read automation properly. Typical DP stuff-DP improves in some areas, and , depending on ones specific habits, can fall back in other areas. I am not sure Snap shotting all automation is a “brute force” thing. Should work fine for normal plug ins. Now, things like Ozone? Things that have seriously large amounts of parameters, I do not snap shot. By the way. Another thing. I recently flew to Colorado to set up a buddies studio, made another DP user. And I tested my automation issues on a brand spanking new system. New trash can mac, new PC hooked up to VE Pro. A virgin, CLEAN system. All my snap shot complaints occurred exactly as they do in my studio. So this proves to me that users here just plain do NOT snap shot a lot. Then I get attacked for using what should be a feature of DP. So again, thanks for handling the trolls. And this last part about the virgin system, should show clearly I am not some nut doing kooky things DP isn’t supposed to do..lol.

[toodamnhip]

No time to debug, so my suggestions are not going to be helpful, but I'd start by going to only SAFE plugins. Anytime I've had these kinds of issues in the past it has ALWAYS been fixed by eliminating all things WAVES. I see TDH has Waves 9. I would (at the least) disable that and see if it fixes things... when you have the time.

Downloaded and installed. Opened current large mix file, Dp would only stutter. Terrible audio playback. Did a safe boot restart which cleans things up, tried again, no go. Only audio stutter. Buffers already maxed at 1024 so I even tried 512, no go. To me, 9.52 is a no go. I have to get back to work and have no time to debug. I will watch to see if anyone here similar has issues. I’m back to 8.07 for mixing large files, and 9.51 for MIDI mute work.

TDH... I am sorry you are having problems. I wonder if some of it is your workflow? It seems maybe MOTU needs to optimize automation. As I recall, don't you snapshot EVERY parameter of your plug-ins? And when you automate a parameter you don't just add automation for that one parameter but your sort of "brute force" snapshot ALL parameters of the plug-in, including the parameters that don't change? And this is with most of the plugs in your projects? Not trying to argue with you (I even deleted a rather rude response from a user) but it has seemed to me that your workflow is atypical and places a very large burden on DP with very large amounts of automation data, including much redundant automation data of parameters that aren't changing.

I cannot rid my mixes of Waves, there’d be little left lol. Of course DPs proprietary plugs work better. That is meaningless in realty. It may give a clue when doing research, but to me, it would be a useless clue. What could I do about it but mix thereafter with DPs plugs only? Talk about handcuffing myself..lol

[toodamnhip]

Downloaded and installed. Opened current large mix file, Dp would only stutter. Terrible audio playback. Did a safe boot restart which cleans things up, tried again, no go. Only audio stutter. Buffers already maxed at 1024 so I even tried 512, no go. To me, 9.52 is a no go. I have to get back to work and have no time to debug. I will watch to see if anyone here similar has issues. I’m back to 8.07 for mixing large files, and 9.51 for MIDI mute work.

And when you automate a parameter you don't just add automation for that one parameter but you sort of "brute force" snapshot ALL parameters of the plug-in, including the parameters that don't change? And this is with most of the plugs in your projects?

The thing is that, last I checked (at least 3 years ago), there was no easy way to tell DP which parameters you want from a plugin snapshot.

IIRC, the option is there in theory, but in practice it didn't work. So if you want to quickly snapshot full sections of the mixes, i.e., chorus and verses, it's either an all-or-nothing affair. I work like that sometimes, and it's really awesome and quick, especially if you have lots of plugin automation anyway. I think TDH also does this to "lock" all the parameters, even if some are not automated.

I'd be interested in knowing TDH's reason to do that (the all-parameter-locking), just out of sheer curiosity.

Please note that automating by manually recording only the parameters that do change doesn't really work for a workflow like the one above. The cool thing about it is the speed with which the section-automation can be done, and doing it one by one would be un-workable.

I will check if this situation has changed when I get time. Perhaps there's some kind of trick to make DP let you choose groups of parameters as desired, but it had either, a bug, or it didn't really work as expected, if my memory serves me well.

There are many many reasons I “lock a mix”, and they could best be described with video tutorials, which I again, don’t have time for. I cant get into all of them here, but, A couple things-
**I rarely have a plug in that needs only 1 setting throughout an entire song. Thus, I lock everything down, knowing I will makes changes later.
**Each sections plug in sound changes depending on intensity, performance, instrument range etc.
**One of my favorite practices can be found in the tips section, called “rubber banding” a mix. When more and more parts come in throughout a production, things change in many ways. Once plugs are “locked”, you can go in and, in touch mode, (without recording automation), go in and test various changes for that specific section. Things such as lesson-ing the compressors' threshold when a singer sings louder in a chorus, etc. If thing are “locked”, you can confidently pull on settings and hear if things improve or not. Once you like a change, you can then write it permanently. I do have to make a tutorial on this one day. Perhaps it doesn’t quite translate when written on a page. But all in all, no way do I ever just set and forget all my plug ins. The thing is, snap shot is a wonderful feature that begets many work flows that are truly advanced and allow for a Living-Breathing mix. I think James is correct, and speaking with other plug in companies I have heard he same. DP has a long way to go to improve its automation capabilities. It does seem this capability comes and goes throughout iterations of DP. For example, I always end up back in 8.07 once 9.5 starts failing to read automation properly. Once a file gets to a certain point in size or automation maneuvers, 9.5 starts becoming unreliable. You can even bring up plug in windows and watch them change on one pass, and fail to do so on another. Going back to 8.07 ALWAYS handles this for me. But beware, you have to rid your 9.5 files of any muted MIDI or formerly muted notes will play back in 8.07. Which brings me to another DP bug. Crashing when erasing “display only” notes using DPs view filters. Happens a lot, and is unpredictable. If it starts on a particular file, one has to get a bit clever as to how to rid a file of the muted notes. My technique has been to drag the muted notes (display only), to a dummy MIDI file, turn all notes back on, and erase the dummy MIDI file in its entirety. Yikes, the things we do to get work done..

[mikehalloran]

There are certainly some tweaks under the hood in the latest version but I threw all of my normal plugs onto a test file and was fine.

My new project had major issues, however. In my case AIFF-C files were little wonky in 9.51. In 9.52, they went berzerk — but that is what led me to diagnose and fix the real problem. I'd heard of AAIF-C with a .aiff suffix but had never seen one before.

I spoke with the guy who prepared the files today. I'm missing three minutes of the project and my client doesn't know how to tell him what I need. Ok, we figured it out and I asked him how he was creating the files. He's cuing up the tape and feeding it into an old CD recorder — did I want him to do anything else? ... uh ... no, that will be fine... If my guy isn't savvy enough to upload it to Dropbox he can get me the CD.

Analog into a CD recorder?

For kicks, I tried loading one of the original files into Logic. I think it laughed at me. DP rocks!

[Bennie Sims]

DP 9.52 is having a case of stuttering audio for me! I’m going back to 9.51!!! Anyone else having such issues?

[toodamnhip]

DP 9.52 is having a case of stuttering audio for me! I’m going back to 9.51!!! Anyone else having such issues?

Yes, I had the same issue on a large mix. It also screwed up my 9.5 version so I am mixing back on 8.07. I have successfully used 9.52 on a new song that has a lower cpu footprint, but the large mixed could no longer be handled after the “upgrade”.

[mikehalloran]

A number of people have had issues. In every case I’ve noted, there is a real problem but 9.52 is only the symptom. It can be a bad plugin or slightly incompatible audio files etc.

Running in Safe Mode will tell you if it’s a bad plugin but won’t tell you which one. If you have incompatible audio or corrupt headers, Safe Mode will have no effect. In my case, prior experience led me to guess correctly and know how to fix my files — I was lucky.

According to many complaints on he FB page, a 9.52 install makes earlier versions just a bad — happened to me, too. Many of the common files are overwritten in every new install even if you protect the old app by renaming it. I noted an example of this here:
viewtopic.php?f=26&t=64851

If you go back to 9.51 or an earlier version, You want to download it again and reinstall. This may make the earlier version behave.
http://motu.com/download/download_match ... oduct_id=1

in my case, I rolled back my system a few hours to before I installed 9.52 and 9.51 behaved again. I then found the real problem with my audio files, reinstalled 9.52 and things are running great.

[kinnylandrum]

Did this start with a template? If so, maybe try a template created in 9.5.2.

Interesting idea. I'll try that. You mean I have to create a new template from scratch, not just copy an old one?

Well, bayswater, you may have actually solved my problem. I made a new template from scratch in 9.52, copying the layout of my previous default template, and saved it as a new default. Then I copied the MIDI data of a solo piano part that had previously stopped bouncing MIDI after about 30-45 seconds. I then bounced that in the new template project and, lo and behold, it bounced the MIDI piano part complete!

Since this bouncing problem has been a little intermittent, though fairly consist with any single track MIDI bounce, I'll just have to see if it solves all previous problems going forward. But again, I thank you for pointing out what is probably a solution that was not at all obvious to me or anyone at MOTU.

Thanks,
Kinny Landrum

[Tobor]

Did this start with a template? If so, maybe try a template created in 9.5.2.

Interesting idea. I'll try that. You mean I have to create a new template from scratch, not just copy an old one?

Well, bayswater, you may have actually solved my problem. I made a new template from scratch in 9.52, copying the layout of my previous default template, and saved it as a new default. Then I copied the MIDI data of a solo piano part that had previously stopped bouncing MIDI after about 30-45 seconds. I then bounced that in the new template project and, lo and behold, it bounced the MIDI piano part complete!

Since this bouncing problem has been a little intermittent, though fairly consist with any single track MIDI bounce, I'll just have to see if it solves all previous problems going forward. But again, I thank you for pointing out what is probably a solution that was not at all obvious to me or anyone at MOTU.

Thanks,
Kinny Landrum

This could be timely, as I've had a couple mysterious crashes in 9.52. I remember having trouble in a couple previous incarnations of DP (7 going to 8?) that was very similar, and just creating a new scratch template solved the problems and made things run more smoothly. Sometimes you can have a prior version (or location) of a plug referenced that trips the breaker, etc.

So thanks from me for the reminder as well!

[bayswater]

This could be timely, as I've had a couple mysterious crashes in 9.52. I remember having trouble in a couple previous incarnations of DP (7 going to 8?) that was very similar, and just creating a new scratch template solved the problems and made things run more smoothly. Sometimes you can have a prior version (or location) of a plug referenced that trips the breaker, etc.

So thanks from me for the reminder as well!

I wonder this would work in some instances, rather than recreating your template from scratch.

1. Open your old template, rather than an old project.
2. Save immediately as a new empty project.
3. Quit.
4. Start up again, load the project in Step 2 and save as a template.

[Phil O]

I wonder this would work in some instances, rather than recreating your template from scratch.

1. Open your old template, rather than an old project.
2. Save immediately as a new empty project.
3. Quit.
4. Start up again, load the project in Step 2 and save as a template.

I do recall having the "old" template issue in a previous update of DP (I don't remember which version). I think I tried your method and it didn't do the job. I had to re-create all my templates. However, I haven't had this issue with 9.52, so I can't advise with confidence on this update. Just a heads up.

Phil

[Klaus]

Will a DP 9.52 installation make DP 7.24 unusable ?
TIA
and best regards

Klaus