GoLive CS2 crashes regularly for me several times a day, and has even managed to crash WHILE SAVING A VERY IMPORTANT FILE, which wiped out an entire day's work for me, causing me to redo it all. I want to warn you about GoLive - it is the most frustrating, least reliable, most crash-prone app I have used since switching to OS X. at the end of the day real web designers hand-code anyway! i'm sure both do what they do equally as well and you should use whichever one you feel most comfortable with. Whatever the differences between the latest iterations of these two old war-horses, it hardly matters. it just happens to be slightly less spaghetti-like than the code generated by golive! dreamweaver still generates horrible code spaghetti and takes about a hundred lines of said electronic pasta to do what you can hand-code in one. Then when using CSS for layout became the 'next big thing' golive was left behind, as macromedia started really pushing the fact that dreamweaver wrote 'clean, standards compliant code' and thus dreamweaver gained the reputation as being the professional's choice. that was back when both apps created their layouts using clunky, hacky, nested tables, built with horrible code spaghetti - when no-one really cared about concepts like standards compliance, as long as it worked on exploder and netscrape. ![]() I used to use golive way back in the days when it was called 'golive cyberstudio' and it was streets ahead of the similarly youthful dreamweaver at the time - at least in terms of ease of use. but it seems like adobe thinks there's life in the old dog yet. i'd thought golive was destined to be taken out the back and put out of its misery with adobe's gobbling up of macromedia. If an update to Premiere Pro could fix this bug (it only appears to happen when Premiere CS6 is installed) as well the loss of Capture, I would be happy.I'm surprised to see this release. I’m not sure if this bug was fixed as the last submission to the Apple discussion was dated 20 June 2012 and the ‘Branched to a New Discussion’ link at the top of the page goes to a removed page. Thankfully I am still able to hear sound in Premiere through my line out so I can still edit. This bug is detailed by others in Apple Discussion page. However, my Mac Pro has now lost all system audio - no Quicktime (”an unknown error -101”), no CD/DVD sound and the iTunes progress bar does nothing when I press play. So I followed the advice here and uninstalled Premiere Pro and reinstalled it from the Production Premium disc and then updated to version 6.0.2. But even if that works it doesn’t solve the problem on all the other computers.Ī cautionary tale:- I too fell foul of the Premiere Pro CS 6.0.5 update bug and kept losing my Firewire Capture. (Macs running Mavericks) In one particular setup we might try using a capture card. Neither of these are options, as least in our case. ![]() Some users have suggested other solutions such as using HDVsplit and HDVxDV for capturing. The solutions presented by actual Adobe techs are unacceptable. That said, I join all the many users who are struggling with this problem. The university-wide method of managing student computer user accounts and login authentication is not compatible with Adobe's per-user account requirements for CC. ![]() I should also note that moving our department to CC is not an option for us. This move required the purchase of additional licenses of CS6 Master Collection for every mac in the department. I oversee 60+ computers in a university journalism department and recently made the decision to leave FCPX and go with Premiere. I'm not ready to throw in the towel just yet.but I'm getting closer. As much as I hate Final Cut Pro X that is apparently the route I'll be heading.Īdobe must not be as focused on cornering the video production realm as I thought, it's a shame because I really like Premiere Pro, very disappointing! Only to find that this problem has not yet been addressed. So I grabbed a camera, shot some footage, plugged the camera into my MacBook Pro and tried to capture the footage. As the company owns 3 Canon HV40s they use to shoot training videos with. I told them to hold off so I could do some testing, due to this issue. I was asked to teach a class on video production for the web and the company I work for was planning to invest in 4 new MACs and Adobe Master Collections for each. I have been using FCP 7 for my capturing and editing since this issue started and hoped that a fix would be along shortly. I can't believe that this issue has existed since Aug. Time to throw in the towel? I have been an avid supporter of Premiere Pro since I started using CS3.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |