Retrieving a Rejected Presentation on Youtube

  • 1
  • Problem
  • Updated 7 years ago
  • Acknowledged
Archived and Closed

This conversation is no longer open for comments or replies and is no longer visible to community members. The community moderator provided the following reason for archiving: Inactive threads; archiving to prevent necroposing

I uploaded a video with camtasia relay to youtube, only for it to be rejected on the grounds that it was too long (it was 41 minutes). I have since verified my youtube account and can now upload longer videos; however, I cannot see how to re-upload my presentation. Would it be stored somewhere on my computer? Please let me know. Thanks.
Photo of Peter Thomas

Peter Thomas

  • 4 Posts
  • 0 Reply Likes

Posted 7 years ago

  • 1
Photo of Richard Campbell

Richard Campbell, Champion

  • 679 Posts
  • 37 Reply Likes
Did you save it as a camproj? If so, render it again and upload it again.
Photo of Peter Thomas

Peter Thomas

  • 4 Posts
  • 0 Reply Likes
I don't know if I saved it as a camproj - where is that likely to be on my computer (it is not in the Camtasia folder in my program files and I can't see any other folders related to Camtasia). When using Camtasia Relay, there is no explicit option to save - it is processed and then uploaded to Youtube directly. In this instance, the upload was fine on the Camtasia side but not at the Youtube end.
Photo of Walter Pelowski

Walter Pelowski, Customer Solutions Engineer

  • 226 Posts
  • 19 Reply Likes
Peter,

If it did not process on the Camtasia Relay server due to its length and now can because you've verified your account. It should still be on the Camtasia Relay server in the Job Status queue. Your Camtasia Relay admin should be able to to go that page and resubmit the presentation for publishing. Do you know who this person is? Would you be able to contact him or her and ask them to perform that function for you?

Walter Mitchell Pelowski
w.pelowski@techsmith.com
Customer Solutions Engineer
Photo of Peter Thomas

Peter Thomas

  • 4 Posts
  • 0 Reply Likes
Hi Walter,

Thanks for the comment - I think it did process on the Camtasia Relay server (it lists it as having a green tick by it); the problem is on the Youtube end, where it was successfully uploaded but then rejected on length grounds.

As for contacting camtasia relay admin, I am correct in understanding this to be a person at my University who has responsibility for overseeing this?

Many thanks,

Peter
Photo of Walter Pelowski

Walter Pelowski, Customer Solutions Engineer

  • 226 Posts
  • 19 Reply Likes
Peter,

I'm surprised the entire presentation has a green checkmark next to it. I would expect it to have a red X. Usually when publications fail (in this case it's not technically a failure but a rejection of the submission) it enters into an error state. I would have your Camtasia Relay admin see if it still does exist in the Job queue nonetheless.

And yes, this is someone at your University that has Administrator rights on your Camtasia Relay server.

Walter
Photo of Peter Thomas

Peter Thomas

  • 4 Posts
  • 0 Reply Likes
Thanks for the information and advice, Walter. I'll find out who the administrator is and see if the presentation can be located. I have re-recorded the presentation but it would still be good to know these things in case other issues arise in the future.

Peter
Photo of Clint Hoagland

Clint Hoagland, Employee

  • 60 Posts
  • 25 Reply Likes
Hi Peter,

Chiming in (a bit late) on this issue: I can confirm that YouTube does tell Camtasia Relay that the publish job succeeded. It's only after YouTube attempts to re-encode the published file that it will flag it as invalid (for whatever reason) and then reject the presentation.

For that reason, when using YouTube publishing it might be worth considering a backup of the presentation somewhere local so that files can be re-uploaded in this situation. For example, you could also publish an "original size mp4" to a network fileshare. (Of course, depending on your organization, space for that kind of thing might be limited.)

This conversation is no longer open for comments or replies.