(strange) Consolidate behaviour - why?

Official support for: bitwig.com
Post Reply New Topic
RELATED
PRODUCTS

Post

I'm still trying out the demo. Today I recognized some strange behaviour concerning the concolidate function.
I edited (and cutted) some Audio clips in the timeline view.
(I know that normally you should use the clip edit view but it's possible so why not?). So it looked like this:
before.jpg
After that I wanted to consolidate the edited audio clips and so did I:
after.jpg
I expected that it would only merge the audio events into a new clip without filling the gaps with audio that hasn't been there before. I don't get the intention of the behaviour as it is at the moment.

Do you have an idea why it is like this? Or should it be like I expected?
You do not have the required permissions to view the files attached to this post.

Post

I think I understand what youre talking about, I never noticed it doing this to me but Ill check it out when I get back home and Ill get back to you if someone hasnt already :)
-Tristan
MacBook Pro|MacOS Sierra|Bitwig Studio 2.0
UA Apollo Twin| EVE SC207 Monitors|ATH M50x|Focal Spirt Pro|Komplete 10|Push

Post

The MIDI consolidate does similar strangeness, I posted something a few days on it. I can't figure out why it works that way with audio or MIDI.

If I consolidate something, I want it to play back exactly the same as it did in the timeline, but as a single clip.

Post

I had a similar problem - seems like Bitwig is unable to consolidate audio events? It is possible to consolidate audio clips, but not audio events i think..

Post

Hm, i can't reproduce this behaviour - it does what i expect it to do. Version 1.0.9 RC3 here, haven't updated to 1.0.10 on this machine yet.
1.jpg
You do not have the required permissions to view the files attached to this post.

Post

Can't figure out how to put more than one image per post, so:
2.jpg
You do not have the required permissions to view the files attached to this post.

Post

Redukt wrote:Hm, i can't reproduce this behaviour - it does what i expect it to do. Version 1.0.9 RC3 here, haven't updated to 1.0.10 on this machine yet.
Hm, I have 1.0.9 RC1. Maybe that's the reason. Yeah, I'll come back to this when 1.10 is out to save download time ;-)
Another idea i got when I saw your picture: Do your BD clip contain audio events that are longer than their length? (longer than a quarter?) Because I did so and consolidating included the hidden parts in the clip again...
I hope you understand what I mean. It's difficult to describe these problems in another language ;-)

Post

u-u-u wrote:
Redukt wrote:Hm, i can't reproduce this behaviour - it does what i expect it to do. Version 1.0.9 RC3 here, haven't updated to 1.0.10 on this machine yet.
Hm, I have 1.0.9 RC1. Maybe that's the reason. Yeah, I'll come back to this when 1.10 is out to save download time ;-)
Another idea i got when I saw your picture: Do your BD clip contain audio events that are longer than their length? (longer than a quarter?) Because I did so and consolidating included the hidden parts in the clip again...
I hope you understand what I mean. It's difficult to describe these problems in another language ;-)
Im on 1.0.10 ._.
You do not have the required permissions to view the files attached to this post.
-Tristan
MacBook Pro|MacOS Sierra|Bitwig Studio 2.0
UA Apollo Twin| EVE SC207 Monitors|ATH M50x|Focal Spirt Pro|Komplete 10|Push

Post

I'm on 1.0.10 win and I get the fill in the blanks behavior.

Image

Post

Ogopogo wrote:I'm on 1.0.10 win and I get the fill in the blanks behavior.
Hey thanks for testing it out. I think, it should be otherwise. Do you know how one can contact the bitwig team best so that they get the feature request? The forum might not be the best way for that ;)

One thing about not having that fill the blanks behaviour (nice name btw) would be that events (hidden 'by the blanks') could get lost while consolidating. But of course there is a solution: the programm would have to mute the hidden events. So why not change it, dear BW team? ;)

When trying out the per event mute button I found out for myself that the muted state for events isn't represented really well in the Arranger view. (Yeah, a slight gray but it really doesn't distiguish itself from unmuted waveforms...) But that's another topic...(Team BW?!)

Post Reply

Return to “Bitwig”