Blackmagic Forum

First, a Feature Request:
Please, BMD, place the full string of the version number on DaVinci Resolve (and also on Fusion) splash screen, visible when users launch these programs.

~~~
Note the strange items I've highlighted in the ResolveDebug.txt as you read along:

Running DRS v14.3.0.014, and in dire need of completing and delivering heavily edited project.


☡Crash Scenario 1: Resolve now always hangs in a silent crash after attempting to move an audio track up or down!


☡Crash Scenario 2: Resolve hangs, when "Save As..." is instantiated.

☡Crash Scenario 3: Sometimes hangs when started while I have Console 1 (MIDI audio control surface) On-Screen Display software running prior to launching Resolve -- and that seems to be related to a possible conflict getting in the way of Resolve 14.3.0.014 properly connecting Softube's CONSOLE 1 and also
Mackie's MCU PRO (the 2 connected MIDI control surfaces)

Note near the bottom of log,
"MidiOutWinMM::openPort: error creating Windows MM MIDI output port."

~~~

The end of this attached debug log reads:
"Received Termination Signal SIGABRT, triggering termination routine."

~~~


I do know I _ignorantly_ screwed around with the database panel to the left of Projects pane, on May 9, 2018, clicking on
"PstgreSQL > New Database" and also later, I clicked
"Local Database > New Database", not knowing what I was doing, and seemingly caused increased instability for the large project I've been editing for months.

I see an earlier DRS version I had previously used, referenced in the log:

Resolve 14.3.0.005 [remark: patched with14.3.0.005 database upgrade]

(Could it be I screwed up and mixed up my databases?)

~~~

Any suggestions describing process of prepping for, and performing a reinstall of version 14.3 is appreciated.

Thank you gang.

RS 14.3 | MiniMonitor | Samsung U28D590 via Spyder5 Pro | DTV 10.9.7 | Win64 8.1 | ASUS ROG G751JL, Intel i7-4720HQ, 24GB, 1TB HDD, 500GB SSD, GTX965M | Mackie MCU Pro | Softube Console 1 | Shuttle Pro 2

UPDATE:
All OP issues with Resolve detailed in this message thread, are now fixed!
• No reinstallation required!

See bottom half of Post #8 for problem and solutions summarized in brief form.

Special shoutout with hanks to Dymitri and also to Peter C.

Stop.
~~~
Optionally, go to 2nd half of Post #8, just below the symbol for summary of problem source and remedial solutions that worked.







Running DRS v14.3.0.014, and in dire need of completing and delivering heavily edited project.

