Bitwig

audiohouse · Post by **audiohouse** » Mon Mar 31, 2014 7:09 pm

dom@bitwig wrote: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!

First thanks for the fast updates, I am really glad that I bought Bitwig after much hesitation..

If you guys keep this up, you will leave all other DAW's in the dust lol

Here is hoping to v1.0.4 gets out tonight, so I can have a go at it again. The problems I have been having gets fixed in 1.04. Oh mama! cant wait!

virtualmark · Post by **virtualmark** » Mon Mar 31, 2014 11:04 pm

It's still broken, exactly the same as before. This is getting old now.

Lesha · Post by **Lesha** » Mon Mar 31, 2014 11:43 pm

What are you talking about, I just tested it and it is fixed.

Orga · Post by **Orga** » Tue Apr 01, 2014 12:35 am

I just tried a similar test to the OP and i'm still getting the same results to be honest.

mrmatt · Post by **mrmatt** » Tue Apr 01, 2014 1:48 am

Yes, it seems to be a bus issue. when tracks are routed to effect tracks for summing. It seems like right now, effect tracks should only be used for sends and not as a summing bus. I've been testing it on 1.0.4 and all clues seem to point to PDC not getting the math right when things are getting routed. Hope this helps the BWS team figure it out

contrast · Post by **contrast** » Tue Apr 01, 2014 3:30 am

1) kurasu acknowledged here http://www.kvraudio.com/forum/viewtopic ... 6#p5699776 that there is another known delay issue involving busses which is not fixed in 1.0.4. (read the whole thread for more info) But busses were not involved in the issue mentioned in the OP.

2) The issue mentioned in the OP is fixed, at least on the Windows version. Putting a no-latency plugin after a high-latency plugin no longer causes bounces to go out of sync.

3) Because of 2, if you are still having problems, you should provide exact steps for reproduction and what platform you are on.

nechronics · Post by **nechronics** » Tue Apr 01, 2014 4:26 am

Orga wrote:I just tried a similar test to the OP and i'm still getting the same results to be honest.

PDC with the OP's scenario is working fine here. I even tried placing everything on a send bus with audio routed to it internally and through the send itself and everything still checked out.

I've showed my results in this video. Can you describe how you're getting different results or what you're doing to get different results? Thanks

Video Here:

virtualmark · Post by **virtualmark** » Tue Apr 01, 2014 4:59 am

It's not fixed at all, I wish people would learn to test properly. It's not difficult, it took me all of 60 seconds to find out that it's not working!

nechronics · Post by **nechronics** » Tue Apr 01, 2014 5:03 am

Ok, point taken...I managed to break it using a chain of linear phase Pro-Q's placed before and after a Volcano and LFO tool.

Hope the devs are on it. Hope they also manage fix the GUI display and playhead going out of sync.

nbless · Post by **nbless** » Tue Apr 01, 2014 5:06 am

Yep, I'm sorry Dom but I still have the same bug (on mac osx and 1.04). Tried with volumeShaper and high latency plugin

virtualmark · Post by **virtualmark** » Tue Apr 01, 2014 5:06 am

nechronics wrote:Ok, point taken...I managed to break it using a chain of linear phase Pro-Q's placed before and after a Volcano and LFO tool.

Hope the devs are on it. Hope they also manage fix the GUI display and playhead going out of sync.

Yeah, it's unbelievable isn't it? There's zero improvement to either issue. The GUI issue is super easy to detect, as it happens as soon as you add a plugin with latency. I guess they don't know how to add plugins or something, there's no other explanation I can see.

contrast · Post by **contrast** » Tue Apr 01, 2014 5:29 am

I attached a screenshot below.

First set of 4 shows automation of Tool gain parameter going out of sync. I used Voxengo Latency Delay on default settings (10k samples of reported and actual latency) to generate the latency.

I renamed the tracks to indicate each plugin chain. 4x indicates that there are 4 latency delays instead of just one.

As shown in the screenshot, the problem occurs when there are multiple latency-inducing plugins followed by a no-latency plugin (or perhaps a lower latency plugin, etc).

Second set of 4 shows a similar issue with LFOtool set to a little square pattern and modulating volume 100%. In this case there is no automation, it's just LFOtool's internal sequencer going out of sync.

The final set of three has LFOtool on the same settings as before except that the volume modulation has been turned to 0. As shown there is no delay in this case; it appears it's only the automation/song postition that are going out of sync in this example.

Andrei Marchenko · Post by **Andrei Marchenko** » Tue Apr 01, 2014 5:30 am

PDC still broken. Confirmed. Plugins chain: U-He Zebra, 8 x Fabfilter Pro-Q, Brainworx Filter.

If put Brainworx Filter before Fabfilter Pro-Q plugins - everything is fine.

I'm on OSX Mavericks 10.9.2. Plugin Delay Compensation is ON, Audio Recording Latency Compensation is ON.

That's how it "works":

owensands · Post by **owensands** » Tue Apr 01, 2014 5:59 am

Geek Model wrote:PDC still broken. Confirmed. Plugins chain: U-He Zebra, 8 x Fabfilter Pro-Q, Brainworx Filter.

If put Brainworx Filter before Fabfilter Pro-Q plugins - everything is fine.

I'm on OSX Mavericks 10.9.2. Plugin Delay Compensation is ON, Audio Recording Latency Compensation is ON.

That's how it "works":

I did three Fab Q at max latency and bounce is definitely off. With one at max latency its dead on though. Not sure why. Maybe they are only taking one plugin with latency into account? Not sure why anyone would have 8 linear EQ plugins in one track though but yeah.

virtualmark · Post by **virtualmark** » Tue Apr 01, 2014 6:25 am

owensands wrote:I did three Fab Q at max latency and bounce is definitely off. With one at max latency its dead on though. Not sure why. Maybe they are only taking one plugin with latency into account? Not sure why anyone would have 8 linear EQ plugins in one track though but yeah.

Yeah it's be extremely rare that you'd have 8 linear EQ plugins lol! But what if we had a couple of distortion plugins, a couple of filters, a couple of eq's, a chorus plugin etc, all automated.

Then something goes out of time - it would be a nightmare to track down the problem. Especially since Bitwig doesn't have the option to turn a VST off, you'd have to actually remove the devices from the chain one by one, until you find the problem. Then add them back, and re-do your automation. Unacceptable.

That's why these extreme test cases are necessary, so that we know it's fixed once and for all.

I've done the exact same test in Cubase. When you press play, nothing happens for a moment, then the transport starts moving and the sounds come out in time. Perfect! The initial delay is so that Cubase can catch up, as the latency is really high with several Pro-Qs. I think about 500ms each. So 4 of them gives a 2 second pause when you press play.

In Bitwig, you press play. The transport starts moving, no sound comes out. Yet the transport is moving over your waveforms. Ah here we are, after a delay the sound is now coming out... but wait.. that's not the sound I expected. Instead I have a different sound coming out, as the automation is also 2 seconds out of sync.

Honestly, I don't know how anyone could have missed this.

Bitwig

KVR Audio

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