Bitwig

SLiC · Post by **SLiC** » Wed May 17, 2017 4:01 pm

PhilipVasta wrote:I really hope the dev team puts out a roadmap. I know that release dates can slip a bit, that's fine. But I would just like to know, roughly, what they have planned. Track freeze, track comping... Are these things coming within the next couple months? Or are they years away? I think it's reasonable to expect this kind of roadmap to be in place with a DAW that is still, in some ways, pretty immature.

I think of Bitwig as 'different' rather than immature

It is missing some features that are important to some people, but it does a lot of stuff DAWS that have been around a decade can't do...cant even get close to doing...

Freeze track is an easy one I think, we already have bounce in place (once done you can just turn of plug). I agree comping needs to come, but then I thought that in Live and we still don't have it at version 9!!

pc999 · Post by **pc999** » Wed May 17, 2017 4:10 pm

In my initial test I love the new AMP

(but I still need to see how well it can emulate a distortion pedal

)

I hope the native devices keep improving (specially since I am on Linux) and I would like to see the synths/sampler get some love too, it would be very cool if they could better emulate real classic instruments.

SLiC · Post by **SLiC** » Wed May 17, 2017 5:15 pm

pc999 wrote:In my initial test I love the new AMP (but I still need to see how well it can emulate a distortion pedal )

I hope the native devices keep improving (specially since I am on Linux) and I would like to see the synths/sampler get some love too, it would be very cool if they could better emulate real classic instruments.

Stick this in front of AMP and you are good to go

https://cytomic.com/scream

Rappo Clappo · Post by **Rappo Clappo** » Wed May 17, 2017 5:22 pm

Linux support is a great trump card (excusez le mot), I am thinking of getting a Linux PC myself. So I keep my fingers crossed for Bitwig.

turbo_kev · Post by **turbo_kev** » Wed May 17, 2017 7:46 pm

Hi All

I am getting problems loading in some of my older projects

Example: Load up the project, it all seems to load correctly , no missing vst,s

But when I look at some of the vst,s instead of the little bitwig logo that you can click to turn the vst on / off. There is the auto suspend graphic

If I click play BW locks up and I have to do a force shutdown

has anybody else had this problem ?

cheers
Kev

turbo_kev · Post by **turbo_kev** » Wed May 17, 2017 8:04 pm

example

WXLF · Post by **WXLF** » Thu May 18, 2017 12:43 am

WXLF wrote:
abique wrote: Please can you give us useful information? Like what is your operating system? What's your processor? What are your plugins? Do you have a SSD? Can you reproduce all those issues always? Do you have an anti-virus causing troubles? And so on...
sure, abique. i was planning on testing it on my windows desktop (7700k) tomorrow before i sent anything useful in. (4:20am for me)

but tonight i was just messing around on my macbook

2.3 GHz Intel Core i7
Sierra 10.12.3
yes, Solid state drive
no anti-virus
built-in output 44.1khz

pressing ok after selecting the drum machine preset froze up about 3/5 times. which has never happened in other versions of bitwig 1.x or 2.0

hey, abique. i got a chance to test it on the windows desktop today and the same thing happened. I was able to reproduce it and figured out the exact steps.. 100% of the time

i sent in an email to support.. subject title "VST does not load (windows 10, sierra mac) (Bitwig 2.1)" with all the details

mercí

xonetacular · Post by **xonetacular** » Fri May 19, 2017 2:09 am

what happened to native multiclock support in 2.1 as detailed here: https://www.bitwig.com/en/home/news-arc ... ation.html

I'm not seeing any preset for it

pdxindy · Post by **pdxindy** » Fri May 19, 2017 2:49 am

xonetacular wrote:what happened to native multiclock support in 2.1 as detailed here: https://www.bitwig.com/en/home/news-arc ... ation.html

I'm not seeing any preset for it

I emailed Bitwig about that and they said

"we should edit this interview, there's not even a preset needed, you just use the Bitwig Studio HW Clock device, select the output there and you're done!"

xonetacular · Post by **xonetacular** » Fri May 19, 2017 12:45 pm

yeah I got the same reply, need to test it later. you still would need to set the divisions... think the default is 1/16th notes and the multiclock does not take 1/16th notes and needs 24ppq.

