Bitwig

virtualmark · Post by **virtualmark** » Sat Mar 29, 2014 1:16 pm

kurasu wrote:We've now reproduced and fixed the delay compensation for device automation, which wouldn't work as it should when the automated device was placed after a plug-in which introduced a delay. We also fixed the transport info one. Those will both be in 1.0.4.

Great news! But what do you mean by transport info? Is this what's causing the display to go out of sync?

kurasu · Post by **kurasu** » Sat Mar 29, 2014 1:26 pm

virtualmark wrote:Great news! But what do you mean by transport info? Is this what's causing the display to go out of sync?

it means tempo-synced stuff would be out-of-phase

virtualmark · Post by **virtualmark** » Sat Mar 29, 2014 1:28 pm

kurasu wrote:
virtualmark wrote:Great news! But what do you mean by transport info? Is this what's causing the display to go out of sync?
it means tempo-synced stuff would be out-of-phase

Ah. So is the display out of sync issue going to be fixed too? Or is it fixed with this patch?

kurasu · Post by **kurasu** » Sat Mar 29, 2014 1:29 pm

You mean that the GUI of the vst is out-of-sync with what you hear?

virtualmark · Post by **virtualmark** » Sat Mar 29, 2014 1:36 pm

kurasu wrote:You mean that the GUI of the vst is out-of-sync with what you hear?

Well, when I add a plugin with high latency and press play, there's a delay in the sound of the audio, as expected. Yet the transport shows that it starts playing instantly, so it's ahead of the music. The line that moves from left to right doesn't line up with the audio basically.

Blue-eyed Blonde Ape · Sat Mar 29, 2014 4:58 pm

will eagerly wait to test it

virtualmark · Post by **virtualmark** » Sat Mar 29, 2014 9:20 pm

Is there an ETA on the patch?

23fx23 · Post by **23fx23** » Sun Mar 30, 2014 2:09 am

great news!!! that was the first thing i tested in the software lol
i was so disapointed discovering it was wrong, cool if just a fixable bug

virtualmark · Post by **virtualmark** » Mon Mar 31, 2014 10:22 am

So.. any news on the patch?

sl1914 · Post by **sl1914** » Mon Mar 31, 2014 10:30 am

Many bugs take more than one day to fix.

virtualmark · Post by **virtualmark** » Mon Mar 31, 2014 10:31 am

sl1914 wrote:Many bugs take more than one day to fix.

If that's the case, why have there been several patches already?

They have confirmed that they've sorted the PDC problem, I'm just interested in when it'll get here.

whyterabbyt · Post by **whyterabbyt** » Mon Mar 31, 2014 10:37 am

virtualmark wrote:
sl1914 wrote:Many bugs take more than one day to fix.
If that's the case, why have there been several patches already?

because he said 'many bugs', not 'every bug'. its not hard to work out that some fixes will have been worked on even as the initial release build was being compiled, and that some bugs fixed since then were solvable very quickly.

sl1914 · Post by **sl1914** » Mon Mar 31, 2014 10:42 am

Many is not the same as all. Some bugs may be fixed quickly, some take more time.
Think about how PDC is handled in other DAWs: if fixing it was quick and simple, don't you think it would be working 100% in all products that people have been using for years?

People have reported problems in many areas. It's not just PDC they are working on.

dom@bitwig · Post by **dom@bitwig** » Mon Mar 31, 2014 10:44 am

1.0.4 is in the making, maybe even comes still today for a fresh start into the week!

The PDC fixes are in there, the OSX graphic glitch on retina machines etc.

More infos later!

dom@bitwig · Post by **dom@bitwig** » Mon Mar 31, 2014 10:46 am

Ah, the VST "save as" bug should also be gone...

Bitwig

KVR Audio

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