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_input_monkey.dll (Read 10066 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

foo_input_monkey.dll

Seems foo_input_monkey.dll decoding not properly - bad quality of APE (only) ( some distortions/hiss). Can see that if convert APE into WAV, then compare. APE sound not equals WAV... No problems with FLAC.  In WINAMP ( standard in_ape.dll) - equal APE/WAV sound quality. Trying to rename standard  in_ape.dll  into  foo_input_monkey.dll, but Foobar not accept that  .
Any idea?

foo_input_monkey.dll

Reply #1 –
Renaming won't do good as those are different files for different programs.

You don't give much information. Be sure to use the correct ape component for the latest foobar2000 versions.

Have you verified the ape file is OK?

foo_input_monkey.dll

Reply #3 –
Quote from: Alexxander on
Renaming won't do good as those are different files for different programs.

You don't give much information. Be sure to use the correct ape component for the latest foobar2000 versions.

Have you verified the ape file is OK?

Foobar0.9.6.9., foo_input_monkey.dll - 2.1.4, released on 2009-05-02.
foo_bitcompare.dll compares length/number of samples only and show no difference. But sound quality is different.
Compare by youself -- take any APE track, convert to WAV, then listen - APE is not equal to WAV.

foo_input_monkey.dll

Reply #4 –
Quote from: serge22 on
foo_bitcompare.dll compares length/number of samples only and show no difference. But sound quality is different.
Compare by youself -- take any APE track, convert to WAV, then listen - APE is not equal to WAV.

My understanding is that foo_bitcompare.dll compares the bits, if the file is bit for bit identical then the differences you're hearing are placebo. Can you ABX the differences?

C.
PC = TAK + LossyWAV  ::  Portable = Opus (130)

foo_input_monkey.dll

Reply #5 –
Quote
foo_bitcompare.dll compares length/number of samples only

No, it also compares content. No difference means that the files have the same content.

Quote
APE is not equal to WAV.

It can be louder/quieter due to replaygain, but nothing more.

foo_input_monkey.dll

Reply #6 –
Quote from: lvqcl on
Quote
foo_bitcompare.dll compares length/number of samples only

No, it also compares content. No difference means that the files have the same content.

Quote
APE is not equal to WAV.

It can be louder/quieter due to replaygain, but nothing more.

Of course - the same content . But foo_input_monkey.dll badly decoding  this APE content with slight dirty hiss(instead of WAV - no decoder) !!!
Does it hard - to compare APE vs the same WAV by youself each other??? And listen by your own ears difference of sound quality ???

foo_input_monkey.dll

Reply #7 –
You are suggestion something that should be theoretically impossible. Before APE files are played they are decoded to PCM (the format inside wav files).. So:
1) APE --> decoding til PCM/wav --> soundcard
2) APE --> decoding to PCM on the fly --> soundcard

should sound exactly the same. Since it is you that is suggesting something that should not be possible it is you that should supply proof in the form of blinded tests. Otherwise noone has any reason to take you seriously.

foo_input_monkey.dll

Reply #8 –
Let me see if I understand:
  • You have a WAV file (say pre_APE.wav).
  • You encode to APE (pre_APE.ape).
  • You decode the APE to WAV, which requires foo_input_monkey.dll (post_APE.wav).
  • You run foo_bitcompare on "pre_APE.wav" and "post_APE.wav" and they are bit for bit identical.
  • Yet even though they are identical they sound different.
Is that correct?

C.

EDIT: added bullets, and was too slow - yes, exactly, this is what is happening when playing -- decode to PCM > soundcard.
PC = TAK + LossyWAV  ::  Portable = Opus (130)

foo_input_monkey.dll

Reply #9 –
Well, will begin again from beginning  .

Typical situation - you have/download lossless music (CD image+CUE, or separate tracks) in APE. Of course listening that music in the player (FOOBAR).
The problem is - FOOBAR's foo_input_monkey.dll decoding badly ( slightly dirty hissed sound). That not occurs with FLAC or WV. That not occurs with APE in WINAMP, which uses original unmodified in_ape.dll (360 kb) (but WINAMP can't play CUE). That occurs  in FOOBAR with APE only due to using modified from original Monkey's his own foo_input_monkey.dll (266 kb).  Of course the simpliest way to fight this bug - convert APE to FLAC and listen with original quality, but a lot of time loosing.

Jan S. - APE --> decoding to PCM on the fly --> soundcard. Of course - but decoding by wrong foo_input_monkey.dll. What to do, if this .dll have a bug ???

Before posting comments such as "it can't be...", " ...placebo...", "theoretically impossible..." simply do compare by youself, please.
Do the folllowing:
1.Take any APE track.
2.Convert this track to WAV, or FLAC, or WV by any converter ( simply by FOOBAR).
3.Listen/compare this APE vs WAV same track.
4.Feel the difference.