for some reason I thought the plugin sent other signals for position too but maybe the plugin handles this idk.

Ybom · Post by **Ybom** » Fri May 19, 2017 10:50 pm

pc999 wrote:I hope the native devices keep improving (specially since I am on Linux) and I would like to see the synths/sampler get some love too, it would be very cool if they could better emulate real classic instruments.

+1

Btw, I'm disappointed by v 2 because there is no more real full screen.
The open files list could go into a drop down menu.
The Bitwig logo could be a button.
We could win a lot of space.

turbo_kev · Post by **turbo_kev** » Sat May 20, 2017 7:43 pm

Just incase you thought that my problem was the audio engine was not activated
I can assure you it is.
some not all of the vst´s used just stay in auto suspend mode
and the project just locks up. even if I deactivate or terminate the process
then click to activate project, it goes through all the motions
of loading vst´s etc etc
but then again locks up

this project works perfectly in V.2
but in V2.1 it just locks up and doesn't do anything

cheers
Kev

r0bsta · Post by **r0bsta** » Mon May 22, 2017 12:06 am

I'm also having issues since upgrading to 2.1 - for some files, I open them and get 3 audio engine crashes in a row. After this, some of the plug ins have the "plug in not found" message on them, even though I can see them, and use them in new tracks, etc. If I try to activate audio engine after this, Bitwig will crash and I have to force quit.

The factory presets also do not work anymore - for eg, if I want to open up a drum kit, I select it and nothing happens. If I create a drum machine and then open a preset from the preset window, nothing happens.

I have tried rescanning my plug ins - this caused Bitwig to hang after running overnight. I tried removing the indexes and caches and rescanning - this at least enabled the scan to complete, but has not cured the above issue.

I have tried opening a new project, creating something in there, then opening a project that causes hangs with the audio engine off in another tab (tabs is a definite plus imo), and copying the tracks from this project into the new one. It sometimes plays, sometimes crashes, but if I save the new project and reopen, it has the same issues as the old one.

I prefer the workflow in Bitwig but this is killing me right now, it seems like the only way I can recover my last 6 months work is to bounce out whatever I have and continue to work on the projects in Ableton

pc999 · Post by **pc999** » Mon May 22, 2017 1:37 am

SLiC wrote:
pc999 wrote:In my initial test I love the new AMP (but I still need to see how well it can emulate a distortion pedal )

I hope the native devices keep improving (specially since I am on Linux) and I would like to see the synths/sampler get some love too, it would be very cool if they could better emulate real classic instruments.
Stick this in front of AMP and you are good to go

https://cytomic.com/scream

Thanks, as soon as they have a Linux version I will try

pdxindy · Post by **pdxindy** » Mon May 22, 2017 1:40 am

r0bsta wrote:I'm also having issues since upgrading to 2.1 - for some files, I open them and get 3 audio engine crashes in a row. After this, some of the plug ins have the "plug in not found" message on them, even though I can see them, and use them in new tracks, etc. If I try to activate audio engine after this, Bitwig will crash and I have to force quit.

The factory presets also do not work anymore - for eg, if I want to open up a drum kit, I select it and nothing happens. If I create a drum machine and then open a preset from the preset window, nothing happens.

I have tried rescanning my plug ins - this caused Bitwig to hang after running overnight. I tried removing the indexes and caches and rescanning - this at least enabled the scan to complete, but has not cured the above issue.

I have tried opening a new project, creating something in there, then opening a project that causes hangs with the audio engine off in another tab (tabs is a definite plus imo), and copying the tracks from this project into the new one. It sometimes plays, sometimes crashes, but if I save the new project and reopen, it has the same issues as the old one.

I prefer the workflow in Bitwig but this is killing me right now, it seems like the only way I can recover my last 6 months work is to bounce out whatever I have and continue to work on the projects in Ableton

I'd recommend when you install an update, that you keep the old version in case there is some issue. Then you can always roll back...

When you completed the new scan, did you check to see if there were errors? That might inform you if there is a particular plugin causing your problems.

Bitwig

KVR Audio

Bitwig Studio 2.1 has been released!