DaVinci Resolve 14 Beta 4 Bug Reports

My system is also exhibiting this behaviour though CPU usage is 9% after going to Fairlight page?

Adam.

The program is running just fine! But i still miss shortcuts for assign colors to clips on the edit page. The only thing that i miss from premiere and that helps me a lot!

while working with 1080 dnxhr sq clips, all 4 betas have thrown what I would call a fatal error during rendering. It doesn't seem to be tied to any one clip, or ordering or processing. The only thing that is constant is that it looks like it fails right before the end. I'd say with in 20 frames of the end of the timeline. However the video looks like it renders out just fine every time.

error.jpg (240.01 KiB) Viewed 27620 times

[Rohit Gupta]

while working with 1080 dnxhr sq clips, all 4 betas have thrown what I would call a fatal error during rendering. It doesn't seem to be tied to any one clip, or ordering or processing. The only thing that is constant is that it looks like it fails right before the end. I'd say with in 20 frames of the end of the timeline. However the video looks like it renders out just fine every time.

error.jpg

Which format are you rendering to?

Can you capture logs after restarting the app and post a link or PM me? (Alt click, press Help, and click capture logs)

[Rohit Gupta]

On Mint/Ubuntu systems, starting or loading a project now shoots out a "Segmentation fault" immediately. This was not the case with any of the previous beta versions.

Tested on 3 Linux systems - all i7 processors with:
1. i7 4/core 1.7GHz - 8GB - nVidia 420M 1GB VRAM - 500GB HD - Mint KDE
2. i7 4/core 2.67GHz - 12GB - AMD RX480 8GB VRAM - 120GB SSD & 2x1TB HDs - Ubuntu Studio
3. i7 6/core 3.2GHz - 24GB - nVidia 580GTX OC 1.5GB VRAM - 2x250GB SSD & 1x120GB SSD - Mint KDE

All OS Kernels are distribution recommended.

Can you please capture logs using alt click help and post it?

Which format are you rendering to?

Can you capture logs after restarting the app and post a link or PM me? (Alt click, press Help, and click capture logs)

Hello Rohit,

I'm rendering to 1080 dnxhr sq. I just pm'ed you a link to the logs.

From the Media tab, when Generating Optimized Media, it works for a short while then freezes Resolve. Tried several times using a short 987 MB clip, choosing a separate SSD for cache. I also tried another longer clip, but it froze after a few seconds also.

Sometimes I experience that I loose the media in the Timeline. The length of the clip is there, but no video or audio plays. When I restart Resolve it is back to normal, perhaps for awhile.

System: OSX Sierra 10.12.6, 64GB RAM, Core i7 @4GHz, latest CUDA and Nvidia drivers, DaVinci Resolve Micro Panel.

Frist: A Big Compliment Team DaVinci Resolve

Title issue, it worked in 14 Beta 2/3
When copying an existing title text within the timeline, with command C / V or option & mouse,
and start changing the title text - all the changes will not show up in the timeline, and I can’t play the program anymore, I can move playhead but current clip will not show up.
I can still move clips around, change audio level, I can do changes in Fairlight, Color page won't work clips are greyed out.

And In the media pool all the clip thumbnails are greyed out.

Sunny greetings from LA

Matthias

+1 on losing ability to play video, but not related to titles. Seems very random as far as I can tell, needs restart to fix.
No video will play in any page, all thumbs are greyed out. Oddly, audio will play (without video monitor up) in FL page when I hit the record button.

Testing on iMac 2.9/4 i5 OS10.12.3, OpenCL. This behavior not experienced in b3 with same system.

Also, still seeing the Q values on the FL EQ changing back to default randomly, and always when clicking EQ open. (Since b1)

So far I haven't seen the crash in pthreadVC2.dll in beta 4, but now the render job from a very simple project that had so far reliably provoked it will just stop doing anything (no progress, showing 0 FPS, no CPU or I/O load), at varying progress into the render.

- Can't delete audio keyframes
- Playback timeline occasionally disables after adjusting audio keyframes (however playback works in Fairlight)

iMac (Retina 5K, 27-inch, Late 2015)
4 GHz Intel Core i7
40 GB 1867 MHz DDR3
AMD Radeon R9 M395X 4096

