Generic error when importing .mxf files

December 31, 2012, 4:40 am

≫ Next: Re: Not able to add default transition

Hi, this will be my first time editing MXF files from the Canon XF100, but when i import them to Premiere Pro CS6, non updated version u get that the fil can not be imported because of a generic error. I usually work with AVI. I am on a Windows 7 64 bit with a quad core 3.3 and 8 gb ram 1667 mhz. I have not downloaded any software except the Canon XF Utility. Anybody who can help me? And yes i imported the whole File map with SIF files and MXF files, and in the map there are also XML and XMP.

Thank you on beforehand§

↧

Re: Not able to add default transition

December 31, 2012, 5:15 am

≫ Next: Re: Premiere Pro / Media Encoder crash during encoding

≪ Previous: Generic error when importing .mxf files

Works perfectly.........

Thanks everone.........

Cabin

↧

Re: Premiere Pro / Media Encoder crash during encoding

December 31, 2012, 5:53 am

≫ Next: Re: Premiere Pro / Media Encoder crash during encoding

≪ Previous: Re: Not able to add default transition

Hi Axel,

Thanks for your suggestions, I just tried cleaning out the media cache and also rendered out a wav file of the audio and placed it in the timeline and deleted the mp3 version.. Tried once again to encode an mpeg2-dvd file.

1st attempt encoding through Media Encoder, pal widescreen with variable bit rate set to 6, 7 and 8 = everything froze, had to restart via button.

2nd attempt encoding through Media Encoder = this time tried video only same settings just no audio = same error (Adobe Media Encoder cs6.0 has stopped working...)

3rd attempt encoding through Premiere Pro, same settings with audio = same error message.

4th attempt encoding through Media Encoder, pal wide preset as standard with no change = same error message.

5th attempt encoding through Media Encoder, h264 preset for vimeo, 720p = same error message.

6th attempt encoding through Media Encoder, AVI (Uncompressed) 720 x 480 preset. 1m40s in the dreaded blue screen appeared. "A problem has been detected and windows has been shut down to prevent damage to your computer. A clock interrupt was not received on a secondary processor within the allocated time interval. " Bla bla bla.

In all instances the encoding is absolutely flying, but always ends up crashing.

↧

Re: Premiere Pro / Media Encoder crash during encoding

December 31, 2012, 6:04 am

≫ Next: Re: Premiere Pro / Media Encoder crash during encoding

≪ Previous: Re: Premiere Pro / Media Encoder crash during encoding

I find when I am encoding the cpu is running flat out, could your problems be down to overheating?

↧

Re: Premiere Pro / Media Encoder crash during encoding

December 31, 2012, 6:04 am

≫ Next: Re: CS6 has problems with Cannon .mxf files that CS5 plays fine

≪ Previous: Re: Premiere Pro / Media Encoder crash during encoding

sostojic21 wrote:

I am using the mercury playback engine with a Gefore gtx 680 (2gb).

You're going to hate this, but try it with the MPE turned off (Project...Project Settings...General, then for Video Rendering and Playback, select software only). I've got an older NVIDIA GTX 285M, and it works for everything except encoding. The only way I can complete an encode (using AME) is to turn off use of the MPE (in PPro). This triples my estimated encode time, but it's the only way I've got to run to completion right now.

Might not be your problem, but it's an easy thing to check, yes? If you do this, don't forget to turn MPE back on after you complete encoding!

↧

Re: CS6 has problems with Cannon .mxf files that CS5 plays fine

December 31, 2012, 6:16 am

≫ Next: Re: Generic error when importing .mxf files

≪ Previous: Re: Premiere Pro / Media Encoder crash during encoding

Hi GodsMaker

What is your workflow?

I always copy the whole topfolder of my memory card to my media drive. I then point to that folder inside premiere pro and import from there.

Can you not get any footage in at all?

Ulf

↧

Re: Generic error when importing .mxf files

December 31, 2012, 6:31 am

≫ Next: Re: Generic error when importing .mxf files

≪ Previous: Re: CS6 has problems with Cannon .mxf files that CS5 plays fine

How do you import the footage?

Ulf

↧

Re: Generic error when importing .mxf files

December 31, 2012, 6:34 am

≫ Next: Re: CS6 has problems with Cannon .mxf files that CS5 plays fine

≪ Previous: Re: Generic error when importing .mxf files

Do you use the media browser to point tothe folder winth the footage?

↧

Re: CS6 has problems with Cannon .mxf files that CS5 plays fine

December 31, 2012, 6:58 am

≫ Next: Re: Is the Quadro K5000 gpu not supported?

≪ Previous: Re: Generic error when importing .mxf files

