Bitwig Studio 1.1beta6

[shadiradio]

Would recommend having a single key be the command for this - especially as it can get very heavy use when editing notes in the piano roll - I will sometime duplicate a midi clip to multiple tracks and go through muting/unmuting a slew of notes in each one, experimenting with different combinations of instruments playing different notes from the same clip.

+1

I would prefer it was a single key, as I also often mute/unmute notes in the piano roll like nechronics. In Live it's just the "0" key and it was such a good friend. The single key could be used to mute/unmute selected notes or clips.

[shadiradio]

Is there a reason why this routing is not allowed?

Track1:
Kontakt multi-out

Track2:
Midi out to Track1>Kontakt>Ch1
audio receiver from Track1>Kontakt>St1

It won't let me "receive" audio from the track to which I'm outputting midi to. As in beta5, I'm trying to figure out how to not create a ton of tracks (double) to work with a multi-out kontakt rack.

[volker@bitwig]

Is there a reason why this routing is not allowed?

Track1:
Kontakt multi-out

Track2:
Midi out to Track1>Kontakt>Ch1
audio receiver from Track1>Kontakt>St1

It won't let me "receive" audio from the track to which I'm outputting midi to. As in beta5, I'm trying to figure out how to not create a ton of tracks (double) to work with a multi-out kontakt rack.

That sound like a bug to me, maybe the software thinks there is a feedback loop because of the MIDI connection. You say "as in beta5", was it different in beta 5?

[volker@bitwig]

Hi guys sorry for this question but can't seem to find it anywhere in 1.1. Is there actual Grouping Tracks now in this version. I know you can by routing to an audio track.

Another question any of you guys have a problem with slate tape plugin. Gui is not opening. The plug In Opens but half the gui does......so it's unusable.

1.1 is running pretty good now.

Thanks

Yes, the plugin looks like this here - 80% of it is shifted out of screen:

Thanks for reporting, we'll look into it.

[shadiradio]

That sound like a bug to me, maybe the software thinks there is a feedback loop because of the MIDI connection. You say "as in beta5", was it different in beta 5?

Oh, no sorry about that. I mean I was also trying to accomplish this in b5. Actually in b5, it would let you choose this routing, but immediately crashed. I see that bug is fixed (in the release notes) for b6, but now it won't let you choose it. I'll record a quick video and post a bug report.

Edit: here's a video of the issue:

[c-wave]

Was talking about this in another thread; it seems deactivating a clip is just muting it? In that case why have the option to "deactivate" at all, why not just mute? It's weird to hit "deactivate" in the menu and the mute button goes on, two names for the same thing.

It's the same thing, just badly labeled, we plan to have the naming of mute/deactivate and also the shortcuts cleaned up in the next beta version.

Dear Volker, It's not just a matter of renaming the labels:

1. On Arranger view: Deactivate a clip should disable that clip (to save CPU power) and not mute it which is what happens now, hence the utility of having a *deactivate clip* instead of just muting the clip.
2. On Clip launcher view: deactivate the clip is also muting the clip, but in addition the clip should dim in the same way a clip dims in the Arranger view but it does not.
3. Activate/Deactivate Scene has no visual feedback whatsoever; it doesn't even dim the clips on that scene.

[owensands]

Tracking my gear using midi time code is still not on the grid in BETA 6. was confirmed by dom that something went awry with PDC engine in 1.1 BETA. Said it would be fixed in next beta release(that would make it 6). For 1.0.15 and lower it was always bang on the grid for me within a 1/1024 note. Now its up to 1/128 note early or late depending whether I have recording compensation ticked.

I am on win 7 64 bit
RME madi hammerfall.

Thanks!

[Ogopogo]

1. On Arranger view: Deactivate a clip should disable that clip (to save CPU power) and not mute it which is what happens now, hence the utility of having a *deactivate clip* instead of just muting the clip.

Could deactivating clips actually save a significant amount of cpu? Hard to imagine that it does. If not then just having mute is simpler.

[c-wave]

1. On Arranger view: Deactivate a clip should disable that clip (to save CPU power) and not mute it which is what happens now, hence the utility of having a *deactivate clip* instead of just muting the clip.

Could deactivating clips actually save a significant amount of cpu? Hard to imagine that it does. If not then just having mute is simpler.

Yeah you're right..well maybe by a very small deal but its insignificant in the small test I made.

[P_Wig]

Beta 6 is better. Crashes when deleting instrument tracks with VSTs fixed. Bitwig no-quit bug fixed. Stylus RMX sets up multitimbral immediately upon dropping it in. Still, no drag and drop of midi files into Bitwig from RMX, and I can only create a few instrument and audio tracks. The command greys out in the drop down menu. If I want more tracks, I have to drop an instrument or audio file into Bitwig. Also, Save is greyed out too. Can't save anything.

I really need that drag and drop action for RMX. It's one of my main go-to apps.

Macbook Pro 2.83ghz.
8gb ram
OSX 10.8.5
TC Electronics Desktop Konnekt 6
iConnect Midi2+

[nexttrack30]

i agree with nechronics and shadiradio for

# just one short cut key for both deactivate and activate.

# only 1 character for activate/deactivate short cut key.
ctrl+alt+d is inconvenient for this HEAVILY used function.
no ctrl, alt, or shift please
(hopefully left area of keyboard since most used short cuts are all placed in left area)

[Megamez]

Experiencing audio drop outs here and there with the latest version of asio 4 all through a line 6 tone port ux1 (bitwig does not pick it up) when using sytrus vsti 32 bit when I play through an arpeggio on my midi keyboard and launchpad. I don't have this problem in fl 11.1 64 bit with the same audio settings (standard sample rate and 128 buffer) and I used the vsti within fl to reproduce the exact steps. I sent in a ticket. On a Lenovo ThinkPad y500 Intel 3630qm processor windows 8.1 line 6 tone port ux1

[xbitz]

if a clip is selected by ctrl+l the working area isn't be refreshed anymore

win8.1, b6

[xanthos]

yeah, finally drag and drop from internal browser to Battery and Nerve are working! Thanks Bitwig Team for that!

[kurasu]

Is there a reason why this routing is not allowed?

Track1:
Kontakt multi-out

Track2:
Midi out to Track1>Kontakt>Ch1
audio receiver from Track1>Kontakt>St1

It won't let me "receive" audio from the track to which I'm outputting midi to. As in beta5, I'm trying to figure out how to not create a ton of tracks (double) to work with a multi-out kontakt rack.

Yes this is by design. The MIDI out you're routing from track 2 to Kontakt is the signal taken at the end of the signal chain, so you can't possibly insert a device depending on Kontakts output before that point without introducing feedback. Besides, you wouldn't have a way of actually getting the audio out of the track as the output routing chooser is used for you MIDI routing.

Also our engine is based around tracks being used as the atomic unit for multiprocessing, so it's not possible to do any back & forth connections between two tracks as one has to be completely processed before the other one can start processing, so they can't both be dependent on each other. This is the reason beta 5 hung when you did that connection there - both tracks essentially waited forever for the other one to finish.