Editing combined images

  • 1
  • Problem
  • Updated 1 month ago
I don't know whether it's just me but is anyone else noticing laggy movement when adding e.g. Steps to a combined image?

It's noticeable when you have the image set to full size but when fit to screen is selected the delay becomes significant.  It makes it very difficult to place a step marker with precision.  This is true whether images are combined with the new function or manually

My desktop is:



If I have Task Manager open when I drag a step marker, RAM use stays constant but CPU cycles zoom from 4 to 34%.  Meanwhile my NVIDIA GeForce GTX 750 Ti is sitting at 0% usage and stays there. 

CPU usage seems excessive for such a simple action.

Anyone?
Photo of Paul

Paul

  • 1205 Posts
  • 936 Reply Likes

Posted 1 month ago

  • 1
Photo of Joe Morgan

Joe Morgan

  • 5855 Posts
  • 3054 Reply Likes
I don't believe SnagIt is capable of utilizing a GPU to any degree worth mentioning.

I created a large combined image as a test. Its 13,160 x 4640 pixels. I don't think anyone would typically create a combine image like this, but that really shouldn't matter.
Once I resized a step large enough to see it in fit to screen mode. Which took a very long time.Every time I dragged the handle,SnagIt froze up for several seconds. I would rinse and repeat the process.I was at 100% scale.
I selected fit to screen. I could add more steps at will.If I tried to move one, SnagIt froze up for several seconds before I could actually move it.Or do anything else. My GPU would register 2% at best that I noticed.

The magic wand is slow at making selections.
Anytime I've throw very large images into the canvas area or used it for more complex editing situations .Things tend to slow down fast. SnagIt is not good with large images or detailed editing situations with a lot of steps. In my experience.

It's still best suited for and works great with quick edits and annotations.

It has a long way to go to run as as fluidly as it should.


Photo of Paul

Paul

  • 1205 Posts
  • 936 Reply Likes
Thorough analysis as always Joe.

The image that I used yesterday was 1685 x 2965.  Big, but not enormous, especially in these days of 4K monitors.  I did some further experiments this morning with a ne example.

With a freshly started PC I started adding screenshots by drag and drop.  I started at 629 x 804.  By the time I had added 2 more the image was 871 x 1225 and still performing well.

I switched to the image from yesterday and the stutter kicked in immediately.  So it would seem there is a tipping point.

However, when I switched back to the image I built today - the one that was previously OK - the stutter had appeared there too.

It looks like a memory register is being exceeded and then not released.

I think I will raise a ticket because this behaviour is persistent.
Photo of Joe Morgan

Joe Morgan

  • 5855 Posts
  • 3054 Reply Likes
I don't know whats to blame exactly.I think its the program overall myself.

It took me over a minute to remove 8 steps from that image. I'm not sure why that would require memory to be released?

However, I switched to arrows because there vector objects as well.Same bottle necks. No point going into detail.

If I saved the image as a .snag I could add 2 arrows quickly and that was about it.

Same with Highlights.After 2, slow as can be until saving the image.

Then I added about 40 arrows rapidly after leaving SnagIt alone while typing this response.
About 25? were added without delay. Then things slowed to the predictable crawl. I opened task manager and saw my  GPU spiked at 100% at times.So SnagIt does in fact tap into a GPU 100% for certain operations.

I added another 30 arrows at least 5 minutes ago and SnagIt is still locked up and not responsive.It's to busy trying to add the currently invisible arrows. The  image is 18,000 x 13,000 pixels now but 80% of that is just one solid color.
That should be very easy for it to process.

This image shows my GPU at 100%.It stays there for only a second and drops rapidly.Hitting different levels and dropping to 0 most of the time.



So, after 8 minutes or so. SnagIt finally started working again.

After Closing SnagIt it took me another 2 minutes to reopen SnagIt because of that image in the canvas.
That's ridiculous. That's not a memory overload issue at start up.That's inefficient SnagIt at the helm.
I wanted to share the image with you but re-sizing was was required.I didn't want to wait 10 minutes for SnagIt to do it so I sent it to Photoshop.

In typing this I realized we needed a side by side comparison of what SnagIt would do with same image resized.

It crashes every time I attempt to resize it with SnagIt.
So I saved it as a png and it did that in about 10 seconds. Then Froze up SnagIt for at least a minute, while attempting to add it to the recent captures tray. I got tired of the .snag file cramping my style and deleted it.

The images look the same at 100% resolution. You have to zoom way in and really scrutinize them to see that the SnagIt images are a little softer in fine pixel outline details. Which really doesn't matter. Some might consider that ideal.While most people would never look that closely at the image in the first place.



Any way you slice it. SnagIt's performance can be abysmal at times.And that shouldn't be the case.
Photo of Paul

Paul

  • 1205 Posts
  • 936 Reply Likes
I have opened a ticket and have referred them to this thread for the detail.

I think that between your tests and mine, Joe, that it's conclusively a problem with the application being a resource hog.
Photo of Paul

Paul

  • 1205 Posts
  • 936 Reply Likes
UPDATE:

It isn't just combined images that are the problem.

I just had to report a problem to another vendor, which required me to take a screenshot from my entire 2K monitor. So 2560 x 1440.  And when I came to annotate it, the stutter was there.

So it's a problem with big images, period.
Photo of damianrx

damianrx

  • 29 Posts
  • 5 Reply Likes
Hi Paul and Joe,
Out of curiosity when your in task mgr is snagit called snagit32.exe?
My 2018 seems to run this program and I'm wondering if it if limited to how it handles memory and registry's
Just a thought.
Photo of Paul

Paul

  • 1205 Posts
  • 936 Reply Likes
64 bit here
Photo of damianrx

damianrx

  • 29 Posts
  • 5 Reply Likes
Thanks Paul, how did you check it?
I know it says in techSmith solutions :
https://support.techsmith.com/hc/en-u...
But I've managed to run the 32 but version on a similar system to yours without intending to. The interface came up as the 2018 version.
When I get time I'll have to hunt my file system and register to see what's going on.
Only other thing I can think of is I had to do a repair on my system because ver 2018.2.2 couldn't open its newly created gif!
Complained about image size... Weird.
Photo of Paul

Paul

  • 1205 Posts
  • 936 Reply Likes
Help > About Snagit.
Photo of damianrx

damianrx

  • 29 Posts
  • 5 Reply Likes
Hi Paul,

I have looked in to it deeper and found that Snagit (snagit32.exe) is actually a 64bit program!
So is the editor (SnagitEditor.exe) and help (SnagPriv.exe) file, but the uploader (UploaderService.exe -  "TechSmith Uploader Service acts as a proxy between the recorder and the controller/API" ) is 32bit.  

Interested to hear the result from techsmith.  Curious why they call their 64 bit snagit, snagit32.exe just a tad confusing I'm sure.

Cheers.

Photo of Paul

Paul

  • 1205 Posts
  • 936 Reply Likes
UPDATE:

Support say this is a known issue that is in the pipeline.

https://support.techsmith.com/hc/requests/522607