ut I guess I can either use 'loudgain'
> (https://github.com/Moonbase59/loudgain) as suggested by MainSqueeze, or
> just subtract 6.00 from all the existing RGs which presumably amounts to
> the same thing and my CPU will thank me!
For standards compliance and compatibility I'
slartibartfast wrote:
> If LMS cannot apply the required replaygain value because the peak of
> the waveform is already full scale then turning off replaygain won't
> make any difference.
>
True. Luckily, I don't have any classical music that's mastered like
that. The Schoenberg "track" that I
LMS's clipping prevention considers two factors: the track peak and the
amount of positive gain calcuated by ReplayGain. If those two add up to
more than 0dBFS (or 1.0 on the ReplayGain scale), then LMS limits the
gain to keep below that threshold.
LMS's clipping prevention doesn't consider any a
Well, the short version is: I can extend gormans custom-convert to
apply equalizer settings to remote streams as well, but in doing so Im
losing the ability to seek within individual streams. The long version
follows:
My test case is a Bandcamp URL:
Code:
https://
gorman wrote:
> Hi! Did you survive the pub? Waiting for new debug lines :-)
Easy, Buster. I've got a few other things on, too, you know. ;)
Anyway, I've already discovered that not all remote streams are in fact
remote. Plugins apparently are "streamMode: I" rather than "R", even
though they
gorman wrote:
>
> As for your question above, with the player.source debug log active, try
> to play an mp3 stream of your choice and post the tokenized command
> here. From there we can work it out, I hope.
Great. Sounds like a plan. What I'd like to do is see how far we can
take custom-conve
gorman was so right when he said, in post 20 above:
gorman wrote:
>
> Convert.conf still is some sort of black magic stuff under many
> aspects... it's good to have clarifications on the forums, when
> possible. For future reference.
Black magic indeed. Each little bit you learn only gives yo
One more question, if I may, to add to my little custom-convert
documentation project: the default convert.conf file lists only three
"current" device types: slimp3, squeezebox and * (for all types). Do you
know how one might specify more recent models, e.g. Boom and Touch? What
are their device
I swear I searched that manual on Sourceforge several times for "-C". It
turns out the manual uses en dashes rather than just ordinary
hyphens...
Still, now that I've recovered from the embarrassment: if "-C" specifies
the compression rate, in this case for output to FLAC, then it should be
safe
I've now updated my custom-convert file, checked the server logs once
more, and it's all good. No more "rejecting" this line or that, just
"found command" and "matched", and the tokenized command on seeking
within a track now reads:
Code:
Tokenized command: "/usr/sha
bpa wrote:
>
> Now you need to wonder - did you ever notice the lack of equalisation
> :-)
Ha. I had a feeling you might say that. ;)
The equalization only takes care of four bass peaks that acoustic
treatment (which, besides several Squeezeboxes, was my best "HiFi
component" ever) couldn't q
Thank you!
So just to make sure I've understood:
The missing "capability T" is precisely the ability to "seek to a start
time offset" that's defined in convert.conf, I suppose. The one I
thought I could do without. ;)
When LMS comes across a command that lacks a required capability (e.g.
my s
I've attached the log; I hope you can make more sense of it than I can.
Worryingly, there are several instances of this:
Code:
[20-07-03 17:15:44.3276] Slim::Player::TranscodingHelper::checkBin (252)
Found command: [sox] -q -t flac $FILE$ -b 24 -t flac - equalizer
bpa wrote:
>
> Can you do a player.source log set to DEBUG when you use WebUI to jump
> to a mid way point in a track.
Will do but it'll be a couple hours or so before I'll get round to it,
I'm afraid. Which log set should I choose from the dropdown at the top
of the logging page? Or is choosi
Just to confirm, I can both skip tracks (i.e. go to the next/previous
track) and navigate to specific points in individual tracks (what in
analogue days, we might have called RWD and FWD).
I'm controlling playback via the web UI (mostly), iPeng (sometimes) and
the touch interface of a Squeezebox
gorman wrote:
>
> Can you skip with that line?
Yes, I can skip (i.e. go to the next/previous track) as well as go to
particular points in individual tracks using a Squeezebox Touch, the web
UI (with Material Skin) or iPeng.
Then again, I'm running LMS on Debian and using the Squeezelite versi
gorman wrote:
> Ok, found solution for MP3s as well. Since I have music only in flac and
> mp3 my solution is complete.
>
> >
Code:
> >
> mp3 flc * bc:5f:f4:bf:3e:70
> # FT:{START=-ss %t}
> [ffmpeg] -loglevel quiet $START$ -i $FILE$ -f wav - | [sox] -D -q
Well, here we are, still installing plugins a good two years after
preparing for Armageddon. :)
Because who'd want to sit through the apocalypse without Wagner in
high-res FLAC piped to [sox] -G bass +11...
MainSqueeze's
18 matches
Mail list logo
