Comments

mark2929 wrote on 7/9/2014, 4:01 PM
OldSmoke

If your saying Quicktime prores has some sort of limitation, can you be more specific?
OldSmoke wrote on 7/9/2014, 4:19 PM
You can search this forum for "Quicktime" and you will find some interesting topics. Here is something to read http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=897720
I don't have any ProRes files to try with but I assume it will be same issue.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

mark2929 wrote on 7/9/2014, 4:47 PM
Yep. There's my problem too.

So ts quicktime that's the culprit! But does QT do this in other NLE's to I wonder,
Former user wrote on 7/9/2014, 6:01 PM
Most NLEs, especially Mac Based (of course) are QT based. Only a few, like Vegas are AVI based.

I said most, maybe not most, but many of the big ones, Avid, FCP even Resolve were designed around QT.
rmack350 wrote on 7/9/2014, 6:37 PM
Really though an NLE should be able to handle this, or do other NLE's have these same boundaries?

Evidently Final Cut (pre X) did. It's a 32-bit application, though, and I wouldn't say that FCP had the exact same sorts of bounds.

It just seems prudent with any NLE that you should give yourself escape routes. Keeping your project broken down into subprojects (sequences, nested veg files, however you want to think of it) seems like a good idea. Along with frequent backups of the veg files, and some agreed upon version naming of the veg files.

Rob
rmack350 wrote on 7/9/2014, 6:57 PM
The OP of the thread that OldSmoke linked to had a few other conversations going. You might read those to gather more opinions. Quicktime on Windows is 32-bit so there's a memory limit. Also, Vegas loads Quicktime through its FileIOSurrogate component, and evidently it's not doing as good a job as whatever Adobe is doing.

Your mileage may vary depending on the quicktime codec involved, but this is the sort of pre-postproduction research you should be doing to make sure you don't find you've painted yourself into a corner a year or two from now. Personally, I think Vegas and Quicktime are good for a few dates but I wouldn't make a long term commitment without some clear pre-nuptial arrangements.