mherger wrote:
LMS (7.9) has a habit of rescanning items if it sees they have
changed.
This behaviour should not have changed in 7.9 compared to 7.8. How is
this being triggered? Does it discover those changes automatically (then
disable auto scan)? Or when you BMF to a changed file?
ralphy wrote:
I've build an OSX 10.4+ i386 squeezelite 1.6.5 on a 10.6 system for you
to try.
You'll find squeezelite-1.6.5.499-osx-i386.tar.gz on mediafire in the
squeezelite/osx folder.
You can also follow the i386 readme to install and run it at startup.
Hopefully it works on
Thanks tcutting phred for clearing up the variable names and
references. Totally agree that getting custom clock skins to look good
is a matter of lots of trial and error! I've been using the same one for
years but all this activity has me motivated to update and improve it.
Thanks again.
-
tcutting wrote:
That is strange. I am looking at my Touch right now, and it's 8:34PM and
showing a night icon.
You could try changing the logging for SuperDateTime to debug - I added
a lot of debug logging so I could make sure it's doing what I expect.
Could you possibly be pointing to a
Great tutorial, thanks!
A heads up for people who might place squeezelite in a directory with
spaces in its name. In the .bat file you need to use quotes, like this:
C:\Program Files (x86)\SqueezeLite\squeezelite-win.exe -n
WhateverYouWantAsAName -s xxx.xxx.xxx.xxx
phred wrote:
First of all, that's a really nice touch changing the logic to read the
time from the query rather than local. It enabled me to test the night
icons here in the daytime by entering a weather code for Hawaii. And
with v 5.10.5, I do not get them. I stop LMS and exit from it.
phred wrote:
...
I also noticed that the Display String Abbreviations are missing on the
SDT set-up page:...
Here is my latest strings.txt, also with german translations. If you
change it (and/or other files) against an older one you must stop LMS
before and then replace it. A complete
I ran that C code now to try to determine the capabilities of my card.
First, I put the ALSA driver in as the argument, compiled and ran the
code, and then put in my Wolfson card as an argument (listed by aplay as
sndrpiwsp) and ran it again. Below are the results:
16982
Even though the program
tcutting wrote:
Try replacing the strings.txt file from the previous version. I will be
out of town for a couple of days and won't be able to help much.
I know you're out of town for a bit, but I wanted to update the issue.
Replacing the 5.10.5 strings.txt with that from 5.10.4 gives me
This is a standard alsa program and it interacts with ALSA API. Since
you didn't supply a device on the command line it is testing the default
device hw:0,0
As far as Alsa is concerned hw:0,0 is a playback device.
why don't you show what arecord -l returns and the supply the wolfoson
input
As far as I can see here, it lists the recording device the same way as
the playback device:
16983
I'm not sure how I would specify the recording device in that C code.
Thanks,
Michael
+---+
|Filename: arecord -l result.png
tcutting wrote:
Try replacing the strings.txt file from the previous version. I will be
out of town for a couple of days and won't be able to help much.
I know you're out of town for a bit, but I wanted to update the issue.
Replacing the 5.10.5 strings.txt with that from 5.10.4 doesn't
gorman wrote:
Great tutorial, thanks!
Seconded
Now I need a tutorial for the uninstallplease:confused:
atb
Ronnie.
Man in a van's Profile: http://forums.slimdevices.com/member.php?userid=43627
View
Have you set up the wolfson card for line in audio record ? The
following is from the driver software
Code:
#!/bin/bash
#Record from onboard Line Input to AP
# +9dB input PGA gain
amixer -Dhw:0 cset name='IN3L Volume' 8
amixer -Dhw:0 cset name='IN3R
I used a preconfigured script which came with the Wolfson setup package.
I'll reset that and give yours a try and let you know in a few minutes.
Michael
mike_b16's Profile:
I don't have this card so I don't know anything about it - all I am
doing is looking though its code.
This card is supposed to be able play back and also record auio in
analog and digital yet iot only has one ALSA device hw:0,0. From point
point of ignorance - thismeans card is setup in some
I ran the script you gave me to enable recording from the line in. I was
able to record a file at 16/44.1 and play it back over the LMS to one of
my players. Recording at 32/44.1 wouldn't playback at all over LMS, and
I haven't configured the ALSA mixer for local playback.
I put the squeezeplug
erland wrote:
I'm very interested to hear how you have configured it and what kind of
problems you had and what the solution was, this will be great input for
future versions which hopefully can make the plugins easier to use for
other people in the future.
Hello Erland,
I have been really
mike_b16 wrote:
I ran the script you gave me to enable recording from the line in. I was
able to record a file at 16/44.1 and play it back over the LMS to one of
my players. Recording at 32/44.1 wouldn't playback at all over LMS, and
I haven't configured the ALSA mixer for local playback.
Apologies. Do you just want the scripts that configure ALSA or the files
with the kernels and such?
mike_b16's Profile: http://forums.slimdevices.com/member.php?userid=63606
View this thread:
mike_b16 wrote:
Apologies. Do you just want the scripts that configure ALSA or the files
with the kernels and such?
Just the ALSA scripts to start with. I don't know what the kernel
scripts are - what do they do - are they custom building the kernel or
modifying values in /proc or
I didn't know how to untar files in Windows and wanted to post this
quickly, so I took a screenshot of each code (they're all less than one
page). Here is Reset_paths.sh (used to reset the AlsaMixer to output
nothing as far as I understand):
16986
This is Record_from_lineIn.sh, which I
In future can you post text and not screen pictures - with text file
compares can be performed - with bit maps it is a visual check which is
never good as hidden chars can't be seen.
Install 7-Zip on Windows it can unpack most formats.
What is the sequence you do when running your record
Is there no option to tell LMS never to rescan unless I explicitly ask
it to? This is quite important for custom scan users.
And Erland, apologies for not noticing some earlier responses from you.
I've no idea why I missed them. My main question is whether there is
some reason why the
In future can you post text and not screen pictures - with text file
compares can be performed - with bit maps it is a visual check which is
never good as hidden chars can't be seen.
Will do!
What is the sequence you do when running your record tests.
With these arecord-to-flac tests I
To get hw_param on record okease
1. run the reset script - this shoudl disable all functionality
2. run the record from line script
3. run the hw_params program
Before because you had enabled playback the hw_param was picking up the
playback capability - the above should mean only record is
I ran through these steps and it's still listing the device as Playback.
Do you have another way in mind?
Michael
mike_b16's Profile: http://forums.slimdevices.com/member.php?userid=63606
View this thread:
Is there no option to tell LMS never to rescan unless I explicitly ask
it to? This is quite important for custom scan users.
Not to scan without user interaction is the default behaviour. That's
why I asked when you experience those scans. What is triggering them?
Because by default LMS
mike_b16 wrote:
I ran through these steps and it's still listing the device as Playback.
Do you have another way in mind?
I think this means you can't trust the wolfson alsa driver or scripts.
It doesn't seem disable functionality as promised.
as a double check using alsamixer with wolfson
After selecting my card in the alsamixer, it looks like there are 50ish
playback devices for which I can change the levels/switch them on or
off. Under capture, there are roughly 30 devices. Master volumes,
equalizers, IN3R, things like that. I believe this has to do with the
available
mherger wrote:
Is there no option to tell LMS never to rescan unless I explicitly
ask
it to? This is quite important for custom scan users.
Not to scan without user interaction is the default behaviour. That's
why I asked when you experience those scans. What is triggering them?
I muted (or reduced to zero) everything in the playback section of the
alsamixer. Rebooted, recompiled hw_params and it still says my Wolfson
card is a playback device. I'm totally stumped.
Michael
mike_b16's Profile:
mike_b16 wrote:
After selecting my card in the alsamixer, it looks like there are 50ish
playback devices for which I can change the levels/switch them on or
off. Under capture, there are roughly 30 devices. Master volumes,
equalizers, IN3R, things like that. I believe this has to do with the
In this sort of situation, I normally take a break and then after a day
or so review all the information gathered so far. Others users report
that recording works so there must be a setup or test procedure issue
which a review may spot.
Yeah, I think I'll take a day and think on all of these
On one occasion I had added an item to a folder, and played it from the
music folder, without a rescan.
Ah, that's the BMF acronym: Browe Music Folder. When you do so, the
folders you're browsing to _will_ be scanned, as otherwise you wouldn't
see new files and folders. This does indeed
mherger wrote:
The problem you're having is that this kind of small change triggers a
bigger action. I do understand the problem, and it's the reason why 7.9
currently doesn't update the fulltext index after a BMF rescan.
I've been thinking about ways how to improve this, but haven't
PasTim wrote:
And Erland, apologies for not noticing some earlier responses from you.
I've no idea why I missed them. My main question is whether there is
some reason why the multilibrary 'standard' library id might change from
1 to 6 or 7 without me asking it to? It really has happened
Shouldn't post scan actions be implemented using the scanner hooks
instead of subscribing for rescan done ?
That's the best option if it's little processing involved. In the case
of the fulltext index this doesn't really apply, as it involves not only
a single track, but the whole album and
38 matches
Mail list logo
