minimalist

Forum Replies Created

Viewing 20 posts - 21 through 40 (of 141 total)
  • Author
    Posts
  • in reply to: r486 warning #1196
    minimalist
    Participant
      • Topics: 10
      • Replies: 141
      • Total: 151
      • ★★
      "atom":157x7ypp wrote:
      allright i’ll definetly look at that @home[/quote:157x7ypp]
      Do you already have some news about this? I’m still on 475 because of that (nerving) bug.
      minimalist
      Participant
        • Topics: 10
        • Replies: 141
        • Total: 151
        • ★★

        Ah, I see – great

        minimalist
        Participant
          • Topics: 10
          • Replies: 141
          • Total: 151
          • ★★

          Woohooo.. I’ve exported my first player version – it really feels magic! I love the idea of having a compact & easy to use final Ctrlr version. One thing: How do I select the desired MIDI device (it doesn’t work in the floating menu bar)?

          Atom, it has been often told: the development of Ctrlr is really targeted & your support is almost unique – thanks!

          in reply to: Creating an Off/On button which receives value 0/127 #2271
          minimalist
          Participant
            • Topics: 10
            • Replies: 141
            • Total: 151
            • ★★

            Oh, I never saw this option (actually I never used a ToggleButton)… YES, it works perfectly. <img decoding=” title=”Smile” /> I’ve set Max value to: 127, value for OFF state: 0 and value for ON state to: 127. This works really great! Is it possible to have this true and false values for an ImageButton, too?

            in reply to: Creating an Off/On button which receives value 0/127 #2269
            minimalist
            Participant
              • Topics: 10
              • Replies: 141
              • Total: 151
              • ★★

              What do you mean with "true & false values"? If you mean max value, midiValue, ect..: Yes I did. The ImageButton was just an example. The same thing happens with ToggleButton (then the check mark isn’t displayed when receiving an on message with value 127), same with uiCombo (then an on message causes "(no selection)"), uiButton (then an on message causes an empty (no name) button. I think the problem I have is generally, because Ctrlr expects for an on state just value "1" to display it correctly(?) That’s why I asked myself if there is a paticular setting for the case when the synth sends an on message with value 127, instead of 1.

              minimalist
              Participant
                • Topics: 10
                • Replies: 141
                • Total: 151
                • ★★

                Of course..

                in reply to: r486 warning #1195
                minimalist
                Participant
                  • Topics: 10
                  • Replies: 141
                  • Total: 151
                  • ★★

                  Many thanks! <img decoding=” title=”Smile” />
                  (this long time when removing plugins issue still exists (in Maschine), but I assume that you know about)[/size:218gl9je]

                  minimalist
                  Participant
                    • Topics: 10
                    • Replies: 141
                    • Total: 151
                    • ★★

                    OK, my Ctrlr crashing problems & msepsis issue didn’t shared the same source. I still (since 4 weeks) can’t export my panels – not as a player version and also not as panel (with resources).

                    in reply to: r486 warning #1193
                    minimalist
                    Participant
                      • Topics: 10
                      • Replies: 141
                      • Total: 151
                      • ★★

                      I’m not sure if this should be fixed (in 496)… If yes: I can’t see any difference to the build before.

                      minimalist
                      Participant
                        • Topics: 10
                        • Replies: 141
                        • Total: 151
                        • ★★

                        While I’m reading this I got the idea that my "Ctrlr-crash-when-export-as-player-bug" (which I was talking about in the forum & bugreport) could have the same source. Because it needs a loooong time when exporting and until the "License question" appears (then when I hit yes/no Ctrlr crashes – Mac). I assume that Ctrlr also tries to create a very huge file (my resources are less than 1 MB).

                        in reply to: r486 warning #1189
                        minimalist
                        Participant
                          • Topics: 10
                          • Replies: 141
                          • Total: 151
                          • ★★

                          Great!

                          in reply to: r486 warning #1187
                          minimalist
                          Participant
                            • Topics: 10
                            • Replies: 141
                            • Total: 151
                            • ★★

                            Do you mean that I maybe have some images (for panel background, sliders, buttons, ect) in the common "resources" folder? Yes, I do (of course).
                            I’ve tested it with with completely fresh & empty Ctrlr plugins – I assume that they don’t grab to this folder in this case?
                            For further tests I’ve deleted now all images (pngs) in that folder… Closing Maschine still needs such a long time.

                            in reply to: r486 warning #1190
                            minimalist
                            Participant
                              • Topics: 10
                              • Replies: 141
                              • Total: 151
                              • ★★

                              I’ve tested it with completely blank/empty Ctrlr plugins in Maschine.
                              Load this project: 1-2 seconds
                              Close the project: 50 seconds

                              in reply to: r486 warning #1192
                              minimalist
                              Participant
                                • Topics: 10
                                • Replies: 141
                                • Total: 151
                                • ★★
                                "atom":c115xgxl wrote:
                                so MAC users please don’t try to use it, it will crash Ctrlr[/quote:c115xgxl]
                                That’s really sadly! Not because I need this LCDLable (for me it’s just a graphical "nice to have")… No, it’s sadly because it seems to me that on PC created panels (which have this LCDLable) are not compatible to Mac anymore!?
                                This seems to be a big step backward in terms of compatibility.

                                "atom":c115xgxl wrote:
                                you will notice a slight delay (hang) when Ctrlr is loading or is beeing scanned by the host[/quote:c115xgxl]
                                Yes, there is a slight hang when Ctrlr is loaded – but because it’s really slight it’s OK. But: there is a very huge delay when Ctrlr plugins get removed from the host (at least on Maschine).
                                In older Ctrlr releases when I wanted to close a Maschine project which e.g. contains 15 Ctrlr plugins… the needed time for this was about 2-3 seconds.
                                Since 486 the needed time for closing the same project is about ONE minute! To wait such a long time just for close a project (or quit Maschine) is a bit… too much?
                                minimalist
                                Participant
                                  • Topics: 10
                                  • Replies: 141
                                  • Total: 151
                                  • ★★

                                  Yeah, we already spoke about this some weeks ago. If I understood it right the most complicated thing to realise this, is the support of ALL synths – because everyone has it’s own Sysex format.
                                  It’s just a completely shot in the dark: I thought about that maybe it could be more easy to implement if each panel supports this "modulator update" just for 1 single synth. Maybe there could be an component option/field where the user can type in a particulary "line of code" which is translating just the dedicated Sysex dump message which comes from the current controlled synth. As I told, it’s just a shot in the dark from a non-programer…

                                  minimalist
                                  Participant
                                    • Topics: 10
                                    • Replies: 141
                                    • Total: 151
                                    • ★★

                                    Oh yes! This is a really great & mighty feature request! Almost every day I’m dreaming about it… <img decoding=” title=”Wink” />
                                    This could be the last step that Ctrlr and the synth are finally REALLY one thing…
                                    And you’re right – the modulator update should happen by program changes done in Ctrlr and also by program changes at the synth itself.
                                    This is my hottest dream ever! <img decoding=” title=”Very Happy” />

                                    in reply to: New Features – Thank You and Question #1633
                                    minimalist
                                    Participant
                                      • Topics: 10
                                      • Replies: 141
                                      • Total: 151
                                      • ★★

                                      Woh, I noticed that you already did some changes in terms of undo/redo – thanks! Though I’m still a bit confused if undo/redo works as it should (I’m on Mac – I assume that it’s working on PC different?).

                                      a) when I’m changing several settings in the modulator’s preferences, then I press undo… ALL changes are resetted at once. It always resets to the state when the panel was loaded.
                                      b) but then – when I undo a parameter value tweak (in the panel), undo sets just 1 value back at the time. That means if I want to undo a value change from 0-127 – I have to press undo 128 times to come back to value 0! Would be nice if undo could reset a whole string of values.
                                      c) some operations are not reacting to undo (e.g. delete, MIDI message type …)

                                      Beeing curious how this works on PC.

                                      in reply to: New Features – Thank You and Question #1626
                                      minimalist
                                      Participant
                                        • Topics: 10
                                        • Replies: 141
                                        • Total: 151
                                        • ★★

                                        And? Do you have any idea why undo/redo doesn’t work in my case (as I understood EVERY change should be undo-able)? A short answer would be nice.

                                        in reply to: New Features – Thank You and Question #1628
                                        minimalist
                                        Participant
                                          • Topics: 10
                                          • Replies: 141
                                          • Total: 151
                                          • ★★

                                          "undo/redo is for all properties changed on the panel/modulator"
                                          Does it mean it should be possible to undo/redo parameter value changes? In my case it definitely doesn’t work (Mac)!

                                          "you’d like to control undo/redo as a vst parameter ?"
                                          Yeah. I’d like controlling Ctrlr plugins completely with external controllers (Maschine, Novation zero sl). Undo/Redo your parameter tweaks is such a powerful feature that I like to control it aswell by external gear. I assume if I’m forced to use the mouse (go to the computer, open plugin, etc etc) for undo/redo it’s disturbing my workflow too much – so that I’ll avoid this great feature.

                                          in reply to: New Features – Thank You and Question #1631
                                          minimalist
                                          Participant
                                            • Topics: 10
                                            • Replies: 141
                                            • Total: 151
                                            • ★★

                                            "Undo/Redo": Which opperations are supported by it? It’s a bit confusing to me, because sometimes it works – sometimes not. Is it also possible to undo/redo the value settings of modulators (for the case to undo/redo your soundsettings in a finished pannel)? Would be nice if this is possible and if it could be external controlled (e.g. host)… like a common component. <img decoding=” title=”Smile” />

                                          Viewing 20 posts - 21 through 40 (of 141 total)
                                          Ctrlr