From: Jon Maser <jonmaser8@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: [FFmpeg-devel] I dont know asm too well =( but I have a tip: mem+sync and machine learning Date: Tue, 9 Apr 2024 19:43:55 -0700 Message-ID: <CAF=mWJMNM0nMpxJdfCzGU=bu7kN1-Z_995VdyFQ-NixOpv7-RA@mail.gmail.com> (raw) i got this idea from postresql, a very small sql database server i see ffmpeg is broken down into optimized asm libraries for embedding in c etc programs, and i know a few things about asm, ie, hardware registers on cpu+, pump in data into a register, get data out, think it goes down the system bus but i was thinking someone could implement an upload to memory feature when uploading/decoding (kinda like a buffer, maybe a queue? add matrix field of vid, range of tiles, algorithm.. pop when done, algorithm etc , ) video and audio using asm, and implement a sync mechanism (basically a queue of registers from the matrice with data you need to process for stuff like deinterlace or fast moving video ) dont know how av is synced, maybe you can implement a buffer and a stream pointer system? you can do (i surmise) scale_cuda_register_with_image img, offset or upload to memory scale_cuda register_with_image image, offset upscale_cuda_register_with_image image, offset sync you can also use machine learning, which deals with matrices and i think hardware estimation of certain numbers it can also work well in writing/reading files, but now that i think of it c/dma allows you to upload data to the memory and access it until its freed, but you can do stuff like stream data into pointers, maybe that helps, would like it wont give a major preformance gain, but im hoping for the best hopefully that works, ffmpeg is good software! cant wait to hit usenet B) _______________________________________________ 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-10 2:44 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='CAF=mWJMNM0nMpxJdfCzGU=bu7kN1-Z_995VdyFQ-NixOpv7-RA@mail.gmail.com' \ --to=jonmaser8@gmail.com \ --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