Bitwig

Ch00rD · Post by **Ch00rD** » Fri May 01, 2015 7:35 pm

PHY6 wrote:Is this 'logo bug' the only bug that's there now ?

Most definitely not. I really don't know how many old ones there are apart from the few dozen I've found myself in the last few weeks, but if you read up, this version apparently not only fixes some bugs, but introduces a couple of new bugs as well.

TeotiGraphix · Post by **TeotiGraphix** » Fri May 01, 2015 9:05 pm

Ch00rD wrote:
PHY6 wrote:Is this 'logo bug' the only bug that's there now ?
Most definitely not. I really don't know how many old ones there are apart from the few dozen I've found myself in the last few weeks, but if you read up, this version apparently not only fixes some bugs, but introduces a couple of new bugs as well.

This was epic.

Edit: This reply was not correct, I actually thought you were referring to 1.2(wrong thread).

tooneba · Post by **tooneba** » Sat May 02, 2015 3:19 am

logo bug is of course no.1 priority to be fixed.

PHY6 · Post by **PHY6** » Sun May 03, 2015 8:48 am

tooneba wrote:logo bug is of course no.1 priority to be fixed.

Very important, yes... Couldn't believe my eyes, seeing everyone talk for pages about a frikkin logo splash screen.

hihu · Post by **hihu** » Sun May 03, 2015 11:48 am

Where to download this? Don't get a notification when I start up my Bitwig.

Ogopogo · Post by **Ogopogo** » Sun May 03, 2015 12:14 pm

Follow the link in the first post. You don't get a notification because it's a beta version, meaning it's unfinished and there are likely bugs. Don't download it unless you want to be a tester.

hihu · Post by **hihu** » Sun May 03, 2015 2:04 pm

Ok will stay with 1.17 as there are not bugs I ran into.
Will update the final version.

Thx

Napalm Candy · Post by **Napalm Candy** » Sun May 03, 2015 9:35 pm

Hihu, i found lot of bugs that are unsolved. Also I see few bug fixes in this version.

askewd · Post by **askewd** » Mon May 04, 2015 7:12 am

I don't see the point of changing the splash logo, it was fine as it was and surely the devs time would be better spent on squishing bugs or more important aspects. My mouse pointer STILL periodically vanishing (since 1.0.0) , and macros still unable to map to Nebula. Could list more.

Anyway, if talking about the logo, it was nice contrast before now it looks wishy-washy. I'm on Mac.

ceasless · Post by **ceasless** » Mon May 04, 2015 8:48 am

And certainly musicians' time is better spent making music rather than talking trash on forums...

The splash logo is something that requires zero programming to change. Just take a look at the fact that you can change it simply by dropping in a different image.

ri0t · Post by **ri0t** » Mon May 04, 2015 12:33 pm

Hint: When editing in layered mode, use the little lock symbol next to the clip, to make sure, the rubber tool does not delete in that clip, too.

Ogopogo · Post by **Ogopogo** » Mon May 04, 2015 4:39 pm

I'm getting a fairly consistent poof when trying to scale down midi clips /2 with the inspector. Sent in a few crash reports. OSX.

codec17 · Post by **codec17** » Tue May 05, 2015 9:26 am

codec17 wrote:Hi..
When in layered editing and use the eraser gummy it deletes all the tracks in layered editing.
See giff.

FALS ALARM!!! FALSE ALARM!!!

I forgot the lock icons on the left of the screen...

But wasnt it locked by default? I dont remember really?(idint realy paid attention to it earlier)
This is just plain stupid of me... Fortunate the BW headquarters remind me of that..(not that im stupid but the locks!

)
So again FALSE ALARM!

Ch00rD · Post by **Ch00rD** » Tue May 05, 2015 11:14 am

codec17 wrote:FALS ALARM!!! FALSE ALARM!!!

Fortunately, and to my embarrassment, the issue I posted above also turns out to be a false alarm.

Ch00rD wrote:It seems to introduce a severe regression issue (for my system, anyway), though. In 1.1.8 RC-1 I can't load a project that I can load just fine in BWS 1.1.7, which maxes out (i.e. using 100% of) the DSP load on my UAD-2 device. Loading the same project using 1.1.8 RC-1 results in a warning message stating that the DSP load limit of the UAD-2 device is exceeded (curiously, disabling all UAD-2 plug-ins leaves a DSP load of 7% in 1.1.8 RC-1, and 8% in 1.1.7).

What actually happened, is that I had changed the sample rate from 44.1 to 48 kHz in Bitwig Studio 1.1.8 RC-1, and then forgot about it; the UAD-2 documentation does mention this at http://www.uaudio.com/support/uad/compa ... chart.html (emphasis added): "All measurements are taken at a sample rate of 44.1 kHz. Some UAD plug-ins use more DSP at higher sample rates."

When changing the sample rate back to 44.1kHz, the same projects now load without issue in Bitwig Studio 1.1.8 RC-1.

SLiC · Post by **SLiC** » Tue May 05, 2015 12:05 pm

codec17 wrote:
codec17 wrote:Hi..
When in layered editing and use the eraser gummy it deletes all the tracks in layered editing.
See giff.
FALS ALARM!!! FALSE ALARM!!!
I forgot the lock icons on the left of the screen...
But wasnt it locked by default? I dont remember really?(idint realy paid attention to it earlier)
This is just plain stupid of me... Fortunate the BW headquarters remind me of that..(not that im stupid but the locks! )
So again FALSE ALARM!

I now hold you personally responsible for delaying the 1.2 beta