Skip to main content
J
Jack25238685mvan
Participant
May 9, 2023
Answered

NDI Transmit Plugin Crashes Premiere Pro

  • May 9, 2023
  • 8 replies
  • 3659 views

Hello, 

 

I recorded a few files using the new H.265 codes on my Atomos Ninja V and I encountered some difficulty trying to open them in Premiere Pro. As soon as I try to load the file in my timeline, the entire app crashes and quits (see attached photo). Has anyone experienced this before? Is there a workaround I can use in the meantime just to get these clips cut and edited? I am running Premiere Pro 23.3.0 (Build 61), which I believe is the latest version of Premiere. 

 

Thanks.

    Correct answer Chris Spiegl

    This issue persists as of 2025-06-22 and NDI Tools Version 6.2! The solution is still to delete the file "/Library/Application Support/Adobe/Common/Plug-ins/7.0/MediaCore/NewTek SpeedHQ.bundle".

     

    Once this file was deleted (and restarted Premiere Pro), I was able to import the H.265 files from my Atomos Ninja V & Shogun Ultra.

     

    I have reached out to Atomos, Adobe, and NDI, but none appears to feel responsible.

     

    Sadly, this has not been fixed yet! 1+ year after the initial report.

     

    8 replies

    K
    Karen30174540id7z
    Participant
    September 15, 2025

    I installed the latest version if the NDI Tools, including the NDI Transmit plugin for Premiere

    https://docs.ndi.video/all/using-ndi/ndi-tools/ndi-tools-for-mac

     

    I then restarted Premiere and opened my project, and the  'clip relinking' phase of opening stalled.

    I restarted the prkect and it stalled at other points and clips.

    I deleted my media chase database, but that didn't help.

     

    When I removed the plugins from the Media Core folder, and restarted Premiere, it started loading the clips properly again.

    jamieclarke
    Community Manager
    jamieclarkeCommunity Manager
    Community Manager
    September 15, 2025

    Hi @Karen30174540id7z - We have seen this before.  I will merge your post with the primary thread.  Have you contacted NDI about this issue?  please see the pinned post.

      jamieclarke
      Community Manager
      jamieclarkeCommunity Manager
      Community Manager
      July 26, 2024

      Adding the Release notes link here for the NDI suite of tools, for future reference if anything has been updated on their end.

      https://docs.ndi.video/docs/docs/release-notes

        Chris Spiegl
        Community Expert
        Chris SpieglCommunity Expert
        Community Expert
        July 26, 2024

        Since NDI does not publish the dates when they release a new version (should be mandatory IMO).

         

        We are talking about all this based on version NDI 6.0.1 on 2024-07-26 (at least that's the latest release I tested with).

          Chris Spiegl
          Community Expert
          Chris SpieglCommunity Expert
          Community Expert
          June 22, 2025

          I tested the latest release of NDI 6.2 today (2025-06-22) and the issue persists.

           

          @jamieclarke do you see any chance of this being fixed? Since it's been about a year at this point.

          C
          charlestonc3776193
          Participating Frequently
          July 25, 2024

          Any updates on this? Just encountered this recently. Downloaded my H.265 video files form my FX30 and everytime I'm previewing the footage, either Premiere Pro crashes or my entire PC freezes and have to reboot.

          I'm using a PC and its running a RTX4090 with 64gb of RAM (52 dedicated to Premiere when editing), updated the latest Nvidia Studio Driver (July 2024).
          Using Premiere Pro v24.5

          Thanks!

          Chris Spiegl
          Community Expert
          Chris SpieglCommunity ExpertCorrect answer
          Community Expert
          July 25, 2024

          This issue persists as of 2025-06-22 and NDI Tools Version 6.2! The solution is still to delete the file "/Library/Application Support/Adobe/Common/Plug-ins/7.0/MediaCore/NewTek SpeedHQ.bundle".

           

          Once this file was deleted (and restarted Premiere Pro), I was able to import the H.265 files from my Atomos Ninja V & Shogun Ultra.

           

          I have reached out to Atomos, Adobe, and NDI, but none appears to feel responsible.

           

          Sadly, this has not been fixed yet! 1+ year after the initial report.

           

            C
            charlestonc3776193
            Participating Frequently
            July 25, 2024

            that file is not in the folder. I only see dummy.txt

            jamieclarke
            Community Manager
            jamieclarkeCommunity Manager
            Community Manager
            May 28, 2024

            Discovered that the NDI tools Plugin was causing issues with this footage for some users.

              jamieclarke
              Community Manager
              jamieclarkeCommunity Manager
              Community Manager
              May 23, 2024

              Hi All @Chris Spiegl @Jack25238685mvan @Da-Cidre Would anyone be willing to send us one of these files that is crashing so that we can investigate further.  Sorry about the crashes we definitely want to get to the bottom of this issue and fix it.  My email is jamiec@adobe.com if you can send me a link to download I would appreciate it!

              Chris Spiegl
              Community Expert
              Chris SpieglCommunity Expert
              Community Expert
              May 28, 2024

              Hi @jamieclarke, thank you for taking a look into this. I was able to shoot some test files and provide them to you via email. I just sent that through. While I am also in contact with Atomos on this matter, and they are looking into it as well.

              Chris Spiegl
              Community Expert
              Chris SpieglCommunity Expert
              Community Expert
              May 23, 2024

              I just ran into the same issue with the R5C + Atomos Ninja V + H265 HQ.

              PP: 24.3 / PPBeta: 24.5 Build 42 

               

              Has anyone tested the other codec variants? Maybe it's just the HQ? Or maybe is has something todo with Premiere Pro not understanding H265 in a MOV container?

               

              I copied the files over from the MOV to a MP4 container via:

               

              ```

              ffmpeg -i file.mov -c copy out.mp4

              ```

               

              And those files then worked flawlessly.

               

              Luckily, the conversion is merely a copy from one container to another (no full on re-encoding) but still annoying enough that I will not use this workflow regularly.

               

              So, any input from those who have found a permanent solution (that does not involve the container switcheru) would be very welcome.

               

              Cheers, Chris

              D
              Da-Cidre
              Participant
              July 17, 2023

              Having similar problems as well with one clip. Did you manage to solve it?

              J
              Jack25238685mvanAuthor
              Participant
              July 17, 2023

              Nah, unfortunately, I ended up downloading a converter and converting it back to MP4 to edit the file. 

              D
              Da-Cidre
              Participant
              July 17, 2023

              Same here. Had to use Handbreak. But I don't understand what's going on? This is footage from the Sony A7SIII into the Ninja V into the H265 format right?

               

              I have a Canon R5c as well and had no problems running that footage recorded in h265 on the Ninja into premiere

              Ishan Y
              Community Manager
              Ishan YCommunity Manager
              Community Manager
              May 10, 2023

              Hey Jack,

              I understand how frustrating this must be. Could you share your system specifications and check if your GPU drivers and up to date? We recommend installing the most recent Studio Drivers if you're using an Nvidia GPU. If that doesn't fix the issue, could you share a link to a sample source file so we can get it tested? We're here to help.

               

              Thanks,

              Ishan

              Terms & ConditionsAccessibility statement
              Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices