![]() ![]() You can learn a lot about new (and old) issues (and how to work around them) by reading peoples posts. updating in the middle of a project is very rarely a good idea. That said, I've not encountered any show stopping issues with these latest updates, but I'm in the middle of a relatively heavy project and I've no wish to tempt fate. At the moment, for example, my workstation is running 17.4.3, my laptop is on 17.4.6. It's not exactly the same, of course, one is Mac and one is PC, but it still provides me a necessary buffer period to discover any obvious issues. ![]() I'm very much more careful now, as a result, and I thoroughly test new versions on my laptop first. but I've been bitten a couple of times as a consequence, updating first and then discovering later that a brand new feature has broken an old one that I rely on. We'd frequently be multiple versions behind the latest release.Īt home I'll admit I've been a bit less strict. I'm working from home these days, Saskia, and sadly don't have the luxury of a spare workstation, but in a multi suite facility I'd always update a test machine first, then only roll out a new version when it proved itself stable. In the moment I tend to feel abandoned by updates or similar idiosyncrasies of DaVinci, instead of being able to rely on it. I as a user who buys a program do it because I use it a lot and daily and want to rely on something. One more general wish: I, as a user of the DVR studio version + BMD cameras in daily professional use, seriously wish that updates are tested on beta audience (or people using the free version) and I, as a professional, am not exposed to bugs and a half-finished program all the time. I look forward to your suggestions for solutions.ĮDIT: I found my mistake - had not linked the destination (Audio Outputs was set and not Track Input) correctly. ![]() ![]() I'm working with the Rode VideoMic NTG (and have been able to record with it in DaVinci before) and the specs below. I also tried Reynaud's approach, but that didn't work either. I ran a crosscheck with Audacity and it works.ģ. I restarted the program to make sure all audio inputs and outputs are configured correctly.Ģ. Since I couldn't imagine that the problem was with my Mic, I tried several things:ġ. I can also start recording, but it does not record because I cannot activate the corresponding track. The R button turns red briefly while clicking on it, and then immediately returns to normal (as it looks when it is not active). The workflow works for me too, except for point 4. to not record the other tracks deactivate other tracks click on R (REC) in audio track on the leftĥ. go to Fairlight → Input Monitor Style → MuteĤ. I have the same problem as described above, but I don't know since which version, because I don't use the in-Program record that often.ģ. I've seen this issue posted on the forum a handful of times and there is never any response/help, does anyone have any clue how to fix this? Attachments No audio after recording resolve4.png (19.63 KiB) Viewed 2842 times Arm for Recording no signal resolve3.png (18.73 KiB) Viewed 2842 times patch/input resolve2.png (14.03 KiB) Viewed 2842 times My mic works in every other program including the web browser, audacity, and OBS. I have gone into settings and ensured that Davici Resolve has access to my microphone, and it does, and from the recording devices menu, I can see that the mic is inputting at 48000 Hz which is what's required for Resolve. I am able to press the record button, however, the resulting recording has no sound/indicator of sound. I believe that I am patching the mono audio correctly, see picture, but when I press arm for record, there is no audio signal being picked up in the mixer, again see picture. Out of nowhere, fairlight has for some reason stopped taking any input from my microphone, it was working as of 4 days ago but now it doesn't seem to want to input anything. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |