sendto doesn't seem to be sending about ccextractor HOT 5 CLOSED

All right -- I dug in and it looks like sendto is limited in scope and I misunderstood its purpose.

I'll document my findings here for the next person who has questions:

1. sendto requires a confirmation byte (1) to be returned after each message.
2. in the current build (0.67), sendto can only send binary format. You can read more about this format here: https://github.com/CCExtractor/ccextractor/blob/master/docs/BINARY_FILE_FORMAT.TXT

I'm likely going to need to fork ccextractor and modify the sendto functionality to send whatever the -out format is, since I don't want to have to write a binary transcript format parser in nodejs!

I'll leave this issue open for the next day or so in case a core contributor comes around and wants to weigh in. Otherwise I'll be closing this issue since sendto is functioning as coded.

from ccextractor.

This was added as part of last years GSoC by @rkuchumov, where the goal was to be able to capture the raw packets on one instance and decode it on another. I'm not sure what his plans are for this summer, but maybe he can help you out :)

On a sidenote, with a bit of luck it might be added in the near future (@kisselef seems to be working on something similar: okisseloff@bd050f6).

from ccextractor.

Thanks @wforums for the context! That makes complete sense; @kisselef let me know if there is any help I can provide, I don't want to redouble your effort. One thought on the referenced commit is that I wonder if there is a way to make -sendto do it all, rather than having two somewhat similar flags.

The use case I'm looking to support is to be able to specify a host/port pair to receive whatever output is specified (instead of a file or stdout). Maybe this would be something like -netout (or a modification of -o to take in network paths somehow?)

from ccextractor.

-tcp and -sendto use a protocol which goal is to send captions to the repository. This protocol supports a passwords and some additional information. That's why there are confirmation bytes. In the end, it sends data in BIN format which is decoded at the server side to TTXT, SRT, ...

If I understood you correctly, you want to send extracted cc data (in txt, srt) to a server, don't you? why not just: nc -l -p 2048 and ccextractor file -stdout -quiet -out=txt | nc 127.0.0.1 2048 ?

from ccextractor.

@rkuchumov That's exactly what I'll do -- I just got sucked down a rabbit hole and didn't think beyond ccextractor. Thank you!

from ccextractor.