Wirecast 7 C# Scripting

Hi!

Funny, but the Telestream's Desktop Support is directed me here to ask my question.

So, did someone ever tried the C# sample code provided by Wirecast 7?

I tried to compile it with MS Visual Studio Community Edition.  It doesn't worked.  I attached the screenshot with the error.

Any idea, what could be the problem?

b.r.

Marton 

26replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Make sure you're on Wirecast 7.5. Perhaps a user using C# can respond.
    What version of Visual Studio are you using? 2017? Earlier version?
    Windows 10?

    Reply Like
  • Hi Craig,

     

    I'm on 7.4 right now but i will check 7.5 today.  But it looks sure if C# sample code didn't changed at all.  I'm using Visual Studio 2015 Community Edition on Windows 7.  Do I need to use VS 2017?

     

    Reply Like
  • VS 2015 should work but I'd recommend test with VS 2017.

    Reply Like
  • I tried VS 2017 with WC 7.5.  Still not working.  Does anybody used this sample script ever?

     

    Reply Like
  • You may want to look at this thread in our old forum.
    I wonder if rolling back to an older version of VS Studio would help.

     

    Reply Like
  • I'm sure your programmer team doesn't use an older version Visual Studio than 2015.  Thanks for the link but I didn't find any relvant information to my problem since it's a 6 years old thread...  They talk about Wirecast version 3.6

    Do you have any information when was the sample scripting library changed last time?

    Reply Like
  • Zsombor Marton Wondering if VS 2008 would work. It did work at one time. I'm not sure anything in Wirecast would break it specifically. Perhaps updates in VS might require changes in the sample script though. Did you show support your specific unhandled exception? It seems to be pointing to a specific .dll.

    Reply Like
  • CraigS Yes I did.  Kitty from desktop support directed me me to here.  I asked her to show the screenshot to one of telestream's programming engineer.  She didn't answered.  What else can I do?   Maybe I will try VS 2008..

    Reply Like
  • Zsombor Marton Do try VS 2008 it may point to an issue with our script if it works there. Also make sure you've update .NET Frameworks currently at 4.6.2 just in case that's a factor. VS 2008 was on 3.5 though. The version of NET Frameworks may be a factor.

    Reply Like
  • I've had someone look at the script.

    1. the sample script for C# is set to use Gameshow and not Wirecast
    2. launching Wirecast from the sample script has an issue due to the Welcome screen. Make sure the welcome screen is set not to appear when launching WC if you want to launch WC with the script, or launch the script after WC is already in a document


    Search for Instances of "Gameshow.Application" and change them to "Wirecast.Application"

    Examples in your screenshot
     

    This is a bug on our end. We need to fix the sample script. Sorry about that.

    Reply Like
  • Please do fill out the report form and note that we've confirmed the issue is with our script. Also include a link to your screen shot as it makes it very obvious. We'll work on the fix.

    Wirecast Support Form

    Reply Like
  • CraigS   Thank You Craig!   Exchange GameShow to Wirecast helps...  Now the sample application starts on Visual Studio 2017.

    A software engineer should work on it because it has some other bugs.  For exampe the status window doesn't shows all the active shots. 

    It can delete the "Clear layer" which not too healthy.

    Sadly I didn't find what I looking for in the sample code.  I would like to catch the events when new active shot selected  and then I would like to know which are the active shots exactly.  My application will do things depends on it.

    I hope someone  will help me how to do that.

     

    I'll report the script issue again.

    Thank you,

    Marton

     

    Reply Like
  • Zsombor Marton we'll work on making sure there's a working sample script. If you believe there are other bugs report them too.

    Reply Like
  • CraigS Thanks Craig but I dont't really want to report more scripting bugs since the last reaction from support team:

    "Thank you for your reply. This is regarding your support case referencing: C# Scripting issue v2.0.

    Scripting is something that is up to the user to get setup. We don't offer support on setting up scripting to automate processes. You would need to figure that out based on the API."

    Great!!!

    b.r.

    Marton

    Reply Like
  • Zsombor Marton Please do report and note that we've confirmed the bug in our script.

    Reply Like
  •  

    Replace:

                try
                {
                    _Wirecast = Marshal.GetActiveObject("Gameshow.Application");
                }
                catch
                {
                    Type objClassType = Type.GetTypeFromProgID("Gameshow.Application");
                    _Wirecast = Activator.CreateInstance(objClassType);
                }

    With:

                try
                {
                    _Wirecast = Marshal.GetActiveObject("Wirecast.Application");
                }
                catch
                {
                    Type objClassType = Type.GetTypeFromProgID("Wirecast.Application");
                    _Wirecast = Activator.CreateInstance(objClassType);
                }
    Reply Like
  • Mohammad Salloum Thanks for that.

    Reply Like
  • Hi CraigS,

    I would like to ask your help personaly, because I no hope that desktop support will help at all...  (the answer is:  scripting is not supported)

    So as you see in this topic, we are on a work to develop a wireless tally-light system for Wirecast and Vmix.  (Vmix has much better support in scripting)

    Finally we made the code in Visual Basic not on C#.  And it's work nicely, we can send the active camera sources to or Tally system via USB.

    But I don't like the way how we do this.  Our VB application asks every 100 millisec Wirecast for the list on every layer for the active shots.

    I like perfect solutions, but it's not really does.  If you think of it, our application gives an unnecessarry system load for the streaming computer with this continous asks.

    It have to be an better way to catch the moment when the active sources are change.  When the live output changes.  Sadly it's not documented how can we done it.  I'm really sure one of the developer of Wirecast can tell it immediatly if someone ask him/her.

    Could you help me to ask this question from on of Wirecast's tech guy?

    Thank You!

    B.R.

    Marton

    Reply Like
  • Zsombor Marton Scripting issues have come up so, the policy is that there's no support provided. Perhaps a better solution is being investigated but I wouldn't be able to discuss that publicly. You may want to submit a "feature request" with details explaining why vMix has better scripting support. That may be of interest and impact to the developers.

    Reply Like
  • There's no support provided for user-made scripts, of course.

    But the EXAMPLE SCRIPTS PROVIDED BY TELESTREAM should work.

    We don't expect you to fix our scripts, we expect you to fix /your/ scripts.

    Hope this helps fix the incredibly broken response by customer support.

    Reply Like
  • chhopsky The issue mentioned should be fixed in a subsequent update.

    Reply Like
  • Thanks Craig - Is it roadmapped for 7.7?

    Reply Like
  • chhopsky I'd hope so. If you have a case number you can ask directly and confirm that but I believe it's an easy fix on our end regarding those errant calls to Gameshow.

    Reply Like
  • I fixed the errant gameshow calls, although if WC isn't open it will launch gameshow.

    The bigger issue is that the demo script crashes on one of the get scene list calls :>

    Reply Like
  • chhopsky Hopefully this will all be fixed in our testing for the upcoming update with fixes.

    Reply Like
login to reply
Like Follow
  • 2 mths agoLast active
  • 26Replies
  • 393Views
  • 4 Following