What kind of options do you wish?)ZXTune project can implement this options.Do you really need them?

Panning and lowpass for example. Not crucial but these options are common in emulators AFAIK.And, having this component, I may remove foo_input_ym, right?Out of interest, what component will be used for playing .ym files if I have both your and foo_input_ym?EDIT: And the same in case of .ay, will it be played by foo_gep (Game Emu Player)?

Panning and lowpass for example. Not crucial but these options are common in emulators AFAIK.

May be i'll add this options to next version.

QUOTE

And, having this component, I may remove foo_input_ym, right?Out of interest, what component will be used for playing .ym files if I have both your and foo_input_ym?EDIT: And the same in case of .ay, will it be played by foo_gep (Game Emu Player)?

Out of interest, what component will be used for playing .ym files if I have both your and foo_input_ym?EDIT: And the same in case of .ay, will it be played by foo_gep (Game Emu Player)?

Accordingly to Peter's words and my own experience with other components it's "random by design" - which means that sometimes .ay files will be played by foo_input_ym and sometimes by foo_gep. Same for other formats. There's no specific logic wich lets foobar choose which component will be used every time, as well as there are no user configurable settings for such options.

Does anyone noticed craches after installing this component?At first, after installing it everything worked fine. I decided to remove .dll for input_ym as it's redundant after installig input_zxtune. And after that I couldn't even open foobar - it has crashed 4 times when I tried to start it. So I placed foo_input_ym.dll again in components directory and foobar now starts properly, but sometimes it just closes unexpectly (right after start), even if nothing is played. After installing this component foobar mostly uses up to 50% of six core CPU time right after start. Any suggestions/reports? Online troubleshooter says that 3 of components that I use are often causing problems: foo_amipwrapper.dll : AMIP Wrapper 1.01, foo_bpm.dll : BPM Analyser 0.2.4.1 and foo_input_usf.dll : LazyUSF 2.1 (Build Jun 26 2011). I will NOT uninstall first 2, maybe I can try with 3rd one.

EDIT:Thanks for hint deus-ex, I forgot about that, it was long time ago when I looked into GEP settings - maybe that's connected with my crashes.

EDIT2:Disabling YM in GEP doesn't help. The only way to eliminate 50% CPU usage at foobar start and unexpected closing was removing input_zxtune from components...

I haven't tried to clean install foobar and use your component. But after so long time I just tried to install your component again. foobar has crashed. And this is what I got from online troubleshooter:

EDIT3:Currently I haven't made a clean install, but I removed all manually installed components, as well as installed via UI. So foobar was ran with only standard components and foo_input_zxtune.dll (installed manually). Crash report is in file failure00000016.txt . I doubt that clean istall will help.

djdron, you owe me a beer. I've made a serious investigation. Generally none of my components caused problems with zxtune. I've installed everything, one by one, restarting foobar after every component added. Every. Input, DSP, OSD, etc. After that I even restored all my settings - and nothing bad happened. Everything seemed fine until... I deleted mudlord's foo_input_ym. I decided that if everythings works properly and now I got 2 components doing literally the same (opening YM files), then I can delete the one which opens only the one format and keep the one with wider abilities (zxtune). After deleting foo_input_ym.dll foobar started crashing. Restoring foo_input_ym doesn't changed anything. The only thing that I can do now is to delete foo_input_zxtune. Or try to reset config and istall everything from scratch. All crash reports point to foo_input_zx_tune...

Further investigations has been made. What can I do to use foo_input_zxtune.dll :1. install foobar normally - this MUST be clean istall. Previous has to be permanently deleted with uninstaler2. allow foobar to run after clean installation. then exit it. This ensures that current changes are somehow applied and saved3. install foo_input_zxtune.dll as FIRST component (I install nearly everything manually into "components" directory in installation folder)4. run foobar and exit it for reasons described above.5. now I can install every other component I used before, to both components and user-components folders - except foo_input_ym !! it shouldn't be installed, then run it and exit it6. now I can import my wavecache db, database (library), playback statistics, cddb data and what is most important - my custom theme file. Now run and exit foobar. 7. now I can import all my settings, for all my components - except file Core.cfg !! . Run foobar and exit.8. now the best - now I can import Core.cfg. My fcuk1n old Core.cfg from all previous foobar installations...

I tried to make points 3-8 at one time. Fail. I had to make another clean install. I tried to make points 5.-8. at one time. Fail. Clean install needed. I tried to make only point 7 and 8 at one time. Fail again. Maybe points 5-7 can be done at one time, but I haven't tried. For sure points 1-4 must be performed as described and point 8 must be separate operation. This let's me use foobar with foo_input_zxtune, but even now crashes accur frequently, foobar shuts down unexpectedly, or despite I closed it properly I got information that last time it was shutted down abnormally. I tried to disable all active DSPs but without result.

4 crash reports included.

EDIT:I determined that this situation is somehow connected with my old Core.cfg file. After several restarts everything stops working correctly and zxtune prevents foobar from start, causing repeated crashes. Another 2 reports.

EDIT2: It seems to be problem with Media Library. Most of crash reports contain "folder watcher thread=>watch loop=>input_entry::g_open_for_info_read" as last call path. Maybe that amount of file extensions and metadata schemes intorduced with this component cause probnlems with ML. I took my old Core.cfg file and managed to remove all folders from ML. It looks like it works again... That was specific to old Core.cfg - loads of folders/files to watch and analyze. New/resetted configuration always missed watched folders... Several crash reports attached.

Additionally several times I got this error:while folders were initialized in Media Library.

Given that the crashes don't occur when foo_input_zxtune is only used for playback and not for background scanning, the question is now whether the component supports multiple decoder instances. Could this be the reason for EpicForever's problems, djdron?