Wirecast stops sending audio to program between Shots
Approximately no less than 3 times in the past week Wirecast has stopped sending audio out when changing shots from an image layer with a music track to an a/v capture card layer. Transitioned back and forth between layers no longer outputs audio. Wirecast must be restarted to clear the issue. Not finding any required/recommended updates on PC or Wirecast.
Issue occurs over multiple pc's running windows 10 with current 14.2 version of Wirecast Pro on i9 equipped Dell Precision desktops. 4 streams (2 audio only, 2 h264 at 720p 1mb) with Record to disk 720p 1mb, also using virtual microphone out to feed TurboBridge Webcall browser application. System CPU is running at around 20% with <10 dropped frames.
-
Joe Vondenhuevel said:
Approximately no less than 3 times in the past week Wirecast has stopped sending audio out when changing shots from an image layer with a music track to an a/v capture card layer.Please describe in more detail so a developer can match what you are doing.
-
CraigS I have a 2 hour audio track and a static full screen graphic layer on a shot in program for between 15-60 minutes "pre-event" with the 4 streams and the virtual microphone/direct show audio outputting as well. At the start of our events we transition to an audio and video capture shot (single Magewell brand capture card providing both). At this point the audio can be seen working in preview but does not go to program. Audio metering appears frozen on program as well. Smooth or cut transition seems to make no difference. There is only one active shot transitioning to another active shot for this switch. Wirecast will have been streaming for roughly 60 minutes during the "pre-event" period. Recording will have been started 10minutes prior to this transition. No warning of any errors during any pre-call testing. All of our standard tests pass without issue.
-
-
Joe Vondenhuevel said:
I have a 2 hour audio trackWe need complete information "track" what codec? What sample rate?
Joe Vondenhuevel said:
full screen graphic layergraphic what format?
Again we must have a reproducible set of specsJoe Vondenhuevel said:
4 streamsplease explain. 4 destination. 4 encoders.
Again we must be able to build exactly what you are doing.
Joe Vondenhuevel said:
virtual microphone/direct show audio outputting as well.to what?
This is all very general. We need to put together a matching situation without any assumptions or guesses to the workflow.Perhaps you can send us the document with the elements included.
-
2 hour audio track is .mp3 192kbps
Full screen graphics are multiple but all are either 1600x900 or 1920x1080 and .jpgStream information is attached. Two streams to two server locations. One each is mp4 1mb (settings attached) the other stream is an "Audio Only" preset.
Per my original posting the virtual microphone/direct show audio is outputting to a TurboBridge Webcall browser application. https://panel.turbobridge.com/webcall/
Magewell usb capture device is receiving an HDMI signal of 1920x1080p @59.94 with stereo audio embedded. -
Joe Vondenhuevel said:
Audio metering appears frozen on program as well.Please describe in detail since meters exist in multiple locations in the program.
Sorry for all these questions but it must be presented in a way the developers know what's going on visually as well as monitoring and output.
Perhaps provide a screenshot of your shot config although a document would be most useful. -
Doing my best. Not sure what you mean about a document. We get no error message dialog when this occurs in Wirecast. The metering next to the preview window still functions properly and shows audio. The program audio meters and the shot audio meters go blank/frozen, the video continues to stream out to all 5 locations (4 streams, 1 record to disc) without the audio included. No amount of switching between shots cause the audio to resume in program.
-
Joe Vondenhuevel said:
Not sure what you mean about a document.The actual Wirecast saved document with the shots in it so we can examine it and recreate it on our end.
-
Joe Vondenhuevel said:
No amount of switching between shots cause the audio to resume in program.I suspect there may be an issue with the mp3 playback but that's only speculative at this point. Sample rate might be an issue. Also trying a wav file might be interesting if the problem is codec-based.
-
The issue occurs when switching off of the mp3/image layer to a live capture layer. Attached is our wirecast document.
-
Joe Vondenhuevel Thanks for all this. Updating to let you know we are investigating WIRE-19073. We may have follow up questions.
What is the sample rate of the MP3 file?
You may want to check in VLC media player for example and post screenshot of its Window > Media Information > Codec Details.
-
-
We use two different audio files but both have the exact same Codec information.
-
Joe Vondenhuevel Thanks for that. It should help us.
-
Joe Vondenhuevel Since the issue may be related to the MP3 and other elements, the developers may need the sources to reproduce. We don't have other reports of this but we're not sure how common this workflow is.
It might be as simple as using a WAV file or other uncompressed audio source for example.
We'd need to know the ease of reproduction. How often does it happen after how many transitions?
How long is the MP3 playing for typically before the transition?
-
-
Was not a super high occurrence. Best estimate would be maybe once every 40 placeholder to capture card transitions on each of the 3 machines we've encountered this issue. Has not occurred in the past week since a large windows/dell firmware update. I believe it may have been related to a issue with one of the drivers.
-
Joe Vondenhuevel Thanks for the update. I'll pass it along to the Wirecast team.
-
-
Has this been fixed? same thing happening each time i switch shots. Live Output sound level resets to -INF
-
Thomas Eckermann There's been no reports since version 15 was released. Please make sure you've updated to 15.1. If you are working with a document imported from 14.x or earlier it might have carried over the issue. Test by creating a new document in 15.1.
-
