Remote / Presentation Connections Lost
I posted before (maybe on the Faithlife group -- I can't remember) about the problems I've been having getting the remote app to work. It seems to be working fine, and then I'll get a message (sorry I can't remember the exact text) telling me that I can't change the slide.
It happened again yesterday morning. This time my son (who is the projectionist) noticed that just before I tried to change the slide, he got a message on the computer running the presentation that said "Connecting to server" (again the actual message might be slightly different from that.)
This sent our presentation into spasms. As the presentation re-connected to the server, it tried to perform the change request, then tried to go back to the slide the computer running the presentation had last projected, and back and forth. It was a bit confusing for my son. So I killed the remote app on my phone, and he took over making the changes again.
Now we have audible requests from me for slide changes in the recording that I published this morning.
I really like the audio recording feature, and want to use it. I need to invest some funds into getting a cleaner audio feed in and don't want to do that until I get the remote function working.
Can anyone please help?
Peace & Blessings,
Colin+
Comments
-
Hi Colin, sorry about the frustrations the remote caused. As your son noticed, if Proclaim or the Remote lose connection to our servers, then the remote won't properly function. To avoid this scenario, we are beginning to build a local wifi version of the remote. This will mean that you will only need your phone and your computer on the network. This should hopefully cut down on the number of factors that can cause poor remote performance.
In the mean time, you could look at getting a wireless clicker. Essentially it works like a wireless mouse. I thought I had a list of some but couldn't find it at the moment. I'll update here if I find it.
- Jordan
Mac | iOS | Android | Windows | Web Developer
0 -
Jordan, there are some of us (ME, ME, ME [:D]) that would absolutely love to beta test the local network option when you get something rough ready. It has been mentioned before that the Remote app works great during the week when we're going through a dry run; and then Sunday morning comes and the connection goes haywire at 10:30 EST.
We are really looking forward to the day when all of this will be behind us!
Thanks a bunch for your efforts!
0 -
I'm with you Bill.
I've beta tested a lot of software over the years, and would love to have the chance to do it again.
Please Jordan, let us help Faithlife make Proclaim even better.
0 -
Jordan,
How's the work coming on the android remote for a tablet? Looking forward to the day that it is live. [:D]
0 -
Hey Richard, the current Android remote app should work on your tablet and let you view your notes side-by-side with the slides. The only thing I have left in my backlog is the having the Order of Service be visible on the left on tablets. What other 'tablet-y' things do you expect to see?
Mac | iOS | Android | Windows | Web Developer
0 -
Thanks for the response Jordan.
Nothing real specific. I guess I was hoping that a tablet version would be a little more responsive. Quicker to respond maybe. There have times when I can see the notes, but the slide image does not show on the tablet. It does show on the screen, but I actually have to look at the screen to make sure the slide changed. The only other wish that I have is that font size for notes could be larger so it could be more easily read by older eyes. [;)][:)]
You guys are doing great. Just thoughts.
Thanks Jordan!
0 -
Jordan Sjodin (Proclaim) said:
In the mean time, you could look at getting a wireless clicker. Essentially it works like a wireless mouse. I thought I had a list of some but couldn't find it at the moment. I'll update here if I find it.
- Jordan
You have got to be kidding! This is the whole reason I stopped using a projector at my last church! There is nothing more frustrating as a speaker than having to click, click, CLICK with your remote as you wave your arm around to get a proper line of sight to the sensor. Totally breaks the flow of a sermon.
And before you suggest, giving "notes" to an operator, that is even worse. They always advance the slide too quickly or not quickly enough. I hate having to stop my sermon and say, "Please advance to the next slide" or "Please go back to the previous slide."
Your software has great promise (and you promised a lot in your promo), but it just does not live up to my expectations!
0 -
Hi Keith,
From the sounds of your post, I'm thinking that we have about the same level of frustration with the remote app. I tried a wireless clicker with less than stellar results. At times (and I couldn't figure out why it would do this some times and not others--hence why I didn't complain about it) the clicker would advance the presentation by more than one slide, then I'd have to back up, and that too was frustrating.
My hope is they get the new app done soon.
Peace & Blessings,
Colin+
0 -
I really appreciate that Logos is forward thinking and innovative, however, I sometimes think that Logos loses sight of the fact that their software is used for a Mission Critical task, the preaching and teaching of God’s Word. Consequently, they should build their software in the same way as a Civil Engineer builds a bridge—two or three times stronger than needed. They should have built the App with Wi-Fi network support first and then added internet support second.
All this reminds me of my horrible experience with the launch of Logos version 4. The Logos servers were not prepared for that “cloud only” upgrade. I purchase the software on Monday and it was not until THURSDAY that I could begin my sermon preparation! You would have thought Logos would have learned from that experience.
The fact that the APP works fine during the week when the traffic is low is proof that Logos is not prepared on their end to support using the remote over the internet.
I invested a lot of pastoral “capital” to make the upgrade happen and our congregation has spent thousands of dollars on this project. Logos has made the launch a disaster. All the opponents of this project now have more fuel for the fire. I am so disappointed and disillusioned with Logos/Faithlife right now.
0 -
Sorry for the great frustration Keith. I went ahead and sent you a message to follow up offline.
For those following along, we are still working on the local wifi remote, and I have been making of list of potential people who may like to take part in a beta when it is first available.
Mac | iOS | Android | Windows | Web Developer
0 -
I would be thrilled to beta test the app.
0 -
You could add me to that list too Jordan. I"m right there with Lanny
0 -
I got you both on my list
Mac | iOS | Android | Windows | Web Developer
0 -
You can add me to your list of crash test dummies! If it can be broken, I will find a way.
0 -
Got you Michael.
Also, so you all know, this change requires significant under-the-hood changes to Proclaim as well, it won't simply be downloading a beta of the remote app. We will begin by rolling it out to a few customers, and then grow it from there. This won't start to take place until after the holidays.
Mac | iOS | Android | Windows | Web Developer
0 -
Please include me in the beta test. I am totally frustrated with the remote app. It has crashed every Sunday during the service for the past four Sundays. It really messes up the flow of the service.
0 -
Will do Darrell.
Darrell Keith Day said:It has crashed every Sunday during the service for the past four Sundays.
What device are you using? We have a known issue with newer versions of Android.
0 -
Jordan, in November 2015 you wrote: 'we are beginning to build a local wifi version of the remote'
But we were told by your colleague, Scott Alexander, in June 2015 that it was already in development.
I asked again in September 2015 for an update on progress and there was no response.
Is there *any* idea when this is likely to be available?
0 -
I have been working on the local wifi remote.
However, Android semi-recently deprecated an API we use (or more accurately is used in a framework we use) that causes a fairly bad memory leak. This crashes or renders the existing remote unusable after a period of time (the period depends on your usage). We feel fixing this is a higher priority because it affects existing remote users and would affect the local wifi remote as well. Because of this I switched gears and started working on a fix for this issue.
Once this is fixed I will go back to working on the local wifi (I am hoping very soon).
I am not comfortable giving an estimate of when a beta version of the local wifi remote will be available because I do not want set unrealistic expectations.
I'm apologize for the issues you are experiencing with the existing remote.
0
