From: ffmpeg@gallery.co.uk To: ffmpeg-devel@ffmpeg.org Subject: [FFmpeg-devel] Modifying mpegts.c to add support for JPEGXS - how to inject video descriptor from PMT into stream Date: Tue, 23 Apr 2024 15:33:02 +0100 Message-ID: <9CB1E73C-E428-4E27-9667-A6E93D93A09D@gallery.co.uk> (raw) Hi Folks I am trying to add decode support for VSF TR-07 (JPEGXS in transport stream), using the intel JPEGXS project for the codec part. The Intel code gets JPEGXS working fine in FFMPEG via mkv or mp4 files but it doesnt implement transport stream support for the new codec so TR07 doesnt work yet JPEGXS TR07 requires a video descriptor block in the PMT entry for the JPEGXS pid. feeding in a known good T07 stream, I have successfully parsed that data in the call parse_stream_identifier_desc() made from pmt_cb() function in mpegts.c, but its unclear how to connect this metadata I have extracted to the internal stream which has been created. Can I inject that newly found video description data into the stream from inside pmt_cb() ? or does this happen somewhere else ? As it stands (since I am not actually doing anything with the parsed descriptor), I still get the error : mpegts @ 0x7fac96104440] Could not find codec parameters for stream 0 (Video: jpegxs, 1 reference frame (2[0][0][0] / 0x0032), none): unspecified sizeConsider increasing the value for the 'analyzeduration' (0) and 'probesize' (5000000) options and as you can see, it doesn't get things like the dimensions when summarising the stream. INPUT FMT: Video: jpegxs, 1 reference frame (2[0][0][0] / 0x0032), none Stream #0:0[0x100], 34, 1/90000: Video: jpegxs, 1 reference frame (2[0][0][0] / 0x0032), none, 60 fps, 60 tbr, 90k tbn Metadata: SRCPID : 256 Could anyone advise how to connect the dots between parsing the PMT and getting that data into the streams parameters ? Thanks !!! _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
reply other threads:[~2024-04-23 14:33 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=9CB1E73C-E428-4E27-9667-A6E93D93A09D@gallery.co.uk \ --to=ffmpeg@gallery.co.uk \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git