Kevin Monahan
My feedback
-
4 votesKevin Monahan
supported this idea
·
-
18 votes
-
2 votes
-
8 votesKevin Monahan
supported this idea
·
-
3 votesKevin Monahan
commented
I also had trouble with audio playback on an underpowered MacBook Pro like yours and I think the system requirements might be too high tor this hardware nowadays. If you can turn off the video track and just play audio and it plays OK, then you know. If you don't want to buy a new computer right now, invest in learning the proxy workflow and you'll be cool. Learn it, know it. love it.
-
1 voteKevin Monahan
commented
What kind of "help" were you looking for? If you want actual help getting your system going again, contact Adobe Support. https://helpx.adobe.com/support.html
-
2 votesKevin Monahan
commented
System requirements have been bumped up for CC2019. You need a 6th or 7th gen CPU. Yours is a 4th gen CPU. A GTX 980 has 4 GB VRAM, which is the minimum for the recommended system requirements.
An editor has to be ready to update major hardware components every 5 years or so. I'd say your system is reaching that threshold and it is probably time to look at a new computer—sorry to say.
-
7 votesKevin Monahan
commented
Your computer is probably out of date and needs an update. Try the proxy workflow and let us know if that works for you. Use ProRes Proxy, not H.264
-
12 votesKevin Monahan
supported this idea
·
-
1 voteKevin Monahan
commented
Is this a project you updated from 13.x to 13.1? Have you deleted media cache? What happens if you do a test in Software Only mode?
-
6 votesKevin Monahan
supported this idea
·
Kevin Monahan
commented
This should be easier. Upvoted.
-
8 votesKevin Monahan
supported this idea
·
Kevin Monahan
commented
Agree that this is a problem that needs a solution. Thanks for pointing out the pain points. Upvoted.
-
1 voteKevin Monahan
commented
Rendering previews or exporting footage? If you are rendering previews, try a different preview codec. If you are exporting footage, also try a different codec; something like ProRes. Try also a test without the AE comps in the sequence.
-
3 votesKevin Monahan
supported this idea
·
Kevin Monahan
commented
Upvoted. Thanks for the request.
-
1 voteKevin Monahan
commented
Kind of hard to file a bug on that without more detailed information about how to reproduce that bug. Any other info you can give?
-
1 voteKevin Monahan
commented
Have you tried deleting media cache? Deleting preferences?
-
1 voteKevin Monahan
commented
Not seeing it on Mojave. Which version of macOS are you on? Can you try clearing media cache and creating a new project? Still having the issue?
-
3 votesKevin Monahan
supported this idea
·
Kevin Monahan
commented
You may want to create a separate request for your second request. I heard that one request per entry is how the team likes to read and collect data on these requests.
-
1 voteKevin Monahan
commented
That's no good. You can get some troubleshooting help here: https://forums.adobe.com/community/premiererush
You can also tweet to @AdobeCare or contact Adobe support by phone or chat: https://helpx.adobe.com/support.html
-
2 votesKevin Monahan
commented
Thoughtful suggestions. Upvoted. Thanks.
Kevin Monahan
supported this idea
·
Wait, what? What kind of video files is this? From a game stream? You may want to capture your games with a hardware device, like an Elgato. That works a lot better. Patching is a different story, you just have to make sure that the all the "blue boxes" are enabled for V1 and A1. Pretty common problem. Hope that helps. ^KM