Resolve 14b4 Windows 10

Media browser has a very surprising "unmount" function when selecting a non-system drive root (D:/ E:/ etc...). (I find it very unusual to see such commands in any place other than the windows control panel).
Using it on some of my drives has no effect (nothing is unmounted, and no error message)

I also did not find any opposite "mount" function.

Hi BM,

First off , thanks for the amazing work on Resolve 14 !!!!!!!!!!

I experience a problem with using clips from a consumer Sony handycam, that worked fine in Resolve up untill 12.5.6 and breaks down in Resolve 14 beta 1-4. It shows itself as random frames of the clips showing as offline.

I am aware resolve does not and has never supported the audio part (ac3) of sony consumer clips , therefore i always rewrap the clips using editready (latest version) where audio becomes pcm , video untouched pass through to mov container and the resulting clips work fine in resolve. I then use resolve not to edit but to transcode and deinterlace to prores 422HQ for editorial.
Would love to use 14 for this as much faster but this problem makes it unusable unfortunately. As they worked in 12.5.6. i hope its a simple bugfix away.

Attached a link to a sample clip (password : resolve)

https://cloud.tachyon-consulting.com:55 ... kr4ovpryDV


System details:

Resolve Studio 14 beta (any beta has same problem so far) , dongle version.
Running in CUDA mode

OSX Sierra 10.12.4
CPU i7 4790
Mem 32GB
GPU 2x Nvidia GTX980TI
Driver version : 378.05.05.05f02 (latest)
Cuda : 8.0.83
Storage : SSD based

Hi Glenn, here no problem to play your clip and audio in Fairlight with the V14B4.

AC3-FAIRLIGHT.jpg

Hi Glenn, here no problem to play your clip and audio in Fairlight with the V14B4.

Tnx for testing man. So it may be system specific then. Crazy. Untill 12.5.6 never had a problem with these kind of clips. Maybe as BM switched engine for H264 type clips, now it shows up on my specific system.
Maybe something with the specific GFX drivers . Back to the drawing board.

Again , tnx for taking the time to test. Much appreciated.

Edit:

Did some further testing and makes no difference if i use, CUDA, OpenCl or Meta and one or 2 GPU's. So maybe OSX specific even as i see you run Windows. If anyone with OSX could maybe do a quick test i would appreciate before i break down my whole system to find if the issue is just with my system.

Can you please capture logs using alt click help and post it?

The only report I get from console run is the "Segmentation fault", therefore I went to the Kernel logs and came up with the following:

Code: Select all

6/17/17 6:27 PM   resolve[8057]   segfault at 2816a7a50 ip 00007f52d07fbf4d sp 00007f51c6ffba60 error 4 in libc-2.23.so[7f52d07c2000+1bf000]

This I ran on a KDE system on nVidia card.

Which format are you rendering to?

Can you capture logs after restarting the app and post a link or PM me? (Alt click, press Help, and click capture logs)

Rohit,

I just sent you another one I got, going from h.264 to dnxhr hq. Same issue, it exported fine but looked to fail right before the end, and killed the application.

Windows 10, Beta 4, this bug was also present in Beta 3

I experience that sometimes I get a single frame from a clip, coming in way to early.
Just a single frame, though.

This happens both when I am just importing media, and when in the other modes. So it shows up in export.

For instance, in the timeline of one of my projects, at timecode 01:00:02:17 I get the frame that is supposed to be at 01:00:06:11

And the same if I just try to preview a file in the source viewer in "Media mode", I get at 00:00:17:05 I get a frame that is supposed to be at 00:00:18:11

Edit: This was not a problem in 12.5.5

It's been mostly great so far, though I haven't had time to dig that much into it yet.

I have run into one startup glitch.

System: Windows 10, Razer Blade Stealth (2016) 4K/16GB Core i7 model, 1TB SSD + Razer Core + EVGA 1080Ti FTW3 card.

I have an external UHD screen, which matches the resolution of the laptop's UHD screen.

The 2nd screen is connected to an HDMI output on the GPU card, rather than on the laptop.

If I start up Resolve with normal settings, it spins up fine, detects the GPU, and it's happy. And fast. Switch to 2-monitor layout, no problem. Reverse the primary displays so that the bigger one is primary, again no problem.

Unless I *start* with that configuration. In that case, I get a black screen, and Resolve just sits there. I had to disconnect the RazerCore, connect the monitor to the HDMI port on my laptop and start it back up so that I could SEE the window, change the preferences back to single screen layout and change the primary screen back to 0 to get Resolve to work again.

So in other words, in order to use Resolve on the 2 monitor setup with the edit and color pages on the bigger monitor, I have to set Resolve to single monitor layout with the smaller screen as primary, start it up, change the workspace to dual screen and switch primary monitors, and then switch it all back before closing it down, or I can't start it back up.

With 14b4 on Mac OS 10.2.5, on occasion clips will no longer play. The interface is responsive in other ways. A Save, Quit and Restart remedies the problem until it reoccurs.

link to logs: https://www.dropbox.com/s/tp2ooncl7z5n8 ... 4.tgz?dl=0

Hello,
When we have a master timeline with some timelines inside : no sound when played.
Thanks for your work

I have the same issue.

I have video clips I have manually synced to audio clips.

When playing the synced clips back in the source monitor, they work fine. However, after creating subclips from those clips, the subclips play massively out of sync (10 seconds or so) in the source monitor. When dropped on to the timeline, they correctly play in sync.

I made quick tests with Resolve 14b4. All the bugs I reported for b3 still exist, so here are they again.

I still haven't played that much with the Beta. However, I encountered a small bug in the Linux version.

When I try using shortcuts to switch between the different pages, it switches the first time, but then each time I try switching I have to click anywhere in the interface with the mouse before I can switch to any other page.

To explain more let's say I am on the Edit page and want to switch to Color. When I click 'Shift+6' it goes to color page as expected. Now, let's say that after going to Color page I realised -before changing or doing anything in the Color page- that I want to do something in Fairlight page. If I press 'Shift+7' now, it won't go to Fairlight. I have to click anywhere in the Color page using the mouse and then press 'Shift+7' and it will switch.

I tested that in Windows, and it worked fine, so it seems to be a Linux-only issue.


SYSTEM INFO
OS: Linux Mint 18 64-bit
Processor: i7-4790K
GPU: GeForce GTX 770
RAM: 32 GB

Here is a list of the bugs I found:

1) (LINUX ONLY) This one is related to the bug quoted above.. When I switch pages in the Linux version and then press Alt+F4 to close Resolve, it doesn't work until I click with the mouse anywhere in the interface, then press Alt+F4

2) (LINUX ONLY) It appears, that Resolve 14b3 doesn't close correctly on Linux. When I check the System Monitor after closing the program, the process is still there. Trying to end it in the GUI System Monitor or using the 'kill' command in Terminal doesn't work as well. The only thing that stops it is using the special command 'kill -KILL'. This causes issues when I try to shut down or restart my computer as it either gives me a warning that Resolve is still running, or it takes ages to shut down or restart. I didn't have this problem in the earlier beta versions.

3) (WINDOWS & LINUX) Issues with Fairlight Timeline View Options:
- Checking 'View Flags and Markers' and 'Show Full Waveform' doesn't work properly. When I check any of these two, the timeline doesn't update. I first have to click somewhere in the interface, and then the timeline will be updated with the new settings.

- The other options doesn't seem to be working at all. To be fair, I am not sure what 'Show Waveform Border', 'Show Audio 1' and 'Show Audio 2' do exactly. However, as far as I understand (and correct me if I am wrong), the 'Show Video' option is supposed to activate a small display of the video tracks. If I am right, then it is not working as well because nothing happens when I check it, even if I click with the mouse on the interface.

4) (WINDOWS & LINUX) Selected audio tracks doesn't seem to be recognized. To explain, let's say I have 2 video tracks and 2 audio tracks, and I need to delete specific part of everything on all of them. When I add in and out points around the part I want to delete and hit the 'Delete' or 'Backspace' buttons, it deletes everything on Video 1, Video 2, and Audio 1, but leaves Audio 2 untouched, although all the tracks are selected.

5) (WINDOWS & LINUX) The compound clip alpha issue I had in most of the Resolve 12 versions (it wasn't fixed until 12.5.4 I think). The issue is back in 14b3 (not sure if it was in the earlier beta releases). Let's say I have a couple of clips, all with alpha channels, and I want to add them into one compound clip. The moment I do that, Resolve converts the alpha channel of all of these clips into black.

Also, resolve process in Linux doesn't terminate when I quit the application. I think this problem started around b3. At least this is when I noticed it. And it is still happening in b4.

As you see in the following picture, Resolve is still loaded into RAM, and taking about 1GB. And it is not like it stays there for a while in case I reopened the program or anything. Usually, it remains there as long as the computer is still running, and it also causes issues when I try to shut down or restart, because the system can't kill it. I have to force kill it manually from terminal because even killing it from the System Monitor GUI doesn't work.

System Monitor

Screenshot from 2017-06-18 01-14-45.png (79.49 KiB) Viewed 25814 times

SYSTEM INFO
OS: Linux Mint 18 64-bit
Processor: i7-4790K
GPU: GeForce GTX 770
RAM: 32 GB

On Color page, selected Unmix. Audio playback stopped. After deselecting Unmix, audio playback was restored.

Mac OS 10.12.5

Still no audio crossfade transitions working... At this point, I'm even wondering if BMD cares.

It looks like rotating video causes a few frames to be reorder.

I take a mp4 clip (form nexus 6 phone, h.264). Create a timeline from the clip. Inspect the clip, and change rotation angel to -90. Do nothing else... no color, not edits, nothing. When playing the timeline about 1-2 frames in every second are in the wrong order. Typically 1-2 frames off from where they should be.

It's not a playback issue. the rotate (or something) changes the clip. The altered frame order seem to be permanent. Even if you clear the cache. If you deliver the clip (vimeo, 720) it renders new altered frame order.

I can see randomly Media Offline alert (for few frames) while playing a timeline. DR14 b4 also render this alert when I export the clip.

I7 6800k
32gb RAM
GTX 970

3) (WINDOWS & LINUX) Issues with Fairlight Timeline View Options:
- Checking 'View Flags and Markers' and 'Show Full Waveform' doesn't work properly. When I check any of these two, the timeline doesn't update. I first have to click somewhere in the interface, and then the timeline will be updated with the new settings.

- The other options doesn't seem to be working at all. To be fair, I am not sure what 'Show Waveform Border', 'Show Audio 1' and 'Show Audio 2' do exactly. However, as far as I understand (and correct me if I am wrong), the 'Show Video' option is supposed to activate a small display of the video tracks. If I am right, then it is not working as well because nothing happens when I check it, even if I click with the mouse on the interface.

These issues are also present in the OS X version.

The "Show Full Waveform" option was functional in beta 1, 2 and beta 3.

Fairlight:
(1) Unable to create a new "Adaptive" audio track.
Workaround: create new audio tracks on the Edit page.

(2) unable to "Change Track Type To" Adaptive.
Workaround: change track types on Edit page.

(3) "Clear All" option not functional in the Flags pop up.
Workaround: manually select the clip's flag and use backspace/delete, alternatively use Mark > Clear Flags.

(4) "Clear All" option not functional in the Markers popup.
Workaround: use the Markers pop up "Clear All" command on the Edit Page.

(5) Zoom > Zoom to Fit command stops playback.
Workaround: none.
Expected behaviour: Zoom to Fit command to continue playback, and merely zoom to fit the currently selected clip to the bounds of the timeline window.

(6) Drag-dropping interleaved audio files in to Timeline creates multiple stereo tracks, one per channel.
Expected behaviour:
(a) Either a single adaptive audio track is created in the Timeline matching the interleaved audio file's channel configuration (i.e. 24 channel adaptive audio track for an NHK22.2 interleaved audio file)
OR
(b) multiple mono tracks to be created matching the channel count of the imported interleaved audio file's channel configuration (i.e. 24 mono tracks for an NHK22.2 interleaved audio file).
Issue: manually changing the track type from stereo to mono becomes laborious when dealing with NHK22.2 channel configurations.
Workaround: none. tracks need to be manually set to the correct track width one-by-one.

