[0.3.4-11-g5d8f00814] [Duke3D] Fluidsynth Issues

Forum rules
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.

Post a reply

Smilies
:D :) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :geek: :ugeek: :!: :?: :idea: :arrow: :| :mrgreen: :3: :wub: >:( :blergh:
View more smilies
BBCode is OFF
Smilies are ON
Topic review
   

Expand view Topic review: [0.3.4-11-g5d8f00814] [Duke3D] Fluidsynth Issues

Re: [0.3.4-11-g5d8f00814] [Duke3D] Fluidsynth Issues

by Graf Zahl » Wed Feb 05, 2020 3:22 am

16.4.4 is up tp date. Weird.

Re: [0.3.4-11-g5d8f00814] [Duke3D] Fluidsynth Issues

by Nash » Wed Feb 05, 2020 3:14 am

Code: Select all

Microsoft Visual Studio Community 2019
Version 16.4.4
VisualStudio.16.Release/16.4.4+29728.190
Microsoft .NET Framework
Version 4.8.03752

Installed Version: Community

Visual C++ 2019   00435-60000-00000-AA549
Microsoft Visual C++ 2019

ASP.NET and Web Tools 2019   16.4.460.23317
ASP.NET and Web Tools 2019

Azure App Service Tools v3.0.0   16.4.460.23317
Azure App Service Tools v3.0.0

C# Tools   3.4.1-beta4-19614-01+165046097562cfe65b09c2e9a9d8f7cd88526f2c
C# components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.

Common Azure Tools   1.10
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.

IntelliCode Extension   1.0
IntelliCode Visual Studio Extension Detailed Info

Microsoft JVM Debugger   1.0
Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines

Microsoft MI-Based Debugger   1.0
Provides support for connecting Visual Studio to MI compatible debuggers

Microsoft Visual C++ Wizards   1.0
Microsoft Visual C++ Wizards

Microsoft Visual Studio VC Package   1.0
Microsoft Visual Studio VC Package

NuGet Package Manager   5.4.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit https://docs.nuget.org/

ProjectServicesPackage Extension   1.0
ProjectServicesPackage Visual Studio Extension Detailed Info

Visual Basic Tools   3.4.1-beta4-19614-01+165046097562cfe65b09c2e9a9d8f7cd88526f2c
Visual Basic components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.

Visual F# Tools 10.4 for F# 4.6   16.4.0-beta.19556.5+e7597deb7042710a7142bdccabd6f92b0840d354
Microsoft Visual F# Tools 10.4 for F# 4.6

Visual Studio Code Debug Adapter Host Package   1.0
Interop layer for hosting Visual Studio Code debug adapters in Visual Studio

Visual Studio Tools for CMake   1.0
Visual Studio Tools for CMake

Visual Studio Tools for CMake   1.0
Visual Studio Tools for CMake

Visual Studio Tools for Unity   4.4.2.0
Visual Studio Tools for Unity
I hope this is useful.

Re: [0.3.4-11-g5d8f00814] [Duke3D] Fluidsynth Issues

by Graf Zahl » Wed Feb 05, 2020 3:10 am

In the about window it should give some info. I know that last autumn there was one compiler version that had code generation issues, let's hope it was just that.

Re: [0.3.4-11-g5d8f00814] [Duke3D] Fluidsynth Issues

by Nash » Wed Feb 05, 2020 3:04 am

How/where do I check that? Sorry, I'm not really knowledgeable in this stuff.

Re: [0.3.4-11-g5d8f00814] [Duke3D] Fluidsynth Issues

by Graf Zahl » Wed Feb 05, 2020 2:55 am

What compiler version do you have?

Re: [0.3.4-11-g5d8f00814] [Duke3D] Fluidsynth Issues

by Nash » Wed Feb 05, 2020 2:49 am

I'm wondering the same thing. All I did was a straight CMake -> build with VS 2019. Release build.

Re: [0.3.4-11-g5d8f00814] [Duke3D] Fluidsynth Issues

by Graf Zahl » Wed Feb 05, 2020 1:23 am

Strange. I wonder what went wrong with Nash's build.

Re: [0.3.4-11-g5d8f00814] [Duke3D] Fluidsynth Issues

by Kinsie » Tue Feb 04, 2020 8:00 pm

This appears to be fixed as of 0.4.0.

Re: [0.3.4-11-g5d8f00814] [Duke3D] Fluidsynth Issues

by Graf Zahl » Tue Feb 04, 2020 7:23 am

No. ZDoom's synth can handle EMIDI just fine. I'll have to compare both sets of files. Like I said, my guess is that somehow the unsigned chars from Build filter down to code that cannot handle them because it's the only difference between those two.

Re: [0.3.4-11-g5d8f00814] [Duke3D] Fluidsynth Issues

by mjr4077au » Tue Feb 04, 2020 7:20 am

Something to do with Duke's MIDI format, perhaps? http://www.vgmpf.com/Wiki/index.php?title=EMIDI

Re: [0.3.4-11-g5d8f00814] [Duke3D] Fluidsynth Issues

by Graf Zahl » Tue Feb 04, 2020 6:48 am

Now that is odd. I wonder if it may be caused by the need to compile Build sources with chars as unsigned - because that's really the only major difference. The entire music system is nearly a 1:1 copy of GZDoom, just with the MIDI synths with incompatible licenses being removed.

Re: [0.3.4-11-g5d8f00814] [Duke3D] Fluidsynth Issues

by Kinsie » Tue Feb 04, 2020 6:43 am

I extracted STALKER.MID from DUKE3D.GRP, renamed it to D_RUNNIN.MID and quickly created a folder mod to run it in GZDoom g4.3.3. It played perfectly in Fluidsynth with my nice soundfont and not a note out of place.

Re: [0.3.4-11-g5d8f00814] [Duke3D] Fluidsynth Issues

by Graf Zahl » Tue Feb 04, 2020 6:32 am

Can you cross-check these MIDIs in GZDoom? The player should be the same. I've been using DN3D MIDIs for Doom level since all eternity and cannot remember ever having issues with them.

[0.3.4-11-g5d8f00814] [Duke3D] Fluidsynth Issues

by Kinsie » Tue Feb 04, 2020 6:26 am

1.) Fluidsynth seems insistent on using the default soundfont instead of my nice custom SC-55 one.
2.) Fluidsynth MIDI playback seems kinda buggy in general. Here's a clip from STALKER.MID (the E1L1 theme) to demonstrate, although it's easy enough to reproduce by just waiting around on the main menu for about ten seconds until GRABBAG.MID hits the little synth solo riff.

Top