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.
Recent Posts
41
General - (fb2k) / Re: Title formatting/syntax for proper bitdepth
Last post by wojak -
Yes, you are right. Since you have released "foo output" I started to experiment with mainly sacd options and must have left it with max. available PCM output. The crashes have gone now. All DSD files show 64 float now. All lossy show 32 float.
As for "?" in place of clips....some of those test files had old verions of "true peak scanner clipped samples" (without "track") so those were getting 3 fields "clipped sample", "clipped samples track" and "clipped samples album" now. After manual delete all seems ok now.
Thank you very much.

Edit: One new strange thing. While playing .m2ts I get:
- 24 fot pcm;
- 32 for TrueHD and DTSHDMA - why if those two are lossless and 24;
- empty for AC3 - while AC3 from .ac3 file gets 32 float.
Edit2: I think those above come from ffmpeg input not from TBS but still they are strange.
42
3rd Party Plugins - (fb2k) / Re: JScript Panel
Last post by JesalRo -
Hi Mark
I am saddened by the decision you have taken, there are many users who have enjoyed and benefited from your great work and having a custom Foobar with your components. I hope you can reconsider your decision and continue again.
Anyway whatever decision you make, thank you very much.
44
3rd Party Plugins - (fb2k) / Re: JScript Panel
Last post by josemescud -
Message to Marc2k3:

I am deeply sorry that you have been forced to close the maintenance of your component.
I have 50% of my interface based on it. So I was very concerned about your decision.
I would love you to seriously rethink a return and continue to provide us with your great work.
However whatever you decide I thank you for all your work that many users have enjoyed.
45
3rd Party Plugins - (fb2k) / Re: foo_uie_webview
Last post by pqyt -
foo_uie_webview v0.2.0.0-alpha5

* Changed:
  * Callbacks
    * onPlaylistItemsAdded(playlistIndex, startindex, locations): Called when items have been added to the specified playlist. (alpha5)
    * onPlaylistItemsReordered(playlistIndex, items): Called when the items of the specified playlist have been reordered. (alpha5)
    * onPlaylistItemsRemoving(playlistIndex, removedItems, newCount): Called when removing items of the specified playlist. (alpha5)
    * onPlaylistItemsRemoved(playlistIndex, removedItems, newCount): Called when items of the specified playlist have been removed. (alpha5)
    * onPlaylistItemsModified(playlistIndex, items): Called when some playlist items of the specified playlist have been modified. (alpha5)
    * onPlaylistItemsModifiedFromPlayback(playlistIndex, items): Called when some playlist items of the specified playlist have been modified from playback. (alpha5)
    * onPlaylistItemsReplaced(playlistIndex, items): Called when items of the specified playlist have been replaced. (alpha5)

    * onPlaylistSelectedItemsChanged(playlistIndex, selectedItems): Called when the selected items of the specified playlist have been changed. (alpha5)

    * onPlaylistsReordered(playlistOrder): Called when the playlists have been reordered. (alpha5)
    * onPlaylistsRemoving(removedPlaylists, newCount): Called when playlists are being removed. (alpha5)
    * onPlaylistsRemoved(removedPlaylists, newCount): Called when playlists have been removed. (alpha5)

  * Changed: *Breaking Change* Callbacks follow the Category-Noun-Verb naming convention. (alpha5)
  * Changed: *Breaking Change* All properties, methods and callbacks to use camelCase convention. (alpha5)
  * Changed: *Breaking Change* The parameter list of most callbacks has been expanded. (alpha5)

You can download it only from GitHub during testing.
46
General - (fb2k) / Re: Title formatting/syntax for proper bitdepth
Last post by Case -
Thanks for submitting crashes. That DSD file crashing did not start with this version, I suspect you had used lower PCM samplerate with foo_input_sacd in the past. The libebur128 library I use for loudness scanning had a bug triggered by these insanely high sample rates and it attempted to access memory beyond what it had allocated.
Uploaded a new preview version with that issue fixed: https://foobar.hyv.fi/foo_truepeak_preview.fb2k-component.
This version also includes 64-bit floating point output detection when run on foobar2000 x64.
If you have strange metadata behavior you could check the file properties to see what's in there. Perhaps your file had for whatever reason multiple fields with the same name, or your display script reads data from multiple fields.
47
3rd Party Plugins - (fb2k) / Re: Routing data flows to Foobar via VB Cable (Windows 10)
Last post by slowpork -
I just tested Qobuz w/ VB cable and it routes fine with record://  on my pc.  It seems you have all steps correctly, I would double check

1. Control panel / Sound / Playback tab / Cable input should show ready status, and when you select it as default, it should have green volume bar moving up and down when Qobuz plays some music.
2. Control panel / Sound / Playback tab / Cable output should show ready status , and the green volume bar will move up and down when Qobuz plays some music , same as #1 and this output signal will go to   Foobar->Preferences->Tools->Recorder, the entry in the Device field is CABLE Output
3. I'm using portable foobar 2000 v2.1.5 (x86) 32bit w/ foo_record component v0.23  with VB-Cable driver pack 45.     Probably you may install another foobar in portable mode and try again? 

if all above still give you the unknown error, may you try uninstall / reboot / reinstall VB-cable or if you may try on another PC ?  I think may be some glitches about driver or something. 
49
CD Hardware/Software / Re: Another HDCD thread...
Last post by krabapple -
Quote from: Replica9000 on

I wanted to see a visual of what the different is between the original audio and the audio after decoding with the HDCD filter.  The filter lowers the gain by -6dBFS, and outputs to 24-bit WAV.  I used ffmpeg to apply the filter, and to draw the waveforms.  The waveforms are the original audio (orange, lowered by 6dBFS) over the decoded waveform (light orange).

This is the track "Blue Monday" that does use Peak Extend.



This visual seems odd to me.  Of the HDCDs I own, a subset* use 'peak extend'.  On those, the undecoded waveform looks slammed, in a loudness wars fashion -- multiple peaks at 0dbFS.  The decoded version has a more dynamic, 'audiophile'-like waveform, just one or few peaks at 0dBFS.  Visually, the waveform difference is striking.

If I interpret Replica9000s visual correctly, the light (decoded) version shows many, many peaks at maximum level, while the dark orange (undecoded) does not.  This looks exactly backwards to me.

Could be I'm reading this wrong.  Showing it as light orange/dark orange overlaid doesn't help, It's not easy for me to tell them apart.  Separate waveforms for decoded/nondecoded might be more clarifying.


* for the rest, all decoding does is lower the level by ~6dB.  The waveforms are otherwise identical.