Focusrite 18i8 Scarlett and Wirecast 10 compatibility Issue.

Hi Will Johnson .

And audio is one of the challenging elements of Wirecast. Having said that, I don't understand how/why that would happen.

Here's an idea to try to identify if it is wirecast or your drivers.

Try installing Dante VIA... and use it to do some audio routing - See if you have any weirdness going from your USB source into Dante... and then try get Dante routing out to Wirecast - and see if the multi channel routing mis-behaves. If it works with Dante but not your USB source... that might identify the source of the problem.

Hope that helps.

Will Johnson You may want to try resting preferences. It's possible that Wirecast 10 is using Wirecast 9.0.1 preferences and that might be an issue. 

Wirecast > Help > Send Support Information but click on lower left Reset Preferences. Then make sure you test in a New Blank Document as issues can carry over from old documents.

Will Johnson I'd also strongly recommend against posting subject titles like yours until you confirm the issue with support. I renamed the title. Please do NOT do that again. For many of our users 10 solves previous issue and you are dispensing wrong or false information.

Will Johnson Submit the issue. If it worked in 9 I'm reasonably sure we can fix it.
Include the link to your screenshots with your explanation as it'll clearly demonstrate the issue to the developers.
Wirecast Support Form

Will Johnson - Set input and output devices to Dante Via. In the VIA console, assign your input device(s) to system output. If that works, you can go further and try to get your input routed via Dante into Wirecast. Check that first, and let me know how you go.

Greg Kuhnert I can confirm I am having the same issue with my Focusrite Scarlett 18i8. The audio channel jumps around randomly.

Eric Ducoff Fill out the form and report that. Since it seems to be happening with multiple devices we may be able to find the pattern to work on fixing this.

The particular issue I was referring to is a known documented issue. Unfortunately, the design is such that allocation of channels to the USB mixer (and therefore any hardware midi mixers) is currently not deterministic. In other words, it is random. I started to use this to pick my lottery numbers, but that didn't help.

This week - it hit me hard during my live broadcast... where wirecast changed the faders, and I didn't pick up on it - and I moved my own audio level to zero - and kept talking to microphone not knowing what had happened.

This defect is documented here in the unofficial community tracker that I am maintaining. Eric Ducoff  - Feel free to go there and vote for that one to get it fixed. Hopefully, community input will help get bugs sorted and resolved in a more timely manner.

GK

Thank you for your patience - we've now fixed this issue and you'll see this fix make its way into a beta shortly.

Of note, this issue was specific to 18 channel audio devices.

Simon Clarke Good to hear! Is there a way to get in on that beta?

Eric Ducoff : Betas are available publicly to all

This fix is included in the Wirecast 11 beta, available here: https://telestreamforum.forumbee.com/t/k92wjc/wirecast-11-beta-now-here

Good to see there's a fix.

I have exactly the same problem in Wirecast 10.x and upwards with a Presonus 14-channel audio interface (StudioLive AR12 USB). So this is not just specific for 18-channel audio interfaces. I'll have to test the Beta of version 11 first as I have a job with Wirecast coming monday.

Can't have other functions all of a sudden stop working now :)

The two attached images show the problem. First image shows the mapper in Wirecast 9 with correct audio on channel 5+6 and 13+14.

Second Image shows the mapper in Wirecast 10 with audio inputs jumping sequentially from input to input.

Hope the Beta of Wirecast 11 gives us a fix or we have a problem on monday.

Isn't it possible to release a fix for this in like a stable Wirecast 10.2 version so we don't have to wait for Wirecast 11 to be finalised?

Rob Swart Please do test the beta. The beta itself is the test and must be completed to ensure it's working without issues. In other words fixed means ready to be tested. After testing it'll be ready for release. The nature of testing means we can't give a concrete release date because the beta testing may reveal more work to be done. The more users testing and reporting. the more expeditious we can be. 

Rob Swart : Would you mind testing the Wirecast 11 beta briefly - it should fix 14 channel sources

Simon Clarke  CraigS

I have tested the Wirecast 11 beta version and the issue seems to be fixed. The inputs are now correct and the input signals are not cycling from input to input anymore  

I’ll do a more extensive test with an ISO recording this weekend. That’s what we use the multi input interface for. 

Thanks Simon and Craig! 

Hope to see a final version soon. 

P.S. Any idea if and when VST-plugins will be supported in Wirecast? Or should I not keep my hopes up?

And by that I mean 3rd party VST plugins :)