Small additions / features

[rudek]

Hi Paul,

after loading Bitwig, some of the already preloaded touchscreen buttons don't do anything, e.g. SMPTE/Beats or Scrub.
- Is there a list of al MIDI functions (0-127) on channel 1 that could be assigned to buttons?
- is there any way to know which preloaded Bitwig buttons actually do work?

I have a few additional features that I would find useful:
1) remove leading zeroes from time display. Having the dots is a big improvement, but the display is still hard to read
2) the colors on the display seem far away from the ones on screen. E.G. I have bright red faders on screen, but on the iCON units they are a dull brown, Any way to influence the selected colors?
3) are functions like Clear Clipping Indicator, Clear all Mutes, Clear all Solos available to program on buttons? All these are available on screen.
4) Is there a way to assign functions to hardware buttons? e.g. the "Shuf" button does not seem to do anything - could it be assigned to Scrub?

Regards
Rudy

[Paul Henty]

Hi Rudy,

- Is there a list of al MIDI functions (0-127) on channel 1 that could be assigned to buttons?
- is there any way to know which preloaded Bitwig buttons actually do work?

The functions that are currently available are listed in the TouchScreenButtons.pdf. At the moment there are not many.

I will go through the Bitwig buttons and see if any other have relevance in Studio One. If they do I will add them to the scripts so they will work. At the moment none of them will work.

1) remove leading zeroes from time display.

This will be in the next version

the colors on the display seem far away from the ones on screen.

I cannot reproduce this. The colours on my unit are very close to the screen colours, even bright reds. They will not be 100% because the iCON unit only uses 28bits for the colour while Studio One uses 32bits.

The colour sent to the controller is the colour on the background of the track name. The small tab at the bottom. The colour of the actual channel strip is altered by the colour settings of Studio One (You can alter the contrast and saturation etc.) So they make look different to the colour sent to the controller.

It could also be that your monitor settings are altering the colour you see. e.g. very high saturation or brightness settings.

3) are functions like Clear Clipping Indicator, Clear all Mutes, Clear all Solos available to program on buttons?

No but I will add them in the next version.

Is there a way to assign functions to hardware buttons? e.g. the "Shuf" button

The shuf button is not available for programming. Its function is fixed in the hardware. When it's active the jog wheel sends out the Bank Left/Right controls when turned.

Paul

[rudek]

Hi Paul,

many thanks for your quick response. Ok on all items, and here some comments on these two items:

the colors on the display seem far away from the ones on screen.

My monitor is more/less calibrated and it should be reasonably true. I attached a photo of two such instances (both faders are unselected, so not made bright by S1):
- the KeysBus fader is bright violet on the monitor, and blue on the iCON console
- the MixsBus fader is bright red on the monitor, and brownish/beige on the iCON console
It is not a big deal, mut maybe this photo helps to explain what I see.

- Is there a list of al MIDI functions (0-127) on channel 1 that could be assigned to buttons?
- is there any way to know which preloaded Bitwig buttons actually do work?

The reason I ask is because after selecting Bitwig on the iMAP, you get the touchscreen buttons attached to functions which seem reasonable (like SMPTE/Beats or Scrub) but they don't do anything on Studio one. There are also functions like "Zoom In/Out" on the U2 page that actually do not zoom but move the cursor around, etc.So ot would be great to remove all the assignments which don't work and replace them by functions that actually work. That is why I was asking if you had a list of Midi functions loaded to buttons when Bitwig was selected so we could work out and make notes what works and what doesn't.

Thanks
Rudy

[Paul Henty]

Hi,

I used that purple colour and I saw the same thing on my controller. It was blue. It's only a problem on some colours.

There's something in the controller (firmware or maybe the display itself) that's not showing some colours correctly - there's too much blue.

I've managed to compensate for this so from the next version all the colours will look much closer to the monitor.

The next version will also have an updated list of the touch screen button so you'll be able to see exactly what works and what doesn't.

Paul

[rudek]

Thanks Paul,
Looking forward to the next version!
Rudy