we’ll need more information about your slow setup, such as your list of installed components, the type of files and their tags that you are working with, etc..

• foo_albumlist.dll
• foo_cdda.dll
• foo_converter.dll
• foo_dsp_std.dll
• foo_fileops.dll
• foo_freedb2.dll
• foo_input_monkey.dll
• foo_input_std.dll
• foo_keep_queue.dll
• foo_navigator.dll
• foo_playcount.dll
• foo_playlisthistory.dll
• foo_queuecontents.dll
• foo_rgscan.dll
• foo_uie_albumlist.dll
• foo_uie_biography.dll
• foo_uie_lyrics3.dll
• foo_ui_columns.dll
• foo_ui_std.dll
• foo_vis_shpeck.dll

Also, it might be somewhat complicating that you’re comparing two different versions...

I'm seeing the same lag when applying changes when adding or removing panels or splitters to my layout.

The irony is that I set up the portable because the installed version was getting buggy and crashing a lot.  But in the process of setting up a whole new portable copy with a radically different layout

I originally thought portable made no changes to system files.  But I think I read that it does do something related to enabling or disabling something, registry settings?, for multiple users on the system. Wonder if there's anything going on there.

Quote

I originally thought portable made no changes to system files.  But I think I read that it does do something related to enabling or disabling something, registry settings?, for multiple users on the system. Wonder if there's anything going on there.

No, it just doesn’t use the registry. All settings are stored within its single folder, nothing outwith that is modified, no system settings are altered (hence the absence of an ability to associate files), etc.

Foobar2000 can now be installed in two modes: standard and portable.

Standard mode
Standard mode is similar to the “install for all users” option in older versions. You need administrative privileges to install foobar2000 in this mode.

Portable mode
Installing in portable mode only extracts the installer content and creates additional files that tell foobar2000 to store any configuration data in its installation folder as well as not to alter the Windows registry. Note that it is not possible to edit file type associations with foobar2000 when using portable mode, as that would require changes in the registry.

P.S. The official page mentioning some unknown application called Foobar2000? Hax

Well it is some issue related to the media library.  I removed the main root folder and then added ones under it one by one, and then in small groups.  Each time I added more files, the lag making any config changes grew a little.  It jumped noticeably after adding folders with a lot of files.

I found something annoying about both my copies of FB2K, one a Vista system and one on the Win7 system.  When I added folders to the media library and then clicked 'Apply' before closing the config screen, FB2K was totally non-operational for several minutes until it completed the process of scanning and adding all the files.  If instead of clicking 'Apply' I click 'OK', the config screen closes and I have full control over FB2K when files are being scanned into the library,

Is that common for everyone?

Is this a network share? I've had similar delays when adding folders over the network.

Try running Process Monitor and logging what happens, isolated to process name foobar2000.exe?

• Downloaded Process Monitor. 
• Created a filter: 'Process Name' - 'is' 'foobar2000.exe' - 'Include'
• Enabled 'Capture Events'
• Deleted part of an MP3 title tag
• Waited 5-10 seconds until FB2K responded again.
• Disabled  'Capture Events'

Appendix C – How to debug filesystem operations or process-related issues

  1. If you don't have it already, download Process Monitor from Microsoft and start it. It doesn't need any installation, you might even use the "Run Process Monitor now from Live.Sysinternals.com" link.
  2. Follow the reproduction scenario up to the point before something bad happens, then clear the Process Monitor window (toolbar icon with the gum) to capture only the relevant information (Note: You might be asked to do it differently later if needed.)
  3. Perform the actions which result in the buggy behavior.
  4. Stop Process Monitor capture (toolbar icon with the magnifing glass).
  5. Save the log to the native PML file, pack it to a ZIP archive or similar (it will compress pretty well) and upload here to the "Uploads - (fb2k)" forum or wherever, then post a link.
  Note: Naturally, you can filter the Process Monitor log for unrelated background processes filling it with nonsense etc., unless the issue being debugged is some weird sharing violation problem between multiple applications.

• Logfile.PML

Oh, interesting. There's even a spot in the log where it stops emitting any log entries for 3 seconds. Hmm, and an awful lot of WinSock2 related queries. Maybe you should also try running Microsoft Network Monitor and see if there's any network queries going on during any of those tagging operations?

I also suggested the Process Monitor logging so you could check if there are any particular parts of the process which differ between logs of the portable and non-portable installations.

Quote from: kode54 on 2012-06-02 18:23:47

Try running Process Monitor and logging what happens, isolated to process name foobar2000.exe?

This is way over my head. 

• Downloaded Process Monitor. 
• Created a filter: 'Process Name' - 'is' 'foobar2000.exe' - 'Include'
• Enabled 'Capture Events'
• Deleted part of an MP3 title tag
• Waited 5-10 seconds until FB2K responded again.
• Disabled  'Capture Events'

I can see the name of the file I tagged in the results along with every other track on the same album.  The one I tagged does show up more often.  But I have no idea what to look for.

Should I do this as well?  I've had the issue of foobar2000 (portable) hanging up on me for 10 seconds if I add new files into my media library by either copy+paste or foobar2000's own Converter, for as long as I can remember.