mirror of
https://github.com/CCExtractor/ccextractor.git
synced 2026-02-03 21:23:48 +00:00
'live' raw data problem #275
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @CTayl0r on GitHub (Feb 10, 2017).
I'm trying to send raw CC data (i.e. mcpoodle raw format) into ccextractor from a live source (extracted form a 2110.40 stream). I've found that ccExtractor buffers quite a lot of raw data before processing any, and then when it does process that, it stops once it sees no more data, despite the live (-s) option. This is the case whether I send the data in via UDP, pipe line it in, or use a file. I've tried the non-buffering options, but they seem to make no difference. Is there a way to get 'live' raw data processed?
@CTayl0r commented on GitHub (Feb 16, 2017):
Some more info, and a way to see this.
I made a tcl script to kick out raw CC data slowly to show the issue.
send_raw_cc_slow.txt
Rename it to send_raw_cc_slow.tcl and make it executable.
If one then pipes the output into ccextractor, nothing happens. This is ccextractor buffering up the data before it does anything. You can ctrl-c to give up.
If you add the '-buff' option to my script, it sends lots of null CC characters after each line. After 5 seconds or so, when lots of data is buffered in, ccextractor wakes up and processes the data; but then it stops; despite the '-s' live feature enabled.
Just for reference, if you run this script into a file (ctrl-c after a while), and then 'cat' that into ccextractor (i.e. a non-live scenario) , ccextractor processes the data nicely.
@cfsmp3 commented on GitHub (Feb 22, 2017):
GSoC qualification: 2 points
@cfsmp3 commented on GitHub (Jan 25, 2020):
@CTayl0r Is this still a problem in the current CCExtractor?
@cfsmp3 commented on GitHub (Mar 28, 2021):
Closing as reporting user doesn't reply.