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.0 bugs (Read 137888 times) previous topic - next topic
0 Members and 7 Guests are viewing this topic.

Re: foobar2000 v2.0 bugs

Reply #825 –
I want to warn that the following Actions are interchanged:

Playback / Volume / Up (instead of UP it lowers the volume).

Playback / Volume / Down (instead of DOWN turn up the volume)

Re: foobar2000 v2.0 bugs

Reply #826 –
How did you reach that conclusion? The actions work exactly as they should here both in foobar2000 v2.0 and in the latest 2.1 preview. Both in 32-bit and 64-bit versions.

Re: foobar2000 v2.0 bugs

Reply #827 –
@josemescud - Have you perhaps edited the "Volume step (dB)" setting found under Preferences -> Advanced -> Playback? It currently doesn't prevent you from entering negative values. If you enter a negative value there that will reverse the adjustment direction.

Re: foobar2000 v2.0 bugs

Reply #828 –
Quote from: Case on
@josemescud - Have you perhaps edited the "Volume step (dB)" setting found under Preferences -> Advanced -> Playback? It currently doesn't prevent you from entering negative values. If you enter a negative value there that will reverse the adjustment direction.

Thank you very much for your help.

You were right. The Volume Step value I don't think I ever modified it. The current value was -5. I changed it = 2 and the keyboard shortcuts for volume up and volume down work perfectly.

Re: foobar2000 v2.0 bugs

Reply #829 –
Quote from: edogawaconan on
I don't know if it's intended, in 1.6.x I can ctrl-f (on playlist) -> type thing -> press enter to play the first hit but I can't do that anymore in beta 10.
just want to report that this is still the case in 2.0 🥲
at least I can work it around by closing the find window first (by pressing esc) and then press enter.

Re: foobar2000 v2.0 bugs

Reply #830 –
Dear Community, I like to report that iPod manager 0.7.2 does not work properly with foobar v. 2.0. The device is recognized but "send playlist" leads to "foobar2000 afcfileref open" error which states that the divice is locked. Uninstall foobar v.2 and restinstall v.1.6.16 fixed the problem.

Re: foobar2000 v2.0 bugs

Reply #831 –
@felix23
I can use it without any problems

iPod nano 6th x2, 7th x1
iPod shuffle 2nd x1, 4th x2

foobar2000 v2.1 preview 2023-09-14 32-bit
iPod manager 0.7.2
iTunes 12.12.10.1 x64
Windows 10, 11 Home

I want it to be compatible with 64bit.





You should move to this thread.
iPod manager: https://hydrogenaud.io/index.php/topic,45160.4200.html
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.0 bugs

Reply #832 –
Sorry if this was posted....

Library not showing DFF or DSF (DSD) files.  In WIndows, I set the file type to be foobar and foobar icon shows in windows explorer.   Win 11 all updates.  Had to move back to 1.6.17...  Both 2.0 and beta has issue.

Otherwise, a great build... thanx... I love the hide devices... I switch devices all the time... just great.

Bruce in Philly

Re: foobar2000 v2.0 bugs

Reply #834 –
I did, nothing...

Yea, I saw that on some other forum... didn't work.   Of course I could have done something wrong but I don't think so... are you sure that will work?  If you are sure, I will re-load 2.0 and try it again... but I am 99% sure I did.

Peace
Bruce in Philly

Re: foobar2000 v2.0 bugs

Reply #837 –
Obligatory "If you want to play DSD, then WavPack can compress them losslessly as long as you use the WavPack executable rather than conversion by a player" comment. (Oh and DST packed are not supported.)

Re: foobar2000 v2.0 bugs

Reply #838 –
Quote from: Porcus on
Obligatory "If you want to play DSD, then WavPack can compress them losslessly as long as you use the WavPack executable rather than conversion by a player" comment. (Oh and DST packed are not supported.)

I just ensured that another PC I have in my home has Foobar 2.0 and has the foo_input_sacd compoent installed.... no go... not picking it up in the library.   So that is two machines, one with Win 10 and other 11 that wont see DSF or DFF files.  Again, I these file types assigned in windows to foobar.

Thanx,
 Bruce in Philly

