Digital Performer 11.33 version

[corbo-billy]

https://motu.com/en-us/download/product ... =true#2021

Enhancements and optimizations
• Improved OMF/AAF compatibility with more recent files, and fixed some import issues on Windows.
• Improved error handling when importing OMF/AAF files containing incompatible audio formats.

Fixes
• Updated Japanese localizations.
• Fixed a bug that could result in UI and efficiency issues in certain VST and AU plugins.
• Fixed a bug causing VST3 factory presets not to read correctly on Mac.
• Fixed a potential crash in certain VST3 plugins (such as u-he).
• Fixed a bug that could result in stuck notes when scrubbing MIDI in audible mode.
• Fixed a crash that could occur when DP is opened on Mac with a multi-stream audio interface selected while voice isolation mode is on, or when changing to a multi-stream audio interface with voice isolation mode on.
• Changed MPE translation so that control and pitch bend messages sent on the basic channel don't get converted into per-note messages.
• Fixed a bug where inserting continuous data would skip the first value.
• Fixed a bug on Windows that could result in sound files being incorrectly reported as missing when reopening a file that is set to use deinterleaved soundbites.
• Fixed a crash that could occur when bouncing ARA audio to disk.
• Fixed a hang that could occur on Mac if a user quits the program using the menu bar while the splash screen is open.
• Fixed a number of visual glitches related to accelerated meter and counter pane drawing on Mac, which could occur when changing UI scaling or moving between Retina and non-Retina displays.
• Partially mitigated a visual glitch that could occur when running on macOS 10.13.
• Fixed a crash that could occur in Nanosampler when changing out the sample during playback.
• Fixed a bug that could result in erratic behaviors with Kontakt direct connection on Kontrol MK3 devices after newly adding a Kontakt track.
• Fixed a bug where the piano roll in the Sequence Editor could jump to a different vertical location when starting to drag a note.
• Fixed a bug causing the counter pane not to update when the theme changes.

This new version does not overwrite version 11.32 _

[Michael Canavan]

Looks like the kind of short list that you would get when a new version is imminent. Though the amount of plugin fixes are all pretty extensive, and probably weren't easy. Hopefully it solves some issues I've had with AU/VSTs.

[mikehalloran]

So far, so good.

[James Steele]

Meh.... hardware insert plugin and EUCON support still blows compared to all other Mac DAWs. I'm beyond mincing words about it these days. I wish I'd known those capabilities are seriously deficient in the DAW I've been using for decades before buying a used Avid S3 and analog outboard hardware.

Good to see the've tweaked OMF/AAF compatibility as I have a feeling I'll be exploring the export functions in the coming months.

[monkey man]

Good to see the've tweaked OMF/AAF compatibility as I have a feeling I'll be exploring the export functions in the coming months.

I see what you did there Jimbo.

Of course, I've been aware of your tearing your hair out asking for this brother. C'mon MOTU.

[James Steele]

Good to see the've tweaked OMF/AAF compatibility as I have a feeling I'll be exploring the export functions in the coming months.

I see what you did there Jimbo.

Of course, I've been aware of your tearing your hair out asking for this brother. C'mon MOTU.

I think basically they have a whole lot on their plate and had to make some tough decisions about what to prioritize. Unfortunately for me, I'm guessing there are not a lot of DP users that are using Avid EUCON control surfaces. I partially base that on how bad EUCON support was when I first got my S3 and started writing to MOTU about all the issues I discovered almost immediately. To their credit, they worked with me to fix a lot of these things, but at some point, they understandably had to move to other things. The job was never finished IMHO.

Likewise the hardware insert plugin is a mess. If I have a project containing them, every time I reopen the project, I need to open each instance one at a time, and re-enter the sample offset. Otherwise tracks that have a hardware insert plugin on them will play LATE... audibly LATE! (I went so far as to create a Keyboard Maestro macro that does this for me.) This appears to be because of a strange interaction between the combined latency of the plugins on the Master Fader and the hardware insert plugin. In fact, the first time you use the button to "ping" the external hardware to get a sample offset, you will often get a wildly incorrect number the first time. This number can be thousands of samples... coincidentally often about the same as the latency on the plugs on the Master Fader.

I, of course, have reported all of this stuff to MOTU until I resemble Papa Smurf. (That means "till I'm blue in the face" for those of you how aren't familiar with the childrens' cartoon.) I don't have time for a crash course in computer programming, so that's the best I can do. I have absolutely zero idea when these issues will be addressed (it could be months or years) so I'm faced with a choice. Do I work around these annoying issues for some undeterminable open-ended period of time (again... months? years? a decade?)? Will I even live to see them fixed? Or do I sit down and start learning my way around another DAW (pick one: Cubase, Pro Tools, Logic) where this stuff "just works." Pro Tools is probably a top contender given the sort of music I do.