(7) Track Height slider only provides the maximum and minimum vertical track height zoom level, no steps in-between.
Workaround: use the "Lock Track Height to" functionality on a per track basis.
Note: the horizontal track zoom level slider functions correctly.

(8) Enabling Automation in the Transport, causes Main Bus level mismatch between channels. On a stereo configured Main Bus, the left channel is reduced by 5dB in comparison to the level of the right channel.
Workaround: restart Resolve.

(9) Media Management command (File menu) is non-functional.
Workaround: use the command on Media, Edit, or Colour pages.
Note: sometimes the command is greyed out, and at other times the command is available (i.e. white text) in the menu.


Edit:
(1) Add Tracks dialogue only provides 16 channel widths for "Adaptive" audio tracks.
Workaround: add adaptive tracks manually one-by-one using Add Tracks > Adaptive > 24 for NHK22.2 channel widths.

(2) "Clear All" option not functional in the Flags pop up.
Workaround: manually select the clip's flag and use backspace/delete, alternatively use Mark > Clear Flags.


Audio plugins:
(1) Grimm/BeatRig LevelView Audio Units plugin does not update its UI in realtime, only when stopping playback.
Note: This issue is also present when inserting the plugin as a clip-based effect.
Workaround: none.

(2) Audio Units and VST plugins' parameters are only adjustable while playback is stopped.

(3) RTW Loudness Tools Audio Units plugin causes the Resolve application to hang when drag-drop adding metering instruments in its UI. This procedure consistently requires a Force Quit of Resolve.
Workaround: none.

(4) Inserting the RTW Loudness Tools plugin on a stereo, 5.1, and Adaptive tracks, only Mono configuration options are available (i.e. the plugin only sees mono Input feeds, instead of standard plugin configurations such as stereo, 5.1, 7.1, et cetera).
Note: The only functional Audio Units plugin in my arsenal is WholeGrain Digital's Trio DynPEQ which is a mono Input plugin but Resolve treats its output as stereo, hence it is functional. Trio DynPEQ appears to be functional as Clip-based effect, as an insert on a track and as an insert on a stereo configured Main bus.

(5) On stereo tracks, Zynaptiq Adaptiverb and LevelView Audio Units plugins only output a mono feed, even when bypassed, when instatiated as inserts on a track.
Solution: Removing the plugin reverts back to a stereo feed.
Workaround: none, VST plugins exhibit the same behaviour.

(6) Instantiating the aforementioned Audio Units plugins as inserts on a stereo configured Main Bus correctly outputs a stereo feed but the balance is now right centric with the left channel down roughly 5dB in level.
Solution: Remove the AU plugin.
Workaround: none, VST plugins exhibit the same behaviour.


Miscellaneous:
(1) Reset Layout is non-functional.

(2) Fairlight > View Clip Info Display settings aren't retained when saving the Project.

(3) Fairlight Viewer window position is not saved with the Layout Preset (i.e. when popped out and resized on a second display, reloading a Layout Preset, the Viewer is popped back in the Meters section).

I concur with the issue mentioned by Abdelrahman on Linux, regarding Resolve not wanting to leave memory when shut down. Earlier I was able to -somehow- bypass the loading issue on one Ubuntu Studio station (othrs still have segfault issues). In short, Beta 4 appears to be able to run on a system with an AMD card but fails to run on systems with the nVidia ones.

On the AMD one, I tried to load an h.264 file, but only a flat-line audio came out on edit. In short, it loaded but the format is not supported, software or otherwise. I am working on a test project nowadays, but the lack of audio on Linux has limited the tests I would have liked to perform.

Crash after adding .mov file to timeline and playing back. Played beautifully for 30 seconds, the best playback I've ever had of raw footage - then it crashed randomly. Tried again, same thing.
Logs and System info attached

davinci_resolve.rar

(5.25 KiB) Downloaded 176 times

system info.rar

(138.65 KiB) Downloaded 171 times

By the way, now I am sitting on a system with a fresh Ubuntu Studio install & properly updated.

I just ran Davinci Resolve and I got the following error the moment I tried to get through the project manager:

Code: Select all

