Problem with "Next Scene" action - possible Bug in Bitwig 5.1.2?

[bombasstard]

Hi there,

following setup:

Scene 1: Next Action = "Play Next".
Scene 2: Looping
Scene 3: any

I configured a Keyboard Shortcut for the action "Play next scene".

This is, what I would expect:
* Start Scene 1
* Scene 1 runs through the end
* Scene 2 is started automatically
* let Scene 2 loop until you feel to go on
* trigger Keyboard Shortcut for "Play next scene"
* Scene 3 is started following its Q-Launch settings


This is, what actually happens:
* Start Scene 1
* Scene 1 runs through the end
* Scene 2 is started automatically
** you see the "active scene marker" in the UI still sitting on Scene 1
* let Scene 2 loop until you feel to go on
* trigger Keyboard Shortcut for "Play next scene"
* Scene 2 is restarted from the beginning
** now the "active scene marker" in the UI moves to Scene 2
* trigger Keyboard Shortcut for "Play next scene" again
* Scene 3 is started
** you see the "active scene marker" in the UI moves to Scene 3

I don't think this is correct behaviour, do you?

---

Background:
I have a bigger project where I play some parts after the other, as the song is written. Then I have Scenes, that just loop with some samples, where I improvise on Guitar or Synthesizer. When I think, I am done, I want to trigger "next scene" using a HID controller that I have configured to the "next scene" action to go on with the next part(s) of the song.
I have more than one looping/inprovising part in this project.

Here is a video demonstrating it:


The sample project for this video is provided as attachment.

next_scene_bug.zip

[pdxindy]

I don't know if it is a bug or planned to be that way.

Perhaps email support and ask them to add an option for the behavior you want. In the meanwhile, there are key commands for Scenes 1-40 so unless you have more than 40, you can assign commands to launch the specific scenes you want to launch manually.

[bombasstard]

I don't know if it is a bug or planned to be that way.

I don't know either. Because of this I have asked the question here in the forum, maybe I am assuming wrong

Perhaps email support and ask them to add an option for the behavior you want. In the meanwhile, there are key commands for Scenes 1-40 so unless you have more than 40, you can assign commands to launch the specific scenes you want to launch manually.

I have already submitted a mail to support for that.

The solution with "Start Scene X" would work for exact one project - in the next, my "impro loop" scene is at another slot ...

[bombasstard]

I have found another thing where the "current scene cursor" does not work.

I attached an Ableton Push 2 controller to my project, set the UI to "Session / Scene" mode and let Scene 1 pass.
Same thing here: in Bitwig, Scene 2 is running - in Push 2, Scene 1 is still marked as active.

Maybe @moss does know something about that?

[bombasstard]

Ok, support answered.

As I understand, this is not a bug but "functions as designed".
One can not enter "Next actions" for Scenes - they are only applied to the clips belonging to that scene.

That's disappointing for me, so I can not use Bitwig that way ...

[koalaboy]

Being able to have true scene follow actions, along with (even better) being able to sequence clips from the arranger timeline, would be a great improvement.

[nowiamone]

Real follow scene actions, without dummy clips, are on my feature wish list, yep.
But also: Being able to assign scene-Selections! You can't midi-map Scene-Selections! Just the launching of Scenes. That's pretty bad for a huge liveset, where you want to jump to different songs quickly via external controller.

Other live performer related wishes are:
- being able to midi map Device Activation. Not talking about bypass, but activate/deactive, which unloads them out of the RAM and gets rid of their latency! This can't be midi mapped to individual plugins, which is really really really disappointing. Yes there's that Alt+A shortcut, but that's not helpful at all for a big liveset with dozens of different effects and vst instruments which could be handled with the press of ONE button (e.g. a custom made "low latency mode" working on the fly via external controller).
- being able to midi map Device Selection. In Ableton, you could midi map the header of devices, so it would get selected when pressing a button on external controllers. It would be really helpful for live performers, because you can double assign it: when changing filter parameters for example, Abletons view immediately switches and shows the corresponding filter!! This is really helpful.
- The thin white Clip-playback-progress lines are not visible enough when further away from the laptop in a live setting. Should have the option to increase their strength or even another method of showing clip playback progress, like filling up with brighter/darker color.
- The Clip-playback-progress should optionally also be shown on Track Level. It is really nice to be able to see the progress within each clip, but as soon as a live performer scrolls in his/her liveset, there is NO MORE visual feedback at all about the current playback progress. Unlike in Ableton, where you see playback progress independently from your current position within the cliplauncher.