Page 1 of 1

Resolve having a meltdown?

PostPosted: Sat Dec 09, 2017 12:43 am
by John Whiteway
Wondering what's happening. As I've been editing away several of my key strokes and menu clicked instructions have stopped working and I don't know why.

Here are just a few examples:

The Match Fram icon and the letter F no longer reconnect me in the source window with the clip and the frame the cursor is on in the timeline
Option Y or clicking the instruction in the menu will no longer highlight all the tracks forward, just some or sections of some
Control + or - will not increase or decrease size of tracks in timeline
Control T doesn't place a transition on audio edit
Right clicking on an audio edit and choosing one of the fade options always produces a video dissolve as well

I'm working with a new IMac that should be able to handle all Resolve throws at it (Processor: 4.2GHz Core i7, 8Gb; Memory: 2400 MHz DDR4; Graphics Card: Radeon Pro 580 8192 MB).

I've been loving learning and working with resolve but these problems have me stumped.

Thanks

John

Re: Resolve having a meltdown?

PostPosted: Sat Dec 09, 2017 12:44 am
by John Whiteway
Oh yes -- I have Keyboard mapping set at Resolve

Re: Resolve having a meltdown?

PostPosted: Sat Dec 09, 2017 7:06 pm
by John Whiteway
Think I've solved most of my problem.

I'd been working with a Timeline a bit over an hour in length and it was full of short clips. I've just made five new timelines, each taking a portion of the entire piece, and now most key stroke and menu options seem to be working. Would seem I just had too much going on in my long timeline and once I'd begun working with transitions, etc. it was proving too much for Resolve to handle. Good leason learned I think.

But though when I select things like "all tracks forward" or "match frame" they are working for me now, some of the key strokes and menu instructions that had never worked still don't work.

"Control + or -" doesn't increase or decrease timeline size. While "Timeline/Add Audio" as a menu selection does create a fade at the selected edit point, its key stroke "Control T" does nothing. Also, if I hover over the audio edit and then choose an audio fade from the sub-menu that appears, a video dissolve always is always created as well. Only way to stop that is to lock the video track first.

So, though the main worrisome problem seems gone I'd still love to have these other functions work too.

John

Re: Resolve having a meltdown?

PostPosted: Sat Dec 09, 2017 9:33 pm
by PeterMoretti
John, for zooming, have you tried Ctrl with the + and - keys between the 0 and Backspace keys? (Not the + and - keys on the numeric keypad.)

Re: Resolve having a meltdown?

PostPosted: Sat Dec 09, 2017 11:08 pm
by John Whiteway
Thanks for the reply Peter.

Actually it has been the + & - between o and delete I've been hitting. Just tried it now with the + & - on the numeric pad. Still nothing I'm afraid.

John

Re: Resolve having a meltdown?

PostPosted: Sat Dec 09, 2017 11:46 pm
by Uli Plank
8 GB RAM is just the bare minimum for Resolve. I'm running the same machine with 24 GB and have not experienced any problems like the ones you describe. Also editing one hour long pieces with lots of short clips.

Re: Resolve having a meltdown?

PostPosted: Sun Dec 10, 2017 12:14 am
by John Whiteway
Thanks Uli.

I'll add lots of RAM and see what happens.

John

Re: Resolve having a meltdown?

PostPosted: Sun Dec 10, 2017 3:15 am
by PeterMoretti
John, I would go into DaVinci Resolve... Preferences... User... Keyboard Mapping... View... Zoom

And see what it says is assigned to Zoom In and Zoom Out.

While on that page, you could also change Search from Command to Shortcut, and in the box to the right type Ctrl + and see what comes up.

Good luck.

Re: Resolve having a meltdown?

PostPosted: Sun Dec 10, 2017 5:59 pm
by John Whiteway
Thanks for the advice.

I went to the Keystroke page and it turns out the Timeline expansion or contraction keystrokes are set to "Command + or -", not "Control + or -". I'm pretty sure I'd read it should be "Control + or -". Or maybe I'm just so used to using that from Final Cut.

Now if I could only figure out why highlighting an audio edit and selecting the fade length from the little pop-up menu always produces a video dissolve of equal length as well - that is unless the video track has been locked first.

As for the keystroke instructions for dissolve or fade, I was at fault here. I was misreading the upward arrow of the keystroke to mean Control rather than Shift. So no problems here.

Thanks again.

John

Re: Resolve having a meltdown?

PostPosted: Sun Dec 10, 2017 6:47 pm
by PeterMoretti
John, I believe the general convention for dual platform programs is that everything that is Control in the PC world is Command in the Mac world.