Display Surface Initialization Failed Premiere Pro 2022

69 views

Skip to first unread message

Edco Haglund

unread,

Aug 5, 2024, 9:07:41 AM8/5/24

to antefeba

fora few days, I have been getting this extremely annoying Error in Premiere Pro. When I try to start up Premiere the splash panel comes up, but nothing happens (it doesn't show that it is loading anything). After a short time the error message 'Display Surface initialization failed' shows up and when I click 'OK', it closes.

None of these things worked and Premiere still doesn't start up. I don't know what else to do and as I'm a freelancer this problem literally costs me money. Please, does anyone have an idea what I can do to fix this?

FIXED FOR ME

Hello Everyone. I just wanted to chime in because I tried all the fixes and have spent the last 18 to 20 hours trying to fix the "'Display Surface initialization failed'" error. We got it fixed adn it was because I was connecting my monitors through a hub! So, when I connected everything directly to the computer instead of through the "Display Link" everything works but if I had it through the hub, it gave me the error message almost every time. (Except when the Adobe tech Jestin was helping)

Before that I tried:

-Updating the drivers

-Updating Windows 11

I am sure I am missing a few but basically those are the things I tried but it was having everything go through a display hub that caused the problems.

I hope that helps one of you good people.

YOU ARE AMAZING! You just saved me HOURS of trying to troubleshoot this problem. You may also note that once Premiere i sup and running, you can plug your monitor(s) back into the hub and it still works fine.

I recently got myself a 2nd monitor to help speed up my video editing. However, I can't launch Adobe Premiere with the 2nd monitor plugged in. After I launch the app, the splash screen shows up, and then after about 20-seconds, the whole thing crashes and I get this error that says "Display Surface initialization failed."

I can work around this by unplugging the 2nd monitor, launching Adobe Premeire, and then re-plugging in the 2nd monitor. It's annoying as I prefer to close the application when I'm not using it to save computer processing power. Any insight on this would be super helpful. I've looked into other posts on the forums, and no solid fix has been found. Thanks for your time!

So ... OS, basic computer specs (including GPU of course), and the details of the two monitors. How are they connected to the computer, and what settings do you have in the OS for using the two monitors?

I'm using a Windows operating system. The monitors are both LG monitors with model code: 32MN50W. The HDMI adapter is "StarTech.com USB 3.0 to Dual HDMI Adapter - 1x 4K 30Hz & 1x 1080p." The setting I'm using for the monitors is "extend these displays.

Thanks for providing great info. Sounds like a frustrating issue. Since you have a USB splitter, and @Ivan28174818i3do reported that removing that interface fixed the issue, can you test your issue with a single monitor? What happens?

Thanks for the continued help! I think you're right on the money with the splitter being the issue. I had trouble with one before, which was was I bit the bullet and upgraded to this $60 splitter. However, I guess I either got the wrong splitter or didn't spend enough. Do you have any recommendations for a good splitter?

Regarding the 2nd display port, the PC was custom built from someone and the top HDMI port doesn't work for some reason. Three of the bottom ports are similar to HMDI, but they have a weird bent shape on one end. Basically, I only have one usable HDMI input slot that I'm aware of. It's possible that a different cord of some kind could be used one of the other imput slots instead of what I'm doing. Any thoughts? Here are some pictures of the tower and back monitor to help.

Thanks for reaching out to help with this! Yes, after more testing, if I unplug one of the monitors, I'm able to launch Adobe Premiere. I can then plug the 2nd monitor back in after the program has already launched, and I don't get the crash report. That said, I'd rather not unplug and re-plug my monitor every time I launch a program.

I believe that you're correct that the issue is the splitter itself. Do you have any recommendations for hardware that could handle/is built for proper splitting? The one I'm currently using was almost $60, so I thought I spent enough to fix the issue. Would appreciate your insight on the proper tools, as I'm not educated in the intricacies of stuff like this.

This software is subject to the terms and conditions of the accompanying End User License Terms. This software is provided only for use with, and for licensed End Users of, the disguise hardware. Any other use of this software is strictly prohibited and may subject you to legal action.

All Notch blocks flickered when they were not being rendered at full frame rates when a user upgraded their project file to r27.8. As a result we removed r27.8 (build number 191665). This has now been resolved in r27.9, which includes a number of additional fixes and improvements.

In order to easily move existing points without accidentally adding new points when doing QuickAlign, a checkbox has been added to toggle on or off adding new alignment points. The checkbox is under the Interface Options menu.

ProRes video codecs are now supported for playout on Disguise. ProRes is a visually lossless codec that uses intra-frame compression, where each frame is stored independently and can be decoded with no dependencies on other frames.

We have added the option to add custom output colour primaries from Designer to enable high performance colour transforms for LED panels. This is available when Gamma Space mode is selected as the colour management mode in Project Settings. This can be found by right-clicking a LED Screen found in a project and right-clicking Colour Profile underneath the Output dropdown menu.

We have reduced the load time when a user adds a Notch layer to a project for the first time, or starts a project with a Notch layer already assigned to a track. We have enabled this as default behaviour.

We have updated the NDI SDK to support NDI 6.0. This includes improvements to the 16-bit colour formats that are supported (P216/PA16) and a new specification for NDI HDR metadata. More information on NDI 6.0 can be found in their release notes here (link). It is important to note that NDI 5.0 video inputs continue to work as expected.

Selection of objects in the Designer visualiser is prioritised based on the type of object. For example, if a camera is behind a projector, the camera will be selected even if the projector is visually in front. In previous releases, the Prop object had the lowest selection priority of all object types. This could be changed with the option switch propSelectionPriority. In this release, the default selection priority of Props has been changed so it is the same priority as a projector, puck, skeleton and 2.5D asset. It is still possible to use the option switch to change this, whereby setting propSelectionPriority to 0 is the lowest priority and 25 is the highest priority.

Two new endpoints have been added:

/quickcal/overwritemanualcalibration which overwrites the manual calibration for the given projector

/quickcal/projectorcalibration which returns information about the projector config including the error values

Prediction time (sec): How much time to predict

Sample interval threshold (sec): This is the threshold of time intervals between samples to filter out noise. If the interval time between samples is bigger, detection will be ignored.

Sample size: The number of samples to use for prediction. More samples will make prediction less prone to the noise

Terms: This is the term of curve that is used for curve fitting. Value can be set to either 1 or 2

Mesh normals can now be toggled on in the Designer visualiser. To turn on normals, go to Stage -> Visualiser Camera -> Render settings -> Object visibility -> Mesh normals. Normals will then be displayed for any mesh which is selected.

The range finder option was toggled on by default when an user upgraded their project file to r27.5. In addition, an access violation was reported during the OmniCal calibration process which led to the project freezing. As a result we removed r27.5 (build number 186871) from the website. These have now been resolved in r27.5.1, which is otherwise identical to r27.5.

We have added a range finder option to the camera visualiser to enable users to know how far away from a screen when completing pixel pitch calculations. This can be turned on by right clicking anywhere in the stage view, and then right clicking the Render settings. The Range finder can be toggled on and off from this menu and will appear as an overlay in the stage view.

Each entry will contain the Track, Layer and usage location, shown as the timecode time from the timeline. A left-click on the entry will jump the playhead to the start of the layer that uses that piece of media.

In previous releases, both DMX and OSC packets were received independently and actioned by each Disguise media server running in the session. We have changed this behaviour so that both DMX and OSC packets are now received by the director machine running in the session and distributed to the actors. This means that all DMX and OSC packets are executed at the same timestamp.