https://bugs.winehq.org/show_bug.cgi?id=48584
Bug ID: 48584 Summary: DTS Master Audio Suite displays a black window if dxvk is installed Product: Wine Version: 5.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: shagooserver@gmail.com Distribution: ---
DTS-MS is installed in a separate prefix, .winedts, while dxvk is installed in the .wine prefix. The display will not display until dxvk is disabled in the .wine prefix.
https://bugs.winehq.org/show_bug.cgi?id=48584
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #1 from Zebediah Figura z.figura12@gmail.com --- Is the bug here that DXVK is affecting an unrelated prefix? If so, what is the value of WINEPREFIX, and from what directory are you running the application?
If the bug is just "DXVK doesn't work", however, then please file a bug with the DXVK project itself; DXVK is not supported by this bug tracker.
https://bugs.winehq.org/show_bug.cgi?id=48584
--- Comment #2 from Scott shagooserver@gmail.com --- The bug is in part as you described, that DXVK is effecting an unrelated prefix.
To give a bit more detail the DTS-MA window pops up correctly for about 1 second then just turns completely black. It seems that when the DTS-MA program connects to it's client there is a change in the buffer size from 600 x 343 to 864 x 701 which may be the cause of the problem.
I do not understand what you want when you ask for the value of the wine prefix.
I use a desktop launcher to start DTS-MA as follows:
[Desktop Entry] Exec=konsole --workdir /home/scott/.winedts/drive_c/"Program Files"/DTS/MAS-SAS -e bash -c "WINEPREFIX=~/.winedts wine cmd | wine dtshd.exe" Icon=/home/scott/Pictures/icons/dts.ico Name=DTS MA StartupNotify=true Terminal=false Type=Application X-KDE-SubstituteUID=false
Although running the program from the installed directory gives the same result.
I do not have sufficient knowledge to determine whether the bug is in DXVK or not, or whether there are 2 bugs, one in wine and one in DXVK. If you are able to clarify this for me I am more than happy to take up the issue with them.
https://bugs.winehq.org/show_bug.cgi?id=48584
--- Comment #3 from Zebediah Figura z.figura12@gmail.com --- WINEPREFIX is the environment variable that selects which prefix is in use.
Exec=konsole --workdir /home/scott/.winedts/drive_c/"Program Files"/DTS/MAS-SAS -e bash -c "WINEPREFIX=~/.winedts wine cmd | wine dtshd.exe"
This won't do what you want it to do; bash environment variables only affect the immediate command and not any commands that you've piped from it. You'll need to do something like "WINEPREFIX=~/.winedts wine cmd | WINEPREFIX=~/.winedts wine dtshd.exe", or alternatively move the WINEPREFIX assignment earlier in the command line.
https://bugs.winehq.org/show_bug.cgi?id=48584
--- Comment #4 from Scott shagooserver@gmail.com --- "WINEPREFIX=~/.winedts wine cmd | WINEPREFIX=~/.winedts wine dtshd.exe"
This causes the program to hang during launch, a window pops up and just stops at about 25%.
https://bugs.winehq.org/show_bug.cgi?id=48584
--- Comment #5 from Zebediah Figura z.figura12@gmail.com --- It's not unlikely that the program was incorrectly installed, if you used a similar command to install it. You may want to try wiping the .winedts prefix and trying again.
Separately, I'm curious what you're trying to accomplish by piping the output of "wine cmd".
https://bugs.winehq.org/show_bug.cgi?id=48584
--- Comment #6 from Scott shagooserver@gmail.com --- The piping is to simulate the command being entered from the program's directory location as entering the wineprefix command from any other location will fail.
https://bugs.winehq.org/show_bug.cgi?id=48584
--- Comment #7 from Zebediah Figura z.figura12@gmail.com --- (In reply to Scott from comment #6)
The piping is to simulate the command being entered from the program's directory location as entering the wineprefix command from any other location will fail.
That seems strange, if the "--workdir" command does indeed act as one would expect. If nothing else, "cd" should be enough to achieve what you want. I'm also not sure that "cmd" executed like that will ever terminate, which probably isn't desirable either.
https://bugs.winehq.org/show_bug.cgi?id=48584
--- Comment #8 from Scott shagooserver@gmail.com --- cmd just opens a terminal which I manually close when I am finished with DTS-MA
https://bugs.winehq.org/show_bug.cgi?id=48584
--- Comment #9 from Scott shagooserver@gmail.com --- I have experimented with: exec=sh -c 'cd /home/scott/.winedts/drive_c/"Program Files"... and find they both do the same thing
https://bugs.winehq.org/show_bug.cgi?id=48584
--- Comment #10 from Scott shagooserver@gmail.com --- Fixed, can be closed.
https://bugs.winehq.org/show_bug.cgi?id=48584
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED
--- Comment #11 from Zebediah Figura z.figura12@gmail.com --- (In reply to Scott from comment #10)
Fixed, can be closed.
Not sure whether there was a valid bug here, but resolving as FIXED nonetheless.
https://bugs.winehq.org/show_bug.cgi?id=48584
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #12 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 6.15.
-
WineHQ Bugzilla