I have seen these glitches also on the video but not on spanned clips (don't have any)

Even saw part of the audio gone.

Exported the mxf files to one folder with the XF utility.

Relinked the files and problem seems to have gone.

↧

Re: Is the Quadro K5000 gpu not supported?

December 31, 2012, 7:05 am

≫ Next: Re: Premiere pro CS6.0.3 keeps crashing when exporting to H.264

≪ Previous: Re: CS6 has problems with Cannon .mxf files that CS5 plays fine

Thanks for sending this info John and Jim.... I am encouraged... and will attempt to see if this works today... I have very little knowledge moving around in DOS land.

↧

Re: Premiere pro CS6.0.3 keeps crashing when exporting to H.264

December 31, 2012, 7:36 am

≫ Next: Re: Premiere Pro / Media Encoder crash during encoding

≪ Previous: Re: Is the Quadro K5000 gpu not supported?

I solved what might be a similar problem last evening by lowering the speed of my i7-3055K (nominal 3.9GHz) to 4.2GHz from 4.5GHz.

My symptoms were similar: new PC build (10 days old); crashing or blue screens about 1 minute into a 3 minute Premiere export or AME render, Win7 Pro. The system had previously been very stable. At first I suspected an H264 codec problem or an iTunes/Quicktime incompatibility but when an AVI render using the NTSC DV Widescreen preset crashed it broadened my search for solutions. Mercury GPU render on/off did not fix the crash problem.

The render last evening was probably the first time that my new CPU was seriously stressed. Lowering the CPU speed was the quick solution. Overclocking sites/forums probably have tips on stress tests, memory tests, voltage tweaking, etc but as long as the system is stable I'll probably be satisified with the slower CPU solution.

The CPU cooling is the Intel stock fan. 32GB of Corsair memory is running at its rated PC1600. CPU and memory voltages are the defaults, i.e., no tweaking. Intel DZ77RE-75K motherboard. EVGA GTX680 FTW+ 4GB at its defaults, i.e., no overclocking/tweaking. 1000 watt power supply , which is probably overkill but it's what I had lying around (I have an almost identical setup (GTX460 rather than GTX680) which runs fine at 4.2GHz with a 700-watt PSU -- but I've never stressed that 2nd PC with an Premiere/AE/AME render).

↧

Re: Premiere Pro / Media Encoder crash during encoding

December 31, 2012, 7:58 am

≫ Next: "Burning in" subtitles from plain text?

≪ Previous: Re: Premiere pro CS6.0.3 keeps crashing when exporting to H.264

sostojic21 wrote:

...
- my case is an Antec 902, with no additional fans. It does sound like it's working harder during encoding, not sure if a heat issue could be causing the software to error?
...

Hi,

I've read your post intensive again and found this point. As Richard has written it could be an overheating problem.

A few days ago I have added two additional fans in my case. Today I have encoding a video clip an the cpu fan sounds normal. Before I have added the fans it was very loud.

Try to open your case and blow up cold air with a ventilator to the mainboard.

Regards from Germany and a happy new year.

Axel

↧

"Burning in" subtitles from plain text?

December 31, 2012, 8:54 am

≫ Next: Re: Premiere pro CS6.0.3 keeps crashing when exporting to H.264

≪ Previous: Re: Premiere Pro / Media Encoder crash during encoding

I have subtitles in SRT format to go along with a video. For purposes of post production, I'd like to burn them onto the image while we work on the final product.

Is there a way to do this in Premiere Pro? The SRT file has the exact time code in/on point with the text, so I just need a way to bring that onto the image. I'm thinking maybe I will have to convert it to another format that Bridge/Story can use, which is fine, but I'm not sure how to get the text from the file as data in Premiere Pro (or After Effects) I can use to create what amounts to PGS/burned in subtitles without LOTS of manual labor I'd just assume not do.

Any ideas would be appreciated. Thanks!

↧

Re: Premiere pro CS6.0.3 keeps crashing when exporting to H.264

December 31, 2012, 9:20 am

≫ Next: Re: Premiere pro CS6.0.3 keeps crashing when exporting to H.264

≪ Previous: "Burning in" subtitles from plain text?

Thanks everyone for the quick responses, your advice is most appreciated.

Ed_Elliott, good advice on the overcloaking idea. It didn't even occur to me. Good news is that it worked. Not sure why but it gives me something else to research. I ran several of the projects that previously failed and they all worked in both Adobe Premiere and AME. I was clocking at 3.7 and normal is 3.4. I lowered it to 3.2 and it worked so I will now try to set it up at normal.

I know this is not the right forum for this but any ideas on why overclocking would affect this?

Thanks again Jon, Jim, and Ed.

Craig

↧

Re: Premiere pro CS6.0.3 keeps crashing when exporting to H.264

December 31, 2012, 9:29 am

≫ Next: Re: "Burning in" subtitles from plain text?

≪ Previous: Re: Premiere pro CS6.0.3 keeps crashing when exporting to H.264

>any ideas on why overclocking would affect this?

Heat... an overheating CPU will cause problems, up to and including a computer that just stops when a sensor in the CPU tells the power supply to shut down

You need a REALLY good CPU cooler to overclock, as well as LOTS of case fans to push room air into the case and out the back

This is NOT with an overclocked system, but the i7 3770 computer I built for my wife in November has 2 optional case fans (front & side) and her temps are CPU 84F & Drives 77F & ATI card 91F and that is with using a stock Intel CPU cooler

Encoding makes the CPU run hotter anyway, and overclocking just adds to that

↧

Re: "Burning in" subtitles from plain text?

December 31, 2012, 9:33 am

≫ Next: Re: Pixelated Transitions

≪ Previous: Re: Premiere pro CS6.0.3 keeps crashing when exporting to H.264

The only way I know of to do this is to create titles and add them.

It's a LOT of work.

↧

Re: Pixelated Transitions

December 31, 2012, 9:37 am

≫ Next: Re: Premiere Pro / Media Encoder crash during encoding

≪ Previous: Re: "Burning in" subtitles from plain text?

You don't need to check max bit depth, although it shouldn't hurt. I would not use the QT container, just use the H.264 format, which also has Vimeo presets.

You might try 2 pass encoding if you haven't. Also, be sure to check the resulting video in different players(QT, VLC, Vimeo) and on different systems.

5000 kbps is pretty low for 720, but yes it is Vimeo's requierement.Sometimes I hedge a little bit and boost the Mbps to 8 or so before sending to vimeo. I don't know if this helps or hurts. They seems to recode everything anyway.

↧