Lemur4Bitwig Template now compatible with 2.1.1

[Anzick]

I am!! Ok, so after playing with it for an hour or so here are my thoughts:

-love all the functionality of the mixer page, i finally took a closer look at it. being able to go in and out of full screen is a really nice touch.

-On the devices page, there seems to be an issue with being able to select more than one send at a time on devices page, as with more than one selected it only sends to one anyway - maybe make it so only one can be selected at a time? device page in general feels buggy / unpolished to me, the way it opens things on top of each other and it isn't really clear the way it functions and what's going on...to me anyway.

-is there a way to customize the layout of the clip launcher page? would like to be able to get rid of the button next to stop button and make the stop button bigger, if possible

-the biggest issue i am currently experiencing with this update is that it is not refreshing at all unless i hit the refresh button, it was never like this before

-i actually experienced no text bug!

-after an hour or so it stopped correctly updating the clip launcher, i've included a screenshot of lemur and Bitwig to show the difference. Also noticeable will be that I added the BPM buttons to the clip page which is awesome for me, thanks again Suloo for the customization tip! i don't know much about editing a lemur template but that little bit was easy enough.

I am still elated that this exists at all and remain incredibly impressed and thankful for your creation of this beautiful template!!

Screen Shot 2015-05-16 at 4.34.06 PM.png

IMG_0010.PNG

[Phorous]

Anzick, did you download the latest version of the Lemur4Bitwig controller script and replace your current one?

The new version we released today should contain a fix for the refresh issue and you should visibly see everything updating very quickly.

I can look into potentially adding a few configuration options to the clip launcher allowing you to disable the "override to arranger" button.

[Anzick]

OK awesome. Yes I am using the newest verison which was released today. I replaced the Lemur4Bitwig script and also the template with the newest versions. Which I noticed also added the options for fixed accent and VU meters in the controller options. Does the VU meter function yet? I couldn't see that it was.

[Phorous]

OK awesome. Yes I am using the newest verison which was released today. I replaced the Lemur4Bitwig script and also the template with the newest versions.

Hmm... I am struggling to reproduce the issue. Is it something specific that stops updating automatically, or everything?

Do you mind uploading me a project you are experiencing the issue with? Just the project file should be more than enough. I am thinking it might be something specific to your use case and I am not doing something that would trigger the issue.

Thanks!

EDIT:

The VU does not function yet, but we plan to add it in a future release!

EDIT2:

I plan on adding the correct scene names soon.

[Anzick]

I figured it out, but I don't understand it! When I was testing it out I was using an ad-hoc network, and now I am testing it on the standard wifi network, and it works as before, refreshing on its own. Why is this so? I thought the purpose of creating an ad-hoc network was decreased latency, no?

EDIT:
Also, does it make sense to post a link to the newest template side-by-side to the newest script on the front page? It's a little confusing to me not having them both together. It would be easy for someone, myself included, to update one and not realize about the other, I think.

[Phorous]

I figured it out, but I don't understand it! When I was testing it out I was using an ad-hoc network, and now I am testing it on the standard wifi network, and it works as before, refreshing on its own. Why is this so? I thought the purpose of creating an ad-hoc network was decreased latency, no?

EDIT:
Also, is it possible to post a link to the newest template side-by-side to the newest script on the front page? It's a little confusing to me not having them both together. It would be easy for someone, myself included, to update one and not realize about the other, I think.

Yes, we plan on having a single page we link to with the stable release very soon... a place where you can clearly get the latest stable version of everything with one click. You are 100% right on that one

That is odd about the ad hoc network. I can think of no reason why it would only work partially, only reasons of why it would either work 100% or not work at all. I know some people rely on AdHoc network setups while performing so I will definitely do some testing and get back with you!

By the way, most of the delay you see in the script is Bitwig being slow to update the observers, hence you don't immediatly see some changes process. I have a feeling this is going to improve in Bitwig updates as the controller API becomes more stable for larger projects such as ours.

