Assigned
Status Update
Comments
va...@google.com <va...@google.com>
va...@google.com <va...@google.com> #2
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, Please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.
da...@mps-data.co.uk <da...@mps-data.co.uk> #3
Hi, Is there any update on this ticket. We are currently in the process of migrating our encoding pipelines to google transcoder. Multiple captions is very important for us to proceed.
va...@google.com <va...@google.com>
da...@mps-data.co.uk <da...@mps-data.co.uk> #4
Hi, is there any update on this?
Description
We want to transcode videos into HLS format with segment duration of 1 second. We have the desired transcoder output being generated using FFMPEG currently, we have replicated the config for this into the GCP transcoder config format, but we are only recieving "Internal Server Error" (code: 13) for all jobs.
All jobs are being created with the TranscoderServiceClient library, using JS and node 18.https://cloud.google.com/nodejs/docs/reference/video-transcoder/latest/video-transcoder/v1.transcoderserviceclient
Problem you have encountered:
"Internal Server Error" is returned from API when requesting with Segment Duration equal to 1 second (and GOP duration set to 0.5s or 1s).
What you expected to happen:
A HLS stream to be produced with a Segment Duration to be 1s (or atleast a better error than "Internal server error" to allow us to track down what the issue is with our config)
Steps to reproduce:
A job config (JS - IJobConfig) that fails:
We have encountered this error when using the H265 codec also.
Other information (workarounds you have tried, documentation consulted, etc):
We have be able to transcode the videos with other transcoder configs, with larger Segment Durations.
Maybe there is something else wrong in our config that you can help us spot.