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
2
3rd Party Plugins - (fb2k) / Re: foo_uie_lyrics3
Last post by tigershark -
Here's the code I'm using:

$if($or($strstr(%path%,'soundtracks_video_games'),$stricmp(%genre%,instrumental),$strstr(%comment%,'do_not_run_lsp')),1,0)

I have folders titled "soundtracks_video_games" and "soundtracks_tv_and_film". None of the songs in "soundtracks_video_games" have lyrics. Since some of the songs in "soundtracks_tv_and_film" have lyrics, I've updated the genre tags of the instrumental songs to "instrumental". There are also some non-instrumental songs in other folders that don't have lyrics, so I've added "do_not_run_lsp" to the comment tags of those songs.

On my installation of Foobar and LSP, the above code works for songs in "soundtracks_video_games" and songs with "do_not_run_lsp" in the comment tags, but it does not work for songs with the genre "instrumental".

Also, the following code doesn't work the first time LSP is run after starting Foobar but works on subsequent runs:

$if($strstr(%path%,'soundtracks_video_games'),1,0)

$if($strstr(%comment%,'do_not_run_lsp'),1,0)
3
General - (fb2k) / Re: Compare two libraries' tagsets (... and overwrite)?
Last post by regor -
If you download the latest files from this repository (not the lastest release), you will find a button named '.\buttons\buttons_save_tags.js'. That should do exactly what I described (it's in a rought state  since I simply mixed things I got here and there from my other tools to show a prototype).
https://github.com/regorxxx/Playlist-Tools-SMP

Tags are saved to .\AppData\Roaming\foobar2000\js_data\tags.json.
Function applies to current selection (so send entire library to a playlist first).
1. edit '.\main\save_tags.js' and change compareTags function with 'selItemsFolder' pointing to the root of your current library and 'toTagsFolder' pointing to the root of the library backup. For ex. I have my music at H:\Music\.... so  toTagsFolder= 'H:\\Music\\'. My backup is at J:\Backup\Music\... so selItemsFolder = 'J:\\Backup\\Music\\'. Tracks will be compared by path then and that part will be stripped, so the rest of the string should match. (*)
2. Load buttons on a SMP foobar panel.
3. Save tags of entire library selected on a playlist.
4. Load all backup tracks on another playlist and select them
5. Click on compare tags. Popups will appear, etc. and done. If there are tracks on Backup not found on current library (you changed paths at a later stage for ex.), a popup will appear listing them too.

(*) You could do some fancy matching here as prev. discussed. Like trying for audiomd5 first, and then path and subsong if no match found with the first check (mp3 for ex. don't have an audiomd5 tag). That way some files may have different paths but still be matched without collisions (and that's what I did with the Playlist Revive tool).
4
Off-Topic / Re: Some computer problems...
Last post by kode54 -
650 watts is more than enough for the parts you've listed. Something else is cursed and/or haunted, or in other words, some one or more defective components. Probably not the CPU. Maybe do a RAM test with memtest86 live media?
5
3rd Party Plugins - (fb2k) / Re: Foo_osd
Last post by kode54 -
Not with the SDK available. Predicting the next track is outside the scope of the SDK, and requires hard coding behavior of every linear/predictable track order mode, and ignoring the shuffle modes.
7
CD Hardware/Software / Re: tools for maintaining existing cue/audio file collection
Last post by brainchild -
I am not understanding the question about "working properly". I would characterize the data that has been taken from the original media as accurate. The audio was extracted through secure reading procedures, along with data for the cue sheets. The audio files decompress and play correctly. The indexing data matches against public databases, except for media of limited distribution, as expected. The features that are messy are the structure of the file tree, including organization and names of files and directories, as well and tagging metadata. Largely, the data from the original media is faithfully copied, but the further data, which may be obtained through queries to metadata services, needs to be updated.

For the record, I have had success running CUETools under Mono in Linux. Some features of the interface, such as display and path conventions, are a bit inconvenient due to cross-platform issues, but so far I have been able to run the different kinds of operations with results as intended by for application features.

Note the success under Mono is limited to the CUETools application specifically, and not the bundled CUERipper.
9
General Audio / Re: Vorbis better than opus?
Last post by Markuza97 -
I can hear frequencies above 20KHz, confirmed by ABX, with and without 20KHz lowpass.

This guy is smoking some good shit, lol.
Anyway, nobody is using Vorbis anymore. It is dead format.

If you want compatiblity and good all-around format stick with MP3.
Use latest LAME encoder and use V2 preset. You will get ~192 kbit/s files that work everywhere and sound great.

If your equipment has been made in the past ~15 years you can use AAC-LC.
Recommended encoder is Apple (qaac). Ideal bitrate is around 144-160 kbit/s.

Third "relevant" format acording to HydrogenAudio is Opus. This is totally false in real life.
Even today, many programs have problems with playing Opus files. It is really only useful for VoIP applications.
I can guarantee you that every single person on HA that is using Opus is very familiar with compatibility
problem but they also have lossless archive so they can encode to any format that they want.

Main point of lossy files is transparency at smallest bitrate. Lossy codecs achieve this at 192 kbit/s.
Everything about 192 kbit/s kills the point of lossy files.
SimplePortal 1.0.0 RC1 © 2008-2021