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 v1.1.11 beta (Read 26172 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

foobar2000 v1.1.11 beta

foobar2000 v1.1.11 beta 1 released. Main changes include new built-in crossfading functionality and easy installation of add-on components through new .fb2k-component file type.

Detailed changelog:
  • Improved built-in crossfading functionality, new fading configuration in Preferences / Output. (Fading functionality available with built-in DirectSound mode only.)
  • New .fb2k-component file type extension for foobar2000 component packages.
  • Fixed some potential security issues.
  • Added type-find in the default playlist
  • Added support for album art in APEv2 tags on MP3 files.
  • "Do not convert in multiple threads" custom encoder option in Converter.
  • Fixed more WAV handling bugs.

Hit up http://foobar2000.org for downloads, as always.

foobar2000 v1.1.11 beta

Reply #2 –
Peter mentioned it a couple weeks ago. Attempt to avoid situations where user in still in the old mindset of opening zip files and dragging .dll to foobar2000 while not noticing that a particular component [and the zip] contains and needs additional files.

Edit: http://www.hydrogenaudio.org/forums/index....st&p=780050

foobar2000 v1.1.11 beta

Reply #3 –
Components comprising multiple files will be bundled in an archive with that filename extension rather than .zip or whatever, and made openable by foobar2000 for their installation, in order to preclude users from only copying the DLL and thereby improperly installing the component and complaining when it does not work.

foobar2000 v1.1.11 beta

Reply #4 –
Does that also mean that you will be able to install a component by doubleclicking the package file?

foobar2000 v1.1.11 beta

Reply #5 –
I think that's the goal, q-stankovic.

Edit: However, the file extension does not yet show up in the shell integration dialog.
 

foobar2000 v1.1.11 beta

Reply #6 –
That indeed would be a great progress as it would be possible to install a component directly from the browser by just executing the file.

Will the packages from the official site be changed automatically or do each developer has to change that? And will it be possible to create .fb2k packages outside of that site?

foobar2000 v1.1.11 beta

Reply #7 –
...

foobar2000 v1.1.11 beta

Reply #8 –
Quote from: Canar on
Edit: However, the file extension does not yet show up in the shell integration dialog.

It doesn't and it won't because it is always associated. It is a foobar2000-specific file type, there's no reason to let other apps take it. Having to manually associate it though relevant preferences dialogs or control panels would defeat the simplicity.
Microsoft Windows: We can't script here, this is bat country.

foobar2000 v1.1.11 beta

Reply #10 –
Quote from: Peter on
It doesn't and it won't because it is always associated. It is a foobar2000-specific file type, there's no reason to let other apps take it. Having to manually associate it though relevant preferences dialogs or control panels would defeat the simplicity.
Mea culpa. That's genius. I'm an idiot.

foobar2000 v1.1.11 beta

Reply #11 –
1.1.11b1 cannot embed/delete cover art form MP3 files: it complains "File is already in use". And it works with FLAC/OGG files.

Added: and converting from ID3v2.3 to APEv2 removes cover art.

foobar2000 v1.1.11 beta

Reply #12 –
Quote from: lvqcl on
1.1.11b1 cannot embed/delete cover art form MP3 files: it complains "File is already in use". And it works with FLAC/OGG files.

Fixed, thanks for reporting. The 1.1.11b1 installer has been updated with this fix.
Microsoft Windows: We can't script here, this is bat country.

foobar2000 v1.1.11 beta

Reply #13 –
Bug or not, I am not sure – I don't have old fb2k's to tell if these ever worked in earlier versions, or if it has ever been the intention that they should work, but since the 1.10 had issues with WAV files, I played around with some oddballs from http://www.esa.int/esaSC/SEMLAJWO4HD_index_0.html . There are four .wav files there, all containing PCM with odd samplerates (27400 and 5513 Hz), but all verify as OK using foo_verifier.

For the 27400 Hz files – http://esamultimedia.esa.int/images/spcs/s...wn_in_space.wav and http://esamultimedia.esa.int/images/spcs/s...l_star_wars.wav – they fail to convert to FLAC. The «copy» ends up having a different number of samples. They do sound the same, though.
On the other hand, converting with dBpoweramp Music Converter (which uses the FLAC DLL) gives a copy bit-identical to the original.


(I think an option to verify against original after copying, would be a good idea. For lossless target format, of course.)

foobar2000 v1.1.11 beta

Reply #14 –
Quote
Improved built-in crossfading functionality, new fading configuration in Preferences / Output. (Fading functionality available with built-in DirectSound mode only.)


Is there any chance it could work with wasapi or asio in the future?

foobar2000 v1.1.11 beta

Reply #15 –
Quote
Improved built-in crossfading functionality, new fading configuration in Preferences / Output. (Fading functionality available with built-in DirectSound mode only.)
Why not make all the DSP Manager functions built-in?
Why is the limit 10s, and why must the buffer be greater?  (is this different than the DSP Manager crossfader behavior?)

PS: there seems to be something up with displaying some embedded album art.
screen: http://i.imgur.com/aAg0T.jpg (mp3tag and windows explorer display the album art just fine)

foobar2000 v1.1.11 beta

Reply #16 –
Quote from: MaCs on
Quote
Improved built-in crossfading functionality, new fading configuration in Preferences / Output. (Fading functionality available with built-in DirectSound mode only.)


Is there any chance it could work with wasapi or asio in the future?

Nope. It's feature of the directSound API.
elevatorladylevitateme

foobar2000 v1.1.11 beta

Reply #17 –
Native fading works with DirectSound only because it relies on playing multiple streams simultaneously, something the other output modes are explicitly incapable of on most systems. Note that native fading can do things that the DSPs cannot (crossfade on manual track change).

MP3/ID3v2 cover art not working on files with ID3v2 + APEv2 - acknowledged, fixing.
MP3 cover art lost on tag type change - acknowledged, fixing.
Problematic WAV files - thanks for the report, looks like it's some kind of a FLAC-specific problem, we can convert these to WavPack etc just fine, investigating.
Microsoft Windows: We can't script here, this is bat country.

foobar2000 v1.1.11 beta

Reply #18 –
Porcus, your issue seems to be a bug in FLAC encoder's wav handling. The fix for 2GB issue I posted here also fixes this problem.

foobar2000 v1.1.11 beta

Reply #19 –
Quote from: Peter on
Native fading works with DirectSound only because it relies on playing multiple streams simultaneously, something the other output modes are explicitly incapable of on most systems. Note that native fading can do things that the DSPs cannot (crossfade on manual track change).


Why is there apparently such a tight coupling between "audio stream" and "file"? Shouldn't you be able to just read whatever, decode whatever and toss it all in a single box and send that to into the audio pipeline?

I've never written any audio or hardware I/O code before (unless you count mass-file creation via WSH  ), so it may be a simpleton question.

foobar2000 v1.1.11 beta

Reply #20 –
Quote from: dhromed on
Why is there apparently such a tight coupling between "audio stream" and "file"? Shouldn't you be able to just read whatever, decode whatever and toss it all in a single box and send that to into the audio pipeline?

If you apply fading before passing data to the audio pipeline, you need v.low output latency to nicely respond to user events such as seeking or manual track changes, which is undesirable - means you get audio glitching from hard drive lag etc.
Microsoft Windows: We can't script here, this is bat country.

foobar2000 v1.1.11 beta

Reply #21 –
It would be a convenient and somehow nearby feature to have the fade slider placeable in a toolbar of a dui-layout. Actually it would be amazing!

foobar2000 v1.1.11 beta

Reply #22 –
Quote from: q-stankovic on
Does that also mean that you will be able to install a component by doubleclicking the package file?

And: Does that include restarting foobar in order to replace an in-use component?

foobar2000 v1.1.11 beta

Reply #24 –
Thank you so much for the crossfading on manual track change.
I was waiting 2 years for this.

At least 10 seconds is to less.

Would it be possible to make more ? 15 or even 20 seconds ?
Warning: fb2k is addictive.