Version 16.0.0B.033 Issues and Nuisances

*** Editing Original post to add responses and save others time later ***

Stability: SplitClip = Ctrl+\ - Behavior inconsistent.
Ctrl+\ - Does not work when the timeline pane has focus (red line indicator), but clip is not highlighted.
Ctrl+\ - Does work when a clip is explicitly highlighted (with a red outline on clip), but this requires mouse activity rather than keyboard-only editing.
Conclusion from Responses: Expected behavior.
Change Request: As an editor using the Edit Page, I'd would like Ctrl+\ to insert a cut at the pointer regardless of what potion of the Edit Page has focus.


I & O Placement Edited 6/26/19 to be as precise and concise as possible.
Change Request: As an editor using the Edit Page, I'd would like a preference for either
(a) The O point to continue to be placed where it is relative timeline pointer as per tradition.
OR
(b) The O point to be placed at the precise timeline pointer location. This option is simply requesting O have identical placement behavior as that of I relative to timeline pointer location.


^^^The two issues above are the most productivity-affecting. ^^^

Stability Audio 'Speaker Configuration'
Audio 'Speaker Configuration' reverts to set ups other than the last one used or specified. It appears user preferences are not consistently being written or are being overwritten. Bottom Line: This setting is volatile AND manual corrections do not work.
Workaround: Configure the 'Monitor Set' that Resolve insists on using as the default to the desired settings. Set and forget, this workaround is fine

Stability: Audio Waveforms
Waveforms do not appear in Edit window most of the time.
Other times they do appear. Cannot discern what differentiates this behavior. Timeline settings are correct to show waveforms. They do appear in some timelines, but not in others.
Conclusion from Responses: Known bug. An inconvenient workaround exists.


Nuisance/Bug: Renaming in Windows
Cursor not visible when renaming clips and timelines and this requires extra effort to locate it.
Conclusion from Responses: Known bug. Very annoying not to be able to see the cursor location.


Nuisance (Audio): Audio Settings
Changes to Audio Settings requires a full application restart.


(EDITED) Nuisance (Startup Load time): 'Looking for Control Surface'
I don't have any Control Sufaces, but Resolve spends ~10 seconds at each startup looking for them. Please have the software check the following user settings and skip the control surface checking operation for those that == None
Preferences > Control Panels > Color Grading Panel = None
Preferences > Control Panels > Audio Console = None
Conclusion from Responses: Known Concern. Confirmed by others

Nuisance (Startup Load time):
Could Resolve be made to start by loading just the last page the user had opened last? Then open other pages on an as-needed basis? I spend most of my time in the editing interface and don’t mind the hit on the first of each subsequent context change.
Conclusion from Responses: Not possible due to inter-dependencies between pages.

Text: Using Font Awesome,
In dialogs, Text is (represented/aliased) as squares but appears as intended on-screen.

I & O - Handles 'Greedy' wrt Titles
Where a title and a clip are aligned and O is set on the boundary with the preceding clip, the O point is interpreted as inclusive of the first frame of the title. Therefore, when the I to O segment is deleted, the title is deleted as well. Please prevent the O marker from surpassing the exact point at which the pointer is located.

There are two conventions with I/O points: last inclusive and last exclusive. I don't know if resolve has a toggle, but I remember other software had it. I got used to it... it will screw me over if it changes !!

Nuisance/Bug: Renaming in Windows
Cursor not visible when renaming clips and timelines and this requires extra effort to locate it.

I saw this very often in LINUX and it is annoying as hell...

Nuisance (Startup Load time):
Could Resolve be made to start by loading just the last page the user had opened last? Then open other pages on an as-needed basis? I spend most of my time in the editing interface and don’t mind the hit on the first of each subsequent context change.

the machine start with the last page and the last timeline only. Isn't the case in your end?

An Out point should land precisely where the pointer is located; not one frame over.

Ctrl+\ - Does not work when the timeline pane has focus (red line indicator), but clip is not highlighted.

I can't reproduce that on Studio 16b4 for Windows. It's working properly here.

The Out point is working correctly. The playhead always looks forward one frame, so if you place the playhead at the end of a clip to make the Out point...

Waveforms do not appear in Edit window most of the time.

viewtopic.php?f=32&t=92288

Ctrl+\ - Does not work when the timeline pane has focus (red line indicator), but clip is not highlighted.

I can't reproduce that on Studio 16b4 for Windows. It's working properly here.

I see it on some timelines but not others.

The Out point is working correctly. The playhead always looks forward one frame, so if you place the playhead at the end of a clip to make the Out point...

I'd prefer the Out point land precisely where the pointer is located; not one frame over. I understand other have other preferences (see above). A preference toggle would be ideal.

I'd prefer the Out point land precisely where the pointer is located; not one frame over. I understand other have other preferences (see above). A preference toggle would be ideal.

Older editors would most likely be adherents to the old convention that the 2 points nominated for an edit (the in and the out) are the first frame you want and the first frame you don't want. It might have been a CMX thing or even earlier (was there earlier? I used some beast called a Dataton or Datatron).
As Walter said, it would mess with a lot of people but an option to set it as a policy would be good.

I'd prefer the Out point land precisely where the pointer is located; not one frame over.

It is landing precisely where the playhead is located. But when you shortcut to the end of a clip, you're actually looking at the first frame of the next clip. You have to back up one from before setting the Out point.

This is SOP for NLE's.

Notice the Control Surface thing. Its 9 seconds on my machine... About half the load time of Resolve. Is there a way to shut this search off (config file, etc.)?

Also, the load time is quite long. Almost never want to close the app, because it takes so long to boot up.

Backloading pages wont work, due to how clips on Edit can reference functionality on other pages.

The more pages they add, the worse it gets...

Ctrl+\ has two different modes -- if a clip is selected, it will cut that clip, and only that clip.

If nothing is selected, it will cut every clip at the playhead, but only if the auto-selector for that track is on.

And as already noted, the "out" behavior is consistent with tradition. If you want to cut inclusively to the last frame of a clip, you'd use the apostrophe shortcut to get there, not next or previous, which takes you to a new cut.

Jon,

With this many issues being listed it would be helpful if you would list the hardware setup you have in your edit system. This will help others deduce the issue source if they're using the same or similar setups.

The Out point is working correctly. The playhead always looks forward one frame, so if you place the playhead at the end of a clip to make the Out point...

I'd prefer the Out point land precisely where the pointer is located; not one frame over. I understand other have other preferences (see above). A preference toggle would be ideal.

Most people get confused because the edit point is actually BETWEEN frames, like a strip of edited film. When you step to the end of a clip, Resolve steps to the first frame of the NEXT clip. It IS precisely where the pointer is located. This is very common in most editing software. Avid has an option to stop on either the last frame of a clip or the first frame of the next clip, but the CURRENTLY VISIBLE FRAME is always included.

Most people get confused because the edit point is actually BETWEEN frames, like a strip of edited film. When you step to the end of a clip, Resolve steps to the first frame of the NEXT clip. It IS precisely where the pointer is located. This is very common in most editing software. Avid has an option to stop on either the last frame of a clip or the first frame of the next clip, but the CURRENTLY VISIBLE FRAME is always included.

I am requesting for an *option* to be added for 'O' to land exactly where the pointer is... VISUALLY within the Edit Page timeline. IOW act just as 'I' does and land where it's placed. Hopefully that is clear.