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 16550 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: foobar2000 v2.1 bugs

Reply #100 –
Using Foobar2000 v2.1 2023-12-06 Denmark Radio HLS (AAC) stations do not play in Internet Search. One station is "DR P4 Fyn (AAC)". Copying URL to Known Stations / Play by stream address, the station play. Using IOS Foobar2000 v1.4.2 2023-12-07 Internet Radio / Radio Search, the station play.

Re: foobar2000 v2.1 bugs

Reply #101 –
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.
* In the "Album List" preferences page, the keyboard shortcuts F2 and Shift+F2 does not work in the list of filters.

Quote from: sacduser on
Using Foobar2000 v2.1 2023-12-06 Denmark Radio HLS (AAC) stations do not play in Internet Search. One station is "DR P4 Fyn (AAC)". Copying URL to Known Stations / Play by stream address, the station play. Using IOS Foobar2000 v1.4.2 2023-12-07 Internet Radio / Radio Search, the station play.
The above issues should be fixed in today's preview.

Quote from: Sergey77 on
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?
Output mode doesn't matter for decoding failures. I don't see how you could get different behavior depending on whether you use exclusive mode playback or not.
I haven't used any network analyzers to see what happens to the traffic, but I have tried that stream a few times and there have been no errors when track changes.

Re: foobar2000 v2.1 bugs

Reply #102 –
Thank you @Case for your comment.
On my side this happens exactly as I described. For the version out of the box too.
But if this doesn’t happen to anyone, then let’s assume that the reason is in my hardware and network.

Re: foobar2000 v2.1 bugs

Reply #103 –
Edit on edit: Tested http://188.40.97.185:8179/stream with yesterday's v2.1 preview, 32-bit.
After a few songs, I got the
Decoding failure at 7:49.107 (Network error):
"http://188.40.97.185:8179/stream"
But the "Playback interrupted, source is stalling..." isn't necessarily between tracks like first I thought.

Also @sacduser : I googled up that DR P4 Fyn internet radio, went through the "inspect" routine in my browser, found the m3u8 - and fb2k starts playing. Here is the URL:
https://drod24m.akamaized.net/all/clear/none/06/6577804b5bcad1249c9f2406/13652302501/stream_ts/LIGA_DRLYD2022Sep_AudioMain_256.m3u8

Re: foobar2000 v2.1 bugs

Reply #104 –
i posted this one year ago in v.2.0 bugs already...
i run win10 in dark mode on uhd screen scaled 125%. the visibility of everything is worse readable (for me) in v.2 vs. v.1.6.
is there an option to scale up and colour the fonts, also for submenus and preferences? also it would be nice to be able to resize the preferences window when working with advanced options.

one year later the gui scales + views good in general, but preferences window and upper menu bar (partially) still show in 100% only. i am not shure about submenus (right mouse click items).
in the upper menu bar "Output" "Order" "RG" are still scaled only 100%.
i am using default ui with green fonts + highlight on black background, selection orange since the beginning ;-D
running v.2.1.2. but still not using it as daily driver since preferences window is unusable for my 50ies eyeview. still greatfull foobar exists

Re: foobar2000 v2.1 bugs

Reply #105 –
Options for bigger font on things like the menus in the main view would be nice, but I wouldn't want it to be forced in a new version. I'm happy with how it looks now.

The preferences window could definitely use better scaling support though. Several component-specific pages have elements cut off because they are scaled bigger than the window size.
Think millionaire, but with cannons.

Re: foobar2000 v2.1 bugs

Reply #106 –
Quote from: Cannonaire on
... I wouldn't want it to be forced in a new version. ..
agreed. in preferences there could be other rows -> default user interface-> colours+fonts-> fonts
for the entiere preferences window and upper menu bar.
upper menu bar needs some font fixes before i believe.

Re: foobar2000 v2.1 bugs

Reply #107 –
Quote from: Cannonaire on
The preferences window could definitely use better scaling support though. Several component-specific pages have elements cut off because they are scaled bigger than the window size.

I'm guessing you won't find anything wrong with any built in fb2k preference page. If you have examples, be specific so they can be fixed.

If you have problems with other components, they need updating by whoever maintains it. That area is their own blank canvas to do anything they like and fb2k has no control over it.

Re: foobar2000 v2.1 bugs

Reply #108 –
The main reason for my post was to say that I think it would be better as an option than an overall change for the font sizes to be different.

It's true, all of the default pages work perfectly. I'm just confused that some elements on a preferences page (again, for specific components) would change in size differently from the window itself. Then again, I don't know a whole lot about how Windows scaling works in various programs. And none of the oddities have prevented me from using components to the fullest either. I suppose it's less of a bug report and more of an expression of confusion at how it happens.

As far as specific components go, it looks like after switching to 64 bit recently, only one of the components I still use has any issues with scaling, and that is the old Queue Contents Editor. I thought there were more, but nothing else significant to me has problems anymore.
Think millionaire, but with cannons.

Re: foobar2000 v2.1 bugs

Reply #109 –
well there is issues with scalability in preferences window here. i dont think it is neccessary to leave it like that

why not make the preferences window resizeable instead of forcing ppl to hover over entries to read whats there?

Re: foobar2000 v2.1 bugs

Reply #110 –
and here is to complete what i mean by preferences window and upper menu bar (partially) still show in 100% only.

"Output" "Order" "RG" are barely readable and font size is not configurable.

Re: foobar2000 v2.1 bugs

Reply #111 –
Quote from: orangefx on
and here is to complete what i mean by preferences window and upper menu bar (partially) still show in 100% only.

"Output" "Order" "RG" are barely readable and font size is not configurable.
Right click and add toggle layout editing mode. Turn it on, and then you can resize it all.
Think millionaire, but with cannons.

Re: foobar2000 v2.1 bugs

Reply #112 –
wrong. font size is not configurable. as with preferences window also this window does not resize font size

Re: foobar2000 v2.1 bugs

Reply #113 –
Quote from: orangefx on
wrong. font size is not configurable. as with preferences window also this window does not resize font size

I thought you meant the size of the UI elements was pushing the text off. My mistake. No, the font isn't configurable as far as I know. I only saw the top portion of your text where you said it only showed in 100% only, leading me to think you were talking about elements becoming unviewable.
Think millionaire, but with cannons.

Re: foobar2000 v2.1 bugs

Reply #114 –
Quote from: orangefx on
why not make the preferences window resizeable instead of forcing ppl to hover over entries to read whats there?

I can't see the size of the preferences window changing. All components have been hardcoded using absolute positioning/size for years. Not a single one is ready for it to dynamically grow. It would look rubbish being bound to the top left corner with big blank spaces to the bottom/right.

edit: I suppose it could expand while the "advanced" node is selected.

Re: foobar2000 v2.1 bugs

Reply #115 –
None of this is really a bug except as it related to improper scaling in specific component windows. Isn't this more of a feature request?
Think millionaire, but with cannons.
 

Re: foobar2000 v2.1 bugs

Reply #116 –
i dont think i am the only f2k user with windows and a 4k screen. dark mode was introduced in v.2, in the beginning there was only system (dark in my case) mode working. there were some layout bugs ironed out since then. fonts are sizable for many parts of the ui, but not for all. to me this looks like a bug. @Cannonaire you may call it what you like.

i would like to use dark/system colour. to me dark mode in v 2.x is unusable because i cannot read it and shurely i am not the only one. 

@marc2k3 i am not familiar with coding. if things did not change for many years, maybe its time to make a change. screen space and resolution is growing.