HISE Logo Forum
    • Categories
    • Register
    • Login

    HISE seems to have butchered all of my loop points.

    Scheduled Pinned Locked Moved Bug Reports
    samplemapsmonolithsample
    5 Posts 4 Posters 213 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.
    • E
      Elezeid
      last edited by

      This is a bit frustrating, considering it looks like many hours of work must now be redone.

      I have meticulously set loop points for over 400 individual samples. I set the loop points first in an audio editor, but HISE only really recognized embedded loop points about 20% of the time, thus I had to manually enter the loop points (a second time) into the samplemaps by hand. One sample per sample map. Every single one of them was rigorously tested for quality and accuracy.

      I converted the samplemaps all to HLAC monolith, and every single one of the loop points has been offset by anywhere from 1, to 5000 samples. Now I'm seemingly forced to jump in and manually set all of these loop points again, but I'm not certain I trust that they'll remain.

      This is a major setback. Is there anything I can do here? Are there any quirks of how HISE handles samples that I should be aware of so that I can avoid this happening again?

      Thanks in advance for any guidance.

      O SimonS A 3 Replies Last reply Reply Quote 0
      • O
        Orvillain @Elezeid
        last edited by

        @Elezeid

        Maintain a dictionary of sample start/end and loop start/end points. You should be able to script this.

        Are the loop points still embedded in the audio files?

        1 Reply Last reply Reply Quote 0
        • SimonS
          Simon @Elezeid
          last edited by

          @Elezeid HISE projects, including sample maps, are trackable in git. It's well worth using and has saved me repeating work several times.

          1 Reply Last reply Reply Quote 2
          • A
            aaronventure @Elezeid
            last edited by aaronventure

            @Elezeid said in HISE seems to have butchered all of my loop points.:

            Are there any quirks of how HISE handles samples that I should be aware of so that I can avoid this happening again?

            You should absolutely use version control like Git when working with HISE. I use Git via the interface (fork.dev) for navigating the HISE repo and managing my own, and use GitHub to back them up online.

            In parallel universes where I'm not using version control while working with HISE, I've probably committed suicide at at least a dozen different points in the past 15 months precisely because of issues like the one you're describing.

            E 1 Reply Last reply Reply Quote 1
            • E
              Elezeid @aaronventure
              last edited by

              @aaronventure This is great advice. I've actually been using git to backup my project after every session, but I'm fairly new to using it so I didn't realize I could revert to a previous version.

              Thanks for pointing this out (and for the other user who mentioned this). I appreciate the guidance!

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

              20

              Online

              1.7k

              Users

              11.8k

              Topics

              102.6k

              Posts