- Posts: 349
- Joined: Sun Oct 10, 2021 10:14 am
- Real Name: Kurt Friis Hansen
The problem arose in Resolve Studio 17.4 on a 2018 MacBook Pro 13 (4 Thunderbolt) - obviously Intel - Big Sur 11.6.
I was experimenting with various PlugIns (what does not work on Mac mini M1 16GB, 1TB, 10 Gigabit, and what does - a loooong story of sufferings).
I had imported a project exported from my M1, and after relinking media, everything worked for a while. Added The Røde SoundField plugin (not working at all on M1), and went on my merry way experimenting with this, that an d the other. Added a few tracks. Moved a few new tracks around in the list. Removed a few. Etc…. Suddenly I accidentally clicked on R on a filebased track (Binaural), and sound really went mad. Like a Latin American horn Dorchester on steroids and too much Mezcal. Nearly blew my ears - cleaned them thoroughly though. Nothing helped. Restarting the Resolve didn’t help either. But rebooting the machine seemed to do the trick, when the project was started again.
Just one problem. Some tracks had lost the “metering” display in Fairlight and everywhere else, they were in use (Except in “Dynamics”, that seems to work perfectly).
There are the following tracks:
A1 M-S Stereo (from video track) - working, metering okay
A2-A7 5.1 Surround file (from file) - working, metering okay
A8 Stereo (from file) - working, metering disappeared (was not “clicked” R)
A9 Binaural (from file) - working, metering disappeared (“R” was clicked)
A10-A13 AmbiX (from file) - working, metering
All files synced to waveform, and project cut to fit everything.
Bus 1: Stereo output (signal from A8)
Bus 3: Binaural Output (signal from A9)
Bus 2: 5.1 Surround (signal from AmbiX, output from Røde PlugIn)
The setup is designed to create a video file with three user selectable audio tracks (Stereo, Binaural, 5.1 Surround).
Sound is working, transmitted and routed to my headphone (both Stereo and Binaural has been tested).
In the image below shows the mssing metering for the Binaural stereo Track (follow Arrows from Left to right to top-mid). The track shows no metering. The Output bus meters the Binaural signal, and the signal is played from headphone, as expected. Similar behaviour for the pure Stereo track.
When clicking on Dynamics in the Binaural track A9, the meters shows both input and output signal as expected:
I have found no way to enable the metering for the two affected tracks (I may be blind, dumb and… ehh… or not, as the case may be No amount of restart or reboot or…. or…. I even placed my biiiig hammer beside the computer (sometimes it even seems to help - at least on my mood, and that also counts for something
The problem has only been experienced on the Intel version (that is not to say, that it could not be provoked on the M1 version as well).
I have not reimported the original M1 project - yet. I wanted to get this in writing before retrying that, and forgetting half of the details. I will add a comment later today (?), but I suspect the problem will vanish, when I do the reimport. It’s just not a very viable way forward, if really large and tricky projects are involved. This was only a tiny ambisonics test project.
Nothing could really go wrong… ehhh…. Smile!
Regards
P.S. First time the Røde Plugin is applied to the AmbiX channel strip, Resolve crashes completely (tears everything down). Restarting Resolve the Plugin is missing as expected, but now there is no problem applying the Plugin to the channel.
The dearVR_MICRO pkg-install from 10.10.2021 just crashes Resolve each time. Retry doesn’t do you anything good on the Intel platform. Works like a dream on M1. Since it is distributed as a package, the actual install is out of my hands.
Normalising audio (relative) - tested with 2 to 6 channels - sometimes delivers a weird result - up to 4-6 dB different from the actual with EBU R128, it seems. There is no system, and I have not been able to reproduce the problem in a consistent way. It just happens - from time to time. I have only experienced it on the Intel platform. Just as with the “metering problem”.
A memory corruption problem???
I was experimenting with various PlugIns (what does not work on Mac mini M1 16GB, 1TB, 10 Gigabit, and what does - a loooong story of sufferings).
I had imported a project exported from my M1, and after relinking media, everything worked for a while. Added The Røde SoundField plugin (not working at all on M1), and went on my merry way experimenting with this, that an d the other. Added a few tracks. Moved a few new tracks around in the list. Removed a few. Etc…. Suddenly I accidentally clicked on R on a filebased track (Binaural), and sound really went mad. Like a Latin American horn Dorchester on steroids and too much Mezcal. Nearly blew my ears - cleaned them thoroughly though. Nothing helped. Restarting the Resolve didn’t help either. But rebooting the machine seemed to do the trick, when the project was started again.
Just one problem. Some tracks had lost the “metering” display in Fairlight and everywhere else, they were in use (Except in “Dynamics”, that seems to work perfectly).
There are the following tracks:
A1 M-S Stereo (from video track) - working, metering okay
A2-A7 5.1 Surround file (from file) - working, metering okay
A8 Stereo (from file) - working, metering disappeared (was not “clicked” R)
A9 Binaural (from file) - working, metering disappeared (“R” was clicked)
A10-A13 AmbiX (from file) - working, metering
All files synced to waveform, and project cut to fit everything.
Bus 1: Stereo output (signal from A8)
Bus 3: Binaural Output (signal from A9)
Bus 2: 5.1 Surround (signal from AmbiX, output from Røde PlugIn)
The setup is designed to create a video file with three user selectable audio tracks (Stereo, Binaural, 5.1 Surround).
Sound is working, transmitted and routed to my headphone (both Stereo and Binaural has been tested).
In the image below shows the mssing metering for the Binaural stereo Track (follow Arrows from Left to right to top-mid). The track shows no metering. The Output bus meters the Binaural signal, and the signal is played from headphone, as expected. Similar behaviour for the pure Stereo track.
- Metering problem
- Metering Problem 2021-10-24 kl. 13.29.26.jpg (674.76 KiB) Viewed 662 times
When clicking on Dynamics in the Binaural track A9, the meters shows both input and output signal as expected:
- Audio present and routed as expected
- Dynamics 2021-10-24 kl. 13.29.26 (2).jpg (189.55 KiB) Viewed 662 times
I have found no way to enable the metering for the two affected tracks (I may be blind, dumb and… ehh… or not, as the case may be No amount of restart or reboot or…. or…. I even placed my biiiig hammer beside the computer (sometimes it even seems to help - at least on my mood, and that also counts for something
The problem has only been experienced on the Intel version (that is not to say, that it could not be provoked on the M1 version as well).
I have not reimported the original M1 project - yet. I wanted to get this in writing before retrying that, and forgetting half of the details. I will add a comment later today (?), but I suspect the problem will vanish, when I do the reimport. It’s just not a very viable way forward, if really large and tricky projects are involved. This was only a tiny ambisonics test project.
Nothing could really go wrong… ehhh…. Smile!
Regards
P.S. First time the Røde Plugin is applied to the AmbiX channel strip, Resolve crashes completely (tears everything down). Restarting Resolve the Plugin is missing as expected, but now there is no problem applying the Plugin to the channel.
The dearVR_MICRO pkg-install from 10.10.2021 just crashes Resolve each time. Retry doesn’t do you anything good on the Intel platform. Works like a dream on M1. Since it is distributed as a package, the actual install is out of my hands.
Normalising audio (relative) - tested with 2 to 6 channels - sometimes delivers a weird result - up to 4-6 dB different from the actual with EBU R128, it seems. There is no system, and I have not been able to reproduce the problem in a consistent way. It just happens - from time to time. I have only experienced it on the Intel platform. Just as with the “metering problem”.
A memory corruption problem???