Snap Shot automation Broken in Waves V9- DP 8 and DP 9

[Phil O]

TDH, what bothers me is that MOTU cannot duplicate this problem. Perhaps someone with an extra hard drive could make a boot drive with clean install of just OS, DP, and Waves plugins and see if the problem still exists. In other words, let's try to duplicate what MOTU is seeing. Perhaps there's other software at work here or something else that we're missing.
You commented somewhere that you couldn't believe MOTU cannot reproduce this. Well there are only two possibilities that I see. There's something different at their end, or they're full of ______. Let's see if we can determine which.

Phil

[Michael Canavan]

TDH, what bothers me is that MOTU cannot duplicate this problem. Perhaps someone with an extra hard drive could make a boot drive with clean install of just OS, DP, and Waves plugins and see if the problem still exists. In other words, let's try to duplicate what MOTU is seeing. Perhaps there's other software at work here or something else that we're missing.
You commented somewhere that you couldn't believe MOTU cannot reproduce this. Well there are only two possibilities that I see. There's something different at their end, or they're full of ______. Let's see if we can determine which.

Phil

Someone said this? MOTU has been able to replicate every problem I've sent them, and Waves are far from the only plug in manufacturer who are affected with this bug. Definitely time to send in a bug report myself on this one.

[stratology]

Since it evolved over the years, there were many patches and back-door connections that had to be rediscovered, examined, and translated into object oriented programming. The odds of getting all that correct even in the first several releases since going 64 bit would be approximately 00.00%.

Just to clarify, 64bit memory addressing has nothing whatsoever to do with object oriented programming. The vast majority of 32bit programs were written in object oriented, rather than procedural, languages. Especially complex apps like DAWs.

Regardless, the point you're trying to make is valid, of course.

The case of the snapshot automation isn't at all like changing a tire while driving the car. Not at all! It's more like copying a region of a spreadsheet and pasting it elsewhere, which is something that every spreadsheet has to do perfectly, every time. Why would we not expect DP to do that? After all, a DAW is basically a 4 dimensional spreadsheet.

I think a better analogy is switching a plug-in preset during playback. Which is a very basic task. And the 'saving' of the preset (taking the snapshot) does not even have to be done while playback is running.

It seems to work with DP's native plug-ins, so expecting it to work with 3rd party plug-ins is not unreasonable.

[Shooshie]

Since it evolved over the years, there were many patches and back-door connections that had to be rediscovered, examined, and translated into object oriented programming. The odds of getting all that correct even in the first several releases since going 64 bit would be approximately 00.00%.

Just to clarify, 64bit memory addressing has nothing whatsoever to do with object oriented programming. The vast majority of 32bit programs were written in object oriented, rather than procedural, languages. Especially complex apps like DAWs.

Regardless, the point you're trying to make is valid, of course.

The ability to go to 64 bit addressing in OS X was predicated on using Cocoa, an object oriented environment that could use Objective C, C++ and perhaps some other languages, but not the "Carbon" based procedural languages that were originally supposed to be a part of this transition. Apple withdrew that support late in the game leaving many developers, MOTU included, scurrying to rewrite their apps in the Cocoa environment. I didn't suggest that 64 bit addressing is a result of using object oriented code, but in the case of OS X, the two are not unrelated. While Apple was originally going to allow developers to grandfather their plain C code into OS X 64 bit addressing using Carbon, they changed their mind and made it Cocoa-only. Cocoa is object-oriented, so in OS X object oriented code was inescapable if you were going to develop your app for 64 bit addressing, though not because of technical dependencies. It was just a decision made by Apple, which may have been arbitrary or it may have been founded on engineering across iOS platforms, or other reasons.

Those memories are all fading now, but even though MOTU didn't publicize it, it was generally believed that they had to rewrite DP from top to bottom using Cocoa once Apple jerked the rug out from under them by dropping Carbon support late in the game. If my memory is correct, DP was being developed in C before that point.

Shooshie

[labman]

We can't get Waves 10 plugs to do snapshot automation at all. (DP9.52) Any luck with any of you others??? Very discouraging

[toodamnhip]

We can't get Waves 10 plugs to do snapshot automation at all. (DP9.52) Any luck with any of you others??? Very discouraging

Anything you don’t manually manipulate before hitting snap shot, will not register in DP. There seems to be a disconnect between the graphics level, and the internal registry that monitors setting in DP> So the solution is to double click any numeric parameter, and the hit tab to tab through all numeric parameters. This registers them with Das internal engine and snap shot can work. Some plug ins will still not work no matter what then, but waves is pretty good if you tab through. Good luck.

[FMiguelez]

We can't get Waves 10 plugs to do snapshot automation at all. (DP9.52) Any luck with any of you others??? Very discouraging

Anything you don’t manually manipulate before hitting snap shot, will not register in DP. There seems to be a disconnect between the graphics level, and the internal registry that monitors setting in DP> So the solution is to double click any numeric parameter, and the hit tab to tab through all numeric parameters. This registers them with Das internal engine and snap shot can work. Some plug ins will still not work no matter what then, but waves is pretty good if you tab through. Good luck.

OMG

Is MOTU even aware of this? This is quite a bug!

Last time I checked, DP still gives and EXPECTS from the user non-sensical and disparate parameter amounts when manually seeing/entering values in its number boxes to tweak Waves plugins.

This makes it impossible to dial in parameters.

Is it still doing this?

[labman]

snip.... So the solution is to double click any numeric parameter, and the hit tab to tab through all numeric parameters.

Thank you TDH. we will give that go!