[Andreas Ahston]

Thank you Bill, for sharing your insight.

The in-body stabilization sounds like it might solve some of the rolling shutter that plagues the sony alpha series. I’m wondering though, if these advantages of the a7r II might be included in the a7s II if and when that arrives. What do you think?

[Andreas Ahston]

I know how that feels. Thanks for your comment. I miss the old final cut too.

[Andreas Ahston]

Hi Sam

I’ll try and move the autosave location to the internal. That is a good idea.
For bigger projects I convert to prores. For smaller projects I often stay with the h264 that nikon dslr’s shoot on. H264 is certainly more suseptible to render errors and other irragularities, but I would not say that my prores projects have a better track-record when it comes to freezing and crashing.

[Andreas Ahston]

Hi Sam and Jon. Thank you for your replies. I am pleased to hear that it shouldn’t be like this and that there is hope for improvment. I’m running an updated premiere pro cc on a 2014 macbook pro retina 2,4 ghz, os X 10.9.5 and an external fast harddrive with usb 3.0 The problem of frequent crashes has remained pretty constant throughout different versions of premiere as well as os X for the last 6 months.
I would estimate that it crashes on average every 2-3 hours. Sometimes the crash can be linked to a particular thing that I want to do, and I will find ways to work around it. But in most cases I cannot discern any clear connection between what I am doing and the crashing. It just seems generally unstable in a way that other editing programs are not.

Do you have any idea where to start looking?

I’d love to hear from other who had similiar issues, particularly the autosave fail

[Andreas Ahston]

Thank you Michael. That is very helpful. I love how your comment goes to the core of the problem I’m describing. Now I understand that premiere’s lack of stability has nothing to do with the software itself, but that it is a consequence of my own lack of professionalism. I’ll look forward to seeing premieres crash less and less, as I improve as an editor.

[Andreas Ahston]

I see your point David. But don’t you think that a adobe has a responsibility that their product doesn’t crash everytime it’s being used? They are selling this as a professional tool, after all. I wouldn’t mind if it was just every once in a while. But it happens quite frequently. And when they include an autosave function, am I really to be blamed for trusting it to work properly?

[Andreas Ahston]

I just talked to someone from Adobe on the phone.

I had to sign out from Creative Cloud and sign in again. They said that the error is caused by being signed out –without being told so– and that the codecs becomes unavailable when you are not properly signed in.

I hope this works for you too.

Andreas

[Andreas Ahston]

Hi David

I am experiencing the same issue. I’m working towards a deadline and this is extreemly frustrating, and it’s costing money. I’ve found a partial workaround. That worked to some extent and that I’ve quoted in the end of the message.

Even though I managed to get my sequences back I’ve still got some way to go. My editing assistant have synced a lot of files while I was working on a different aspect of the project. Because this workaround is based on work done in sequences that can be imported from one project to another. But in my case the work that I need to import consists of merged files and I can import them from the other project.

This is not the first time Premiere slows down my work. The initial switch from FCP was easy, but I’ve run into a lot of strange bugs and errors like this. The damn thing just doesn’t work well enough to take over from FCP. Generally Premiere has a lot of problems with onlining material. It is strange that Final Cut Pro worked a lot easier with Adobe Photoshop than Adobe Premiere does. FCP would immediately update any changes made in the psd files. In Premiere you have to do everything from scratch if you have changes to any graphic element.

So in the off chance that anyone from adobe actually cares enough about it’s costumers to read this: You guys need to get your act together. I am just about ready to switch to Avid.

Andreas

“My solution:
1- Create a NEW PROJECT and save it in the same folder you have your project with the problem (DO NOT OVERWRITE your original file, save it with a different name you will need to import it in the end).

NOW here is the TRICK — >
2- Create a NEW SEQUENCE
2.1- Click on ANY of the presets you like
2.2- Now click on the tab SETTINGS
2.3- In the 1st option = Editing Mode — > CHANGE it to — > CUSTOM (DO NOT USE ANY of the Adobe presets)
2.4- Set the other parameters as you like
2.5- In VIDEO PREVIEW (for PC) I use Microsoft AVI — > dv24p advanced… MAC probably use QuickTime.
2.6- ****** CLICK — > SAVE PRESET — > use any name you like.
2.7- SELECT your new custom preset and double click on it.

3- IMPORT the original file using the option — > IMPORT SELECT SEQUENCE –> Select ONLY the editing sequence…
3.1- now double click the IMPORT sequence.
3.2- click on the timeline, select all your project (ctrl+a) and copy it (ctrl+c)
3.3- double click the NEW sequence
3.4- the new sequence should be EMPTY (no video/audios). Now paste it (ctrl+v)
3.4- DELETE the old sequence you imported (JUST the old imported sequence, keep all the linked files)

4- Save it

It worked for all my files in Premiere Pro CS6 and I also tried on Premiere Pro CC and all opened perfectly…

I hope it helps you !!
Fabio – washingmachinelab.com”

[Andreas Ahston]

Hi Peter

Thank you for your reply.

I’m using Premiere Pro CC on a 2014 macbook pro retina (13) 8 gb Ram. Premiere was unhappy about perian, so i’ve uninstalled that. I’ve got fx factory installed, but i’m not really using it.

I haven’t found any pattern to the crackling. I’t gets worse when I run the heavier sections of a timeline with things like keyframe animations of psd’s (text and icons) and warp stabalization. It did help to reduce the playback quality, so I guess it’s got something to do with computer processing or harddrive speed. But once it begins, it tends to continue even if I go back to working on less complicated timelines or disable effects and animation tracks.

Andreas

[Andreas Ahston]

Hi David

Thank you for your reply. I too read about not being able to change the aparture while in video-mode. I have not had a problem with that. Maybe because I use old as/ais lenses where I change aperture directly on the lense ring. But I can also change the ISO and shutter speed while recording. Maybe the problem have been fixed on the D7100?

What you write pretty much confirms what I thought was the case. I’ve seen some comparisons on youtube where canon clearly beats the D800 on the ISO in low light. I wonder if the D810 has improved since the d800 on iso?

I remember reading somewhere that one of the most important things in dslr video, is how the camera transforms the much bigger chip, to create a HD video image. I’ve had the impression that this is where Canon have outpaced Nikon and become the leading brand in dslr video. Do you know anything about this? While reseraching before I bought the D7100 I got the impression that Nikon have been fixing some real issues with their dslr video, but I’m not clear on what these issues might be or how they have improved?

Thanks