Latest stable version of 17

I am trying to do a simple task in 17.4 studio in the fusion page. Some tracking and patch replace. Davinci keeps chrashing every few minutes doing this. Can someone tell me what would be a stable version to go back to?

Thanks, Robert

Verstuurd vanaf mijn SM-N950F met Tapatalk

Platform? GPU? Memory?

Sent from my CPH2025 using Tapatalk

Platform? GPU? Memory?

Sent from my CPH2025 using Tapatalk

Sorry forgot to save my signature... but now i did
All worked fine in 16, i know 17 seems to be more demanding, but this is unworkable

Resolve 17.4.2 studio. Windows 10. i7-3930K @3.20Ghz. GTX 1060 6GB.

17.4.3 is the latest version.

17.4 was and embarrassment for Black Magic. They rushed out 17.4.1 and 17.4.2 that still had problems. I haven't seen many complaints with 17.4.3

I personally have stayed on 17.3.2 as 17.4 didn't add anything I care about.

Platform? GPU? Memory?

Sent from my CPH2025 using Tapatalk

Sorry forgot to save my signature... but now i did
All worked fine in 16, i know 17 seems to be more demanding, but this is unworkable

Resolve 17.4.2 studio. Windows 10. i7-3930K @3.20Ghz. GTX 1060 6GB.

Beware of downgrading. Even within version 17, a downgrade from 17.4 to - let’s say - 17.3.2 may lead to "unexpected behaviour", as seemed to be the reason for my experience in:

https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=149450

I had created the project on my M1 installation (17.4 Studio), but had in this case opened the project from my Intel Mac installation (17.3.2 Studio) in the belief, that the versions were the same - both 17.4.

Anyway, this seem to confirm, that Blackmagic does not even guarantee compatibility on exported project files between minor versions of the Studio software.

It doesn’t help, that the project files use huge, tyically “binary blobs” with unknown content instead of standard xml definitions (you need to unpack the drp file, in order to get access to the content). Binary data is often position dependent, and the use and content of individual blobs, may not be downward compatible (as is xml, where the basic assumption is, that if a program does not understand a term, it can legally and should definitely be ignored. That's the huge strength of using xml.).

Here’s a somewhat random - and small - selected example from the “project.xml” file (after unpacking the actual "something.drp file”):

Code: Select all

    .... a lot of text
    <UserSetup>
      <SM_UserSetup DbId="183a9405-4748-4961-9fff-c3cd0c841aa5">
       <FieldsBlob>00000001000000080000005000530069007a0069006e00670049006e0074006500720061006300740069006f006e00730046006f007200570069006e0064006f007700730041006e00640046005800560065007200730069006f006e0000000200000000030000001c00500072006f00780079004d006500640069006100500061007400680000000a000000005c002f0056006f006c0075006d00650073002f0059006f007400740061003100540042003900370030002f0044006100560069006e00630069005200650073006f006c00760065002f00500072006f00780079004d00650064006900610000002600500072006f00780079004d00650064006900610043006f006400650063004e0061006d00650000000a0000000008006100700063006e0000002e004f007000740069006d0069007a00650064004d00650064006900610043006f006400650063004e0061006d00650000000a0000000008006100700063006e000000320043006c0069007000500072006f00630050006100720061006d0073004f00760065007200720069006400650053006500740000000c000000023a000000010000000e0000000200390000000a000000001e00500061006e00610073006f006e00690063004b0065006c00760069006e0000000200380000000a000000001a00500061006e00610073006f006e0069006300540069006e00740000000200370000000a00000000180052004500440055007300650072004300750072007600650000000200360000000a00000000160053006f006e007900460036003500540069006e00740000000200350000000a000000001600430061006e006f006e004b0065006c00760069006e0000000200340000000a00000000140042005200410057004b0065006c00760069006e0000000200330000000a00000000120044004e0047004b0065006c00760069006e0000000200320000000a000000001200430061006e006f006e00540069006e007400000004003100330000000a00000000260053006f006e00790046003600350057006800690074006500420061006c0061006e0063006500000004003100320000000a00000000220052004500440055007300650072004300750072007600650047007200650065006e00000004003100310000000a00000000200052004500440055007300650072004300750072007600650042006c0075006500000004003100300000000a000000001e0052004500440055007300650072004300750072007600650052006500640000000200310000000a0000000010004200520041005700540069006e00740000000200300000000a000000000e0044004e004700540069006e00740000003200430061006300680065005400720061006e0073006900740069006f006e0049006e0055007300650072004d006f0064006500000001000100000032004300610063006800650043006f006d0070006f007300690074006500730049006e0055007300650072004d006f006400650000000100010000001e0041007500640069006f0042007500730069006e0067004d006f00640065000000020000000001</FieldsBlob>
       <LastWorkingProject/>
       <LastWorkingProjectFolder/>
       <DefaultToLocalVersion>true</DefaultToLocalVersion>
       <SaveClipVSR>false</SaveClipVSR>
       <ResolveVersion>0.0.0</ResolveVersion>
       <StillTrackClip>0</StillTrackClip>
       <SourceBlanking>0</SourceBlanking>
       ....etc


Only a tiny fraction of the content of one, single xml file included in the drp-file. I’m especially taken in by this statement:

Code: Select all

 <ResolveVersion>0.0.0</ResolveVersion>

Ehhh…? My resolve version 17.4.3 build 10 is not even capable of identifying itself, also making it more of a lottery for a later (or even earlier) version of Resolve to establish any “deviations” from the “one and true settings religion” valid at the moment of creation of the file and the moment of creation for the DaVinci version.

They may be different in vital details (or it may be a trivial omission in this case); the example highlighted above, is a typical indication of rushed work, never remedied at a later time. After nearly 40 years as a systems programmer on all levels - specialising in hunting down bugs, nobody else seem to be able to find (often because, there are “absolutely no bugs there” and they “know, there can’t be because….” and a looong explanation follows. When one actually starts looking into some or even many of the socalled bugfree nooks and crannies, wadajunou, there really are some squished critters and "dubious" code lurking innocently in the dark from time to time, but if you don't look...

To make a long story short:

IF you downgrade, export all active and recent projects to a “backup folder”, before doing anything else.

Then be prepared for a surprise or two, but now you still have the original content in the saved project files located somewhere safe (this is up to you, so... . Remember to add a text file describing which version, the files were saved from and if it was a "free" or a Studio version.

Have fun!

17.4.3 is the latest version.

17.4 was and embarrassment for Black Magic. They rushed out 17.4.1 and 17.4.2 that still had problems. I haven't seen many complaints with 17.4.3

I personally have stayed on 17.3.2 as 17.4 didn't add anything I care about.

Thanks for answering
Unfortunately it did not help me at all.... maybe even the opposite, but not sure.
I will not use Fusion in Resolve for a future project, but will use the standalone instead.
One more clip to go.... fingers crossed.