Need Option For Post-Production Automatic Export To Zip

  • 3
  • Idea
  • Updated 2 years ago
I do a lot of a high volume screencasting, and am always looking for ways to save time doing it.
What I would like to see is the production wizard offer some additional options ...

A check box that would automatically zip the produced project into the designated output folder.

The last wizard screen should remain open after production completes, and should offer 2 new buttons ...

A button that will open the output folder, and another button that will play the video.

By way of example, I'm currently updating a legacy collection of 401 projects [CS8 to CS9], a task I've been working on over the past 2 1/2 months, consuming 309 manhours so far.

I usually work with large collections of similar projects; these projects are produced to MP4 w/controller, into sub folders; every project is zipped into the output sub folder for archival purposes.

After every production, I immediately zip the project, and I then navigate [Windows Explorer] to the output folder and play the video to ensure it produced OK; I then upload the video to my web site.

In my current workflow, these post production tasks [zip, navigate, click to play] take, on average, 35 seconds to accomplish; call it .6 minute [not counting video play time].

.6 * 401 = 240 minutes = 4 hours of labor that could be saved, if the wizard auto-zipped and gave me a button to click to play.

Zipping projects is a critical step if a project might have to be worked on again at a later date; I think it would help many users if that step could be automated and made a part of normal production workflow.

So what is 4 manhours worth?

For me, it's enough time to take a 50 mile bicycle ride, or, enough time to paddle a 15 mile kayak trip.

Screencasting is very time consuming, especially considering all the tasks involved in executing project management, production management, and media management.

Anything that can make the process less labor intensive would be greatly appreciated.
Photo of kayakman

kayakman, Champion

  • 6251 Posts
  • 1835 Reply Likes

Posted 2 years ago

  • 3
Photo of Bob Lewis

Bob Lewis

  • 353 Posts
  • 174 Reply Likes
Great ideas. Have you found any areas where converting from 8 to 9 need to be addressed to make the new video production files and MP4 work as expected.  ( as it worked in 8 )
Thanks
Photo of kayakman

kayakman, Champion

  • 6251 Posts
  • 1835 Reply Likes
are there some specific issues you're having with MP4 videos produced by CS9?

one issue I've consistently run in to has to do with the new smart player & onyx controller

with CS8, every MP4 w/controller production I made used the classic controller; when CS9 was released, I already had over 1,200 such productions on my web site

what I found was that after making a CS9 onyx production, and playing that video, playing one of the old classic controller videos always started that video playing with its volume set to 0%

this was very annoying, and caused frustration whenever a viewer looked at one of my CS9 videos, then viewed one of my CS8  ones; the initial reaction was always that something was wrong with their system's audio

the fix was to delete Browser history before viewing an older video, but that only works if you already know the fix

I reported this as a bug; but not sure what can be done about it

accordingly, I've decided that the only real solution was to upgrade all my old CS8 videos to CS9; hence, my current activities

I'll give some more thought re your question and post as appropriate
(Edited)
Photo of Bob Lewis

Bob Lewis

  • 353 Posts
  • 174 Reply Likes
Thanks  kayakman.
I always appreciate you for your very experienced and insightful comments. 
They have been and are very helpful. 
Photo of kayakman

kayakman, Champion

  • 6251 Posts
  • 1835 Reply Likes
I've remembered another production issue that was great in CS8 but not available in CS9

In CS8 [at least up until 8.6.0 was released], the production wizard [to MP4 w/controller] supported relative URL paths in both the end action parameters, and in jump-to-URL hotspots

the ability to use relative URL paths was a huge benefit because it allowed the hosting of URL dependent videos to anywhere without needing to worry about re-scripting all the affected URLs

I had numerous videos that mimicked button style menus that used jump-to-URL hotspots; some of those menus had over 2,000 hotspots with relative URLs

these menus and their related video collections could be hosted anywhere on a web site, or on your local system, and the hotspots always worked as expected; these video collections could be easily relocated to other web site or local system locations without having to produce all the content again, or, without having to edit the config.xml and config_xml.js files, swapping in new URL values

CS8.6.0 killed that functionality, as does CS9

I ended up having to retire most of my menu videos [which also offered great keyword searching capability], and resorted to using PDF links lists

Such is life ...

But I still would like relative URL support to be restored in CS9
Photo of Bob Lewis

Bob Lewis

  • 353 Posts
  • 174 Reply Likes
Maybe others also used that ability. I wonder why they removed it?
Photo of kayakman

kayakman, Champion

  • 6250 Posts
  • 1834 Reply Likes
I was told it was for security reasons; the [relative URL] jump-to-URL function apparently also allowed java script stuff to be called instead of a URL?
Photo of Bob Lewis

Bob Lewis

  • 353 Posts
  • 174 Reply Likes
Thanks
Photo of Robert R.

Robert R., Online Community Admin

  • 1465 Posts
  • 414 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!

-Robert

This conversation is no longer open for comments or replies.