✔ Small Feature Requests... [Bitwig]

[nsq]

Oh... and about the step sequencer, it would be something like this:

Step sequencer is already implemented when "hide irrelevant notes" is on. We only need ghost clips for full functionality.

[carlosjcuevasm]

Oh... and about the step sequencer, it would be something like this:

Hell yes.

AWESOME!

[owensands]

Oh... and about the step sequencer, it would be something like this:

Hell yes.

And I think it's not that hard for them to create something like this.

We just need a BIG PETITION..........

no. Use the grid. Way too many other issues to be sorted.

[konXfront]

The grid isn't even fixed yet. Looping a midi clip can result in some annoying irregularities like notes from the beginning of the clip manifesting in the last part of the clip.

[powermat]

The grid isn't even fixed yet. Looping a midi clip can result in some annoying irregularities like notes from the beginning of the clip manifesting in the last part of the clip.

That usually happens when I accidentally loop-stretch the clip instead of just stretching the clip (to fit the area, the midi does not stretch).

This may be obvious, but if you right click on the clip and select Consolidate, you should be able to extend the clip and delete the note that is barely there, inside the clip.

[Regnas]

A option to disable the LFO's visualization on the knobs/parameters etc. It keeps moving even without play and can be very distracting. I also find that this knob movements are very CPU hog.

[PolaroidThePenguin]

I vouch for more keyboard utilization as well, if there is one thing darn FL Studio has got down, it's the utilization of keyboard for writing MIDI notes. This, of course, depends on your particular computer, I believe. For example, Live has got one of the worst keyboard set ups ever when it comes to writing MIDI.

Step editor... meh... easier to work with with simple rhythmical patterns, sure, but I can't have as much control over my writing with regular step editor when creating something more substantial. My drum machine gets super busy real quick, trust me. This is part of the reason why I like Ableton Live so much. Maybe you can have fl studio-like step editor as an option?

[nexttrack30]

A option to disable the LFO's visualization on the knobs/parameters etc. It keeps moving even without play and can be very distracting. I also find that this knob movements are very CPU hog.

+1

[Redukt]

Oh... and about the step sequencer, it would be something like this:

Hell yes.

AWESOME!

Yesterday i fooled around with the Sampler device's multisample function - and i thought this could be used for a step sequencer device, too...

Excuse my extremely crude photoshop skills, but this is basically what i imagined:

StepSequencer01.jpg

Yes, i took FL Studio's step sequencer...because of that nifty little function that lets you change the channel's velocity, pitch, pan, etc...

StepSequencer02.jpg

So, like the multisampler, the step sequencer would replace the clip launcher/arrange view as soon as the edit button on the drum machine device is pressed. After another button press, it becomes invisible again. Therefore people who like to work in the piano roll instead wouldn't even know it's there...

What do you think (of the sequencer implementation, not my photoshop skills, of course)?

Could be a cool addition for 3.0 or some other future version. Or could something like this even be built with the modular system in 2.0?

[Tearing Riots]

The automation system and the note editor are far superior to what i see here imo.

There´s a certain accessibility to Fruity Loops but it also makes it very hard to do certain stuff (try to play a note a bit earlier in this thing)

And the drag&drop of samples would not do much for me, most stuff in the rack gets layered and modulated-

[u-u-u]

A option to disable the LFO's visualization on the knobs/parameters etc. It keeps moving even without play and can be very distracting. I also find that this knob movements are very CPU hog.

I think the drawing isn't that CPU intensive compared to the modulation itself. I mean it only draws the visible devices and AFAIK the GUI is redrawn at a specific rate anyway.

Just an idea that came during writing: Maybe fast knob movements could be blurred so that the overall image becomes less distractive (?)

But I have to admit that momentary there are other things that are higher on my personal feature wish list.

[PHY6]

I think there's way too many fr's. In my opinion they're going way to fast, because this program is anything but bug-free. bringing in this many new features at once is bringing shitloads of bugs with it, making it harder to find the culprit. Adding new functions can break things that were working before.

I think they should focus on stability and solving the current bugs.

[u-u-u]

The automation system and the note editor are far superior to what i see here imo.

Yes, I really like how the automation and sequencing is done. Maybe there could be some refinements. But I see no need for an additional stepsequencer. Here's what you can achieve with the given tools:
+ always remember you CAN do stepped automation with the drawing tool + ALT pressed (on Windows)
+ set the note editor to drum mode to see only the (named) drum lanes

BWS 1.1.6 DrumSequencing.gif

And here's the .bwclip ->

BWS 1.1.6 DrumSequence .rar

[markussomething]

I think there's way too many fr's. In my opinion they're going way to fast, because this program is anything but bug-free. bringing in this many new features at once is bringing shitloads of bugs with it, making it harder to find the culprit. Adding new functions can break things that were working before.

I think they should focus on stability and solving the current bugs.

I second that.

[Cyoon]

probably falls under the radar anyway as long as noone sends them in to tech support