The All In One Source Bitwig Information & Speculation Thread

[hibidy]

"bitwig......you torment me!!!!"



Nobody is more frustrated with hosts than me I understand too well when things are not going right what a pisser it is.

[Cyoon]

[aMUSEd]

HDMI Audio drivers should be disabled. Check that.

Disabled.

Why should anyone have to disable their HDMI audio drivers just to run a host? I use HDMI audio all the time, I would hate to have to disable it.

[ezelkow1]

yea i dont think its necessary, i leave mine enabled on my gfx card outputting to another room all the time

[Lesha]

I have found out that some of the buffer size settings make crackles - 512, 192, 96, 48 and 32 samples.
I am not sure about 32, I think it crackles because it is too low.

[hibidy]

It's odd that 512 does. From what I understand, it is recommended for some hosts to use the even numbers (64/128/256/ and your dreaded 512) Don't really know why but live was at least one host that did. Maybe something in bitwig is similar.

[dsan@mail.com]

It's a rule of thumb (around the webz) to use double the previous size if you have problems (like what you have written hibidy 64/128/256 etc.)

I found it interesting what ezelkow1 suggested that evrything related to your audio interface run at the same rate. Didn't know that before but it does sort of make sense in effort to avoid conflicts with the software/interface.

Can't say for sure though as it all is Greek to me. I just read and apply and if it works I'm good to go

So far I've been lucky, I guess.

Even Live is now cooperating

Bitwig not so much with the new release

Happy Musiking!
dsan

[trimph1]

That is why I stay with what I have. Everything, well, almost, works fine here. After the last tussle with DP8 I ended buying hosts.

And no, no Bigwig here...

[hibidy]

It's a rule of thumb (around the webz) to use double the previous size if you have problems (like what you have written hibidy 64/128/256 etc.)

I found it interesting what ezelkow1 suggested that evrything related to your audio interface run at the same rate. Didn't know that before but it does sort of make sense in effort to avoid conflicts with the software/interface.

Can't say for sure though as it all is Greek to me. I just read and apply and if it works I'm good to go

So far I've been lucky, I guess.

Even Live is now cooperating

Bitwig not so much with the new release

Happy Musiking!
dsan

r u serious? UGGGGGGGGGGGG, what are we going to do with you? I thought bitwig was kickin' ass there.

[lfm]

I had a similar issue when using windows WASAPI drivers. I got it working by going into control panel > sound then de-selecting exclusive mode in the playback and recording advanced tabs. Maybe it works for you too.

Thanks for the advice, but that unfortunately didn't fix the problem. I am using ASIO in BWS and I don't see why it should interfere with other drivers.

As a test I would try and turn off Windows sound - overall.

Then if that works - it might have to do with either:

a) host you are running is demanding exclusive mode.
Most hosts have a setting whether to allow others to use interface.
And some further settings releasing device when not active application.

b) use a different out to soundcard of windows sound, and do routing in soundcards drivers - if allowing that. RME Totalmix let you do that easily.

I had windows sound attached to same audio device outs as daw and got issues starting a daw, saying similar things to your message - could not open...I used b) above. Then you can still use mediaplayer to test you rendered mixes etc.

[Lesha]

As a test I would try and turn off Windows sound - overall.

Then if that works - it might have to do with either:

a) host you are running is demanding exclusive mode.
Most hosts have a setting whether to allow others to use interface.
And some further settings releasing device when not active application.

b) use a different out to soundcard of windows sound, and do routing in soundcards drivers - if allowing that. RME Totalmix let you do that easily.

I had windows sound attached to same audio device outs as daw and got issues starting a daw, saying similar things to your message - could not open...I used b) above. Then you can still use mediaplayer to test you rendered mixes etc.

Thanks for your input.

Windows sounds are already turned off. Exclusive mode turned off.

I have made a different pair of outs for WDM, but foobar or other media players don't produce sound at all.

[dsan@mail.com]

r u serious? UGGGGGGGGGGGG, what are we going to do with you? I thought bitwig was kickin' ass there.

It was, couldn't have been happier, till this last update.

The new features we all wanted implemented, and that is so great, but now it locks up on saving state of VEP5 VST on slave machine. Strange that the beta didn't give this problem but the release does.

Note to self: Turn off Exclusive Mode! (Thank you lfm )

I think that could be the problem (keeping my fingers crossed).

Too bad the day job will keep me from finding out too soon

Happy Musiking!
dsan

[dsan@mail.com]

That is why I stay with what I have. Everything, well, almost, works fine here. After the last tussle with DP8 I ended buying hosts.

And no, no Bigwig here...

Yeah Barry - I'm almost to the point of no buy nothin no more.

But then there's not much left I haven't bought

Happy Musiking!
dsan

[Lesha]

I have contacted Bitwig tech support several days ago, but for now I am completely ignored, no response at all.

[hibidy]

I haven't had much response from email support either. Anyways, hopefully they are just a little behind from launching 1.1

You know, it didn't even occur to me that bitwig has a bridge I'll have to check out my old URS plugs and see if they work