Skip to main content

Recent Posts

1
Some additional note:
I went to Windows 10 installation, because of Forza Horizon. Additionally I dug through foobar installation on that OS. I cleaned up components in similar manner as under Windows 7, with one exception  - I left there unconfigured foo_input_ffmpeg and I left there working foo_input_ds. I tested there a bunch of old, non remuxed Mvids awaiting for final removal.

Observations:
First of all - waveform seekbar works there very well (as it was usually, before I overloaded foobar with DLLs). All waveforms, for all supported video files are displayed and they don't disappear at any circumstances.
Then:
There are some files which are barely seekable (audio is reset to beginning upon any seek operation). But that changes when LAV Filters are re-installed from their separate installer (see below).
There are some files which incorrectly report their length, even after LAV reinstallation - they are cut by 20, 30, 45 seconds. What is specific: when all video files are played in foobar, in notification area I have just LAV Splitter and LAV Audio Decoder icons. But when some of these "broken" files come to its premature end - these icons start quickly appearing and disappearing with LAV Video Decoder showing up 2-3 times for an eye-blink. Waveform seekbar shows their waveform cut, accordingly to length reported on playlist, which is rather proper behavior.
That Westbam - Hard Times mvid reports proper length and is properly seekable, with proper waveform in seekbar displayed... So it is totally different to what is achieved through foo_input_ffmpeg as a data feed for foo_waveform_seekbar.

What I can say - both systems were installed at the same time, so I used the same KLCP installer on both, and used the same settings for installation. So I suppose this is KLCP installer that messes something in system (not the first one, but not all of them are such buggy). It may be also something with recent version of LAV filters, as in both cases (Win 7 & Win 10) installing just LAV Filters taken directly from their source doesn't change situation that much. I suspect it because afaik both KLCP installer and direct LAV installer install LAV in the same version, so that may suggest that it is this exact version of LAV to be blamed. Foo_input_ds relies on it and that's why there are some problems at least with certain files.
2
3rd Party Plugins - (fb2k) / Re: foo_wave_seekbar
Last post by EpicForever -
Some additional note:
I went to Windows 10 installation, because of Forza Horizon. Additionally I dug through foobar installation on that OS. I cleaned up components in similar manner as under Windows 7, with one exception  - I left there unconfigured foo_input_ffmpeg and I left there working foo_input_ds. I tested there a bunch of old Mvids not remuxed to .mkv , awaiting for final removal.

Observations:
First of all - waveform seekbar works there very well (as it was usually, before I overloaded foobar with DLLs). All waveforms, for all supported video files are displayed and they don't disappear at any circumstances.
Then:
There are some files which are barely seekable (audio is reset to beginning upon any seek operation). But that changes when LAV Filters are re-installed from their separate installer (see below).
There are some files which incorrectly report their length, even after LAV reinstallation - they are cut by 20, 30, 45 seconds. What is specific: when all video files are played in foobar, in notification area I have just LAV Splitter and LAV Audio Decoder icons. But when some of these "broken" files come to its premature end - these icons start quickly appearing and disappearing with LAV Video Decoder showing up 2-3 times for an eye-blink. Waveform seekbar shows their waveform cut, accordingly to length reported on playlist, which is rather proper behavior.
That Westbam - Hard Times mvid reports proper length and is properly seekable, with proper waveform in seekbar displayed... So it is totally different to what is achieved through foo_input_ffmpeg as a data feed for foo_waveform_seekbar.

What I can say - both systems were installed at the same time, so I used the same KLCP installer on both, and used the same settings for installation. So I suppose this is KLCP installer that messes something in system (not the first one, but not all of them are such buggy). It may be also something with recent version of LAV filters, as in both cases (Win 7 & Win 10) installing just LAV Filters taken directly from their source doesn't change situation that much. I suspect it because afaik both KLCP installer and direct LAV installer install LAV in the same version, so that may suggest that it is this exact version of LAV to be blamed.

What is important to note: seems that foo_waveform_seekbar is really reliable here and only wrong data feed causes it to work in an unusual way. However, as noted in my previous message - it would be OK if waveform parts that are successfully calculated were kept, and parts of file where waveform can not be calculated due to errors in data fed to seekbar component, were simply left blank. Instead of blanking full seekbar.
By the way - I got some idea / feature proposal. Maybe if for some reason for certain file waveform creation is completely impossible (CD Audio, infinite loop, .3gp file recorded with SE E15i, whatever else) there could be displayed simple text on the waveform seekbar:
"Waveform unavailabe". Or more detailed way: "Waveform unavailable (unsupported file or location)". Just a small thing to add, when there will be a bigger reason to release newer version :)
3
MP3 - General / Re: Lame 3.100 has been released
Last post by ajfoucault -
LAME development is culminated. Last quality changes were made 6 years ago.
In the other hand LAME developers have squeezed all out of what MP3 can do.

Thank You for release.

:) life continues ...