This is not something I mention lightly. I've been a staunch proponent and evangelizer for MOTU and DP for decades... and well... I started UnicorNation in the early 90s which later became MOTUnation. But to borrow from the Righteous Brothers, I'm starting to lose that loving feeling. Seems like that's something MOTU might care about, but what do I know? There are now Facebook groups that are busier than this board. They may not need me or this board anymore. There comes a point where you want to work they way you want to work, and you can't be hindered by blind loyalty to a company or a piece of software.

[James Steele]

This new version does not overwrite version 11.32 _

I'd be cautious about this last part. I just downloaded and ran the installer and it was installed as "Digital Performer.app" with no version number appended, etc. Might be a good idea to add the version number to the filename of the previous version (if you want to keep it) before running the new installer.

I could be wrong, but might be good just to be on the safe side.

[Michael Canavan]

This new version does not overwrite version 11.32 _

I'd be cautious about this last part. I just downloaded and ran the installer and it was installed as "Digital Performer.app" with no version number appended, etc. Might be a good idea to add the version number to the filename of the previous version (if you want to keep it) before running the new installer.

I could be wrong, but might be good just to be on the safe side.

They have some neat code with their installer on Mac OS at least that appends 11.2 onto the old version, that way for instance your docked DP icon doesn't need to be updated when an update comes out. Basically the latest version always does not include the version number, and that is appended to the last version, upon installing the latest.

[HCMarkus]

There comes a point where you want to work they way you want to work, and you can't be hindered by blind loyalty to a company or a piece of software.

Absolutely! But, for me, the problem is not blind loyalty to DP... I'm "hindered" by the fact I work faster and better in DP than any other DAW! I've had to work in Logic here and there of late. SO frustrating to be hobbled by unfamiliar tools. Logic is great, or so my son assures me, but it's not the software I know. And at this point in my career, I'd rather spend my time doing music (and getting paid for the work) than trying to grok the language and conventions of new software.

Looking forward to lunch Friday and further discourse. I should have 11.33 installed by then.

Thanks for keeping the lights on here at MOTUNation!

[James Steele]

This new version does not overwrite version 11.32 _

I'd be cautious about this last part. I just downloaded and ran the installer and it was installed as "Digital Performer.app" with no version number appended, etc. Might be a good idea to add the version number to the filename of the previous version (if you want to keep it) before running the new installer.

I could be wrong, but might be good just to be on the safe side.

They have some neat code with their installer on Mac OS at least that appends 11.2 onto the old version, that way for instance your docked DP icon doesn't need to be updated when an update comes out. Basically the latest version always does not include the version number, and that is appended to the last version, upon installing the latest.

Ahhh... I suspected this might be the case but didn't test it. Out of habit, I had already named the older version "Digital Performer 11.32.app"

[James Steele]

There comes a point where you want to work they way you want to work, and you can't be hindered by blind loyalty to a company or a piece of software.

Absolutely! But, for me, the problem is not blind loyalty to DP... I'm "hindered" by the fact I work faster and better in DP than any other DAW! I've had to work in Logic here and there of late. SO frustrating to be hobbled by unfamiliar tools. Logic is great, or so my son assures me, but it's not the software I know. And at this point in my career, I'd rather spend my time doing music (and getting paid for the work) than trying to grok the language and conventions of new software.

That's all well and good in your situation. I understand. I'm really not under the same kind of deadlines and the problem is that I think I would really like to alter my working style to take advantage of my control surfaces because I do think it would make me more efficient, but I will never know because I'm unable to even FIND OUT with DP.

I also don't like futzing around with hardware inserts and having to reset the sample offset every time I open a project. Or if I reassign a MIDI track to a VI. Or if I move the hardware insert plugin from Insert A to Insert B it loses the connection to my interface and I have to open the plugin, assign both the input and output to something else, then assign them back. This is just plain broken.

So here's where I'm at, and I'm just being honest. PT is similar enough to DP, and I'm not recording other people, so I'm seriously considering taking a couple of steps back for a while with the learning curve so that I can use the tools that I want to use!

Because it will be nice to...

• just load a project and not have to do a workaround before it will play properly.

• to look at an insert and be able to see "WA-2A" or "76F" and not "Hardware Ins..." which tells me nothing.

• to actually assign a plugin to an insert with my S3 because DP has no hierarchy and thus requires me to page through 1,000+ plugins 16 at a time.

• to be able to have custom parameter maps that actually work which would let me designate which plug in parameters appear on the encoders EVERY TIME I edit that plugin. This works in PT, Cubase, Logic... but broken in DP.

[Note: I have reported every one of these issues above to MOTU months ago... multiple times... ad nauseum.]

I've said here before that if someone approached me who had EUCON control surfaces and analog outboard and asked me if I recommended DP, there's no way in good conscience I could say yes.

Anyway... it's appearing that it's nothing personal, but just that MOTU's priorities and mine are beginning to diverge. It may just be that if I want to work in a way that DP won't let me, I need to investigate my options. Yes, the lack of a truly seamless interchange format between DAWs can sort of keep us "hostage" to a DAW. We may have hundreds of projects in a particular DAW and so changing is daunting. "What are you going to do? Learn a new DAW?" But then again there are a crap ton of YouTube videos and tutorials online for just about every DAW out there except... can you guess?

But I'm realizing that the features that are important to me aren't necessarily important to MOTU. So yeah... I might be willing to bear down for a few months and develop some facility with Pro Tools as a hedge while I wait for MOTU to fix some of these things. And there's no guarantee that they ever will. I don't necessarily like sending Avid $199 once-a-year, but then again, I'd send MOTU $199 a year if they would fix some of these long standing issues.

Yeah... sorry guys... but I guess this is my "season of discontent" with DP. I never been more unhappy about DP than I have been lately.

Looking forward to lunch Friday and further discourse. I should have 11.33 installed by then.

Thanks for keeping the lights on here at MOTUNation!

Hopefully, DP 11.33 will have some fixes that benefit you. It holds nothing I'm interested in unfortunately. I can only hope MOTU is holding back major fixes for a DP 12. If that's the case and the hardware insert plugin is improved and I can start to use my S3 to its potential (yes, the S3 is being phased out but these issues also affect current hardware like the S1) I will withdraw my complaints and once again sing MOTU's praises.

[mhschmieder]

I won't have a chance to test a specific listed bugfix until this weekend or early next week, but I am hoping that the issue with initial CC being ignored will take care of a glitch that I thought was internal to Vienna Organ Player, for patch switching.

[HCMarkus]

Hopefully, DP 11.33 will have some fixes that benefit you.

From the list of fixes, sounds like, and I'm hoping, it fixes the Waves plugin graphics bug. Not a huge issue as there is a simple fix (Run instances of this plugin in real time when plugin window is open) but it would be nice to put it to bed.

[James Steele]

Hopefully, DP 11.33 will have some fixes that benefit you.

From the list of fixes, sounds like, and I'm hoping, it fixes the Waves plugin graphics bug. Not a huge issue as there is a simple fix (Run instances of this plugin in real time when plugin window is open) but it would be nice to put it to bed.

That's good. I'm just weary of continuing to hope for things to get better and they just don't. Might be different if MOTU had responded "We're aware of that and we're looking into it. We're going to get that fixed in (reasonable time frame)." You know... one day you just say "I'm done."

[Michael Canavan]

I, of course, have reported all of this stuff to MOTU until I resemble Papa Smurf. (That means "till I'm blue in the face" for those of you how aren't familiar with the childrens' cartoon.) I don't have time for a crash course in computer programming, so that's the best I can do. I have absolutely zero idea when these issues will be addressed (it could be months or years) so I'm faced with a choice. Do I work around these annoying issues for some undeterminable open-ended period of time (again... months? years? a decade?)? Will I even live to see them fixed? Or do I sit down and start learning my way around another DAW (pick one: Cubase, Pro Tools, Logic) where this stuff "just works." Pro Tools is probably a top contender given the sort of music I do.

This is not something I mention lightly. I've been a staunch proponent and evangelizer for MOTU and DP for decades... and well... I started UnicorNation in the early 90s which later became MOTUnation. But to borrow from the Righteous Brothers, I'm starting to lose that loving feeling. Seems like that's something MOTU might care about, but what do I know? There are now Facebook groups that are busier than this board. They may not need me or this board anymore. There comes a point where you want to work they way you want to work, and you can't be hindered by blind loyalty to a company or a piece of software.

I've jumped ship before, and used Live in conjunction with DP or Logic when I used it. I've looked into them all, and it's always some form of compromise. With Logic it was the way tracks were laid out, DP's track selector is missed when you don't have it in the other DAWs. Lately I've been experiencing issues with DP in relation to hangs and crashes in a few songs as they near completion, not enough information in the crash report to isolate where the issue is coming from etc. I would be lying if I said it didn't make me take pause. I do like these older "do everything" DAWs, but most of them have senior moments, i.e. they have buried technical debt that means the occasional hang or crash. Modern DAWs like Bitwig and Reaper are pretty much crash free, this isn't me trying to bash DP, Cubase and Logic can have some fun times this way as well. Both are currently reported as stable though. I did have a super fun hang on AUv3 scan with Logic that was near impossible to solve last year though.

That said it's been about 3 years and almost 4 months since DP11 came out. This is near the longest between upgrades, 3y 6m and 3y 5m are the longest, the rest are all 3 years or less. DP12 is around the corner, and for any deep cleaning, they're definitely going to wait for a full number upgrade. Plus IMO going deeper into better control surface support seems like a super logical thing to do, it's been a poor area for DP for a long time. Shoring up plugin handling is hopefully on that list as well. VST3 is needed for many things and it's volatile in DP on Mac anyway.