The Bitwig thread

i cant believe i’m saying this ! but i would love if they add comping :sweat_smile: !!!

i was trying it the other day in reason for some guitar and vocal recordings ! and oh boi it really made me want to work more with recording stuff

but yeah my top ones right now are , (polyphonic midigrid), MSEG, some form of pitch correction device (autotune,neptune,Newtone etc) .

i would also love if they add a sinebank module and some spectral blocks in the grid for sound design

2 Likes

Ableton announcement made a lot of people think the same. I somewhat agree ( but do not find it really necessary as i do not record audio often - if at all)

i agree with this, as on linux it would be all-in-one solution as a mature DAW (+comping)

Reason is tempting and most of the time i cannot decide between the two, but the easiness of audio drag&drop/manipulation is way ahead compared to Reason’s workflow… fx layer device… i’m ‘parallell-chains’ freak so i cannot simply handle so many parallel tracks within one track in other daws than bitwig fx layer, ableton fx rack or renoise sampler fx tab :stuck_out_tongue:

I never manage to use the grid to actually create stuff that I use.

What I would like is

  • a MSEG modulator. Seriously there are 100 modulators but no actual multi stage envelope ? Not great if you want evolving stuff
  • sample slicing in sampler. Right now you have to have a “clip”, place markers, and “slice to drum machine”, this creates one sampler for each slice. If you want to move the slices afterwards, its a pain. Would be so simpler to have slicing like in bitwig !
2 Likes

you can also use multisample mode of one sampler for multiple slices, but i agree, it’s a mess a bit… specially compared to renoise slicing + layering, it’s so straightforward… slice break, duplicate kick slice, replace with another kick, you have great sounding break in seconds…
I often approach the timeline, use alt+drag to nudge audio waveform, slice, stretch and it results to similar effect, but somewhat different approach…

we are talking about Bitwig here, right? :smiley:

And the sample/vst/preset browser is just wrong, I still don’t understand how resizing works haha. when I grab a corner and move the mouse left, it resizes right, etc. makes no sense at all

like renoise ! haha sorry

1 Like

can you please demonstrate here, i’m confused what is the issue? you mean on the docked like shown here or?
bw001

yes, so at the end we have to do the same as in 2001, no evolution in workflow :laughing:

no, the popup one. there are 3 columns that i cant resize, and resizing the whole window doesnt work the way it should.

1 Like

well yeah, slicing break in the timeline removes all the modulation possibilities from the sampler - other than solely audio FX…
but also, stretching is not yet even possible in the sampler - which would be a great thing… idk why it’s not still available/implemented

  • i just checked it, and now i understand your problem… i’m not (still) annoyed tho :smiley:

bw002

1 Like

A better midi editor would be great (like e.g. in Reaper) and I hope they add not more stuff and concentrate on usability first. I also didn’t use the grid that much and tbh I’m a bit lazy to build presets with it. For the last two tracks I used Renoise and yesterday I set up Reaper again which supports LV2 plugins now under Linux.

Maybe I make the next track with Reaper, just not to forget how things work :smile:

2 Likes

i’m not sure ! about the midi editor in reaper :sweat_smile:

i remember last time i used it i wanted to move a note up and down using the mouse !
and that was changing the velocities :sweat_smile:

1 Like

Oh and another one:

  • Remember scroll position/focused device position in dsp lane per track. Currently you always will restart from very left.
  • Generate shortcuts html
1 Like

I have some real headaches with Bitwig when it comes to missing detail features, but maybe I simply do not know how to do it, can you help me? These points constantly drive me crazy:

  1. There is no audio buffer reset / clear like in Renoise (double press stop button). So if I use fx with lot of feedback, I’ll have to wait some minutes until the audio buffer is empty and I can rerender! This seems to be pretty absurd to me, what the hell? The new render will contain a rest of the old play. Pretty annoying. Is there a way to workaround this or can I even clear the audio/plugins’ buffers?

  2. Everytime I switch the samplerate in the settings, the whole project will reload. But I often render multiple samplerates to hear some unknown rendering differences, kind of interesting. But reloading the whole project all the time, will make these tests very annoying. Why is that?

  3. Each time I developed a further composition, I all the time have to manually refresh the render area, each time I save a new song version, I manually have to reenter a new rendering filename. Also while live rendering, I can’t mute the audio! So I can’t continue to work an other audio stuff while rendering. These points drives me nuts.

  4. The note chase feature is a nice addition - for live editing/looping etc. But what the heck, it also will be applied on rendering! Why is that, makes no sense to me.

  5. After switching tracks and going back, it does not remember the last scroll position of the dsp bar in that track. But it seems to already remember the last highlighted device. So why it’s not scrolling to that device on switching? I don’t get it. Lot of nonsense mouse operations.

  6. I can’t reset LFOs? So each start of the song might be a total random combination! I then have to rerender multiple times, until I get the balance I want. Really timeconsuming and annoying. I neither seem to be able to reset a LFO modulator nor the LFO in the chorus, etc.