Re: foobar2000 v2.0 bugs

Reply #839 –
Quote from: Porcus on
Obligatory "If you want to play DSD, then WavPack can compress them losslessly as long as you use the WavPack executable rather than conversion by a player" comment. (Oh and DST packed are not supported.)

I just re-read your post....  The issue isn't playing these files, it is just that Foobar doesn't recognize their existence.  I don't want them converted or "played", just passed through to my DAC bit-for-bit.   The bug in Foobar is a library issue.

Peace
Bruce in Philly

Re: foobar2000 v2.0 bugs

Reply #840 –
@Air Ken

I guess my wired setup might be the reason but it worked for several years. I use an ipod touch 2G and I love the playlist features which help me to teach my sport lessons. I know that sounds strange but I do not like the idea of streaming. I own the music and I can use it when I want to use it. Anyway

when I connect my ipod touch 2G it will be recognized by win11 under usb-devices (apple mobile device usb composite device). In this state I cannot use the ipod manager 0.7.2 because the device can not be found. It is every time the same procedure. Now I need to uninstall the apple mobile device usb composite device driver and also set unistall driver. After that I need to rediscover all changed devices. Now the ipod touch 2G is recognized as USB-Controller device (apple mobile device usb driver ver 6.0.9999.67 from 18.05.2015). In this state ipod manger 0.7.2. finds my ipod touch 2G and can be synced. I know it sounds rediclious but this worked for me several years since the 2.0 update appeared. What I am looking for is a configuration without the whole itunes package, just the drivers to get foobar running. I spended so my hours in the past to get it running and I really fear the effort again to set it up working. May you or others had the same issue and can provide a setup that is foolproof.

Many thanks.

Re: foobar2000 v2.0 bugs

Reply #841 –
@felix23

I own two iPod touch 7th 32GB.
iPod touch is not supported.
I was thinking how much I wish I could use it.
Currently, it is connected to foobar2000 v2.0 32bit as foobar2000 mobile iOS.
Or as a device controller...
MonkeyMote for foobar2000
https://www.monkeymote.com/home
------------
hahaha...
I didn't know there was such a trick.
But this can't be helped.
This is not a bug in foobar2000 v2.0.
We can use any supported iPod, so it's 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.0 bugs

Reply #842 –
Quote from: Bruce-in-Philly on
I just re-read your post....  The issue isn't playing these files, it is just that Foobar doesn't recognize their existence.  I don't want them converted or "played", just passed through to my DAC bit-for-bit.   The bug in Foobar is a library issue.
Did you perhaps add your DSD collection path to media library before you installed foo_input_sacd component? It seems foobar2000 v2.x remembers all the files it sees when library is initialized and it will keep ignoring all old files it didn't recognize during initial scan even if you later add components that can handle them.
You should be able to work aroud this issue by removing the media library path from Media Library configuration, restart foobar2000, then add the path back.

Re: foobar2000 v2.0 bugs

Reply #843 –
@Air Ken

