Paul Draper
Forum Replies Created
-
In sum: Resolve can simply export and import individual projects via a right-click in the Project Manager window.
Open the DR Project Manager window, right-click on a project and ‘export’ each of these in turn to the relevant media folder. That’s pretty much exactly the same as a ‘save as’ in any other app. Project folders can then be moved around to other drives, backed up, archived etc. One tip: rename each of these files to be the same as the project name; Resolve defaults to naming each of these with a generic ‘project’ title. That wil help later (below) when you re-import each of these into a new DB.
Do that for all projects, here in this context or in any other for that matter. And that is a ‘backup’ beyond this DB versioning matter.
*Clean* uninstall DR Resolve 16 beta, ie, get rid of all prefs, related install folders etc. On Windows, something like ‘IOBit Uninstaller’ does a good job; then clean registry (say ‘CCleaner’), then reboot. Same process for Mac OS, something like ‘CleanMyMac’ can do clean uninstalls. Otherwise, just do it manually if you know where to look in all the usual places. Delete all DBs for 16.
Reboot, install DR 15.3.1 (latest, very nice). Set up the various prefs as usual. Open the Project manager, then ‘Import’ individual projects by right-clicking on the Project Manager window space and selecting each of the above ‘saved as’ export files in turn. When that’s all done, then there will be a full /new DB file again. Depending on the location of the original media files, you many need to point the project at the most recent path and/or link files in the Media page.
Dell T7910 workstation, Win10x64 Pro; 64GB Ram; 2x 12 core Xeons; Nvidia 1080Ti; LG 34UM95 & BenQ SW2700PT, BM DeckLink Mini Monitor 4k. Audio: RME Fireface UFX+, RME ADI-8, UAD-2 quad core PCIe. Resolve Studio, Adobe Premier, Nuendo, ProTools HD.
-
Yes it does, but is directly related to the CPU & GPU processing power.
I work with native GH5 codecs & rarely transcode given the wait time involved & the extra storage space required.
FWIW, you do not need a third party app to transcode to say ProRes or DNxHD: Instead use Resolve’s built-in Media Manager to convert the camera files to a format /dir of choice.Dell T7910 workstation, Win10x64 Pro; 64GB Ram; 2x 12 core Xeons; Nvidia 1080Ti; LG 34UM95 & BenQ SW2700PT, BM DeckLink Mini Monitor 4k. Audio: RME Fireface UFX+, RME ADI-8, UAD-2 quad core PCIe. Resolve Studio, Adobe Premier, Nuendo, ProTools HD.
-
No, you get complete mixing there, ie, no ‘limitations’ etc (assuming no silly post-prod extremes have been committed in the Resolve timeline) – its *only audio* Wav multichannel. eg:
Export a QT movie with (say) 4 x stereo tracks (using Timeline IDs in Resolve);
Import the vid into the DAW (Nuendo or Pro Tools here), import automatically extracts the 4 x stereo tracks onto individual lanes & pus the vid in a video track.
Next I label & colour code each audio track, then ‘Strip Silence’ – Many DAWS use this also to maximise plug-in, CPU power, ie, the CPU backs off when there’s no audio on the lane.
The stripped clips are then completely manipulable via the usual clip gain, handles, fade curves, cross-fades, in-line processing, whatever.There is zero difference between that audio import /mixing and using AAFs (save for the fact that the AAF can often have problems with handles or conversely, than Resolve doesn’t always accurately mirror its own lane fades/ edits to AAF).
In the case of the multitrack QT bounce, none of that is an issue because you are simply printing each audio lane to a QT audio track and this mirrors the existing Resolve temp mix exactly. One bug that comes up from time to time: when exporting form Resolve, each audio track needs to be added in turn as a ‘Timeline track’ and then its output set to mirror the Edit timeline audio track number. Sometimes the bug will not show enough track numbers available. Re-boot Resolve and its usually fine.
Hope that helps. Personally, I haven’t had too many probs with AAF-to-ProTools either except for fade handles. In any case, I completely stopped using this now because the QT export method, i) is much faster, ii) works perfectly without odd handle bugs and ii) is completely DAW agnostic & so now I usually choose Nuendo and avoid Avid altogether. Ditto for any other DAW: Reaper, Cubase, Logic, what ever. It just becomes generic multitrack audio.
Try it.
Dell T7910 workstation, Win10x64 Pro; 64GB Ram; 2x 12 core Xeons; Nvidia 1080Ti; LG 34UM95 & BenQ SW2700PT, BM DeckLink Mini Monitor 4k. Audio: RME Fireface UFX+, RME ADI-8, UAD-2 quad core PCIe. Resolve Studio, Adobe Premier, Nuendo, ProTools HD.
-
Yes, a PITA. AAF export is such a waste of life – and the various hidden menus and ways to ‘produce’ this. The ‘DAW’ component of Resolve 14 is still very poor/buggy/non-standard & lacking conventions & so I always round trip to a DAW for mastering multi-rack audio & drop back into Resolve as a LUFS normalised stereo file. FWIW, only the following two options work for me without head-scratching over why various elements of Resolve do not work correctly:
Deliver page:
1) The ProTools option (mxf) works with ProTools HD 12.8; this opens the video and audio tracks as laid out in the Resolve timeline. It can have problems with handle lengths from time to time, gaps between audio sections, doesn’t seem to recognise small cross-fades etc that may have been made in Resolve. (Don’t do any fades in Resolve beforehand then).
2) Now my preferred choice: Custom menu, under the video tab deliver a .mov file of choice for DAW reference (eg: 720p H264); under the audio tab, select ‘Output’ and set this to ‘TimeLine’ Track and allocate the 1st Resolve Track number; keep adding more TimeLine tracks via the plus button and allocate track numbers to match the Resolve Timeline audio tracks. eg, if I have 4 x stereo audio tracks in the Resolve timeline (say, wild camera, V/O, Music, FX) then there will be 4x Timeline tacks made under the Audio export menu. Linear PCM /24 bit.
This exports a QT mov with 4 x stereo tracks & which then open perfectly in a DAW, in my case, works with Nuendo, Cubase, Pro Tools. Mix & Master and drop back into the Resolve Media page.
Thinking in advance: you can split /copy/paste & name more audio tracks in Resolve in mind of the above multi-track export.
My 2 cents. This is the only reliable workflow I’ve managed to come up with thus far.
Dell T7910 workstation, Win10x64 Pro; 64GB Ram; 2x 12 core Xeons; Nvidia 1080Ti; LG 34UM95 & BenQ SW2700PT, BM DeckLink Mini Monitor 4k. Audio: RME Fireface UFX+, RME ADI-8, UAD-2 quad core PCIe. Resolve Studio, Adobe Premier, Nuendo, ProTools HD.
-
What I do: make each of the ‘chapters’ on separate timelines (like you do); then make each a Compound Clip (ie, pack into a folder); then place each Compound clip in sequence on a Master timeline for full vid-length play back and rendering.
Dell T7910 workstation, Win10x64 Pro; 64GB Ram; dual 12 core 3.0GHz Xeons; Nvidia 1080Ti; LG 34UM95 & BenQ SW2700PT, BM DeckLink Mini Monitor 4k. Audio: RME Fireface UFX+, RME ADI-8, UAD-2 quad core PCIe, Monitoring: Munro Eggs, Genelec 8020Bs, Logitech Z550 5.1. NLEs: DaVinci Resolve Studio, Adobe Premier. DAWs: Nuendo, ProTools HD, DP9, Live.
-
What a bizarre thing to say by B&H, best to ask them exactly what they mean eh?
In my system, the BM card is seen at the system level & sends video to the BenQ via HDMI [also works via a StarTech HDMI to Display Port adapter]. I switch between the BenQ as a second, extended desktop monitor [via Display Port & Nvidia GPU] to BM video preview on HMDI [the BenQ remote is very handy for this, and for calibration profiles etc].
The BM card is seen and used by DaVinci Resolve, Premier, Nuendo, Pro Tools – all in exactly the same way: as a preview monitor for video in use by that application. I default the BM card control panel to 1080p.
Dell T7910 workstation, Win10x64 Pro; 64GB Ram; dual 12 core 3.0GHz Xeons; Nvidia 1080Ti; LG 34UM95 & BenQ SW2700PT, BM DeckLink Mini Monitor 4k. Audio: RME Fireface UFX+, RME ADI-8, UAD-2 quad core PCIe, Monitoring: Munro Eggs, Genelec 8020Bs, Logitech Z550 5.1. NLEs: DaVinci Resolve Studio, Adobe Premier. DAWs: Nuendo, ProTools HD, DP9, Live.
-
I know exactly what you mean!
Went through all that myself, many detailed reviews and tests out there: subsequently I went with a BenQ SW2700PT, driven by a BM Decklink Mini Monitor 4k PCIe card. Very happy with this arrangement & works beautifully with Resolve Studio, Premier, Nuendo, Pro Tools.
e.g., see https://www.color-management-guide.com/benq-sw2700pt-monitor-review.html
https://www.4kshooters.net/2017/06/29/benq-sw2700pt-is-an-affordable-video-editing-and-color-grading-monitor-that-wont-break-your-bank/
Tom Antos review https://www.youtube.com/watch?v=idmyPGcAzLII think the key point with the rabble is do not use a compute GPU for display, rather use the BM Desktop video drivers and dedicated I/O. You could also go a BM Thunderbolt interface if that suits better for a later Mac. Lovely screen, Rec 709 and other internal presets, calibrates well.
Dell T7910 workstation, Win10x64 Pro; 64GB Ram; Samsung SSDs. CPUs: 2×12 core 3.0GHz Xeons; GPUs: 2x Titan X; VDUs: LG 34UM95, BenQ SW2700PT, BM DeckLink Mini Monitor 4k. Audio: UA Apollo & UAD-2 PCIe, RME ADI-8. Monitoring: Munro Eggs, Genelec 8020Bs, Logitech Z550 5.1. NLEs: DaVinci Resolve Studio, Adobe Premier. DAWs: Nuendo, ProTools, DP9, Live. Plugs: UAD, Steinberg, FabFilter, SoundToys, Sonnox. VIs: NI, MusicTech, Output, MOTU, Steinberg Absolute 3.
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
Yes it works (14b6), haven’t had a re-look yet in b17. The odd thing (b6) is that there is no input monitoring /metering indication & so you need to first record briefly to check levels etc, then do the recording proper:
Fairlight page:
Map your input(s) to monitoring outputs as per the manual instructions.
Select a new audio track with same input assigned.
Record-arm that track (small ‘R’ button’ above the fader).
Press ‘record’ under the view screen and off you go, now recording.Dell T7910, Win10 x64 Pro; 64GB Ram; 2x E5-2687Wv4 CPUs; 2x Nvidia Titan X GPUs; LG 34UM95 & BenQ SW2700PT VDUs, BM DeckLink Mini Monitor 4k; UA Apollo & UAD-2 PCIe. Samsung SSDs. DaVinci Resolve Studio, Nuendo, Pro Tools, Wavelab.