FFAStrans forum

@Kwantumm
"aud" is really the only thing you need to add in x264 custom options in order to add the "access unit delimiter" headers in the h264 bitstream.
@FranceBB just needed to utilize TSMuxer because it added some infos to the ts container that frank did strip off in an earlier step of the workflow by demuxing to a h264 raw stream. Demuxing h264 to raw is something you really want to avoid in general because some vital infos (timing at least) gets lost. Also we noticed that TSMuxer modifies the h264 bitsream by adding some header fields to the h264 bitsream this was somewhat unexpected because a muxer should mux and not modify the video bitsream usually.

Kwantumm wrote: ↑Wed Dec 22, 2021 10:06 am @FranceBB Also, Is it a question of just placing the TSmuxer in the processors folder of FFastrans?

Cheers!

Placing TSMuxer inside the FFAStrans folder won't do anything as by default the processors.a3x of the H.264 node uses FFMpeg as muxer. You would have to call it using a command executor node. I can come up with a command line for you to use within a command executor node but not right now 'cause I'm on my mobile.

emcodem wrote: ↑Wed Dec 22, 2021 4:30 pm @FranceBB just needed to utilize TSMuxer because it added some infos to the ts container that frank did strip off in an earlier step of the workflow by demuxing to a h264 raw stream. Demuxing h264 to raw is something you really want to avoid

Just to clarify, the whole confusion comes from the fact that I didn't use FFMpeg, but simply put I didn't demux any existing stream. Basically I used x264.exe directly to write a raw_video.h264 file which I then muxed to .TS with TSMuxer.
That being said, no one is stopping you from using FFMpeg as a muxer, Wayhu did it and it worked, emcodem also did it and it worked, but personally I like to shy away from it and call encoders and muxers separately (it's an habit I've had since 2006, sue me - as Michael Scott would say eheheheh). That being said, nothing is stopping you from remuxing through TSMuxer inside FFAStrans as well with a command executor. I'll share a mock-up workflow in the coming days anyway. We actually even had the conversation internally about whether we should add TSMuxer as an additional muxer, a bit like we have BBC BMX Transwrap as additional MXF muxer and in the end we voted no to add it, but the option is still open. In the future who knows, if enough people ask for it, I'll bring it on the table of discussion a second time and we'll see.

Anyway now I'm interested in your workflow, @Kwantumm, what do you exactly need to do and why do you need TSMuxer? The more we know the better (maybe in a separate thread).

@FranceBB I'm not sure I need to use TSMuxer yet.
I'm basically trying things out and trying to get a better understanding of how these things work by looking at other peoples workflows etc.
So I've actually had a go with Wahyu's Create_TS and modified it to my needs. In my case it is not needed for playout but for archival purposes.
A little bit of background;
We have this recurring job every month where we have to supply a client with Broadcasted programmes/items they require for their archive. We download these from a third party that logs pretty much everything on Dutch TV as high resolution .TS files and pass them on in a neat package with .MD5 checksums.
Now occasionally for whatever reason something goes wrong and we can't get these files through the usual means. Sometimes we have to make do with a lower quality, lower resolution version which our client still accepts.
But I have taken it upon myself to be able to offer better service by delivering the same kind of high quality files the client is used to. We have good contacts at pretty much all the broadcasters so getting hold of the master .MXF is usually not a problem and allows me to deliver something that approximates the files we would normally get from the third party.
However once converted to .TS in our existing software I have on occasion noticed ugly blocking etc. So FFastrans to the rescue! But I still have some way to go match the specs as noted in Mediainfo and I'm certain I won't get everything right (metadata wise for instance).