Is the lack of programmer memory more of a problem than machine memory?

  • 3
  • Idea
  • Updated 2 years ago
How well do today's software product managers remember the past and understand the need to retire bugs PERMANENTLY? I'm wrestling with a Camtasia "save" failure (presenting itself on both media optimized MAC and PC platforms), similar to the same problem posted half a decade earlier. A suggested solution is to make sure there are no "special" characters in the file names (which there aren't), but it begs the question- didn't we cover this in the 80's? Seriously, that was one of the big marketing points of the whole initial MAC line in 1982- name things how you like. Are 1970's DOS name programming requirements still a necessity for Camtasia code execution? Another suggested solution is to divide the video project into smaller sub-files. Really? Perhaps that was a suitable suggestion back in the days when copious memory and disk space were expensive and uncommon (mid-nineties at the latest), but not today. Would you also suggest getting the razor blades back out and cut the film to overcome programming problems in current software? I'd hope not!

What hasn't changed in professional artistic endeavors is the desire to use tools that work each time, every time. Perhaps it was acceptable to have bugs 30 years ago, but for users to still be working out similar issues by trial and error today is discouraging. I see posts on your support site about of the need for 60 FPS, user defined interface colors, and other eye candy... none of which helps put food on the table of the average creative professional. Is that more important than being known as a "rock solid" tool?
My memory is quite good- and this isn't the first weekend I've spent extended time riffling through error codes and reams of support docs, all the while hoping your software that I've paid for three times over via "updates" works. The road is littered with dead companies that sold programs to professionals that are more like vaporware than a professional tool. On a Sunday night, knowing I have to disappoint a client on Monday, I wonder if history just keeps repeating itself because the past was forgotten by historically challenged Techsmith management.

My suggestion, use your educational software to teach your programmers that artists don't get paid by the hour. Every time I have to find a "work around" to complete a project that another software package does reliably, it costs me time and money, or I have to make creative compromises to accommodate your product failures. Eventually, it destroys customer confidence and subsequent revenue. They say it takes ten times the money to win back lost customers than to satisfy them in the first place. In my case, this was your second chance- I went to Sony products ten years ago to overcome bugs in the early releases of your products. I recently came back and updated my Techsmith products hoping you had moved beyond problems of past decades. That is seemingly not the case.
I understand your business requires you to be riding the curl of the wave all the time- as does mine. The difference is that I don't have customers that will wait thirty years for me to get it right. And frankly, neither do you. The next time you fly, be glad the airline industry doesn't operate like the software industry...
Photo of Kevinw

Kevinw

  • 3 Posts
  • 0 Reply Likes
  • frustrated

Posted 2 years ago

  • 3
Photo of Paul Middlin

Paul Middlin, Employee

  • 835 Posts
  • 185 Reply Likes
Recently, Camtasia for Windows release its 64 bit version, which has helped many of our customers that had large or complex project significantly. Have you had a chance to try it? 
Camtasia for Mac has been 64-bit for quite some time as well. 

In general, we certainly strive to have a rock solid product, leveraging countless hours of QA testing and beta feedback. However, some machines or projects still have issues that we couldn't encounter here. If you're having such an issue, we really do want to try to figure out why and see if we can find a cause. These isn't one simple save bug or complex project issue, or else it certainly would have been fixed by now. Instead there are some hard to pin down things on occasion that people like you can help us sort out.
Photo of pjonesCET

pjonesCET

  • 358 Posts
  • 65 Reply Likes
One reason Mac in the past could name files, folders, Hard Drives, Device names anything was we started out  using Motorola Chips and C, C+, C++, and Objective C. Then because of growing Pains Motorola couldn't or wouldn't keep up. So Macs Started using Intel chips and deep Down code is based on x86 the trouble with  X86 is forbidden characters inherent in X86 code. X86 trace it roots all the way back to CP-m. So  Apple now has issues with forbidden characters: For example In Office application you can use any of these Forbidden characters  and pretty much applies system wide:

Some of the Forbidden Characters are:
Numbers before names, Superscript/Subscripts.And these Characters:

+ * ” ‘ \ | / ; [[ ]] << >>

Numbers after Names are okay but before extensions.
None of these characters can be used in the name of:
A) Hard Drive.
B) Directory (Folder) Names.
C) Any File Names.
D) Any Device Names.
E) And on servers

For Servers: no names can have the name File or Fileserver in any path names.
You can use _ (underscores).
NOTE: I haven’t included dashes/hyphens because I haven’t found any information.
Photo of Kevinw

Kevinw

  • 3 Posts
  • 0 Reply Likes
From my work programming FileMaker Pro over the years I have learned to separate only using underscores and following the guidelines you suggest. I built the original video presentation in Camtasia v.8 on PC, then upgraded to v.9 recently. I needed to finish it on the road with my Mac (with my DAWs and other audio programs) so I saved it to v.3 Mac. I removed the callouts (a dialog said they were legacy and not compatible in the Mac version). The transfer went smoothly, but I tried adding a scale up effect and it crashed every time. In both versions, the save problem started acting up, so I am convinced it is a bug that effects both Mac and PC versions. Yes, it could be my source material, but both the video and audio play and edit fine in other programs on both platforms. I'm at a loss how to get past this and just want to get what I have done delivered and not trouble shoot software.
Photo of ExpertNovice

ExpertNovice

  • 352 Posts
  • 105 Reply Likes

Someone explain to me what the save bug is?  It was not explained in the post and, having several decades of working with computers I don't understand.  I have never lost any work trying to save a Camtasia file;  which does NOT preclude the existence of such a bug.