[Cyoon]

Hey Anzick,

thanks for your reply. I just uploaded a new template version wich fixes the send selection issue. Now you can only select one channel at a time.

I also changed the colors of the mode knobs to white and the selected to green, so you might now be able to see the selected mode faster then before. Let me know if this helps you, or what you think is missing.

Actualy i didn't try to use an Ad Hoc network yet to check the syncing, will also do this soon.
However, i think when the OSC over USB in midimux is supported, we will experience no issues anymore, apart from Bitwig being slow.

With the cliplauncher, well this is now handled inside canvas, so i fear there is no such easy way like with the buttons before to change this, and it is quite useful for studio & live work to have the back to arrangement button there. I imagine that in our single item project we could provide a more DJ orientated version of the cliplauncher tho.

cheers

[Anzick]

Ok great I will check out the new template and let you know.

Yeah, OSC over USB in Midimux should definitely solve any issues with syncing, and be a great solution for reliability during performance. A couple days ago I asked the Midimux developer, Pascal, how far out it was and he confirmed it will take "some more weeks".

[Cyoon]

Also, does it make sense to post a link to the newest template side-by-side to the newest script on the front page? It's a little confusing to me not having them both together. It would be easy for someone, myself included, to update one and not realize about the other, I think.

you mean here on KVR? In the install instructions, there is a link to the script, should i place that next to the template link? A new place is in the works yea.

[Anzick]

you mean here on KVR? In the install instructions, there is a link to the script, should i place that next to the template link? A new place is in the works yea.

Yeah, until the new place is set up, having the link to each next to each other works fine. I see that you added the template right below the script and that was what I meant, that's perfect. Should definitely make it easier for newcomers to join in the fun.

[bschmaus]

I posted an issue a couple of weeks ago about the keyboard and pad UIs sending two notes when transposing up and down. Turns out that I had both a MIDI and OSC target configured in Lemur on my iPad and removing the MIDI target resolved the issue for me. Just wanted to mention that in case others have run in to the issue.

[Phorous]

Bugs I am working on currently that I hope to have fixed soon:

Clip launcher text doesn't have optimal handling for long clip names
Clip colors on certain locations in the clip launcher are not working for audio clips
Displayed track / device is off by one sometimes
Clip launcher rendering optimization code causes certain cells / rows to not update properly

If anyone has noticed any other bugs please post them here!

Also doing some usability work on the clip launcher, thinking about the overall page layout and controls and how it could be improved for live / production use.

[Cyoon]

I posted an issue a couple of weeks ago about the keyboard and pad UIs sending two notes when transposing up and down. Turns out that I had both a MIDI and OSC target configured in Lemur on my iPad and removing the MIDI target resolved the issue for me. Just wanted to mention that in case others have run in to the issue.

thx for sharing bschmaus!


btw, the midimux guys just posted a beta for audiomux2, so they probably are not too far away from implementing OSC over USB also..just a guess tho

[zengel]

hi the Lemur for Bitwig Team!
i try to figure out something. i tried to modify your Template so that it is for me more bitwig-looking and i tried to implement the vu meter . i worked using the Moss graber wiki doc function but it is slooooowww...
then i tried with the original osc script...it was so fast, but not totaly functional . you did a great job on the refresh part !!!
then my question ? is it possible that i have a bug with your script or is it normal ?

[Cyoon]

Hi Zengel! thx for your interest..

there already is a VU meter included in the experimental version on GitHub, but needs further improvements in speed yes.

What is the Moss graber wiki doc function btw?

The script by Moss (OSC4Bitwig) is the original script and the one by Voice303 (Lemur4Bitwig) is the Lemur optimized one.

Not sure i understand wich one you were using.

However, when Bitwig 1.2 is stable we are going to rework everything to make it compatible, but currently there are still changes to the API, so it doesn't make much sense to work it out right now.

cheers