Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums DaVinci Resolve I have just ccrashed DaVinci 16

  • I have just ccrashed DaVinci 16

    Posted by Terence Christopher on June 29, 2019 at 5:54 am

    I think that I should report an error that I made which cause DaVinci 16 to seize up. I found that one of my partially complete videos had recorded that link to a clip was missing. I thought it would be easy to correct and went into relink clips in the edit menu and then found a possible but incorrect clip. The programme could not verify the linkage and stopped. I was unable to perform any action to back out of the situation, and was forced to shut down DaVinci 16 by using task manager.

    Joseph Owens replied 6 years, 10 months ago 6 Members · 18 Replies
  • 18 Replies
  • Robert Withers

    June 30, 2019 at 5:04 pm

    This is interesting. I have avoided any experiments with DV 16 because it is still a public beta release . . . https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion . . . and I have enough trouble learning DV 15. I trust you are reporting your experiences to BMD.
    Thanks for reporting on the Beta version,
    Robert

    Robert Withers

    Independent/personal/avant-garde cinema, New York City

  • Terence Christopher

    June 30, 2019 at 6:19 pm

    No I reported t here with the expectation that someone would pass it on. I don’t know of any formal way of reporting things like this.

  • Robert Withers

    June 30, 2019 at 6:30 pm

    I imagine we can all pass these things along to the software designers, eg via https://www.blackmagicdesign.com/support/contact/email
    But thanks for reporting here. I’ll stay away from the DV 16 for now and continue learning DV 15.

    Cheers,
    Robert

    Robert Withers

    Independent/personal/avant-garde cinema, New York City

  • Terence Christopher

    June 30, 2019 at 8:40 pm

    p.s. I am a very low quality of student in the matters of Davinci however I recently tried 16 and found that it seemed easier to use than 15 and more intuitive. I am finding more of the important features with less difficulty so I would not go back to 15.
    Previously I had trouble with 15 because it would not accept my M2t files and had to learn to use Pro res which works well with both.

  • Michael Gissing

    June 30, 2019 at 10:47 pm

    Here’s where Blackmagic wish bug reports to be posted.
    https://forum.blackmagicdesign.com/viewforum.php?f=32

    Posting here may be of interest to COW readers but will not get back to Blackmagic

  • Glenn Sakatch

    July 1, 2019 at 2:09 pm

    You can always send a question to Blackmagic support.
    Don’t assume someone on this forum is taking up the tasks of reporting other peoples findings to Blackmagic.

    At the bottom of their support page is a link to email or phone with a specific question or concern.
    They have a forum on their site as well, and as much as they do monitor it, and chime in, it isn’t really the official way to post a support ticket. Sometimes they respond to forum posts…sometimes they don’t.

    Glenn

  • George Dean

    July 2, 2019 at 1:44 pm

    As others have pointed out……

    Phone support for Resolve is for the studio version ($300). You can get support from the community at the Resolve forums for the public (free) version. The Resolve Facebook page is for professional users of Resolve.

    Regardless, you are not going to get a lot of support for a lot of issues for the beta version regardless of it being the free or paid for version. Resolve released the beta version for users of all levels to report bugs and problems so they can address those issues in future releases, not spend time with end users to fix it in the current release.

    Beta versions are for testing, not production. By using the beta version you are a community free tester, one of the guinea pigs! One of the most important parts of being a tester is to include the log files when reporting bugs and issues. Development uses the logs to determine what is happening in the background, the part as a user you do not see, and help them discover the question ‘why’.

    I don’t understand your comment about 16 beta being “more intuitive” than v15. It is the same interface, but whatever works for you, just keep in mind if you are doing production with a beta version you can expect errors, problems, issues, crashes, and instability.

    Best Regards……George

  • Terence Christopher

    July 2, 2019 at 4:34 pm

    Hi George. Thanks for your comment. I wrote the note solely to raise the possibility of a bug, not to request help. I have subsequently reported it on the Black Magic forum as I was advised to. I am now struggling with resetting the audio/video synch on clips that were fouled up by some previous programme that I had used. Though not yet successful I have found it easier to use than in 15 though perhaps it just reflects where I am on the learning curve.
    I am still accommodating to the need for gobs of disc space for handling the uncompressed files. I am now doubtful that I can fit two year’s videoing onto 8 TB ignoring backup.
    Thanks for your help
    Graham

  • George Dean

    July 2, 2019 at 5:43 pm

    Hi Terence,

    You have jogged my memory, and although I don’t recall the specifics I do now remember you had some previous threads fighting the m2t files and available disk space with your large and multiple projects.

    It’s good that you reported the bug, as it may not just be in v16 beta but also in v15, just so obscure that others haven’t found it or haven’t reported it.

    Anyway, best of luck getting things in your project linked up and finished up.

    Best Regards……George

  • Terence Christopher

    July 3, 2019 at 2:24 pm

    I have followed everyone’s advice and sent the information to the Black Magic forum.
    Thanks everyone for the advice.

Page 1 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy