INTERACT FORUM

Networks and Remotes => Remotes => Topic started by: Paul S.A. Renaud on March 28, 2017, 02:27:22 am

Title: Theater View and JRemote
Post by: Paul S.A. Renaud on March 28, 2017, 02:27:22 am
I posted this in JRiver for MAC. However, zero reactions. Is there anybody successfully using the swipe/press functionality JRemote and JRiver? Am I alone here? P.M. I am using JRiver MC22 for MAC.

The swipe/tap/double tap functionality of JRemote does not work for Theater View. When will this be solved as without this functionality properly working Theater View is pretty useless. I understand it is not a JRemote issue but a JRIver MC22 for MAC issue. Or any other suggestion to make Theater View workable?
Title: Re: Theater View and JRemote
Post by: sandifer on April 11, 2017, 12:39:08 am
Any update on this? I am having the same issue.
Title: Re: Theater View and JRemote
Post by: Werner on April 13, 2017, 06:02:39 am
Aha! I’m not alone with this problem. It doesn’t matter if this is a problem with JRemote or with MC22, it would simply be nice if somebody could try to fix it.
Title: Re: Theater View and JRemote
Post by: blgentry on April 13, 2017, 06:45:46 am
I can report that this also does not work with EOS remote's theater remote mode.  I'm guessing Hendrik and friends haven't yet hooked the theater view remote commands into the Mac version.  Just a guess.

Brian.
Title: Re: Theater View and JRemote
Post by: bob on April 13, 2017, 02:04:19 pm
I can report that this also does not work with EOS remote's theater remote mode.  I'm guessing Hendrik and friends haven't yet hooked the theater view remote commands into the Mac version.  Just a guess.

Brian.
It's a function that's not been implemented in Mac or Linux yet.
Title: Re: Theater View and JRemote
Post by: Werner on April 13, 2017, 02:19:19 pm
If it is not implemented it should'nt be there. At least it should givbe a message, that this place is under construction.
Title: Re: Theater View and JRemote
Post by: bob on April 13, 2017, 03:35:20 pm
It just got missed when porting and there's not a way for JRemote to know that it doesn't exist.
It looks like it should be pretty easy to implement however.