PDA

View Full Version : SDK example not functioning properly since V2



Doggy
01-10-2017, 12:19 PM
Since V2 one of the C# examples,"managed NDI send" , only sends a frame every 10 seconds once connected locally.
The same example did not have any problems in V1 as do the other examples

Anyone has any idea or experienced this too ?

Thank you

Doggy
01-11-2017, 01:38 PM
It does run BUT :hey:

it needs to be opened by 2 two receivers (monitors) to be triggered to run !!

ZachSchuster
01-19-2017, 03:52 PM
Are you having any issue with the managed receiver example? We can't get it to recognize that NDI feeds are present on the version 2 examples.

ZachSchuster
01-19-2017, 04:04 PM
I just heard back from Dr. Cross himself. The examples are incorrect. I think the next release will have them fixed, but you can email him at [email protected] to request a link for thenew examples.

Doggy
01-20-2017, 02:26 AM
Are you having any issue with the managed receiver example? We can't get it to recognize that NDI feeds are present on the version 2 examples.

I can now after I changed "IntPtr SourcesPtr = NDI.Find.NDIlib_find_get_sources(_findInstancePtr, ref NumSources, 0);" in line 125 (approx) to


IntPtr SourcesPtr = NDI.Find.NDIlib_find_get_current_sources(_findInst ancePtr, ref NumSources);

as NDIlib_find_get_sources is obsolete. did confuse me to initially

"managed NDI send" still has the issue (need to open 2 viewers to get it triggered to run sending)

ACross
01-23-2017, 11:05 AM
I can now after I changed "IntPtr SourcesPtr = NDI.Find.NDIlib_find_get_sources(_findInstancePtr, ref NumSources, 0);" in line 125 (approx) to

IntPtr SourcesPtr = NDI.Find.NDIlib_find_get_current_sources(_findInst ancePtr, ref NumSources);
as NDIlib_find_get_sources is obsolete. did confuse me to initially
"managed NDI send" still has the issue (need to open 2 viewers to get it triggered to run sending)

We have fixed this (I think!) in the next SDK release which should occur in the next few days. If you need it before then, just email [email protected]

We are not making the find_get_sources call obsolete, we are simply depreciating it (it will still work) and replacing it with two that should be easier to understand.
1) Let me know when changes to the list of sources occur.
2) Give me the current list of sources.

This was the API call that caused 90% of all email questions, so improving it hopefully will help.

Andrew

zenvideo.co.uk
01-26-2017, 06:46 AM
We are not making the find_get_sources call obsolete, we are simply depreciating it (it will still work) and replacing it with two that should be easier to understand.
1) Let me know when changes to the list of sources occur.
2) Give me the current list of sources.

That definitely sounds like a better mechanism.