Can't launch

[Brain Hurter]

Whenever I try to open the program a solid minute of nothing happens, then a window pops up for a split second before closing entirely. What's going on?

[Jae Nornec]

There is likely another version of BMIDI installed on your computer.
From another post of mine on the discussion board:

"I suggest running the BMIDI installer from the 3rdPartyInstallers folder in your install directory for Midinous. This usually happens because something else you use for music (such as NI software) uses the BMIDI back-end and it happens to be a different version.
You can reach the folder by right clicking on Midinous in your library and going to Manage >> Browse Local Files"

[Brain Hurter]

Worked for me, thanks man!

[technochitlin]

Windows 10 machine-
I'm having a similar problem- the program starts; I can hear the audio cue that a MIDI device has initiated; then a second later Midinous exits. (I can see this by watching the prompts on the Steam launch page).
I tried reinstalling the Bome MIDI driver and that appeared to succeed, but Midinous itself refuses to run. The previous version worked fine.

[Jae Nornec]

You can find your log files in %AppData%/Local/Midinous. Please send these to [e-mail]

[ishman99]

Originally posted by technochitlin:

Windows 10 machine-
I'm having a similar problem- the program starts; I can hear the audio cue that a MIDI device has initiated; then a second later Midinous exits. (I can see this by watching the prompts on the Steam launch page).
I tried reinstalling the Bome MIDI driver and that appeared to succeed, but Midinous itself refuses to run. The previous version worked fine.

Same here

[Jae Nornec]

Once I get people's log files, i can see what's going on and push a fix out or make a suggestion.

[technochitlin]

Sent the logs just now

[Jae Nornec]

So I've had a chance to look at the logs, and unfortunately it seems if there was any exception, it didn't get recorded to the logs and I can't seem to reproduce it on my test boxes. However they may have been written to the Windows Event Viewer. This is going to be somewhat complex if you've never done it but, this is what I'll need to investigate further:

1. Hit your Windows key, or go to app search and type "event viewer"
   
2. Once you are in the event viewer, check on the left tree for Windows Logs > Application.
   
3. Once you click that, a series of events will appear on the right. Right click on the Application section on the left again and click "Find".
   
4. In the dialog that pops up, type in "midinous" and hit find. You're looking for an event of level "error". It should have a red circle with an exclamation next to it with the word "Error" by it. This should also be from the "Application Error" source, not something like "bonjour service". This process might take awhile.
   
5. Once you've found one (or several) of these errors, you'll want to right click the event and select "Copy >> Copy Details as Text" or take a screenshot of the details you see from the general tab.
   
6. Chuck these in a text file or email and send them to me (if you find them).

Here are some example details i pulled from a time when Forza crashed on me:

Faulting application name: ForzaHorizon5.exe, version: 1.573.834.0, time stamp: 0x00000000
Faulting module name: ForzaHorizon5.exe, version: 1.573.834.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000930c0c
Faulting process id: 0x4760
Faulting application start time: 0x01d96282c84b4667
Faulting application path: Z:\SteamLibrary\steamapps\common\ForzaHorizon5\ForzaHorizon5.exe
Faulting module path: Z:\SteamLibrary\steamapps\common\ForzaHorizon5\ForzaHorizon5.exe
Report Id: e13132c9-a6bb-4f4f-883e-f36c88a23d8a
Faulting package full name: 
Faulting package-relative application ID: 

I'm hoping to see a little more than this though, like actual exception details from .NET (the framework the program is written in). Let me know if you need help or if this is too much. Again, I have attempted to reproduce the issue but can't find a cause. Have you tried installing Midinous on another computer if available? I'm thinking this has something to do with the upgrade. I wonder if a clean install of Midinous (including deleting the folder in steamapps/common) might fix things?

[technochitlin]

Done just now. Note- I have completely deleted Midinous from my system, including deleting its folder, and reinstalled, and it still won't launch.

[Jae Nornec]

Thanks. This is really good information, sorry if it was a pain to collect. But this boils down to a memory access issue. I'm uncertain if it is directly related to Midinous, but I found this really interesting thread for Reaper users
[link]https://forum.cockos.com/showthread.php?p=2424517[/link]

Is Midinous the only thing running (music wise) when you try to open it? Do you have things like firewalls, anti-virus, multiple plugins/vsts open and/or running when trying to open it? Someone had mentioned running the system file checker (SFC) to see if your system files are ok, specifically for msvcrt.dll, the faulting file found in the System32 directory.

I should note that this issue isn't happening with everyone. I try my hardest to accommodate all platforms and configurations but such as it is with software and unmanaged code, you're basically rolling the dice. But we're not out of options quite yet. Let me know how it goes.

[ishman99]

EventData

AppName Midinous.exe
AppVersion 1.1.0.0
AppTimeStamp 63ed8286
ModuleName ucrtbase.dll
ModuleVersion 10.0.22621.608
ModuleTimeStamp f5fc15a3
ExceptionCode c0000409
FaultingOffset 000000000007f61e
ProcessId 0x9c8
ProcessCreationTime 0x1d988dd144c8d89
AppPath D:\Steam\steamapps\common\Midinous\Midinous.exe
ModulePath C:\WINDOWS\System32\ucrtbase.dll
IntegratorReportId c219e4ba-d369-4c4b-b6b5-2c1c5f9cc24c
PackageFullName
PackageRelativeAppId
---------------------------------------------------------------------

Hope this can help you ;)

[Jae Nornec]

It does help, as it tells me ucrtbase.dll is the issue here, which some Vital users reported running into: https://forum.vital.audio/t/vital-1-5-3-crash/10866/5

But only for some users. Things to check: Windows updates, C++ redistributables up to date, graphics drivers up to date, and I would attempt to do some of the things i suggested in my last post and report back. If there is more than one crash log as well, it would be nice to know if all of them are the same.

[technochitlin]

Is Midinous the only thing running (music wise) when you try to open it?
No other music software is running when I try to start it
Do you have things like firewalls, anti-virus, multiple plugins/vsts open and/or running when trying to open it?
Nothing that wasn't running when I was able to successfully start the previous version

Ran sfc /scannow; no errors reported. Ran dism; my system files are reported ok.

Note that my system runs Live, Reason, and Reaper all successfully so I'm not sure what the Cockos link was for. I'm not sure of what else I can do.

[Jae Nornec]

Between the last version and now i run unmanaged code to run the audio callback. I am unfortunately not in control of this code and it is likely what is causing the issues for some users. But as it was clear in this thread alone two people with the same crash had different reasons for the crash. I only linked the Reaper and Vital threads to give you an example of the same error in a different app. I can enable a legacy mode for users for now until i have some ideas. You can at least try to run the old version. You bought the software, you ought to be able to run it. I'd be curious to see if you ran into the same issue on another machine. It's likely you wouldn't, and not everyone is getting this crash. I can't control the configurations of thousands of users, and i wish i could plan for all situations.

I have enabled a "legacy" branch accessible through right clicking Midinous in your library, going to Properties >> Betas and selecting "legacy" on the right. This should put you back at version 1.0.3, the last stable version before this update. Unfortunately it won't have all of the new stuff, but you'll at least be able to run it (hopefully). Let me know if this works for you.

[ishman99]

Just to confirm that the legacy version works fine on my computer. Thank you for offering this possibility while the issues with the new version are fixed