The question was - does it possible to replace wrong modified  foo_input_monkey.dll  by correct original ?
Or how to contact developer to report a bug ?


foo_input_monkey.dll

Reply #10 –
Quote from: serge22 on
4.Feel the difference.

See TOS #8

You've provided no proof that you can "feel the difference". Use fb2k's ABX comparitor.
I have foo_input_monkey.dll and no problem - I can't "feel the difference".
Furthermore when I decode as per my example I get 100% bit for bit identical - which means there is NO difference to be felt.

You need to provide ABX results to prove you can hear a difference.

C.
PC = TAK + LossyWAV  ::  Portable = Opus (130)

foo_input_monkey.dll

Reply #11 –
serge22: Instead of telling the world what to do, first do what the HA world is telling you: Do an ABX test! Thousands of people haven't detected a single problem with ape decoding in foobar2000 for quite a few years now. Without a proof you can hear a difference don't waste time of others.

Post a list of installed and active components and ABX results.

foo_input_monkey.dll

Reply #12 –
Quote from: serge22 on
Well, will begin again from beginning  .

Typical situation - you have/download lossless music (CD image+CUE, or separate tracks) in APE. Of course listening that music in the player (FOOBAR).
The problem is - FOOBAR's foo_input_monkey.dll decoding badly ( slightly dirty hissed sound). That not occurs with FLAC or WV. That not occurs with APE in WINAMP, which uses original unmodified in_ape.dll (360 kb) (but WINAMP can't play CUE). That occurs  in FOOBAR with APE only due to using modified from original Monkey's his own foo_input_monkey.dll (266 kb).  Of course the simpliest way to fight this bug - convert APE to FLAC and listen with original quality, but a lot of time loosing.

Jan S. - APE --> decoding to PCM on the fly --> soundcard. Of course - but decoding by wrong foo_input_monkey.dll. What to do, if this .dll have a bug ???

Before posting comments such as "it can't be...", " ...placebo...", "theoretically impossible..." simply do compare by youself, please.
Do the folllowing:
1.Take any APE track.
2.Convert this track to WAV, or FLAC, or WV by any converter ( simply by FOOBAR).
3.Listen/compare this APE vs WAV same track.
4.Feel the difference.

The question was - does it possible to replace wrong modified  foo_input_monkey.dll  by correct original ?
Or how to contact developer to report a bug ?

foo_input_monkey.dll and in_ape.dll are plugins for two different programs. foo_input_monkey.dll is not a modified in_ape.dll. They are based on the same sourcecode.
When you decode to wav using foobar it uses foo_input_monkey.dll too, so you get the same data in the way that you do when you play the file directly. If the plugin has a bug it should show up in the wav file too.
If you are right but don't supply proof no-one can/will help you and you are wasting everybody's time.
If you are wrong you are wasting everybody's time.

Until you attempt to supply proof there is no point in posting anything more.

foo_input_monkey.dll

Reply #13 –
In theory, APE decoding is more CPU intensive. Greater power consumption can lead to some audible artifacts.

But this should also affect Winamp decoder too.

foo_input_monkey.dll

Reply #14 –
Few words how ABX(in foobar) works - it convert both tracks to PCM 2822 kbps, then compare sample by sample.  In this case ABX is useless, because main/the only source is APE. ABX will compare the same ( both tracks(for ABX) are decompressed from the only APE source) and will show 100% identity. That's the same as to decompress from one source two times and then compare these two clones.

Don't know which way Foobar convert / decoding on the fly (must be different algorithms or foo_converter.dll for convert?), but bugs/artifacts with decoding APE on the fly really presents .  Looks like light white noise/hiss.

foo_input_monkey.dll

Reply #15 –
Quote from: AlexZ on
but bugs/artifacts with decoding APE on the fly really presents .  Looks like light white noise/hiss.

Sounds to me like poorly designed motherboard and on-board audio. Try playing WAV file while doing some CPU intensive tasks on background.
Sharing delusions since 1991.

Re: foo_input_monkey.dll

Reply #16 –
Today as I ran Foobar2000 v2.0 beta 34, this following error pops up

Failed to load DLL: foo_input_monkey.dll
Reason: Obsolete component; please remove.

But I can't find this file anywhere on C:\ drive whatsoever. What's going on? Thanks.

It turns out I have to go to

C:\Users\******\AppData\Roaming\foobar2000\user-components

C:\Users\******\AppData\Roaming\foobar2000-v2\user-components和user-components-x64

to delete.

Re: foo_input_monkey.dll

Reply #17 –
Monkey is now available out of the box. https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Version_2.0_Release_Notes
Remove foo_input_monkey.dll in File | Preferences | Components