Maybe this sounds like 1st world problems to you, but in the sum it really frustrates me… Should I have a better frustration tolerance or do you agree here? Maybe once you are used to such comfort like in Renoise, it is pretty difficult to “downgrade” your habits again… Any tips to workaround or do it the right way?

2 Likes

i workaround this by terminating the audio process - but not mangling with lot of ambient/decaying stuff so i really do not have a problem right now

i guess because of sandboxing and the engine itself, i also wouldn’t expect ‘fluid’ workflow by changing something crucial like sample rate or audio buffer size.

for the other topics, i do not have an argument since i’m not bothered by those…

but i always come back to renoise due to qwerty power, since i’m that ‘terminal’ guy… and i love to utilize keyboard as much as possible…

2 Likes

What I really love about the Bitwig’s EQ+, that it sounds super precise and high quality in any case. Even if you use like 4 instances in serial, the sound does not appear to be degraded. This thing really is like a swiss army knife, they nailed it. I find the sound better than pro-q3. I can add warmth and color to a sound or neutral mixing. And somehow they really managed the analyzer graph to show exactly what you hear. It even seems to compensate for volume, so you always have it nicely in the middle (unlike for example pro-q, where you see nothing, if the track is low in volume).

So I am actually missing an all-in-one eq+ solution very much in Renoise. The EQ5/10 really is ok, when it comes to some kind of “oldschool” mixing. But for example the lack of really well balanced and flexible 12dB/24dB LP/HP filter slopes straight inside the eq, the lack of the analyzer within, is quite limiting in workflow, and a good result will take a lot longer, so then a vst like pro-q or melda dyneq is a much better choice in the end, sadly. Also the 4x times oversampling in EQ+ of Bitwig is very audible on the higher frequenies. EQ+ is super precise here, you actually can boost stuff at 20kHz (I have no idea why you should do that though). It seems to make the eqing in the higher frequency spectrum much more precise. My dream of a refreshed eq in Renoise would be on top of the current analyzer view, including those 12/24dB hp/bp, and maybe even all the filters of Renoise available, with 10 bands. Then you would have a very high precision in editing.

how can you achieve both? are you sure that you are not just using gained bands to feed some other processor in the chain which does the ‘warmth’? since no eq should sound warm (except analog emulation which have some sort of clipper/saturator at the end of the plugin chain)

wait, what?

i agree that eq+ is great. Renoise eq is also just fine, i already proposed to merge filters with eq, and make its gui resizable or docked to the analyzer on top, it would be awesome. No need to code another eq… just merge all eq/filters and make it resizable and it would be more than enough.

Well, “warmth” always was a very subjective term… I think “analog warmth” also comes from emphasizing the fundamental of a sound a bit, and in mixing, emphazising the hp’s resonance a bit. But this only works with some of the type of filters and slopes, not all. It works very well with Bitwig’s eqs. It is a special technique of eqing. I tend to use mutliple instances of an eq, one for “coloration”, one for mixing. At least that is my goal.

I did that before, too, actually you could have used search before (EDIT actually I can’t find my own post anymore, maybe it was lost while forum conversion. Or I deleted the post myself…). I read and agree with your post. The filters in Renoise are really nice, but I would say that they wouldn’t be very neutral for a general HP/LP eqing purpose. It is actually pretty difficult to use them as mixing filters. Maybe the new digital filter would be good, didn’t use it too much yet.

But let’s be realistic, until taktik does not make Renoise open source, this most likely will not happen due lack of manpower. I would imagine some project like surge.

1 Like

Bitwig is cool but if it the audio engine wouldn’t crash every 5 min with the latest version it would be nice too.

Wut why that? Bitwig engine is the most stable out there. Are you using VPSAvenger or so? Which version, what plugins? I even disabled sandbox mostly, only for some secific plugins…

I wonder if this months detailes about v3.4 will be published. This was the regular pattern in the last years, what do you think?