SamY wrote:
> Those logs look almost perfect. The only negative I can see is that
> apparently the Denon doesn't like getting volume commands telling it to
> change the volume to the setting it's already at, which can happen with
> small +/-1 or 2% changes. It doesn't bother to answer these
MarSOnEarth wrote:
> A brief look at the log confirms your hope/effort being realized. Two
> logs this time, the *1155 is with still with the player's output set to
> variable, and in the *1205 to fixed, all else as before. More comments
> later in DM, but so far it's all looking good. Thanks!
SamY wrote:
> The log file shows that the plugin has been upgraded to v3.0, replacing
> the beta code I uploaded earlier. Actually, I have discovered a couple
> of relatively minor issues in that version, so here are the latest files
> for you and David to test with. I hope to see some debug
MarSOnEarth wrote:
> Ill test the new version later. Earlier in the day I did run a
> sequence of tests for which a log, and the associated settings are
> included.
The log file shows that the plugin has been upgraded to v3.0, replacing
the beta code I uploaded earlier. Actually, I have
MarSOnEarth wrote:
>
> ... I tried to switch to fixed on the client, but that is not workable
> for one major reason; one cannot use a browser for playback on a
> smartphone. To clarify, this setting disables the volume bar, and
> browsers have no access to the hardware buttons; hence, no
OK Sam, because I tried every suggestion we/you have talked about, the
answer to every of your questions below is, yes. Thats why Ill have
to clarify each variation. So...
SamY wrote:
> Let me make sure I understand what is happening though. I see the AVR
> settings in your previous post.
SamY wrote:
> Okay, David and Mars. Are you feeling lucky? Here is the latest version
> of the beta, with actual support for the Quick Select command in Zones 2
> and 3. I have done all the testing I can without actually having a Zone
> 2 or 3, included actually sending Z2QUICKn commands to my
Okay, David and Mars. Are you feeling lucky? Here is the latest version
of the beta, with actual support for the Quick Select command in Zones 2
and 3. I have done all the testing I can without actually having a Zone
2 or 3, included actually sending Z2QUICKn commands to my receiver
without any
SamY wrote:
> Okay. Sorry about waking the neighbors. Let me make sure I understand
> what is happening though. I see the AVR settings in your previous post.
> Did you change the setting in Player->Audio->Volume Control to "Output
> level is fixed at 100%" or did you actually change the volume
MarSOnEarth wrote:
> I see what happened, and it's the best argument against setting initial
> volume on power-on. The plugin read the clients 100% setting and applied
> it the the AVR.
Okay. Sorry about waking the neighbors. Let me make sure I understand
what is happening though. I see the
Aesculus wrote:
> @SamY and I have completed our updates to version 3.0 and it has now
> been posted on GitHub.
>
> Look for it in the LMS Settings>Plugins tab over the next six hours or
> so.
Have update to V3.0, will let you know if any issues.
Cheers, David
*Server*rpi3 pCP5.0.1
MarSOnEarth wrote:
> ...
> See if you can make sense of what happened, but it was an attempt, at
> the very least, at entertaining not just the present in the room, but
> also the neighborhood.
> Good luck.
I see what happened, and it's the best argument against setting initial
volume on
SamY wrote:
> The debug log shows that the plugin is correctly handling the volume
> requests that it is getting. However, those requests are all over the
> map, starting at 22, then 26, 54, 74, 53, 75, 96, 75, 92, and then a
> bunch of incremental changes taking it to 100, followed by 61, 78,
@SamY and I have completed our updates to version 3.0 and it has now
been posted on GitHub.
Look for it in the LMS Settings>Plugins tab over the next six hours or
so.
Chris
Aesculus's Profile:
MarSOnEarth wrote:
> Here it is, but barring more adjustments the user experience is
> diminished vs. the previous settings. For one, the usable volume range
> has been compressed into the upper quarter of the total, and it's
> logarithmic; so, nothing, nothing, something, and L O U D. No
Yes, got it. This way allows you have multiple SB with multiple Denon
*SqueezeBoxes:* 1x Transporter (Living room) 1x SB2 (shed), 1x Radio
(Kitchen), 1x Boom (Dining room), 1x piCorePlayer (jacuzzi), 1x
piCorePlayer (Garden) 1x OSMC + Squeezelite (Movie room), 1x Touch
(Study 2), few spare
edwin2006 wrote:
> No way!
> Never guessed it would be there. Thinking of it it is somehow logic.
> The alternative would be a plugin setting where you point which player
> should take initiative to power up the denon.
The reason is that the plug-in can be used for multiple players at once
vs a
SamY wrote:
> The config settings are done in the Player section of the LMS menu,
> where you will find a new submenu called DENON AVP/AVR Control. And be
> assured that you're not the first to ask this question. [emoji6]No way!
Never guessed it would be there. Thinking of it it is somehow
SamY wrote:
> ...
>
> Please send a debug log after you make the change. If the results are
> what I expect, I will go back to my original plan of syncing the client
> volume to the Zone 2 volume setting returned from the Z2ON command, as
> is now done for the main zone.
>
> Thanks.
Here it
edwin2006 wrote:
> Really feeling very silly...
> Installed plugin but now what?
> Where to config?
> Searched high and low and plugin says installed plugin, restarted lms
> multiple times the same for the underlying picoreplayer.
The config settings are done in the Player section of the LMS
Really feeling very silly...
Installed plugin but now what?
Where to config?
Searched high and low and plugin says installed plugin, restarted lms
multiple times the same for the underlying picoreplayer.
*SqueezeBoxes:* 1x Transporter (Living room) 1x SB2 (shed), 1x Radio
(Kitchen), 1x Boom
SamY wrote:
> Glad to hear that.
>
>
>
> I had to look at a Denon manual to see what you are referring to here
> but it explains some of the strange behavior we are seeing, specifically
> the fact that the response to the Z2ON command, where I expect to see
> the current Zone 2 volume setting
MarSOnEarth wrote:
> It's all looking good here, Sam; the on/off commands work reliably now,
> and so are the volume changes.
Glad to hear that.
> ...the AVR displays "-3dB" (the hard limit that's been set), and all the
> volume changes are under software (your plugin) control. I'm guessing
>
SamY wrote:
> Okay. So the AVR volume synchronization with the client at power on is
> now working properly. That is good news. However, all of the volume
> change commands sent to your AVR continue to time out which, as I said
> before, is not necessarily a problem in itself as long as they
SamY wrote:
> David and MarSOnEarth:
>
> Here is a new version of the beta code for you to try. If the client
> reports its volume as 0 during power on, it will set it to 25%. This is
> a temporary fix and there is actually a chance that it will work as
> originally planned due to a change in
MarSOnEarth wrote:
> Here it goes,
> Thanks
Okay. So the AVR volume synchronization with the client at power on is
now working properly. That is good news. However, all of the volume
change commands sent to your AVR continue to time out which, as I said
before, is not necessarily a problem in
SamY wrote:
> David and MarSOnEarth:
>
> Here is a new version of the beta code for you to try. If the client
> reports its volume as 0 during power on, it will set it to 25%. This is
> a temporary fix and there is actually a chance that it will work as
> originally planned due to a change in
David and MarSOnEarth:
Here is a new version of the beta code for you to try. If the client
reports its volume as 0 during power on, it will set it to 25%. This is
a temporary fix and there is actually a chance that it will work as
originally planned due to a change in how the client volume is
SamY wrote:
> Well that's a "good news / bad news" scenario if I ever saw one. The
> good news is that the response times for everything except the volume
> changes are dramatically improved, presumably due to the AVR reset.
> However, every one of the volume change requests continue to time
DavidBulluss wrote:
> Squeezer works quite nicely, but turning on the zone 2 volume sets at 0
> still.
Yep. I can see that in the log file. I'm not sure why it happens with
your system (and with MarSOnEarth too) but not with mine. Maybe it's
something specific to running with a non-main zone.
MarSOnEarth wrote:
> Hi Sam,
>
> Here are my results.
>
> Thanks
Well that's a "good news / bad news" scenario if I ever saw one. The
good news is that the response times for everything except the volume
changes are dramatically improved, presumably due to the AVR reset.
However, every one
DavidBulluss wrote:
> Log file attached. What I have noticed is that when first turned on and
> track played that there is no volume. Turning up volume brings it
> suddenly to life and volume is probably as it was when last played
> before being turned off. No waking of neighbors :-) The other
SamY wrote:
> Thanks, David. The debug log is very helpful. Unfortunately, the Squeeze
> Ctrl app is letting me down again. For some reason, it is setting the
> client volume to 0 during the "power on" sequence so that is the value
> that the plugin retrieves and uses to synchronize the AVR
Hi Sam,
Here are my results.
Thanks
+---+
|Filename: 210320_11-server.log |
|Download: http://forums.slimdevices.com/attachment.php?attachmentid=33854|
DavidBulluss wrote:
> Log file attached. What I have noticed is that when first turned on and
> track played that there is no volume. Turning up volume brings it
> suddenly to life and volume is probably as it was when last played
> before being turned off. No waking of neighbors :-) The other
DavidBulluss wrote:
> Loaded in, restarted, and... off for some testing. Then I will do the
> log and sent it to you.
>
> Regards, David
Log file attached. What I have noticed is that when first turned on and
track played that there is no volume. Turning up volume brings it
suddenly to life
SamY wrote:
> Please generate a debug log of a power on followed by playing some
> music, adjusting the volume, and a power off.
Loaded in, restarted, and... off for some testing. Then I will do the
log and sent it to you.
Regards, David
*Server*rpi3 pCP5.0.1 LMS7.9.2
*Media*USB hard
SamY wrote:
> Okay. I think I see the problem here. When you said "your newest code",
> I assumed you meant the code I just uploaded a couple of hours ago in my
> post to David but the debug line numbers don't match and neither does
> the behavior. Please download that version and generate
MarSOnEarth wrote:
> Hi Sam, I've been timing things out after resetting my AVR. Here are a
> few data points with your newest code:
> >
Code:
> > P-off: 1.1926 P-on: 0.1833
> 1.0956
MarSOnEarth wrote:
> Hi Sam, I've been timing things out after resetting my AVR. Here are a
> few data points with your newest code:
> >
Code:
> > P-off: 1.1926 P-on: 0.1833
> 1.0956
This is odd looking. Seconds after successful power-off command, there
are all these extra reads. Odd because, a) huge delay, and b) my zone 2
is set to stereo music.
+---+
|Filename: P-off-reads.log
SamY wrote:
> Okay, David. Here you go. As I mentioned before, this intermediate
> release does not actually contain support for the Quick Select command
> in secondary zones but there are significant changes to how other
> commands are processed. Assuming everything works as designed (a BIG
>
DavidBulluss wrote:
> It would be a pleasure, bring it on! Very happy to test the beta.
>
> Cheers, David
Okay, David. Here you go. As I mentioned before, this intermediate
release does not actually contain support for the Quick Select command
in secondary zones but there are significant
SamY wrote:
> Thanks. I'll let you know. The present changes I am working on apply
> only to secondary zones. Was my response to your question about volume
> synchronization helpful? V3.0, which will be released soon, should take
> care of any remaining inconsistencies in that area.
Yes. Your
madpatrick wrote:
> SamY,
> If needed im willing support with testing.
> Ive not yet setup different zones but maybe it helps with the quick
> select function.
> Since ive just a few days the receiver, im still learning all
> functions :)
Thanks. I'll let you know. The present changes I am
SamY wrote:
> Hey David. I have a question. Now that you know to back up your plugin
> files in a safe place when beta testing :), I wonder if you would be
> interested in testing some changes I've been working on with regard to
> secondary zone support. Before I move on to the next coding
SamY wrote:
> I wouldn't get my hopes up. The latest changes, specifically the
> 2-second timeout on the Z2? command, has gotten you past the "power on"
> problem. The timeouts on the Z2OFF aren't necessarily a problem unless
> the Denon is failing to perform the task of turning off the Zone 2
MarSOnEarth wrote:
> This may, or may not be so, but either way, not available as an option
> (this house's backbone is all powerline), and a different conversation.
> Mine is hoping that Sam can find a way to code around such absurdly off
> numbers.
I wouldn't get my hopes up. The latest
MarSOnEarth wrote:
> This may, or may not be so, but either way, not available as an option
> (this house's backbone is all powerline), and a different conversation.
> Mine is hoping that Sam can find a way to code around such absurdly off
> numbers.
My experience with the delays is that it
edwin2006 wrote:
> Temporarily replace powerline adapter via long ethernet cable and test
> again. I found powerline adapters very unreliable.
This may, or may not be so, but either way, not a available an option
(this house's backbone is all powerline), and a different conversation.
Mine is
MarSOnEarth wrote:
>
>
> Timing seems to be the culprit and the Achilles' heel of the
> implementation in every hiccup the plugin exhibits I ever encounered ;-)
> Yet, my AVR is hard-wired over 500Mbps power-line adapter with low
> latency..
Temporarily replace powerline adapter via long
SamY wrote:
> Hey David. I have a question. Now that you know to back up your plugin
> files in a safe place when beta testing :), I wonder if you would be
> interested in testing some changes I've been working on with regard to
> secondary zone support. Before I move on to the next coding
DavidBulluss wrote:
> Yep, the next time I was replacing the files with the beta ones I saved
> them elsewhere as a backup :-)
Hey David. I have a question. Now that you know to back up your plugin
files in a safe place when beta testing :), I wonder if you would be
interested in testing some
SamY wrote:
> Interesting. The first thing that sticks out to me is that the Z2?
> command, which is the first command issued by the plugin during "power
> on" processing to check the status of Zone 2, is consistently taking
> ~1.7 seconds to respond. The timeout interval for that command was 1
SamY wrote:
> Oops! Not sure what happened there, David. Maybe the plugin was updated
> during that time but, if that were the case, it should have overlaid the
> new files too. I guess the safest thing to do is to copy the old files
> somewhere else. If you ever need to go back to an older
DavidBulluss wrote:
> Interesting that you suggested to rename the old files. That was also
> what I did before placing the new files into the folder on the
> assumption they would still be there if I needed to revert. Next time I
> looked the renamed files had disappeared!
>
> Cheers, David
MarSOnEarth wrote:
> Thanks, and glad to do it. Two server logs; they are both of just power
> on/off commands from my desktop (W10P, FF w/ Material UI), though I also
> use Material app on Android (10) phone. The second (+net) log also
> includes debug from network.asynchttp. Hope you find it
DavidBulluss wrote:
> Interesting that you suggested to rename the old files. That was also
> what I did before placing the new files into the folder on the
> assumption they would still be there if I needed to revert. Next time I
> looked the renamed files had disappeared!
>
> Cheers, David
SamY wrote:
> Copy them into your DenonAvpControl plugin directory after renaming
> the old ones and then restart LMS.
Interesting that you suggested to rename the old files. That was also
what I did before placing the new files into the folder on the
assumption they would still be there if
SamY wrote:
> All I can tell you is that the line numbers in the debug log correspond
> to v2.1 and not v2.3 so that's a mystery to me.
I had a trouble updating the plugin from v2.1 (the update kept looping),
so maybe that's when things got out of sync.
SamY wrote:
> In any case, if you would
MarSOnEarth wrote:
> Just checked, the 'install.xml' does say 2.3; so, I'm good there.
All I can tell you is that the line numbers in the debug log correspond
to v2.1 and not v2.3 so that's a mystery to me.
In any case, if you would feel comfortable doing it, I would like you to
try running
MarSOnEarth wrote:
> Hmm. It shows 2.3 in the LMS plugin list. What to do?
Just checked, the 'install.xml' does say 2.3; so, I'm good there.
MarSOnEarth's Profile: http://forums.slimdevices.com/member.php?userid=69826
SamY wrote:
> Hi Mars. First of all, from the log it appears that you are running v2.1
> of the plugin. Please upgrade to v2.3.
Hmm. It shows 2.3 in the LMS plugin list. What to do?
SamY wrote:
> You are correct in observing that the power on command is not being
> sent. That is because the
MarSOnEarth wrote:
> On the one hand, I see so much of new activity here, and on the other, I
> don't get to use that particular player that's hooked up to our Denon
> often, but now I tried it after quite a while, and the power on/off
> sequence no longer works. It all used to work quite
On the one hand, I see so much of new activity here, and on the other, I
don't get to use that particular player that's hooked up to our Denon
often, but now I tried it after quite a while, and the power on/off
sequence no longer works. It all used to work quite splendidly, zone2
on/off, quick
madpatrick wrote:
> The plugin is working nicely and i learning every day how handle my new
> Denon Receiver.
>
> Is it possible to set the volume of the squeezebox at a fixed start
> level.
> Now my receiver is set to a start volume level and also the squeezebox,
> but this is too low at
The plugin is working nicely and i learning every day how handle my new
Denon Receiver.
Is it possible to set the volume of the squeezebox at a fixed start
level.
Now my receiver is set to a start volume level and also the squeezebox,
but this is too low at start.
I like for example to set the
SamY wrote:
> Oh. Okay. That whole part of the plugin code is a black box to me as the
> only Apple products I have ever owned were an Apple II (actually two of
> them) and an iPod Touch 4th gen. I still have the iPod in a drawer
> somewhere. Maybe I should give it a charge and see if it will
Oh. Okay. That whole part of the plugin code is a black box to me as the
only Apple products I have ever owned were an Apple II (actually two of
them) and an iPod Touch 4th gen. I still have the iPod in a drawer
somewhere. Maybe I should give it a charge and see if it will run iPeng.
Sam
SamY wrote:
> Hmmm... I never noticed that. Does it only happen the first time after
> the plugin is installed, or every time LMS is restarted?
This is a feature that is unique to iPeng. The author added the plugin
audio features capability. I never reached out to the Squeezer author
to see
Aesculus wrote:
> I am still upset that the menu's in the Plugin don't get set properly on
> the first viewing. You have to go into the menu, see nothing has been
> set, leave and come back, or select something.
Hmmm... I never noticed that. Does it only happen the first time after
the plugin
FWIW I migrated the Wiki to a more friendly GitHub format and updated
the contents.
https://github.com/aesculus/denonavpcontrol/wiki
Chris
Aesculus's Profile: http://forums.slimdevices.com/member.php?userid=14876
View
SamY wrote:
> I've found through experience that, while this may be true for some of
> the settings, most changes take place immediately without having to
> restart LMS.
I decided trying to figure out and then explain which does and which
does not to be to complex. :-)
I am still upset that
Aesculus wrote:
> Note if you make changes you have to restart the LMS.
I've found through experience that, while this may be true for some of
the settings, most changes take place immediately without having to
restart LMS.
Sam
Hi Aesculus,
I found it just after you posted your reply.
Thanks !
-
Patrick
madpatrick's Profile: http://forums.slimdevices.com/member.php?userid=4929
View this thread:
madpatrick wrote:
> Thanks for your reply.
> I've installed the plugin by the plugin section, but i don't see any
> settings page for this plugin
> Could this be that i'm on LMS : 8.1.1 - 1610364019 ?
Go to the Player menu in Settings and you will find the ability to add
the Plugin there. Note
Thanks for your reply.
I've installed the plugin by the plugin section, but i don't see any
settings page for this plugin
Could this be that i'm on LMS : 8.1.1 - 1610364019 ?
-
Patrick
madpatrick's Profile:
madpatrick wrote:
> Hi,
> Just saw this post about the Denon plugin for the first time.
> Im looking for a new receiver to replace my current.
> The functionality/integration with LMS would be great
> If the plugin can control the receiver this would be way step forward.
>
> Does this plugin
Hi,
This saw this post about the Denon plugin for the first time.
Im looking for a new receiver to replace my current.
The functionality/integration with LMS would be great
If the plugin can control the receiver this would be way step forward.
Does this plugin all Denon AVR receivers ? Or is it
SamY wrote:
> Well, so much for that theory. I just did a test with Squeezer and it
> also sends dial-based volume changes in a series of 1-unit increments
> which are cached in the plugin until there is a 1/4-second break which,
> to me, results in a fairly smooth feeling, if not analog,
SamY wrote:
> It appears that the Squeezer app is more conservative in sending
> "analog" volume changes to LMS. It probably does some caching of its own
> in the UI as the dial is rotated, whereas Squeeze Ctrl seems to send
> every volume change in individual increments of 1, which causes the
Aesculus wrote:
> FWIW on Squeezer I use both the physical volume control and the digital
> spinner. Both work well for me.
It appears that the Squeezer app is more conservative in sending
"analog" volume changes to LMS. It probably does some caching of its own
in the UI as the dial is
FWIW on Squeezer I use both the physical volume control and the digital
spinner. Both work well for me.
Chris
Aesculus's Profile: http://forums.slimdevices.com/member.php?userid=14876
View this thread:
SamY wrote:
> Okay. The log looks good except for a lot of timeouts due to the high
> number of requests. I suggest trying a larger volume increment per press
> in the app to cut down on the network traffic. 5 seems to work well for
> me in Squeezer. Also, if you are looking for more volume
DavidBulluss wrote:
> Log attached. I set the app to use phone vol buttons for vol adjustment.
> There is a setting for amount of volume change per press, I set that at
> 2. Doesn't all work as well as I would hope for, amp volume was adjusted
> along with LMS volume, but when I was in the 90's
SamY wrote:
> If you end up doing that, I would be curious to see the debug log
> showing what volume increment the app is sending to LMS when the up/down
> buttons are pressed. Thanks.
Log attached. I set the app to use phone vol buttons for vol adjustment.
There is a setting for amount of
DavidBulluss wrote:
> I may be best to turn of screen swiping and rely on the on screen vol
> buttons in that case.
If you end up doing that, I would be curious to see the debug log
showing what volume increment the app is sending to LMS when the up/down
buttons are pressed. Thanks.
Sam
SamY wrote:
> It's a combination of both. The plugin caches volume change requests
> that are received within .25 seconds of each other in order to avoid
> overloading the AVR with a continuous stream of small changes. From the
> log, I can see that Squeeze Ctrl is sending a flood of very small
DavidBulluss wrote:
> Not sure which app and/or plugin is responsible!
It's a combination of both. The plugin caches volume change requests
that are received within .25 seconds of each other in order to avoid
overloading the AVR with a continuous stream of small changes. From the
log, I can
Aesculus wrote:
> It's interesting that back on the 9th the logs showed volume settings
> around 50 or so. Then on the 10th all the requests were in the 90's.
>
> Do you think this is when the settings were changed on SqueezeCtrl to
> 100% volume? Not sure what that would cause volume changes
Aesculus wrote:
> Do you think this is when the settings were changed on SqueezeCtrl to
> 100% volume?
I do. I believe that the app was adjusting the volume higher in a
(misguided) effort to reflect the "fixed at 100%" setting. You may have
noticed that the first volume command sent to the
SamY wrote:
> I don't know how the Squeeze Ctrl UI handles volume control but,
> according to the log, it seems to prefer values in the 90's. ;-)
> I tend to believe it's a bug (or feature) particular to that app.
> Combined with your +15 max volume setting, you were driving your amp to
>
SamY wrote:
> I don't know how the Squeeze Ctrl UI handles volume control but,
> according to the log, it seems to prefer values in the 90's. ;-)
> I tend to believe it's a bug (or feature) particular to that app.
> Combined with your +15 max volume setting, you were driving your amp to
>
DavidBulluss wrote:
> I just gave the Squeeze Ctrl settings as suggested a run... volume
> jumped straight up to 100% (wishing now I had tweeked the limit to -10!)
> and interestingly when I tried to turn it down it seemed to affect the
> LMS volume marginally and took it down to 93%. I didn't
SamY wrote:
> Sounds good. Alternatively, you could use the Squeeze Ctrl preferences
> option described in Chris's last post if you want to try "fixed at 100%"
> again. Just remember to lower the max AVR volume plugin setting.
I just gave the Squeeze Ctrl settings as suggested a run... volume
DavidBulluss wrote:
> Thanks for the heads up about Squeeze Ctrl behaviour, will just continue
> with "volume control adjusts outputs", I probably had worked out years
> ago that it didn't work with "fixed at 100%"
Sounds good. Alternatively, you could use the Squeeze Ctrl preferences
option
SamY wrote:
> Looks like it's working correctly with "Volume control adjusts outputs".
> However the log shows no volume change requests when "Volume is fixed at
> 100%" is selected. Apparently Squeeze Ctrl by default detects when this
> option is in effect and does not send volume requests to
Aesculus wrote:
> I emailed the author. Lets see if we get a response and I will post here
> of course.
The author emailed me back immediately and indicated that the setting
for having Squeeze Ctrl to send the volume request when at 100% is:
> Preferences > Controls > Fixed Volume Send
SamY wrote:
> According to the author's comment in the link I posted, there is already
> an option in Squeeze Ctrl to do this. However he doesn't specify how to
> activate it.
I emailed the author. Lets see if we get a response and I will post here
of course.
Chris
Aesculus wrote:
> So now someone needs to contact the Squeeze Ctrl author to ask them to
> pass the requests through to LMS to make this work there also.
According to the author's comment in the link I posted, there is already
an option in Squeeze Ctrl to do this. However he doesn't specify
501 - 600 of 935 matches
Mail list logo
