Problem importing .mov file

M-Cox wrote on 7/23/2020, 11:34 AM

I have just installed MEP 2020 and when I try loading in a MOV I get the error message that the file format cannot be read. I still have MEP 17 Plus installed on the same machine. I can load MOV files into that with no problem, save the project and then open it in MEP 2020 and edit as normal. Why can't I load directly?

Comments

johnebaker wrote on 7/23/2020, 11:47 AM

@M-Cox

Hi and welcome to the forum

MOV file format is a container format not a video format - without knowing what the internal video format (codec) is we would be guessing.

Analyse the clip that will not import with MediaInfo and post the results from the Text view within MediaInfo.

Do you have Quicktime Essentials installed?

John EB
Forum Moderator

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 24H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

M-Cox wrote on 7/23/2020, 12:46 PM

My, that was quick. Here's the info from Mediainfo

General
Complete name                            : D:\cox\reel1\reel1-1-01.mov
Format                                   : MPEG-4
Format profile                           : QuickTime
Codec ID                                 : qt   0000.02 (qt  )
File size                                : 10.9 GiB
Duration                                 : 11 min 14 s
Overall bit rate mode                    : Variable
Overall bit rate                         : 139 Mb/s
Writing application                      : Lavf55.19.100

Video
ID                                       : 1
Format                                   : ProRes
Format version                           : Version 0
Format profile                           : 422 HQ
Codec ID                                 : apch
Duration                                 : 11 min 14 s
Bit rate mode                            : Variable
Bit rate                                 : 139 Mb/s
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Constant
Frame rate                               : 16.000 FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:2
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 4.190
Stream size                              : 10.9 GiB (100%)
Writing library                          : fmpg
Language                                 : English
Matrix coefficients                      : BT.601
 

I have Quicktime 7.7.9 installed. As I said, what I can't understand is why files like the one above load into MEP 17 Plus with no problem on this machine, but not the latest MEP version.

johnebaker wrote on 7/23/2020, 1:14 PM

@M-Cox

Hi

. . . . what I can't understand is why files like the one above load into MEP 17 Plus . . . .

Does the above file load in to MEP 17?

I suspect it will not as from the MediaInfo analysis

Format                                   : ProRes
Format version                           : Version 0
Format profile                           : 422 HQ

Prores 422HQ is not supported by Movie Edit Pro, if this is a codec format you will be using regularly you may want to consider moving up to Video Pro X which does, on my testing, support ProRes 422HQ video - try the trial version first.

Check the MOV files that MEP 17 does import - I suspect they will be either AVC, h.264 or JPEG encoded video.

HTH

John EB

 

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 24H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

M-Cox wrote on 7/23/2020, 1:22 PM

The file details I sent you are for a video that imports into MEP17 no problem. I just checked it again. There is an error message reading: "Unknown error occurred during audio extraction", but that is simply because the video is of a silent film - so no soundtrack at all. In fact, I have many video files of this type and I have been using them with MEP17 without difficulty for about four years.

M-Cox wrote on 7/23/2020, 2:03 PM

Just some additional information. The version I of MEP17 I have is the PlusHD one. Also the MOV file plays perfectly well on Quicktime.

CubeAce wrote on 7/24/2020, 11:53 AM

@M-Cox

Hi.

That seems a very odd frame rate being reported. Is that correct?

Can I ask what device the file comes from? You say the older version of MEP is handling it but it seems like a new format of an existing file type. Most unusual an puzzling. Really high bit rate as well for a 1080p file. Quite impressive.

[Edit] Can I also ask the recording medium? What type of card and write speed is needed please?

Ray.

Last changed by CubeAce on 7/24/2020, 11:56 AM, changed a total of 3 times.

 

Windows 10 Enterprise. Version 22H2 OS build 19045.5737

Direct X 12.1 latest hardware updates for Western Digital hard drives.

Asus ROG STRIX Z390-F Gaming motherboard Rev 1.xx with Supreme FX inboard audio using the S1220A code. Driver No 6.0.8960.1 Bios version 1401

Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU with Intel UHD 630 Graphics .Driver version Graphics Driver 31.0.101.2135 for 7th-10th Gen Intel® with 64GB of 3200MHz Corsair DDR4 ram.

1000 watt EVGA modular power supply.

1 x 250GB Evo 970 NVMe: drive for C: drive backup 1 x 1TB Sabrent NVMe drive for Operating System / Programs only. 1X WD BLACK 1TB internal SATA 7,200rpm hard drives.1 for internal projects, 1 for Library clips/sounds/music/stills./backup of working projects. 1x500GB SSD current project only drive, 2x WD RED 2TB drives for latest footage storage. Total 31TB of 10 external WD drives for backup.

ASUS NVIDIA GeForce RTX 3060 12GB. nVidia Studio driver version 572.60 - 3584xCUDA cores Direct X 12.1. Memory interface 192bit Memory bandwidth 360.05GB/s 12GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x8 Gen3. Two Samsung 27" LED SA350 monitors with 5000000:1 contrast ratios at 60Hz.

Running MMS 2024 Suite v 23.0.1.182 (UDP3) and VPX 14 - v20.0.3.180 (UDP3)

M Audio Axiom AIR Mini MIDI keyboard Ver 5.10.0.3507

