Philip Meyer;559661 Wrote:
> >But you will find that if you remove CustomBrowse and TrackStat all of
> >a sudden it will only use half of that.
> I know - but that's not due to a few options, or a bit of code to
> support the options.
>
> I actually think it would be better to split CustomBrowse
>But you will find that if you remove CustomBrowse and TrackStat all of
>a sudden it will only use half of that.
I know - but that's not due to a few options, or a bit of code to support the
options.
I actually think it would be better to split CustomBrowse into a smaller plugin
for core stuff,
Philip Meyer;559658 Wrote:
>
> Try Multi-library instead ;-)
>
I did - until I found out after hours that it wouldn't work without
installing CustomBrowse as well ;) ...
--
bluegaspode
1x SB-Controller+Receiver (Duet), 1xSB-Boom. 1xSB-Radio
Server (7.5.1) running on SheevaPlug (Ubuntu) with
>It scared me away a long time. So much that I didn't care that my music
>library was mixed up with (strange :D) music from my wife.
>
I was an early adopter, before there were quite so many options, and explored
addtional functionality gradually over time.
>From what I remember, I just installed
erland;559638 Wrote:
>
> And Custom Browse without Custom Scan is pretty useless.
NO I don't use Custom Scan but still need Custom Browse to separate
Audio Books from Music.
Philip Meyer;559648 Wrote:
>
> My CustomBrowse prefs file is 52K - quite a lot, but compared against
> my current S
>
> Personally, I don't think people decide not to use it because there are
> scary configuration options.
>
It scared me away a long time. So much that I didn't care that my music
library was mixed up with (strange :D) music from my wife.
Only after getting a son (and some albums with lullabie
bluegaspode;559639 Wrote:
>
> So actually the device tells the server "I'm able to show context
> menus" (that's why all SP-devices set this parameter) and the server
> then returns "Touch To Play" key mappings for the SP-devices.
> If you don't use this option, the server returns commands to sh
erland;559641 Wrote:
> Have you already tried if this works or did you just look at the source
> code ?
I used 7.5.1 Desktop-SqueezePlay, played around with the code-snipped
from above (commented out this one line) and went to the artists menu.
Instead of starting a track, SqueezePlay shows the
>Funny side effect: if you hack SqueezePlay not to send this parameter
>you can make a Radio present menus exactly like the Boom.
>
Sounds great - what do I hack to achieve that?
>Wouldn't make sense for the Touch as it lacks an explicit 'play'-button though.
>
But it would be possible to bring up
>The problem is that a lot of code is needed to implement this
>flexibility which results in that it takes more time to maintain it and
>it definitely takes more time to test new releases.
>
Yes, I can understand that. Perhaps "Developer time" is also considered a
"resource" in this regards.
>So
bluegaspode;559639 Wrote:
>
> Funny side effect: if you hack SqueezePlay not to send this parameter
> you can make a Radio present menus exactly like the Boom.
That sounds like a brilliant hack. I still prefer the 7.3 UI for
Controller, but that hack might be enough to let me upgrade past 7.3.4
bluegaspode;559639 Wrote:
>
> Funny side effect: if you hack SqueezePlay not to send this parameter
> you can make a Radio present menus exactly like the Boom. Wouldn't make
> sense for the Touch as it lacks an explicit 'play'-button though.
>
It also makes sense on a Touch if you control it wi
pippin;559634 Wrote:
> I don't think this is what this option does. I mean: it's purely a
> Squeezeplay parameter used in menu mode queries. I have no idea what it
> does but context menus DO work without it, iPeng uses the context menus.
This option changes how the server returns the menu comman
Philip Meyer;559628 Wrote:
> >The current Custom Browse
> >solution is useful if you like to do something really special but
> it's
> >too complex to configure for 80% of the other more normal cases. The
> >issue is just to find out what would cover 80% of the cases.
> >
> The great thing about C
>Yes there is. CB as it is is a resource hog. It would be cool if it
>would run e.g. on a Touch or perform better on low-powered devices
>(although it also seems to get better with 7.6).
>
I'm pretty sure that removing a few options would not significantly reduce the
resources that it uses.
And I
bluegaspode;559626 Wrote:
>
> Even though 'useContextMenu' isn't documented - why would you think
> this would change in the future ?
>
All undocumented features are subject to change, aren't they? I mean,
this is nothing special, it's not only the case with Logitech devices.
>
> As Logitech h
Philip Meyer;559628 Wrote:
> There's no point removing settings and assuming some default value,
> especially when the settings have already been implemented.
Yes there is. CB as it is is a resource hog. It would be cool if it
would run e.g. on a Touch or perform better on low-powered devices
(al
>The current Custom Browse
>solution is useful if you like to do something really special but it's
>too complex to configure for 80% of the other more normal cases. The
>issue is just to find out what would cover 80% of the cases.
>
The great thing about Custom Browse is that it is customisable. I
which would mean, that if erland uses this feature nothing would change
in iPeng, because:
- iPeng isn't sending 'useContextMenu' so even a changed CustomBrowse
would send the same data as now
- iPeng isn't rendering CustomBrowse-Menus like SqueezePlay anyway -
iPeng recognizes albums/title-lists
Actually that's pretty much what Triode uses it for.
iPeng will only deliver the parameter if it's provided in the command
parameters in the menu. So if an action contains a parameter
"useContextMenu=>1" iPeng will hand this back to the server, if it
doesn't, iPeng will not add it.
--
pippin
pippin;559597 Wrote:
> They currently do this (Triode uses it to distinguish between iPeng and
> SP in the Spotify plugin).
>
So I'm guessing this means that iPeng won't do this, so I can't use
this method because then I won't get touch to play functionality in
iPeng ?
pippin;559597 Wrote:
>
erland;559575 Wrote:
> Do they do this for all menu browse queries ? Also for third party menus
> ?
> (Would be nice if stuff like this was documented somewhere...)
>
> Anyway, thanks for the information.
I just looked into (7.5) squeezeplay code (SlimBrowserApplet), it seems
they do it for all
erland;559575 Wrote:
> Do they do this for all menu browse queries ? Also for third party menus
> ?
> (Would be nice if stuff like this was documented somewhere...)
>
They currently do this (Triode uses it to distinguish between iPeng and
SP in the Spotify plugin).
I don't think it's guaranteed
bluegaspode;559558 Wrote:
> By chance just stumbled again over this issue :D
>
> Erland - I just realized, that all SqueezePlay-based devices
> automatically add 'useContextMenu:1' in their Requests to to server.
>
Do they do this for all menu browse queries ? Also for third party
menus ?
(Wou
erland;527807 Wrote:
> When/if I get some time, I'll update Custom Browse to make it consistent
> with the rest of the interface, probably through a global configuration
> option. It won't happen in the near future though because I have some
> other stuff I like to finish first in other applets/p
>Feels like it should either work as it does today or exactly as all the
>other menus does. So this means that even if I don't really like it,
>I'll probably change it so it on Squeezeplay devices also affects the
>IR remote interface while it doesn't on Boom/Classic/Transporter. It
>will probably
>TouchToPlay is the right step for all devices and its a pity that it
>wasn't introduced to the Boom.
Whilst I do understand the change for touch devices (although inconsistent and
could be improved), I totally disagree for all other players (classic and
Radio). First instinct is for knob/right-
Philip Meyer;527823 Wrote:
>
>
> >This makes it completely inconsistent if you also have a Boom or
> >Classic in your setup since those still show song details when you
> hit
> >the right arrow.
> Hurrah!
>
> >When/if I get some time, I'll update Custom Browse to make it
> >consistent with the
Philip Meyer;527823 Wrote:
> >IMHO, the main issue isn't really "TouchToPlay", the main issue is
> that
> >IR remote uses right arrow button to play (even though there is a
> play
> >button on the remote).
> It makes little sense on a Touch player (IMO), and no sense on Radio or
> Classic player
>IMHO, the main issue isn't really "TouchToPlay", the main issue is that
>IR remote uses right arrow button to play (even though there is a play
>button on the remote).
It makes little sense on a Touch player (IMO), and no sense on Radio or Classic
players because there are dedicated Play and Add
erland;527807 Wrote:
> This makes it completely inconsistent if you also have a Boom or Classic
> in your setup since those still show song details when you hit the right
> arrow.
How annoying that TouchToPlay was just implemented for SqueezePlay
devices :(
Can you check if you can reproduce the
IMHO, the main issue isn't really "TouchToPlay", the main issue is that
IR remote uses right arrow button to play (even though there is a play
button on the remote).
This makes it completely inconsistent if you also have a Boom or
Classic in your setup since those still show song details when yo
>Welcome to the inner circle. Now you've got the honor to be able to
>discuss the higher virtues of TTP vs. bitrate information with Phil
>until the cows come home :)
Yeah, I'll take the bait...
I have no interest in bitrate information (nor most other items in "More Info")
- I think you miss th
@bluegaspode
Welcome to the inner circle. Now you've got the honor to be able to
discuss the higher virtues of TTP vs. bitrate information with Phil
until the cows come home :)
--
pippin
---
see iPeng, the Squeezebox iPhone remote, at penguinlovesmusic.com
-
>I'm happy if my wife doesn't ask me, why it is different :)
>For most 7.4.x users, the current way will be confusing.
>
For most users that have used existing products, TouchToPlay will be confusing.
After all, it's the new players that have changed, causing a difference,
rather than existing p
Philip Meyer;527646 Wrote:
> >I was just confused by navigating a custom-browse menu on my
> Radio.[color=blue]
> I am happy that it brings up options
I'm happy if my wife doesn't ask me, why it is different :)
For most 7.4.x users, the current way will be confusing.
>
> If "play all songs in s
>I was just confused by navigating a custom-browse menu on my Radio.
>I'm very used to TouchToPlay so expected to have a song start after
>clicking it. In a CustomBrowse-Menu this opens the options of the track
>(which I'd expect on the '+' icon).
>
I am happy that it brings up options, as I don't
I was just confused by navigating a custom-browse menu on my Radio.
I'm very used to TouchToPlay so expected to have a song start after
clicking it. In a CustomBrowse-Menu this opens the options of the track
(which I'd expect on the '+' icon).
Furthermore in the original library menu, when a sele
38 matches
Mail list logo
