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: foobar2000 v2.1 bugs (Read 16838 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: foobar2000 v2.1 bugs

Reply #75 –
Worked it out - the sqlite database was corrupted. Renamed it and FB starts fine, but need to rebuild the thing as all the visible tags have fallen off the playlists and album list.

Re: foobar2000 v2.1 bugs

Reply #76 –
%playback_time not working in Playlist View (Default UI).

Now playing info
https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Titleformat_Reference#Now_playing_info

Statusbar Text Display (JScript Panel 3 - Per-second updates) are no problem.

TEST:
foobar2000 v2.1 preview 2023-07-20 32bit 64-bit Default UI
SHURE SRH1840, SENNHEISER HD660S2, SENNHEISER HD 490 PRO, DT 1990 PRO, HiFiMAN Edition XS, Bowers & Wilkins P7, FiiO FT5, 水月雨 (MOONDROP) 空鳴 - VOID, Nakamichi Elite FIVE ANC, SONY WH-ULT900N (ULT WEAR) (made a Upgrade/Balanced Cable by myself)

Re: foobar2000 v2.1 bugs

Reply #77 –
About this new pre-version . Can i install it and keep my installation of FB2K 64-bits v2.0 in parallel ?
i don't want to loose , just want to test it ? thanks

Re: foobar2000 v2.1 bugs

Reply #79 –
For WebDAV detection (mentioned in the changelog) have you tried to use PROPFIND?
Code: [Select]
  PROPFIND / HTTP/1.1 
  Host: www.example.com 
  Content-Type: application/xml; charset="utf-8" 
  Content-Length: xxxx 
      
  <?xml version="1.0" encoding="utf-8" ?> 
  <propfind xmlns="DAV:"> 
    <propname/> 
  </propfind>

It should return "HTTP/1.1 207 Multi-Status" response if WebDAV is supported and "HTTP/1.1 501 Not Supported" if not. Though I have no practical experience how compatible/reliable it is across different web servers.

Re: foobar2000 v2.1 bugs

Reply #80 –
Quote from: Air KEN on
%playback_time not working in Playlist View (Default UI).

Now playing info
https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Titleformat_Reference#Now_playing_info

Statusbar Text Display (JScript Panel 3 - Per-second updates) are no problem.

TEST:
foobar2000 v2.1 preview 2023-07-20 32bit 64-bit Default UI

It was a request, not a bug.

SHURE SRH1840, SENNHEISER HD660S2, SENNHEISER HD 490 PRO, DT 1990 PRO, HiFiMAN Edition XS, Bowers & Wilkins P7, FiiO FT5, 水月雨 (MOONDROP) 空鳴 - VOID, Nakamichi Elite FIVE ANC, SONY WH-ULT900N (ULT WEAR) (made a Upgrade/Balanced Cable by myself)

Re: foobar2000 v2.1 bugs

Reply #81 –
Quote from: ApacheReal on
2023-06-20

    HLS radio fixes, segmented MP4 DASH now plays.
   Networking improvements, better read-ahead buffering performance.

There are problems on all the components that manage graphic effects such as Vu Meter, Spectrum etc..

Likewise they are still, unmanageable.

Unlike what was said in my next post, there are significant problems with the radio streams and the management of spectrum / vu meter / seekbar / waveform graphic effects.

With radio streams the effects are either blocked, slowed down or in fits and starts.

Re: foobar2000 v2.1 bugs

Reply #82 –
Quote from: ApacheReal on
With radio streams the effects are either blocked, slowed down or in fits and starts.
Most of my listening is with radio streams, and with Foobar v2.1 preview 2023-07-20 64-bit I am experiencing NONE of what you describe, on the built-in VU and Spectrum meters, Enhanced Spectrum, or Loudness Peakmeter.

I have hardware acceleration checked in Prefs/Advanced/Visualisations, 20ms update interval.

You don't happen to have 32-bit with the old Yegor foo_vst plugin installed do you?  That plugin definitely interfered with my visualizations of the time.

Re: foobar2000 v2.1 bugs

Reply #83 –
Does any one noticed that the program suddenly closes (crash without advice) after some time since opened?
Happens since the preview 2023-07-27
Win 10 x64 foobar2k version x86 (32bit)

Re: foobar2000 v2.1 bugs

Reply #84 –
Quote from: Fabcore on
Does any one noticed that the program suddenly closes (crash without advice) after some time since opened?
Happens since the preview 2023-07-27
Win 10 x64 foobar2k version x86 (32bit)
I noticed similar. But so far I can't catch the pattern. No crash reports.
Happened at the start of playback of radio streams.
Win10 32bit fb2k v2.1 x86 preview

Re: foobar2000 v2.1 bugs

Reply #85 –
yeah, is very unpredictable, could late some minutes as some hours, playing or not to crash without notice. This apply in general playing.

Re: foobar2000 v2.1 bugs

Reply #86 –
Some accessibility bugs:
* In the "Internet Radio" dialog, I can't find a way to switch panels between known stations and search using the keyboard.
* "ReFacets" (opened from the Library menu) doesn't seem to be accessible at all.
* In the "Album List" preferences page, the keyboard shortcuts F2 and Shift+F2 does not work in the list of filters.

Re: foobar2000 v2.1 bugs

Reply #87 –
Quote from: Fabcore on
Does any one noticed that the program suddenly closes (crash without advice) after some time since opened?
Happens since the preview 2023-07-27
Win 10 x64 foobar2k version x86 (32bit)

Same here. I never used the 2023-07-27, which may explain why I didn't notice until recently.

Re: foobar2000 v2.1 bugs

Reply #88 –
You people suffering from the player crashing without crash logger catching it, can you open Windows' Event Viewer and check if Windows Logs -> Application log shows any details.

Re: foobar2000 v2.1 bugs

Reply #89 –
Been using since the last post i made here in this thread, no crashes at the moment.
Deactivating "monitoring while running" and "scan at every startup" the offline volumes the crash disappear
Which i can confirm the bug is in the library scanner when a path is offline or not accessible.

Re: foobar2000 v2.1 bugs

Reply #90 –
Could console messages "Folder watching failure: bad allocation", "Recovering watcher database" and "Unrecoverable playback error: bad allocation" have anything to do with it?
The thing is, I had a drive disconnected. But it should not crash fb2k.


In detailed timings using wmic, here is what I got out of the %appdata% folder for the most recent crash tonight. No unrecoverable playback error this time.
fb2k started 21:41, crashed after forty minutes, in the middle of an eighty minutes long tagless .wav file. There is nothing in the Windows Logs -> Application log from around the time of the crash (I find only things like "Offline downlevel migration succeeded." and "Successfully scheduled Software Protection service for re-start at 2023-08-25T23:50:01Z. Reason: RulesEngine.", but those were minutes before the crash.)

  • 20230825214103.789872+120 file "running" created (and last modified)
  • 20230825214104.843416+120 console-2023-08-25-21-41-04-P17988.txt created
  • 20230825214105.338167+120 metadb.sqlite last modified
  • 20230825214105.447619+120 library-error-log.txt created. It had been cleared on previous run.
  • 20230825214105.633921+120 library-error-log.txt last modified
  • 20230825214105.819222+120 version.txt created (and last modified)
  • 20230825214700.071723+120 folder "playlists-v2.0" last modified. That is six minutes later.
  • 20230825212151.996432+060 folder "crash reports" last modified, suggesting it was attempted written to. (No dump.) I think the "+60" vs "+120" indicates that this is precisely the same timestamp as the next item:
  • 20230825222151.996432+120 console-2023-08-25-21-41-04-P17988.txt last modified.
And here are the last few lines - the only the only entries after I started the aforementioned WAVE file:
Code: [Select]
[2023-08-25 22:21:27.439] Folder watching failure: bad allocation
[2023-08-25 22:21:31.788] Folder watching failure: bad allocation
[2023-08-25 22:21:51.988] Recovering watcher database
[2023-08-25 22:21:51.988] Recovering watcher database
[2023-08-25 22:21:51.996] Recovering watcher database
[2023-08-25 22:21:51.996] Recovering watcher database

Re: foobar2000 v2.1 bugs

Reply #91 –
%__encoding% MISSING
returns AC3 in Matroska and AC3 in MP4/MOV as well.

Same stream in .ac3 is identified as "ATSC A/52A (AC-3)" with encoding "lossy"
In .mka/.mp4(/.m4a and .mov) it is identified merely as "AC3" but neither as lossy nor lossless.

Re: foobar2000 v2.1 bugs

Reply #92 –
Quote from: Case on
You people suffering from the player crashing without crash logger catching it, can you open Windows' Event Viewer and check if Windows Logs -> Application log shows any details.
@Case, thanks for the advice.
Today there was a sudden fb2k crash (no crash log) while listening to a radio stream.
The Windows Event Viewer reports a failure in the ntdll.dll module:
Code: [Select]
  - EventData 
   foobar2000.exe 
   2.1.0.0 
   64e77a7a 
   ntdll.dll 
   10.0.19041.3324 
   da946cf1 
   c0000005 
   000275e3 
   1edc 
   01d9d809e1e06e58 
   C:\Program Files\foobar2000\foobar2000.exe 
   C:\WINDOWS\SYSTEM32\ntdll.dll 
   8e9667b8-b9a2-44c7-85e0-19069a4adc6e
Scanning the OS with DISM and SFC identified and fixed the issues.
I'll see if anything has changed.

Re: foobar2000 v2.1 bugs

Reply #93 –
Does anyone else suffering from crashes happen to have VLevel component? I improved the version I thought I fixed in 2018 and fixed it some more. Update can be found here.

Re: foobar2000 v2.1 bugs

Reply #95 –
Not sure if it's a bug or intentional:

Dimmed and highlighted titleformating displays as their literal string characters when used for playlist custom grouping schemes.

Re: foobar2000 v2.1 bugs

Reply #96 –
In foobar2000 v2.1 preview 2023-08-28 autotrack not working.

items / properties / tools / autotrack number

Re: foobar2000 v2.1 bugs

Reply #98 –
Quote from: blindpainkiller on
Some accessibility bugs:
* In the "Internet Radio" dialog, I can't find a way to switch panels between known stations and search using the keyboard.
* "ReFacets" (opened from the Library menu) doesn't seem to be accessible at all.
* In the "Album List" preferences page, the keyboard shortcuts F2 and Shift+F2 does not work in the list of filters.

These bugs (except ReFacets) still exist in 2.1 preview 2023-11-07.

Re: foobar2000 v2.1 bugs

Reply #99 –
Hi there!

Please take a look at this radio station: http://188.40.97.185:8179/stream
At the end of each composition the connection speed drops to zero and fb2k stops playback with the error:
Code: [Select]
Decoding failure at 3:22.919 (Network error):
"http://188.40.97.185:8179/stream"
Sometimes playback continues, but most often it stops. This happens for "Primary Sound Driver".
For exclusive mode, playback continues but with glitches at the beginning of each composition.
Does anyone have the same symptoms?

Windows 10, fb2k v2.1 2023-11-27 х86