My production machine is more similar, an X570 Ryzen 7 workstation, but its currently running 18.1.4 under Windows 10, and it won't be upgraded (to 18.6.x) before December due to ongoing work commitments. Yes, if you'd like you can share it privately with me via PM, I'd be happy to test, but note that my 18.6 test machine is a 2020 M1 Macbook Pro, so not very comparable to your set up. Now, try again to convince me that "I am the problem"īartReynaard wrote:However if you want (also for the Product Owner) I can give you the uncompressed on private.Understood. but I have to be very careful because the 18.5.1 crashes after a while as well. it didn't suddenly crash like the 18.6 so I was lucky and able to do """all""" what you see here below. and guess what? i was able at least to to this. It's quite blatant that when I do anything on this magic mask on the system crashes. Even if I make some mistake, it's not justified such kind of crash. And if not, you might have to consider alternative options.īesides the fact I misunderstood you previously (I'm not certainly in the normal mood with this issue), it doesn't mean I am the issue generator.Īt the end the day, it should work with a couple of clicks as I made. If there is genuinely a bug then the extra crash reports should help identify it. ![]() If you'd like, upload the source (or section of it) to a file sharing site and post the link and others, including BMD, can try to see if they can reproduce the crashing issue with the same source. Crashes as wellĪndy Mees wrote:The common denominator in all these issues seem to be you and your computer, Bart. Many of the H.264/H.265 codecs out there are also limited to 8-bit color, which is another issue for post, since it will tend to "break" under a lot of processing (like keys, secondaries, etc.). Their lack of unique file names and non-conflicting timecode also creates havoc with conforms. Using them puts a lot of stress on the computer, since it has to de-compress the images and play them back at speed, in addition to applying all the processes Resolve requires. Marc Wielage wrote:H.264/265 and other highly-compressed Long-GOP codecs can be difficult for post. Proxy Media can also work very effectively (and is preferred in some ways). My preference is to do it manually, because then I can control where the files go and how they're named. The alternative is to use Optimized Media, which basically transcodes it all in the background. You'll get much better performance that way. ![]() My advice is to transcode all the H.264 material to a simpler codec for your system, something visually-lossless like DNxHR SQ or ProRes 422HQ, and use that instead. H.264/265 and other highly-compressed Long-GOP codecs can be difficult for post. Needles to say that after a while DRS crashed also (closed itself) and I cannot work on this footage. ![]() You see the mask I was able, after the previous crash, to paint.įortunately now the crash was not resetting the machine and not damaging the small app I used for the screencast (just the first time I tried to use it so I could show you what I meant in all this thread) So, I started with this scene which has a duration of 2 seconds. The footage is 1280x720 (it was made almost 10y ago) and I have to change something. As soon as I restart to track with the Magic Mask, it make crash the driver immediately.Īfter that I was a bit "luckier" please here what I was able to get for you so you can understand better: Note I should update the title of the thread since this issue still there and it's even worse. This morning back to work on the same video.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |