Ethan Gallo
Forum Replies Created
-
oops, typo. AVCHD archives use .MTS files not .MKV, other than that, it did fix the problem for me. The file outputted.
Ethan Gallo-
-
Hey, I recently ran into a similar problem. Apparently there is a glitch when you queue a sequence in media encoder that contains .mkv files (from AVCHD cards or archives) When working with them in premiere initially I got a status bar at the bottom that said “conforming 00000.mkv” which is some sort of pre rendering it does to interpret the footage without having to transcode it. Apparently when you send it out to AME it has to re-conform the footage, but I didn’t notice the status bar in the bottom of the “select a premiere pro sequence” window. After letting that window sit and do its conforming of the clips again, I hit okay to send the sequence into the queue. The sequence is currently outputting normally without errors (it’s really long) and I had been getting the same thing where it would go for a minute or so then come up with an unknown error.
SO long story short, if you’re working with some form of card based footage (not necessarily AVCHD, could be EXCAM or something else too) straight into PrPro without transcoding, try opening the project via Dynamic Link in Media Encoder and once you navigate to the sequence, but BEFORE you add it to the queue, see if there are any progress bars in the bottom right corner of the window that need to do some thinking before you start the encode.
Hope this helps
Ethan Gallo-
-
No problem. Glad to be of help.
Ethan
Ethan Gallo-
-
I never did for after effects. Premiere usually tries to default all of your files to Macintosh HD/users/username/documents/Adobe/Premiere Pro/5.0
Ethan
Ethan Gallo-
-
Hi Ryan,
If I understand correctly you’re having the same issue, only with Premiere Pro CS5? If so, I did find a workaround. After researching the issue i found that a lot of users of Premiere have also been plagued with this problem. I too am primarily a FCP 7 user and capture scratches, render caches etc have always been easy to set up which is why it Premiere was driving me nuts when I was considering switching. What I had to do was start a new project, let Premiere have its way with setting the scratch disks to default (UserName/Documents I think) then once I have the new project open, change the scratch info in preferences and go from there. I cant remember if I saved my old project to XML and then re-imported in the blank project, or if it let me copy sequences. But either way, using this method seemed to set things properly on my system, working off of an external. I was considering switching from FCP to Premiere permanently, but its still a little too buggy for me. I’ll use it when I’m working on a project that has a lot of After Effects elements to take advantage of Adobe Dynamic Link, but other than that I’m sticking with FCP for now. So give the above suggestion a try. It worked for me, it may work for you, but no guarantees. I don’t know if Adobe addressed the issue in CS 5.5 but I know with 5 a lot of users were getting mixed results with workarounds.
Ethan
Ethan Gallo-
-
Hello everyone, not too much activity in this thread for awhile but I recently went through the same problem so I figured I would share my insight. My issues started after we got out i7 imac back from Apple (for a logic board swap) with a fresh install of 10.6. I installed FCS 3 and all of our plugins. We’ve got 2 other machines running FCS 3 with no issues. What happened to me was i would go to open up one particular project on the i7 and FCP would crash about 40% into loading the project. BUT the project opened fine with on the other machines with the same plugins installed and everything. Some other threads recommended Digital Rebellion’s Pro Maintenance Tools (https://www.digitalrebellion.com/blog/posts/pro_maintenance_tools_2.0.5_and_pro_admin_1.5.3_released.html)
I downloaded it (15 day free trial) and opened the “plugin manager” feature. This is a pane that allows you to disable all or one of your plugins manually without uninstalling or trashing them. Basically what I did was systematically disable each 3d party plugin and try opening the FCP file until I came across the culprit. It was Boris FX’s “Contunuum Express” like i said, all of our plugins work beautifully on our other machines, but if I disabled it on the i7 it solved my issue. It was likely a glitch in the install of the plugin.
I understand that many things can cause a SIGBUS crash, and reinstalling the OS and/or FCS will likely solve the issue, but consider checking into this before you spend 1/2 a day reinstalling all of your software.
Cheers,
Ethan Gallo
Ethan Gallo-
-
Just stumbled on this whilst encountering the same issue. Here is the workaround that worked for me. I’m working with DVCPro 720p30. I exported the clip I wanted to denoise with identical settings as the source essentially creating a copy of the selected portion of the master file. Then I brought it back into FCP literally into the same sequence in which resides the clip that was giving me grief before and 0 issues at all. Obviously this wont be very conducive to large volumes of media, but all I needed was to denoise a :45 sec clip. Give it a try and see if it works for y’all.
Ethan Gallo-
-
Like I said, my startup disk is quite on the full side. I never ever use drives like this as working drives. The startup disk is for personal data. I am working off of a FW800 external with 1.5tb of free space. No worries. All of my AE files are on said external, so I think it is AE dumping clips somewhere onto my startup disk by default.
Ethan Gallo-
-
It’s a med/cu stationary shot. The subject shifts his head slightly from time to time but only by an inch or so. Focus never changes. The goal is to remove the background and replace with a matte. This is part of 8 or 9 different people on the same background. The others look b-e-a-utiful, it’s just something about this guy’s jaw and ear that the rotobrush doesnt seem to like. Like I said it’s shot on a light gray/whiteish background. The client wanted it on a pure white one so AE was the logical choice to change this after the fact. There is great separation/ edge definition between the subject and background so it is odd that it is having trouble. On all of the other subjects the background removal/replacement looks seamless, it’s just this one guy, so I was wondering if there were any suggestions to modify settings for the rotobrush tool that might combat this issue.
Ethan Gallo-
-
Will do. Thanks for the advice gents.
Ethan Gallo-