goodweather

Forum Replies Created

Viewing 20 posts - 1 through 20 (of 399 total)
  • Author
    Posts
  • in reply to: exportMeWithRessources : issue #116781
    goodweathergoodweather
    Participant
    • Topics: 41
    • Replies: 399
    • Total: 440
    • ★★

    I would first change the directory name of your images from µQ to MQ.
    Could be that.
    Maybe reload the images in the panel then export
    Check the images and their names in the temp directory of your panel (on PC under Appdata/Roaming/Ctrlr/your_panel_ID
    Good luck!

    in reply to: UILabel modulatorValue() issue #116643
    goodweathergoodweather
    Participant
    • Topics: 41
    • Replies: 399
    • Total: 440
    • ★★

    I’m using uiLabels for displaying values on patch sheets.
    I’m putting a modulator OnChange method on the main modulator where I add something like the following line into it to modify the corresponding uiLabel (lblTune has been declared as modulator in another method)

    lblTune:getComponent():setPropertyString ("uiLabelText", tostring((value-50)/20))

    in reply to: Install Error #116642
    goodweathergoodweather
    Participant
    • Topics: 41
    • Replies: 399
    • Total: 440
    • ★★

    Hi, if you have this with the latest stable 5.3.201 and all versions then this has probably nothing to do with the soft as such.
    Did you try installing as admin? So, use “Run as administrator” by right clicking on the .exe file
    I have the impression that I got that error myself quite some time ago on a PC 😉

    in reply to: Creating a Panel – video tutorial #116570
    goodweathergoodweather
    Participant
    • Topics: 41
    • Replies: 399
    • Total: 440
    • ★★

    You can also have a look to my step by step guide
    https://ctrlr.org/forums/topic/ctrlr-step-by-step-guide/

    in reply to: XY Pad broken? #116287
    goodweathergoodweather
    Participant
    • Topics: 41
    • Replies: 399
    • Total: 440
    • ★★

    Interesting question.
    Never used the XY pad but will try and have a look at the issue.
    Greetings

    in reply to: Ctrlr not shown correctly in FL Studio #116233
    goodweathergoodweather
    Participant
    • Topics: 41
    • Replies: 399
    • Total: 440
    • ★★

    Unfortunately, the last stable version is 5.3.201.
    There are several newer versions but from my side I don’t know what has been changed in those.
    The only thing we all know is that they are giving problems with the panels.

    in reply to: Yamaha AN200 Panel #115973
    goodweathergoodweather
    Participant
    • Topics: 41
    • Replies: 399
    • Total: 440
    • ★★

    Very nice panel so, as Possemo said, respect and welcome to Ctrlr panel makers’ community (if that one is existing, hahaha… 😉 )

    in reply to: Yamaha AN200 Panel #115837
    goodweathergoodweather
    Participant
    • Topics: 41
    • Replies: 399
    • Total: 440
    • ★★

    Héhé…now I could be interested!
    I have a PLG150-AN card in a Motif ES8 but never used it as the process for using it was just heavy and not intuitive at all. Took me long time to have Yamaha’s editors working at all on Win10 but still, way of working was not good (need to save then to send)… Then finally dropped this and did something else with my other synths.
    So, I may try this in the coming months 😉

    Which setup did you use for your MU100R to have the PLG150-AN card responding?

    in reply to: Yamaha AN200 Panel #115832
    goodweathergoodweather
    Participant
    • Topics: 41
    • Replies: 399
    • Total: 440
    • ★★

    Hi, you can also look at my Pro2 panel. I have there patch and librarian.
    As for my other panels, everything is based on a memory block that I’m filling when reading/saving a patch file.
    It is easy to manage either by single byte or range.

    About the FREE EG, yep, you should use a uiCustomComponent then the various drawing capabilities offered by Juce graphics class (https://docs.juce.com/master/classGraphics.html) but also other classes.
    Check also the DEMO – Render panel provided by Roman with Ctrlr (in Ctrlr installation directory)

    in reply to: Ctrlr vsti sends midi messages twice #115595
    goodweathergoodweather
    Participant
    • Topics: 41
    • Replies: 399
    • Total: 440
    • ★★

    Yep and this is what I have been using except that I only do it on the Input Devices and that it seems to be enough.
    Now, doing it on Output and Controller do not hurt either 😉

    in reply to: Delay MIDI message? #115563
    goodweathergoodweather
    Participant
    • Topics: 41
    • Replies: 399
    • Total: 440
    • ★★

    Best way to handle midi message exchange is probably to do it and follow it with Lua methods.
    You initiate the exchange with a button (for example) that triggers the first send message method.
    On reception of some received message you send the second one.
    If you need to only send messages with some time interval in between, at the end of the first send message method you start a timer that will send the second message after some time.

    in reply to: Ctrlr vsti sends midi messages twice #115562
    goodweathergoodweather
    Participant
    • Topics: 41
    • Replies: 399
    • Total: 440
    • ★★

    Well, removing the Midi Output completely should prevent you to enjoy the benefits of bidirectional behavior, no?

    in reply to: Standalone Lua Not Loading #115561
    goodweathergoodweather
    Participant
    • Topics: 41
    • Replies: 399
    • Total: 440
    • ★★

    Yep, I may indeed change my panels to take that approach.
    I have already a PanelLoaded method using a bPanelLoaded and it is triggering a timer to show a welcome message.
    So, just need to change my isPanelReady and keep only the check for bPanelLoaded.
    Will definitely try this!
    Thanks

    in reply to: Standalone Lua Not Loading #115541
    goodweathergoodweather
    Participant
    • Topics: 41
    • Replies: 399
    • Total: 440
    • ★★

    We may need to have 2 versions for each panel then: one using getProgramState() check for standalone export and one without for VST export.

    Good that you remembered there was something about that!
    I checked the forum for getProgramState() but didn’t find any info.

    I have now made some VST tests (still need to do more): you can have any number for VST index.
    In my exported panel I have them between 2400 and 2600 and they all went thru without issue.
    Before exporting I just changed my Preferences to set 5000 as Max exported VST params.

    What could be good to do however is to only export the parameters that need automation.
    This is the next test I’ll do: check if everything is working fine with “Don’t export” except for automotion params.

    in reply to: LUA scripts not working in VST #115540
    goodweathergoodweather
    Participant
    • Topics: 41
    • Replies: 399
    • Total: 440
    • ★★

    We may need to have 2 versions for each panel then: one using getProgramState() check for standalone export and one without for VST export.

    Good that you remembered there was something about that!
    I checked the forum for getProgramState() but didn’t fins any info.

    in reply to: Understanding VST panels and presets #115530
    goodweathergoodweather
    Participant
    • Topics: 41
    • Replies: 399
    • Total: 440
    • ★★

    So I continued the investigation…
    Found the issue then found different posts on the forum and adding the following info.

    I discovered that we should not have getProgramState() in the condition in the isPanelReady function.
    Removing that and thus only using
    if panel:getBootstrapState() == false and bPanelLoaded == true then
    solves the issue. VSTs are working fine.

    I can have 3 instances of the same panel at once. Each with a different patch.
    Saving the project then loading it back gives no issue.

    Before exporting as DLL, I have also adjusted my preferences to have “Max exported VST parameters” set to 5000
    At the moment (I will do more thorough tests) all parameters seem to work.
    Not sure if the .overrides file is needed. This was maybe related to older Ctrlr versions than 5.3.201.

    I will search further in the forum about the meaning of getProgramState().
    All the startup phase of a panel is still a bit cryptic even if I understand it more and more.

    And about VST, still would be interested to know how to make presets (I suppose fxp files) appearing in the DAW.

    in reply to: Link to Modulator modulation type property #115529
    goodweathergoodweather
    Participant
    • Topics: 41
    • Replies: 399
    • Total: 440
    • ★★

    FYI, I’m just busy to make my first VST versions of my panels and had the problem that no Lua code was launched as dll. Spent the whole afternoon reading the forum about VST preparation.
    Found the issue then found different posts on the forum and adding the following info.

    I discovered that we should not have getProgramState() in the condition in the isPanelReady function.
    Removing that and thus only using
    if panel:getBootstrapState() == false and bPanelLoaded == true then
    solves the issue.

    I will search further in the forum about the meaning of getProgramState().
    All the startup phase of a panel is still a bit cryptic even if I understand it more and more.

    in reply to: restore state, program state and bootstrap state #115528
    goodweathergoodweather
    Participant
    • Topics: 41
    • Replies: 399
    • Total: 440
    • ★★

    FYI, I’m just busy to make my first VST versions of my panels and had the problem that no Lua code was launched as dll. Spent the whole afternoon reading the forum about VST preparation.
    Found the issue then found different posts on the forum and adding the following info.

    I discovered that we should not have getProgramState() in the condition in the isPanelReady function.
    Removing that and thus only using
    if panel:getBootstrapState() == false and bPanelLoaded == true then
    solves the issue.

    I will search further in the forum about the meaning of getProgramState().
    All the startup phase of a panel is still a bit cryptic even if I understand it more and more.

    in reply to: LUA scripts not working in VST #115527
    goodweathergoodweather
    Participant
    • Topics: 41
    • Replies: 399
    • Total: 440
    • ★★

    Hi,
    I’m just busy to make my first VST versions of my panels and had the problem that no Lua code was launched as dll. Spent the whole afternoon reading the forum about VST preparation.
    Found the issue then found also your post here.

    I discovered that we should not have getProgramState() in the condition in the isPanelReady function.
    Removing that and thus only using
    if panel:getBootstrapState() == false and bPanelLoaded == true then
    solves the issue.

    I will search further in the forum about the meaning of getProgramState().
    All the startup phase of a panel is still a bit cryptic even if I understand it more and more.

    in reply to: uiCombo not responding to MIDI CC #115526
    goodweathergoodweather
    Participant
    • Topics: 41
    • Replies: 399
    • Total: 440
    • ★★

    Hi,
    I’m just busy to make my first VST versions of my panels and had the problem that no Lua code was launched as dll. Spent the whole afternoon reading the forum about VST preparation.
    Found the issue and maybe it will also be interesting for you.

    I discovered that we should not have getProgramState() in the condition in the isPanelReady function.
    Removing that and thus only using
    if panel:getBootstrapState() == false and bPanelLoaded == true then
    solves the issue.

    I will search further in the forum about the meaning of getProgramState().
    All the startup phase of a panel is still a bit cryptic even if I understand it more and more.

Viewing 20 posts - 1 through 20 (of 399 total)
Do NOT follow this link or you will be banned from the site!