Forum

    • Register
    • Login
    • Search
    • Categories

    Logic X "Thumbnail Generator" Crash?

    General Questions
    2
    5
    85
    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.
    • A
      ally last edited by

      Hey everyone, I'm having an issue with an exported AU crashing Logic X very occasionally. It passes validation and works fine most of the time, but it will randomly crash and give the error "99 Thumbnail Generator" or "97 Thumbnail Generator." Has anyone seen that before?

      Casey Kolb 1 Reply Last reply Reply Quote 0
      • Casey Kolb
        Casey Kolb @ally last edited by

        @ally I've seen this a bit over the years, especially with the Convolution audio waveform, but I believe it's mostly fixed in the newer develop branch. If it's a super rare crash it'll probably be fairly hard to debug. Do you have a lot of thumbnails in your app?

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

        A 1 Reply Last reply Reply Quote 0
        • A
          ally @Casey Kolb last edited by

          @Casey-Kolb It has one convolution reverb instance with 3 possible waveforms to use, so only one shown at any given time. Is there anything else that would be considered a thumbnail?

          Casey Kolb 1 Reply Last reply Reply Quote 0
          • Casey Kolb
            Casey Kolb @ally last edited by

            @ally Hm, that should be mostly fine as far as I'm aware. I believe those are the only "thumbnails".

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

            A 1 Reply Last reply Reply Quote 0
            • A
              ally @Casey Kolb last edited by

              @Casey-Kolb Coming back to say thanks! I replaced those 3 waveforms with pngs and that seems to have solved it. It wasn't super reliably replicable so won't be 100% sure till the plugin is released and people do or don't complain lol... but I haven't gotten the error again yet.

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

              15
              Online

              977
              Users

              6.6k
              Topics

              60.6k
              Posts