Issue when Importing a .MOV file.

[teacherman]

I'm trying to import a video that I took with my iPhone 12.

When Importing the .MOV file into Protools, both audio and video are scrambled: audio track becomes basically some form of white noise and the video track is smeared/blurry looking.

My PT Session is at 44.1 /16Bit.

Your support, please.

thank you.

[infohou]

Originally Posted by teacherman

I'm trying to import a video that I took with my iPhone 12.

When Importing the .MOV file into Protools, both audio and video are scrambled: audio track becomes basically some form of white noise and the video track is smeared/blurry looking.

My PT Session is at 44.1 /16Bit.

Your support, please.

thank you.

Possibly a codec like HEVC or HEIC that Pro Tools doesn't like. Try opening the file in Invisor or something that will tell you what codec and format the file is in. You may need to convert it.

Remember MOV is a container that is capable of handling several codecs.

Hope that helps,
Robert

[audiolex1]

Originally Posted by teacherman

I'm trying to import a video that I took with my iPhone 12.

When Importing the .MOV file into Protools, both audio and video are scrambled: audio track becomes basically some form of white noise and the video track is smeared/blurry looking.

My PT Session is at 44.1 /16Bit.

Your support, please.

thank you.

Get Shutter Encoder, its free. Convert the movie to a different codec like H264 and PCM audio.

Then import it.

[infohou]

Originally Posted by audiolex1

Get Shutter Encoder, its free. Convert the movie to a different codec like H264 and PCM audio.

Then import it.

Depends on what platform to which he is delivering. H.264 will probably lower the quality. For instance if he is fixing audio then going to Media Composer then he may want to go with DNXHD.

Y'all take care,
Robert

[Eric Lambert]

From an iPhone 12 I'd guess that the format is HEVC and I'm not surprised that PT won't import it directly.

As mentioned above, get Shutter Encoder. You should have that anyway because... well, everyone should have that Swiss Army knife. Made by people who work in the business who constantly update and improve it.

[Eric Lambert]

Originally Posted by infohou

Depends on what platform to which he is delivering. H.264 will probably lower the quality.

It would, but perhaps only slightly. And if it's a situation where you ultimately only want to alter the audio you could strip the original audio out of the original .mov file and replace it with the new audio. Video would remain intact.

[audiolex1]

Originally Posted by infohou

Depends on what platform to which he is delivering. H.264 will probably lower the quality. For instance if he is fixing audio then going to Media Composer then he may want to go with DNXHD.

Y'all take care,
Robert

That is actually not true. H264 doesn't mean lower quality. It means more compressed.
You can have H264 HD video as I get it all the time. It is just very CPU hungry as the decompression takes a lot of power.
And why Apple Silicon put in an H264/5 engine into the chip so it would leave the CPU alone.

I actually backup my shows from the DNX36 to H264 for space saving, roughly 15 gigs, and have re encoded it to DNX36 with no picture loss.

And if going into MC, it will likely convert it anyway.

[Eric Lambert]

Originally Posted by audiolex1

That is actually not true. H264 doesn't mean lower quality. It means more compressed.
You can have H264 HD video as I get it all the time. It is just very CPU hungry as the decompression takes a lot of power.
And why Apple Silicon put in an H264/5 engine into the chip so it would leave the CPU alone.

I actually backup my shows from the DNX36 to H264 for space saving, roughly 15 gigs, and have re encoded it to DNX36 with no picture loss.

And if going into MC, it will likely convert it anyway.

We may be getting off-topic here, but I'm wondering if we'll see wider usage of HEVC (H.265) in place like ProTools. Because PT has had issues with H.264 files in the past (forcing the video engine offline, something that has plagued PT for years), I'm wondering if 265 might someday be an option.

As you suggested, it requires more computational power, and maybe that alone will keep it at a distance from PT for a while.

But I hope not. I've gotten tired of having to convert videos to DNxHD just so the video engine can stay in place. These converted files are WAY larger than they need to be.

[BScout]

As long as the AVE is not native on Macs, it can't take advantage of the coprocessor on M series chips to decode. That is also true for processing HEVC (h265) as much as the other codecs.

[Eric Lambert]

Originally Posted by BScout

As long as the AVE is not native on Macs, it can't take advantage of the coprocessor on M series chips to decode. That is also true for processing HEVC (h265) as much as the other codecs.

That's right, I'd forgotten that the engine isn't native. Odd, considering Avid is largely a video company.