This is something I haven't done in a looong time. Does anyone remember how to capture a 29.97 telecine tape with 2:3 pulldown into a 24 or 23.976 Media Composer project while removing the pulldown during the capture? I seem to remember that once a project was setup correctly it was just a matter of marking an in point on an A frame (customarily

I ran a Prores 4444 XQ file through this hack: https://davidtorcivia.com/articles/decoding-proresxq-on-windows I can AMA link in Windows MC 7.0.3. but the playback drops a lot of frames. On a Mac I can AMA link both the original and the hacked file. The original plays back without a problem, the hacked file drops frames same as in Windows. On a Mac

Hmm, Rereading my commnet lines, I don't see how the 0xCD56 could be a delimiter if it changed from project to project. It would probably be more correct to say that the bin ID is 2+2+3 bytes long and that the 0xCD56 is a part of it. I probably used these two bytes because they were unique in my template .avb and made it easy to locate and modify

I'll need to dig up the documentation I've left behind when hacking .avb, if any. I'm trying to remember why I decided not to alter the bin IDs of non-empty bins. It's possible that the ID wasn't clearly delineated. My recollection is that it was located somewhere towards the end of the binary and it shifted place based on the dynamic

I just read my original post. After about a year of randomly generating bin IDs, I'm confident that there is no harm to doing it externally. The projects have been 100% stable on both Mac and Windows. I never heard back from anyone in the engineering, but you know how it's with these old pieces of code. It's possible that no dev has looked

[quote user="Phil Norris"] ... interested in finding out if the bin ID generated on the project level by MC is totally unique - or unique only on a project level. eg. Opening the same bin in the MC project twice generates an error because of the clash of both ID's being registered (probably) in the projects binary *.avp file [/quote] I

DS and Media Composer are two completely different NLEs that have very little in common. They can not share bins. In fact, Avid DS bins are nothing but Windows directories that contain files that represent sequences and clips. Media Composer bins are binary files that contain descriptions of sequences and clips. There is an AAF export option in DS which

Stefano, I have finally fixed the issue with the marker converter. It was not accepting Unicode non-English letters. Unicode in file names and in marker files are now fully supported. As a reminder, the marker converter will take a marker file from Media Composer and generate a clean looking HTML page for client review as well as a subtitle file which

You may want to look into Frame Flex.

Thanks Marianna.