Digital Performer 9.52 released today

[daniel.sneed]

Well... So far, so good!

[mikehalloran]

I finally figured out the cause problem I was having. Although the files I was supplied had .aiff extensions, a Get Info showed that they were AIFF-C. It also explains why exporting them from TwistedWave fixed them. I'm glad to have had a good batch converter as doing them one at a time would have been time consuming with any of the freeware (especially iTunes—yikes!)
https://en.wikipedia.org/wiki/Audio_Int ... ile_Format

My client is not knowledgable enough to have done this and I don't have contact with the studio who did. Live and Learn.

I'll file a Tech Link since they made DP 9.52 exhibit all kinds of weird behavior when 9.51 did not.

[Tobor]

It's good that DP supposedly now recognizes files with both AIFF and aiff cap and non-cap. That one drove me nuts for awhile.

Also encouraging, I upgraded to both High Sierra and DP 9.52 on my MBP yesterday. What has bothered me in 9.5.X is that although pre-gen seems to make DP run more efficiently, when tracking memory hungry VIs I would get spikes and glitches on occasion vs. not having this problem in 9.0.2. Output instruments, for example. Today when playing around with one of these problem instruments in my MBP after the upgrades it was smooth as silk, no processor spikes. Yay.

[stubbsonic]

It's good that DP supposedly now recognizes files with both AIFF and aiff cap and non-cap. That one drove me nuts for awhile.

Yea, it was the same with .WAV vs .wav. I'm glad they fixed that (if they did).

[mikehalloran]

It's good that DP supposedly now recognizes files with both AIFF and aiff cap and non-cap. That one drove me nuts for awhile.

Yea, it was the same with .WAV vs .wav. I'm glad they fixed that (if they did).

How long ago was that still an issue? I don’t remember running into it since the .SD2 vs .sdll days. Perhaps I’ve led a sheltered life.

[bayswater]

How long ago was that still an issue? I don’t remember running into it since the .SD2 vs .sdll days. Perhaps I’ve led a sheltered life.

I think a long time. But for me it was obscured by other audio files would not load for various reasons, and many of those did not load in Logic or QT either. I've opened - saved with DSP-Q and that's generally worked.

[stubbsonic]

I just ran into it because my H2n produces .WAV files, and I had some other devices where all caps were used with filenames. As recent as 9.51, DP won't accept drag & drop from .MP3 or .WAV (but will accept .AIF on my system). If I change the extensions to lower case they drag & drop fine.

[mikehalloran]

I think a long time. But for me it was obscured by other audio files would not load for various reasons, and many of those did not load in Logic or QT either. I've opened - saved with DSP-Q and that's generally worked.

You can make it even simpler by not opening the files. Use the batch processing function to export the files the way you want. I've only done it once in DSP-Q to see that you could as I prefer the workflow in TwistedWave. Anyway, I set the action, drag a group of files in, hit a button and am done.

In TW, I set my action to keep the original location and do not overwrite the original audio. This way, I can drag files from multiple folders into the same window and it puts the new ones into those same folders. It doesn't matter what the source is—FLAC/wav/aif/AAC/mp4 Apple Lossless etc. or all of them. I'm not sitting in front of my Mac at the moment but I think you can do the same in DSP-Q. TW is great and blazingly fast but can't do Red Book.

Back in the DP 4–5 days, I'd have to open them one at a time in QuickTime Pro and export that way. I don't miss that at all.

[James Steele]

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.

[kinnylandrum]

The problem still exists that, if I record only one MIDI track, usually a piano part, and then try to bounce it, it will stop recording the MIDI bounce at some point. It usually happens somewhere in the track from a minute to three minutes in, approximately. If I record any other MIDI part that fills up most of the time of the track, I can then bounce just the first track with the rest muted and it will work. The dummy track has to have more than few notes, for most of the time of the track, and it has to be on a different instrument and/or MIDI channel (I'm not sure which).

But this is a really aggravating problem that has been there since after 9.13 (the last version that worked correctly) and MOTU can't seem to find the answer. Wonder if anyone else has experienced it. It really makes doing piano demos painful. Freezing of course works, but that's time consuming.

[MIDI Life Crisis]

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.

[bayswater]

The problem still exists that, if I record only one MIDI track, usually a piano part, and then try to bounce it, it will stop recording the MIDI bounce at some point. It usually happens somewhere in the track from a minute to three minutes in, approximately. If I record any other MIDI part that fills up most of the time of the track, I can then bounce just the first track with the rest muted and it will work. The dummy track has to have more than few notes, for most of the time of the track, and it has to be on a different instrument and/or MIDI channel (I'm not sure which).

But this is a really aggravating problem that has been there since after 9.13 (the last version that worked correctly) and MOTU can't seem to find the answer. Wonder if anyone else has experienced it. It really makes doing piano demos painful. Freezing of course works, but that's time consuming.

An odd problem but I don't see it here. I realized I've never bounced tracks in a project with one track. So, I started an empty project, drew in 3 minutes of MIDI playing on the Apple DSLMusicDevice and bounced it. It all worked as expected. I assume your sequence length, memory pointers, etc are all as expected?

[kinnylandrum]

An odd problem but I don't see it here. I realized I've never bounced tracks in a project with one track. So, I started an empty project, drew in 3 minutes of MIDI playing on the Apple DSLMusicDevice and bounced it. It all worked as expected. I assume your sequence length, memory pointers, etc are all as expected?

Yes, the bounce is the full length of the track, just blank after the MIDI stops playing (and if the sustain pedal is down, it extends until the sustain stops or the end of the track). I really wish I could figure this out, since if I take the same project and open it in 9.13, it bounces fine.

[bayswater]

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

[FMiguelez]

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.