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 33083 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Re: foo_midi (foobar2000 v2.0)

Reply #127 –
Yeah, well, I trust the 2 most important ones, MS Defender and Kaspersky.
 

Re: foo_midi (foobar2000 v2.0)

Reply #128 –
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.)

Re: foo_midi (foobar2000 v2.0)

Reply #129 –
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.)
I'll look into it after foo_vis_spectrum_analyzer is a little bit more mature.

Re: foo_midi (foobar2000 v2.0)

Reply #130 –
Current version: 2.9.1.3, released on 2023-11-02
Just checked in Virustotal, there are 13 (!) alerts at the time writing. The "older version" from kode54 is clean... Will not install this.

Re: foo_midi (foobar2000 v2.0)

Reply #131 –
Quote from: doomerguy82 on
Current version: 2.9.1.3, released on 2023-11-02
Just checked in Virustotal, there are 13 (!) alerts at the time writing. The "older version" from kode54 is clean... Will not install this.
Good for you! Has it ever occurred to you that virus detectors can have bugs too? Besides, the source code is available.

Re: foo_midi (foobar2000 v2.0)

Reply #132 –
Quote
Has it ever occurred to you that virus detectors can have bugs too?

Yes, I know that. Hope it will be fixed in the future (seems as the VSThost exes cause the alerts). I like the new things the plugin could do. But when the alert pops up while downloading a simple plugin you have to know exactly what to do. I'm a coder guy too and could read and compile the git for myself. But my intension was to simply listen to some new SF2's I got new, so all good for me, even with the old plugin version. Keep up the good work!

Re: foo_midi (foobar2000 v2.0)

Reply #133 –
Well, it is now unavoidable - MS Defender is now reporting this as malware.
X

Someone other than pqyt should compile from source and scan, to confirm if it's an issue with this specific build itself or with the build process on pqyt's end - from what I can see, Phonzy is one of those "this virus will spread to other programs on your machine" viruses, so the build process itself might have gotten infected.

EDIT: I ran the source through clamscan and that all came up clean, so if there's something wrong it's likely in the build process itself.  Unfortunately I don't have a clean build environment at the moment (I'm paranoid and will be scanning everything once I'm done with work today).  The "good news" is that it doesn't look like the vst hosts aren't required for libADL or libOPN so I can still listen to all my midis

Re: foo_midi (foobar2000 v2.0)

Reply #134 –
its most likely a false-positive...
 so I white listed it to prevent ti from messing up my FB2k install.. lol

Re: foo_midi (foobar2000 v2.0)

Reply #135 –
Quote from: Melchior on
its most likely a false-positive...
 so I white listed it to prevent ti from messing up my FB2k install.. lol

I've reported it as a false positive and haven't heard back from my anti-virus vendor for a while now.  Normally I hear back from them within a day or two.

Re: foo_midi (foobar2000 v2.0)

Reply #136 –
Quote from: raekuul on
Well, it is now unavoidable - MS Defender is now reporting this as malware.
[attach type=image]28211[/attach]

Someone other than pqyt should compile from source and scan, to confirm if it's an issue with this specific build itself or with the build process on pqyt's end - from what I can see, Phonzy is one of those "this virus will spread to other programs on your machine" viruses, so the build process itself might have gotten infected.

EDIT: I ran the source through clamscan and that all came up clean, so if there's something wrong it's likely in the build process itself.  Unfortunately I don't have a clean build environment at the moment (I'm paranoid and will be scanning everything once I'm done with work today).  The "good news" is that it doesn't look like the vst hosts aren't required for libADL or libOPN so I can still listen to all my midis
vshost works by setting up a pipe between itself and foobar2000 to send the MIDI messages and responses back and forth. That's a perfectly legit use case.

FYI. I work in IT security so I'm well aware of the risks. That does not exclude a possible infection of my build machine but I've had Defender complain about spawning a PDF reader after a print to PDF action from Excel. Human intelligence still beats artificial intelligence.

Re: foo_midi (foobar2000 v2.0)

Reply #137 –
considering we've all been getting a false positive for the same component (vsthost64), there's clearly something as has gone wrong.

Re: foo_midi (foobar2000 v2.0)

