Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: foo_midi (foobar2000 v2.0) (Read 83627 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: foo_midi (foobar2000 v2.0)

Reply #300 –
I don't understand why you refuse to show the error message you get.

I looked at the sources, the actual midi file indeed is loaded by foobar2000 so your chinese characters are absolutely not a problem. But what happens next can be, there are ansi character set temp files used depending on your midi component settings and plenty of other places where paths are passed, all depending on configuration. If you shared the error you got it should be easy for pgyt to know what needs improving.

Re: foo_midi (foobar2000 v2.0)

Reply #301 –
Quote from: Case on
But what happens next can be, there are ansi character set temp files used depending on your midi component settings and plenty of other places where paths are passed, all depending on configuration.
The temporary filename is only used when an embedded sound font is found and it is generated by the OS.
Quote from: Case on
If you shared the error you got it should be easy for pgyt to know what needs improving.
Indeed.

Re: foo_midi (foobar2000 v2.0)

Reply #302 –
v2.17.0.0, 2025-03-16

* New: Metadata MIDI_EMBEDDED_SOUNDFONT: Contains "SF x.x" (where x.x is the version number of the SoundFont specification) or "DLS" if the MIDI file contains an embedded soundfont.
* Improved: Support for XMF/MXMF files with raw deflated content.
* Improved: Tweaked the handling of embedded sound fonts for BASSMIDI and FluidSynth again.
  * The Official SF2 RMIDI Specification example files seem to work now.
* Improved: The RIFF IPRD chunk will also be used to add an Album tag in case an IALB chunk is not found.
* Improved: FluidSynth player understands Polyphonic Key Pressure (Aftertouch) now.
* Changed: Increased the gain of the FluidSynth player.
* Changed: Disabled dynamic sample loading in the FluidSynth player. It causes distortion when playing some very short samples.
* Fixed: A pending SysEx message would get skipped when the next event used the running status.
* Fixed: More Multi Port MIDI files play correctly in BASSMIDI now.
  * The first MIDI Port message of a track is now added at the start of a track to make sure it occurs before any Program Change events

Download from GitHub or the foobar2000 Components repository.

Automatic update from within foobar2000 does not work.

Re: foo_midi (foobar2000 v2.0)

Reply #303 –
Quote from: Case on
I don't understand why you refuse to show the error message you get.

I looked at the sources, the actual midi file indeed is loaded by foobar2000 so your chinese characters are absolutely not a problem. But what happens next can be, there are ansi character set temp files used depending on your midi component settings and plenty of other places where paths are passed, all depending on configuration. If you shared the error you got it should be easy for pgyt to know what needs improving.

These are the only error messages. No more information is displayed in the console. It seems that the output is cut off, not that I don't show it.

Re: foo_midi (foobar2000 v2.0)

Reply #304 –
Quote from: Case on
I don't understand why you refuse to show the error message you get.

The attached video is a merge of two clips, the first one uses the new version of foo_midi, the second one uses the old version, I don't know how to get more error information?

Re: foo_midi (foobar2000 v2.0)

Reply #305 –
Quote from: ha7pro on
Quote from: Case on
I don't understand why you refuse to show the error message you get.

The attached video is a merge of two clips, the first one uses the new version of foo_midi, the second one uses the old version, I don't know how to get more error information?
Thx. I see what you experience now. That does not mean I understand what's happening yet.

Re: foo_midi (foobar2000 v2.0)

Reply #306 –
Quote from: pqyt on
Quote from: ha7pro on
Quote from: Case on
I don't understand why you refuse to show the error message you get.

The attached video is a merge of two clips, the first one uses the new version of foo_midi, the second one uses the old version, I don't know how to get more error information?
Thx. I see what you experience now. That does not mean I understand what's happening yet.
I really have no clue what's going on. The file plays correctly on my x86 setup. Even if there was an error during processing an exception would have been thrown with the error message.

A lot has changed in the SoundFont handling. Which SoundFont are you using? Which player do you have selected?

Re: foo_midi (foobar2000 v2.0)

Reply #307 –
Unfortunately, the forum has been rolled back, and the screen recording attachment I had posted is also lost.
It was a video recorded in a win7 virtual machine to capture what happens when different versions of foo_midi handle adding files and directories to the playlist.
In short: In some cases, newer foo_midi may cause some midi files with CJK characters to fail to be added to the playlist, or even if they are successfully added, the files cannot be correctly recognized. Just change the names of these unrecognizable files to English or numbers, and everything will be normal again. The interesting thing is that whether or not it can be successfully added to the playlist seems to be very random, and I haven't found a definite pattern. If want to find the source of the problem, can consider looking for code changes from the first beta version after the 2.16 stable version, especially the code related to file or metadata reading.

Re: foo_midi (foobar2000 v2.0)

Reply #308 –
Quote from: ha7pro on
Unfortunately, the forum has been rolled back, and the screen recording attachment I had posted is also lost.
It was a video recorded in a win7 virtual machine to capture what happens when different versions of foo_midi handle adding files and directories to the playlist.
In short: In some cases, newer foo_midi may cause some midi files with CJK characters to fail to be added to the playlist, or even if they are successfully added, the files cannot be correctly recognized. Just change the names of these unrecognizable files to English or numbers, and everything will be normal again. The interesting thing is that whether or not it can be successfully added to the playlist seems to be very random, and I haven't found a definite pattern. If want to find the source of the problem, can consider looking for code changes from the first beta version after the 2.16 stable version, especially the code related to file or metadata reading.
I already did a comparison and with MIDI file handling between 2.16 and 2.16.1-alpha1 not a lot has changed. But in the sound font handling a lot did change. I run a US Latin-1 setup but adding the file with Chinese characters poses no problems.

My last question was: are you willing to run a private debug version that contains a lot of trace messages to the foobar2000 console  to be able to pinpoint where exactly things go wrong?

Re: foo_midi (foobar2000 v2.0)

Reply #309 –
Quote from: pqyt on
My last question was: are you willing to run a private debug version that contains a lot of trace messages to the foobar2000 console  to be able to pinpoint where exactly things go wrong?
ok
I am willing to test it.
Please provide the download link and I will try it as soon as possible.
However, there is a time difference in our area, and the time we use on the forum is not synchronized.
Moreover, there is GFW here, and the network is not very stable.
The feedback information may not be very timely.
Please forgive me in advance.

Re: foo_midi (foobar2000 v2.0)

Reply #310 –
Created a new win10 virtual machine,
clean system,
portable installation of foobar2000,
test foo_midi,
please see the attached video

Re: foo_midi (foobar2000 v2.0)

Reply #311 –
Quote from: ha7pro on
Quote from: pqyt on
My last question was: are you willing to run a private debug version that contains a lot of trace messages to the foobar2000 console  to be able to pinpoint where exactly things go wrong?
ok
I am willing to test it.
Please provide the download link and I will try it as soon as possible.
However, there is a time difference in our area, and the time we use on the forum is not synchronized.
Moreover, there is GFW here, and the network is not very stable.
The feedback information may not be very timely.
Please forgive me in advance.
Thank you in advance. I sent you a PM with the details.

Re: foo_midi (foobar2000 v2.0)

Reply #312 –
Quote
a PM with the details.
^_^
Test feedback has been replied to privately

Re: foo_midi (foobar2000 v2.0)

Reply #313 –
Quote from: ha7pro on
Quote
a PM with the details.
^_^
Test feedback has been replied to privately
Fast and unexpected. I've added some more detailed messages.

Re: foo_midi (foobar2000 v2.0)

Reply #314 –
Quote from: pqyt on
Quote from: ha7pro on
Quote
a PM with the details.
^_^
Test feedback has been replied to privately
Fast and unexpected. I've added some more detailed messages.

The second test has been reported in the private message.
From the log, the error occurred when reading metadata.
Maybe it is a good idea not to read some fields in metadata that may contain CJK characters?
I have to prepare dinner and may not be back for a few hours.

Re: foo_midi (foobar2000 v2.0)

Reply #315 –
v2.17.2.0, 2025-03-19

* Fixed: Crash while attempting to open a MIDI file containing non-ASCII characters. An old bug suddenly surfaced while attempting to open a WRD file containing external lyrics.
  * Thank you to ha7pro for reporting the bug and helping me fix it.

Download from GitHub or the foobar2000 Components repository.

Automatic update from within foobar2000 does not work.

Re: foo_midi (foobar2000 v2.0)

Reply #316 –
Quote from: pqyt on
v2.17.2.0, 2025-03-19

* Fixed: Crash while attempting to open a MIDI file containing non-ASCII characters. An old bug suddenly surfaced while attempting to open a WRD file containing external lyrics.
  * Thank you to ha7pro for reporting the bug and helping me fix it.

Download from GitHub or the foobar2000 Components repository.

Automatic update from within foobar2000 does not work.
THX!
it works ^_^

Re: foo_midi (foobar2000 v2.0)

Reply #317 –
What's up with automatic updates not working with this component?
Random digital audio nerd girl
A potato
 

Re: foo_midi (foobar2000 v2.0)

Reply #318 –
Quote from: Meowdori on
What's up with automatic updates not working with this component?

the original MIDI  component by Kode54 is named
foo_midi
https://www.foobar2000.org/components/view/foo_midi

on the official Foobar2000 component webpage..
but Pqyt's build based on it is named..
foo_midi+(x64) on the website but named foo_midi on the folder name as to be installed over ins the same place..
https://www.foobar2000.org/components/view/foo_midi+%28x64%29

since its not of the foo_midi main page that is under Kode54's name it won't auto update..
I hope that explanation helps.. lol ;-)

