A new old WaveBurner bug?

[Djehuti]

So maybe this is old (1.2, 1.5) and maybe it's new in 1.6, or maybe I just don't get something about how to use WaveBurner.

When I insert a plugin in WaveBurner, it keeps jumping back to its default settings when I stop and start playback (sort of like if I'm adjusting an auto-read-enabled param in a PT plug). But sometimes it doesn't, and the setting sticks. Sometimes the setting in the parameter list (in the lower right part of the WB interface) tracks the plugin window, sometimes it doesn't. When it does, the setting sticks.

When I close the project, quit WaveBurner and open it again, it almost always doesn't stick, and all my plugin settings are reset to the defaults.

Clearly there are people using WaveBurner for real work, but I can't see how this is happening.

Is it that other people aren't encountering this bug? Or is it that it isn't a bug and I'm just doing something wrong? Or is there a workaround that I don't know about?

[jdg]

yah, thats lame. i call it bug, but i'd bet they'd call it a feature.
workaround:
in region plug-in window, save your settings as a preset, then recall that preset.
settings will stick then

[Djehuti]

Originally Posted by jdg

yah, thats lame. i call it bug, but i'd bet they'd call it a feature.
workaround:
in region plug-in window, save your settings as a preset, then recall that preset.
settings will stick then

I tried that too. I can recall the preset, but I have to actually recall it; it doesn't automagically come up. Soooper lame.

Hi ho. Hi ho... It's back to PT+Peak I go...

[Coyoteous]

[Jerry Tubb]

I kinda expected there would be some plug-in and automation issues.

v1.6.0 is just that... a new dot zero version.

JT

[Coyoteous]

Has OS X WaveBurner ever had anything else?

That's what worries me the most about all this now that it seems to finally be bit accurate. Of course, we've seen that some fixes can be outside the actual app.

Automation and DDP were sorely missed "killer ITB mastering app" features... so close now, yet so far! Though I suppose it needs external capture to be really serious.

To this particular problem, I never had anything like that with previous versions. But, it makes sense that it would be related to the addition of automation in 1.6.

For me, WB was about speed, and doing everything in one application. This particular bug/feature seems like a show-stopper for that.

Fortunately, I don't have to work fast anymore... still disappointed. I'll probably just wait and watch from the sidelines until things are fixed and/or I find cheap upgrade.

[Table Of Tone]

That's what bugs me about OSX for mastering, period!
No choice and buggy as hell.
It's fine if you know the workarounds but I'm fast getting bored with it!

I switched to mac around four years ago but I think I am gonna move back over to the dark side of the force!
Sequoia just p***es over ANY OSX workstation!

[Jerry Tubb]

We should get Nick up to speed soon in our B Room with WB 1.6 and Leopard on our Mac Pro.

I'll get him to post his analysis of these problems, he has a very scientific organized way of looking at things, and quite the expert on WaveBurner.

For most projects we both use Pro Tools as a playback source DAW, for capturing the analog EQ loop processing, except for when I use soundBlade for same in unattended sessions.

We'll be using WB 1.6, sB, PMCD, and perhaps even Peak Pro 6 for assembly & burns.

I wouldn't mess with plug-ins on WB 1.6.0 ...let 'em update a few revisions first.

JT