Now Fixed:
All Resolve 14.3 issues described in this thread by me (Issues #1, #2 and #3 -- have been remedied, and solutions summarized in brief form, on the lower half of Post #8 within this message thread, as a potential aid to others.

Now Fixed:
☡Crash Scenario 1: Resolve now always hangs in a silent crash after attempting to move an audio track up or down (moving video tracks up or down is Ok).


Now Fixed:
☡Crash Scenario 2: Resolve hangs, when "Save As..." is instantiated.

Now Fixed:
☡Crash Scenario 3: Sometimes hangs when started while I have Console 1 (MIDI audio control surface) On-Screen Display software running prior to launching Resolve...[/quote/]

Update: Progress was achieved after disabling then re-enabling key device items -- especially the WindowsMM Output device under Device Manager > Sound, video and game controllers, then restarting the PC.

Both MIDI Control Surfaces are now happily residing and damaged media files and .drp project file have been restored from back-up files.

RS 14.3.0.014 | MiniMonitor | DTV 10.9.7 | Win64 8.1 | ASUS ROG G751JL, Intel i7HQ, 24GB, 1TB HDD, 500GB EVO 850 SSD, GTX965M | Mackie MCU Pro | Softube Console 1 | Shuttle Pro 2

☡Crash Scenario 2: Resolve hangs, when "Save As..." is instantiated.

How did you fix that exactly? It happens to me every time File Explorer is invoked by Resolve.

Hi guys, crash logs.. only those generated by Resolve.. the full zip please.
viewtopic.php?f=21&t=69837

Peter Chamberlain wrote:Hi guys, crash logs.. only those generated by Resolve.. the full zip please.
https://forum.blackmagicdesign.com/view ... 21&t=69837

Thanks. I posted a new thread with a Resolve-generated Diagnostics Log from the Resolve Help Menu as required.

RS 14.3.0.014 | MiniMonitor | DTV 10.9.7 | Win64 8.1 | ASUS ROG G751JL, Intel i7HQ, 24GB, 1TB HDD, 500GB EVO 850 SSD, GTX965M | Mackie MCU Pro | Softube Console 1 | Shuttle Pro 2

Eugenia Loli wrote:

☡Crash Scenario 2: Resolve hangs, when "Save As..." is instantiated.

How did you fix that exactly? It happens to me every time File Explorer is invoked by Resolve.

I did many things in a quest to eliminate my "SAVE AS" operations causing Resolve to crash, but it seems the most impactful remedies likely were:
1. Getting rid of an obvious conflict with my 2, connected, USB MIDI surface "controllers" by one at a time, Disabling then (re-)Enabling their drivers in Device Manager > Sound, video and game controllers.

2. Restarted Resolve but did so, by opening a previously saved version of the project, using an alternate Database I had saved an earlier project version under.

3. Cleared all unused cache
4. Performed another "Save As" (project) operation and also
5. Exported Project (saving that on another drive as a safety backup)
6. Cleared all Unused Cache (from the Playback Menu)
7. Clicked Project Manager icon (little "house" icon, lower right corner of Resolve's user interface and backed up this current state of the Disk Database.

To be candid, Eugenia, those things were done by a series of intuitive guesses on my part, as I'm relatively new to Resolve, and new to working with an NLE that utilizes a database paradigm for preserving project properties.

Perhaps some of this is enlightening, even if the MIDI "controller" devices conflict I had (which at times, also prevented Resolve to do a regular "Save" or even prevented Resolve to start up) may not apply to your situation.

Sent from my P00I using Tapatalk

Peter Benson wrote:Perhaps some of this is enlightening, even if the MIDI "controller" devices conflict I had (which at times, also prevented Resolve to do a regular "Save" or even prevented Resolve to start up) may not apply to your situation.

I think it's gonna be tough trying to chase down a problem when you have non-supported hardware, like the MIDI controller. It's hard enough when you're using a Tangent or Avid or even Blackmagic controller. Once you throw something in totally non-standard, the potential for weirdness is bound to increase.

Marc Wielage wrote:

Peter Benson wrote:I think it's gonna be tough trying to chase down a problem when you have non-supported hardware, like the MIDI controller. It's hard enough when you're using a Tangent or Avid or even Blackmagic controller.

Once you throw something totally non-standard, the potential for weirdness is bound to increase.

I hear you loud snd clear, Marc though that's not completely the case for the MIDI controllers-connected Resolve system here. To wit:

MIDI HUI and MCU protocols are indeed standards Blackmagic Design has advertised [at least basic] support for, since the days of Resolve 12.5 or perhaps even a bit earlier for one or the other.

And to that end, both MIDI devices here run happily and agreeably in Resolve 14.3.0.014, simultaneously and without issue at all -- except BMD ought to hire someone to finish implementing at least "basic" (sic) support for MCU Pro controllers for their Bkackmagic Design promotional material to earn credit for plausibility in regard to [basic] "MCU Pro" support.

IMHO, it ought to be that at the very least, with MCU Pro connected to a Resolve host computer via USB MIDI [MCU protocol especially -- but maybe, just maybe in the more-limited HUI protocol]...

• Timecode display should not only illuminate (as it indeed does), but it needs to advance past 0:00:00:00 -- and run on every page in Resolve. It does not advance in Resolve 14.3 at all!
• Master fader should work (it does not at all! It should ve that Resolve PREFERENCES permits users to map the MCU Master FADER to whichever FAIRLIGHT/EDIT Audio Buss we desire -- especially MAIN 1 Out should be Master Fader controlled by default.

So Marc, I give you points for politely inferring BMD's need to address incomplete support of "Resolve-supported" controller devices, at least, and most especially in the realm of some basic operational features on Mackie MCU Pro Universal Surface Controller.


Stop

~~~

For related success story and Windows 8.1 OS "Forced-Update Attempt" and resultant disk drive and Resolve Files Damage intrigue, and how I overcame this monstrous disaster involving nearly 1,000 media files in the timeline, read on...


I finally tracked down the source of my Resolve 14 Save/Save As crashing and failed Startup issues to
• Windows Multi-media MIDI Output file dysfunction, caused by Windows 8.1 Home attempting to shut down all running applications (including Resolve while rendering!)
Resolve stood still in a silent crash, and subsequently media files, project file and a brand new G-Drive USB-C 4TB rendering target drive were all damaged.


Solutions:
• Disabled, then re-Enabled several pertinent MIDI device drivers one at a time
• Replaced the new drive, damaged by the unexpected Windows OS Update attempt (thankful I had WiFi switched to "Off" so Update never occurred, but a read of a log in the Windows Event Viewer suggests Windows shut Resolve and other apps down in defiance!)
• Restored project and some corrupted media files from earlier-produced back-ups.

RS v14.3.0.014 | MiniMonitor | DTV 10.9.7 | Win64 8.1 | ASUS ROG G751JL, Intel i7HQ, 24GB, 1TB HDD, 500GB EVO 850 SSD, GTX965M | Mackie MCU Pro | Softube Console 1 Hdwe/Softwe Audio Plugin | Shuttle Pro 2

Peter Benson wrote:I hear you loud snd clear, Marc though that's not completely the case for the MIDI controllers-connected Resolve system here.

If you're going to use Resolve for mission-critical work, I would strongly advise you to use a Tangent, Avid, J.L. Cooper, or Blackmagic panel (all of which are selectable in prefs). Anything else is going to be buggy -- in my opinion. There are affordable options out there.

Having said that: I have used a standalone XKeys (and eventually an Elgato Streamdeck, when I get around to it) with Resolve, but those just store keystrokes and mouseclicks, nothing more. As far as Resolve is concerned, I'm still using a mouse and keyboard. I would be lost without a physical control panel for actual color, and it's too important for me not to use one specifically supported by Resolve.

Marc Wielage wrote:

Peter Benson wrote:I hear you loud snd clear, Marc though that's not completely the case for the MIDI controllers-connected Resolve system here.

If you're going to use Resolve for mission-critical work, I would strongly advise you to use a Tangent, Avid, J.L. Cooper, or Blackmagic panel (all of which are selectable in prefs). Anything else is going to be buggy -- in my opinion. There are affordable options out there.

...I would be lost without a physical control panel for actual color, and it's too important for me not to use one specifically supported by Resolve.

Gotcha. That opinion is yours for the record, although a patently unfair sweeping generalization to the 3 Resolve-connected controllers in use here, and likely other controllers not on your faves list.

Disparaging presumption of inferior or "buggy" interaction with Resolve aside, my experience and that of others, including users of the Akai APC Mk i contrtollers adapted for wildly-comprehensive use with Resolve, yes, even on mission-criticsl work assignments gives us solid basis for resoundingly disagreeing with any sour grapes put-down of our controllers.

If your assertions were tested against the last 3 products listed in my signature, I'd eat my Shuttle Pro 2 if any of the 3 exhibited buggy behavior as you might have our readers believe.

1) Softube Console 1 [C1] is simply an exceedingly efficient software/hardware VST plug-in for faithfully emulating the sound characteristics and knob twirling experience encounteted from a coveted SSL 4000E British mixing console at a modest cost of under $500USD that uber-easily integrates into Resolve (because Resolve sipports VSTs -- with absolutely NO Resolve preference settings needed -- or available at all, for Console 1 to work as an Audio Plugin and Surface Controller.
It truly is "Plug and Play".

2) Mackie MCU Pro is a surface controller suitable for tactile management of audio recording, mixing, and mastering duties within NLEs and DAWs. When plugged into a Resolve host computer with driver instslled, needs only a 7 sec. trip within 3 little Resolve Preferences settings to get connected as an Audio Surface Controller.

Resolve Preferences automatically provides this little 3-line interface for MCU Pro hardware interoperability, once its firmware is installed and plugged into USB:
• MCU or HUI]?
• MCU Pro MIDI Input
• MCU Pro MIDI Output

MCU Pro is explicitly supported by BMD for Resolve since version 12.x -- and it is not buggy -- only the gurus at BMD have not yet[i]nearly given it the basic modicum of support it utterly deserves, just yet.

Console 1 with Resolve is simple. Point its driver software to the Resolve executable file and load the Resiolve Preset in the Contour applet.

STOP.
~~~
Here's more for those intrigued...

The Softube Console 1 is course indirectly "supported" (sic) by BMD because it is in fact a VST2/VST3/AU/AAX plugin accompanied by a dedicated surface controller (although running the Console 1's included "SL 4000E" channel strip emulator plug-in software was painstakingly modeled in tight adherence to the circuitry characteristics of an actual British SSL 4000E mixing board -- that plug-in does not even require the use of its hardware controller, once you have it "authorized" -- and that novel plugin combo just works, plug and play with no MIDI setup routine required at all -- to work with Resolve.

Biggest bonus for users is its exceedingly low latency or demand on the CPU, despite instances of that plugin on every channel you're likely to thow it on.

Softube recommends that every audio track and every audio buss, be
loaded eith tge Console 1 plugin.

Recording, Mixing, and Mastering while listening to its mindblowingly awesome impact on Resolve's audio tracks for, ssy, a video shoot of a live concert -- or even adding the characteristic warmth to s simulate vocal dialogue ovee expensive hardware is ridulously fast, intuitive and fun.

to every on e quite quickly is nothing short of breathtaking in Resolve --
did I mention latency
cy is superbly miniscule, despite the manufacturer encouraging it be loaded on every track, in a template project gor easy access when a new project is launched?

Suspicions aren't warranted with Ct, nor MCU Pro. MCU over USB MIDI is a tried and true protocol that works with aplomb.
2) Mackie MCU Pro uses MIDI MCU protocol for speedy, tactile console-like control of SOLO, MUTE, FADER, FADER AUTOMATION, PAN, Track SELECTion (plus scrubbing and the usual transport controls for use in the Fairlight page at least for now).

3) Contour Shuttle Pro 2 controller is for placing Resolve shortcuts within easy reach

Mackie MCU Pro Universal Control Surface | Softube Console 1 | Contour Designs Shuttle Pro 2

Peter Benson wrote:
☡Crash Scenario 1: Resolve now always hangs in a silent crash after attempting to move an audio track up or down!

I have been getting a silent crash or frozen Resolve when moving audio clips to different tracks in Fairlight. This is with version 14 & 15. I wondering if it might be when moving from a mono to a stereo track or stereo to mono but I need to do some testing to see if this is constantly the problem.