Re: foo_midi (foobar2000 v2.0)

Reply #319 –
Quote from: Melchior on
Quote from: Meowdori on
What's up with automatic updates not working with this component?

the original MIDI  component by Kode54 is named
foo_midi
https://www.foobar2000.org/components/view/foo_midi

on the official Foobar2000 component webpage..
but Pqyt's build based on it is named..
foo_midi+(x64) on the website but named foo_midi on the folder name as to be installed over ins the same place..
https://www.foobar2000.org/components/view/foo_midi+%28x64%29

since its not of the foo_midi main page that is under Kode54's name it won't auto update..
I hope that explanation helps.. lol ;-)
An unfortunate choice at the time but it was my first component.

Re: foo_midi (foobar2000 v2.0)

Reply #320 –
v2.18.0.0, 2025-04-05

* Changed: Enabled dynamic sample loading in the FluidSynth player again when using FluidSynth 2.4.4 or later.
* Added: BASSMIDI will ignore NRPN Vibrato Depth events in SC-88Pro mode. It overreacts to this parameter.
* Added: Support for MMF/SMAF MA-2 files.

Download from GitHub or the foobar2000 Components repository.

Automatic update from within foobar2000 does not work.

Re: foo_midi (foobar2000 v2.0)

Reply #321 –
Noticed some non-ideal interaction with foo_wave_minibar_mod. Some more details in that discussion.