VXP 14, MMS 2024 Suite, Vegas Studio 16, Vegas Pro 18, Vegas Pro 21,Cubase 4. CS6, NX Studio, Mixcraft 9 Recording Studio. Mixcraft Pro 10 Studio. CS6 and DXO Photolab 8, OBS Studio.

Audio System 5 x matched bi-wired 150 watt Tannoy Reveal speakers plus one Tannoy 15" 250 watt sub with 5.1 class A amplifier. Tuned to room with Tannoy audio application.

Ram Acoustic Studio speakers amplified by NAD amplifier.

Rogers LS7 speakers run from Cambridge Audio P50 amplifier

Schrodinger's Backup. "The condition of any backup is unknown until a restore is attempted."

M-Cox wrote on 7/24/2020, 1:00 PM

All my ProRes files are of old cine film of various gauges and they were transferred by a commercial company. The frame rate chosen by the company was the lowest usual rate for silent standard 8 mm gauge film, although some of the films had soundtracks and therefore were filmed at a higher frame rate. The details I sent you were for a silent film so 16 fps was quite normal. I don't know why the bit rate is the way it is. I'm sorry, but I don't understand the rest of your questions. What exactly do you mean by recording medium? Is that the original film? If it is then I have answered the question above. As regards the card and write speed, do you mean the graphics card? If so, it is an AMD Radeon RX550, I hope that makes sense. I couldn't see any information about write speed.

I really think this must be a bug in the new program, because once I have created a project in MEP17 with the ProRes file I can then load it into MEP 2020 with no problems and it reads the file flawlessly and allows me to edit and apply effects as usual. I can even delete the ProRes file in the project and then load it in again without any trouble. If I try to load any other ProRes file into it, however, I again get the error message.

 

CubeAce wrote on 7/24/2020, 1:16 PM

@M-Cox

Hi.

That may be useful information to others, hence my questions.

First, we didn't know the origins of the files so the info you gave on your files have nothing to do with the original recording medium and were the result of having them professionally transferred from film into a digital format.

That is information we didn't have before and may help someone else here understand the problem better.

The rest of my questions were centred around thinking they files had come from a digital camera of some sort. So no longer relevant as you have now clarified the situation of the original source of the files.

The high bit rate I referred to was probably the result of the transfer method trying to extract as much detail from the film images as possible.

It would seem from what you have further described that there may be a bug or problem that you have found and would be best dealt with by the Magix technical department than here.

Equally there could be a member here that has had a similar problem and solution that has not looked at the forum post yet but my bet would be to get in touch with Magix through your Magix email account and raise a ticket for a reply.

 

Ray.

 

Windows 10 Enterprise. Version 22H2 OS build 19045.5737

Direct X 12.1 latest hardware updates for Western Digital hard drives.

Asus ROG STRIX Z390-F Gaming motherboard Rev 1.xx with Supreme FX inboard audio using the S1220A code. Driver No 6.0.8960.1 Bios version 1401

Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU with Intel UHD 630 Graphics .Driver version Graphics Driver 31.0.101.2135 for 7th-10th Gen Intel® with 64GB of 3200MHz Corsair DDR4 ram.

1000 watt EVGA modular power supply.

1 x 250GB Evo 970 NVMe: drive for C: drive backup 1 x 1TB Sabrent NVMe drive for Operating System / Programs only. 1X WD BLACK 1TB internal SATA 7,200rpm hard drives.1 for internal projects, 1 for Library clips/sounds/music/stills./backup of working projects. 1x500GB SSD current project only drive, 2x WD RED 2TB drives for latest footage storage. Total 31TB of 10 external WD drives for backup.

ASUS NVIDIA GeForce RTX 3060 12GB. nVidia Studio driver version 572.60 - 3584xCUDA cores Direct X 12.1. Memory interface 192bit Memory bandwidth 360.05GB/s 12GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x8 Gen3. Two Samsung 27" LED SA350 monitors with 5000000:1 contrast ratios at 60Hz.

Running MMS 2024 Suite v 23.0.1.182 (UDP3) and VPX 14 - v20.0.3.180 (UDP3)

M Audio Axiom AIR Mini MIDI keyboard Ver 5.10.0.3507

VXP 14, MMS 2024 Suite, Vegas Studio 16, Vegas Pro 18, Vegas Pro 21,Cubase 4. CS6, NX Studio, Mixcraft 9 Recording Studio. Mixcraft Pro 10 Studio. CS6 and DXO Photolab 8, OBS Studio.

Audio System 5 x matched bi-wired 150 watt Tannoy Reveal speakers plus one Tannoy 15" 250 watt sub with 5.1 class A amplifier. Tuned to room with Tannoy audio application.

Ram Acoustic Studio speakers amplified by NAD amplifier.

Rogers LS7 speakers run from Cambridge Audio P50 amplifier

Schrodinger's Backup. "The condition of any backup is unknown until a restore is attempted."

M-Cox wrote on 7/24/2020, 1:31 PM

Thanks for that. I'm not sure how to "raise a ticket", but I expect I'll find out. I'll wait a few days however just in case someone has had a similar problem and knows how to solve it. It may be that I've missed some important information about the new program - my eyes tend to glaze over when I try to read manuals!

I think you are right about the company trying to extract maximum detail from the images.