*** Error in `./resolve': corrupted double-linked list: 0x000000000cb52130 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7feaef1847e5]
/lib/x86_64-linux-gnu/libc.so.6(+0x7e643)[0x7feaef18b643]
/lib/x86_64-linux-gnu/libc.so.6(+0x800a8)[0x7feaef18d0a8]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x4c)[0x7feaef19098c]
/opt/resolve/libs/libFairlightPage.so(_ZN9__gnu_cxx13new_allocatorI17ParameterTypeDataE10deallocateEPS1_m+0x2f)[0x7fe9f609999f]
/opt/resolve/libs/libFairlightPage.so(_ZNSt12_Vector_baseI17ParameterTypeDataSaIS0_EE13_M_deallocateEPS0_m+0x41)[0x7fe9f60906cb]
/opt/resolve/libs/libFairlightPage.so(_ZNSt12_Vector_baseI17ParameterTypeDataSaIS0_EED1Ev+0x67)[0x7fe9f608a593]
/opt/resolve/libs/libFairlightPage.so(_ZNSt6vectorI17ParameterTypeDataSaIS0_EED1Ev+0x74)[0x7fe9f6085b9a]
/opt/resolve/libs/libFairlightPage.so(_ZN11StudioModelD1Ev+0x39a)[0x7fe9f607c7fa]
/lib/x86_64-linux-gnu/libc.so.6(+0x39ff8)[0x7feaef146ff8]
/lib/x86_64-linux-gnu/libc.so.6(+0x3a045)[0x7feaef147045]
Segmentation fault (core dumped)


The only symbolic links I have are the ones mentioned in the following article:
https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=58668

I followed its instructions up to the point it says about downloading the application. I performed the:

Code: Select all

inxi -Fxz

Which verified that my nVidia drivers are properly installed and running, including the cuda-toolkit & opencl. Direct rendering works as well. Basically, it's the same I used for all the previous installations and worked.

"Open as new Window" in media tab bug:

When you click "open as new window" in Dual Screen mode a new window pops up as expected. Though, when you click somewhere outside of the new windows the window dissapears. When you restart Resolve the new windows appear once again, but - if ou click outside of the respecting window -they dissapear again!

I hope this will be fixed asap!

Cheers

Hey everyone,

Complete noob here and first time poster.

Just a couple of issues that could reproduce pretty consistently.

(1)GoPro Hero 5 footage at either 2.7k or 1080p at 60fps would cause consistent random crashes in pretty much all editing scenarios with 100% CPU usage. After reducing frame rates in the camera to 30 and trying a new project, all the crashing has stopped.

(2)Frame Jumping. This is with GoPro footage at 1080p 30fps on both 14b3 and 14b4. If I set in and out markers on a preview clip and drag it into the timeline usually all is well but, If I start to add fade ins/outs or text, random frame jumping occurs on the timeline clip. It also carries over to the preview clip and the only way to rectify it is by removing the in/out markers on the preview clip, play through a portion of the preview clip and then reset the markers. This will usually fix it but if you miss one and finalize/render the clip it will show in the render. I did not have this problem with 60fps footage.

Thanks for the great program.

Nate

Windows 10 Home x64
i5 6600K OC'd to 4.1 ghz
16 GB DDR4 2133
GPU RX480 8 GB, driver 17.6.1
2 samsung 850 evo SSD's (500GB)
Multiple 7200 HDD for backups and long term storage.

Is it really so difficult to solve the problem with sound? Or do the writers ignore it? I know that the problem with the sound is not for everyone, but it's enough who has this problem.

Yes, I'm sure the programmers spend all their time playing Star Wars Battlefront and posting their one-shot kills on YouTube instead of working on fixing the audio for Resolve 14 just so that you will keep bitching about it.

Tapping through frame-by-frame in source viewer plays no audio. Audio only plays if pressing "play".

Fairlight page HPF and LPF save problem....
After I set up lpf and hpf in some fashion and save a project, next time I loud project lpf and hpf are in default position.
Delivery page problem...
after I render clip, in any format and any codec, there is a few red frames with "Media Offline"

See my signature for system details - Resolve 14.0.0b.037 crashes at varying places when rendering an H.264 timeline (GoPro HD and Sony A7Rii UHD) to MP4 output at Best setting - I get 'Too large' errors when I try to submit attachments, so logs and project export are at: https://www.dropbox.com/sh/ffse73koqi62 ... pIjUa?dl=0
Cheers
Steve Winter

Great update, thanks so much.

I've been working most days over the last couple of weeks with 14beta & nine or so chapters of 4k footage shot by a GH5 while on holiday in Italy. Good fun, but not commercially relevant of course. Formerly, b3 was crashing all the time, of many different & often inconsistent reasons. I concur with many of those posted elsewhere.

In 14b4 however, I've been working full days without crashes. Render, transcodes, bounces and generally operates without fuss. Notwithstanding the audio side of things of course - in my experience this is still generally useless, buggy and asking for trouble. I guess I weaned myself off that in the shorter term in b3 & now know what to avoid - pretty much everything.

Which brings up audio round tripping. Am working with Steinberg Nuendo to get good mixes of muti-camera audio (cleaned with various plugs /post) and multiple music tracks, plus a little SFX foley library. AAF is still highly problematic and doesn't speak to anything except for Pro Tools. Please improve /add other options.

At one point I had tried every export option, and including manual audio bounces on a per track basis. Even here this was buggy, refusing to export 'some' audio lanes & giving nonsense error messages like 'permissions problems' etc . (Error messages are also incorrect elsewhere, like a database drive simply not being mounted, yet reported and 'incompatible' ... etc. ) Turned out to be untrue and further developed time consuming workarounds to get the sound out of Resolve. Shouldn't be that hard.

How about – give us OMF? Old format, but should help with a variety of DAW destinations.

Otherwise - internal rendering /bouncing still gives colour grading shifts - despite the format, resolution, codec etc. Much of that reported elsewhere, but with inconclusive results. Does not yet seem possible to 'get what you see' in a render export then import.

Have been using this to compile new timelines with post-produced audio - and given that nested timelines nor compound clips work correctly yet. Nor does a simple cut & paste all of a timeline into a new timeline - i.e., a way of assembling chapters. Sometimes as expected, others, will simply crash Resolve.

Anyways, certainly heading in the right direction and the engine is certainly now much improved in this version, thank you. e.g., last night ran up a large list of Delivery job queues - a 60 min timeline as 'all', plus many chapters marked as in-out points, and all for both 720p and 1080p renders. Walked away and the whole thing chugged away to produce perfect results as expected. Fast, reliable, no crashes. Nice.

2 more bugs...

- Opening an existing project, the edit is in place but there is no video displayed. Just grey monitor windows. Going into the media pool, the clips are also listed and right clicking to view them in Finder works. So the media is where it needs to be, edit in place, there’s no error stating the media not found, it’s just that nothing is displayed and clips can not be played. The project window when Resolve opens, just displays the default Resolve Icon on the project screen.
- When Resolve crashes, at times, it corrupts the videos files in the media pool. Even Quicktime can no longer open a ProRes file.

14b4 seems to be way less stable than the previous version.

Here are a series of bugs that I have run into:

1. Clips won't play after certain events (not clear what is causing the issue). The rest of the UI remains responsive. But the clip in the timeline window won't change as you move around, and it appears that the player has jammed. The only way to fix is to restart Resolve.

2. I have lost sound in the playback in the Color window after making changes to the grade. I could go back to the Edit window and still hear sound, but not in the Color window. Restarting Resolve fixed the problem.

3. I have imported a title that I exported from Final Cut Pro in ProRes 444 with Alpha Channel. It is placed on top of a clip in the timeline. The title plays back fine with Proxy Mode set to Off. But when I change to Half Res, the title plays, but not the underlying clip, which shows up as black.

Thanks, David Skok (my real name - waiting to be changed by the PM)

Retimed clip export bug

Resolve has a bug export any clip from my timeline where I have done Retime work on it in the Resolves Retime Curves editor. It will export them fine into a single clip, but not as individual clips. What happens is that Resolve seems to jump forward and then backwards a few frames producing a stutter effect. I wanted to attach a file to show what this looks like, but the forum would not let me upload a m4v extension, or paste in a Dropbox link. If you email me, I can send you either one. (The file is less than 1 MB, as I reduced the resolution.

Thanks, David Skok (my real name - waiting for a PM to change my user name)

Insert Clip - inserts at start of Timeline, not playhead position.

14b4 Bug - Dragging a clip from the Clip Viewer to the Timeline Viewer, and asking to Insert, inserts at the beginning of the timeline, not at the playhead position.

Thanks, David Skok (real name, waiting for PM to change my username).

Crash Bug

14b4 crashes when I drag a clip from the Clip Viewer over the Timeline, and drag it around inside the existing timeline, looking for the optimal spot to place it.

MacBook Pro 2017 latest version, fully maxed out config.

Thanks, David Skok (real name, waiting for PM to change my username).

Anyone else experiencing the following:

Clips are in timeline and bin, but no video or audio can play. just a black frame. I can see audio waveforms.

Also for some projects, when performance mode is checked, playback struggles. Unchecking this and playback is smooth.

Further to my earlier bug report (crashes when rendering h.264 timeline) I am not so sure it is a Resolve problem, as I have also experienced crashes in Photoshop. I'm going to try DDU driver uninstaller and different drivers for my new GTX 1080 Ti. Any stable driver recommendations?
Cheers,
Steve Winter

Moin, thanks for the Update!

macOS Sierra 10.12.5 on a MacPro Late 2013:


(1) When Media is added per Drag & Drop into Media Pool, Timecode is killed and starts at 00:00:00.00 of each clip (ARRI RAW .mxf). Over right click "Import media" it works perfectly.

(2) To put a memory still to place E and F alt+5 or alt+6 is not working, have to use alt+ctrl+5 or 6

(3) saving a still on memory place B, still is deleted after restart resolve although saving project.

So far...

Cheers
Chris Saure

Anyone else experiencing the following:

Clips are in timeline and bin, but no video or audio can play. just a black frame. I can see audio waveforms.

Also for some projects, when performance mode is checked, playback struggles. Unchecking this and playback is smooth.

Yes, I wrote about the issue on the first page.

Without much to go on, it seems to happen on OSX (Window/Linux users, please chime in). It *seems* like Resolve in someway looses the contact with the media due to a bug in Resolves link to the file system.

I can't create optimized media because after a second or to the progress just stops and hangs. The minutes/seconds keep ticking, but no progress. Also I quickly loose contact with any media, resulting in no video - or audio playback.

Hopefully BMD can figure this out quickly and send out a Beta 4.1 for testing.

Fairlight:
8(a) Enabling Automation in the Transport, causes Main Bus level mismatch between channels. On a stereo configured Main Bus, the left channel is reduced by 5dB in comparison to the level of the right channel.
Workaround: restart Resolve.

8(b): enabling Automation, increases the Main Bus Right channel level peak value (by roughly 1.5dB), causing the Right channel to clip when the timeline audio segment's maximum level peak value is -1dBTP, the Timeline audio segment is now reproduced with audible distortion.
Note: Audio Track peak levels are unchanged. Issue only related to the Main Bus.
Workaround: Insert a TruePeak Limiter plugin on the Main Bus insert, set to -1dBTP Output if Automation is required (Flux Elixir VST inserted during testing).
Alternatively, enable the Main Bus built-in Limiter, set to a threshold of -1.2dB (disadvantage of this approach is as the Threshold is reached, the Main Bus channel Left/Right balance is affected, reverting to its prior state once Input signal is below threshold. The Flux Elixir True Peak Limiter VST plugin approach does not exhibit this behaviour).
Side note: this TruePeak Limiter plugin workaround improves the issue as described in 8(a) but does not solve it.


8(c) selecting "Misc" in the Automation bar, flips the Main Bus Left/Right channel balance again, now Left focused, with the Right channel's level down -5dB. Deselecting "Misc" in the Automation bar reverts to a condition as described in 8(a).
Note: none of the other Automation type buttons exhibit this behaviour. Audio Track peak levels are unchanged when enabling and disabling the "Misc" automation button. Issue only related to the Main Bus.
Workaround: none.

- Gallery start to lose stills that I saved some time ago. They look blank and with no grading
- Poor NR performance compared with 12.5

amazing work otherwise!