Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 716434" data-attributes="member: 82144">Hi FreakyJYeah, I got your PM. After reading that I was ***very*** angry with Terratec. I guess now that they got my emails but didn't even have the decency to respond. One half of me wanted to say &quot;well we won't support your devices any more&quot; while the other half said &quot;we'll support your devices better than you do yourself&quot;! I think the best option is the second option. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite7" alt=":p" title="Stick Out Tongue&nbsp; &nbsp; :p" loading="lazy" data-shortname=":p" />This new program that you've found is very tricksy! I'm interested, and it could definitely help, but I don't understand the screenshots. The call stacks (the lists of functions on the left hand side) are just as important as the parameters, but I can't figure out which way up the call stack is. There also appears to be at least two threads with important function calls - it is important to see information about both...If we're going to use this application then I think the first function we need to get information about is TTDvrCommonInterfaceGlobalInitialize() - what context is it called in, and what does it return. Having said that, I've looked at the DLLs you posted and there are other functions that might be important that weren't in the original list:There could be more too. There are even 2 or 3 different DvrApi.dll files that I've seen now. I suspect there may be two interfaces: 1 for the TwinHan io Control which is already supported in TV Server, and the other for TerraTec USB devices which is not yet supported. Either that or one interface is a high level one and the other is a low level one. We need to know what is happening at the low level.</blockquote>

[QUOTE="mm1352000, post: 716434, member: 82144"] Hi FreakyJ Yeah, I got your PM. After reading that I was ***very*** angry with Terratec. I guess now that they got my emails but didn't even have the decency to respond. One half of me wanted to say "well we won't support your devices any more" while the other half said "we'll support your devices better than you do yourself"! I think the best option is the second option. :P This new program that you've found is very tricksy! I'm interested, and it could definitely help, but I don't understand the screenshots. The call stacks (the lists of functions on the left hand side) are just as important as the parameters, but I can't figure out which way up the call stack is. There also appears to be at least two threads with important function calls - it is important to see information about both... If we're going to use this application then I think the first function we need to get information about is TTDvrCommonInterfaceGlobalInitialize() - what context is it called in, and what does it return. Having said that, I've looked at the DLLs you posted and there are other functions that might be important that weren't in the original list: There could be more too. There are even 2 or 3 different DvrApi.dll files that I've seen now. I suspect there may be two interfaces: 1 for the [B]T[/B]win[B]H[/B]an io [B]C[/B]ontrol which is already supported in TV Server, and the other for [B]T[/B]erra[B]T[/B]ec USB devices which is not yet supported. Either that or one interface is a high level one and the other is a low level one. We need to know what is happening at the low level. [/QUOTE]

Verification