Hello
as I understand avidemux 2.6.19 should run under Win XP.
On my computer and on a computer of a friend it does not run under native XP but it works in a VM with XP.
I think the developer test avidemux with XP only in VMs.
Does anybody know how to make avidemux running under native XP?
Sorry for my english.
Could you give relevant details?
What doesn't work on native XP? (Possibly see debug log.)
Ftr, which VM(s) does it work in?
Sorry I have forgotten the half.
Avidemux does not start under native XP. The program window flashes up short and then avidemux ends.
In admlog.txt the last few columns are:
...
Probing for DXVA2...
[init] 16:45:49-040 Probing for D3D support
[init] 16:45:49-415 D3D library loaded, creating instance
When I start avidemux under XP in VBox admlog.txt is much longer.
...
Probing for DXVA2...
[init] 16:56:05-608 Probing for D3D support
[init] 16:56:06-590 D3D library loaded, creating instance
[ADM_FAILED] 16:56:06-680 Failed with error code=0x8876086a
[init] 16:56:06-770 D3D:Cannot create d3d9 device
[init] 16:56:06-820 D3D:D3D init failed
[dxva2Probe] 16:56:06-850 D3D init failed
DXVA2 not available
Probing for SDL...
Probing for SDL...
Calling initSDL with driver=dummy
...
Maybe there is a problem with video acceleration because 3D acceleration in the VM is not activated.
Fwiw, I confirm v2.6.19 starts correctly on Win XP in Virtual PC 2004 SP1 (5.3.582.27) too.
@ Slowthinker,
Could you try "recent" win32 nightlies (http://www.avidemux.org/nightly/win32/) to narrow down possible regression timeframe?
Don't you get any crash/debug data from Windows (tools)?
PS:
Could someone (= mean!?) restore correct thread subject?
Also, could this thread be moved to Windows area?
http://www.avidemux.org/nightly/win32/avidemux_2.6.19_r170329_win32.exe shows the same behaviour and ends at the same point:
admlog.txt
...
Probing for DXVA2...
[init] 11:36:29-123 Probing for D3D support
[init] 11:36:29-279 D3D library loaded, creating instance
The event viewer from XP contains no corresponding entry.
...
With filemon.exe from sysinternals.com I have figured out that avidemux accesses at least d3d9.dll and d3d8thk.dll.
After deleting d3d9.dll out of system directories from XP avidemux starts and I can load a video to its editor. So it confirms my suspicion that the issue relies on 3D acceleration more or less :)
admlog.txt:
...
Probing for DXVA2...
[init] 11:59:26-701 Probing for D3D support
[init] 11:59:26-717 Dxva2: Cannot load d3d9.dll
[init] 11:59:26-717 D3D:D3D init failed
[dxva2Probe] 11:59:26-717 D3D init failed
DXVA2 not available
Probing for SDL...
Probing for SDL...
Calling initSDL with driver=dummy
...
I think it is not a good solution to delete d3d9.dll permanently. Maybe any developer can use this information to terminate the issue.
---
EDIT:
Meanwhile a friend of me figured out that it is possible to deactivate 3D acceleration in dxdiag or in Windows XP display properties (I do not know the exact path in english because I am using a german version). With that adjustment avidemux starts too.
EDIT2:
Is it possible to start avidemux with a commandline parameter to ignore 3D acceleration? Or is there a config file which allows that?
So it does not work if you let avidemux try to use hw accel ?
Might be the D3D9ext probe failing, as windows XP does only have D3D9
Quote from: Slowthinker on April 01, 2017, 12:17:50 PM
http://www.avidemux.org/nightly/win32/avidemux_2.6.19_r170329_win32.exe shows the same behaviour and ends at the same point:
avidemux_2.6.19_r170329_win32.exe actually equals v2.6.19 release.
Could you try ("all as needed") older files?
Quote from: mean on April 01, 2017, 01:16:12 PM
Might be the D3D9ext probe failing, as windows XP does only have D3D9
Guess:
ADM_coreD3D.cpp (https://github.com/mean00/avidemux2/blob/579ab2ad2cd608b488fc22d5f99f494db9340f17/avidemux/common/ADM_render/ADM_coreDxva2/src/ADM_coreD3D.cpp#L190)
D3DCall(IDirect3D9,GetAdapterDisplayMode,d3d9, adapter, &d3ddm);
misses "... if(ADM_FAILED(hr)) ..."?
Quote from: mm0359 on April 01, 2017, 01:50:25 PM
avidemux_2.6.19_r170329_win32.exe actually equals v2.6.19 release.
Could you try ("all as needed") older files?
I have tried 2.6.15, .18 and .19.
All version crashes.
2.6.8 is the last working version. As far as I know 2.6.9 to 2.6.13 are not programmed for XP.
Quote from: mean on April 01, 2017, 01:16:12 PM
So it does not work if you let avidemux try to use hw accel ?
I think I cannot affect if avidemux try to use hardware acceleration. I only can deactivate the acceleration in Windows.
QuoteMight be the D3D9ext probe failing, as windows XP does only have D3D9
I don't know. I never examine 3D features because I never used it knowingly.
Quote from: Slowthinker on April 01, 2017, 04:58:47 PM
I have tried 2.6.15, .18 and .19.
All version crashes.
2.6.8 is the last working version. As far as I know 2.6.9 to 2.6.13 are not programmed for XP.
It's already a good start to know it regressed between v2.6.8 and v2.6.15.
(Iirc,) v2.6.14 too should work as is on Win XP.
For v2.6.9 to v2.6.13, see
http://avidemux.org/smif/index.php/topic,17055.msg76689.html#msg76689 (http://avidemux.org/smif/index.php/topic,17055.msg76689.html#msg76689)
NB:
I used to have a native XP, but I never had this bad behavior.
Its hardware is (currently/now) broken.
Do you have d3d9.dll on your XP in VirtualBox?
If not, could you test copying it from your native XP?
Meanwhile I have tested 2.6.14 and it works.
In admlog.txt ist no entry for "d3d9.dll".
So the error must have come with a change from 2.6.14 to 2.6.15.
Toward my statement from yesterday 2.6.14 is the last working version under native XP with activated 3D acceleration.
d3d9.dll exists on my XP in VirtualBox and it seems to be the same Version (5.03.2600.5512 (xpsp.080413-0845)).
The deciding different is the deactivated 3D acceleration in the VM environment. I have not installed the 3D extension for 3D in any virtual machine.
Quote from: Slowthinker on April 02, 2017, 01:40:31 PM
So the error must have come with a change from 2.6.14 to 2.6.15.
The deciding different is the deactivated 3D acceleration in the VM environment.
Thanks for (all) the details!
It seems to make sense:
2016-11-19: 2.6.15 : Improved hardware decoding / encoding and usability bugfixes.
* Hw Accel : Experimental Dxva2 video decoder + Dxva2/D3D display engine (windows)
After some weeks I have remembered the issue and have tested the newest nightly avidemux_2.7.0_r170625_win32.
It crashes reproducibly under XP with activated 3D acceleration also.
i'll try disabling some hw accel to see if it helps
Please retry in a couple of days
Thank you. I 'll report.
I have tested avidemux_2.7.0_r170712_win32 just. It crashes also.
EDIT:
avidemux_2.7.0_r170727_win32