David Busse
Forum Replies Created
-
Oliver,
I am having this problem on a 2012 iMac and a 2014 iMac. On a 2013 MacBook Pro it was working fine. We are now running all on 12.0.1Also, FWIW had a problem where XML from Premiere 12.1 from our laptop wouldn’t work in 12.0.1 so I sent the XML to Premiere 2017 and it opened in there then I was able to update that project to 12.0.1
Video Producer/Editor
https://cidesigninc.com/ -
Agreed! Mine wouldn’t even open. After 1.5 hours of troubleshooting, uninstalling, reinstalling I was able to get back up and running by downgrading back to 12.0.1
Video Producer/Editor
https://cidesigninc.com/ -
This happened to me to. I uninstalled and am up and running again with 12.0.1
Video Producer/Editor
https://cidesigninc.com/ -
David Busse
October 15, 2017 at 8:27 pm in reply to: Premiere is using more RAM than I have on my systemThanks! Good to know.
In this case, the problem is still happening even though ~20% of my startup disk space is free. I also did all troubleshooting after clearing space off of my disk.
Video Producer/Editor
https://cidesigninc.com/ -
David Busse
October 14, 2017 at 8:29 pm in reply to: Interview with Randy Ubillos and How I came to enjoy FCP X -
David Busse
October 14, 2017 at 8:28 pm in reply to: Interview with Randy Ubillos and How I came to enjoy FCP XBrett, absolutely. Apple’s poor roll out of FCP X with the timing of me just graduating college is what drove me away from it. I think had the timing in my own life been different that I may have been more up for exploring FCP X and seeing what it really had to offer, but at the time Premiere Pro offered the closest thing to FCP 7 and I didn’t want to risk the early days of career on learning completely new software. I still believe switching to Premiere Pro was the right move for me and I have no regrets about not giving FCP X a better chance back then(for the record, I did dabble with it for a few projects). I’m glad to hear it is software that works great for you and I hope that I can convince some members of my local community to give it another chance.
PS…didn’t mean to double post this, still getting used to the functionality of this forum and I wasn’t able to edit the post I made above.
Video Producer/Editor
https://cidesigninc.com/ -
David Busse
October 5, 2017 at 5:01 pm in reply to: Interview with Randy Ubillos and How I came to enjoy FCP XAndy, I agree with you that Premiere is still great software. There is no reason that we have to be either with FCP X or against FCP X. For me part of what muddied the FCP X waters over the years was the black and white nature of many debates. To me, both Premiere and FCP X are tools that are both very capable. The rest is a matter of opinion and needs.
Brett, absolutely. Apple’s poor roll out of FCP X with the timing of me just graduating college is what drove me away from it. I think had the timing in my own life been different that I may have been more up for exploring FCP X and seeing what it really had to offer, but at the time Premiere Pro offered the closest thing to FCP 7 and I didn’t want to risk the early days of career on learning completely new software. I still believe switching to Premiere Pro was the right move for me and I have no regrets about not giving FCP X a better chance back then(for the record, I did dabble with it for a few projects). I’m glad to hear it is software that works great for you and I hope that I can convince some members of my local community to give it another chance.
Steve, Thanks!
Video Producer/Editor
https://cidesigninc.com/ -
Thanks for the responses. I see what you guys are saying.
FWIW I also discovered the “Used Media Ranges” tool and that is extremely helpful in creating a selects sequence. Before I had everything tagged, but no easy way of seeing what footage was already pulled into my sequence.
Video Producer/Editor
https://cidesigninc.com/ -
David Busse
June 26, 2017 at 3:22 pm in reply to: Premiere is putting audio cache files next to originalsI do not use Audition. It is not even installed on my computer.
-
I didn’t see your post at 1:32:41 pm when I responded.