My vague sense of logic made me inclined to think I was looking at a combination of problems, rather than an isolated one. There were also conditions when this was happening, where Windows' sound settings would still show a sample rate of 48Khz, when playback was actually taking place at 44.1. A few things struck me as worthy of consideration.Įven though playback would be a semitone slower in the edit and cut pages, causing the amount of drift I would expect, in the Fairlight page, the drift was not happening. I've been experimenting with playback under the unwanted conditions Resolve was exhibiting. It is simply to be able to work with Resolve at DVD quality, the same audio quality i use with my other music software and my browser. That should furnish me with at very least a work-around, if not a solution. Then I would try every way I could think of to make the problem happen, until I could see a pattern emerge. ![]() It's tempting to leave things as they are when they start working, without seeing a predictable pattern of behaviour, but it doesn't inspire confidence, so I decided to load up some of the training materials (lesson 1 to be precise) in the knowlege that the material should be as robust and correct as it should. I've seen the sample rate on my audio devices changing from 48Khz to 44.1 as Fairlight loads. I've had the same problems with slow and choppy playback of audio and lack of sync when playing clips. I've suffered problems with Resolve adjusting the sampling rate of my audio devices, just like others on this thread. It's taken me a fair amount of experimentation to come to grips with what I believe has been causing my problems, but I think I have a sensible take on them now. I have had the same problem with Windows'/DR's handling of both devices. I'm a Win10 user and I have a MOTU 828 Firewire and also an RME 9652. I'm using DR17.2.2 and have had an interesting time getting my audio device and DR to work in harmony. I know this is a slightly older thread now, but what I have to say is relevant, I think. Oh, the hours of frustration I have spent diagnosing this conundrum, and I still only partially believe I've got it worked out. Would be good if a BMD developer/designer could comment as to whether my assertion is correct, and whether BMD still intend to enable ASIO in Resolve?. It really shouldn't be like this, but I guess that until BMD allow a proper ASIO interface to be configured for Resolve, then it will always be a pain when working in a mixed sample-rate scenario. This work-around is very convoluted and slow, and wrecks my work-flow - but after a few minutes of faffing-around, I usually get back to a working state again. Once synchronisation lock has been re-established, then both the interface 'FW active' and 'Locked' lights return to steady 'on' state, and audio in Resolve (and other Windows apps) works again. ![]() I can then re-load a Cubase arrangement to set the 'real' sample rate (can be different from 48khz, but needs to be the same as the Windows Sound Control Panel default setting). At this point, the interface firewire and lock lights go out, and start flashing approximately every 1 second, with a quiet audible click on each cycle. ![]() But as soon as I load Resolve (whether or not Cubase remains loaded) it takes ages to load the Project Manger, and then won't play any audio from within a project. ![]() If I go into Cubase first, then ASIO audio works fine. Even when I'm creating a new project, Resolve only seems to allow 48/96/192khz, so 44/88/176khz timeline rates are not seemingly configurable anyway. Resolve/Project Preferences/Fairlight/Timeline Sample Rate/Audio Sample Rate appears to set to 48000 on my system, but is greyed-out once a project is under-way, so I can't subsequently change it on-the-fly. It can be (and for me often is) different from the (48khz) setting in Windows/Resolve. This situation makes it very difficult to switch quickly between Resolve, other Windows applications - and particularly for me Steinberg Cubase v10.xĬubase (using ASIO drivers) seems therefore to be able to force-set it's own sample rate (and the consequential matched setting of my interface) on a per-arrangement basis. with the MixControl v3.7 driver and mixer control panel app. I have a similar mis-matched sample rates problem here using a Focusrite Liquid Saffire 56 interface over firewire on Windows 10 Pro (1909).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |