Bug Report at 18.6 new update

How has this still not been resolved?
This is a huge issue, making my job take nearly twice as long, I'm downgrading now but I'm quite disappointed an issue this colossal has taken so long to fix...

Before demanding here a quick fix for this bug:
Why don't take the minimum time yourself to read the FAQ on this forum of how to report a bug.
You don't state your system specs, you don't describe what you are doing in a way developers can reproduce. You do not post crash logs.

How do you except them to solve the issue without necessary information? A lot of people post here that they have a problem and most of them provide no meaningful information. Do people here expect BMD developers to have mind reading capabilities and a crystal ball for seeing what's going on?

This has to be done systematically. If several people with similar hardware or same driver versions report a problem, then it is possible to encircle the issue.

So please, if you want to help to resolve the issue fast - read the FAQ here and provide as much information as possible about your problem.

Same issue with Ripple Delete. What I'm seeing is it appears correct in the edit tab that the audio was moved in sync with the video but after opening the fairlight tab the audio didn't move with the video.

Robert,

If you check the forum and the internet you will find that this is not one bug we are reporting. I am not the only one to say that 18.6 is "unusable".

Most users - myself included - have had to downgrade to 18.5 after wasting hours trying to make 18.6 work.

I wasted a whole morning fiddling with 18.6 thinking it was my specific install.

These are basic editing features which are broken in 18.6. BMD cannot expect their users to do beta testing for them - unless I download a beta version. It takes a few minutes for any QA engineer to realise that 18.6 is NOT ready for release.

Under these circumstances, I am not prepared to invest even more of my time to properly document such obvious bugs which are clearly known to BMD - if they are not, then there is something very serious going on with the whole project and BMD should stop and think of what's happening.

Hi,

I'm having the same problem. Mainly, the ripple delete function is super slow it takes 5 seconds to complete and mutes sections of my audio and leaves it out of sync.

Yeah, same here, and it's not only ripple. If you delete a clip, than select all clips to the right, and move them by hand to close the gap, it also messes with the audio. It's okay after I restart Resolve though.

My 18.6 is working fine on a 2017 iMac with only 20gb ram. I haven't loaded it on to my main machine but if it works on my old banger I can't imagine a better, more recent machine would be worse.

I have seen none of the problems you report so I'm thinking it could be something not quite right with your system/setup. It would definitely help to list details.

Whenever I enter something in a number field and press "enter" it doesn't commit, it doesn't leave the field, or it goes to the next field, escape doesn't work either, I have to find somewhere to click away else I'm left wondering why spamming space doesn't play my timeline, and why the field I was working on earlier is now is filled with spaces lmao.

Am I the only one ?

Changing the proxy resolution worked for me! It even works after I revert it back thankfully, it would be painful to go back and forth while I'm grading and whatnot.

For me, this problem seems to be linked to Voice Isolation and Dialogue Leveler which I had turned on for the entire clip at the start of my project.

In a new video, I left them off and the cutting and editing did not have the same muting problem.

Just giving feedback for anyone working on this problem.

well, fail. it was good then I added a short 2 sec audio clip and it's back to being f*## up. Joy.

All the confusion in this thread once again highlights just how valuable it would be for BMD to run a "known issues" list so that people having problems could save a *lot* of time if they're having problems.

If they see they've encountered a known bug then they can sit tight or downgrade to the previous version.

If they see no matching problem they can submit a bug-report.

If they're thinking of upgrading they can weigh up the list of "known issues" against the benefits of that upgrade and save themselves the hassle of finding out the hard way.

Many, many software companies provide a list of known issues and sometimes they even include an estimated "time to fix". Hell, even Google/YouTube does this and they're the *least* user-centric corporation on the planet.

Same issue, had to roll back to 18.5.1.

All the confusion in this thread once again highlights just how valuable it would be for BMD to run a "known issues" list so that people having problems could save a *lot* of time if they're having problems.

What I like about Avid’s Known Issues list is they also give known work-arounds if possible. The transparency is so helpful & refreshing.


Sent from my iPhone using Tapatalk

Whenever I enter something in a number field and press "enter" it doesn't commit, it doesn't leave the field, or it goes to the next field, escape doesn't work either, I have to find somewhere to click away else I'm left wondering why spamming space doesn't play my timeline, and why the field I was working on earlier is now is filled with spaces lmao.

Am I the only one ?

Is it the voice isolation in the inspector? or any text field?
Because for me, clicking on the number for the voice isolation is lagging, but nowhere else.
When I select it, or when I type, the change is not instant.. I constantly have to bash the mouse-click

All the confusion in this thread once again highlights just how valuable it would be for BMD to run a "known issues" list so that people having problems could save a *lot* of time if they're having problems.

If they see they've encountered a known bug then they can sit tight or downgrade to the previous version.

A known issue list would help but in my humble opinion the issues 18.6 is suffering are unacceptable. They are not minor glitches people can live with, they just makes impossible to use the software!

