home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
Installation, configuration support
Colossus Bitrate Setting - I just don't understand it
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mm1352000" data-source="post: 1126886" data-attributes="member: 82144"><p>Hello again Rob</p><p></p><p></p><p>Wow, that's impressive! You must have been involved in a lot of interesting stuff. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p></p><p>No, it doesn't. At least, not one that I'm aware of.</p><p></p><p>The API(s) that we currently support are Microsoft DirectShow's <a href="https://msdn.microsoft.com/en-us/library/windows/desktop/dd377231%28v=vs.85%29.aspx" target="_blank">IVideoEncoder</a>, <a href="https://msdn.microsoft.com/en-us/library/windows/desktop/dd693975%28v=vs.85%29.aspx" target="_blank">IEncoderAPI </a>and <a href="https://msdn.microsoft.com/en-us/library/windows/desktop/dd311953%28v=vs.85%29.aspx" target="_blank">ICodecAPI</a>. AFAIK they are industry standard on Windows, at least for basic settings such as bit rate. Colossus <em>should</em> support ICodecAPI. It acts like it does... but then fails to actually set values.</p><p></p><p>There's no other public or private interface that I'm aware of that would affect bit rate.</p><p></p><p></p><p>We almost always work with property sets (a subset of <a href="https://msdn.microsoft.com/en-us/library/windows/hardware/ff559769%28v=vs.85%29.aspx" target="_blank">IKsControl</a>) when we interact directly with hardware. The public APIs seem to use IKsControl underneath too. And yes, a lot of vendors will not share the details of their private IKsControl/IKsPropertySet implementations. More often than not they are secret... and for good reason. You need to know what you're doing when directly accessing I2C buses etc. It is easier (and cheaper!) to keep information private and avoid 3rd party developers ruining your company's reputation (when their code doesn't work correctly or at worst "bricks" hardware), than to document and release.</p><p></p><p></p><p>My expectation is that this would be superfluous. I'd be very surprised if the failing calls had any effect.</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1126886, member: 82144"] Hello again Rob Wow, that's impressive! You must have been involved in a lot of interesting stuff. :) No, it doesn't. At least, not one that I'm aware of. The API(s) that we currently support are Microsoft DirectShow's [URL='https://msdn.microsoft.com/en-us/library/windows/desktop/dd377231%28v=vs.85%29.aspx']IVideoEncoder[/URL], [URL='https://msdn.microsoft.com/en-us/library/windows/desktop/dd693975%28v=vs.85%29.aspx']IEncoderAPI [/URL]and [URL='https://msdn.microsoft.com/en-us/library/windows/desktop/dd311953%28v=vs.85%29.aspx']ICodecAPI[/URL]. AFAIK they are industry standard on Windows, at least for basic settings such as bit rate. Colossus [I]should[/I] support ICodecAPI. It acts like it does... but then fails to actually set values. There's no other public or private interface that I'm aware of that would affect bit rate. We almost always work with property sets (a subset of [URL='https://msdn.microsoft.com/en-us/library/windows/hardware/ff559769%28v=vs.85%29.aspx']IKsControl[/URL]) when we interact directly with hardware. The public APIs seem to use IKsControl underneath too. And yes, a lot of vendors will not share the details of their private IKsControl/IKsPropertySet implementations. More often than not they are secret... and for good reason. You need to know what you're doing when directly accessing I2C buses etc. It is easier (and cheaper!) to keep information private and avoid 3rd party developers ruining your company's reputation (when their code doesn't work correctly or at worst "bricks" hardware), than to document and release. My expectation is that this would be superfluous. I'd be very surprised if the failing calls had any effect. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Installation, configuration support
Colossus Bitrate Setting - I just don't understand it
Contact us
RSS
Top
Bottom
