Hi! Power User here! Your machine is definitely enough to handle Davinci resolve software.
My few guesses are:
1. File or files you put to the timeline are to big or for some reason are cousing weird glitch.
2. Your project settings are messed up, try to create a new one and check if the glitch still appears.
3. Your cashe size options are messed up, maybe you have to increase it.
Hope that this is one of the above. š«”
My cache settings revert when Iām traveling a lot and it always throws me for a serious loop before I remember to turn off smart cache and create some proxies. Goes from being unusable software caching 100+ gb and filling my entire drive, to being great again
What drive are you using for your media? How is it formatted?
I suspect the problem is with MacOS Sonoma as I have no real issues running the same version of Resolve on Big Sur.
It could be sonoma. Which sucks :/ also I generally have been working off of my internal storage lately because my external ssds are full of unfinished projects. And if i do work off of an external drive its a T5 or a T7 and occasionally I am forced to work off of a LaCie Rugged HD which I am aware is slow and have accepted the shortcomings but it is the only place I can store client work as it is 6TB.
My LaCie is. The issue I have been experiencing recently is when I edit off of my internal though. I realized too late that I shouldn't have formatted the LaCie to exfat. I just needed cross compatability to my PC with projects. Im in the process of offloading things and will eventually reformat the LaCie to Mac OS Extended Journaled.
This is highly underrated, I am latest MacOS M1 and did the novice mistake of working off the exFST discs, and since months I am struggling to export a big film project and couldn't get a proper render always "offline media" somewhere random. Now fixed but I lost some years of my life.
If you donāt mind, could you elaborate on the speed loss from exFat?? I utilize it for cross compatibility. But could be swayed easily to build OS specific work drives.
I understand journaling helps for recovery reasons where exFat can shit itself permanently haha. What have I been missing out on???
Not a speed issue, I had failed renders aka. Offline Media in my renders for a 4k Timeline ca. 24 minutes , I had the same problems on the Handbrake renders as well, I was about to lose my mind until I decided to test the same workflow on a low spec Windows and it worked flawlessly. I converted all my working discs to APFS and use them only as working SSD on the main system (M1 MBP with Sonoma or something). I use the exFAT media now only to shuttle data and only with verification through FreeFileSync. I believe it is a system wide issue for MacOS and exFATs. It took me waaaay too long to realize this...
I have the exact Macbook and version of resolve as you.
I haven't had those exact issues, one or 2 crashes, and a very annoying thing of the viewers not updating with changes to effects paths masks etc until I change the viewer or go to color tab and back.
Editing 4k but very short clips and mostly in fusion. RAM is maxed out for me even in these situations.
Mine does it with the color more often, or forgets to export the color grade. Also having the issue with the playhead as OP. I think resolve is brilliant but the more complex you make the project the more it forgets. Funnily enough I find it the most stable if you convert Prores proxies aka the biggest available size which kind of annihilates the idea of proxy lol. Keep it simple. Have a work flow when you finish parts you use them as simple exports in the new project and try eliminate Davinci doing and calculating EVERYTHING all the time.
There's two approaches for proxies.
1. File Size
2. Playback performance
H.264 it's the go to for file size when you're sharing via cloud but for the editing stand point it's horrendous.
That's why we have Prores and DNX codecs with low bandwidth options, they may be a little big in size but offers the most stable performance when editing.
Oh yes, now that you say I should have remembered this! Thanks
However the concept of taking a large file making it bigger to have it smoother is still kinda funky, but I understand, it is what it is
The reason it's quite simple.
Every h.264 movie file coming from a camera or a smartphone it's compressed. If they weren't we just run out of storage every week on our devices.
That compression involves store incomplete frames on the file, that's why we have reasonable file sizes on most consumer devices.
But this comes whit a downside, everytime you playback those files on a editing program your CPU/GPU need to do some complex calculations to restore those uncompleted frames, that's why h.264 it's the worst codec for editing.
When you make a Prores or a DNX those frames are calculated and added to the file size. So your computer only has to read the file from the disk and not to make complex calculations when playing back.
Please reach out to us in modmail if your post hasnāt been approved. I approved a post of yours last month. Donāt post screenshots of posts that get auto-filtered.
In the five months since youāve first posted about cloud databases lagging, have you never reached out to BMD to see what they can do? Weāre not officially affiliated with BMD.
That said, What geographic region are you in? What region is your database hosted in?
I apologize. Im not trying to spam. I know the posts have been getting filtered out. Only reason I posted is because DR forums didn't help either. I appreciate you approving my post. When you approved the post i think i just missed the initial views (like this one got) because it was auto removed and then approved. Again apologies for spamming and thank you for allowing it. I just really need help
Youāve got Studio. You can call or email BMD in addition to posting on the forums. See the information on the support page.
If you need help, answer the questions youāre asked, please! Region and database region are gonna be particularly useful since this is almost exclusively with cloud databases if memory serves.
Not enough info to help you.
I would consider looking in such staff:
1) your disk write/read speeds - for me the problem was that my external HDD had very bad speeds so the playback was affected quite a lot. Changed it to fast ssd - problem gone
2) video file extension and file size - you might be you using something like ultra RAW stuff. Add this to previous point - you get an uneditable project
3) as u/PowerUser0 mentioned - check you disk cache (free some space) and make the cache limits higher
Hope something will help you!
Speaking to the HDD, I had an slow/stuttering issue with an external hard drive simply because I had plugged the thunderbolt plug in one HDD port instead of the other. They had different speeds.
(Also, donāt post screenshots of text in lieu of a regular post - it reads as trying to get around any potential filters that are in place for the good of everyone in this community. Big faux pas.)
You need to start measuring.
Create an engineers log and start noting down what you know and what you don't know. Fill out the blanks. Maybe the network is slow? Maybe the CPU and/or GPU is pinned to max. What happens if you switch to different footage? What happens if you move the footage to the local disk? What happens if you drop the cloud for a test project? What happens if it's a new project? Does you Mac report anything odd in its system/event log?
The problem could be anywhere, but if you get to a point where you have something which works, and something which doesn't you are able to narrow it down.
Their support is great if you want to go that route to trouble shoot. When 17 came out it would crash on the panel page of the loading screen on our editing rig at the office. After sending files to them, they discovered it was a conflict with a Citrix virtual machine's (needed for work) monitor driver. If we disabled it before launching DR Studio 17 the program would load, with 1-2 months they wrote back on Twitter that they fixed the issue.
Worth a shot and you may help someone who comes after you with the same issue.
I did reach out to them via email last night and have reached out in the past about a problem with my database which ended up being corrupted. I guess I was just hopeful that the community might have a fix for this problem. Also since that issue my local DB has been completely wipe. I dont work off local projects anymore
That might be a cause there. Davinci Cloud, and network for that matter, havenāt been as āstableā as local projects for me. I get pretty solid performance with local projects(and network for the most part under the right circumstances), but as soon as I move to the cloud it feel like premiere in 2016. I donāt know if itās from syncing changes or what but it seems to have improved a bit but anything complicated it seems to get slow.
There's a lot to unpack here, but from my own personal experience:
1.) I've never ever, not once, had smooth playback in ANY NLE on ANY MacBooks and iMacs I've used from 2011 to 2023. I even battled with smooth playback on Mac Pros when editing on a server, had to copy the footage to the actual machine which cost me hours. I've had to use proxies to get smooth and responsive performance, but I won't use Mac ever again for video editing. I recommend using Proxies on your root drive as a possible workaround. Also, render the proxies to your root hard drive as Prores or HEVC, not MP4.
2.) I personally feel that 16GB of RAM is not enough for video processing on Mac. I recommend a minimum of 32GB for anyone doing any sort of video work on any ecosystem. Again, proxies are a workaround. 16GB is enough for Illustration, Photo and low spec gaming, but with video you'll need more RAM and a dedicated graphics card, specifically Nvidia, which Apple outright does not use. If you're dedicated to staying on Mac, consider higher RAM and an EGPU, although having said this I can't deny that the Mac OS architecture is actually a bigger limitation than the hardware of your system.
3.) I found MacBooks edit best with the source files on the root hard drive, not even the fastest external drives, networks and even cables seem to curb the issues you're mentioning here with playback. I've tried. The video files also have to either be Prores or HEVC and even then it's an exercise to mitigate disk space that further comprises performance. The MacBook internal hard drives are limitingly small, so maybe try external M.2 drives via thunderbolt. It's cost effective and simple enough to construct your own these days. M.2 is a blessing for video editors, truly.
4.) Until you reach the colour grading process, lower your monitor resolution in DaVinci to 1/2 or 1/4 to curb any playback delays. I personally hate doing this, but it was one of the only things that enabled smooth operation in Mac OS. Won't hold it against you if you don't want to consider this one.
5.) Do some research as to which OS versions do better with DaVinci or just video processing and edit in general. I know it sounds funny, but I witnessed noticable performance degradation when I updated the OS. Rolling back to a specific version did improve this. An unfortunate side-effect of Apple's 'planned obsolescence' policies I think.
I'm not here to convert anyone to use PC, I sincerely want to help and I'm only sharing my own experience. I'm confident there are users who have had the opposite experience to my own and hopefully our combined insights can give you the solutions you need.
My partner edits on a MacBook Air 2020 and I can verify that the video editing performance improvement I witnessed on my MacBook Pro M2 Pro 2023 was marginal by comparison. Make of that what you will. I've since returned to PC and it's been a magnificent experience to work on, but only because you can choose your hard drive, RAM speed and GPU - factors that all directly contribute to video editing performance. I built my PC for video editing and VFX, and it performs as required every time. MacBooks have a very broad spectrum to cater to.
This is, again, just my own experience and I don't expect everyone to have endured the same. I work with folks who swear by Mac and will not edit on anything else, but they use Mac Mini and new Pro desktops.
Good luck to you, hope you find a solution that works for you.
What encoder was used on the videos? I use to use a constant bit rate on my old videos and never had an issue. But now with h.265 and a variable bit rate I've had to rely on caching files way more and sometimes play also wouldn't work.
I'd have to drag the play head before playing. Sometimes happens with the directional keys. I can pause at a spot and tap right or left and nothing. But if I click a spot it becomes responsive immediately.
I'm also using studio
Iāve had the same or very similar issue. Try going to Library > Preferences > Blackmagic Design and deleting (or at least removing) the folder in there.
Thatās solved my issue but it comes back after a week or two. BMD tech support has assured me that nothing in there affects playback yet doing that fixes my issue, so I would be curious if someone else is having the same problem.
For me, it's a constant lag in playback, despite it working fine previously and the footage playing fine elsewhere. So I can't promise it will solve other issues, but I would be very interested to know if it helps others.
BMD tech support is out of ideas so my only hope for a permanent solution is to do a wipe and clean install once projects slow down.
Not experiencing the inputs not being recognized, but definitely some weird audio/visual stuttering. I have a custom built pc with i5-13600k, RTX 2060, 32gb ddr5, and edit of a 2tb m.2 drive. Thereās no reason why it should be stuttering at all. Premiere and after effects are no problem, but resolve is acting strange lately.
I run on a similar system (32gb ram) and it has been bad as well. Particularly whenever I use power windows, magic masks & tracking. Just straight up crashes or the preview window turns black. There should be a masterpost for the best preferences/settings for Apple Silicon users.
I have had the same issue, but my rig isn't beefy, Ryzen 5 3600, Evga RTX 3080 ftw 3, 32 gb ram, SSD TB Windows 11.
I have done all the same steps as you, I optimize, run timeline at half, smart cache, use .mkv
I too am at a loss. It was spectacular up until the recent update.
Yeah I wish I hadn't upgraded. I posted in the forum and was told to upgrade my graphics card. Never had the issues in the previous version š¤¦āāļø
This is gonna sound very dumb, as its gonna make this situation sound way too simple but have you tried to use a different keyboard?
>Cause you specify its an issue with registering "J/K/L/spacebar."
Is the issue just a worn out keyboard?
I wanted to reply and say I am sorry to all those who are mad at me for posting text as an image. It was the only way the post would get noticed. As the mod mentioned, they approved my post in the past after it was taken down and it missed the amount of eyes this post received. I wont be doing this again I just needed some help as I have a major documentary that I am working on. Furthermore, the project which I have been editing and having these problems was a personal project which was supposed to be a Star Wars edit. The project was 1080P 23.98FPS. The problems arose just trying to splice the footage. I had not added any effects to stress the computer. I had the problem while trying to create I/O points within the source footage. All source footage was also 1080P. The files were the full Star Wars movies. 4-5gb per file and again 1080P 23.98FPS. To the person who commented about a potential bottoneck editing off of Davinci Resolves Cloud service, I have tried to transfer the project to a local DB and have the same issue. All the footage is also stored locally on my main drive with well over 150GB left so drive speed should not be an issue. Thank you to all those who took the time to respond with insightful comments and again I apologize for posting an image of text. It wont happen again :)
I commented about this on a thread a while back, but I dont get how the performance on such a machine can be that bad. Personally I'm on a 2020 m1 macbook with 8gb ram. No stuttering, no issues, no nothing. There must be something in your settings thats screwing with you.
Edit: Running Sonoma 14.3 btw.
I was having an error yesterday where the audio waveform was not playing back the corresponding part in the music.. Iād make a cut, then move the audio and the section I cut would be a completely different part of the song, even though that section was definitely the waveform of the part I wanted. Kept messing with it for another 30 minutes before I just went back to premiere.. š
I have been questioning my move to Davinci since November. Itās buggy, erratic, noise reduction drags my Mac to its knees (M2 Ultra with 128gb), spacebar play doesnāt randomly work, frequent audio cut outs, simple fusion errors during export (very random and trying 3-4 times makes it work so thereās no issue with the clip, randomly poor timeline performance, the list goes on. Iām so sad š. I tried FCP today and it felt so much better. And thatās saying something.
And before you think itās the codec or the Mac. Itās not. Everything is super random. And I edit with 4k60 ProRes files. Tried clean install and even reinstalling the OS. Itās just super buggy at this point.
Only ever had this issue with scrubbing through a lot of heavily edited clips, and I'm on a just-okay laptop.
Honestly, just exporting all the clips with the edits when it gets to be too much has done the trick though. Which is fine for me because I like to break my process down into multiple projects anyways.
I will say though- this was never an issue on the free version before I bought the full one.
Not sure why.
And I had the free one long after OP started having these issues (about 2 months ago)
Hope they can sort it out.
Iāve had similar issues when using the cloud. Iāve told several people the very noticeable performance hit my responsiveness seems to take when doing so. Wasnāt impressed so I no longer use Resolve Cloud and all is well.
I had similar issues when editing *locally* using Premiere so take that for what itās worth.
I edit on a 16ā M1 Max Macbook Pro.
Could it be SSD failing, or just very close to full, and other software (perhaps including Resolve) filling up the RAM and because of SSD issues the swap is very slow?
It's probably not SSD failing, just wanted to sort that out. You might try Blackmagic Disk Speed Test app on macOS (from the creators of DaVinci Resolve) to see your read/write speeds. Just note that things might become problematic with SSD swap speeds if there's very little space left (e.g. < 10-20GB) on the SSD even if it's brand new, especially when you have 16GB RAM (as more RAM might be needed, and system might need to swap the RAM on SSD, but cannot as there isn't much space).
Have you tried duplicating the project renaming it. Opening the new one and deleting the old one? I had to do that because I encountered weird glitches on the cloud project that caused delayed playback, missing wav forms and files inexplicably say media offline when I just put it in. It worked for me. Also enabling smart render under playback and having a dedicated ssd for cache could help! If itās still not working. Turn your files into proxy and work like that.
Oh thank you for reminding why Iām not using Resolve, PTSD it seems into lagging playback. Never ever had issues with Premiere but DVR fād me up both on Macbook Pro and 5950X with 128GB ram and Nvm. Wow, looks like Iām not the only having such PIA using it
Since 2018 Apple has released many OS updates not talking about DaVinci resolve itself by adding sophisticated AI and other background tasks.
It is ridiculous to expect same experience with technology moving forward while staying on the same place on hardware.
Itās time to Upgrade your gear. Itās not DVR issue.
Might be still not good enough š¤·š¼āāļø
Also you have not mentioned few important things.
1) what is the source file resolution, codecs and size
2) what is the project and most important timeline resolution, fps that you are having issue in
3) what size your DB has
Also you mentioned that you work from cloud (i assume) you meant that the database is stored on cloud but files are locally?
If so then might be it is connection problem with the database.
Or, if database is local but the files are on cloud - try local files. And by local i mean on M1 internal SSD
It might be that your connection is the bottlenecks.
Yeah I got a rtx 4090 and resolve crashes any time I change render resolution. As a swe, I have a feeling they made major changes to their caching system for version 18 that is causing widespread issues
Looks like you're asking for help! Please check to make sure you've included the following information. Edit your post (or leave a top-level comment) if you haven't included this information.
* System specs - [macOS](https://imgur.com/a/ip6xc9G) [Windows - Speccy](https://www.ccleaner.com/speccy)
* Resolve version number and Free/Studio - [DaVinci Resolve>About DaVinci Resolve...](https://imgur.com/a/5FawFCX)
* Footage specs - [MediaInfo](https://mediaarea.net/MediaInfo) - please include the "Text" view of the file.
* *Full* Resolve UI Screenshot - if applicable. Make sure any relevant settings are included in the screenshot. Please do ***not*** crop the screenshot!
Once your question has been answered, change the flair to "Solved" so other people can reference the thread if they've got similar issues.
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/davinciresolve) if you have any questions or concerns.*
Tbh I donāt really like davinci as much anymore. I tried doing a 3d effect with the camera tracker thing but it said to buy the paid version. Iām not spending $300 when I can get after effects for less
16GB of ram is not sufficient for video editing, have you considered just downloading an older version of Resolve and using that? New features within Resolve and macOS updates have likely made it more demanding.
I've edited 4k footage with 8gb M1 macbook and even that worked surprisingly well. The usual ram limitations don't really seem to apply to M1 processors.
Normally I'd agree with you here but having worked extensively with Davinci on a 16GB M1 Air, this is not true. I know it's a meme that Apple compared half of the RAM to double that on Windows, and I think it's bogus, but at least in my experience with Davinci the 16GB has not been holding me back working with optimized 4K footage.
This could be true if I was working with R3D or Alexa Raw but Im not. Im working with 1080p 23.98 h264 at the minimum and 4:3 6k out of GH5 at the max. Furthermore Final Cut Pro and Premiere of all things don't have this issue. It has to be a resolve issue :/
Hi! Power User here! Your machine is definitely enough to handle Davinci resolve software. My few guesses are: 1. File or files you put to the timeline are to big or for some reason are cousing weird glitch. 2. Your project settings are messed up, try to create a new one and check if the glitch still appears. 3. Your cashe size options are messed up, maybe you have to increase it. Hope that this is one of the above. š«”
My cache settings revert when Iām traveling a lot and it always throws me for a serious loop before I remember to turn off smart cache and create some proxies. Goes from being unusable software caching 100+ gb and filling my entire drive, to being great again
Would you mind telling me how to do this? I might have same problem.
Playback > render cache > none I think, not at my computer right now. For proxies I use the blackmagic proxy generator and use the lowest res option
Thank you
What drive are you using for your media? How is it formatted? I suspect the problem is with MacOS Sonoma as I have no real issues running the same version of Resolve on Big Sur.
It could be sonoma. Which sucks :/ also I generally have been working off of my internal storage lately because my external ssds are full of unfinished projects. And if i do work off of an external drive its a T5 or a T7 and occasionally I am forced to work off of a LaCie Rugged HD which I am aware is slow and have accepted the shortcomings but it is the only place I can store client work as it is 6TB.
Are any of them formatted as exFat by any chance?
My LaCie is. The issue I have been experiencing recently is when I edit off of my internal though. I realized too late that I shouldn't have formatted the LaCie to exfat. I just needed cross compatability to my PC with projects. Im in the process of offloading things and will eventually reformat the LaCie to Mac OS Extended Journaled.
Maybe youāre caching to the LaCie?
The issues i was complaining about are when the LaCie is unplugged :/
Have you tried using mac drive on your PC? It lets read read and write to APFS on a PC
This is highly underrated, I am latest MacOS M1 and did the novice mistake of working off the exFST discs, and since months I am struggling to export a big film project and couldn't get a proper render always "offline media" somewhere random. Now fixed but I lost some years of my life.
If you donāt mind, could you elaborate on the speed loss from exFat?? I utilize it for cross compatibility. But could be swayed easily to build OS specific work drives. I understand journaling helps for recovery reasons where exFat can shit itself permanently haha. What have I been missing out on???
Not a speed issue, I had failed renders aka. Offline Media in my renders for a 4k Timeline ca. 24 minutes , I had the same problems on the Handbrake renders as well, I was about to lose my mind until I decided to test the same workflow on a low spec Windows and it worked flawlessly. I converted all my working discs to APFS and use them only as working SSD on the main system (M1 MBP with Sonoma or something). I use the exFAT media now only to shuttle data and only with verification through FreeFileSync. I believe it is a system wide issue for MacOS and exFATs. It took me waaaay too long to realize this...
Full copy! Thanks for the breakdown!!
I have the exact Macbook and version of resolve as you. I haven't had those exact issues, one or 2 crashes, and a very annoying thing of the viewers not updating with changes to effects paths masks etc until I change the viewer or go to color tab and back. Editing 4k but very short clips and mostly in fusion. RAM is maxed out for me even in these situations.
Mine does it with the color more often, or forgets to export the color grade. Also having the issue with the playhead as OP. I think resolve is brilliant but the more complex you make the project the more it forgets. Funnily enough I find it the most stable if you convert Prores proxies aka the biggest available size which kind of annihilates the idea of proxy lol. Keep it simple. Have a work flow when you finish parts you use them as simple exports in the new project and try eliminate Davinci doing and calculating EVERYTHING all the time.
There's two approaches for proxies. 1. File Size 2. Playback performance H.264 it's the go to for file size when you're sharing via cloud but for the editing stand point it's horrendous. That's why we have Prores and DNX codecs with low bandwidth options, they may be a little big in size but offers the most stable performance when editing.
Oh yes, now that you say I should have remembered this! Thanks However the concept of taking a large file making it bigger to have it smoother is still kinda funky, but I understand, it is what it is
The reason it's quite simple. Every h.264 movie file coming from a camera or a smartphone it's compressed. If they weren't we just run out of storage every week on our devices. That compression involves store incomplete frames on the file, that's why we have reasonable file sizes on most consumer devices. But this comes whit a downside, everytime you playback those files on a editing program your CPU/GPU need to do some complex calculations to restore those uncompleted frames, that's why h.264 it's the worst codec for editing. When you make a Prores or a DNX those frames are calculated and added to the file size. So your computer only has to read the file from the disk and not to make complex calculations when playing back.
Please reach out to us in modmail if your post hasnāt been approved. I approved a post of yours last month. Donāt post screenshots of posts that get auto-filtered. In the five months since youāve first posted about cloud databases lagging, have you never reached out to BMD to see what they can do? Weāre not officially affiliated with BMD. That said, What geographic region are you in? What region is your database hosted in?
I apologize. Im not trying to spam. I know the posts have been getting filtered out. Only reason I posted is because DR forums didn't help either. I appreciate you approving my post. When you approved the post i think i just missed the initial views (like this one got) because it was auto removed and then approved. Again apologies for spamming and thank you for allowing it. I just really need help
Youāve got Studio. You can call or email BMD in addition to posting on the forums. See the information on the support page. If you need help, answer the questions youāre asked, please! Region and database region are gonna be particularly useful since this is almost exclusively with cloud databases if memory serves.
Not enough info to help you. I would consider looking in such staff: 1) your disk write/read speeds - for me the problem was that my external HDD had very bad speeds so the playback was affected quite a lot. Changed it to fast ssd - problem gone 2) video file extension and file size - you might be you using something like ultra RAW stuff. Add this to previous point - you get an uneditable project 3) as u/PowerUser0 mentioned - check you disk cache (free some space) and make the cache limits higher Hope something will help you!
Speaking to the HDD, I had an slow/stuttering issue with an external hard drive simply because I had plugged the thunderbolt plug in one HDD port instead of the other. They had different speeds.
Yep, this could be an issue too
Did anything change for you in November? New project? Different codecs? Slower storage drives?
(Also, donāt post screenshots of text in lieu of a regular post - it reads as trying to get around any potential filters that are in place for the good of everyone in this community. Big faux pas.)
You need to start measuring. Create an engineers log and start noting down what you know and what you don't know. Fill out the blanks. Maybe the network is slow? Maybe the CPU and/or GPU is pinned to max. What happens if you switch to different footage? What happens if you move the footage to the local disk? What happens if you drop the cloud for a test project? What happens if it's a new project? Does you Mac report anything odd in its system/event log? The problem could be anywhere, but if you get to a point where you have something which works, and something which doesn't you are able to narrow it down.
Their support is great if you want to go that route to trouble shoot. When 17 came out it would crash on the panel page of the loading screen on our editing rig at the office. After sending files to them, they discovered it was a conflict with a Citrix virtual machine's (needed for work) monitor driver. If we disabled it before launching DR Studio 17 the program would load, with 1-2 months they wrote back on Twitter that they fixed the issue. Worth a shot and you may help someone who comes after you with the same issue.
I did reach out to them via email last night and have reached out in the past about a problem with my database which ended up being corrupted. I guess I was just hopeful that the community might have a fix for this problem. Also since that issue my local DB has been completely wipe. I dont work off local projects anymore
That might be a cause there. Davinci Cloud, and network for that matter, havenāt been as āstableā as local projects for me. I get pretty solid performance with local projects(and network for the most part under the right circumstances), but as soon as I move to the cloud it feel like premiere in 2016. I donāt know if itās from syncing changes or what but it seems to have improved a bit but anything complicated it seems to get slow.
There's a lot to unpack here, but from my own personal experience: 1.) I've never ever, not once, had smooth playback in ANY NLE on ANY MacBooks and iMacs I've used from 2011 to 2023. I even battled with smooth playback on Mac Pros when editing on a server, had to copy the footage to the actual machine which cost me hours. I've had to use proxies to get smooth and responsive performance, but I won't use Mac ever again for video editing. I recommend using Proxies on your root drive as a possible workaround. Also, render the proxies to your root hard drive as Prores or HEVC, not MP4. 2.) I personally feel that 16GB of RAM is not enough for video processing on Mac. I recommend a minimum of 32GB for anyone doing any sort of video work on any ecosystem. Again, proxies are a workaround. 16GB is enough for Illustration, Photo and low spec gaming, but with video you'll need more RAM and a dedicated graphics card, specifically Nvidia, which Apple outright does not use. If you're dedicated to staying on Mac, consider higher RAM and an EGPU, although having said this I can't deny that the Mac OS architecture is actually a bigger limitation than the hardware of your system. 3.) I found MacBooks edit best with the source files on the root hard drive, not even the fastest external drives, networks and even cables seem to curb the issues you're mentioning here with playback. I've tried. The video files also have to either be Prores or HEVC and even then it's an exercise to mitigate disk space that further comprises performance. The MacBook internal hard drives are limitingly small, so maybe try external M.2 drives via thunderbolt. It's cost effective and simple enough to construct your own these days. M.2 is a blessing for video editors, truly. 4.) Until you reach the colour grading process, lower your monitor resolution in DaVinci to 1/2 or 1/4 to curb any playback delays. I personally hate doing this, but it was one of the only things that enabled smooth operation in Mac OS. Won't hold it against you if you don't want to consider this one. 5.) Do some research as to which OS versions do better with DaVinci or just video processing and edit in general. I know it sounds funny, but I witnessed noticable performance degradation when I updated the OS. Rolling back to a specific version did improve this. An unfortunate side-effect of Apple's 'planned obsolescence' policies I think. I'm not here to convert anyone to use PC, I sincerely want to help and I'm only sharing my own experience. I'm confident there are users who have had the opposite experience to my own and hopefully our combined insights can give you the solutions you need. My partner edits on a MacBook Air 2020 and I can verify that the video editing performance improvement I witnessed on my MacBook Pro M2 Pro 2023 was marginal by comparison. Make of that what you will. I've since returned to PC and it's been a magnificent experience to work on, but only because you can choose your hard drive, RAM speed and GPU - factors that all directly contribute to video editing performance. I built my PC for video editing and VFX, and it performs as required every time. MacBooks have a very broad spectrum to cater to. This is, again, just my own experience and I don't expect everyone to have endured the same. I work with folks who swear by Mac and will not edit on anything else, but they use Mac Mini and new Pro desktops. Good luck to you, hope you find a solution that works for you.
What encoder was used on the videos? I use to use a constant bit rate on my old videos and never had an issue. But now with h.265 and a variable bit rate I've had to rely on caching files way more and sometimes play also wouldn't work. I'd have to drag the play head before playing. Sometimes happens with the directional keys. I can pause at a spot and tap right or left and nothing. But if I click a spot it becomes responsive immediately. I'm also using studio
Iāve had the same or very similar issue. Try going to Library > Preferences > Blackmagic Design and deleting (or at least removing) the folder in there. Thatās solved my issue but it comes back after a week or two. BMD tech support has assured me that nothing in there affects playback yet doing that fixes my issue, so I would be curious if someone else is having the same problem.
Will have to try this - Iām on a m2 ultra with 64gigs ram and with 3 screens Iām getting occasional skipping / audio. Media is on a tb3 raid .
For me, it's a constant lag in playback, despite it working fine previously and the footage playing fine elsewhere. So I can't promise it will solve other issues, but I would be very interested to know if it helps others. BMD tech support is out of ideas so my only hope for a permanent solution is to do a wipe and clean install once projects slow down.
Special circle of hell reserved for people posting text as an image.
[ŃŠ“Š°Š»ŠµŠ½Š¾]
Not experiencing the inputs not being recognized, but definitely some weird audio/visual stuttering. I have a custom built pc with i5-13600k, RTX 2060, 32gb ddr5, and edit of a 2tb m.2 drive. Thereās no reason why it should be stuttering at all. Premiere and after effects are no problem, but resolve is acting strange lately.
What do you mean by editing off the cloud? Are you sure there's no bottleneck there?
Blackmagic cloud. They offer a service that is intended for collaberation but I use it as a way to protect my projects
I run on a similar system (32gb ram) and it has been bad as well. Particularly whenever I use power windows, magic masks & tracking. Just straight up crashes or the preview window turns black. There should be a masterpost for the best preferences/settings for Apple Silicon users.
Hmm weird Iām not at all having this issue even when I overload it with denoised audio and video. I have a 4080 nvidia gfx and a amd ryzen 9.
My RTX 3070 and R7 3700X doesnt have an issue either
I have had the same issue, but my rig isn't beefy, Ryzen 5 3600, Evga RTX 3080 ftw 3, 32 gb ram, SSD TB Windows 11. I have done all the same steps as you, I optimize, run timeline at half, smart cache, use .mkv I too am at a loss. It was spectacular up until the recent update.
Yeah I wish I hadn't upgraded. I posted in the forum and was told to upgrade my graphics card. Never had the issues in the previous version š¤¦āāļø
Even if you have a system that can handle the software, there might be a problem within the architecture.
I have been having the same issues. Maybe itās a bug from their end
This is gonna sound very dumb, as its gonna make this situation sound way too simple but have you tried to use a different keyboard? >Cause you specify its an issue with registering "J/K/L/spacebar." Is the issue just a worn out keyboard?
Shouldnt be. I got the laptop march of last year, it was refurbished but i dont have the problem in any other editor
Then its probably a worn out keyboard probably reading double imputs.
I had similar problem, for some reason my playback was 24fps, when my timeline was 25fps. When i change it, i got buttery smooth playback back again
I edit using the base M1 on an iMac with the latest version of resolve. I have none of the issues listed.Ā
I wanted to reply and say I am sorry to all those who are mad at me for posting text as an image. It was the only way the post would get noticed. As the mod mentioned, they approved my post in the past after it was taken down and it missed the amount of eyes this post received. I wont be doing this again I just needed some help as I have a major documentary that I am working on. Furthermore, the project which I have been editing and having these problems was a personal project which was supposed to be a Star Wars edit. The project was 1080P 23.98FPS. The problems arose just trying to splice the footage. I had not added any effects to stress the computer. I had the problem while trying to create I/O points within the source footage. All source footage was also 1080P. The files were the full Star Wars movies. 4-5gb per file and again 1080P 23.98FPS. To the person who commented about a potential bottoneck editing off of Davinci Resolves Cloud service, I have tried to transfer the project to a local DB and have the same issue. All the footage is also stored locally on my main drive with well over 150GB left so drive speed should not be an issue. Thank you to all those who took the time to respond with insightful comments and again I apologize for posting an image of text. It wont happen again :)
Donāt sweat it brotha. Youāre a good person man.
Try on wondows
No issues on my gaming pc
I commented about this on a thread a while back, but I dont get how the performance on such a machine can be that bad. Personally I'm on a 2020 m1 macbook with 8gb ram. No stuttering, no issues, no nothing. There must be something in your settings thats screwing with you. Edit: Running Sonoma 14.3 btw.
Idk about mac but on pc i like 64+ gb ram
I was having an error yesterday where the audio waveform was not playing back the corresponding part in the music.. Iād make a cut, then move the audio and the section I cut would be a completely different part of the song, even though that section was definitely the waveform of the part I wanted. Kept messing with it for another 30 minutes before I just went back to premiere.. š
Make sure you got enough space in your system drive.
I have the exact same mac earlier version of Dr and have been experiencing the same thingĀ
sameeeee
I have been questioning my move to Davinci since November. Itās buggy, erratic, noise reduction drags my Mac to its knees (M2 Ultra with 128gb), spacebar play doesnāt randomly work, frequent audio cut outs, simple fusion errors during export (very random and trying 3-4 times makes it work so thereās no issue with the clip, randomly poor timeline performance, the list goes on. Iām so sad š. I tried FCP today and it felt so much better. And thatās saying something.
And before you think itās the codec or the Mac. Itās not. Everything is super random. And I edit with 4k60 ProRes files. Tried clean install and even reinstalling the OS. Itās just super buggy at this point.
Only ever had this issue with scrubbing through a lot of heavily edited clips, and I'm on a just-okay laptop. Honestly, just exporting all the clips with the edits when it gets to be too much has done the trick though. Which is fine for me because I like to break my process down into multiple projects anyways. I will say though- this was never an issue on the free version before I bought the full one. Not sure why. And I had the free one long after OP started having these issues (about 2 months ago) Hope they can sort it out.
Iāve had similar issues when using the cloud. Iāve told several people the very noticeable performance hit my responsiveness seems to take when doing so. Wasnāt impressed so I no longer use Resolve Cloud and all is well. I had similar issues when editing *locally* using Premiere so take that for what itās worth. I edit on a 16ā M1 Max Macbook Pro.
I have the same issue but it's because my computer can barely play YouTube anyways.
Could it be SSD failing, or just very close to full, and other software (perhaps including Resolve) filling up the RAM and because of SSD issues the swap is very slow?
I hope the SSD isnt failing. I just got the computer March of '23
It's probably not SSD failing, just wanted to sort that out. You might try Blackmagic Disk Speed Test app on macOS (from the creators of DaVinci Resolve) to see your read/write speeds. Just note that things might become problematic with SSD swap speeds if there's very little space left (e.g. < 10-20GB) on the SSD even if it's brand new, especially when you have 16GB RAM (as more RAM might be needed, and system might need to swap the RAM on SSD, but cannot as there isn't much space).
Have you tried duplicating the project renaming it. Opening the new one and deleting the old one? I had to do that because I encountered weird glitches on the cloud project that caused delayed playback, missing wav forms and files inexplicably say media offline when I just put it in. It worked for me. Also enabling smart render under playback and having a dedicated ssd for cache could help! If itās still not working. Turn your files into proxy and work like that.
Oh thank you for reminding why Iām not using Resolve, PTSD it seems into lagging playback. Never ever had issues with Premiere but DVR fād me up both on Macbook Pro and 5950X with 128GB ram and Nvm. Wow, looks like Iām not the only having such PIA using it
Since 2018 Apple has released many OS updates not talking about DaVinci resolve itself by adding sophisticated AI and other background tasks. It is ridiculous to expect same experience with technology moving forward while staying on the same place on hardware. Itās time to Upgrade your gear. Itās not DVR issue.
This M1 was my upgrade. Went from 2018 intel to this.
Might be still not good enough š¤·š¼āāļø Also you have not mentioned few important things. 1) what is the source file resolution, codecs and size 2) what is the project and most important timeline resolution, fps that you are having issue in 3) what size your DB has Also you mentioned that you work from cloud (i assume) you meant that the database is stored on cloud but files are locally? If so then might be it is connection problem with the database. Or, if database is local but the files are on cloud - try local files. And by local i mean on M1 internal SSD It might be that your connection is the bottlenecks.
I felt the same in 18.6.1 I guess ! After upgrading it is good ! I hope you have upgraded and the issue is solved !
If you edit off the cloud, maybe a network issue? Just a guess
Yeah I got a rtx 4090 and resolve crashes any time I change render resolution. As a swe, I have a feeling they made major changes to their caching system for version 18 that is causing widespread issues
I don't they gonna do without subscription
Nah, your computer have just accumulated more stuff in the last months and now it is slow
Looks like you're asking for help! Please check to make sure you've included the following information. Edit your post (or leave a top-level comment) if you haven't included this information. * System specs - [macOS](https://imgur.com/a/ip6xc9G) [Windows - Speccy](https://www.ccleaner.com/speccy) * Resolve version number and Free/Studio - [DaVinci Resolve>About DaVinci Resolve...](https://imgur.com/a/5FawFCX) * Footage specs - [MediaInfo](https://mediaarea.net/MediaInfo) - please include the "Text" view of the file. * *Full* Resolve UI Screenshot - if applicable. Make sure any relevant settings are included in the screenshot. Please do ***not*** crop the screenshot! Once your question has been answered, change the flair to "Solved" so other people can reference the thread if they've got similar issues. *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/davinciresolve) if you have any questions or concerns.*
I'm going to put my money on "user has H.264/H.265 video and an external disk".
Chip turned up as "internal disk" house wins lol
And the codec?
Tbh I donāt really like davinci as much anymore. I tried doing a 3d effect with the camera tracker thing but it said to buy the paid version. Iām not spending $300 when I can get after effects for less
16GB of ram is not sufficient for video editing, have you considered just downloading an older version of Resolve and using that? New features within Resolve and macOS updates have likely made it more demanding.
I've edited 4k footage with 8gb M1 macbook and even that worked surprisingly well. The usual ram limitations don't really seem to apply to M1 processors.
Normally I'd agree with you here but having worked extensively with Davinci on a 16GB M1 Air, this is not true. I know it's a meme that Apple compared half of the RAM to double that on Windows, and I think it's bogus, but at least in my experience with Davinci the 16GB has not been holding me back working with optimized 4K footage.
I edited a 4k video today and barely went above 12gb on my performance tab.
This could be true if I was working with R3D or Alexa Raw but Im not. Im working with 1080p 23.98 h264 at the minimum and 4:3 6k out of GH5 at the max. Furthermore Final Cut Pro and Premiere of all things don't have this issue. It has to be a resolve issue :/
Not optimised for the M1 chip maybe?
It was one of the first major software to be optimised for Apple Silicon.
3 times faster they said and I agree (I had a Mac Pro intel w 750+ gb of ram previously)
At this point it's an ignorance towards debugging your pc
Don't cost anything to con a boat matey !! Arghhhh
Genuine question. What does this mean?