beta 7: playhead not running in Fairlight page

in beta 7, two projects of mine with several audio tracks do not run when the play button is clicked or the space key is pressed. The play button lights red, but the playhead does not run. Also, the page selection becomes blocked, other pages cannot be selected.

I can switch to a test project with only one camera audio track, and Resolve runs fine in the Fairlight page. Then I can select the Edit page, go to the home screen and select one of those problematic projects. As long as I don't enter the Fairlight page, all goes well.

Another bug: every time I run beta 7, the MIDI output of the control panel is wrong. A different MIDI port is selected. I can select the correct port and save the preference, but after re-starting Resolve, the port is wrong again.

Does that problem project work properly without any panels connected?

it is a Mackie Control alternative, a MIDI controller. Not a Color or Resolve panel. But thank you for the tip, I will try without the controller.

My guess is that the problem has something to do with sampling rates and my audio interface. There is a strange behaviour that causes problems since some time, also in Resolve 16: I have to set the interface to 44,1 kHz. When I set the interface to 48 kHz, the correct SR, there is no sound.

Thanks again, you set me on the right track. Pretty sure it has something to do with external hardware.

Edit: the problem is gone now. Playback works in the Fairlight page, in all projects. It was the audio interface, or more precise, the audio interface driver. I exchanged the audio interface with another one that has a more modern driver. And even better converters, it's an Apogee Duet 2. Only downside is that I have only 4 outputs now, instead of 6 that I had before. But mostly I work in stereo anyway, and will get a new multichannel interface (or an ADAT 8-channel expansion for my RME Babyface).

The driver for the M-Audio Fast Track Ultra interface is a bit dated (year 2014), and won't be updated anymore. The Duet 2 driver works perfectly fine.

Thanks again Jim, you brought me on the right track. It was a bit hard to let my old audio interface go, which has worked well for so many years, but it is time.

Glad you're up and running.

Did you find a workaround to the bug that causes the wrong control panel midi ports to be saved in the preferences?

On my setup the problem affects both the input and output midi port. They reset to the second port in the list, no matter which it is.

no, unfortunately not. Let's see how the next beta, or the final version 17 will handle MIDI control surface inputs.