Default filename for output files arbitrarily limited to 50 characters, Camtasia 2018

Commentaires

33 commentaires

  • stephensterry853
    I believe the limitation was imposed due to Windows file path limitations.
    File paths are limited to 260 characters in Windows.

    I tried to produce a test video using 225 characters. I received the error message your reporting.

    I use an online character counter and a couple of sentences from the webpage to create the 225 character file name. Thats how I can be so specific {:>)

    I overcame that limitation by disabling "Organize produced files into sub-folders"



    Producing a video with 225 characters.



    I suspect its a setting that TechSmith has imposed? If you create a file path that exceeds 260 characters. Windows won't open it.

    With Windows 10, you can exceed 260 characters with a registry hack. This may or may not have an effect on Camtasia?
    https://lifehacker.com/windows-10-allows-file-names-longer-than-260-characters-1785201032

    As far as Camtasia is concerned?
    If theres a registry setting you can hack for producing with sub-folders. They might be able to answer that for you. You could contact support.2018 is fully supported.

    Regards,Joe
    0
  • david
    Thanks, but this is not the problem I'm seeing.

    I don't check the checkbox you have indicated (I don't use the player), and the whole file path I'm using is only 80 characters. I can add characters to the proposed filename, so it's not a Windows issue. In the example below, which is the one I'm working on now, only the last letter of the project filename is truncated, but it's always no more than 50 characters that is proposed. 

    I'll start a ticket, but I'm 95% sure the answer I'll get is "use shorter project names," not a way around this arbitrary limit.

    David
    0
  • stephensterry853
    What version of Camtasia 2018 are you running?
    Theres a couple of bug fixes in 2018.0.6 related to long file names.
    I'm using 2018.0.7 and created a 225 character name. So what your reporting isn't effecting me.

    I wasn't using the smart player either.
    0
  • david
    I'm using 2018.0.8.

    The problem is not that I can't create a long filename. I can add more characters to the filename that Camtasia proposes, which is based on the project name. The problem is that Camtasia truncates that proposed  rendered filename to 50 characters if the project name is longer than 50 characters.

    I want the output file to be the same as the project name, so I have to add the missing characters to the proposed rendered filename manually. It's an unnecessary extra step I will be repeating many times, unless I choose shorter project names, which I'd prefer not to do.

    Thanks,
    David
    0
  • SSA-Ed
    David - It's not arbitrary - it's more than 98% of us need, you're the exception.
    TechSmith software engineers save file names in fields of data base files and those are properly (IMO) limited to 50 characters, more than I would ever use. If we voted on it, I'd be a staunch no - I don't need TechSmith files on my PC to grow untethered.
    And it may be out of TS hands. They use a Sequel style DBMS, which may make that limitation for them.

    0
  • stephensterry853
    The way I read it, Dave can't save a project with a very long file name.

    I showed that I can above.
    Heres the thumbnail of that project. With 225 Characters. Saved without issue.

    0
  • Rickstone1975
    @Joe, it seems you are showing a final MP4 file in your image, not a project file. Perhaps you meant to say the final MP4?

    @All others: So here's how I am understanding it. David creates a project and is able to save it with a really long file name. I tested and am also able to save a project using a really long file name. I used:

    ThisWillBeAProjectFileSavedWithAnUnusuallyVeryLongAndUnusuallyVeryDescriptiveFileNameSoICanTestThis

    And according to Microsoft Word, that's 99 characters and Camtasia seems to have no issue whatsoever saving it.



    So I go to produce that project and when I get to the screen where I specify the Camtasia Produced MP4 file, I see this:

    Note that the pre-populated file name is:

    ThisWillBeAProjectFileSavedWithAnUnusuallyVeryLong (truncated to 50 Characters as David is reporting)



    Incidentally, this was using Camtasia 2018. When I tested this using Camtasia 2019, that 50 characters increases to 80 characters.

    It seems reasonable to me to conclude that in the internal programming of Camtasia, the developers never anticipated a file name longer than 50 characters for version 2018 and they boosted that count for 2019. 

    Now I'm not a Camtasia programmer, but in my professional career I've done a fair amount of programming using different languages, so I am only basing things off what I'm seeing here. And what I'm seeing tells me that there is likely a field that has been declared in the Camtasia programming code that stores the project file name so it can pre-populate the final file name we see at the end. 

    This would explain why we originally see the truncated version at the end, but are easily able to overcome it by typing additional characters as needed.

    This indicates (to me, at least) that the issue is with an internal field storing the information and not with the field we use to specify that file name.

    I looked in the Windows Registry and didn't see anything that would govern this. But for David, if he hasn't already thought of this, a temporary workaround would be to click File > Save As just before you choose to produce the output. Because this will allow you to copy that long file name to your clipboard in order to paste it into that final file name dialog.

    Cheers... Rick :)
    0
  • Rickstone1975
    This isn't intended to be a slam on David at all, it's just that this discussion reminded me of this scene from SpaceBalls and I think we all can stand a good laugh from time to time.

    .
    0
  • david
    Ed,

    I disagree. Unless TechSmith surveyed a large proportion of Camtasia users and got near-universal agreement that 50 characters is plenty, and that the vast majority of these users wanted no more than that, then the decision to deliberately truncate the proposed filename is by definition arbitrary: "Based on or subject to individual discretion or preference or sometimes impulse or caprice."

    There is no performance or storage savings gain with this approach, and users are still free to make their filenames as short as they want. I can't see any programming efficiency gain, either. It's trivially easy to parse the full path of the current project, extract the filename, and then create a string composed of the new path, the existing filename, and the new extension and populate the "Production name" field with it. Camtasia has this information already stored in its program space (it's displayed in Recent Projects, for example). The TechSmith designers have simply chosen to truncate the project name when they output it in the "Production Name" field.

    As for your concern about TechSmith files growing untethered, I don't see the relevance. TechSmith already stores the full path of the project. So no additional space is taken up in any database by displaying the full filename in a dialog box. Besides, if database size were their concern, then they'd presumably limit all file path fields to 50 characters. Nowhere else do they do that. Just here.

    David


    0
  • david
    Rick,

    Thanks for testing and verifying that this is what Camtasia does and for your educated speculations on why they may have decided to do so.

    David
    0
  • stephensterry853
    I completely misunderstood the problem. Sorry about that {:>(
    Brain Freeze??? IDK

    Camtasia 8 let me create a project with my 225 characters. And even produce it using the project file name.
    Then,
    I exported the video with sub folders. It truncated the videos name and all related files.
    I zipped the project, but couldn't open it. Error codes 114 & 527.
    This occurred in Cam 8 and 2018.
    Cam 2019 threw out 2 error messages. Lacking any error code numbers.

    My view from 30,000 feet?
    They increased the limit in 2019 to accommodate people like yourself.
    I don't believe its an arbitrary number.
    Its likely a number that's intertwined with the Smartplayer.The Zipping and Un-Zipping of projects & what Windows may or may not accommodate. With many other possibilities. 

    Bottom line, there will be no updates for 2018. So your stuck.
    If you complain loud enough, can demonstrate this restriction is hindering your workflow. They might upgrade you for free or offer you a discount?
    They darn sure won't update 2018.
     
    It was an interesting topic.
    0
  • david
    My view from 30K' is that it's another example of TechSmith not really adequately testing their products before they release them. If some part of their system can't accommodate long file names, then they should prevent you from saving files with long filenames, not just truncate the display of the MP4 file. Or, better, fix the whole system so it accommodates the filename length limit of the operating system.

    I like using Camtasia when it works, and it has been a decent learning experience, but the amount of troubleshooting it took just to get it running more or less adequately - about 15 hours on my own and with tech support - plus the signs of an immature product that's in its 10th or 11th release will probably lead me to a more robust editor after this. Currently, I'm trying to wrap my head around the complexity of DaVinci Resolve. 

    Anyway, as you say, it was an interesting topic I hadn't expected to take the turns it did.

    David
    0
  • SSA-Ed
    David,
    First an apology for being blunt in my prior post.

    When office 2007 came out my son in law started giving all his Word and Excel spreadsheet files very long file names. Within 3 years he couldn't find anything in a timely manner, so he spent a Sunday afternoon making sense of it by renaming almost all of them.

    "- about 15 hours on my own and with tech support - "
    Totally avoidable had you just played the hand you were dealt (IMHO).
    0
  • david
    Ed,

    My "apology for being blunt," back. 

    The "hand I was dealt" with Camtasia that you say I should have "played" was that I had 1) frequent crashes while editing and 2) unusable jumping and jittering during the editing process as soon as I stared adding transitions and behaviors. Everything else ran on my new computer, purchased for Camtasia after it failed to run on my existing computer, just fine, including other video editors. On the new computer, too, Camtasia was completely unusable. Not just nit-picky unusable. Completely unusable. 

    That's what took 15 hours to fix, troubleshooting here and with TechSmith tech support, before I finally got a somewhat usable video editor out of Camtasia. I love the features -- it's perfectly adapted to the kinds of instructional videos I'm doing -- but the QA for the product is poor. I've been using computers since 1980. I've never had a piece of software that was as difficult to get to do what it's supposed to do as Camtasia.

    At this point, the preview is still jumpy and sometimes out of sync with the audio, but the crashes don't often happen. The 15 hours of trying workarounds and back-and-forth with TechSmith got it running as long as 1) I preprocess my MP4s through Handbrake, 2) fall back to the on-board GPU instead of using my (much better) GPU card, and 3) eliminate using hardware acceleration in the UI with a registry hack TechSmith provided after reviewing my crash dump files. 

    The filename thing is a trivial matter, a minor annoyance. The other issues were show-stoppers. Had I not already invested the time in taking a Camtasia course, I would have moved on then and tried to get my money back. 

    What you seem to be "apologizing" for is TechSmith (IMHO). You may be one of the lucky Camtasia users who has had a decent experience with it out of the box, but if you look through this board you'll see that a lot of others have had similar experiences to mine.

    As for your opinions on long filenames, I got by with 8.3 in the CP/M and MS/DOS days, but long filenames greatly simplify my workflow. Your son-in-law's experiences with long filenames are irrelevant to me. 

    David
    0
  • Rickstone1975
    Just an aside. I honestly wonder about today's users reading this thread and David's reply and whether the terms 8.3, CP/M, and MS/DOS has any remote meaning.
    0
  • SSA-Ed
    David - I was unaware of all your other Camtasia problems.
    Many here have turned off Hardware (GPU), including me - takes 10% longer to render but that's a small price to pay for "smooth as silk" videos

    ". . . registry hack TechSmith provided after reviewing my crash dump files." That's interesting  - changing Camtasia's H/W acceleration on and off (preferences, advanced) changes the registry for me.
    Now when Windows allowed special characters in file names, that rang my bell!!

    If my filenames fit in the allotted space below, I'm good, if not I rename, personal preference.

    .

    0
  • david
    Ed,

    That particular registry hack stops Camtasia from using hardware acceleration for the UI, which it apparently does even when you tell it not to use hardware acceleration. I needed to also turn off acceleration for the UI in order to get Camtasia to stop crashing (most of the time - crashed today twice, even with the hack).

    David
    0
  • SSA-Ed
    David -

    I don't think you've defined what you believe an adequate length would be.
    Cam 2018 does 50, Joe said Cam 2019 does 80, what length would you like?
    128?, 256?, 512? or ??

    Would longer lengths crash other programs?  At some point you'd be opening a can of worms, do you know where that is? I certainly don't.
    0
  • david
    Rick,

    "Just an aside. I honestly wonder about today's users reading this thread and David's reply and whether the terms 8.3, CP/M, and MS/DOS has any remote meaning."

    I would be shocked if they did know any of these things, and it's not important that they do, anymore than they need to know Fortran or assembly language. But, I was responding to Ed, who I'm sure does know what I'm referring to. 

    David
    0
  • Rickstone1975
    Just from an observational standpoint, I would think the length should match what the operating system allows.
    0
  • david
    Ed,

    I don't understand your question. Camtasia already allows filenames to be as long as the file system allows, as it should. I just want it to display the long name in that particular dialog box.

    It already does what you seem to be afraid it will do and keep asking about.

    David
    0
  • SSA-Ed
    Rick -  While true, what OSes are allowed by Camtasia?
    I think Camtasia requires Win 7, 8.1 or 10. Do all share file system properties?
    I know personally Windows 7 doesn't allow " ÷  ≈   ≡ " in file names.

    0
  • SSA-Ed
    @David  -

    In your original post, you said:
    "Camtasia 2018 truncates the project file name to the first 50 characters ..." I took your word for it!

    Now you're much clearer:
    ". . Camtasia already allows filenames to be as long as the file system allows, as it should."

    I never thought of it as a dialog box real estate issue!

    0
  • Rickstone1975
    Well, actually, if you read the post title it begins with the word "Default". ;)
    0
  • stephensterry853
    I'm Un-Following this post topic.
    This dead horse has been beaten to death don't you think?
    0
  • Rickstone1975
    I thought the discussion was focused on the number of characters that Camtasia feeds into the output field if the project has been saved.

    Seems that special characters is a completely different issue and wasn't brought up here.

    While it would be great if the Camtasia developers were able to filter out special characters and perhaps substitute a nice and safe underscore, I believe that is a completely different issue and should perhaps be in a different thread if warranted. ;)
    0
  • SSA-Ed
    Rick -  As originally posted, how did you take it to mean? 
    0
  • Rickstone1975
    As with so many discussions of this type, I'm not sure what David could have done differently to make things clearer. 

    Perhaps this stems from my many years of working in a call center supporting computers and learning to "read between the lines", but I generally scan the post headline, then read the body in the hopes that whomever is posting is clear about what they are asking for help with.

    So the headline read "Default filename for output files..." and that was enough to clue me in that what he is seeing is something Camtasia is using as a default. But a new Camtasia project typically defaults to "Untitled Project" unless you first save the project file with a unique name. So I had to assume it meant David is saving the project first and what he was seeing was based on that filename used when first saving.

    On a bit of an aside, it seems to me that this is a failure on the part of the development team. Although, like you, I don't use file names that are unusually long. I suppose it is a bit of a holdover from the old 8.3 standard. But I'm much more lax these days about keeping things really short.

    Hey, old dogs CAN learn new tricks!

    Happy Monday all... Rick :)
    0
  • david
    Rick,

    I suppose I could have said "default proposed filename for rendered file in Production dialog box," but I doubt that would have fit into the subject line.

    I think in terms of input and output. Input is the media files and project file, output is the rendered file, much like source code and the compiled executables.

    David
    0
  • Rickstone1975
    I thought your initial post was easy to understand. Like I said, given the situation, I'm not sure how you could have done it any better than you did. 

    Let's all now form a circle and hold hands as we pray to the TechSmith gods for a week to ten days and hope they decide to look at this issue for a future modification! LOL
    0

Vous devez vous connecter pour laisser un commentaire.