Bitwig modulation mapping preview

[garyboozy]

it's not a file. it's from the application itself.
if you really want to see, right-click Live's icon:
Show Package Contents > Contents > MacOS
and open the Live file in Text Edit

search for options.txt, edit them into a readable form.
be careful in there!

[aMUSEd]

Found it

https://www.ableton.com/de/articles/opt ... file-live/


looks like you have to add it with each new install though

[garyboozy]

sorry, thought you were asking where the hidden options were being found, not how to enable them

[aMUSEd]

The -ShowDeviceSlots is pretty nifty too, turn it on, look on the right near the i/o and other buttons for a new button to enable disable, shows all the effects on a track but now on the mixer/clip strip up top

That's useful but it doesn't show the device name - is that another hidden option?

[ezelkow1]

The -ShowDeviceSlots is pretty nifty too, turn it on, look on the right near the i/o and other buttons for a new button to enable disable, shows all the effects on a track but now on the mixer/clip strip up top

That's useful but it doesn't show the device name - is that another hidden option?

Thats why its not enabled by default yet, if you expand your track width then the names will show up. The names also disappear when re-arranging them from within that mixer strip until you resize it again. So its useful, but not ready yet so why its not enabled officially

[pdxindy]

Where did you find the information for this stuff? I'd love a complete listing of options to play with

from here:
https://forum.ableton.com/viewtopic.php?f=4&t=177825

i saw a bunch of other blog posts after i posted about the mapsiblingsomacro option. seems they never quote their source. hohum.

I hate it when apps hide away options in obscure text files. If it's an option then put it in options/preferences. No wonder so few people know about this.

So where do you find this file on mac?

WIP stuff I guess...

user/Library/Preferences/Ableton/Live (current version)/Options.txt

[wasi]

Oh dear, I derailed my own thread by mentioning Ableton in the same post as Bitwig.

I love the mapping the way it's shown, especially directly assigning the macro range and not having the value snap to zero. These would be huge workflow improvements.

You can configure Live via the options.txt file to not snap to zero but stay on the existing parameter value.

Apparently. It's cool to at least be able to disable a bug in a file you need to create manually at an obscure location. I would have preferred they just fix it. Kudos to you and ezelkow1 for pointing it out though.

I also enabled -MakeLiveNineAwesome=1 while I was at it. Fantastic. I may have to upgrade after all now.

[pdxindy]

Oh dear, I derailed my own thread by mentioning Ableton in the same post as Bitwig.

I love the mapping the way it's shown, especially directly assigning the macro range and not having the value snap to zero. These would be huge workflow improvements.

You can configure Live via the options.txt file to not snap to zero but stay on the existing parameter value.

Apparently. It's cool to at least be able to disable a bug in a file you need to create manually at an obscure location. I would have preferred they just fix it. Kudos to you and ezelkow1 for pointing it out though.

It is not a bug. It is a less than ideal implementation... It is rather easy to create the file, though it seems you just want to look for things to be negative about.

Live is today being used by thousands of people to help fulfill their own creative visions. It must be millions of people who have attended and enjoyed live performances based on Live. We are all lucky to have such a fine tool and to enjoy the creative efforts of talented people who use it.

As of today, Bitwig has accomplished nothing. If and when it ships, perhaps it will clearly surpass Live and that is a good thing. But then Bitwig has not had to be in the limelight, or deal with thousands of users all with different needs, setups, performance situations. We will see how it handles that in real world use. I am rooting for it, but it is also quite possible it will take a year or more once it ships to iron out the wrinkles. In the meanwhile, Live is a fine piece of software that I can use today.

[ZenPunkHippy]

How (with all the various squares) do you remember what part is on what button if you were to use it in Live or BWS or similar? Can you tag the buttons or something or do you just have to remember what button plays what part?

AFAICT there is a standard layout for each function so it's basically a combination of memory and specific functions always being mapped to certain areas of the 8x8 squares.

Might be cool (in Ableton I suppose) if the name of the clip actually showed up on the button ... if it doesn't... and again, I have no clue either way. I do know my old brain might have some small difficulty sorting that out across X# of patterns and buttons to remember.

Other than multi-coloured LEDs to indicate mode there is no visual feedback like text on the buttons.

In practice I think it will work fine, but to get the best out of it will require regular practice / usage i.e. it really needs to be integrated in to your workflow.

