.net Library - StarDust.CasparCG.net


AFAIK there is not much difference in the arguments it takes. The only thing I know of is the AUTO parameter that only makes sense for LOADBG.

Of course the big difference is, were it is loaded. The standard LOAD command loads in the foreground (visible), while the LOADBG load in the background (invisible).


Hi Romain,

Thanks for your efforts. I really appreciate that.
Unfortunately it’s still not running stable.
Every now and again the connection fails when I try to connect either from a previous disconnect (reconnect) or from a freshly started application.
It throws the following error message:

  Nachricht = Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
  Quelle = StarDust.CasparCg.net.Device
   bei StarDust.CasparCG.net.Device.CasparDevice.OnUpdatedChannelInfo(InfoEventArgs e)
   bei StarDust.CasparCG.net.Device.CasparDevice.<GetInfoAsync>d__77.MoveNext()
   bei System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) in f:\dd\ndp\clr\src\BCL\system\runtime\compilerservices\TaskAwaiter.cs: Zeile184

  Diese Ausnahme wurde urspr√ľnglich von dieser Aufrufliste ausgel√∂st:
    System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task) in TaskAwaiter.cs

Maybe you might encounter this problem with the test-app I sent previously.

It seems that there is a timeout when the server tries to answer to INFO command or THUMBNAIL LIST command that is sent automatically by your library on connect.

Sorry to cause so much trouble… :neutral_face: