Graphics

Hello Everyone!

Recently we have been experiencing some crashing of Xpression during some of our shows. We see that certain images cause a larger spike in memory usage than others while being played out of Xpression. Comparing the images properties side by side, we were not able to see much differences. We did see however the pictures that were causing some issues were missing some meta data that others had.

For instance, pictures that are working ok have this data.

Color Model: RGB

Depth: 8

DPI Height: 72

DPI Width: 72

Orientation: 1 (Normal)

Pixel Height: 920

Pixel Width: 1,650

Profile Name: sRGB IEC61966-2.1

Date Time: Oct 13, 2014 11:04:04 AM

Orientation: 1 (Normal)

Resolution Unit: inches

Software: Adobe Photoshop CC (Macintosh)

X Resolution: 72

Y Resolution: 72

While the images that appear to be less stable have this data

Color Model: RGB

Depth: 8

DPI Height: 72

DPI Width: 72

Pixel Height: 920

Pixel Width: 1,650

It seems that the problematic images are missing some of the meta data. They do not have a color profile associated with them and they do not have an orientation asset.

Would this be causing something in Xpression to malfunction and crash?

Let me know if I can give you some more info. Any and all help would be greatly appreciated.

Thanks!

Also on a side note,

Is there a reccomended set of photo Export settings out of Photoshop that work best with Xpression?

#XPression

Isaac,

What version and build of XPression are you running?

There is no obvious reason why those two different JPEGs would cause any issue. Can you post the two different JPEGs so we can try them out?

XPression should be able to handle the majority of JPEG image types. We actually don't have a doc covering image export because we don't ever have any issue with it.

#XPression

Thanks for responding Garner,

I agree that it is probably not the Jpegs. We have seen that the majority of our memory spikes are caused from our lower thirds. We believe that the way they were built was incorrect. We are standing by to bring in a desinger to check it out. Also we are running build 5.5 2722.

Would there be a crashing issue going from this lower third that takes up a lot of memory to another full screen after it?

#XPression

Can you post a copy of your project so we can look at the scenes? It will be much easier to find any potential problems with a copy of the project.

#XPression

The whole folder is 47 gbs, here is just the project file. https://drive.google.com/file/d/0B-noYbunE6iEMURoQ2RSYk9MVFU/view?usp=sharing

#XPression

What's the resolution of the videos you have in your scenes? I'm guessing the video is 1920x1080?

Is it a full screen background or just a lower third bar?

Is your system running on Ross Video XPression hardware? If so, what is the NVIDIA card being used? Edit > Preferences > Hardware Renderer > Adapter > GTX ###

#XPression

http://i.imgur.com/Qsq27wC.png

#XPression

The video files are 1920x1080. The problems occur mostly on the lower thirds.

The NVIDA card is gfx780 (#0)

Also we have experienced a new error today. here is a screenshot of it.



#XPression

If the videos are only displaying a lower third you will get significantly better performance and memory usage if they are re-rendered to just the size of the lower third.

For example - instead of using 1920x1080 videos for your lower thirds use 300x1080. Full frame videos are the most resource intensive element you can use in XPression. On a single channel system like you are using XPression is caching and rendering multiple full frame videos as you play take items in the sequencer - because you are using the dissolve/dissolve transitions there are multiple scenes with full frame video online at the same time.

There's a good chance that reducing the number of full frame videos in use will eliminate the crashes you are experiencing.

As for the Access Violation. That is a memory leak in the software. To correct this we need to be able to replicate the steps/actions you are performing that generate the Access Violation. For us to fix Access Violations quickly we need to be able to replicate them. Are you able to generate the Access Violation repeatedly?

#XPression