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

Comments

vkmast wrote on 2/16/2019, 11:50 AM

@Former user tested with your files with the workflow you suggested. My experience was similar to yours. 50+ in PM window caused problems and TL did not like more than 40.

Former user wrote on 2/16/2019, 12:18 PM

@diverG 👍

I did a small update to the hyphen batch file.

Former user wrote on 2/16/2019, 12:22 PM

@Former user tested with your files with the workflow you suggested. My experience was similar to yours. 50+ in PM window caused problems and TL did not like more than 40.

Thanks @vkmast At least a consistency of sorts, it doesn’t seem to matter the size of file as these are quite small. Could be installed memory, @Eagle Six has 64gb. Then it could be the phase of the moon either 😏.

Former user wrote on 2/17/2019, 5:58 AM

 

@Former user@Former user @Eagle Six

I loaded 120 instances of your clip in VP14

 

Hi @Musicvid When you say you loaded 120 instances of the clip in VP14, can I take it that you simply loaded the single file ONCE into VP (that was made available by @- -A) and then created multiple copies WITHIN Vegas, thanks,

Musicvid wrote on 2/17/2019, 12:52 PM

JN_

I chose the word "instances" carefully, because I was as unsure as anybody here about the OP's obscure instructions. To be clear, I pasted 120 events of one project media.

That said, I am in the market for a dslr, but its going to be well under 12,000 shekels. (Note to self: avoid MJPEG for time being). Meanwhile, some beta tests wwag provided are still on the list, and I am immersed in yet another round of my dither tests.

https://www.vegascreativesoftware.info/us/forum/this-is-not-about-grading--114804/

Your desire to track this down is commendable, and a welcome contribution. One thing, are "yousguys'" qt32plug.dll in FileIOplugins made by' Magix, and does a subsequent QT install make theirs the default?

Eagle Six wrote on 2/17/2019, 3:14 PM
Your desire to track this down is commendable, and a welcome contribution. One thing, are "yousguys'" qt32plug.dll in FileIOplugins made by' Magix, and does a subsequent QT install make theirs the default?

@Musicvid to be clear on my end, in the FileIO plugins folder I have a qt7plug folder and in that I have the qt7plug.dll and the qt7plug.chm. I can find nothing like a qt32plug in either of my VP15 and VP16 installations. I'm not sure if I had Quicktime installed at the time I installed Vegas Pro 15/16.

@Former user I will next download you sample file and .bat file a follow your instructions and report back. Hopefully, I will come out with the same results you and @vkmast have.

Best Regards....George

System Specs......
Corsair Obsidian Series 450D ATX Mid Tower
Asus X99-A II LGA 2011-v3, Intel X99 SATA 6 Gb/s USB 3.1/3.0 ATX Intel Motherboard
Intel Core i7-6800K 15M Broadwell-E, 6 core 3.4 GHz LGA 2011-v3 (overclocked 20%)
64GB Corsair Vengeance LPX DDR4 3200
Corsair Hydro Series H110i GTX 280mm Extreme Performance Liquid CPU Cooler
MSI Radeon R9 390 DirectX 12 8GB Video Card
Corsair RMx Series RM750X 740W 80 Plus Gold power pack
Samsung 970 EVO NVMe M.2 boot drive
Corsair Neutron XT 2.5 480GB SATA III SSD - video work drive
Western Digitial 1TB 7200 RPM SATA - video work drive
Western Digital Black 6TB 7200 RPM SATA 6Bb/s 128MB Cache 3.5 data drive

Bluray Disc burner drive
2x 1080p monitors
Microsoft Window 10 Pro
DaVinci Resolve Studio 16 pb2
SVP13, MVP15, MVP16, SMSP13, MVMS15, MVMSP15, MVMSP16

Musicvid wrote on 2/17/2019, 3:24 PM

I have a Magix branded qt7plug,dll in that Vp14 folder, but never installed QT on that machine.

[Corrected]

Former user wrote on 2/17/2019, 3:31 PM

