New Canon 5D Mark IV camera files - limit on how many will open?

Marco. wrote on 2/19/2019, 1:22 AM

MediaInfo reports "JPEG", VP16 reports "Photo JPEG", VLC player reports "Motion JPEG", Canon itself writes it's Motion JPEG.

Musicvid wrote on 2/19/2019, 3:46 AM

I think it's Motion JPEG, or MJPEG. Initially developed as a medical imaging format with a smaller AVI footprint. Canon seems to have come full circle by elevating a native intraframe compressor. At least we don't have to deal with elusive pyramid-b frames, which are cheap knock-offs of I-frames. What a contrivance:-)

Marco. wrote on 2/19/2019, 4:23 AM

Photo JPEG and Motion JPEG are same compression but Motion JPEG adds translation information for some kind of hardware devices. For software usage both could be considered being the same.

Eagle Six wrote on 2/19/2019, 12:35 PM

To add some fuel to the fire, I get similar results, in around adding the 47th clip of the source media from an Atomos Ninja Flame 1080p 422 10 bit DNxHD

Marco. wrote on 2/19/2019, 12:44 PM

Because it's Quicktime decoded again, I think.

Musicvid wrote on 2/19/2019, 1:25 PM

Question for testers, is the behavior the same when the QuickTime 7 MJPEG Codec is used to create your Source media?

Eagle Six wrote on 2/19/2019, 1:37 PM

Because it's Quicktime decoded again, I think.

Exactly

Eagle Six wrote on 2/19/2019, 1:56 PM

Question for testers, is the behavior the same when the QuickTime 7 MJPEG Codec is used to create your Source media?

@Musicvid I'n not sure I follow your question. I rendered an MjpegA, which is I think the closest I can get the MJPEG and yes it does the same similar crash/hang failure in around the 43rd clip mark.

Best Regards.....George

Musicvid wrote on 2/19/2019, 2:03 PM

That is significant to me. We need a 64 bit codec, and Apple won't be providing it.

Eagle Six wrote on 2/19/2019, 3:02 PM

The only other NLE I have is Resolve 15.2.3, which doesn't need Quicktime and therefore will load as many as I can throw at it and being a 64 bit loads and handle them pretty quick.

--A wrote on 3/26/2019, 10:31 PM

Hi guys. Issue sitll exists. Can you write to official support too?
I did it 2 months ago but they really don't care about me. And they answears are soriusly... stupid.
They treat that issue or me not seriously enough.

What about you to write to support too? I wwould not be alone anymore.
https://support2.magix.com/customer/en

https://www.magix.com/us/support/technical-support/

--A wrote on 4/3/2019, 10:02 AM

Guys? :D Is there anything else to to in that thread? Nothing happened :]
Can you ask official support about it like me?

Eagle Six wrote on 4/3/2019, 10:43 AM

@--A I think asking your question once in this thread will encourage others having the same problem to submit a request, but asking again just fills the thread with redundancy. I myself do not have the problem and therefore will not submit the problem, but I'm sure the others using a Canon 5D, having the same problem, and wishing it was addressed by Magix will submit on their own behave.

--A wrote on 4/10/2019, 1:10 PM

Ok, that's why I am asking for.
Can you tell me if you do that?

--A wrote on 4/19/2019, 7:51 PM

Has anyone done this?

Former user wrote on 4/20/2019, 3:48 AM

@--A

Against my better judgement. https://www.vegascreativesoftware.info/us/proxy/85b33662fb5aedd97263/?link=https%3A//support2.magix.com/customer/en/vegas/form

I know i’m going to regret this, especially the meaningless and inane questions and suggestions that will have no bearing on the issue, I've been here before, mostly a waste of time. Nick Hope had already added it to his list of known issues, if he sent in a request then maybe someone might pay attention.

john_dennis wrote on 4/20/2019, 2:33 PM

"I know i’m going to regret this, especially the meaningless and inane questions and suggestions that will have no bearing on the issue..."

All Good Samaritans will be punished until the good works stop.

My number is 43.

Happy Otter Scripts Render Events makes light work of transcoding to

Magic YUV RGB (lossless)

or

Magix Intermediate (respectable quality) in Vegas 15 (Magix ProRes in Vegas 16).

I'd expect Magix to write a decoder for MJPEG in a MOV wrapper when they get a round tuit. In the mean time, I'd be getting my work done. Corporate obstinance on the part of Apple and Canon doesn't necessarily create a crisis for Magix.

Former user wrote on 4/20/2019, 3:59 PM

Indeed John, its not like there aren’t several workarounds that are available, many other suggested here, but “—A” needs the small files, otherwise using the Canon software to import as I suggested on page 1 of this long thread to the OP in 2016 would do, its what i’d do today if needs be.

eikira wrote on 4/21/2019, 7:38 PM

this thread is to long, i had not the motivation to read everything. but try ffdshow x64 if you need MJPEG. cant say if then the codec inside it acts as x64 compatible itself and eliminates the memory issues, but so far maybe worth a try?

--A wrote on 4/24/2019, 10:49 AM

1. We all knot that ffdshow exsists.

2. As someone wrote...
if he sent in a request then maybe someone might pay attention.

The may don't know this issue. If we sent, they will know. This is ONLY A FORUM.
Issua have to be report. We should inform MAgix that there is an issue.
So... Can someone sent that ticket to their support to?

Hm? @peter-pappas?

Former user wrote on 4/24/2019, 12:47 PM

I have got back some basic response from the ticket I opened, not sure if thats it, i’ll wait a while longer to see. So far recommendation is to disable quicktime and do a rewrap if using Cineform, hardly relevant to the Canon codec.

Maybe theres more to come?

This is about it so far ...

”The error message is reporting a crash in FileIOsurrogate, which is a component of VEGAS.
To resolve this issue, navigate to C:\Program Files\VEGAS\Vegas Pro 16.0\FileIO Plug-Ins\qt7plug
Rename the qt7plug.dll to qt7plug.old

Restart Vegas”

“Modern .mp4 and .mov files can be read in Vegas applications without requiring QuickTime.

Without QuickTime installed, these applications can read .mp4 and .mov files that use H.264/AVC video and use AAC or PCM audio. These modern formats are written by many DSLR and action cameras.

QuickTime is required to read .mp4 and .mov containing ProRes, CineForm, and other QuickTime based or installed video codecs. Uninstalling QuickTime for Windows will remove support for these formats in these applications. If using CineForm, we recommend that you re-wrap into AVI format.”

Former user wrote on 4/24/2019, 4:17 PM

Ok i’m pretty sure this is a final response ...

”This is escalated to QA and Development, to be resolved in a future application version or update.”

--A wrote on 4/30/2019, 9:42 PM

I have got back some basic response from the ticket I opened, not sure if thats it, i’ll wait a while longer to see. So far recommendation is to disable quicktime and do a rewrap if using Cineform, hardly relevant to the Canon codec.

I did it a lot of weeks before and that idea is not working.

recommendation is to disable quicktime and do a rewrap if using Cineform

That is not working in my 3 computers.
What about yours? Is that method work? I don't think.

fr0sty wrote on 4/30/2019, 10:22 PM

did you download the update that dropped today?