Bitwig

webhamster · Post by **webhamster** » Thu Apr 02, 2015 6:20 pm

Thank you anyway. I'll fiddle a bit more to see how far I can get with it

Liquinaut · Post by **Liquinaut** » Thu Apr 02, 2015 9:52 pm

Please let us know if you get it working. I'd be interested to know

webhamster · Post by **webhamster** » Thu Apr 02, 2015 10:15 pm

It is actually working pretty well!

There are still a few issues, but to a large extend it is working. When I fix a few of the bugs I will share the script.

tomsa · Post by **tomsa** » Sat Apr 04, 2015 11:54 am

webhamster wrote:It is actually working pretty well!

There are still a few issues, but to a large extend it is working. When I fix a few of the bugs I will share the script.

That's great! Have you managed to implement any functionality not covered by the MCU script?

webhamster · Post by **webhamster** » Sat Apr 04, 2015 11:20 pm

presonus.zip

Here is the Faderport script.

I am not sure to what extend it has more options than the MCU script, but it works differently. I tried to make it feel more like the Faderport does in native mode (though it does need to run in Mackie Control mode).
Especially selecting channels seemed to be acting strange in the MCU script (note that you need to press the 'bank' button to change channels).

Do read the 'help' that is included.

Please let me know if anything is acting strange or something is missing

tomsa · Post by **tomsa** » Sun Apr 05, 2015 8:32 am

Awesome! I'll give it a try and let you know how it goes!!

Liquinaut · Post by **Liquinaut** » Sun Apr 05, 2015 2:44 pm

Great, thank you! I probably won't have access to a faderport until the end of the week, but I'll try and report back.

Thanx for sharing your updated script with us!

ThomasHelzle · Post by **ThomasHelzle** » Mon Apr 06, 2015 11:16 am

Liquinaut · Post by **Liquinaut** » Fri Apr 10, 2015 9:32 am

Hey webhamster,

I've tested the faderport with Bitwig yesterday and I must say you've done a pretty awesome job in getting this to work properly! Everything works as you described, the documentation included is good, so thank you very much!

Maybe you can send it over to Bitwig to be included in the users controller script library? And if you have the chance to host it over at Github maybe others like me would be able to jump in anytime, so the script may grow overtime? Just a suggestion, though... I think it is very good already!

Thanx again!

tomsa · Post by **tomsa** » Tue Apr 14, 2015 7:25 am

webhamster wrote:
presonus.zip
Here is the Faderport script.

I am not sure to what extend it has more options than the MCU script, but it works differently. I tried to make it feel more like the Faderport does in native mode (though it does need to run in Mackie Control mode).
Especially selecting channels seemed to be acting strange in the MCU script (note that you need to press the 'bank' button to change channels).

Do read the 'help' that is included.

Please let me know if anything is acting strange or something is missing

Hey webhamster- I've been trying to get this to work for a few days now. I extracted the .zip into ~/Bitwig Studio/Controller Scripts and I can't find it in my available controller scripts in Bitwig's preferences. I checked the file/directory permissions and everything seems to be okay. Am I the only one having issues, or did I miss something really obvious??

Liquinaut · Post by **Liquinaut** » Wed Apr 15, 2015 6:35 pm

What OS are you on?

I noticed that either the Mackie MCU Script OR the Presonus Faderport Script is available as a controller script inside Bitwig, they don't coexist unfortunately. In my case the Faderport Script knocks out the MCU Script as soon as it is saved in ~/Bitwig Studio/Controller Scripts - maybe it's just the other way round for you?

ThomasHelzle · Post by **ThomasHelzle** » Wed Apr 15, 2015 6:54 pm

Did you put in an unique GUID? If yes it should work...

Cheers,

Tom

webhamster · Post by **webhamster** » Wed Apr 15, 2015 10:57 pm

It does have a unique ID and should co-exist with the Mackie MCU script.

The file path should be ~/Documents/Bitwig Studio/Controller Scripts (note the Documents folder).

Thanks Luiqinout for the compliment. I will send it over to Bitwig. Github is a good idea, though I've never used that actually.

tomsa · Post by **tomsa** » Sun Apr 19, 2015 6:43 am

webhamster wrote:It does have a unique ID and should co-exist with the Mackie MCU script.

The file path should be ~/Documents/Bitwig Studio/Controller Scripts (note the Documents folder).

Thanks Luiqinout for the compliment. I will send it over to Bitwig. Github is a good idea, though I've never used that actually.

That's probably what's making the difference for me. I'm using Ubuntu 14.04.2. When I installed the Bitwig .deb package, it automatically put in in my /home directory, rather than ~/Documents.

webhamster · Post by **webhamster** » Mon Apr 20, 2015 4:04 pm

When you put other scripts in that folder do they work?

As far as I understand the scripting language there shouldn't be any difference between OSX/Linux/Windows, but maybe there is some difference that I am not aware of.

Have any other people tested it? Would love to hear. Maybe that'll give a clue to the Linux version.

Bitwig

KVR Audio

Support for Presonus Faderport?