If I understand this correctly then the last man standing is @Eagle Six, (unless anyone else wants to try) he's the only one that has loaded beyond 40 clips successfully and he didn’t do that by just make copies / instances within Vegas, if I understand him correctly.

Every other individual, myself, @Musicvid  @vkmast @—A and their machines, a total of about 7 machines so far, using file copies on disk have failed to get much past 40 on the timeline.

Unfortunately the instructions from @- -A left themselves open to interpretation, and so the confusion.

Eagle Six wrote on 2/17/2019, 3:38 PM

Somehow I deleted my own post as @Former user was posting, strange!

Anyway, my results are now the same, @Former user using your sample and work flow in both VP13 and VP16. The crashes were a bit different but the end result was the same. Next I'll go back using --A sample and the unique duplicate I made and retest, as I might have made a mistake in my haste to get out of town yesterday.

System Specs......
Corsair Obsidian Series 450D ATX Mid Tower
Asus X99-A II LGA 2011-v3, Intel X99 SATA 6 Gb/s USB 3.1/3.0 ATX Intel Motherboard
Intel Core i7-6800K 15M Broadwell-E, 6 core 3.4 GHz LGA 2011-v3 (overclocked 20%)
64GB Corsair Vengeance LPX DDR4 3200
Corsair Hydro Series H110i GTX 280mm Extreme Performance Liquid CPU Cooler
MSI Radeon R9 390 DirectX 12 8GB Video Card
Corsair RMx Series RM750X 740W 80 Plus Gold power pack
Samsung 970 EVO NVMe M.2 boot drive
Corsair Neutron XT 2.5 480GB SATA III SSD - video work drive
Western Digitial 1TB 7200 RPM SATA - video work drive
Western Digital Black 6TB 7200 RPM SATA 6Bb/s 128MB Cache 3.5 data drive

Bluray Disc burner drive
2x 1080p monitors
Microsoft Window 10 Pro
DaVinci Resolve Studio 16 pb2
SVP13, MVP15, MVP16, SMSP13, MVMS15, MVMSP15, MVMSP16

Musicvid wrote on 2/17/2019, 3:45 PM

Not exactly. I haven't tried forty discrete files, so I don't know the outcome, nor am I planning on making a purchase that would mandate that kind of deep testing. Eagle Six may have found some Magic Sauce somewhere, so let's keep it as an inquiry; I'm sure Magix would be less embracing if it seemed like a competition. That said, keep up the good work.

vkmast wrote on 2/17/2019, 3:50 PM

The "Everything" search engine found no qt32plug.dll ATM.

Eagle Six wrote on 2/17/2019, 3:59 PM

OK, I think I have figured out how I came up with the two test that appeared to pass. The first was using --A's sample clip putting it in the Project Media bin and then adding it repeatedly to the timeline, so I could get lots, as I thought that is how he wanted us to test.

When I duplicated his clip, I mistakenly copy and pasted his clip 10 at a time. When I started adding them, of course the Explorer sort, which I wasn't paying attention to in my haste, I ended up putting duplicates of the 10 copy and paste, so I got to the 40 mark easily because it was really 10 unique files duplicated each 4 times.

Now when I just went back I got the same of my latest test with @Former user sample clips, resulting in a crash in around the 40 plus mark. I'm not getting a specific crash at a specific point to repeat, but it is very close and nonetheless so similar that I can call it the same.

I'm going to delete by Quicktime and install Vegas Pro 15 and see if I can come of with the qt32 plug that @Musicvid has with his VP14

System Specs......
Corsair Obsidian Series 450D ATX Mid Tower
Asus X99-A II LGA 2011-v3, Intel X99 SATA 6 Gb/s USB 3.1/3.0 ATX Intel Motherboard
Intel Core i7-6800K 15M Broadwell-E, 6 core 3.4 GHz LGA 2011-v3 (overclocked 20%)
64GB Corsair Vengeance LPX DDR4 3200
Corsair Hydro Series H110i GTX 280mm Extreme Performance Liquid CPU Cooler
MSI Radeon R9 390 DirectX 12 8GB Video Card
Corsair RMx Series RM750X 740W 80 Plus Gold power pack
Samsung 970 EVO NVMe M.2 boot drive
Corsair Neutron XT 2.5 480GB SATA III SSD - video work drive
Western Digitial 1TB 7200 RPM SATA - video work drive
Western Digital Black 6TB 7200 RPM SATA 6Bb/s 128MB Cache 3.5 data drive