Peace,
Andy.

*edit to number of squares

[jeffh]

Eh... Looks just like how NI Massive has been doing it for years... Except not as well as Massive was doing it years ago... Color me unimpressed..

Massive at least draws those pretty rings around everything so that you know what is being modulated and how much, at a glance. I'd prefer dropdown boxes over this...

OTOH, I care more about the quality of the sound than a flashy UI, but I'm in a tiny minority with that preference

[pc999]

BTW at 2.05 they give a small look of the modular system



And here they do of it and the online colab

http://blog.dubspot.com/bitwig-studio-d ... irst-look/

Modular Accessibility
One of the most innovative aspects of Bitwig is that the entire system has been designed from the ground up using a built-in native modular toolkit that will be completely user-accessible. This will allow you to modify and customize the onboard instruments or effects and then save and share your modified versions with other users. You can add new parameters or controls to an existing device, or even build a completely new instrument or effect from scratch.

Bitwig features an expanded mixer view and Clip view
Although this kind of functionality will be familiar to users of programs like Reaktor or Max/MSP (which is course available to Ableton users as Max for Live), Bitwig's design seems to go a bit further than other DAWs in offering users the ability to modify virtually any aspect of its internal workings, although we don't have all the details yet about how this will work.
Network Collaboration
One of the most exciting things we saw demoed in Bitwig were the multiuser collaboration features planned for future versions, which will allow you to work on a shared document with another user over a network. Essentially the idea is that multiple users on the same network can all work on the same project at the same time via LAN, allowing for a new level of creative collaboration. Although we have seen some applications with somewhat similar functionality before (most notably Ohm Studio from French plug-in developer Ohm Force, also still in beta), to our knowledge Bitwig is the first full-featured DAW that will offer this degree of collaboration.

Those features seems quite developed, I wonder if they are reserved for a 2.0 or 1.x update???

[pdxindy]

Those features seems quite developed, I wonder if they are reserved for a 2.0 or 1.x update???

According to Bitwig, accessing the modular structure and multi-user collaboration are for 2.0

[ZenPunkHippy]

Those features seems quite developed, I wonder if they are reserved for a 2.0 or 1.x update???

According to Bitwig, accessing the modular structure and multi-user collaboration are for 2.0

Which sounds like a long wait, but I get the impression 2.0 will happen relatively quickly after the initial release. More speculation, but that's how I see it.

Peace,
Andy.

[pdxindy]

Eh... Looks just like how NI Massive has been doing it for years... Except not as well as Massive was doing it years ago... Color me unimpressed..

Massive at least draws those pretty rings around everything so that you know what is being modulated and how much, at a glance. I'd prefer dropdown boxes over this...

OTOH, I care more about the quality of the sound than a flashy UI, but I'm in a tiny minority with that preference

This is built into the DAW itself. Every Bitwig device and later the ones users make from the modular system will have this functionality.

[jeffh]

Eh... Looks just like how NI Massive has been doing it for years... Except not as well as Massive was doing it years ago... Color me unimpressed..

Massive at least draws those pretty rings around everything so that you know what is being modulated and how much, at a glance. I'd prefer dropdown boxes over this...

OTOH, I care more about the quality of the sound than a flashy UI, but I'm in a tiny minority with that preference

This is built into the DAW itself. Every Bitwig device and later the ones users make from the modular system will have this functionality.

I assume by modular system you mean that Reaktor-style thing they were showing... I kind of think that's a fail too just on a conceptual level, it's not like there's a single Reaktor ensemble out there that just beats the pants off of any plugin made with C/C++ code... In fact, quite the opposite, Reaktor uses way more CPU, especially for anything remotely complex in the way of DSP...

For that matter, if you own Reaktor and Ableton or Max4Live and Ableton, what compelling reason is there to switch to Bitwig? I really doubt that they are going to somehow deliver a better Reaktor-style modular synth-maker thingie than the others that have been around for so much longer... Based on Bitwig's inability to get a product out the door, I'd expect it to be somewhat inferior, and probably years late...

I was an avid Reaktor user many, many years ago that eventually gave up and moved to real C/C++ code, because the GUI-programming paradigm is so limiting... Also, the act of wiring together stuff for hours on end is very counter-productive to actually making music, I can personally attest to that