1) The Display Setting don't seem to "set." We have 5 video streams, with two sets mirrored (1, 2/3, 4/5). Generally when we start up the settings have changed requiring us to always go and set up the displays before doing anything else. Sometimes the settings will change in the middle of editing a program and, rarely, when running a program.  Is it possible that SSP is confused with mirrored video streams?

2) (And much more serious) There seems to be a memory "leak" during any type of editing. For example, if I start last week's program the memory will be about 280Mb. Each time hat I delete a song, scripture, slideshow, the memory will bump up by about 15-20Mb. By the time I have stripped down the program so that I can begin adding new material, the memory usage is up to 8-900Mb. About this time the program will crash. In order to run SSP we have to keep the task manager visible so that we can shut down when the memory usage get too high. The same phenomena happens on my workstation. I have a plethora of programs on my computer and none have a similar problem. I recently switched from 9.2 to 9.3 hoping to solve these problems, but it hasn't helped.

As of 10/12/24 neither of these problems has been solved!

Hi Dick,

I will briefly address these items here just to clarify the context however if you want to pursue a support case for them, please submit a support ticket for each of them.

Item 1 - Display Settings - 99% of the time when people are having issues with the display settings working consistently it is because they are not starting up and shutting down the system consistently as recommended.  SSP only knows what Windows tells it and if that config changes, SSP may be incorrect.  Please review this article for details - SSP Best Practices - Windows System Start Up and Shutdown for SongShow Plus.  Regarding the "Streams" you are referring to - if the 2/3 ; 4/5 are mirrored in Windows, and they are not working consistently then that would be a Windows thing, not an SSP thing.

If you believe you are following all of the suggested best practices and/or there is something SSP specific that we are missing in this scenario, please submit a ticket to explore further.

Item 2 - Memory Leak when editing program - We actually had an escalation open with you on this behavior and did extensive testing including getting precise steps from you for what you were doing, and we were unable to replicate the same behavior that you experienced.  There were some addition questions and details requested, including getting a program from you, but it appears we lost contact and the ticket was closed.

If you are still able to consistently replicate this behavior, please submit a ticket to explore further.

By the way, 8.5 doesn't have this problem on any of our computers - any edits, deletes, additions and the memory allocation is almost constant. We never had any crashes with 8.5 and searches for images was almost instantaneous.

Regarding item 2, we continue to have crashes, mainly after editing or changing display settings. 

I am now to the point where after editing, I restart SSP before projecting.  It's sad because being able to edit while projecting used to be one of the stong points of SSP. It's a hard habit to break.

FYI - We have replicated Dick's issue related to a possible memory leak.  In his case it appears to be multiple additive factors.  Turning off the auto save in preferences should help a little.  We are working on additional updates.

Mark - I am curious - Do you use a lot of program level slide properties in your programs?  We would be interested in getting a program package if that is the case.

I have now begun saving an extra copy of my program so that If (when) it crashes and returns with corrupted file

I still have something with which to work. Automatic saves don't solve this problem. This is just a very, very

"touchy" program and I never get completely finished with a week's editing and then projection without a crash

of some sort - sometime minor with no loss, just the bother of restarting, other times loss of all the program past

where the last edit was. With 8.5, I rarely ever had a crash and never lost data.

Both our 4-port Nvidia card and Windows Display ALWAYS report the same configuration, but

SSP generally reverses two of the three sets, but not the same two. Not a big problem, just means that whoever is

going to use the program needs to know to set the displays before doing anything else. Rarely

does SSP reset the displays once set and running. Seems queer that only SSP has trouble knowing

which display is which until we tell it. As for the "Best Practices," it is not reasonable to require all

display devices to be on prior to turning SSP on, especially when we're only editing a program or

checking for some information. I don't know of any other program that makes such a requirement.

Certainly "Display Settings" is a misnomer since it seems SSP can randomly change whatever is there

using no particular logic.

I am now to the point that I save every 5 minutes or so when editing a program, and restart SSP before every service. I long for the stability of earlier versions. 

I have saved some event logs - would it help to submit them?

I have also been watching the memory in task manager. I seems to run up to 500 MB or so, but stays there.

Mark - I am curious - Do you use a lot of program level slide properties in your programs?  We would be interested in getting a program package if that is the case."

We rarely use program level. Generally everything is set in the  main slide properties. 

Mark,

The system event logs won't tell us anything about the SSP settings or edit pattern, so those will not really help.

The best course of action is to submit a ticket with details about your settings, edit pattern and then submit a PTG of a program that you have edited that caused issues.

Once we have this info we can investigate further.  

To submit a ticket go to the Support tab.