Closed Creatinator512 closed 2 years ago
Do you have any other MIDI driver installed by any chance?
OmniMIDI is the only one showing up for MIDI output.
If the DLL hell message appears, that means that there's another program or driver loading its own BASS libraries into the process.
Could you please send the debug log here?
Found the DLL hell error I was talking about after enabling troubleshooting mode. Here's the debug log that was created during that process. PFA-1.1.0-x86_64.exe (Debug output).txt
Can you check which MIDI devices are installed through the OmniMapper control panel? If GetModuleHandle returns an handle to an already existing BASS lib in memory, then there MUST be something loading the libraries before OM is able to do so.
OmniMIDI and Microsoft GS Wavetable Synth are the only ones showing up in the OmniMapper control panel.
I think I had a glitched version of OmniMapper, because when I uninstalled the MIDI Mapper to access the control panel, everything started working as expected, even when I reinstalled it. I believe going through a couple updates without uninstalling and reinstalling it resulted in some problems between the driver and the mapper.
Just got this error now. This is the BASS error I mentioned. The same warning and error sequence happened as well when I switched MIDIs, but now the Guru Meditation errors are changing. After that, PFA started behaving as it did before this issue and OmniMapper is now mixed up again in installing or uninstalling it. Reinstalling OmniMIDI has worked in getting rid of the issue temporarily.
Is this folder called "opt" in the System32 and SysWOW64 OmniMIDI folders with duplicate bass and bassmidi DLL files intentional? Also, I have attempted uninstalling anything that I could determine could be a culprit, but that has not worked.
Deleting that folder has mostly fixed it. I started getting that same issue today and got this error after clicking "No" on the multiple bass libraries loaded warning.
It should be fixed in 14.6.10.
It's been a good amount of days without any errors, so it must be fixed. Thank you for your help in handling this problem!
Problem Summary: PFA freezes occasionally and will remain even after closing. This bug seems to have some correlation to OmniMIDI due to a BASS error. Description: After starting PFA and loading a MIDI, I immediately got an error message about BASS being started already with no description. However, PFA and OmniMIDI played the MIDI fine after that error. I loaded a different MIDI and got a warning message about a "DLL hell" where conflicts between two different libraries could result in weird crashes. But the MIDI was played fine again. I believe these two errors could correlate to an issue I've been having for a while where PFA's MIDI visualization freezes after trying to load a MIDI. Even after closing out of it, it can still remain, as shown in the screenshot.
Steps to reproduce
Expected behavior PFA should run without any errors or without freezing and it should close with the task ended.
Screenshots/Videos
Environment
Additional context These problems happen by chance for me, so this issue isn't easily reproduceable, but this can happen fairly often. The BASS error started upon starting up my computer, then loading PFA and a MIDI.