Barrie Williams
Forum Replies Created
-
Sascha makes an excellent suggestion.
In scene detect , We really need a minimum length between cuts so strobing images don’t create a huge number if pointless cuts.
I had a 30 minute program yesterday which detected 2000+ scenes when there were really only 300.
-
hi Jamie,
please read page 3 under Snapping
or just press the “N key”, i think that is what you are asking.
-
I have jlcooper and elements panels here. Since the elements panel arrived I have not turned on the JLCooper once.
Having a reset button built into every knob ball and ring makes it a great time saver for us.
The mapping is in need of a little more work by davinci, but its pretty good .
I love my elements panel. I can’t say the same about the jlcooper.Doubtless the resolve original panel is superb, but its the price of a car.
Barrie. -
AWESOME!
barrie
-
Rohit.
I forgot to mention this when we chatted , but this solution is not available in 3d because it corrupts the hdsdi output.
Barrie -
First set playback settings to 8 bit instead of 10…
Then try full screen playback.Barrie
-
It is not broken.
I thought it was broken until I learned how to use the wildcards in the EDL helper string.
The best facility is the “test” button… Set the full file path WITH filename, then Press TEST to see what Davinci is seeing as the reel name. If you see no reel name, you have done it wrong.
Barrie
-
Open the EDL in text editor, double check that reel numbers are in EDL .
If they are there, then look at manual on EDL helper, especially the wildcard characters . It’s a little tricky but there is a “test” button so you can quickly check what DaVinci is seeing as reel number.
You will need to turn on the helper as it is not enabled by default.
In case you wonder where I get this incredible knowledge … I read the manual !
😉
Barrie -
Oh yea please
I spend much time deleting wrong cuts that would not be there if we had a minimum detect period.
Barrie -
Not just Alexa, it does the same on prores too.
I reported this when v9 was released. It’s a screen redraw resource issue which was not in v8.
You can get full speed playback by using full screen mode, or switching from clip nodes to track nodes, or even on OSx swapping screens so resolve is running off screen.
I spoke with the dev guys, and reading between the lines I believe that the new graphics cards to replace the gt120 will cure this bottleneck.
Barrie