Reply #138 –
Can you we get back on topic: playing MIDI files?

If you don't trust it, recompile it. If you don't know how, don't use it. There's a Delete key on every keyboard.

Re: foo_midi (foobar2000 v2.0)

Reply #139 –
Bug report. I noticed that foobar sometimes crashes when playing files with the Emu de MIDI plugin selected. Unsure of exact steps to reproduce, but it seems to happen when first opening files with it. Sometimes it might happen once, but not happen again for a while after foobar is restarted. Here's a crash dump.

Re: foo_midi (foobar2000 v2.0)

Reply #140 –
Quote from: Slender on
Bug report. I noticed that foobar sometimes crashes when playing files with the Emu de MIDI plugin selected. Unsure of exact steps to reproduce, but it seems to happen when first opening files with it. Sometimes it might happen once, but not happen again for a while after foobar is restarted. Here's a crash dump.
Can you provide an example MIDI file that causes a crash?

Re: foo_midi (foobar2000 v2.0)

Reply #141 –
The crash doesn't seem to be specific to any particular file. Onestop.mid can also cause it.
Here are some more reliable steps to reproduce I've discovered.
1. Restart your computer.
2. Load the Emu de MIDI plugin and play a file, such as onestop.mid. The crash will occur on the first play, but won't re-occur until you restart your computer again.

Re: foo_midi (foobar2000 v2.0)

Reply #142 –
Fixed in the next release: division by 0 because the dynamic synthesis rate was not initialized on time.

onestop.mid sounds nicer in BASSMIDI, IMHO.

Thx. for the report.

Re: foo_midi (foobar2000 v2.0)

Reply #143 –
Curious if you are going to add Yamaha XG emulation once MAME finishes their chip research, like MT32, to make things like VSTi's redundant. Only this time, they are working on the XG line of synths to be emulated properly.

Re: foo_midi (foobar2000 v2.0)

Reply #144 –
Quote from: mudlord on
Curious if you are going to add Yamaha XG emulation once MAME finishes their chip research, like MT32, to make things like VSTi's redundant. Only this time, they are working on the XG line of synths to be emulated properly.
I will certainly look at it. But just emulating the XG won't be sufficient. You'd need the sample banks too, wouldn't you?

Re: foo_midi (foobar2000 v2.0)

Reply #145 –
That's 100% correct yes. You will need the control param ROM and sample ROM, just like with Roland GS synth emulation and the "Secret Sauce".

Re: foo_midi (foobar2000 v2.0)

Reply #146 –
v2.9.2.0, 2023-12-24, Merry Christmas

* New: Compatible with foo_vis_midi v0.1.0.
* Bug Fix: Crash in Emu de MIDI because dynamic synthesis rate was not initialized in time.
* Bug Fix: Loop type was not respected when converting to other audio formats.
* Builds with foobar2000 SDK 2023-09-23.

Download from GitHub or the foobar2000 Components Repository.

Automatic update from within foobar2000 still does not work...

Re: foo_midi (foobar2000 v2.0)

Reply #147 –
thumbs up!

Re: foo_midi (foobar2000 v2.0)

Reply #148 –
Working fine on my end.

Also, this build comes up clean in clamav so any hits from antiviruses for this build should be reported as false positives.

Re: foo_midi (foobar2000 v2.0)

Reply #149 –
Quote from: raekuul on
Working fine on my end.

Also, this build comes up clean in clamav so any hits from antiviruses for this build should be reported as false positives.
ClamAV as a security measure? ???   Is this a joke for insiders?  ::)
ClamAV can at best be used as a secondary scanner for retired malware.
The last definition update is how old? Okay, I'll give it away: October 25, 2023.
Although I think there have been two updates a year for the past two years. Yeah, ClamAV is improving!

I'm afraid it's more likely that a blind person can correctly identify the color of 5 T-shirts with the help of its blind man's stick than that ClamAV can identify two 0-day viruses with the help of definitions that are several months old, let alone five 0-day viruses.

Regards
Michelist

With greetings from:
https://www.virustotal.com/gui/file/93e28bab767288c13ede2c9ff43448a4ff0513ff40fe144527d603f22ac9c302?nocache=1   :'(