Mixers and Jive ?

[erland]

How do I launch a MusicIP mix from the Jive remote ?

Is this something that hasn't been implemented yet, or is there some hidden mysterious way to do it ?

If it hasn't been implemented yet, here is a suggestion:

I would like to have a "Action menu" that could be launched from any item, when launched it would show all the functions that can be executed on the selected item. It could be mixers but it could also be other things. Compare it with the right click context menu available in all Windows applications. The "Action menu" doesn't have to be launched from a completely new button, it could for example be lauched by holding the middle button down for a while.

A solution like this would make it easier for the user to remember all the remote key combination. The user just have to remmeber how to launch the action menu and then he get a menu which shows all functions available in that context.

To make it extensible it is also important that third party plugins can register its available actions.

A action menu like this would actually also be good both in the SqueezeBox interface and in the web interface, but as a start I would like it to at least be available in the Jive interface.

Any thoughts ?

[erland]

Does anyone know the status regarding mixers (MusicIP) and Jive ?

[bklaas]

There is no support for MusicIP in Jive right now. Feel free to open a bug, but MusicIP support is not on the first page of my own priorities right now.

cheers,
#!/ben

[Siduhe]

Found this thread when searching for an answer to the same question.

Couldn't find an open bug, so committed as 6560 (http://bugs.slimdevices.com/show_bug.cgi?id=6560).

Ben, any clue on whether/when this might make it to the first page of priorities? Not hassling, just curious, and the lack of MIP support is the one thing that is preventing me from moving to use the Jive controller full time right now.

[dwilliams01]

That would be high up on my list of needed features. I make extensive use of MIP on the fly playlists.

[Siduhe]

Now bug 6561 (http://bugs.slimdevices.com/show_bug.cgi?id=6561) for anyone that's following this request.

Although why my bug gets marked as a duplicate of Dean's when mine came first, I just don't know...

[kdf]

Quoting Siduhe <Siduhe.32xlbb1199902802 (AT) no-mx (DOT) forums.slimdevices.com>:

>
> Now bug '6561' (http://bugs.slimdevices.com/show_bug.cgi?id=6561) for
> anyone that's following this request.
>
> Although why *my* bug gets marked as a duplicate of Dean's when
> mine came first, I just don't know...
>
Because, as I said in the comment, 6561 was already assigned. It was
not intended to hurt feelings. The important thing is that it gets
tracked and done, not who came first or that the forum is always kept
up to date on each update of a report.
-kdf

[Siduhe]

kdf, I think my shorthand has led to a misunderstanding - apologies if so. TFIC is "Tongue Firmly in Cheek". Not offended or hurt in any way...also really pleased this has been assigned.

[kdf]

Quoting Siduhe <Siduhe.32xnmn1199905801 (AT) no-mx (DOT) forums.slimdevices.com>:

>
> kdf, sorry TFIC is Tongue Firmly in Cheek. Not offended or hurt in any
> way...also really pleased this has been assigned.
>
not a problem. It was also due to the fact that Dean's report stated
how he wanted it to work. Basically, Dean is just more
important...unless I disagree with him. ;)

-kdf

[bklaas]

Ben, any clue on whether/when this might make it to the first page of priorities?

FYI-- See comment #2 of the bug (http://bugs.slimdevices.com/show_bug.cgi?id=6561).

cheers,
#!/ben

[dwilliams01]

Great idea - holding down the middle button sounds very generally useful. Since there wouldn't be any visual indicator (at least right away?) when it was available there would need to be some sort of tutorial, etc. somewhere to tell a new general user how to do it.

[erland]

I've added this to the bug report, but I'll say it here also.

I've earlier written a bug report regarding a context menu concept:
http://bugs.slimdevices.com/show_bug.cgi?id=6021

I would really like us to avoid a lot of different key combination to reach different third party plugins stuff on Jive. Holding middle button is a logical way to reach the context menu, but I really think the context menu should be able to contain other stuff than Jive.

I've already written a lot of information in the feature request 6021, so I won't repeat this here.

The problem with not having a context menu is that the user has to remember a lot of different remote key shortcuts to reach different things. This is IMHO not good user interface design with the old remote and it won't be any better with the Jive. So I think some kind of context menu concept it needed to solve the mixer problem and make it extendible for the future.

[dwilliams01]

Just in case you thought that I was poaching - I was referring to your design/request in my earlier comment. Taking it one step further - I was wondering how to tell someone who was picking up the controller for the first time that there was a context menu to be accessed. For instance, there are some things on the existing remote that I fear to touch because they do something, but I don't know what and worry about finding out. That is a barrier to ease of use and general user acceptance.

Here's a thought I'll toss out: The plus key is one of those "mystery" keys, in my opinion. I don't know what it will do so I fear to touch it. It seems to add/remove things or something... Might be an even better choice for a context menu for new users - at least it would have a visible representation. Also if it pops up a menu then it isn't a "scary" button for a new user. Seems like a good graphic as well - "+" would mean "more options". I know that it breaks with tradition from the old remote, though.

[erland]

Just in case you thought that I was poaching - I was referring to your design/request in my earlier comment. Taking it one step further - I was wondering how to tell someone who was picking up the controller for the first time that there was a context menu to be accessed. For instance, there are some things on the existing remote that I fear to touch because they do something, but I don't know what and worry about finding out. That is a barrier to ease of use and general user acceptance.

The optimal solution would be a special button called "Menu" or "Functions" or something similar, but that's not an option since the hardware has already been released.

I think we probably don't want to remove any of the standard click actions on the available buttons, so it probably needs to be a hold action. I personally don't care if play+hold, add+hold or middle+hold is used as long as we get this context menu functionality. The advantage of play+hold is that it would be consistent with the old remote, the advantage of middle+hold is that it would be similar to middle click which also kind of opens a new menu but add+hold would also work.