FOLKDISCO

Forum Replies Created

Viewing 18 posts - 1 through 18 (of 18 total)
  • Author
    Posts
  • in reply to: Mouse Down Events and Toggle Buttons #102137
    FOLKDISCO
    Participant
      • Topics: 2
      • Replies: 18
      • Total: 20

      That’s what got me. I always save important docs, songs, etc, regularly as filename 001, filename 002, etc with a round 10 number sometimes for significant steps. What got me was that I saved the thing in lots of versions, but from a certain point forward, none of the saves had my Lua methods. I have a program called “agent ransack”, a file search thing so I did a full computer search for panels containing “string.sub”, sorted by date. Only took an hour to re-write the last two methods and other enhancements, not too bad.
      I historically lost important stuff, so I’m pretty anal about saving lots of versions of everything.
      It is the one program on my whole computer where I have more than two versions…. *SIX* different versions installed in different folders.
      In your humble opinion, is Ctrlr-5.3.201.exe better than Ctrlr 5.4.29?
      Also, almost all the different versions seem on the face of it to be exactly the same as each other!
      The only big differences seem to be that Ctrlr-5.5.2.exe took ages to load, and I didn’t have all the dlls for v6.x. Need to run CTRLR on a w10 x32 windows tablet, with so much space, so don’t want to install extra dlls if possible.

      I just plumped for the latest version which loaded speedily.
      You say “For developing panels I would use the recommended version here: Ctrlr-5.3.201.exe”
      Is there a different better version for running panels more efficiently? I found there’s quite a big CPU hit spinning rotaries on my old laptop.

      • This reply was modified 5 years ago by FOLKDISCO.
      • This reply was modified 5 years ago by FOLKDISCO.
      in reply to: Mouse Down Events and Toggle Buttons #101497
      FOLKDISCO
      Participant
        • Topics: 2
        • Replies: 18
        • Total: 20

        Two panels written, exported, etc.
        Feel a bit daft for uploading a useless panel.
        Oh well.
        Cheers again.
        Definitely getting faster at doing this stuff.
        To start with, you just look at CTRLR and think. “….. WHAAAAT?”
        Then you look at Lua methods and go “….. WHAAAAT?”
        It all gets easier.
        Just need to know the basics of programming.

        in reply to: Mouse Down Events and Toggle Buttons #101462
        FOLKDISCO
        Participant
          • Topics: 2
          • Replies: 18
          • Total: 20

          I saved my panel, and it didn’t save the Lua methods!
          So it was working 100% in CTRLR, kept saving different versions, and now they don’t work because the methods have gone AWOL.
          Why would it do that?
          Lesson learned, I will be more paranoid in future, but I now need to rewrite 2 methods.
          Everything saved fine previously, including methods.
          I am on version 5.4.29, because that loads lots, lots faster, than 5.5.2 and I don’t have the correct dlls for version 6.
          And thanks for your reply about the 24 pixels.

          • This reply was modified 5 years ago by FOLKDISCO.
          in reply to: Mouse Down Events and Toggle Buttons #101150
          FOLKDISCO
          Participant
            • Topics: 2
            • Replies: 18
            • Total: 20

            uicustomcomponent supports mouse down and up?
            Maybe I should have used uicustomcomponent, but all the buttons needed some lua anyway.
            Here’s the full panel, everything working, sending out midi.
            I used global variables 0-15 for current clip.
            19 for the mute/stop toggle button, which changes the function of the s/m buttons.
            20-35 for the mutes.
            Obviously only using up to 8 and 28 currently, but there is plenty of space for expansion.
            Also double clicking the mute/stop button this clears the scenes and clips.
            All buttons send out note on except mutes which send out CC 0 or 7f, matching the rotaries.
            Think it responds really nicely, and looks a lot nicer using uiLabels than ctrlr buttons.
            Buttons have some strange colour effects I couldn’t work out how to turn off.
            When I save as an exe, a small part of the panel is chopped off at the bottom.
            What’s going on there?
            Cheers again for your help.
            And your iso keyboard looks lovely.

            • This reply was modified 5 years ago by FOLKDISCO.
            Attachments:
            You must be logged in to view attached files.
            in reply to: Mouse Down Events and Toggle Buttons #100963
            FOLKDISCO
            Participant
              • Topics: 2
              • Replies: 18
              • Total: 20

              Actually… Rethink!
              I am going to scrap a lot of the above, and just work with static uiLabel.
              At a basic level, I am fighting problems resulting from mouse up behaviour, and it is impossible to turn this off.
              Probably simpler to just use statics, creat my own radio groups, and set colours on mouse down using:
              panel:getModulatorByName(“static1”):getComponent():setPropertyString(“uiLabelBgColour”,”ff0000ff”)
              The basic problem I had isn’t CTRLR, it’s the touch screen.
              I can set mouse down behaviours but mouse up is so inconsistent.
              It works literally about 2/3 of the time, unless I am being really careful, and you don’t do that in performance situations.
              Pretty sure I know what I’m doing now.
              On the plus side, uiLabels actually are physically looking nicer.

              • This reply was modified 5 years ago by FOLKDISCO.
              in reply to: Mouse Down Events and Toggle Buttons #100567
              FOLKDISCO
              Participant
                • Topics: 2
                • Replies: 18
                • Total: 20

                It certainly makes A LOT of sense to have a free variable on components, for users to pass variables.
                From their name I would be surprised if Atom didn’t put these here for this purpose.
                If I was you I would use it.
                There was a point where I was thinking, “hold on, do I need 100 methods here?”
                Then making hacks/workarounds like passing variables through component name until Possemo pointed me in the direction of ModulatorCustomIndex/Name.
                Writing Lua is fine, because Lua is documented, but even if you have had decades of writing code, writing Lua code in CTRLR is really difficult, because nothing is documented.
                You search in the forum, but obviously the forum is chaotic and disorganised because it’s a forum!
                We could really do with documentation.
                Maybe a wiki with all the CTRLR functions, passed variables.
                Maybe a couple of examples if people can do that.
                I think Atom gave us all CTRLR for nothing, so I’m not going to go asking him to document the thing.
                I am probably over the difficult hump now, but it’s a steep hill at first.

                • This reply was modified 5 years ago by FOLKDISCO.
                in reply to: Mouse Down Events and Toggle Buttons #100514
                FOLKDISCO
                Participant
                  • Topics: 2
                  • Replies: 18
                  • Total: 20

                  Already did this last night.
                  All buttons now named b-0-0, b-0-1… b-2-0, etc now.
                  Buttons send out midi note on c15 0-9 for track 1, c15 0x10-0x19 for track 2, c16 0x0-0x9.
                  Scene buttons send out 0x40-0x49.
                  This leaves some space at the end of the tracks and clips for future expansion, if I need it.
                  Not sure if I will need more, but if I do, leaving space means I won’t have to reassign all the midi in Reaper.
                  Have separate methods for mouse down on channel 15, channel 16 (same as 16), and scenes.

                  mouseDown15 = function(comp, event)
                  
                      -- get the Note from the Custom Name
                      local NoteNr = comp:getOwner():getProperty("modulatorCustomName")
                  
                      -- send the NoteOn event
                  	panel:sendMidiMessageNow(CtrlrMidiMessage("9e"..NoteNr.."40"))
                  
                      -- reset the Button colour
                      comp:setValue(0,false)
                  
                  end

                  mouseDown() functions use getProperty(“modulatorCustomName”) instead of getPropertyInt(“modulatorCustomIndex”), because I might as well store and read hex, rather than read integers and then have to convert this into hex every time for CtrlrMidiMessage().

                  When it came to the scenes, in retrospect this actually freed up modulatorCustomIndex for scene numbers so that pressing a scene button can reset and set relevant button on/off colours.
                  Of course this doesn’t send out any extra midi, but it’s massively useful to know where you are with the scenes and clips currently playing.

                  scenic16 = function(comp, event)
                  
                      -- get the Note from the Custom Name
                      local NoteNr = comp:getOwner():getProperty("modulatorCustomName")
                  
                      -- send the NoteOn event
                  	panel:sendMidiMessageNow(CtrlrMidiMessage("9f"..NoteNr.."40"))
                  
                      -- reset the Button colour
                      comp:setValue(0,false)
                  
                  	local scene= comp:getOwner():getPropertyInt("modulatorCustomIndex")
                  	local t={0,0,0,0,0,0,0,0,0,0,0,0}
                  	local i=1
                  	local j=1
                  	t[0]=0
                  	t[scene]=1
                  	for i=0, 8 do
                  		for j=0, 9 do
                  			n="b-"..i.."-"..j
                  			panel:getModulatorByName(n):setModulatorValue(t[j], false, false, false)
                  		end
                  	end
                  end

                  I was a bit more paranoid about making variables local with the scene button Lua, as it will take longer to run.
                  I created a fully functioning panel with buttons then deleted all except one of the buttons and rotaries.
                  I use a php script to build all the XML script (buttons and rotaries) into a textarea box.
                  Save, then open the panel in a text editor, delete the one modulator and paste in the text from the PHP textarea.
                  Not sure if this saved time or made it all ridiculously more complicated for myself!
                  But it does mean that I can build new versions of my panel automatically, rather than having to edit and resize 100 buttons and 60 rotaries manually.
                  Just want to actually use the thing now.
                  Cheers again for your help, goodweather and Possemo.
                  Not just specifically on this thread, but I also found useful stuff from both of you on other threads.
                  The rotaries work left/right, because I have my tablet in portrait mode, but work it in landscape mode.
                  This is to maximise screen usage/screen wastage, both on CTRLR and windows taskbar etc.
                  When I run Reaper/Playtime on my laptop, I use rtpMIDI over wifi tablet -> laptop.
                  When I run Reaper/Playtime on my tablet, I use Loopbe to route back midi.
                  Going forward, I was thinking I might make the last set of buttons for each track a simple on/off toggle, not in the radio groups, for a midi mute function on all tracks.
                  I think this might be more useful than an extra clip on each track.
                  Really quite happy how this turned out.
                  Take a look, I think it’s pretty cool.

                  • This reply was modified 5 years ago by FOLKDISCO.
                  • This reply was modified 5 years ago by FOLKDISCO.
                  • This reply was modified 5 years ago by FOLKDISCO.
                  Attachments:
                  You must be logged in to view attached files.
                  in reply to: Mouse Down Events and Toggle Buttons #100454
                  FOLKDISCO
                  Participant
                    • Topics: 2
                    • Replies: 18
                    • Total: 20

                    Is there any way to set a radio group by just setting one value or modulator value?
                    Rather than setting all values for the whole group?

                    I can see how to set a modulator on or off with panel:getModulatorByName(“ModulatorName”):setModulatorValue(1, false, false, false)
                    But this does not affect the rest of the modulators in the radio group.

                    in reply to: Mouse Down Events and Toggle Buttons #100440
                    FOLKDISCO
                    Participant
                      • Topics: 2
                      • Replies: 18
                      • Total: 20

                      Thank you so much Possemo.
                      Your buttons work great.
                      Just looking at your coding, using modulatorCustomIndex to set the button output note.
                      I am happy with a fixed midi channel from the onMouseDown() function.
                      I might use two functions to cover channel 15 and 16, rather than using one panel midi channel.
                      See below.
                      Anyway, your use of radio group works great.
                      Playtime is happy with different inputs, but I have seen before that Ableton seemed to have a problem when a note on wasn’t terminated by a note off.
                      Maybe something else in the setup was messing with things, I don’t know, but notes were disappearing.
                      You used Aftertouch rather than note on for the buttons…
                      Any reason for this?

                      I might in the future look into pressing one scene button, and this sending just one midi note, but also setting the equivalent radio group buttons for all the tracks.
                      Currently, pressing a scene button leaves all the other buttons untouched.

                      goodweather, thanks again for your help.
                      Yeah I had figured out string.sub(), Lua itself actually has pretty good documentation, so it’s easy enough to work out what you’re doing.
                      But Possemo’s use of modulatorCustomIndex works fine and I suspect it’s faster and more efficient so I’ll probably use that.
                      I had just got stuck on midi out.
                      Basically, I was just working on CTRLR before I connected to anything, and component midi always appeared in monitor so I just kept wondering why the Lua midi wasn’t there…
                      D’oh!
                      With no set output, component midi appears in the monitor, but Lua midi doesn’t.
                      Just one of those CTRLR quirks.

                      Thinking through my overall approach to channels and midi control.
                      Do I need to use two channels, 15 and 16 to cover all the options?
                      Or do I go one channel using 0-9, 10-19, etc to cover all the buttons?
                      Will I ever want more than 10 buttons per group/track?
                      Perhaps.
                      I do want consistent midi now, so different future versions of my controller work with different songs made now and in the future without having to learn new controllers in my DAW, etc.
                      So for example, if I have one panel with just some scene buttons and a few rotaries, these should match up so everything still lines up on a different panel with hundreds of buttons and rotaries.
                      Just wondering how quickly I can put together a panel with this using PHP.
                      Let’s see…
                      Probably sleep now and try it tomorrow.
                      It is interesting that CTRLR has been envisaged from the start as creating panels to control specific devices.
                      I was just looking for a ridiculous number of buttons and controllers, and nothing seemed to fit the bill.
                      CTRLR is quirky and complicated but it’s just ridiculously flexible, and I’m really grateful to everyone involved in putting it together.

                      • This reply was modified 5 years ago by FOLKDISCO.
                      in reply to: Mouse Down Events and Toggle Buttons #100435
                      FOLKDISCO
                      Participant
                        • Topics: 2
                        • Replies: 18
                        • Total: 20

                        Got the midi send and button name extraction working really late last night. Buttons called b15-1, b15-2…
                        Sending note on, channel 15.
                        I’m thinking b16-1, b16-2, to send to channel 16, via function buttonDown16.
                        When I have so many buttons, and I want to keep them on 0-15 track1, 16-31 track2, etc, then I run out of buttons and CCs on one channel!
                        Want to keep it so if it expands or contracts in future, the note-ons and CCs follow a consistent plan.
                        So the same song can be run with a huge panel or a simplified panel, and all the top buttons and CCs will be the same.
                        Not 100% sure how I’ll use it yet!
                        How many buttons and CCs I’ll need!

                        The Lua substring stuff was easy, because there is plenty of documentation for Lua.
                        Just not full documentation CTRLR Lua.
                        The problem I was having, above anything else is that when no output is set, midi LOOKS like it is working because midi from components appears in the monitor.
                        However Lua does not output midi or appear in the monitor until you set an output!
                        Took a while to work out why everything was suddenly working.

                        buttonDown15 = function(--[[ CtrlrComponent --]] comp, --[[ MouseEvent --]] event)
                        	-- t=table containing midi message as numbers. 
                        	t={0x9e, tonumber(string.sub(L(comp:getOwner():getName()), 5)), 0x47}
                        	msg = CtrlrMidiMessage(t)
                        	panel:sendMidiMessageNow(msg)
                        end

                        So going forward, I am thinking that if a button is set ON in Lua, then that will trigger the rest of the radio group off and reset the other radio group button colours without me having to do it manually?
                        Let’s see!
                        Also turning the current button ON via Lua, would that change its colour?
                        Not sure if it is good to use the toggle functionality in CTRLR or if that will cause unwanted button off behaviour, etc.
                        That’s probably better than manually resetting all the other colours via Lua, so I’ll try that first.
                        Again, many thanks for your help, it has has been really useful.
                        I now need to put 4 young boys to bed, and have a look at Possemo’s stuff.
                        I won’t do anything more whatsoever until I have had a good look at your posts today.
                        Big cheers, both of you.

                        • This reply was modified 5 years ago by FOLKDISCO.
                        in reply to: Mouse Down Events and Toggle Buttons #100398
                        FOLKDISCO
                        Participant
                          • Topics: 2
                          • Replies: 18
                          • Total: 20

                          Hmmm….! So something happens on mouse down, but still no midi.
                          I was trying to shove midi send data into the Button_OnClick function to see if anything happens.
                          It doesn’t!
                          But at least I have some Lua which does something!
                          Also, the title doesn’t go red every time I try to compile it!

                          --
                          -- Called when a mouse is down on this component
                          --
                          
                          Button_OnClick = function(--[[ CtrlrComponent --]] comp, --[[ MouseEvent --]] event)
                          	
                          	-- Get current button
                          
                          	sName= L(comp:getOwner():getName())
                          
                          	message = CtrlrMidiMessage({0xf0, 0x42, 0x30, 0x00, 0x01, 0x0d, 0x41, 0x03, 0x00, 0x23, 0x00, 0x00, 0x0f, 0x7f, 0x7f, 0x7f, 0x7d, 0xf7})
                          	panel:sendMidiMessageNow(message)
                          	utils.infoWindow("Info", "This is "..sName)
                          
                          end 

                          There was stuff I was doing in flash a couple of decades ago, changing the way a component works, by its name.
                          So if we can read a button name as a variable, then the button name can be “Button-9e-01” and it can read its own name then send out midi “9e 00 40”.
                          Still haven’t managed to get Lua to actually send midi tho!
                          It does make it difficult programming when there is no manual.

                          in reply to: Mouse Down Events and Toggle Buttons #100205
                          FOLKDISCO
                          Participant
                            • Topics: 2
                            • Replies: 18
                            • Total: 20

                            My original green buttons are sending midi once, and I can set the blue buttons to send midi once easily.
                            I can make your buttons and my buttons send midi once easily.
                            The problem is that they are sending midi once on mouse up, and I want them to send midi on mouse down.
                            Also, I have chosen to send midi twice, as this is better than sending midi only on mouse up, for the reasons explained above.
                            If you have some Lua code that will work only on Component generic:”Called when a mouse is down on this component” and does not do anything on mouse up, then that is problem one fixed.
                            If this also works the radio group on mouse down, resetting button colour on other group members, that would be extra brilliant.
                            My big problem number two is that a radio group toggle uiButton which works great on mouse down, then resets its colour to off when you let go (mouse up).
                            I have found that you can slide sideways out of the button and then let go, it works fine on my buttons, sends midi once and leaves the colour set.
                            But obviously having to press and slide finger/mouse sideways isn’t ideal.
                            If there is some, any Lua that sends midi on mouse down and not up, on one button, that would be great, and I can copy/paste this to other buttons.
                            My problem is I am just not making any Lua work and send out any midi.
                            If there is a way to make CTRLR work on mouse down and not up without Lua, then I don’t need any Lua, but there doesn’t seem to be a way to do this.
                            My big problem currently is getting Lua in Component generic:”Called when a mouse is down on this component” to send any midi.
                            My scripts don’t compile.
                            I don’t know what I am doing!
                            If I can see one example of a simple Lua script sending midi CC or Note on, then that would be a big help.
                            I have seen examples of coding, but not whole scripts to paste in the Component generic:”Called when a mouse is down on this component” box.
                            If the correct Lua scripting is in this box, and the MIDI:”Midi message type” is set to “None” then will that send midi on mouse down, and not send it on mouse up?
                            Cheers again!

                            • This reply was modified 5 years ago by FOLKDISCO.
                            • This reply was modified 5 years ago by FOLKDISCO.
                            • This reply was modified 5 years ago by FOLKDISCO.
                            • This reply was modified 5 years ago by FOLKDISCO.
                            in reply to: Mouse Down Events and Toggle Buttons #99875
                            FOLKDISCO
                            Participant
                              • Topics: 2
                              • Replies: 18
                              • Total: 20

                              Goodweather, I sent you a PM with my number and other stuff.
                              I really wanted to spend more time with your “Ctrlr – Step by step guide” today, but time ran out.
                              Have already tried to get Lua information from this as a docx, but I think the most relevant bits weren’t complete.
                              Anyway, here’s some answers to your questions, and a panel upload.

                              – how do you see that the Midi msg is sent on Mouse up io Mouse Down?
                              From the midi monitor.
                              You can clearly see buttons responding to mouse down/up events.
                              When you use uiButton, you get a tickbox Component:”Trigger button on mouse down events”
                              To show you the difference I set blue buttons with this ticked and green buttons unticked.
                              Unfortunately, there is no tickbox Component:”Trigger button on mouse up events”, or I could easily turn it off without any Lua.

                              – what is the difference? How does it matter?
                              I just found that on a small touchscreen, mouse up didn’t respond consistently.
                              There are lots of buttons jammed in there 10×10 in 10 radio groups, and 60 rotaries on an 8″ screen, and my finger must just slide a bit or something.
                              I just found that when buttons respond to mouse/finger down it triggers every time.
                              With mouse up, I lose a lot of button presses.
                              I’m probably going to be doing other stuff like playing guitar and singing, so it needs to be consistent.

                              – please give me the names you would like for the buttons. I can call them Button1 to Button99
                              Whatever button names are fine.
                              Unless there’s some reason I don’t know about to care, I don’t care!
                              I was trying to be metodical and consistent with note and CC output, but unless you’re referencing components from Lua, I’m not sure it makes any practical difference?

                              – please give me the typical messages you would like to send to Playtime.
                              There are 60 rotaries sending CC, controlling all kinds of fun stuff. Volumes, filter cuttoff, velocity scale, random note kill.
                              I’m already using all those CCs, so it just made more sense to use something else like note on for the buttons controlling Playtime. But again, I’m not too bothered about this.

                              – Provide me with all the different message types and the complete ones.
                              – You can take them from the Midi monitor.
                              You can clearly see the double sends here.
                              If you tap fast, the two notes have the same time stamp.
                              If you hold on a while, it’s longer.
                              Like I said, if I just have one working button, I will probably use my PHP script to repeat that across the panel, with the correct values inserted.
                              I open the panel file in a text editor, add that to my PHP script, The PHP script outputs text with 100 buttons and 60 rotaries in the correct positions etc, I insert that into the panel file, and….
                              BINGO!
                              [00:15:00:000164]: [Note on] Ch:[15] No:[ 0] Val:[ 64]
                              [00:15:00:000727]: [Note on] Ch:[15] No:[ 0] Val:[ 64]
                              [00:15:02:000455]: [Note on] Ch:[15] No:[ 17] Val:[ 64]
                              [00:15:02:000821]: [Note on] Ch:[15] No:[ 17] Val:[ 64]
                              [00:15:08:000689]: [Note on] Ch:[15] No:[ 48] Val:[ 64]
                              [00:15:08:000689]: [Note on] Ch:[15] No:[ 48] Val:[ 64]
                              [00:15:09:000634]: [Note on] Ch:[15] No:[ 48] Val:[ 64]
                              [00:15:09:000634]: [Note on] Ch:[15] No:[ 48] Val:[ 64]
                              [00:15:29:000568]: [Controller] Ch:[15] No:[ 0] Val:[ 63]
                              [00:15:29:000580]: [Controller] Ch:[15] No:[ 0] Val:[ 62]
                              [00:15:29:000592]: [Controller] Ch:[15] No:[ 0] Val:[ 60]
                              [00:15:29:000603]: [Controller] Ch:[15] No:[ 0] Val:[ 59]
                              [00:15:36:000068]: [Controller] Ch:[15] No:[ 16] Val:[ 65]
                              [00:15:36:000103]: [Controller] Ch:[15] No:[ 16] Val:[ 66]
                              [00:15:36:000118]: [Controller] Ch:[15] No:[ 16] Val:[ 67]

                              Anyway I realised that I hadn’t uploaded the original panel, so here it is, and a pic of it.
                              Currently, the panel works in portrait mode, but is used landscape, because less screen is wasted that way!
                              Go figure!
                              I don’t really care what it looks like, I just want a ridiculous number of lovely buttons and rotaries on one screen!

                              Attachments:
                              You must be logged in to view attached files.
                              in reply to: Mouse Down Events and Toggle Buttons #99771
                              FOLKDISCO
                              Participant
                                • Topics: 2
                                • Replies: 18
                                • Total: 20

                                I forgot to say… I set some midi output for your buttons, but on both normal and momentary buttons it outputs midi on mouse up, not mouse down.
                                Just one message, but nothing on mouse down.

                                in reply to: Mouse Down Events and Toggle Buttons #99769
                                FOLKDISCO
                                Participant
                                  • Topics: 2
                                  • Replies: 18
                                  • Total: 20

                                  You can test for touchscreen, as this responds exactly like a mouse click.
                                  Touch a button=mouse down, let go=mouse up.
                                  I am testing on my laptop, not my tablet.

                                  But I am really confused now.
                                  All the options down to Component generic:”Called when a double click occurs on this component” are the same.
                                  Looking down from here, your buttons and my buttons have completely different options!
                                  My buttons have the tick boxes Component:”Button is toggle button” and Component:”Trigger button on mouse down events”.
                                  Your buttons do not!
                                  Is this because yours is a uiImageButton and mine is a uiButton?

                                  However, I can see “Called when a mouse is down on this component” on both sets of buttons.
                                  I have no idea what to do with this!
                                  All I want to do is output static midi.
                                  I know all about what midi hex numbers to send, no problem, but I’m completely baffled what to put in these boxes to send that midi!
                                  Have created a copy of one of your buttons, have turned off midi, and am currently trying to write a myMethod.
                                  It very much isn’t working out for me!

                                  in reply to: Mouse Down Events and Toggle Buttons #99663
                                  FOLKDISCO
                                  Participant
                                    • Topics: 2
                                    • Replies: 18
                                    • Total: 20

                                    Thank you so much!
                                    For some reason, your new buttons are replicating my buttons behaviour, but not sending out any midi.
                                    Is this correct?
                                    I know the monitor really well, but have never done any Lua.
                                    Don’t think I have disabled Lua, Lua disable is not ticked in preferences.
                                    Please note my current button behaviour is not what I am trying to achieve.
                                    The different colour buttons just show what happens with “Trigger button on mouse down events” ticked (blue) and unticked (green).
                                    My panel buttons and rotaries are made and placed automatically as text with a PHP script which I copy/paste into a .panel file, so all I need is one working button, and I can replicate this and fill the different note/CC colour values.
                                    I just use blue/green/red buttons to make it easier to visualise the different tracks.
                                    1-3=blue, 4-6=green, 7-9=blue, 10+red (scenes).
                                    All the buttons just output a simple static trigger, note or CC is fine.

                                    IDEAL BEHAVIOUR OF BUTTONS
                                    ON MOUSE/TOUCH DOWN
                                    1) Midi note on OR midi CC sent.
                                    2) Button changes colour to red. Ideally, subsequent presses on a red button would leave it red.
                                    3) Other buttons in the same radio group are reset to their original colour (blue or green).

                                    ON MOUSE/TOUCH UP
                                    Nothing!

                                    *IDEALLY*, pressing a scene button would turn all the other clip and scene buttons back to their original colours, but lets not worry about that for now!
                                    If a double note on or CC is sent, that isn’t ideal, but I easily could live with it.
                                    Many, many thanks again for looking at this. 🙂

                                    in reply to: Issue with the Grandmeister 36 panel #99542
                                    FOLKDISCO
                                    Participant
                                      • Topics: 2
                                      • Replies: 18
                                      • Total: 20

                                      I think he’s referring to this?

                                      Hughes & Kettner – GrandMeister Desktop Remote

                                      in reply to: Mouse Down Events and Toggle Buttons #99535
                                      FOLKDISCO
                                      Participant
                                        • Topics: 2
                                        • Replies: 18
                                        • Total: 20

                                        Many thanks, goodweather!
                                        Sorry, this has 8 buttons, not one or two.
                                        My original panel has 100 buttons and 60 rotaries.

                                        THE UPLOADED PANEL
                                        All buttons are identical, except for the note-on key output, and that the blue radio buttons have “Trigger button on mouse down events” ticked, and the green buttons have this unticked, to show the difference.
                                        Blue buttons are radio group 3, green buttons are radio group 4.
                                        I use my panel to control the Playtime session view in reaper.
                                        https://www.helgoboss.org/projects/playtime/
                                        It is very simple in operation, just sending static midi on notes, no 2-way communication or Lua.

                                        The blue buttons work consistently on my small 8″ touch screen, sending out at least one note-on.
                                        I have found you need to be careful how you touch the green buttons, or they do not send midi.

                                        Obviously, it isn’t ideal that the blue buttons trigger twice, on mouse down and mouse up, but especially that they do not hold their red colour.
                                        However, the green buttons are not consistent on a small touch screen.
                                        Often you press them, your finger moves a little, and no midi is sent.
                                        In performance situations, you need to tap a button and know it will perform.

                                        My ideal would be for the buttons to respond only to mouse down events, to have some way to disable mouse up events.
                                        Also, it would be nice if the buttons did not toggle off when you press them again, so that they stay red no matter how many times you press them.
                                        I don’t know if you can use Lua to program only a mouse-down event for the buttons?
                                        Or if there are any internal ways to disable mouse-up?
                                        Obviously, on a toggle button, when you cannot disable mouse up events, it toggles off again every single time you let go!
                                        Cheers, in advance for looking at this.

                                        • This reply was modified 5 years ago by FOLKDISCO.
                                        • This reply was modified 5 years ago by FOLKDISCO.
                                        Attachments:
                                        You must be logged in to view attached files.
                                      Viewing 18 posts - 1 through 18 (of 18 total)
                                      Ctrlr