Resolve 12.5b broken Color Setting in the Dip To Color Dissolve (Yes I know it's beta.)

The Dip To Color Dissolve behaves erratically in Resolve 12.5b causing the app to crash. In the Inspector, the Color Setting doesn't show properly, any attempt at modifying the Color while in this state will result in a crash.

After several attempts at replacing the transition, the proper display of Color will show, and things will be fine - no more crash.  Eventually, after a crash, the Color setting will show its normal state.

Erratic behavior1:

 The Color setting has a slider and a box with "0.000" in it.

Erratic behavior2:

The Color setting displays a slider and a box with "--" in it.

Any attempt at modifying the Color in both cases will crash Resolve.

Normal behavior:

Here it shows its normal state, clicking on the rectangle opens the color wheel, and all is fine.

Color wheel pops-up on clicking the rectangle.

Premiere Pro 9.2 to Resolve 12.5b via FCP xml

Good news: Export Final Cut Pro xml works well.  Cuts are accurate, speed changes (including keyframing) are accurate, L and J cuts, scaling is accurate (including keyframing.)

All these work equally well on Merged Clips, ah!  I just transferred a small 30sec. project, so nothing big, we'll see how it goes with longer projects.

Retime preferences need to be reset in Resolve, as the Premiere settings do not translate.  No biggie.

Cross-dissolves translate perfectly and can be modified further into Resolve.

On the other hand, Dip to black dissolves translate fine, Dip to White dissolves turn into Dip to black dissolves for some reason.

You'd think: Easy enough to change them back to Dtwd I'll select the transition, open the Inspector, change Video Transition Style to something else, then select Dip to Color Dissolve again...  Nope.

Any attempt to change the transition either results in instant CRASH, or the BALL OF DEATH or if you're lucky enough to be able to open the Inspector panel, the Color Setting will CRASH Resolve. Interestingly enough, sometimes after the crash (but not always), the Color setting behaves properly... Go figure.

Note that after a crash, the Resolve Project comes back as it was the last time it was saved.  You will loose anything you've done between the last save and the crash. You've been warned.

I then tried to purely replace the Dip to Color Dissolve with the Resolve flavor... Well this transition appears to be BROKEN in 12.5b.  The Color setting behaves erratically, and when the Color does not appear, there is instead a slider with a box and "000" in it. Trying to change that value will crash.  Eventually after a few attempts replacing the Dtcd, the proper Color setting shows up: a rectangle with the selected color in it.  Clicking on the rectangle will open the color wheel.  So it's all Resolve fault.
http://humanuser.blogspot.com/2016/04/resolve-125b-broken-color-setting-in.html

DaVinci Resolve 12.5b

Kicking the tires of Resolve 12.5b:

- Much more responsive! I think BMD and Adobe are busting their chops to reduce FCPX advance, and that's a GREAT thing!

- Better playback speed, good. Although with some thingss like file overlay it chokes like before.

- The file overlay is not resized when changing frame size, not at the Project, nor at the Clip level. That needs to be fixed. Something I do often: work on the full size Timeline, insert a full size overlay, render a half size Proxy with burned-in overlay. Well the overlay does not get resized by half. Not right. By contrast, the "build-in" overlays, like Source TC, etc. do resize properly.

- And by the way, I would like to have a better preview of the output BEFORE hitting Render.  Adobe does it, one can even compare Source/Output, I would like to see this implemented in Resolve.

- Seem to me that rendering speed is improved as well, not by a lot more, but somewhere like 1.5 possibly, one and a half time real time, as opposed to real time before for a similar rendering task.

- Waveform display in the Viewer, multi Composite modes, yeah!  Full screen Playback, cool!

- The Auto-Sync works fine, I would like to be able to fine-tune the audio after it's been merged though. Except in Clip Attribute where there is a vague "Linked Audio", or in the Media Pool where it shows 4 channels (fro ex.) instead of the Clip 2 channels. I would like to be able to quickly see in the Media Browser that any Clip has synced audio, and the name of the audio clip attached.

- Fine tuning of the synced audio is possible in the Media Pool: Show the Audio Offset Column, and it will display (in Sec. and 1/100th of a Sec?) the Offset applied to the audio file.  Double click in this box, and you can adjust the value for perfect sync.

- There is also a convoluted way of doing it via the Media page, with the audio tab open, use Option Comma/Period to offset by one frame before/after, or Option Right/Left Arrows to offset by 1/10th of a second.
In my test, I can only offset one way: in advance with Comma and Arrow Left.  Period and Arrow Right seem to be non operant.  Maybe a bug?
The biggest bug is that it has no provision for appending tracks... It replaces the embedded tracks with the separate ones - Even if I first Auto-Sync to append audio...  So for appending tracks, the above Fine Tuning is the only viable one. For now.

- There is a way to add Timecode to a non Timecoded Clip (from TC less DSLR say), LTC recorded onto the camera audio track will be used to generate a Timecode track - Right-click on the clip and select "Update Timecode from Audio-LTC." I got to try this.

- Note on audio recorded without Timecode: Set the Timeline Frame Rate in the Master Project Settings BEFORE importing the audio, else just like FCP legacy, Resolve will stamp the imported audio to the FR of the Settings - and then audio will eventually DRIFT if on the wrong FR.  Double check Frame Rates for all clips in the Edit page /Media Pool.

More to come.

BMD DaVinci Resolve 12.0, 12.0.1 and 12.2.2 on Mac - What a pain!

RESOLVE 12 (and 12.0.1) BUGS AND AGGRAVATION

- Crashes A LOT !!!

- Crashes when deleting or duplicating a Timeline (opened or not.)

- Takes forever to load a project and to save a project, and there is a long lag after the save window closes and before you can get back to work without any kind of feedback (is it doing it?) Each time you save you loose 1min. Each day you loose hours.

Apple is leading the charge in terms of functionality, EVERY SINGLE PRO APP must be saving in the bkg like FCPX does, save your every move until the last before the crash, and restore the project to the last move so that you do not loose anything.

- With Resolve 12, one looses work when the app crashes.  Again, should be like FCPX: nothing is ever lost when it crashes. Not only but you have to go through this cumbersome loading of backup projects from the Settings window / Auto save. Why can't backups be accessed from the Project Manager window????  This takes too long and is unnecessary. Just save the damn project once properly and do not corrupt project files to start with.

- Sometimes it crashes without telling you it does, great, project gone, app closed. You come back to the Projects Manager window and they are new projects files here... Or EMPTY Sequence Containers, all with weird names.  Open your project just saved a moment ago you will see that ALL THE TIMELINES ARE EMPTY!!!!  What the hell is that?  Yet again, the only way to go back to your hard work is to load a backup project.  Forces you to auto-save every 5min. (and of course loose 1min. every 5min.)  Still you've lost the last 5min. of work.

- There are ghosts lines that appear in the Node window, making it hard to visualize links.

- Copying a grade to another clip or multiple clips in the Timeline hangs/crashes the app once in a while.

- When mouse-dragging a value drastically (like Saturation) the timeline jumps to some random clip before or after the one you're working on. Yes, I do drastic moves sometimes. This is a pain, please fix this behavior.

I will continue to vent my frustration here as I battle Resolve 12, otherwise a great app... If only it would WORK!

--- Update and more aggravation ---
Updated to v12.0.1 ... promises more stability... right... Nope.

- I need to EDIT the Timeline (1), supposedly that's what Res is all about now, but when I select a large number of audio clips (that are unlincked from video) and delete them, it crashes. Great!

- I need to EDIT the Timeline (2), but when I select a single clip and try to Trim Edit, it crashes. Awesome!

-  And now it crashes on loading the project... This can't be better!

- All right, reloading a recent backup through the stupid Auto Save page...

- Project opened, worked on, saved several times, closed, opened again, all is well.  Except I cannot use anything but copy and paste, select and move clips around, delete one or two clips her and there, and that's it.  Any attempt to Trim, delete a bunch of clips.... Crashes the app immediately.

- Project saved the day before, opened the following day ... make the app CRASH. I'm pretty sure it has to do with the dreaded "this project has not been saved..." etc. bullshit message that pops up without any reason - I just saved the Project and waited 3 min. before closing to be sure.  But no, it had to ask again, all right, I clicked SAVE, I had to close Resolve what else can I do?  What do you know, instead of saving, it CORRUPTED the Project file.  Well thank you so much.  Yet again, back to restoring an Auto Saved Project... And making sure all your last moves are still in there. Great way to start your day.

--- More updates and more aggravation ----
Another thing that's driving me CRAZY!  Why does UNDO work on certain things and not others???  If I do a color correction, and then I do a resizing and undo, it ONLY undo the CC, not the resizing.... What?  This is utterly confusing.  Please undo the LAST MOVE whatever it is, resize, tracking, pasting...  Or at least give us the option to choose what gets undone.

--- Update
So I installed RESOLVE 12.2.2, created a project.  Then I quit the app, came back a few minutes later, tried to open the project I just created... It CRASHES. And again generates the stupid ".tmp" files ad nauseous.  At least the auto-generated ".tmp" opens fine.  But then I have to do the dance: trash the original project, rename the ".tmp"... Pfff, come on BMD, fix the code please.

--- What's your experience with Resolve12.x.x on Mac?
I know my config is not optimum: MacPro 5,1 Quad, OSX 10.10.5, AMD Radeon HD 7950, Dual 1980x1080 displays, Decklink Mini Monitor PCIe, Desktop Video Utility 10.5
II am OK with real time (or less than) rendering, I'm only dealing with HD ProRes files, not exotic formats.