Bluray Disc burner drive
2x 1080p monitors
Microsoft Window 10 Pro
DaVinci Resolve Studio 16 pb2
SVP13, MVP15, MVP16, SMSP13, MVMS15, MVMSP15, MVMSP16

Eagle Six wrote on 2/17/2019, 4:23 PM

Well, my test to find a qt32plug.ddl has failed. I uninstalled Quicktime. I uninstalled VP15. I reinstalled VP 15 and did not find a qt32plug.dll, but it does have the qt7plug. Then I installed VP14 trial. Again it has qt7plug but no qt 32plug.

Either my trial version of VP14 is different from @Musicvid or, despite my effort of deleting everything Quicktime related from the registry, I have missed something!

So @Former user I think I'm done, and sorry it took so long for me to join all you failures!!!

System Specs......
Corsair Obsidian Series 450D ATX Mid Tower
Asus X99-A II LGA 2011-v3, Intel X99 SATA 6 Gb/s USB 3.1/3.0 ATX Intel Motherboard
Intel Core i7-6800K 15M Broadwell-E, 6 core 3.4 GHz LGA 2011-v3 (overclocked 20%)
64GB Corsair Vengeance LPX DDR4 3200
Corsair Hydro Series H110i GTX 280mm Extreme Performance Liquid CPU Cooler
MSI Radeon R9 390 DirectX 12 8GB Video Card
Corsair RMx Series RM750X 740W 80 Plus Gold power pack
Samsung 970 EVO NVMe M.2 boot drive
Corsair Neutron XT 2.5 480GB SATA III SSD - video work drive
Western Digitial 1TB 7200 RPM SATA - video work drive
Western Digital Black 6TB 7200 RPM SATA 6Bb/s 128MB Cache 3.5 data drive

Bluray Disc burner drive
2x 1080p monitors
Microsoft Window 10 Pro
DaVinci Resolve Studio 16 pb2
SVP13, MVP15, MVP16, SMSP13, MVMS15, MVMSP15, MVMSP16

Musicvid wrote on 2/17/2019, 4:34 PM

I'll leave my overpost up in the interest of clarity (I don't know my outcome). Kindest regards.

Musicvid wrote on 2/17/2019, 4:44 PM

I made a mistake. I have qt7plug.dll on my virgin Vegas 14 install (no QT installed). The "32" was hallucination.

Former user wrote on 2/17/2019, 4:47 PM

@Musicvid “I'm sure Magix would be less embracing if it seemed like a competition.” I honestly fail to see that anywhere in this.

Although we haven’t found a solution for the issue, so far everyone who has tried 40+ actual clips has had the same result now. So if Magix were to look at this thread, and this issue, they might be more inclined to think of addressing it given that its a pretty conclusive result, not an issue that some users have and some don’t have.

@Eagle Six Thanks for the clarification on your testing and the effort you and others have put into this.

Unless someone can find a solution I don’t think theres much more to do. The issue/limitation, is very likely caused by a combination of 32bit QT and this MJpeg type of .mov codec.

Musicvid wrote on 2/17/2019, 4:55 PM

I am thinking ahead to your bug report, as I'm sure you are. Diverse individual outcomes are more or less expected, but 100% consensus is not a requirement. If it is 100%, you have a strong case and I applaud your diligence. Again, knowing which versions of qt7plug.dll are on people's machines may help them, I'm not sure.

I'm a fly on the wall, lacking investment, so you may weigh my thoughts as such. In fact, just ping me when you have found an answer.

Eagle Six wrote on 2/17/2019, 5:41 PM

Following @Musicvid reference to Quicktime versions, I have 7.6, 7.7.6, 7.7.7 and they all have failed per @Former user test work flow.