In my humble opinion there has to be any connection with the new version. I reinstalled foobar2000_v2.0 (32bit) in a different directory and ran it. The ipod touch 2g is support (https://wiki.yuo.be/dop:start at least for my software version) and was recognized. I used File->iPod->manage contents, where a window appeard, curiously since some update in the past "genius playlists" appeard several time on my device, but I don't want to complain about it, if the whole device still syncs. Now I tried to remove some old playlist and all of these genius playlists. Finally I hit "save and close" and following error appeard

I/O Error: AFCFileRefOpen returned: 2 Path was: /com.apple.itunes.lock_sync

So I closed foobar2.0 and reopened directly the old version 1.6.16 and did the same steps above, but this time it worked. So in my humble opinion something is not right aligned between these two versions. Does anybody has any ideas about it?

Many thanks.

Re: foobar2000 v2.0 bugs

Reply #844 –
Quote from: Case on
Quote from: Bruce-in-Philly on
I just re-read your post....  The issue isn't playing these files, it is just that Foobar doesn't recognize their existence.  I don't want them converted or "played", just passed through to my DAC bit-for-bit.   The bug in Foobar is a library issue.
Did you perhaps add your DSD collection path to media library before you installed foo_input_sacd component? It seems foobar2000 v2.x remembers all the files it sees when library is initialized and it will keep ignoring all old files it didn't recognize during initial scan even if you later add components that can handle them.
You should be able to work aroud this issue by removing the media library path from Media Library configuration, restart foobar2000, then add the path back.

I did this... no go.   BTW, if one should need to do this, then what happens when you copy new DFF files to the music directory?  Delete and restart again?  No, 1.x versions worked fine... no hoops to jump through.  Foobar has always been great... i have just one directory (and only one path in foobar) on a NAS called Music.  Under that is a folder for each band or artist, under that a folder for each album, and under that, the tunes.   Always worked really well and pretty fast too.  When I buy new files, I just copy, via Windows, to the music folder.   If Foobar is running, it finds it almost immediately... if not running, it will maybe 5 - 10 minutes after firing it up (I have a huge library).  It just worked.  Been using it for what... now over 20 years or so???  I dunno for ever...

Peace
Bruce in Philly
 

Re: foobar2000 v2.0 bugs

Reply #845 –
That initial scan issue is the absolutely only problem I can trigger. And it is a bug. But even if you suffered from that problem any new added files would be visible just like with the old foobar.
Note that this issue is super easy to avoid for you: once you install foobar2000 v2.x, install foo_input_sacd first. After it is installed, configure media library paths.

Are you certain you restarted foobar2000 after you removed the configured media library paths? Without this step the previously ignored entries will not be cleared.
Perhaps I should suggest you to remove the "library-v2.0" directory under the foobar's profile path. That will achieve the same plus it will reset the exclude filter to default.

PS: this thread is scarily titled foobar2000 v2.0 bugs. Everyone should be using the v2.1 previews as that is where all the recent developments and fixes have happened. The 2.0 "stable" is half a year behind on fixes.

Re: foobar2000 v2.0 bugs

Reply #846 –
Ok, here is what I am about to do....

I am going to download and run 2.1 (have 2.0 on my test machine).  Then I will ensure foo_input_sacd is active... it should as it is already there.   Then I will delete the path to my music folder.   Then I will shut down foobar... reopen.. then initialize the path to the folder and I will report what happens.

Update:   OK.... did the deeds.... now waiting for library to build.....

Update: WOOOHOO!!! it worked.  Thanx so much.  Yep a bug, but now I am back in business.

Peace
Bruce in Philly

Re: foobar2000 v2.0 bugs

Reply #847 –
@felix23
Oops.
Your older iPod touch is on the list of supported models.
https://wiki.yuo.be/dop:start#supported_models

You should go to the iPod thread.
iPod manager: https://hydrogenaud.io/index.php/topic,45160.4200.html
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.0 bugs

Reply #848 –
Quote from: Case on
PS: this thread is scarily titled foobar2000 v2.0 bugs. Everyone should be using the v2.1 previews as that is where all the recent developments and fixes have happened. The 2.0 "stable" is half a year behind on fixes.

Yes the latest 2.1 preview is actually more stable than the 2.0 "stable" release. I think Peter has specific issues in his backlog that he wants to fix before releasing 2.1

Re: foobar2000 v2.0 bugs

Reply #849 –
Quote from: LeVvE on
One thing I noticed with 2.0 is that the album list doesn't swap between light/dark font when text is highlighted based on how dark your background color is?

This is how it used to look: https://i.imgur.com/vTFDDkc.png
This is how it looks now: https://i.imgur.com/wElxea4.png

If I make the background any darker it's really hard to read the text in the album list because it's black instead of white, also when anything is clicked in the playlist the highlight color is removed and turns black so it's black on black and I can't read it at all.
Just installed the new 2.1 release, I really like the new radio interface stuff. Internet Radio looks the same as the playlist with correct? highlight and text color.

Internet radio white text on blue selection: https://i.imgur.com/ium2Oh8.png

Album list still shows weird colors with dark selection/highlight color and black instead of white text, the "box" around the text also has rounded edges compared to everywhere else: https://i.imgur.com/ePKIKZf.png

Thanks.