[Bug 21017] New: Adobe Premiere Pro CS4 won't start

http://bugs.winehq.org/show_bug.cgi?id=21017

Summary: Adobe Premiere Pro CS4 won't start
           Product: Wine
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

Created an attachment (id=25215)
 --> (http://bugs.winehq.org/attachment.cgi?id=25215)
Log of Premiere Pro CS4 itself

To reproduce this you'll have to install Premiere Pro CS4 using wine 1.1.16
(there's also a patch available for current trunk)

I believe this beginning error lies somewhere in msxml and gdiplus.

(You can get a lot further in the program using native dll's (like msxml and
gdiplus) but then you're not allowed to post bugs for obvious reasons. You can
try it out using the same winetricks for Photoshop CS4)

[Bug 21017] Adobe Premiere Pro CS4 won't start

http://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #1 from Vincent Povirk   2009-12-14 17:01:37 ---
Well, can you get a +msxml,+gdiplus,+seh,+tid log then? ;)

[Bug 21017] Adobe Premiere Pro CS4 won't start

http://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #2 from Jelle De Loecker   2009-12-14 17:09:42 ---
Created an attachment (id=25216)
 --> (http://bugs.winehq.org/attachment.cgi?id=25216)
Log with extra WINEDEBUG parameters

Log output with WINEDEBUG=+msxml,+gdiplus,+seh,+tid

Sorry, forgot all about the extra logging.

[Bug 21017] Adobe Premiere Pro CS4 won't start

http://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #3 from Vincent Povirk   2009-12-14 17:39:47 ---
Hmm, this isn't clear to me at all. I blame the exception at

0009:trace:msxml:isaxattributes_getLength Length set to 0
0009:trace:msxml:isaxattributes_Release 0x231d0030
0009:trace:seh:raise_exception code=c0000005 flags=0 addr=0xf6afe1b8
ip=f6afe1b8 tid=0009

Apparently the code branched to a bad address somehow. :/

[Bug 21017] Adobe Premiere Pro CS4 won't start

http://bugs.winehq.org/show_bug.cgi?id=21017

Vincent Povirk  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|-unknown                    |msxml3

[Bug 21017] Adobe Premiere Pro CS4 won't start

http://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #4 from Jelle De Loecker   2009-12-14 18:06:25 ---
Created an attachment (id=25217)
 --> (http://bugs.winehq.org/attachment.cgi?id=25217)
Log from wine 1.1.34

Hmm...

Is it normal that I can't reproduce the exact same log report using the same
wine version? (trying it again, there is no more reference to
"addr=0xf6afe1b8")

Btw, I did try that log using the latest git, not wine 1.1.34.

The new attached log is using wine 1.1.34, and is 30 kB's smaller.

(It seems like wine itself crashes in 1.1.34 and adobe fires up it's crash
reporter in the git version)

[Bug 21017] Adobe Premiere Pro CS4 won't start

http://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #5 from Vincent Povirk   2009-12-14 18:20:51 ---
Yes, the address itself probably isn't meaningful.

[Bug 21017] Adobe Premiere Pro CS4 won't start

http://bugs.winehq.org/show_bug.cgi?id=21017

Vitaliy Margolen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|msxml3                      |-unknown
            Version|unspecified                 |1.1.34

[Bug 21017] Adobe Premiere Pro CS4 won't start

http://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #6 from Dmitry Timoshkov   2009-12-15 01:57:29 ---
(In reply to comment #0)
> To reproduce this you'll have to install Premiere Pro CS4 using wine 1.1.16

Is there a bug report for that regression? Where is the regression test
results?
> (there's also a patch available for current trunk)

What patch is that?

[Bug 21017] Adobe Premiere Pro CS4 won't start

http://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #7 from Jelle De Loecker   2009-12-15 02:26:04 ---
There are several mentions of this on the Photoshop CS4 app page itself
(Premiere Pro CS4 and Photoshop CS4 use the same installer)

I didn't think I should create a new bug for it since bug 18070 was created for
the Photoshop CS4 installer.

I could add the debug results with wine 1.1.16.

Attachment id=25093 (from that bug 18070) is the patch that makes the installer
work again on current trunk.

[Bug 21017] Adobe Premiere Pro CS4 won't start

http://bugs.winehq.org/show_bug.cgi?id=21017

Petroy  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1

--- Comment #8 from Petroy   2010-01-15 11:02:51 ---
*** This bug has been confirmed by popular vote. ***

[Bug 21017] Adobe Premiere Pro CS4 won't start

http://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #9 from Austin English  2011-10-02 11:45:42 CDT ---
This is your friendly reminder that there has been no bug activity for 1 year.
Is this still an issue in current (1.3.29 or newer) wine?

[Bug 21017] Adobe Premiere Pro CS4 won't start

http://bugs.winehq.org/show_bug.cgi?id=21017

Ken Sharp  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
         Depends on|                            |18070

[Bug 21017] Adobe Premiere Pro CS4 won't start

http://bugs.winehq.org/show_bug.cgi?id=21017

Fincer  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 21017] Adobe Premiere Pro CS4 won't start

http://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #10 from Fincer  ---
Still present in Wine 1.7.12

Very hard to say where this bug is related but at least I can get a bit further
if doing the following steps:

-------------------

1. To get loading process bit further, you need to add wmvcore.dll from Windows
OS (system32). I set it as native library in winecfg.

Maybe it's better to execute

winetricks allcodecs

and then do the step one, not sure. Anyway, after DLL have been copied to the
correct system32 directory and set to native...

---
2. Run Adobe Premiere

---
3. It gets stuck to the following message (terminal output):

err:ole:CoGetClassObject no class object {e1c73132-0196-4fe2-b8cd-a428cebeb239}
could be created for context 0x4

---
4. Open wine regedit and take backup of key named
{e1c73132-0196-4fe2-b8cd-a428cebeb239}

---
5. Kill Adobe Premiere forcefully

---
6. Delete the mentioned registry key with subkeys

---
7. If you run Adobe Premiere once again, some plugins should be loaded.
However, Premiere gets stuck again. Once I renamed the following file...

C:\Program Files\Adobe\Adobe Premiere Pro
CS4\MediaIO\writers\WinMediaWriter.vwr -> WinMediaWriter.vwr.old

I got a bit further. Currently I'm stuck at "Loading FLV | MP4" dialog.

---
8. Premiere doesn't load twice. You need to repeat steps 1 - 7 in order to get
it start to load some plugins again. By learning myself I've figured out that
the registry key {e1c73132-0196-4fe2-b8cd-a428cebeb239} is an important factor.

-------------------

In addition, Premiere is loading mlang.dll from system32 directory. Not sure,
if this is relevant information at all. I copied mlang.dll from Windows OS
installation and set it to native in winecfg library tab.

[Bug 21017] Adobe Premiere Pro CS4 won't start

http://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #11 from Fincer  ---
In order to get Adobe Premiere CS4 installed (if normally installation
procedures don't work), follow/apply the instructions here:

http://appdb.winehq.org/objectManager.php?sClass=version&iId=9488

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #12 from Austin English  ---
Is this still an issue in current (1.7.36 or newer) wine? If so, please attach
terminal output.

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #13 from Fincer  ---
Created attachment 50785
  --> https://bugs.winehq.org/attachment.cgi?id=50785
Premiere Pro CS4 terminal output (without debugging)

Yes it is. The startup process hangs on loading "SolidComposite.AEX" and
finally the whole program crashes. Wine 1.7.36 32-bit.

File location:
Premiere_Installation_Directory\Plug-ins\Common\AEFilters\SolidComposite.AEX

Because backtrace logs are exceptionally huge, I provide them as link
attachments. I'm sorry if uploading that much of tracing log makes you feel
frustated. However, I still want to provide as much information as I can to
make it easier to trace and possibly fix this problem.

+win,+nls backtrace log:
https://www.dropbox.com/s/my0uk5c8p3lufhq/premiereprocs4_win_nls_backtrace?d...

+ole backtrace log:
https://www.dropbox.com/s/43da6b0qghvnfl0/premiereprocs4_ole_backtrace?dl=1

----------------------------------

Short terminal output (without debugging) as a normal attachment.

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #14 from Fincer  ---
Created attachment 50786
  --> https://bugs.winehq.org/attachment.cgi?id=50786
Adobe Premiere Pro CS4 Windows crash log file (xml)

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #15 from Fincer  ---
Created attachment 50793
  --> https://bugs.winehq.org/attachment.cgi?id=50793
Premiere Pro CS4 loading, wmvcore disabled

I checked my logs and I think this is not a case of loading SolidComposite.AEX
but instead Ellipse.AEX.

Anyway, it seems that we may have actually two issues here:

1) builtin wmvcore library causes the crash event described above. Disabling it
or using a native one let the program load one step further and more important,
the program *does not crash*. This is not much, though. And causes a lot of
complaints about missing program-related "Windows media importer"
libraries/stuff.

2) Premiere AEX libraries (After Effects Plugins) do not load -> stuck. They
load on Premiere Pro CS3. So something has changed between CS3 and CS4 versions
of Premiere Pro AEX libraries.

If I prevent Ellipse.AEX from loading, the program gets stuck with the next AEX
libary on the list, one by one. And it keeps going so far that after removing
all AEX files causes Premiere's processcoordinationserver.exe to crash.

I disabled wmvcore library on winecfg just for testing. Output as an
attachment.

long rpc backtrace log uploaded here (1.5 MB):
https://www.dropbox.com/s/5yd1u183agmpfvb/premierecs4_rpc_trace?dl=1

If any more logs/tests are required, please let me know.

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #16 from [e-mail] ---
Could you test 1.8 or 1.9 series of wine?

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #17 from Fincer  ---
@winetest

Hi there,

just tested Premiere Pro CS4 with Wine 1.9.21 32-bit with MSI Dummy patch
applied (just for program installation). Patch here:
http://bugs.winehq.org/show_bug.cgi?id=18070

Unfortunately, I still can't start the program. According to Wine terminal
output it has problems to determine the proper OpenGL version. As I run the
program, I get the following output in terminal:

OpenGL version as determined by Extensionator...
OpenGL Version Error determining GL version.Internal return value: 1 
Device: 0015D37C has video RAM(MB): 128
Vendor string:    Intel Open Source Technology Center
Renderer string:  Mesa DRI Intel(R) Haswell Mobile x86/MMX/SSE2
Version string:   3.0 Mesa 10.4.3
AIF Internal exception

And then crash.

As I posted on 2015-02-19, the graphical loading screen still shows that
loading of the program gets stuck at AEX (and DLL) files located at
drive_c/Program Files/Adobe/Adobe Premiere Pro CS4/Plug-ins/Common/ folder.
Once again, I tried renaming and removing of these files without any luck.

Some folks on several forums suggest to run GPUSniffer.exe located at Adobe
Premiere Pro CS4 main folder in order to determine current GPU version. Well,
that works fine on Windows but I can't run it on Wine because it simply crashes
on Wine. And I don't think it's great help anyway because the problem we have
seems to relate to a proper determination of used OpenGL version in Wine, not
to specification of our GPU name or whatsoever.

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #18 from Fincer  ---
The same OpenGL problem I described above happens with GeForce GTX 760M, too.

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #19 from Fincer  ---
Created attachment 56205
  --> https://bugs.winehq.org/attachment.cgi?id=56205
Premiere Pro CS4 - Wine Staging 1.9.23 - OpenGL determination error

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #20 from Fincer  ---
Allright,

I tested Adobe Premiere Pro CS4 with Wine Staging 1.9.23 (32-bit) which should
have improved GPU support.

As already said, the program seems to crash in OpenGL determination process.
The same crash event is present in both normal and staging versions of Wine.

I think the bug affects *every* newer Adobe software (After Effects etc.) which
take more advantage of GPU focused processing methods. These methods were not
present in older Adobe program versions. It explains why, for example, Premiere
Pro CS3 works quite well.

The extent of this problem makes the issue a major one. It probably affects
almost every newer Adobe production software (excluding Adobe Photoshop CC
where the accelerated GPU support is still optional and not loaded during the
program launch process?).

Anyway. Using both normal and staging versions of Wine, the program gets stuck
while loading "Write_on.AEX" plugin and then crashes. It is able to load
several plugins before that one.

What's noteworthy is that everytime any plugin is loaded, the following OpenGL
error occurs in terminal:

OpenGL version as determined by Extensionator...
OpenGL Version Error determining GL version.Internal return value: 1

and

err:winediag:wined3d_dll_init Setting maximum allowed wined3d GL version to
3.2.

Short informal & partial "debug" log as attachment (Wine Staging 1.9.23 used):

https://bugs.winehq.org/show_bug.cgi?id=21017#c19

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #21 from Fincer  ---
Created attachment 56225
  --> https://bugs.winehq.org/attachment.cgi?id=56225
Premiere Pro CS4 - Wine Staging 1.9.23 - OpenGL determination error

Damn it! Please ignore the previous attachment, it's just a stupid copy of my
comment. Don't know how did I mix these texts in the first place. Please delete
it, if possible.

Correct attachment here.

Apologies.

Though I used an experimental CSMT feature in Wine Staging, it doesn't really
matter because the same error occurs whether it's enabled or not (yes, I tested
it).

I used my laptop's Intel card for this testing. Same OpenGL errors occur with
Nvidia card (GTX 760M), too (yes, I tested it).

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

Matteo Bruni  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #56205|0                           |1
        is obsolete|                            |

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #22 from Fincer  ---
The same GL error is still present in the latest wine version 2.1

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #23 from Fincer  ---
Still present in Wine 2.3.

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

Luke Short  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #24 from Luke Short  ---
The exact same OpenGL error is still present in Wine Staging 2.19.

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #25 from Luke Short  ---
Created attachment 59592
  --> https://bugs.winehq.org/attachment.cgi?id=59592
OpenGL Version Error (Debug)

The main error in here is a false-positive report:

warn:wgl:is_extension_supported The function requires OpenGL version '3.3'
while your drivers only provide '3.2'
warn:wgl:wglGetProcAddress Extension GL_VERSION_3_3 required for
glVertexAttribDivisor not supported

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #26 from Luke Short  ---
(In reply to Luke Short from comment #25)
> Created attachment 59592 [details]
> OpenGL Version Error (Debug)
>
> The main error in here is a false-positive report:
>
> warn:wgl:is_extension_supported The function requires OpenGL version '3.3'
> while your drivers only provide '3.2'
> warn:wgl:wglGetProcAddress Extension GL_VERSION_3_3 required for
> glVertexAttribDivisor not supported

I found a bug that reports the same exact problem as we are experiencing here
with Adobe Premiere Pro CS4. That bug has already been fixed so a similar patch
may be needed here.

https://bugs.winehq.org/show_bug.cgi?id=39769

My OpenGL version is definitely higher than 3.3.

```
$ optirun glxinfo | grep "OpenGL version"
OpenGL version string: 4.5.0 NVIDIA 384.90
```

The Adobe Premiere Pro CS4 trial can be downloaded for testing by following
these instructions:

http://prodesigntools.com/download-adobe-cs4-and-cs3-free-trials-here.html

For getting past a lot of issues with launching Premiere after installation
(and to get to the OpenGL error) some of these Winetricks overrides are
required:

```
adobeair
atmlib
colorprofile
corefonts
gdiplus
gdiplus_winxp
mfc42
msls31
msvcirt
msxml3
msxml6
riched20
riched30
vb6run
vcrun2005
vcrun2008
vcrun2010
vcrun6sp6
vcrun6
```

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017
Bug 21017 depends on bug 18070, which changed state.

Bug 18070 Summary: Multiple apps need separate msi custom action server process due to COM/MTA and/or isolation issues (Adobe CS3/CS4, Flash, Windows SDK 2008, Strawberry Perl, MS Office 2010)
https://bugs.winehq.org/show_bug.cgi?id=18070

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|STAGED                      |RESOLVED
         Resolution|---                         |FIXED

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

Louis Lenders  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #27 from Louis Lenders  ---
Hi, I tried this from

https://trials2.adobe.com/Applications/PremierePro/CS4/Win/ADBEPPROCS4_LS7.7...

and

https://trials2.adobe.com/Applications/PremierePro/CS4/Win/ADBEPPROCS4_LS7.e...

The program starts fine for me using winetricks atmlib, and using a native
msdmo.dll, copied from my windows-drive. I`ll have a look into this later this
week. I think opengl error is gone (???).

- Note1: the installer was not rendered properly (no checkuttons visible) but
with tab-key you can selsct options
- Note2: while trying to extract the installer had a crash, but appaently the
setupfiles were still exracted in ~/.wine/drive_c/users/myname../Desktop

sha1sum ADBEPPROCS4_LS7.*
a861fb29a39e753402f81d0e0a5d19f342569035  ADBEPPROCS4_LS7.7z
2d0d5da2ec79c1410a9d88be3e48d6d127256274  ADBEPPROCS4_LS7.exe

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #28 from Louis Lenders  ---
Created attachment 61323
  --> https://bugs.winehq.org/attachment.cgi?id=61323
+msdmo,+seh log

attached +msdmo,+seh log

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #29 from Louis Lenders  ---
Created attachment 61324
  --> https://bugs.winehq.org/attachment.cgi?id=61324
stub atmlib

attached a stub atmlib.dll patch. I don`t know if this dll is present by
default on windows. This patch allows Premiere + native msdmo only to start

atmlib functions are documented here: 
web.mit.edu/PS/Adobe/Documents/5073.ATM_Adv_Win.ps

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

tokktokk  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #30 from Louis Lenders  ---
Hi, I`m posting some info here that applies to the trial.

This bugreport is somehow dealing with too many issues so my suggestion is:
could any of the reporters/commenters try the recipe below, then if the
application starts we can resolve this as fixed

1. The trial starts just for me disabling wmvcore (in wincfg)

2. If you don`t disable wmvcore, you`ll need a`` winetricks wmp10`` _and_ use a
native msdmo, then it starts fine as well.

These issues 1 and 2 need to be tracked by new bugreports I guess. The issue
where the most comments of this bugreport is about (the OpenGL error) is AFAICT
fixed, but really need confirmation by one of the reporters/commenters

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #31 from Luke Short  ---
The OpenGL error is only present if "wmvcore" is enabled. Disabling that DLL
removes that error.

I am still running into issues launching the program. Method #1 seems to be the
most reliable on my two test machines. However, I still cannot fully launch the
application.

It gets stuck on the purple "Adobe Premiere CS4" start pop-up. I have tested
with Wine 3.8 32-bit (both development and staging) in clean prefixes. There
are a lot of fixmes from NdrCoellation* functions. Here are the last few lines
of output from Wine before Premiere hangs on the launch screen pop-up.

```
003b:fixme:rpc:calc_arg_size Simple reference pointer (type 0x8).
003b:fixme:rpc:calc_arg_size Simple reference pointer (type 0x8).
003b:fixme:rpc:calc_arg_size Simple reference pointer (type 0x8).
003b:fixme:rpc:calc_arg_size Simple reference pointer (type 0x8).
004c:fixme:ole:NdrCorrelationInitialize (0x214f560, 0x214f63c, 1024, 0x0):
semi-stub
004c:fixme:rpc:calc_arg_size Simple reference pointer (type 0x8).
004c:fixme:rpc:calc_arg_size Simple reference pointer (type 0x8).
004c:fixme:rpc:calc_arg_size Simple reference pointer (type 0x8).
004c:fixme:rpc:calc_arg_size Simple reference pointer (type 0x8).
004c:fixme:ole:NdrCorrelationFree (0x214f560): stub
003b:fixme:ole:NdrCorrelationFree (0x9e2ef1c): stub
003b:fixme:ole:NdrCorrelationInitialize (0x9e2ef5c, 0x9e2f0ec, 1024, 0x0):
semi-stub
004b:fixme:ole:NdrCorrelationInitialize (0x203f560, 0x203f63c, 1024, 0x0):
semi-stub
004b:fixme:ole:NdrCorrelationFree (0x203f560): stub
003b:fixme:ole:NdrCorrelationFree (0x9e2ef5c): stub
003b:fixme:ole:NdrCorrelationInitialize (0x9e2ef5c, 0x9e2f0ec, 1024, 0x0):
semi-stub
004c:fixme:ole:NdrCorrelationInitialize (0x214f560, 0x214f63c, 1024, 0x0):
semi-stub
004c:fixme:ole:NdrCorrelationFree (0x214f560): stub
003b:fixme:ole:NdrCorrelationFree (0x9e2ef5c): stub
003b:fixme:ole:NdrCorrelationInitialize (0x9e2f05c, 0x9e2f1ec, 1024, 0x0):
semi-stub
004b:fixme:ole:NdrCorrelationInitialize (0x203f560, 0x203f63c, 1024, 0x0):
semi-stub
004b:fixme:ole:NdrCorrelationFree (0x203f560): stub
003b:fixme:ole:NdrCorrelationFree (0x9e2f05c): stub
```

Thanks for all of your hard work on this so far, Louis!

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #32 from Louis Lenders  ---
(In reply to Luke Short from comment #31)
> The OpenGL error is only present if "wmvcore" is enabled. Disabling that DLL
> removes that error.
>
> I am still running into issues launching the program. Method #1 seems to be
> the most reliable on my two test machines. However, I still cannot fully
> launch the application.

Hi, thanks for testing it. Let`s keep this bug open then.

- Could you provide a bit more info: is this with the retail version or the
trial?
- Also, what graphics card do you have? I have a cheap intel onboard card, so
i`m i bit suprised that it starts here. Maybe fiddling with reported opengl
version could help a bit (if i`m not mistaken i think setting mesa environment
variables can do that?) I guess you have the same problem as in comment 5:

fixme:win:EnumDisplayDevicesW ((null),0,0x33f354,0x00000000), stub!
Query adapter ram failed. Error code = 0x 80041002
Vendor string:    Intel Open Source Technology Center
Renderer string:  Mesa DRI Intel(R) Haswell Mobile x86/MMX/SSE2
Version string:   3.0 Mesa 10.4.3

OpenGL version as determined by Extensionator...
OpenGL Version Error determining GL version.AIF Internal exception
Internal return value: 1

- adding a +wgl,+opengl debuglog might be useful (?)

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #33 from Louis Lenders  ---
Additional note to my last comment:

Also while testing do it in a virtual desktop ( set it in winecfg) because all
these Adobe programs sometimes pop up error or info messageboxes, that appear
behind the splash screen.

It then looks as if the program is stuck/hangs, but you really just have to
click a button in the messagebox, that is behind the splash screen....

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #34 from Louis Lenders  ---
Hi, did a bit of more testing, and maybe this is related to bug 43060

I can more or less reproduce some output, and not starting of the program by
running like:

LIBGL_ALWAYS_SOFTWARE=1  WINEDLLOVERRIDES=wmvcore=d wine Adobe\ Premiere\
Pro.exe
(did not set any registry key)

Then I get too:

OpenGL version as determined by Extensionator...
OpenGL Version Error determining GL version.AIF Internal exception
Internal return value: 1

If I add environment variables like
LIBGL_ALWAYS_SOFTWARE=1 MESA_GL_VERSION_OVERRIDE=1.4
MESA_GLSL_VERSION_OVERRIDE=140 WINEDLLOVERRIDES=wmvcore=d wine Adobe\ Premiere\
Pro.exe

then the program starts.

So might be worth a try (I guess) to run the program like:

"MESA_GL_VERSION_OVERRIDE=1.4 MESA_GLSL_VERSION_OVERRIDE=140
WINEDLLOVERRIDES=wmvcore=d wine Adobe\ Premiere\ Pro.exe"

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #35 from Luke Short  ---
Both of my test systems are Fedora 28 (64-bit) with proprietary NVIDIA graphics
drivers. I am using the Adobe Premiere CS4 trial (not the full product).

Using the overrides you (Louis) recommended finally gets the program fully
opening for me!

"MESA_GL_VERSION_OVERRIDE=1.4 MESA_GLSL_VERSION_OVERRIDE=140
WINEDLLOVERRIDES=wmvcore=d wine Adobe\ Premiere\ Pro.exe"

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #36 from Louis Lenders  ---
> Using the overrides you (Louis) recommended finally gets the program fully
> opening for me!
>
> "MESA_GL_VERSION_OVERRIDE=1.4 MESA_GLSL_VERSION_OVERRIDE=140
> WINEDLLOVERRIDES=wmvcore=d wine Adobe\ Premiere\ Pro.exe"

Hi Luke, thanks for testing. Then this bug is either a duplicate now or the
initial bug (crash) is fixed. 
The problem is/was really GpuSniffer.exe either crashing or returning error.
I`m very busy now, but i`ll revisit this bug later to resolve carefully.
Regards

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #37 from Luke Short  ---
The previous workaround no longer appears to work in Wine 4.0.

===============
LIBGL_ALWAYS_SOFTWARE=1 MESA_GL_VERSION_OVERRIDE=1.4
MESA_GLSL_VERSION_OVERRIDE=140 WINEDLLOVERRIDES=wmvcore=d wine Adobe\ Premiere\
Pro.exe
===============

Behind the Premiere start-up splash page is a dialogue box with this error:

===============
"Adobe Premiere Pro could not find any capable video play modules. Please
update your video display drivers and start again."
===============

Starting Premiere without any special arguments/overrides leads to the same
generic OpenGL version error from before:

===============
OpenGL version as determined by Extensionator...
OpenGL Version Error determining GL version.Internal return value: 1
===============

I am using a Nvidia GTX 960 with the 415.27 proprietary graphics driver.

[Bug 21017] Adobe Premiere Pro CS4 won't start

https://bugs.winehq.org/show_bug.cgi?id=21017

Julius Schwartzenberg  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |julius.schwartzenberg@gmail
                   |                            |.com

--- Comment #38 from Julius Schwartzenberg  ---
I see the same "Adobe Premiere Pro could not find any capable video play
modules. Please update your video display drivers and start again." with Wine
4.12.1 with winetricks wmp10 and native msdmo.dll.

What was the last version in which it ran? Maybe it makes sense to do a bisect?

[Bug 21017] Adobe Premiere Pro CS4 won't start

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=21017

--- Comment #39 from Luke Short  ---
I am still encountering the same issues mentioned previously using Wine 5.0rc2.
Wine 3.8 was the last version where we were able to get this to work.

[Bug 21017] Adobe Premiere Pro CS4 won't start

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=21017

Neko-san  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]