System Specs......
Corsair Obsidian Series 450D ATX Mid Tower
Asus X99-A II LGA 2011-v3, Intel X99 SATA 6 Gb/s USB 3.1/3.0 ATX Intel Motherboard
Intel Core i7-6800K 15M Broadwell-E, 6 core 3.4 GHz LGA 2011-v3 (overclocked 20%)
64GB Corsair Vengeance LPX DDR4 3200
Corsair Hydro Series H110i GTX 280mm Extreme Performance Liquid CPU Cooler
MSI Radeon R9 390 DirectX 12 8GB Video Card
Corsair RMx Series RM750X 740W 80 Plus Gold power pack
Samsung 970 EVO NVMe M.2 boot drive
Corsair Neutron XT 2.5 480GB SATA III SSD - video work drive
Western Digitial 1TB 7200 RPM SATA - video work drive
Western Digital Black 6TB 7200 RPM SATA 6Bb/s 128MB Cache 3.5 data drive

Bluray Disc burner drive
2x 1080p monitors
Microsoft Window 10 Pro
DaVinci Resolve Studio 16 pb2
SVP13, MVP15, MVP16, SMSP13, MVMS15, MVMSP15, MVMSP16

Former user wrote on 2/17/2019, 5:49 PM

@Musicvid

I’ve no intention of creating a report. The issue was raised by the OP and a few years later by - -A. If they do so then fine. If not fine. My input here was in 2016, to offer a temporary workaround, to clarify, search for a solution amid different user reporting, as were those i’m sure who also input their time and effort. It might still be solved, but I think its less likely without input from Magix.

“Diverese individual outcomes are more or less expected” So far there’s nothing diverse with the result. Everyone who has tested using 40+ actual clips, not “instances” has had the exact same result.

If more users chip in and the results change then of course it becomes diverse.

The lack of diversity in the results has to be a plus in getting a solution someway.

Several bandaids have been suggested by myself and the many contributors to this post to get around the problem, all useful, but none as good as fixing it.

 

”lacking investment” Given you’re prodigious input to all things on this forum i’m genuinely surprised.

If you change your mind you know where the link is to download the single .mov file and batch file.

Just to save you searching ... https://www.vegascreativesoftware.info/us/proxy/8f46b1d2e6ce01304dd7/?link=https%3A//www.dropbox.com/sh/cebefr9ru6a3pfv/AADB9T-zWztN0pPijMLgIFBka%3Fdl%3D0

 

Musicvid wrote on 2/17/2019, 7:48 PM

And I support your efforts unconditionally.

klt wrote on 2/18/2019, 7:44 AM

What if... ???

...convert those things to huffyuv?

ffmpeg -i 001.mov -c:v huffyuv 001.avi

Of coures that requires to install huffyuv codec, but no quictime stuff is required and seems to work flawlessly with Vegas13.

Downside is that file sizes increase a lot, for example that 001.mov example 144MB turned into a 310MB avi.

 

Last changed by klt on 2/18/2019, 7:45 AM, changed a total of 2 times.

Camera: JVC GY-HM600

Desktop: AMD Ryzen 5 1600, 16GB RAM (dual channel 2400 MHz) - Videocard: Radeon R9 380 2GB

Laptop: i5 5200u, 8GB RAM (1600MHz single channel) Videocard: integrated HD5500

Musicvid wrote on 2/18/2019, 10:01 AM

And UT and Magic RGB are also mathematically lossless, putting them closer to AVC source size

klt wrote on 2/18/2019, 10:14 AM

UT and Magic RGB are also mathematically lossless,

Basic concept is to get rid of Quicktime, while staying compatible with Vegas13, using a codec also supported by ffmpeg. So the transcoding can be a batch. Huffyuv was the first that came to my mind, of course any other codec will do which fulfills this requirement 😀

NickHope wrote on 2/19/2019, 1:01 AM

In VP16 build 361 with Quicktime 7.7.9 for Windows I also get a crash when I attempt to load a 42nd uniquely-named copy of --A's sample file to the timeline. FWIW, I can load literally thousands of copies of the same file.

By the way, I read that the codec is Motion JPEG, not Photo JPEG.

I'll add it to the known issues list.