FFAStrans forum

Hey @Ghtais

Can you share a small example file?

yes for sure
here is my workflow and one test file

@Ghtais
i have 2 different issues:
1) @FranceBB inserted "clear media properties" checkbox into the custom avs script processor and set it to be checked by default, so i get the error "i don't know what m_clip means". Solution: uncheck clear media properties in the custom script processor
2) Then after submitting your file, i get the error unable to initialize quicktime environment, Solution: you'd need to provide the linked mxf file, otherwise i cannot come to the spot where it hangs forever for you

You will find a package with 1 x QTref file and the media associated. The pb is that on my side, the media are stored on a AVID nexis and the QTref pointed on this storage. You probably not be able to open the file until you modify the path directly in the QtRef
Let me know.

https://we.tl/t-QkDgAcm8Vu

OK thanks @Ghtais no worries about the reference stuff thats really easy for me to handle that but what is still problematic for me is that i don't even get a simple mp4 working using ffastrans > 1.4. I tried quicktime players 7.6 and the "latest", it can always open and play the file in quicktime player but no ffmpeg/ffprobe is working with the avisynth plugin.
On one Win10 machine, using your ref files, i came that far that i even get the error in ffastrans that quicktime misses the DNX codecs.
So to make it reproduceable for me, i'd unfortunately need the quicktime player that you use and if possible the avid codec plugin, i hope you work with a copy of this Codec pack that is not available anymore since 10 years, was it called Avid Codec Pack LE?

EDIT:
OK i solved now "unable to initialize quicktime environment Error. Got it working by copying the whole contents of
C:\Program Files (x86)\QuickTime\QTSystem
to
C:\temp\FFAStrans1.2.2.1\Processors\ffmpeg\x86

The reason for that is that the Quicktime dll was not found anywhere even if the Path above was in the PATH. I debugged it and found out that it just does not look for the dll in the QT install path but it does look for it in the same path where ffmpeg is that is why copying all the dlls from QTSystem folder to the folder where ffmpeg is worked.

Now i can continue debugging but i fear i'll still need the quicktime decoder plugins for dnx codecs to reproduce your specific error.

ok, no pb, here is the famous old school AVID pack

https://we.tl/t-3QBedUMwEe

Thanks @Ghtais
So "unfortunately" it works for me after this long journey of getting some mp4 source file working ONCE in ffastrans 1.2.2.1 as described above. Then i installed the avid codec pack from you. After that, i updated the references in the qt file using hex editor from nexis to localhost, created the needed folder structure and share on my pc and made sure your test file plays in QT player with success.
Of course you will not need to reproduce any of the above, its just for info what i did.

Then it just worked in multiple ffastrans versions, 1.3.x and 1.4.0.7 among them. I did not need to apply the mentioned hack from above (copy the qt dlls into ffmpeg folder) after installing avid qt pack.

I needed to change 2 things in the custom avs processor from your DEBUG.json workflow. I double checked that clear media properties in the avs processor is not checked, also i needed to remove , info = 1 from the arguments to QTInput function (with info = 1 it hangs a minute at "reading source media properties then crashes).
I get however only 1 audio working, guess that comes from the audio argument to QTInput function but you know better for sure.

For consitency reasons, i'll attach the workflow exactly as it is working for me, i used manual submit of course to submit the qtref source.

Let me know your results

Hello Emcodem

I must say that I don't really understand what you've done.
I look at your Avisynth script and don't see any differences with mine (I had already tested without the info=1 ).

I copied only this modul and it works very strange.

Anyway thank you for the time you passed on this old school workflow

bye

Hm, i comprared the jsons of our workflows and i see that the "clear_props" field is "missing" in your workflow.
That can explain why it showed the "clear props" checkbox as enabled when i imported your workflow in first place and i had to disable it. But it does not explain your error behaviour at all.
So unfortunately i have no explaination why your wf could lead to the described behaviour but not mine