FFAStrans forum

Yeah, at least microsoft defender currently detects most programs that were created with auto-py-to-exe (python script to standalone executeable). Well, here is the exe and the source code if you dont trust the exe hehe...
https://github.com/emcodem/createaaf

@falitronic, sorry i still need to investigate why there are no links to files in the aaf.. actually that is the very reason why this program exists, to make an aaf that links to the actual files... so it worked with my testfiles but anyway... stay tuned!

OK @falitronic
sorry that was my fault, obviously the createaaf version you used was the latest but i made a mistake when building it, it was using outdated pyaaf2 dependencies which did not create a link to the actual files (Networklocator). Actually it was @nknuelle who added the needed changese to pyaaf2 in order to make this work, please send him a thanks if everything works for you this way.

https://github.com/emcodem/createaaf/releases/tag/0.1

falitronic,

if we deploy any web service , we may automate the ingest

Hmmm there would be a number of people interested in a processor that does the webservice API call for Interplay checkin, unfortunately AVID keeps their Interplay api confidential and does not allow any open source projects using it. I fear this will never change - every interplay customer will need to develop their own interplay checkin tools.

Hello @emcodem, first of all sorry for not answering before. I have tried the new version of createaaf and in the Workspace field if the path of the files appears, however the record in Interplay is not entirely correct. I think you are absolutely right when you say the problem is in the APIs, it seems that Avid does not allow these APIs to be used with tools other than their own. We work with an Avid Unity Isis system that uses a file system that is also Avid's own (AVIDFOS) and I don't know if this also influences it. In any case, we will continue investigating this topic in case we can achieve a positive result and be able to share it through this forum. Thank you very much for your interest, it has really been very helpful to us. a greeting

Hello Falitronic,
I work all day long with AVID products and yes, Avid keeps their API confidential. Of course we already can do a lot of things with FFAStrans but we reach limits when we want to "link" all the softwares. Another example is the DNxHR atom files. FFASTrans can do DNxHD atom files (and it is realllyyy very useful) but it can't do DNxHR....It can be a problem for future when we want UHD files for editing.
Anyway, hope we can move forward anyway
Cheers.
Benjamin

This all might create a false view to the hard facts, so i want to point out what we are able to do and what not here:

1) we want to create mxf and aaf file that are 100% compatible to any AVID system in every thinkable way
2) we cannot create or distribute any software that communicates to Interplay and such API - at least not for free

If anyone is unsure about wether a specific problem's cause is 1) or 2), then please just feel free to ask. It might just take a little more time and investment of resources than you think, but if we can influence it, then we will do so.

falitronic wrote: ↑Sat Oct 10, 2020 9:38 am in the Workspace field if the path of the files appears, however the record in Interplay is not entirely correct.

@falitronic i am really interested in your experiences

Hi

I don"t think AVID want to keep their API confidential. They just want to select third party projects to make sure they will be 100% full compatible with AVID ecosystem. This is the only way to guarantee that every third party products works great in the AVID environment.
I have seen many software editors asking AVID to be validated and If the project is valid AVID give access to all documents en API needed.

Interesting @emcodem. The whole SOAP API and all the .wsdl/.xsd files are available on :80 of the server we run Avid-WS on. But you are saying even if you/me/anyone here figured out how to check in media to Interplay via that API using FFAStrans that would be a violation of a TOS? Sorry for my ignorance on the subject but I have never been involved in commercial software development (only copy paste from stack exchange ).

Yeah if TOS means the same in english than AGB in german you might be right
I dont have any AVID stuff but i did some research in the web and found some interesting discussions in the avid forums about it. Well i guess there is a reason why you don't find any Interplay related open source stuff and at the same time the much(!!) more complex AAF stuff is actually published open source. To be honest i had a look into their Api, it sounded pretty complex but not impossible to generate a general purpose checkin tool.

@Ghtais i guess it has many reasons to keep this stuff protected, additionally to what you say they are controlling the market and ass kissing partners that develop/deliver product suites, then we have kind of a security aspect and so on...

Not to forget, mostly people mix up the creation of compatible media and aaf with the Interplay SDK, so again i need to point out that only the Web Service call for Interplay is protected but the creation of aaf and mxf can be done freely which is what we attemt to do.