Skip to main content
Recent Posts
General - (fb2k) / [solved] "Track selection count" status bar tag/option?
Last post by Faziri -
I see the following in the changelog for 1.4

Improved status bar: added optional display of selected track count.

I'm using 1.4beta20 and can't find anything about this. It's not in the settings panel as far as I can see, I can't find anything in the title formatting webpage nor the bundled syntax help manual.

A pointer, please?
3rd Party Plugins - (fb2k) / Re: Waveform Minibar (mod)
Last post by no9 -
Thank you @Case. Now when it is halted the progress display disappears together with waveform. Great thing about Waveform Minibar is that whether it renders waveform or not for me it is still better seekbar than the default one. Ability to halt rendering is great when working on battery and in some other cases. Really handy now.
3rd Party Plugins - (fb2k) / Re: foo_skip: skip tracks that match a specified search query
Last post by Case -
There are no generic compatibility problems between foo_skip and the latest foobar2000 version. Only thing one could count as incompatibility is the lack of support for reading metadata from tag fields marked as spam in LargeFieldsConfig.txt. If you were to add "fieldSpam=skip" to the said config file, the component would see the field as containing nothing else than a dot.

I can't replicate the problem you describe. I added to the playlist with foo_youtube and added SKIP tag -00:00:33;00:02:00-. Double clicking the track starts playback from 33 second marker. The track is shorter than 20 minutes so I altered the end skip to two minutes instead. At around that time the playback jumps to the next track.

I also don't know why the field's contents aren't visible for you on the playlist. I tested that too and there are no problems seeing the metadata from foo_youtube entry.
Support - (fb2k) / DLNA
Last post by abax2000 -
I am trying to connect from my w10 laptop (while using foobar) to wifi soundbar (Samsung MS750).
Tried to install and use both foo_out_upnp and foo_upnp, with no success.

Although soundbar got visible in Foobar's output drop-down list, no sound is coming out.
Usual error is "time-out".
I had a success only once for 10 mins, with foo_out_upnp; as soon as I tried to change something in settings, sound was lost (although I reverted the setting to original value).

Can anyone network-knowledgeable please provide some advice?
Opus / Re: Opus 1.3-rc
Last post by dwalkerdon -
Sorry if this is a noob question, but would this update be worth replacing my current library of opus 1.3 beta encoded at 160kbps? Thanks in advance.

Like Deathcrow already said, it would be almost certainly a waste of time simply because @ 160kbps the wiki page says, 160-192kbps = "Transparent with very low chance of artifacts (a few killer samples still detectable)." ; so when your already borderline perfection, it's not really possible for v1.3 to improve on that to any real degree even though I guess technically if it fixed those rare killer samples, that would be a improvement but at this point you would be nitpicking for sure.

basically with v1.3 it seems the sound quality improvements are mainly at bit rates of around 48kbps and lower from what I have read around here. but on the higher bit rates (say about 96kbps+) I would expect to see very little if anything since they are already high quality on the current release of v1.2.1 as 96kbps shows 'approaching transparency' on the wiki page for Opus which means even that bit rate already offers quality sound. you can't really go wrong with 96kbps/128kbps/160kbps.

or let me bottom line Opus... I think I can say that the vast majority of people who have a concern for sound quality will use a bit rate of between 96-160kbps (maybe 192kbps for the somewhat paranoid types) as while you can go lower than 96kbps you start to gamble a bit on sound quality even though at the lower rates the sound quality is quite respectable given the bit rates, like... 32kbps/48kbps/64kbps etc. but any higher than 160-192kbps is pretty much a waste of storage space given the info in the Opus wiki page.

I find that Opus 1.2.1  at 128 kbps for 5.1 audio tracks, and 64 kbps for stereo tracks sound pretty transparent to the source. The main problem with 48 kbps is that it suffers from artifacts in violins and string based music.
Audio Hardware / Re: Active Digital Monitor - Onboard Chip/Extern
Last post by Supersu -
Thank you for the detailled answer.

Currently I use a RME HSDPE AIO:
You think a card like this uses the same chips like a onboard soundcard? ;-)

I plan to have a new smaller system (mITX) where I would use onboard chips.
But now I'm happy to hear that for the basic music playback with digital transmission, there's nothing to worry about.
3rd Party Plugins - (fb2k) / Re: foo_skip: skip tracks that match a specified search query
Last post by Wolfbane -
Im not sure if the plugin is broken or foobar version Im using is not compatible. But it does not seem to work anymore.

Using "foobar2000 v1.4 beta 20" and "YouTube Source 2.3.2"

Not working is the info below, that used to work.
SKIP -00:00:33;00:20:00-

Here is a screenshot of the plugins and the properties of the file, if u need to check if I did something wrong.

And one more question...
I tried to display/add "Columns" "SKIP" to try and display what songs have the settings enabled on them.
But seems to display blank on all. Any clue what I did wrong on that part?
Audio Hardware / Re: Active Digital Monitor - Onboard Chip/Extern
Last post by polemon -
So this is it ?
Well, WASAPI will simply forward the decoded PCM stream. You cannot really send encoded FLAC through S/PDIF. Your monitor will simply see a 44.1hHz, 16bit/sample, 2ch PCM stream.

So there's nothing to worry about using a cheap china onboard souncard.
Tbh., your expensive, dedicated, external, USB-3.1 sound card, with superb ASIO drivers, is also quite possibly made of the same "cheap" Chinese electronics, except it gets a bit more quality control.

As I said before, there is no DAC/ADC action going on, until the signal reaches your monitor. There's digital signals only get modulated for whatever transmission medium they use.

If you were to need a higher margin, as we've discussed here, i.e. higher sample rate, greater bit depth, more channels, that what the limitations of your internal S/PDIF interface are, only then I'd opt to get a new, external interface.
SimplePortal 1.0.0 RC1 © 2008-2018