git-moss / drivenbymoss Goto Github PK

The encoder sensitivity for the scale selection is IMO too high. It's quite hard to select a certain scale and leave the selection in place when releasing the encoder, because releasing it often causes another jump in the selection.
You have recently adjusted the sensitivity for the encoder use in the browser view, thanks a lot for that, is really so much better now! But it seems that the scale selection needs a similar treatment. Again I suggest: Can't we have a knob sensitivity setting in the preferences, and use a common debouncing mechanism based on that value for all the encoders?

I didn't find in the bitwig java api a function to get the default value of a parameter.
Do you know?

Otherwise I'd like to build a OSC url /device/param/x/defaultValue

When I click on the solo/mute buttons on a layer in a drumpad, no OSC messages are being send out.

Hey there,
Using the APC 40 mk2,
It would be amazing if i could adjust the length of notes in a sequencer the same way i select the pages to be played (hold the first and last notes to determine length). This way i could easily program in more complex patterns

Add a track deactivate it and hide it with the x on bitwig and it remains visible on the tablet. Should disappear from view I would think.

Also hiding deactivated tracks on a large file crashed your script once. But it didn’t say it crashed. But the clip window disappeared and wouldn’t come back until I restarted bitwig.

Requires function to mute steps.
teotigraphix/Framework4Bitwig#263

make an fx layer fill it with one empty layer and three layers with effects ( for parallel processing )

entering the layers with effects works fine

I can enter but can't exit the layer with nothing in it.

Bitwig studio 2.2.3 registered, downloaded from Bitwig studio website.
Up-to-date macos el capitan.
DrivenByMoss from here: http://www.mossgrabers.de/Software/Bitwig/DrivenByMoss.zip and installed according to the docs

Steps:
Start Bw, Go to controllers preferences, load OSC extension, choose virtual midi (IAC 2 for my case), set listening port to 8016, set sending port to 8017 (both hosts to 127.0.0.1), deactivate extension, reactivate extension.

Now in terminal:
sudo lsof -i | grep Bitwig
output: only IPV6 bindings, and none on the 8016 port.
Two on UDP ports:

• UDP *:irdmi
• UDP *:54130

Fire Puredata, create a simple [udpreceive 8017] -> [unpackOSC] -> [print].
Result:
Everything from osc4bitwig is received and printed to the Pd console.

/edit

The sending Pd test:

when pressing the [send /play 1(, the result is no effect in Bitwig, and when pressing a second time, "udpsend send: Connection refused (61)" in Pd console.

I remember that your BW script was in different language before. JS, if I'm not mistaken.
Not it's a one big archive - *.bwextension. I tried to open it and found .class files.
I'm specifically interested in SLDisplay.class.
As far as I understand, you've already implemented a method to reduce plugin name strings, so they would fit into 8 character fields on the SL's LCD. I wonder what function/set of rules did you use for that task.
Like, leave numbers untouched, leave capital letters, delete vowels and so on.
Could you, please, share your approach with me?

Wrong call for this method.

Should be;

 return this.mixer.isCrossFadeSectionVisible().get ();

Hi, I'm using a Push 1 with Bitwig 2.1.3 on Windows 10 64bit.

I'm seeing weird layouts for some scales when in chromatic mode, specifically Locrian, diminished, whole tone, minor blues, minor pentatonic, major pentatonic, super locrian, Hungarian minor, Hirojoshi, in-sen, iwato, kumoi, and pelog. Based on what Ableton does at least, these should all keep the standard chromatic layout (each higher octave is two over, two up) and just change which white keys are lit.

Also, I think there should be another half note scale degree in the whole-half scale. Both chromatic and in-key modes are affected.

Much thanks -- Andy

1. Debug window: Remove the maximize icon, implement the close icon and add a state to image (isWindowVisible()).

Nice to have:
2) Functions for getting default colors and icons.

Requires function to delete automation.
teotigraphix/Framework4Bitwig#262

Note: Since Bitwig 5.1 there are now the actions:
delete_all_project_automation:Project:Delete All Project Automation
delete_all_automation_owned_by_selection:Project:Delete All Automation Owned by Selection

First one needs to have the track selected and it needs to be focused.
Second one requires a dialog confirmation.

hey I was trying to implement a single fader for device layer volumes like this

but it doesn't seem to work, maybe its not possible?

I could do a modal with the faders in there too

As the title says: the 12 very top and 4 very bottom sample slots in Drum Machine can not be reached via Push's Octave up/down buttons. An improvement would be nice.

An Idea could be the use of the Shift-button together with the Octave-buttons to jump only 4 notes/slots up or down instead of 16.

Transport displays beats as '1.1.1'

/beat/str sends '0.0.0'

OSC received: { address: '/beat/str', args: '0.0.0' } From : 127.0.0.1:5995

When the selected track is 8, and you do /track/+

java.lang.ArrayIndexOutOfBoundsException: 8
at de.mossgrabers.framework.daw.AbstractChannelBank.getTrack(AbstractChannelBank.java:93)
at de.mossgrabers.osc.protocol.OSCParser.parseTrackCommands(OSCParser.java:723)
at de.mossgrabers.osc.protocol.OSCParser.handle(OSCParser.java:229)
at com.bitwig.flt.control_surface.opensoundcontrol.BQr.HBU(SourceFile:316)
at com.bitwig.flt.control_surface.opensoundcontrol.BQr.HBU(SourceFile:293)
at com.bitwig.flt.control_surface.opensoundcontrol.hzb.HBU(SourceFile:109)
at QYT.faG(SourceFile:237)
at ti1.run(

Requires access to a list with available in-/outputs and setter/getter methods..

Requires: teotigraphix/Framework4Bitwig#20

Is there no way to just make a pull request for the following changes?: 70084c7

Functions required.
Are already actions available?

Bitwig v2.1
linux Mint 18.1

using the new v5 script installed into ~/Bitwig Studio/Extensions my Akai APCmini worked first time but then refused to work at all no matter what I tried. $ lsusb identifies the device and dmesg|tail shows it enumerate, and I can read data from it (e.g. using midisnoop).

[edit 22/5/17 - it is possible that this "first" detection was due to BW seeing the device via the earlier v4 script which I had installed in readiness, and subsequent removal of the v4 script has resulted in not being able to detect the controller]

Installing the older v4 script in ~/Bitwig Studio/Controller Scripts and deleting the v5 "DrivenByMoss.bwextension" ... restarting BW immediately autodetected the APCmini and it worked well.

Trying the v5 script again, back in its correct location, and BW couldn't identify the device. Manually installing the device from the dropdown list shows the "DrivenByMoss" version to be available, but when I install it and configure it, the controller doesn't work. No lights, no onscreen response.

There seems to be some conflict between Alsa and Jack and APCMini - Alsa as the driver model allows v4 APCMini to be autodetected. Jack as the driver model does not allow BW to autodetect. Using v5 i(n either case) fails to be detected

BWS v2.1, using v4 APCMini script - the clip buttons seem to be swapped round such that the top row of buttons on the controller actually triggers the left hand vertical column in BWS.

(Can't test with the v5 script - maybe that's already taken care of).

Bearing in mind I am a BWS novice and a clip controller novice, the mistake may easily be mine.

I changed the default ports but this has no effect. Bitwig still registers ports 8000 and 9000, whatever I set it to in the settings.

Requires: teotigraphix/Framework4Bitwig#44

Display the names of the first 4 rows of clips in the display.
Not possible due to: teotigraphix/Framework4Bitwig#178

Presets can be switched with /device/param/+ and /device/param/- .
Can you please send out the name of the chosen preset as well when this change happens?

Requires fix: teotigraphix/Framework4Bitwig#124

I had an up arrow mapped with plus and and it moved the selected position down. minus goes up.

I think its because each layer is named plus one going down as you add them

no big deal I just swapped it but might be good to switch on your end to match bitwig?

Automation control set to touch doesn’t really work with tablet. When I release the fader it doesn’t go back to where it started. It also just continues to write automation at the level I let go of it. Is this your experience Moss?

Also it doesn’t really function well in Bitwig Studio on the computer. If you move the fader there the automation line moves back to original position when released but the fader on screen stays put.

On a polysynth and using the aftertouch url ( /vkb_midi/{Channel:0-16}/aftertouch/{Note:0-127} {Pressure:0-127} ), the last note pressed keeps playingn and the extension crashes.

I'd like have a OSC url to fetch the name of a drum/pad, if not too much work.

Hi Moss. Thanks so much for all your work on the new Java controller scripts.

I really like the way grouped tracks can be collapsed/expanded.

Has the 'user' controls functionality been removed? When I press the USER button it selects send2. Is this a bug or a feature?

Also in the previous version of the script I was able to map the device controls, whereas now if I map those, they behave a bit randomly. Sometimes they work correctly, sometimes the value is locked to 0, and sometimes the value jumps back to 0 after a certain amount of time.

Scenes currently don't have a play state.

Could be indicated if all clips of the scene are playing?

I think everything is in the title.

The OSC controller script is pretty complete as-is, but I'd like to be able to remotely edit a clip using OSC.

What do you think about it ? Is it feasable ?
I see this in the Scripting docs:
/Applications/Bitwig Studio.app/Contents/Resources/Documentation/control-surface/api/a00032.html

I would like to have a /track/selected/hasParent so I can conditionality show a /track/parent button.

Wondering if anyone else is experiencing this. I have 9 tracks open,when I try to switch from track 8-9 the clip bank moves from 1-8 to 2-9 but instead of the track selection jumping to track 9 it jumps back to track 9 and I have to scroll all the way through the new bank. This has only happened since 2.2 I believe.

Any help would be amazing. Thank You.

Requires teotigraphix/Framework4Bitwig#192

Hey,let me know if there is a format you prefer here and I’ll make sure to use that as I find issues.

Vu meters don’t react to live audio being recorded

Arm track with live input of voice or guitar and Vu meters are dead

Requires a stable clock / timer from Bitwig.

Requires teotigraphix/Framework4Bitwig#59

I would like to have a scale factor for the encoder sensitivity in the preferences. For my fingers, the knobs answer far to quick, which makes e.g. using the browser to skim search through the presets a real pain - the slightest movement of my knob finger, or even just releasing it from the encoder, changes the dialed in value (in this case the preset). So I suggest having a scale factor in the preferences to 'slow down' the encoders to personal taste.

I am running linux if this matters

Hi, Jurgen. I have a question about this controller.
What's the reason behind the following behaviour:
If some info was displayeв on the LCD, it would stay there, but only until any of the faders was moved or a button from one of the two rows on the right side is pressed. Then, "Automap is offline" is shown.
This doesn't happen if pressing any other button or touching any controls.
I've tried to inspect your script and Ableton one for the answer, but couldn't find anything.
Help, please.

When I play a part of a drum, I don't get the volume/vu. I do get /master/vu and /track/selected/vu . According to the source code, these should get flushed, I don't understand.

Using a vst3 plugin and mapping a macro to something on the instrument that is a selector type (fixed values) often the names reported back to the tablet are off from where the switch is

So if it’s a simple on off, the tablet will show on when it’s off. And it gets worse when it has more steps like models in fabfilter Saturn.

Might be a bitwig bug too I can’t tell

/preroll : receives an integer, but sends a string

Perhaps it should send + receive only integers, or only strings

When an integer is sent, the client display (ex. OpenStageControl dropdown or switch, which should reflect current integer-based state) is wiped by immediate feedback as string

OSC sent: { address: '/preroll', args: [ { type: 'i', value: 1 } ] } To : 127.0.0.1:8000
OSC received: { address: '/preroll', args: 'one_bar' } From : 127.0.0.1:59956

• Add beat repeat button
• Session scene button indication for current scene play
• Session: Select+Convert: Bounce in place. Long press convert button convert midi clip to bounce in place audio.
• Drum + Note Sequencer : Impl long press to adjust note length and velocity
• Drum Grid: Pads states currently tied to primary device.
• Drum: Direct selection of a measure
• Sequencers: Jump to step-page
• Delete button combinations
  • hold Delete + Automation button to delete all automation in a clip
  • hold Delete + select a device to remove that device
• Mute/Solo button combinations
  • hold Mute + pressing a step to deactivate it without deleting it (Step Sequencer mode)
• Hold Shift + Master volume knob to adjust Pre-Cue volume
• Waveform display, slicing, etc.
• Adjust the Input and Output routing
• Visual feedback for the count-in

... Either by configuring it in the dialog, or by setting it via OSC ala
/page/size/set [page size] and
/page/size/get to retrieve it.

My use case is that sometimes I want to get the whole session and handle the paging on the controller size, or more basically I would like to make the "current page" span my whole grid device which is 16 as of now.

What do you think ? You could still let the default page size to 8.

For now I can just call a page and the next and handle the data I get back from it on the controller side but it seems a bit hacky...

I noticed when we open the device panel with osc and go through the devices (/device/+ and /device/-), the bitwig gui does not give a 'selected device' notification for that.

Is there something we could do about that?

When /track/vu is switched off, meters presently continue to display the last received value (ie. they appear stuck)

Possible to send '/track/{1-8}/vu 0' when the meters are switched off?