Issues I have ran into while using Proclaim.

We used Proclaim for the second week in our main service with significant issues. Below is a short description of each.

1) One of the user added a content slide using of the purchasable media backgrounds. Even though this was deleted it kept coming back including in the middle of worship which stopped the program made it go offline and then jumped the Lyrics to a different song.

2) tried to edit a song on the fly by copying one line and the pasting it just below the existing line and the system froze and crashed.

3) Videos will not upload and play.

Those were the three major errors. Anytime we have to apologize from the platform for our media is a big deal and that tends to lead us away from that software. Proclaim has a lot of great features and I realize that we are still in Beta but we have to get these things fixed.

Find more posts tagged with

Comments

Matt Mencel

I'm going to reply here with our experience too. Second week with Proclaim live in our service. It went better than last week which you can probably chalk up to the tech guy having a bit more experience with it. Much of the info below has been mentioned before, but these are the notes my tech guy shared with me so I'll repeat them here.

Transitions can be slow at times or Proclaim reacts slowly to user input. Some of this may be because our PC is a bit old (we're replacing it soon) or that we still run SSP in another tab in case we need to switch back to it if we have Proclaim problems.
Font is too small. Common complaint I know. There's another thread from Rick Goettsche that mentions being able to enable an "advanced editing" mode for more tech savvy churches. That would be cool.
Song/verse order is clunky. Make it easier to put songs slides in custom order.
When you click "On Air", Proclaim always returns to the very first slide in the Service. We couldn't figure out how when you clicked "On Air" it would open back up on the projector to a different slide that the first one.
When we come in on Sunday mornings, there always seems to be a long delay starting Proclaim because there are updates or new content to download. Can downloading new updates be optional, so that the program asks first if we want to download new updates now....before forcing us to do so? That way we can start it quickly regardless of whether there are updates available and do the updates at a later time.

I'm sure we'll have more next week.

Thanks,

Matt

Allen Petersen

Jerry,

I'm sorry to hear you ran into these issues while using Proclaim. To help us track down and fix them could you please attach the Proclaim log and crash files?

Thank you for your help testing Proclaim,

-allen

jstandridge

https://community.logos.com/discussion/comment/298985#Comment_298985

Thanks for the reply Allen. I will try and retrieve those when I get back in the office. I am assuming those would be stored on the local computer that was running it and not accessible from the web via a separate computer?

Another issue that we are experiencing is the system appears to be preventing us from deleting a scripture reference. As I believe I pointed out above this created problems for us. However, in addition to this I attempted to delete a presentation and like the scripture reference it appears to delete on the reappear a few minutes later.

Also, is there a way to remove a signal once it is added. Some of Scripture verses show up with two signals and I am not sure how they get there. I am not the one that has been entering them but as far as I can tell they cannot be removed.

Hunter Clagett

https://community.logos.com/discussion/comment/298992#Comment_298992

Thanks for the reply Allen. I will try and retrieve those when I get back in the office. I am assuming those would be stored on the local computer that was running it and not accessible from the web via a separate computer?

Also, is there a way to remove a signal once it is added. Some of Scripture verses show up with two signals and I am not sure how they get there. I am not the one that has been entering them but as far as I can tell they cannot be removed.

Yes, those files are stored on your local machine. You can find full instructions on how to gather and submit logs here: http://community.logos.com/forums/t/39446.aspx

A signal is added for the verse range on a bible slide automatically when it is entered into the reference box. They cannot be removed.

Thanks,

jstandridge

https://community.logos.com/discussion/comment/299009#Comment_299009

Thanks Hunter,

So why would there be two different ones. Does it add a signal everytime it is modified? So say I enter Acts 1:5 and the decide I actually want Acts 1:7 so I modify it does it have a signal for both? that is what it appears to be doing. If that is the case then when it is modifed the original signal should be modified or removed automatically when the new one is added.

Hunter Clagett

https://community.logos.com/discussion/comment/299013#Comment_299013

When you modify the passage in the Reference box you are seeing duplication/proliferation of the signals?

It is intended to simply update the current automatically-generated signal.

Thanks,

Rob Schlegel

https://community.logos.com/discussion/comment/299075#Comment_299075

We used proclaim this week at our Sunday service. We even used the iphone app to control the message slides... didn't run into any significant issues (mediashout was ready to roll in the background), but I would agree the program is a bit sluggish and our computer is fairly new.

jstandridge

https://community.logos.com/discussion/comment/299075#Comment_299075

Hunter,

I tried duplicating the signal duplication last night and could not get it to so this may not be the issue. I did check the scripture reference from the previous week and there are two signals on it. One is the actual portion of scripture (about 5 verses) and the other is the entire chapter (about 40 verses). I will monitor this for a few more weeks and see if I can better document when / if it happens again. Thanks.

also i have attached the files you requested earlier.

3632.Proclaim.log

5707.ProclaimCrash.txt

ProclaimCrash.txt