Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

issue with loading Fluidsynth on Woof using DOOM Mod Loader v2.5 #28

Closed
Premo36 opened this issue May 14, 2022 · 1 comment
Closed

issue with loading Fluidsynth on Woof using DOOM Mod Loader v2.5 #28

Premo36 opened this issue May 14, 2022 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@Premo36
Copy link
Owner

Premo36 commented May 14, 2022

  • OS: Windows
  • DML Version: v2.5 (Stable)
  • Sourceport: Woof!

From user report:

I came across an error where I cannot use the Fluidsynth sound backend for playing midi when using the loader. And yes I can boot it just fine outside the program when using Woof as a standalone

error woof

WORKAROUND:

  1. Open woof! Doesn't matter if through DML or directly.
  2. Change from "native" to "Fluidsinth". I will tell you to close it on order to apply changes. Close it.
  3. Go into the woof folder (the one with woof.exe and a bunch of .dll and other stuff) and locate the "soundfonts" folder.
  4. Copy the "soundfonts" folder in the DML 2.5 folder. Now you should have 2 soundfonts folder, the original in the woof folder and one next to the DML 2.5 exe.
  5. Open woof through DML v2.5. It will now start without any error and using fluidsinth!

Woof folder:
workaround woof 1

DML 2.5 folder:
workaround woof 2

You may have to repeat this process with any new woof! release, depending if anything inside that folder changes between releases.

@Premo36 Premo36 added bug Something isn't working question Further information is requested labels May 14, 2022
@Premo36 Premo36 self-assigned this May 14, 2022
@Premo36 Premo36 removed the question Further information is requested label May 16, 2022
@Premo36
Copy link
Owner Author

Premo36 commented May 17, 2022

Updated issue with workaround. Please note that woof! It's not an officially support sourceport for v2.5

@Premo36 Premo36 closed this as completed May 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant