Bitwig Studio 1.3.6

[SpellBound]

There is a couple bugs exists:
First. Drug and drop of any audio file on free place from the side browser does not create a new audio track.

I can't reproduce that. OS X yosemite

working fine here as well

I see drug and drop works fine in your case. But drugging up or down corners have to make different options (making the audio container longer(up), creating the loop (down)

[Cyoon]

yes, you have to turn off the loop button in inspector. I'm not too sure, but i think, formerly it automatically turned off the loop when dragging from the right upper corner.

If that has actualy changed it would be a bug then i guess. Did you report that?

[mosska]

There is a couple bugs exists:
First. Drug and drop of any audio file on free place from the side browser does not create a new audio track.

I can't reproduce that. OS X yosemite

working fine here as well

I see drug and drop works fine in your case. But drugging up or down corners have to make different options (making the audio container longer(up), creating the loop (down)

YES! i talked 'bout it to Dom or somebody from the bitwig crew and i was told that it had been like that all the time. BUT as far as i remember, formerly it was like that: you grab upper line and it goes container, you grab down line and it goes looping. But it got changed and now i have to turn off or on the loop, depends on my need. it used to be automatic.

[xbitz]

GUI refresh is broken, macro > faders assignment

[vondersulzburg]

There is a couple bugs exists:
First. Drug and drop of any audio file on free place from the side browser does not create a new audio track.

I can't reproduce that. OS X yosemite

working fine here as well

I see drug and drop works fine in your case. But drugging up or down corners have to make different options (making the audio container longer(up), creating the loop (down)

YES! i talked 'bout it to Dom or somebody from the bitwig crew and i was told that it had been like that all the time. BUT as far as i remember, formerly it was like that: you grab upper line and it goes container, you grab down line and it goes looping. But it got changed and now i have to turn off or on the loop, depends on my need. it used to be automatic.

Hi, I am on Latest Mac os and 1.3.6 and on my MAC it works as ever before. Upper half of the clip makes the clip longer lower half of the clip loops it.

But sometimes it last to or 3 try to get this behavior. When you come from the right side of the clip and move a very small bit over the right end of the clip to the left it always is the sign for making the clip longer without looping

[Cyoon]

in early days one wouldn't need to move it slightly to the left imo, but could be wrong.

Ah, i think i just work too infrequently with audio
The behaviour with MIDI clips is actualy different to the one with Audio clips.

With midi clips there is no autoloop, why is that?

[codec17]

FIXED - Controller API: crash when using device layer bank.

Push hangs, or bitwig crashes big time when entering fx-layer overhere,. W7 x64.
(did send report)

[takaii]

There is a couple bugs exists:
First. Drug and drop of any audio file on free place from the side browser does not create a new audio track.

I can't reproduce that. OS X yosemite

working fine here as well

I see drug and drop works fine in your case. But drugging up or down corners have to make different options (making the audio container longer(up), creating the loop (down)

YES! i talked 'bout it to Dom or somebody from the bitwig crew and i was told that it had been like that all the time. BUT as far as i remember, formerly it was like that: you grab upper line and it goes container, you grab down line and it goes looping. But it got changed and now i have to turn off or on the loop, depends on my need. it used to be automatic.

Hi, I am on Latest Mac os and 1.3.6 and on my MAC it works as ever before. Upper half of the clip makes the clip longer lower half of the clip loops it.

But sometimes it last to or 3 try to get this behavior. When you come from the right side of the clip and move a very small bit over the right end of the clip to the left it always is the sign for making the clip longer without looping

What is hard to understand about looping a audio or midi clip?
I will explain the behaviour that bitwig allways have had as far as i know.
In preferences you can set-up when putting in audio from browser in arranger
to be raw or streched by determing if clip is longer than and shorter than

1.png

What does this has to do with automatic looped clip?
Well actually if you put in a clip that will be raw, then loop will not be active.

If you put in a clip that will be streched that you set-up in preferences when clip is a certain length,
then loop will be active on that clip.

By selecting clip and having inspector on left open you can see if loop is active, and even turn it off there.

2.png

It is true about up right corner, draggin up corner or the right side of clip will make clip longer (if loop is not active)
dragging right down corner will activate loop on clip and loop from that point set.

If you looped a clip and want to change how short or long the intervalls is then do this as gif, drag the doted line in arranger left and right and you change the length of intervall of loop

loop length.gif

youn can also decide the lenght of intervalls through clip editor, be sure to have "edit content of individuall clips active", meaning you only see the selected clip in editor and not the entire arranger in editor.
as i cant add more pictures than three ill try to explain how, in editor shift tab or e(if capslock active alt+e),you see on top of the editor that there is a loop bar or what to call it. by changing that you change the length of loop intervall also.

i hope this will make better sense on how looping works.

And about midi not being automatic looped in arranger is because its not set to raw or streched, and bitwig has no length longer then or shorter then to be looped automatic.
However creating a clip by doubleclicking in cliplauncher will automatic be looped, or if you have a clip in arranger that is not looped and you move it to cliplauncher it will automatic be looped, if you decide to drag that clip back into arranger in a later place loop will stay active.
If that is not decided just turn loop of in inspector after you put in clip, also you can turn it off in inspector for clips in cliplauncher also(i).

2.png

moving a AUDIO clip from arranger to clip editor will also be looped even if its not looped in arranger, but draging a clip from the browser will depend same as you set preferences

1.png

bounce and consilidate with loop active
when you consilidate a clip (both midi and audio) in cliplauncher and arranger, loop will if activated be deactivated. So if you want loop deactivated on clip in cliplauncher a quicky would be to consilidate
If you bounce in cliplauncher (both midi and audio) it will stay looped and audio that is not looped will stay inactive. Bouncing audio and midi in arranger with loop active will turn loop off, it becomes one long file instead.

One tip, if you have long files but its repetetive with no changes, note difference, velocity and same movement, bounce out 1 file instead of long files. Loop that file or dublicate, this will save workspace. If you have samples used in project or old bounced files saved with project, go to project tab and at low bottom press "delete unused" (Y)

[nickallen]

there is a http://www.kvraudio.com/forum/viewtopic ... 9&t=455342 Preview samples popping topic, just dropping here too



please fix it

I think I found the cause of this one. It seems some wav files have metadata after the end of the audio data and in some cases we read a few bytes beyond the end of the audio data (which we should not). So this metadata is getting interpretted as audio data. I think I will have a fix shortly. Thanks for reporting!

[takaii]

nickallen, BUG! on midi tracks, PUNCH-OUT stop recording before loopmarkers end and leave a bit space. Check gif and you understand.

punch out.gif

[der_r]

I was working on a track today. Among many of the bugs from the RCs and bugs other people have mentioned here, this is what happened:

After about two hours I saved my progress, closed down Bitwig and took a break. When I opened it back up, my track sounded muddy. I opened the EQs and compressors (Fabfilter) and they all came back in the default settings.

After about two more hours, Bitwig turned into a solid white window.

I was very sceptical after 1.3.6 got released so shortly after the buggy RC's. I love Bitwig, but how much time do you spend testing your releases? I mean both traditional unit tests built on past bug reports, a variety of test computers and actual music producers who use it to make tracks. It's tough to recommend Bitwig to friends if your users feel like your sole testers.

[Edit]

I just tested if I could reproduce the bug by creating an empty project with nothing but a Fabfilter compressor and some random values. After reopening the project all settings were still fine. This means something inside Bitwig must have caused the bug while using it during the two hours. Which basically means I can't safely use it for longer work sessions because you don't know what triggers this behavior.

[anp27]

This means something inside Bitwig must have caused the bug while using it during the two hours. Which basically means I can't safely use it for longer work sessions because you don't know what triggers this behavior.

Huh? I was working on a track today for more than 2 hours. It sounded exactly the same the whole time.

[der_r]

This means something inside Bitwig must have caused the bug while using it during the two hours. Which basically means I can't safely use it for longer work sessions because you don't know what triggers this behavior.

Huh? I was working on a track today for more than 2 hours. It sounded exactly the same the whole time.

The bug happened after closing and reopening Bitwig. Either the EQ and compressor settings didn't save or can't be read back... when I check, all instances of them are blank.

[PORTMAN_DNB]

Same is happening to me . Sometimes I get a white screen. I then have to reset my laptop completely because you can't even see the task manager to close it down. Also my patch in harmor resets to default. But if I go to and earlier saved version the patch is still there working fine. I don't even know how to reproduce as this just random.

[PORTMAN_DNB]

I did think this was because of my laptop but it happened on my iMac running Windows. In the end I had to remove harmor completely because it wouldn't load and play at all.