Managing the Snagit Library - How does the Library Work?
I'd like to know how best to manage 1000s of captures in a Snagit Library. Here's my situation...
1. I'm using the beta of M1 Snagit 2021 and it's working very well. Many of the issues from previous not Apple Silicon version have gone away.
2. I have 1000s of Snagit captures which I've already consolidated and all seem to be accepted and show up (I think).
The issue is as before, where I get very high CPU utilization when scrolling through the library. On the M1, while it does it, it seems to cache some of the earlier ones but I'd like to know how the caching happens and whether or not I'm able to make all of them cache or a good portion cache. If you have thousands of captures, what good is it if you can't scroll through it?
So perhaps the question is at what point should I archive and perhaps output them to images (batch image)? At what point should we consider the library too big? Is there any advice for me on how to manage years of data? Thanks.
-
Hi Scott,
Great question, I have over 5,000 captures in my library so I know what you're dealing with. We have been doing a lot of work to improve performance in the library, and some of that work is in the M1 pre-release build. We're not done though, and we have some good things coming that should help out with this on M1 and Intel.
As far as how to manage this in the mean time, you can use searching and tagging to browse smaller sets of images. Little known trick, searching will look for any text inside text/callout objects, and also will search the URLs of any captures you took of a web browser. Hopefully this helps you find things in the mean time, and we'll keep working on making scrolling perform better.
0 -
Hi Scott,
We shipped 2021.3.0 today which has native M1 support, and on top of that, performance improvements when scrolling through the library on Intel and M1. The CPU usage may still spike on occasion, but it should scroll much smoother with faster image previews. Enjoy!
0
Please sign in to leave a comment.
Comments
2 comments