Couldn't have said it better...
4
3rd Party Plugins - (fb2k) / Re: foo_scrobble
Last post by gix -
OK, but it seems that foo_scrobble plugin requires that total tracked time is at least 100% length of the track. As far as I remember from my experiments foo_audioscrobbler was simply sending scrobble after half of this time was achieved. So I could listen to 20% of the song, then skip next 30% with seekbar AND on 80% of track length, track was scrobbled. And I could advance to next track at let's say - 82%. Still 50% was achieved (in 2 parts - 20% + 32% ) and everything was in accordance with the rules. In foo_scrobble, when I omit just 5% of the track - there is no scrobble. I haven't checked if I can search back and forth and scrobble is done if total listening time sums up to at least 100%. But it does not matter if scrobble should be sent after 50% (or after 4 minutes, whichever occurs first - as mentioned by marc2003).
As said earlier a track is submitted when the next one starts playing or playback is stopped even if the actual conditions are met earlier. This is no different than the other plugin.
5
3rd Party Plugins - (fb2k) / Re: foo_scrobble
Last post by EpicForever -
I've made some tests and... I think it is bit vague how this plugin works. It seems that I can not rewind track to make it scrobbled - looks like only track of which 100% of its length is listened is scrobbled, while 50% should be enough accordingly to L.fm rules, even if rewind was used - as long as total time was more than 50% of track.
I cannot reproduce that. It tracks the total time the track has been played, regardless of any seeks (Same as foo_audioscrobbler).

(...)

OK, but it seems that foo_scrobble plugin requires that total tracked time is at least 100% length of the track. As far as I remember from my experiments foo_audioscrobbler was simply sending scrobble after half of this time was achieved. So I could listen to 20% of the song, then skip next 30% with seekbar AND on 80% of track length, track was scrobbled. And I could advance to next track at let's say - 82%. Still 50% was achieved (in 2 parts - 20% + 32% ) and everything was in accordance with the rules. In foo_scrobble, when I omit just 5% of the track - there is no scrobble. I haven't checked if I can search back and forth and scrobble is done if total listening time sums up to at least 100%. But it does not matter if scrobble should be sent after 50% (or after 4 minutes, whichever occurs first - as mentioned by marc2003).
6
3rd Party Plugins - (fb2k) / Re: foo_scrobble
Last post by gix -
I've made some tests and... I think it is bit vague how this plugin works. It seems that I can not rewind track to make it scrobbled - looks like only track of which 100% of its length is listened is scrobbled, while 50% should be enough accordingly to L.fm rules, even if rewind was used - as long as total time was more than 50% of track.
I cannot reproduce that. It tracks the total time the track has been played, regardless of any seeks (Same as foo_audioscrobbler).

Plugin says that it scrobbles something (would be nice to have information which exactly track was send - its title - just to make it more clear) and it scrobbles everything, no matter if tags are present or not - and that was confusing for me and that's why I asked for adding special functionality. [...]
Yes I was unaware that people were using these field mappings that way.

I've added a new release that allows skipping tracks based on a titleformat script and adds a mainmenu command to toggle scrobbling.

7
3rd Party Plugins - (fb2k) / Re: foo_scrobble
Last post by EpicForever -
I've made some tests and... I think it is bit vague how this plugin works. It seems that I can not rewind track to make it scrobbled - looks like only track of which 100% of its length is listened is scrobbled, while 50% should be enough accordingly to L.fm rules, even if rewind was used - as long as total time was more than 50% of track.
Plugin says that it scrobbles something (would be nice to have information which exactly track was send - its title - just to make it more clear) and it scrobbles everything, no matter if tags are present or not - and that was confusing for me and that's why I asked for adding special functionality. Last.fm however filters tracks without title for example, so still expression
$if(%skip_lastfm%,,%title%)
put into "Field remappings - Title" causes that tracks with my special tag filled in are not visible in Last.fm . So let's say that requested functionality is de facto present in pipeline, but thanks to filtering applied on Last.fm servers, and not because it is implemented in plugin itself (plugin reports that it was scrobbled). But I suppose it shouldn't work like this. After changing it, it would be great if plugin was differentiating tracks that should not be scrobbled from others and if it was clearly printed in console ("Not scrobbling because: missing tile" or "Not scrobbling - insufficient legth" for example). Similarly to information about track being outside of ML.
8
General - (fb2k) / Library filter hotkey?
Last post by Maximko -
I use Default UI, and the most useful feature for me is the library filter where I can quickly find what I need. The only drawback is that I cannot find a shortcut to quick access that filter. Yes, I can assign the shortcut to Library / Album List which brings focus the Album List, but then I need to use Tab key to go further to the filter. I can also use Library / Search, but it doesn't work with the folder structure view. Could there be a direct solution I missed, or maybe a workaround using, e.g., AutoHotKey script?
9
How about splitting these files using converter (at least all lossless, so conversion will not change audio quality)?
10
3rd Party Plugins - (fb2k) / Re: foo_scrobble
Last post by marc2003 -
Just looking at the readme, you don't need to link to the 64bit C++ redist as foobar2000 and your component are only 32bit.