What can we realistically expect in Bitwig v2.4?

[Pyrotek45]

Im still emailing them, however they are very very slow responders. They said changing this is NOT planned but they will consider adding it to the "wish list"...oh boi. Whatever that means.

Then everyone who wants this should email them. That is what gets things done

I agree.

[Scoox]

I would like to see better midi loop recording, so we can undo the last pass while recording. At the moment it's really hard to get creative because of this limitation.

[smoothny]

Bitwig 2.4 will get an update for the sampler, you can take a sneak preview in the summer sale banner.

https://cdn.bitwig.com/dms/bitwig/2018_ ... Save_B.png

Greetings,
smoothny

[Scoox]

I would like to see more resources put into workflow improvements than adding new plugins and modulators and fancy stuff. Decent loop recording (with undo), linked loops and automation clips like in FL Studio are all very important for electronic music production. That's why currently I'm using FL, but I would like a DAW that can do what FL does plus live work, hence my interest in Bitwig.

[Hanz Meyzer]

I really hope the Bitwig team currently is addressing the GUI problem in a serious way. For me this is the absolute essential base problem which needs to be resolved , everything else can follow later. A fluent GUI and operation response time in Bitwig would be awesome!

[pdxindy]

I really hope the Bitwig team currently is addressing the GUI problem in a serious way. For me this is the absolute essential base problem which needs to be resolved , everything else can follow later. A fluent GUI and operation response time in Bitwig would be awesome!

They said they are on it... they also said it is a lot of work so I would take that to mean it may or may not make it into the next update.

[pc999]

Bitwig 2.4 will get an update for the sampler, you can take a sneak preview in the summer sale banner.

https://cdn.bitwig.com/dms/bitwig/2018_ ... Save_B.png

Greetings,
smoothny

Cool!

[antic604]

I really hope the Bitwig team currently is addressing the GUI problem in a serious way. For me this is the absolute essential base problem which needs to be resolved , everything else can follow later. A fluent GUI and operation response time in Bitwig would be awesome!

They said they are on it... they also said it is a lot of work so I would take that to mean it may or may not make it into the next update.

Plus there's this unexpected development: viewtopic.php?f=259&t=507154

[Hanz Meyzer]

Bitwig 2.4 will get an update for the sampler, you can take a sneak preview in the summer sale banner.

https://cdn.bitwig.com/dms/bitwig/2018_ ... Save_B.png

Greetings,
smoothny

Doesn't it look like granular support?

[Pyrotek45]

i made a short goof on bitwigs drum machine and how the auto keytracking is messed up.

https://www.youtube.com/watch?v=haXLrtM ... e=youtu.be

[coltpeacemaker]

A time ruler would be nice! It's needed and long overdue!!

[toby]

i made a short goof on bitwigs drum machine and how the auto keytracking is messed up.

https://www.youtube.com/watch?v=haXLrtM ... e=youtu.be

I was worried it was only our samples causing this problem (as a lot of them were saved with Edison) so I went through my Splice library and found actually about 20% of the samples I own have some kind of metadata that causes this problem.

[Pyrotek45]

i made a short goof on bitwigs drum machine and how the auto keytracking is messed up.

https://www.youtube.com/watch?v=haXLrtM ... e=youtu.be

I was worried it was only our samples causing this problem (as a lot of them were saved with Edison) so I went through my Splice library and found actually about 20% of the samples I own have some kind of metadata that causes this problem.

I've been talking to as many people as i can about it and it's not just black octopus samples. i have many drum packs myself and yours is not the only one it does it to.

[rodanmusic]

Ah yes this has happened to me a few times. I agree that It is extremely frustrating.

[gulden]

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

Had similar problem with some samples, so today had some time to experiment,..
Found some samples that triggered keytracking in drum machine, and all of them had metadata info from fl studio,..
examples:

comment - modified by flstudio xx
comment - recorded on x/xx/xxxx in Edison.
software - FL Studio xx
software - Edison

where x is number

All of them triggered keytrack mode on, but then in one of the libraries I found two samples that had fl studio software metadata, but only one triggered keytracking,..

So, I downloaded demo version of FL Studio (can export stuff but cannot save projects)
In the miscellaneous section when exporting to wav file, there are 4 options for adding metadata to audio files:
1. Save playlist markers
2. Save loop markers
3. Save note markers
4. Save tempo information

Default setting for exporting to wave file has two options selected:
1. save playlist markers
2. save loop markers

If you leave save loop markers when exporting, bitwigs drum machine will turn keytracking on, if you deselect it, it won't.
video:
https://streamable.com/ntju6 (https://streamable.com/ntju6)

Now about Edison export, it's a sample recorder/editor in FL Studio, I'm pretty noobish with it,..
You can export by drag and droping from an interface icon or do save as wave file, in both cases it didn't ask me to choose embedded metadata and both files triggered keytracking in bitwigs drum machine,..

Maybe there are some advanced settings for Edison exports, I couldn't find them,...
Anyway I've sent this finding to bitwig support.
For me I'll just nuke all the metadata from libraries made with fl studio, and keep on working as usual, as soon as I find suitable software for the job.