HISE Logo Forum
    • Categories
    • Register
    • Login

    Can't have "." in Sample Map name

    Scheduled Pinned Locked Moved Bug Reports
    4 Posts 3 Posters 235 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Casey KolbC
      Casey Kolb
      last edited by Casey Kolb

      It seems in the most recent develop build you can't include a period in sample map names, so any previous sample maps I've made (e.g. "Mr. Blippy") are now irreversibly messed up for my end users without a reinstall of the samples. Now, if I try to convert a sample map like "Mr. Blippy" to a monolith, the monolith will be named just "Mr.ch1". This also irreversibly affects any presets using these sounds.

      @Christoph-Hart Do you know if there was something added recently that could have altered this behavior?

      EDIT: It appears the issue is when you try to load a sample map with a "." in the name, it can't find the monolith because it assumes the name stops at the period. So "Mr. Blippy" looks for a monolith named "Mr".

      Casey Kolb
      Founder & CEO of Lunacy Audio
      Composer | Producer | Software Developer

      d.healeyD 1 Reply Last reply Reply Quote 0
      • d.healeyD
        d.healey @Casey Kolb
        last edited by

        @Casey-Kolb Generally a bad idea to put . in file names because Windows some operating systems think that means the end of the file name and whatever follows is the extension. But since it was working for you before I think this is a bug that needs resolving.

        Libre Wave - Freedom respecting instruments and effects
        My Patreon - HISE tutorials
        YouTube Channel - Public HISE tutorials

        Casey KolbC 1 Reply Last reply Reply Quote 0
        • Casey KolbC
          Casey Kolb @d.healey
          last edited by

          @d-healey Yep, and I'm having this issue on Mac too, so it's something in the way the sample map names are being parsed when looking for the monoliths.

          Casey Kolb
          Founder & CEO of Lunacy Audio
          Composer | Producer | Software Developer

          Christoph HartC 1 Reply Last reply Reply Quote 0
          • Christoph HartC
            Christoph Hart @Casey Kolb
            last edited by Christoph Hart

            @Casey-Kolb Yes I rewrote some of the monolith file handling stuff to allow split monolith files (for samplemaps that have more than 2GB of samples). This might have introduced this issue.

            I'll take a quick look. I second Davids advice that it's not the smartest thing to do but now it's in the open and you don't want every user to reinstall stuff because of that.

            1 Reply Last reply Reply Quote 1
            • First post
              Last post

            22

            Online

            1.8k

            Users

            12.1k

            Topics

            105.4k

            Posts