Can confirm that changing proxy settings does NOT fix it for me.

Also noticed today that deleting a gap between clips when there are many edits following it in the timeline is very, VERY much slower than usual (the program hangs for a good 20-30 seconds or so).

Finally gave up on waiting for a fast hotfix for this, so I've had to roll back to 18.5.1 today to be able to get projects done.

I've given some basic specs before, but here's more in case it helps.

Windows 10
AMD Ryzen 7 2700X
NVIDIA GeForce GTX 1080 Founders Edition
16 GB of RAM
Fully updated graphics drivers

Hello all,

I have found a new issue in Resolve Studio 18.6 (assume it is in the free version as well) as far as I can see. When in the colour tab (area) with the (Tracker - Window) section open/visible (does not matter which tool in the tracking section is selected (window, stabilize or fx) the error occurs in all tools) and playing a clip back as normal and then playing into the next clip pressing the [space bar] to stop/toggle playback and then using a mouse or pen to grab the red play head in the (Tracker - Window) to scan/scroll back or forward in the current clip the entire Resolve Studio quits without warning and/or message to the desktop.

This is very repeatable and quite annoying, even if this is accidental touch of the play head in the tracker window Resolve crashes, hard. It seems to only happen when play forward to the next clip in the timeline.

Please help - Thanks,

Can confirm that changing proxy settings does NOT fix it for me.

Also noticed today that deleting a gap between clips when there are many edits following it in the timeline is very, VERY much slower than usual (the program hangs for a good 20-30 seconds or so).

Finally gave up on waiting for a fast hotfix for this, so I've had to roll back to 18.5.1 today to be able to get projects done.

I've given some basic specs before, but here's more in case it helps.

Windows 10
AMD Ryzen 7 2700X
NVIDIA GeForce GTX 1080 Founders Edition
16 GB of RAM
Fully updated graphics drivers

Is rolling back as easy as uninstalling Resolve 18.6 and using the 18.5.1 Installer? Database doesn’t get deleted?

Hello all,

I have found a new issue in Resolve Studio 18.6 (assume it is in the free version as well) as far as I can see. When in the colour tab (area) with the (Tracker - Window) section open/visible (does not matter which tool in the tracking section is selected (window, stabilize or fx) the error occurs in all tools) and playing a clip back as normal and then playing into the next clip pressing the [space bar] to stop/toggle playback and then using a mouse or pen to grab the red play head in the (Tracker - Window) to scan/scroll back or forward in the current clip the entire Resolve Studio quits without warning and/or message to the desktop.

This is very repeatable and quite annoying, even if this is accidental touch of the play head in the tracker window Resolve crashes, hard. It seems to only happen when play forward to the next clip in the timeline.

Please help - Thanks,

Probably should be its own thread.

Is rolling back as easy as uninstalling Resolve 18.6 and using the 18.5.1 Installer? Database doesn’t get deleted?

Yeah, that's what I did, and the database stayed just fine. You're advised to backup your database first though, just in case.

Is rolling back as easy as uninstalling Resolve 18.6 and using the 18.5.1 Installer? Database doesn’t get deleted?

Yes, thankfully the database didn't get updated. As mentioned, do back it up anyways just in case.

Is rolling back as easy as uninstalling Resolve 18.6 and using the 18.5.1 Installer? Database doesn’t get deleted?

Yes, thankfully the database didn't get updated. As mentioned, do back it up anyways just in case.

Thanks. Worked perfectly. Can finally actually edit. I still can’t believe BM let this build 18.6 through.

Also broken for me - I found that on short, simple timelines it's working ok, but as soon as the timeline gets longer and more complex ripple delete is broken.

Wound back to 18.5.1 and I'm OK.

M1 Max Studio 32GB
Ventura 13.5.2
Resolve Studio

Same and I feel this is why many users seem to be ok with 18.6.

Hello all,

I have found a new issue in Resolve Studio 18.6 (assume it is in the free version as well) as far as I can see. When in the colour tab (area) with the (Tracker - Window) section open/visible (does not matter which tool in the tracking section is selected (window, stabilize or fx) the error occurs in all tools) and playing a clip back as normal and then playing into the next clip pressing the [space bar] to stop/toggle playback and then using a mouse or pen to grab the red play head in the (Tracker - Window) to scan/scroll back or forward in the current clip the entire Resolve Studio quits without warning and/or message to the desktop.

This is very repeatable and quite annoying, even if this is accidental touch of the play head in the tracker window Resolve crashes, hard. It seems to only happen when play forward to the next clip in the timeline.

Please help - Thanks,

PS: Watch it crash: https://f.io/appUKeSv

I don't really know if this problem as been mentioned with the cutting problem or not, but since it is a related problem, I would like to specify that there is also a problem with the auto trim editing in the cutting page.

