Forum
    • Categories
    • Register
    • Login
    1. Home
    2. the red_1
    T
    • Profile
    • Following 0
    • Followers 0
    • Topics 5
    • Posts 16
    • Groups 0

    the red_1

    @the red_1

    5
    Reputation
    1
    Profile views
    16
    Posts
    0
    Followers
    0
    Following
    Joined
    Last Online

    the red_1 Unfollow Follow

    Best posts made by the red_1

    • Auto-Generate 128-Frame Knob Filmstrips for HISE

      Hi everyone,
      I’d like to share a Python script that saves a lot of time when creating knob filmstrips for HISE.
      Instead of rotating a knob image manually frame by frame, this script:
      Takes one knob image
      Automatically detects the visible (non-transparent) area
      Crops and centers it perfectly
      Rotates it smoothly
      Exports a 128-frame sprite sheet (no jitter, no wobble)

      Features

      • True center rotation (no shaking)
      • list itemAutomatic alpha-based cropping
      • list item 128 frames (super smooth)
      • list item Vertical or horizontal filmstrip
      • list item Ready to use in HISE
      • list item Huge time saver

      Requirements :

      pip install pillow numpy
      

      Full Python Code : ⬇️

      from PIL import Image
      import numpy as np
      import os
      
      # === Settings ===
      image_path = "PATH/TO/KNOB.png"
      output_image = "PATH/TO/KNOB_128fps.png"
      num_frames = 128
      start_angle = 150
      end_angle = -150
      orientation = "vertical"  # "vertical" or "horizontal"
      
      # === Load image ===
      img = Image.open(image_path).convert("RGBA")
      w, h = img.size
      
      # === Detect non-transparent area ===
      alpha = np.array(img.split()[-1])
      ys, xs = np.nonzero(alpha > 0)
      x_min, x_max = xs.min(), xs.max()
      y_min, y_max = ys.min(), ys.max()
      
      # === Crop to real knob area ===
      img = img.crop((x_min, y_min, x_max, y_max))
      w, h = img.size
      
      # === Make square canvas for perfect rotation ===
      side = max(w, h)
      square = Image.new("RGBA", (side, side), (0, 0, 0, 0))
      offset = ((side - w) // 2, (side - h) // 2)
      square.paste(img, offset)
      img = square
      w = h = side
      
      # === Lock rotation center ===
      cx, cy = w / 2, h / 2
      print(f"Rotation center locked at ({cx}, {cy})")
      
      # === Create sprite sheet ===
      if orientation == "horizontal":
          sprite = Image.new("RGBA", (w * num_frames, h), (0, 0, 0, 0))
      else:
          sprite = Image.new("RGBA", (w, h * num_frames), (0, 0, 0, 0))
      
      # === Generate frames ===
      for i in range(num_frames):
          angle = start_angle + (end_angle - start_angle) * (i / (num_frames - 1))
          rotated = img.rotate(angle, resample=Image.BICUBIC, center=(cx, cy))
      
          if orientation == "horizontal":
              sprite.paste(rotated, (i * w, 0))
          else:
              sprite.paste(rotated, (0, i * h))
      
      sprite.save(output_image)
      print(f"Sprite generated successfully: {output_image}")
      
      

      Save the file with this name : ⬇️

      generate_knob_sprite.py
      

      Make sure the file extension is .py and not .txt.
      Open Command Prompt / PowerShell & Run the script ⬇️

      python .\generate_knob_sprite.py
      

      Good luck

      posted in Presets / Scripts / Ideas
      T
      the red_1
    • RE: Unable to Move UI Knob Directly — Only via Macro 1

      @David-Healey It worked! Thank you from the bottom of my heart for all your efforts, and thanks once again. 💛

      posted in General Questions
      T
      the red_1

    Latest posts made by the red_1

    • RE: Auto-Generate 128-Frame Knob Filmstrips for HISE

      @Ben-Catman Thank you very much! I’m really glad you found it useful. Hope it helps save time in your HISE workflow 😊

      posted in Presets / Scripts / Ideas
      T
      the red_1
    • Auto-Generate 128-Frame Knob Filmstrips for HISE

      Hi everyone,
      I’d like to share a Python script that saves a lot of time when creating knob filmstrips for HISE.
      Instead of rotating a knob image manually frame by frame, this script:
      Takes one knob image
      Automatically detects the visible (non-transparent) area
      Crops and centers it perfectly
      Rotates it smoothly
      Exports a 128-frame sprite sheet (no jitter, no wobble)

      Features

      • True center rotation (no shaking)
      • list itemAutomatic alpha-based cropping
      • list item 128 frames (super smooth)
      • list item Vertical or horizontal filmstrip
      • list item Ready to use in HISE
      • list item Huge time saver

      Requirements :

      pip install pillow numpy
      

      Full Python Code : ⬇️

      from PIL import Image
      import numpy as np
      import os
      
      # === Settings ===
      image_path = "PATH/TO/KNOB.png"
      output_image = "PATH/TO/KNOB_128fps.png"
      num_frames = 128
      start_angle = 150
      end_angle = -150
      orientation = "vertical"  # "vertical" or "horizontal"
      
      # === Load image ===
      img = Image.open(image_path).convert("RGBA")
      w, h = img.size
      
      # === Detect non-transparent area ===
      alpha = np.array(img.split()[-1])
      ys, xs = np.nonzero(alpha > 0)
      x_min, x_max = xs.min(), xs.max()
      y_min, y_max = ys.min(), ys.max()
      
      # === Crop to real knob area ===
      img = img.crop((x_min, y_min, x_max, y_max))
      w, h = img.size
      
      # === Make square canvas for perfect rotation ===
      side = max(w, h)
      square = Image.new("RGBA", (side, side), (0, 0, 0, 0))
      offset = ((side - w) // 2, (side - h) // 2)
      square.paste(img, offset)
      img = square
      w = h = side
      
      # === Lock rotation center ===
      cx, cy = w / 2, h / 2
      print(f"Rotation center locked at ({cx}, {cy})")
      
      # === Create sprite sheet ===
      if orientation == "horizontal":
          sprite = Image.new("RGBA", (w * num_frames, h), (0, 0, 0, 0))
      else:
          sprite = Image.new("RGBA", (w, h * num_frames), (0, 0, 0, 0))
      
      # === Generate frames ===
      for i in range(num_frames):
          angle = start_angle + (end_angle - start_angle) * (i / (num_frames - 1))
          rotated = img.rotate(angle, resample=Image.BICUBIC, center=(cx, cy))
      
          if orientation == "horizontal":
              sprite.paste(rotated, (i * w, 0))
          else:
              sprite.paste(rotated, (0, i * h))
      
      sprite.save(output_image)
      print(f"Sprite generated successfully: {output_image}")
      
      

      Save the file with this name : ⬇️

      generate_knob_sprite.py
      

      Make sure the file extension is .py and not .txt.
      Open Command Prompt / PowerShell & Run the script ⬇️

      python .\generate_knob_sprite.py
      

      Good luck

      posted in Presets / Scripts / Ideas
      T
      the red_1
    • RE: Unable to Move UI Knob Directly — Only via Macro 1

      @David-Healey It worked! Thank you from the bottom of my heart for all your efforts, and thanks once again. 💛

      posted in General Questions
      T
      the red_1
    • RE: Unable to Move UI Knob Directly — Only via Macro 1

      @David-Healey
      Thanks for the suggestion, but when I assign Macro 1 in the property editor, the UI knob still doesn’t move.
      Also, the Macro itself only goes from 0 to 6 instead of 0–127 because in the property editor I set Max = 6, Min = 0, and 7 steps (FPS), so the macro and knob ranges don’t match the full 0–127 range expected for a macro control in HISE

      Also, I have another knob in the UI that is set to 128 FPS, but I set Step Size = 1, Max = 6 and Min = 0 for it. It does rotate, but the steps and angles aren’t accurate — the increments feel uneven and the knob doesn’t feel precise when turning, likely because the UI control range doesn’t line up with the macro’s expected 0–127 range.

      Lastly, I don’t want to use HISE Script for this because the DSP part doesn’t work for me or seems broken — it still fails even after building the latest HISE Dev version. I’m avoiding scripting because I can’t get the DSP network working reliably,

      posted in General Questions
      T
      the red_1
    • Unable to Move UI Knob Directly — Only via Macro 1

      Hi everyone,

      I created a knob in the UI and linked it to script FX1, specifically to a hseq knob inside the script that is connected to an SVF EQ node. Then I linked Macro 1 to the knob in the interface, and it works well — it jumps between frequencies in 6 steps, similar to a Stepped Frequency Knob.

      However, the knob in the UI interface appears faded compared to the other normal knobs, and I can’t move it directly — it only moves through Macro 1, like in the video. ⬇️

      vid.gif

      Also, I don’t want to write code because I don’t understand C++ or Java.

      My question:
      Why can’t I move the knob in the interface directly?

      Thanks in advance for any help!🙏🏼

      posted in General Questions
      T
      the red_1
    • RE: HISE develop build does not show Git commit hash after building specific commit (VS2022)

      @David-Healey I thought they were the same thing, I’ll give it a try.

      posted in General Questions
      T
      the red_1
    • RE: HISE develop build does not show Git commit hash after building specific commit (VS2022)

      @the-red_1 5d1403bf-297c-4887-9d08-3519f8df4711-image.png

      I rebuilt HISE after properly cloning the repository using:

      git clone https://github.com/christophhart/HISE.git
      cd HISE
      git checkout 3c36e36c0c27adf97be22206fdebf87ec9c7eeb0

      After rebuilding, the commit hash (short form: 3c36e36c) does appear in the About HISE window,
      as shown in the screenshot, but it disappears shortly after.

      So the commit hash is detected initially, then it vanishes from the About window.
      0349c2b0-a78f-407a-8712-5c35449ac86d-image.png

      posted in General Questions
      T
      the red_1
    • RE: HISE develop build does not show Git commit hash after building specific commit (VS2022)

      @the-red_1 I ran git log -1 in the source folder and got:

      fatal: not a git repository (or any of the parent directories): .gitCapture d'écran 2025-12-22 192643.png

      posted in General Questions
      T
      the red_1
    • HISE develop build does not show Git commit hash after building specific commit (VS2022)

      Hello everyone,

      I’m facing a confusing issue with HISE develop build and I hope someone can clarify it.
      I cloned HISE from GitHub at this specific commit:

      3c36e36c0c27adf97be22206fdebf87ec9c7eeb0
      

      Then I built the standalone app successfully using Visual Studio 2022 (x64, Release).
      The generated executable is located here:

      D:\HISE-3c36e36c0c27adf97be22206fdebf87ec9c7eeb0\projects\standalone\Builds\VisualStudio2022\x64\Release\App\HISE.exe
      

      The build finishes without errors, and HISE.exe runs normally.

      However, when I open Help → About HISE, I see:

      Version: 4.1.0

      Git commit hash: “current hash…” (not showing the actual commit)

      Clicking Show commit on GitHub does not point to my commit

      So it looks like the executable was built correctly, but it does not embed or display the Git commit hash, even though I built directly from a specific commit.

      My questions:
      Is this expected behavior when building HISE from source?
      Is there an extra step required to embed the Git commit hash into the build?
      Could this be related to building outside a Git environment or missing Git metadata during build?
      Is the executable actually using the correct commit internally, even if it doesn’t show it in “About HISE”?

      I’ve attached screenshots of:
      Capture d'écran 2025-12-22 004119.png Capture d'écran 2025-12-22 004143.png
      The About HISE window

      The Release\App folder containing HISE.exe

      Any clarification would be greatly appreciated.
      Thanks in advance 🙏

      posted in General Questions
      T
      the red_1
    • RE: Best practice for stepped frequency parameters in SVF EQ

      @dannytaurus
      Thanks for the suggestions and explanations.

      To be honest, I’m not fully sure about the specific branch or commit details — I haven’t worked with building HISE from source before, and I don’t want to take up too much of your time diving into that.

      At this point I’m just trying to get the current functionality working, so I appreciate all the help and pointers, and thank you for your patience!

      posted in General Questions
      T
      the red_1