Bitwig PDC... exactly same problem as LIVE!!

[virtualmark]

Just had confirmation from one of the devs that the PDC bug is being worked on right now and should hopefully make it into an update very soon (but not 1.0.3 as this is being compiled now).

Source - public Webinar with Volker (Bitwig Dev)

So what does 1.0.3 fix?

[Costa Rica]

Guess I'll wait for v1.04

[Sprocket-Audio]

I didn't ask.. he was being asked many in depth questions! I guess as its being compiled now, we'll find out very soon!

[nbless]

wooow cool, they are fast

[virtualmark]

I didn't ask.. he was being asked many in depth questions! I guess as its being compiled now, we'll find out very soon!

Maybe, but we didn't get any release notes for 1.0.2. Hopefully they'll tell us what they've changed this time.

[kayhel]

Just had confirmation from one of the devs that the PDC bug is being worked on right now and should hopefully make it into an update very soon (but not 1.0.3 as this is being compiled now).

Source - public Webinar with Volker (Bitwig Dev)

These are very good news - lloking forward...

[kayhel]

What do you really think the answer is?

"Bitwig features PDC except for the built in modulation system"



Probably not ...

no, but that would be the typical ableton answer

[humanbeingbeing]

Just a quick note, so nobody has to panic: the pdc is designed to compensate the audio, the automation, the timing information for plugins. Most of it works great, but there's currently a bug with the last one, for example and there might be other scenarios that don't behave correctly, as pdc and time/routing stuff can be a real pita Anyway, the problems are not by design but bugs and we will check out all scenarios that don't work as they should and fix it.
Normally everything that can be reproduced reliable is fixable, esp. as the code base is still fresh...

Cheers,
Dom

Thanks for this response Dom, this kind of feedback with users is super important... and I think it's the first time that automation timing has been explicitly stated as a feature... I'm really interested in how quickly bug fixes will be coming out because I've experienced too many so far but still super impressed with the software and looking forward to some of these minor issues being resolved quickly. I think beta testing should've been more widespread because some of the day 1 issues feel like they would've become maybe more apparent if there were as many users.... still looking forward to making that jump, crossing my fingers for quick updates, needed features and bug fixes.

[virtualmark]

Just had confirmation from one of the devs that the PDC bug is being worked on right now and should hopefully make it into an update very soon (but not 1.0.3 as this is being compiled now).

Source - public Webinar with Volker (Bitwig Dev)

This was yesterday, and it was apparently being compiled. I wonder what's happening, anyone got any ideas?

[ZenPunkHippy]

No idea, but probably internal testing. Releasing an update to 100s or 1000s of users is no easy task!

[robogone]

While I understand why Bitwig went with a close beta test, I think things like this show the benefits of a more public beta. Fixing the code this quickly because the bug wasn't found until v1.0 isn't the best approach to coding.

[Blue-eyed Blonde Ape]

Testing with Ozone5 to introduce latency, Automation PDC is not correctly compensated.

Have you tried the same test with some different high latency plugin ? Because Ozone is misbehaving and messed my own similar tests on some other DAWs, haven't tested bitwig that way yet, but curious if you tried to throw in some other high latency plugin instead of Ozone.
iZotope built it purely for mastering, to put it on a master bus, so I wouldn't surprise that it's misreporting its latency to host or something like that, it even has some kind of latency reporting built in in its options, so yeah Ozone is messy for such tests in my expierence.

[virtualmark]

Testing with Ozone5 to introduce latency, Automation PDC is not correctly compensated.

Have you tried the same test with some different high latency plugin ? Because Ozone is misbehaving and messed my own similar tests on some other DAWs, haven't tested bitwig that way yet, but curious if you tried to throw in some other high latency plugin instead of Ozone.
iZotope built it purely for mastering, to put it on a master bus, so I wouldn't surprise that it's misreporting its latency to host or something like that, it even has some kind of latency reporting built in in its options, so yeah Ozone is messy for such tests in my expierence.

Yes, I've tried it with Ozone 5 and with Fabfilter Pro-Q. The problem is with Bitwig, and has been confirmed by them as a bug. They have stated in this thread that they are working on it.

[Blue-eyed Blonde Ape]

Yes, can confirm it, just tested it myself, because to my understanding confirmed bug was about "synced" plugins, not sure though, that's why I was curious about "manual" automation, wish that both things would be fixed, we've had enough of live and the likes.

[virtualmark]

Yes, can confirm it, just tested it myself, because to my understanding confirmed bug was about "synced" plugins, not sure though, that's why I was curious about "manual" automation, wish that both things would be fixed, we've had enough of live and the likes.

Yeah tell me about it lol. Does your screen go out of sync too? Mine does, it's really annoying. I did the same test on Cubase, it's rock solid. The screen is in time, the automation is bang on and sounds exactly the same no matter where I put the plugins. That's how it should be.