1
Lossless / Other Codecs / Re: Reasonable handling of non-compliant source files in lossless audio compressors
Last post by MonkeysAudio -If anyone finds an exception to this, please provide a sample and I'll fix it.
Thanks.
There is no mention of it in the docs so I assume it's not currently possible, but it would be neat if one could use SQL query syntax to generate titles for target playlists.Although not explicetly, it acutally is:
Inserting entries into the Playlist table will result in adding items to the relevant playlists.
...
If the specified playlist doesn't exist, it will be created.
INSERT INTO PlaylistUpdatable(path,playlist_name)will create the playlist "New Playlist" with one empty, invalid track. For sure it would be better to populate this playlist with existing tracks, e.g.
SELECT '','New Playlist';
INSERT INTO PlaylistUpdatable(path,subsong,playlist_name)assuming that there are tracks from Motörhead in your library.
SELECT path,subsong,'Motörhead'
FROM MediaLibrary
WHERE artist='Motörhead'
It would be amazing if there was some way to use SQLite to generate autoplaylists. Is there a chance for something like this in the futureThere is absolutely no chance. This is technically not possible.
Hello pqyt
I have detected an anomaly in the latest version. If you enable Leds in Peak Meter mode (Image1) and mark Left and Right (Image2) it does it correctly, but if you disable Left and Right (Image3) only the Left channel is displayed. In the previous version it did it correctly.
But the Peaks seem OK to me (by eye), those also seemed OK from the beginning. Only two or three version from a few days ago seemed wrong and now it seems OK again with music (and weird with this one test file but only with +3 which should not change peaks as it is supposed to recalibrate RMS only).See the screenshots from the quick hack above. I never expected this to be more difficult than the curve representation of the spectrum...
I again propose to implement text peak values as it would make the comparison with other meters easier. Other meter usually show the max value of the track up to the present point (the highest value reached from the beginning of the track to "now") and not the actual momentary value.
OK. I fold. ;-)As for RMS - I just made a live comparison of readings while playing a track and it was like that:@wojak, would you please download one of the test files from https://www.soundonsound.com/techniques/sos-audio-test-files, preferably one with a dBFS number on the file name (e.g. 1_mono tone 1kHz -20dBFS 44k.wav or 19_Pink Noise stereo 20Hz_20kHz -23dBFS 44k.wav) and let us know what readings you get with other plugins?
- your component with +3 disabled showed the same values as VST TT Dynamic Range Meter and the same as VST dpMeter5 and the same as VST Span (that one with DBFS+3 set). If I changed Span to DBFS (without +3) it showed 3 more than all the others (inluding yours which was with +3 disabled). So it seems (again judging by eye) that your RMS set to 0 shows what other show and when set to +3 it shows different values than others.
So to me (as an amateur) it seems that Peaks now are OK and RMS might be too high by 3. Or in other word: to make all those 4 meters show the same values I have to set yours to 0 (+3 disabled) and Span to DBFS+3. Other two do not have those options to change but show the same values.
1_mono tone 1kHz -20dBFS 44k.wav:
- your component at 0: 20/20 (RMS/PEAK)
- your component at +3: 17/17
- vst TT Dynamic Range Meter: 20/20
- Span at DBFS: 23/20
- Span at DBFS+3: 20/20
- dpMeter: 23/20
- youlean loudness meter: 23/20
So it seems that RMS should be as @Case said - lower by 3 (or third option: -3).
Peak seem OK but one strange thing that your component also shows 17 as peak when +3 while all others show 20 no matter if +3 or not.