asked Oct 30 '14 at 19:07 by Lachmund (226)

17
7

Is it true, there is still no option for track delay in Bitwig? This is an essential feature for me.

We do have recording offset and plugin latency correction. The first releases introducing these were a bit bumpy, though, because we had some regressions where the new features got missing etc. This should be fixed - and stay fixed - in the next upcoming versions.

There probably also are a few bugs in these very new and complex features, which we'll be rooting out, please have a little patience :)

Have fun with Bitwig Studio!

  — (Mar 09 '15 at 13:32) riot ♦♦

Unfortunately I just recently got an answer from the support and they don't plan to implement this feature in the future. Very disappointing.

"Hello M,

a track delay is not planned, as a negative track delay causes the same amount of negative delay as latency to other tracks. If you want to shift events back or forth, you should do this on the actual events on the sequencer level (notes, audio events, clips) instead of delaying the whole track in the mixing engine. Additional information can be found in this thread: http://www.kvraudio.com/forum/viewtopic.php?f=259&t=433877"

  — (Mar 30 '15 at 18:33) Lachmund

12next page »

Bitwig guys. Please address this issue. This is EXTREMELY irritating.

Having a negative track delay is essential for running outboard gear to compensate for the round trip latency. It is impractical to place an audio delay on all tracks just to get a negative delay on single track. A global shuffle is great but to achieve accurate results, a negative track delay is essential. Typically percussion samples have a 1-10ms zone just before the transient. Not being able to align that transient with adjacent tracks causes additive/subtractive phasing issues that could easily be remedied if a negative delay was possible. Ableton and Logic have always had this. Sure I could edit the sample start time but I want to retain the character of the original sample.

After 7 or so updates, I find it disheartening that this feature is still missing. I hope there isn't anything fundamental in the software architecture that precludes this from being implemented.

Again. Please incorporate a track delay that includes a negative delay. -50mS to +50mS would be acceptable. Samples rather that mS would be preferable.

Thanks,

Kenneth Graham

link

answered Jan 12 '15 at 02:58 by KennethGraham2014 (114)

having a choice between ms and samples would probably be the way to go. I am use to add some ms on an "offbeat" snare.

Definitely a very essential tool to have ASAP

  — (Mar 28 '15 at 23:42) run2hype

Unfortunately I just recently got an answer from the support and they don't plan to implement this feature in the future. Very disappointing.

"Hello Matthias,

a track delay is not planned, as a negative track delay causes the same amount of negative delay as latency to other tracks. If you want to shift events back or forth, you should do this on the actual events on the sequencer level (notes, audio events, clips) instead of delaying the whole track in the mixing engine. Additional information can be found in this thread: http://www.kvraudio.com/forum/viewtopic.php?f=259&t=433877"

  — (Mar 30 '15 at 18:31) Lachmund

Time Shift tool.

You can shift audio / instrument track forwards or backwards: -/+ 500ms or -/+ 2048 samples.

link

answered Jan 31 at 10:13 by niedobryjasiu (113)

Bitwig 2 has delay compensation for the external hardware devices, but it still doesn't have it at the track level. Has anyone figured out a clever routing scheme to get negative timing offsets going on a track-by-track basis?

I feel this is such an important and musically critical feature. Case in point: sequenced shaker tracks. The shaker sound has an initial attack that rushes the beat. Finding the right groove requires some experimentation and feedback. Moving around note events is not a solution because it's fiddly, error prone, and results in a sequence that has lost all grid information.

link

answered Mar 22 '17 at 02:31 by bugeats (41)

1

It's really unfortunate this still hasn't been addressed. The only solution I found is to zoom in extremely on a clip or event level, to like 65000 resolution or so, and move the start point to the left a few bits. It's tedious and still kinda unprecise but it's a workaround.

Bitwig really needs to implement this feature on a track level. All major DAWs have it and it makes it hard to use on a professional level.

  — (Mar 22 '17 at 09:20) Lachmund
1

Fully agreed. The request here is not necessarily delay compensation.

Music is all about timing and getting it right is everything. You do this by ear, moving things forward and backward in time in very small increments. You really don't want to do it on the sequencer level because you still want the midi notes to be on the proper beats because it's easier and better to work that way. Positive track delay you can achieve with delay plugins but mostly only above 10ms or more. Negative track delay is impossible to achieve manually because you'd need to move all other tracks forward milliseconds

  — (Mar 22 '17 at 19:49) norbert
1

Also track delay would be super useful for playing around with phase alignment. Currently you need to bounce the instrument track to audio only to move it around manually using the mouse. It's a waste of time and effort. If there was track delay available in the mixer on the track level you could adjust the track with ease backwards/forward until you get proper phase alignment even with instrument tracks.

  — (Mar 22 '17 at 19:52) norbert

"Hello M, a track delay is not planned, as a negative track delay causes the same amount of negative delay as latency to other tracks. If you want to shift events back or forth, you should do this on the actual events on the sequencer level (notes, audio events, clips) instead of delaying the whole track in the mixing engine."

This is a copout. Of course adding negative delay adds latency. We are professionals who understand the tradeoffs and we need software with professional features.

  — (Mar 23 '17 at 03:52) bugeats

As a software dev myself I'm going to guess that they failed to build the audio engine with negative offsets in mind, and it's probably a daunting task to fix it -- hence the rationalizations.

  — (Mar 23 '17 at 03:52) bugeats

+1

agree with that !

link

answered Jan 27 '15 at 22:28 by Tres_Bien_Plus_Plus (21)

Same Here, I can't synchronise correctly my Roland TR8 -> (USB) -> BWS : the TR8 audio buffer creates a delay that I can't correct with a negative delay inside BWS. More than annoying, this makes my TR8 unusable with BWS. Would love to use BWS for live gigs, but this track delay is a blocking point for me to switch to BWS.

link

answered Feb 07 '15 at 13:02 by guyhom (21)

edited Feb 07 '15 at 13:02

1

Did you actually check the recording offset setting in the preferences?

  — (Feb 12 '15 at 16:55) riot ♦♦

Yup. Acutally I need more than a simple track delay : My Roland TR8 needs a certain delay, but I have other hardware machines that could require a different delay (SE 1X, DSI Evolver, MachineDrum, Matrix 1000 and so on). So I need to be able to adjust a midi delay (+/-) for each midi In/Out, and adjust a delay (+/-) for each track. It's the only way I can synchronise all these stuff together with a maximum precision.

  — (Feb 27 '15 at 23:13) guyhom

HARDWARE FX IS NOT DELAY COMPENSATED AT ALL FIX IT VERY ANNOYING

link

answered Feb 12 '15 at 09:09 by salganikas (51)

edited Feb 12 '15 at 09:11

2

Hey guys - yes we're aware of a few issues and are fixing this. All will be good!

  — (Feb 17 '15 at 13:54) riot ♦♦

I just posted an idea to the KVR forum that it more related to this transient correction usecase of a per-track delay: http://www.kvraudio.com/forum/viewtopic.php?f=259&t=433877#p6071088 Already sent that idea to tech support. Hope they will somehow implement that...

(For the hardware issues there should be a more elegant (automatic and not manual) solution. But as riot wrote they seem to be aware of it...)

link

answered Mar 11 '15 at 12:58 by Triple-U (56)

Its true for current beta and production version (1.x and 1.1b).

link

answered Nov 01 '14 at 18:59 by Solidtrax (919)

Same here. Really need the option to push tracks by milliseconds. Working with lots of hardware.

link

answered Dec 12 '14 at 23:15 by hazeltine (11)

There is a workaround if you need a track delay of 10ms or more:

Use the delay-1 device without feedback (0%) and a full wet setting (100%) btw: Less than 10ms or negative delay is not possible yet.

link

answered Dec 15 '14 at 17:04 by Solidtrax (919)

edited Dec 15 '14 at 18:33

1

thanks..negative delay unfortunately is what I miss the most

  — (Dec 15 '14 at 20:09) Lachmund

Check the recording offset.

  — (Feb 12 '15 at 16:55) riot ♦♦

The recording offset doesn't work for single tracks...it's just a global value which might be ok for certain cases but doesn't adress the problem.

Other DAWs like Ableton, Logic or Cubase do have this function.

  — (Mar 09 '17 at 18:12) Lachmund

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×24
×10

Asked: Oct 30 '14 at 19:07

Seen: 5,638 times

Last updated: Feb 01 at 19:05