CS9 Editor Usability And Efficiency Need Improving

  • 2
  • Idea
  • Updated 4 years ago
  • (Edited)
I am somewhat of a high-volume Camtasia user, and for me, screencasting has become a "Death By A Thousand Cuts".

As the CS editor has evolved to offer more and more capabilities over the last 3 versions [CS7 - CS9], the time to edit projects has tended to increase with each new version.  Additionally, functions that used to take 1 keyboard click or 1 mouse click now seem to require 2 or 3 to accomplish. Furthermore, with CS9, the editor is less user friendly in numerous ways.

CS9 editor overhead has definately increased the time it takes for me to do my work.  For many CS9 enhancements, as compared with those in CS8, this seems like 1 step forward ... then 2 steps back.

For simplicity, the subject matter of this "idea" will be limited to focusing on just 2 items: (1) having a persistent setting for video background color, and (2) automatically zipping a project after production.  I've actually worked up about 70 enhancement ideas, but I'll leave those for later time.

Why the 2 specific ideas in this thread?

Due to a conflict between the new remix skinned controller, and the older classic skinned controller, and, also wanting to take advantages of enhancements in the current CS9 controller, I needed to republish virtually all of my legacy videos [1,200+].  I started doing so back in October.

My most recent current screencasting tasks involve updating a bunch of these legacy videos; all are software tutorials [475 MP4 videos].  This bunch of zipped projects is organized in 3 collections comprised of 59 sub-collections.  I've worked through 375 of them so far; and almost of the work involved is rote administrative tasks, as opposed to creative.

For each of these projects, I have to manually set a background color [10 seconds work requiring 5 mouse clicks], and I have to zip each project after production [15 seconds work requiring 9 keystrokes and 2 mouse clicks].

Although seemingly small potatoes on a project-by-project basis, the effort needed to just add a background color and zip a project will cost me about (475 x [10 + 15] =) 4.75 man hours spread over the 475 projects involved.

Furthermore, for each of the 59 sub-collections, I have to manually verify [reconfirm] that I did indeed zip each project for archive purposes [takes about 30 seconds using a Beyond Compare 4 folder compare], as the original projects are being deleted to recover disk space.

This zip checking will cost me another (59 x 30 =) 30 minutes.

That's over 5 hours of unnecessary labor that could be eliminated if the CS editor could automatically accommodate these tasks.

I really believe that both a persistent background color property and post-production auto-zipping should be a built-in CS9 functionality.

I don't need anymore practice in setting the same background color hundreds of times over, and I definitely shouldn't have to manually zip each and every project post production.

If curious, I've created a tutorial describing my current workflow [11 minutes of very non-entertaining video]; where these unnecessary tasks are "time span" indicated by callouts.


CS9 offers exceptional stability compared to earlier versions, and that, on its own, makes it a great upgrade from CS8.  But from my perspective, many of the CS9 editor enhancements are eye-candy changes that really don't help me do my work, and in many instances, actually slow me down compared to CS8.

Going forward, I recommend that some development time be invested into optimizing editor behaviors so that it becomes more efficient and faster to use.
Photo of kayakman

kayakman, Champion

  • 8024 Posts
  • 2775 Reply Likes

Posted 4 years ago

  • 2
Photo of Robert R.

Robert R., Online Community Admin

  • 1682 Posts
  • 556 Reply Likes
Hi and thanks for submitting your idea!

As outlined in our New Community Processes post, feature requests are open to voting up through the 1st of the month (this month is slightly different, due to the holidays) where we will then tally the votes and present the findings to our product teams. To ensure we have the most accurate data, on the 1st of the month we will be locking the threads that were listed in the Feature Request Round-up that was posted on the 15th. Once we have reviewed the submitted feature requests, our product team(s) may respond to the request, and if that is the case then that thread will then be unlocked for further discussion.

In the event that your idea is not selected for a response feel free to resubmit the idea and share it with your colleagues to garner as much exposure as possible!

Thank you again for your idea and we look forward to hearing more from you!


This conversation is no longer open for comments or replies.