Re: foo_midi (foobar2000 v2.0)

Reply #322 –
Quote from: iridescentaudio on
Something I asked about back when kode54 maintained the component, but I thought it might be worth asking again.

Is support for the Ensoniq AudioPCI wavetables feasible? They consist of three .ECW format soundbank files, similar to soundfonts. 2MB, 4MB & 8MB respectively. Support for these wavetables continued as late as the release of the SoundBlaster Audigy, which offered an alternative Windows MIDI device called "Creative S/W synth" in order to access them instead of the usual soundfonts.

There's a format specification here if it helps. I have the 2MB and 8MB banks uploaded here and here. (I suspect the 4MB bank is around somewhere too, but I can't find it right at this moment.)

Hello, I've been thinking about the Ensoniq Concert Wavetable banks a lot again lately, as I've been diving into the oldest depths of my midi collection.
To the best of my knowledge, there is currently no software that can use these ECW banks for MIDI playback on any system this side of Windows XP. For a while the "S/W Synth" was the fallback MIDI device for DOS gamers, since other midi devices only worked under Windows. It was a budget device with a crisp, tinny sound which is quite iconic of late 90s/early 00s midi - here is an example of the Duke 3D theme playing with it. I really hope that these banks could be supported in foo_midi somehow.

Re: foo_midi (foobar2000 v2.0)

Reply #323 –
Quote from: iridescentaudio on
Quote from: iridescentaudio on
Something I asked about back when kode54 maintained the component, but I thought it might be worth asking again.

Is support for the Ensoniq AudioPCI wavetables feasible? They consist of three .ECW format soundbank files, similar to soundfonts. 2MB, 4MB & 8MB respectively. Support for these wavetables continued as late as the release of the SoundBlaster Audigy, which offered an alternative Windows MIDI device called "Creative S/W synth" in order to access them instead of the usual soundfonts.

There's a format specification here if it helps. I have the 2MB and 8MB banks uploaded here and here. (I suspect the 4MB bank is around somewhere too, but I can't find it right at this moment.)

Hello, I've been thinking about the Ensoniq Concert Wavetable banks a lot again lately, as I've been diving into the oldest depths of my midi collection.
To the best of my knowledge, there is currently no software that can use these ECW banks for MIDI playback on any system this side of Windows XP. For a while the "S/W Synth" was the fallback MIDI device for DOS gamers, since other midi devices only worked under Windows. It was a budget device with a crisp, tinny sound which is quite iconic of late 90s/early 00s midi - here is an example of the Duke 3D theme playing with it. I really hope that these banks could be supported in foo_midi somehow.
Ha! Forgot about that. I promise *again* that I'll look at it.

Re: foo_midi (foobar2000 v2.0)

Reply #324 –
Heads up: FluidSynth 2.4.5 has been released but the main DLL has been renamed from 'libfluidsynth-3.dll' to 'fluidsynth-3.dll'.

foo_midi will not be able to use FluidSynth because it looks for 'libfluidsynth-3.dll'.

Quick fix: Rename 'fluidsynth-3.dll' to 'libfluidsynth-3.dll' again until the FluidSynth package gets changed or until I can release an update that compensates for this name change.