The auto trim editing in the cutting page has been proven useful to me in all of my projects. I am so disappointed that they have taken that away from the cutting page as well

Please fix this !!!!!

I installed Resolve 18.6 today and have a huge problem. The Video-Files are interpreted as audio files. Thats in the media pool and source folder. No video can be seen. MP4 files are ok, but MXF video files and footage from my canon XF605 are interpreted as audio files. Any Solution?

That sounds a lot like a Free vs Studio problem, Andreas, where you will need the paid Studio version to work with that media.

Likely unrelated to this thread.

Thank you! Yes, it was...found that out, too!

Okay it's been resolved for me?? Maybe backdoor update?!?!

Robert,

If you check the forum and the internet you will find that this is not one bug we are reporting. I am not the only one to say that 18.6 is "unusable".

Most users - myself included - have had to downgrade to 18.5 after wasting hours trying to make 18.6 work.

I wasted a whole morning fiddling with 18.6 thinking it was my specific install.

These are basic editing features which are broken in 18.6. BMD cannot expect their users to do beta testing for them - unless I download a beta version. It takes a few minutes for any QA engineer to realise that 18.6 is NOT ready for release.

Under these circumstances, I am not prepared to invest even more of my time to properly document such obvious bugs which are clearly known to BMD - if they are not, then there is something very serious going on with the whole project and BMD should stop and think of what's happening.

It's ridiculous really. Becoming the new Adobe. Might be ''orders from the above'', and the development team doesn't have the guts to speak out or they are just not listened to... They are starting to run Resolve like Adobe runs Premiere and the whole creative suite.

This situation reminds me of when BMD added "the boring detector" (a feature nobody asked for) to Resolve... at a time there were a significant number of other bugs and shortcomings that users had been begging to get fixed for many years (some of those are still to be sorted even today).

And now we have 18.6 driving people crazy... but hey, ignore those problems... we've got a new app for the iPhone (that nobody asked for) Woohoo...

I appreciate new things, even that camera app.

But the stability and performance is paramount.

As I mentioned (here or on a different thread), let's go LTS and "full features".

LTS stays quieter and gets stability and performance updates while the other goes on with all the latest and greatest. Once the new feature is stable and reliable, it trickles to the LTS version.

[Peter Chamberlain]

Please see if 18.6.1 resolves the issue you have with 18.6.

Please see if 18.6.1 resolves the issue you have with 18.6.

Who’s first?

Please see if 18.6.1 resolves the issue you have with 18.6.

Who’s first?

Why not you?

Please see if 18.6.1 resolves the issue you have with 18.6.

Who’s first?

Why not you?

Learned my lesson in trusting updates. How about you?

I did a quick test with 18.6.1 with a random video file.
I can ripple delete without having the ghosting audio like before.

It happened (for me) with 18.6 when I had an audio transition somewhere, and every cut/ripple delete on the left of it had the ghosting audio.

Whenever I enter something in a number field and press "enter" it doesn't commit, it doesn't leave the field, or it goes to the next field, escape doesn't work either, I have to find somewhere to click away else I'm left wondering why spamming space doesn't play my timeline, and why the field I was working on earlier is now is filled with spaces lmao.

Am I the only one ?

Is it the voice isolation in the inspector? or any text field?
Because for me, clicking on the number for the voice isolation is lagging, but nowhere else.
When I select it, or when I type, the change is not instant.. I constantly have to bash the mouse-click

Any single field, the cursor stays in it after pressing enter, or it just switches to the next one if it was a multiple field panel. I have to click in some random place to make sure I'm out the field

Looking like it's fixed so far. Thanks, Blackmagic Design! Appreciate you guys!

It looks like it's fixed now! Appreciated
There is still a similar bug when I duplicate my timeline, where *all* the audio clips and video clips got rubberbanded backwards (or forward, don't remember) wouldn't know how to replicate this, it's only happened once. I'll post again if I encounter it further

[Peter Chamberlain]

Please update to 18.6.2. and report if this does not fix your issue.

Hello all,

I have found a new issue in Resolve Studio 18.6 (assume it is in the free version as well) as far as I can see. When in the colour tab (area) with the (Tracker - Window) section open/visible (does not matter which tool in the tracking section is selected (window, stabilize or fx) the error occurs in all tools) and playing a clip back as normal and then playing into the next clip pressing the [space bar] to stop/toggle playback and then using a mouse or pen to grab the red play head in the (Tracker - Window) to scan/scroll back or forward in the current clip the entire Resolve Studio quits without warning and/or message to the desktop.

This is very repeatable and quite annoying, even if this is accidental touch of the play head in the tracker window Resolve crashes, hard. It seems to only happen when play forward to the next clip in the timeline.

Please help - Thanks,

PS: Watch it crash: https://f.io/appUKeSv

Update: still broken/bug/crash in Resolve Studio 18.6.2

Waiting for 18.6.3 by the end of the week I guess? I need a faster internet connection.