In the window that appears, click on the Sound icon, then on the Output tab. Try turning the sound card off and back on again.Ĭan your computer “see” the Soundcard? Go to the Apple menu in the very top left of your computer’s display, and select System Preferences from the menu. Make sure the sound card is turned on - are there any LED lights or displays on it that should be illuminated? Some sound cards plug into a mains socket, whilst others get their power from the computer they are attached to. It’s not uncommon, particularly on computer systems that are moved around for the cable to pop out a few millimetres, and it can look like it’s connected but isn’t properly inserted. Make sure the sound card is connected to your computer, and that the cable is fully inserted. It’s ridiculous that this step often fixes 90% of problems! The first step to try whenever there is a problem is to shutdown your computer, turn the power off to the computer and any other devices attached to it, and turn it back on. Relatively simple shows might connect using the headphone output socket of the computer. There are also some forms of “virtual” sound card, such as Dante Virtual Soundcard (DVS), where there isn’t a separate hardware device, but your computer is connected to the sound system using an Ethernet cable. Sound cards (aka audio interfaces) are typically a separate hardware device that are connected to your computer using a USB, Firewire or Thunderbolt cable. Even at 64samples when I could hear audio-dropout due to heavy processing load this particular error didn't occur more.ĭoes anyone have ideas or suggestions about what to do, we are premiering the show in two days and this is quite stressful.The “This cue does not have a valid audio output device”, “No audio device” or “issue with audio output patch” error message indicates to us that QLab can’t find the sound card / audio interface that it was using to send sound out of the computer to the sound system. Experimented with audio buffer sizes, it didnt seem to matter.Prepared the computer following the Qlab suggestions (exluding the timemachine one).Made sure that all audio files are at native sample-rate (48k running over DNS).Making sure at-least 100GB are free on the SSD.I have been doing my best to diagnose and fix the problem but no luck. Quuad-2.9GZ-I7) ran the same session to the same mixer while running Ableton Live and exporting the multichannel ambisonic files from reaper, so I think the Mac Pro should have power to spare with this Qlab Session (and activity monitor proves me right). But my personal computer (16GB-DDR3 late 2017 MacBook Pro OSX121. This session works with multiple 8 channel audio-files that I alter the playback speed of at moments, so it could be considered heavy. It's a late 2013 Mac Pro, Xenon CPU, 32GB DDR3, 500GB SSD, Running Mac OSX 10.13 High Sierra, audio over Dante Virtual Soundcard. This computer is only used for running sound and has not had problems like this before. All the cues in this session are Audio, fades, devamps, midi and network cues. It only happens when the cues beforehand have been fired. The particular cue that this happens most frequently at is simple, a stereo audio-file and a volume fade. What happens is that when certain cues (always the same couple of cues) are fired Qlab outputs this loud stutter sound that does not stop unless you send a panic command. Hi everyone, I have a critical error happening in the qlab session of the production that I am working on at the moment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |