Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BrightCoveRendition read only fields #37

Open
AtomicRaven opened this issue Nov 11, 2015 · 2 comments
Open

BrightCoveRendition read only fields #37

AtomicRaven opened this issue Nov 11, 2015 · 2 comments

Comments

@AtomicRaven
Copy link

Hi,

I'm attempting to write MetaData and noticed some Brightcove rendition fields are read-only while in the api docs they are write-able.

Specifically EncodingRate, FrameHeight, and FrameWidth:

http://support.brightcove.com/en/video-cloud/docs/creating-videos-remote-assets-using-media-api

frameHeight: Required for multiple renditions: The height of the image in pixels.
frameWidth: Required for multiple renditions: The width of the image in pixels.
encodingRate: Required for multiple renditions: For multi-bitrate streaming renditions, the encoding rate in bits per second. For example, 150 kbps is specified as 150000.
If you do not supply a value for the encoding rate, the encodingRate property for the video will be returned as 0.

Is there a way to change this?

Best,
Rob

@dmillz
Copy link
Contributor

dmillz commented Nov 12, 2015

Hi Rob,

Thanks for reaching out. I'm not 100% sure, but it's possible that the API defined those fields as read-only a few years ago when I first wrote this wrapper. I don't see any reason why we shouldn't now tweak to code to remove the private on the relevant setters, make those fields writable, and pass them along to the API when serializing a BrightcoveRendition.

My day job doesn't leave a whole lot of time for maintaining this project any more; and I'm no longer really set up to develop with .NET, anyway. Do you think you'd be able to make the changes to this project to suit your needs, maybe add a test or two, and submit a pull request? I'd be happy to offer guidance and feedback to assist you.

Thanks.

Regards,
Dave

@mister-ben
Copy link
Contributor

These are writable for remote assets, but otherwise read only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants