Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Justin Wastnage <jw@vloggi.com>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] Looking for FFMPEG developer to help fix pipeline
Date: Thu, 7 Sep 2023 14:50:44 +1000
Message-ID: <CAOkCqXCok9dEDwPV8JzJfPtpbx3j2DzqBxN1z6eTd3OgLXrXyg@mail.gmail.com> (raw)

Hi FFMPEGgers

We have an FFMPEG encoder running various scripts on an AWS server within a
NodeJS environment.

I need to update various scripts (such as adding support for different
codecs) and add various filters.

I also need to add some concatenation logic.

Looking for developers who can help on a project basis within the existing
stack but also potentially explore more permanent refactoring suggestions.

Contact me at the details below with FFMPEG somewhere in the subject line.

Regards

Justin

-- 

Book a meeting with me <https://calendly.com/jwastnage/30min>


Justin Wastnage / Founderjw@vloggi.com / +61 410 219 131 <61410219131>

L2, Fishburners, 11 York StAU-2000 SYDNEY
vloggi.com

[image: Twitter]
<https://twitter.com/intent/tweet?screen_name=vloggi_app&hashtags=vloggi>
 [image:
Facebook] <https://www.facebook.com/vloggiapp/>  [image: Google +]
<http://googleplus.com/cine_souk>  [image: LinkedIn]
<https://www.linkedin.com/company-beta/17919057/>  [image: Instagram]
<https://www.instagram.com/vloggi_app>  [image: Youtube]
<https://www.youtube.com/channel/UCpQ-ZB-2vjfaIzO3y0H_eUA>
_______________________________________________
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:[~2023-09-07  4:51 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=CAOkCqXCok9dEDwPV8JzJfPtpbx3j2DzqBxN1z6eTd3OgLXrXyg@mail.gmail.com \
    --to=jw@vloggi.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