Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Lynne <dev@lynne.ee>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v6 0/1] avformat: add Software Defined Radio support
Date: Mon, 10 Jul 2023 08:57:36 +0200 (CEST)
Message-ID: <NZy_qLq--3-9@lynne.ee> (raw)
In-Reply-To: <20230702224636.GN1093384@pb2>

Jul 3, 2023, 00:46 by michael@niedermayer.cc:

> On Mon, Jul 03, 2023 at 12:03:10AM +0200, Lynne wrote:
>
>> Jul 2, 2023, 23:15 by michael@niedermayer.cc:
>>
>> > On Sun, Jul 02, 2023 at 08:55:40PM +0200, Lynne wrote:
>> >
>> >> Jul 2, 2023, 13:01 by michael@niedermayer.cc:
>> >>
>> >> > On Fri, Jun 30, 2023 at 04:38:46PM +0200, Jean-Baptiste Kempf wrote:
>> >> >
>> >> >> On Fri, 30 Jun 2023, at 16:08, Michael Niedermayer wrote:
>> >> >> > Also as said previously, If there is at least a 2nd developer working
>> >> >> > on this then we could & should move this to a seperate libraray (libavradio)
>> >> >>
>> >> >> Why wait for a 2nd dev?
>> >> >>
>> >> >
>> >> > as libavradio so far has been the only actionable suggestion.
>> >> > ill move the code to that and next revission or the one after that
>> >> > will be in libavradio.
>> >> >
>> >> > thx
>> >> >
>> >>
>> >> Could you move it to another repository which other developers
>> >> have access to, like nv-codec-headers? It'll still be an official library
>> >> of the project, and patches for it should still be sent to this ML,
>> >> but it would keep the main repo from becoming a monorepo.
>> >>
>> >
>> > Yes
>> > https://git.ffmpeg.org/libavradio
>> > gil@git.ffmpeg.org:libavradio
>> >
>> > everyone should have acess, but keys a syced from videolan a while ago, so
>> > if someones is missing, mail me
>> >
>> > PS: i found a DAB library that i think can take raw IQ data and return
>> > AAC frames. With that adding DAB support should be alot more practical
>> > than a full implementation of all layers of DAB
>> >
>>
>> Thanks. I look forward to see what becomes of it.
>> Whilst you're at it, could you also make an empty repo
>> for my streaming protocol/container, with the same access
>> permissions? It should be named "avstream", without "lib",
>> as it contains specifications and a reference library, like nut.
>>
>
> created:
> https://git.ffmpeg.org/avstream
> gil@git.ffmpeg.org:avstream
>
> you have power do do non fast forward pushes if need arrises
> git log mail should go to ffmpeg-cvslog@ffmpeg.org
> emailmaxlines= 10000
>

Thanks
Sadly, the name has too many conflicts, both with us and other projects
Could you rename the repo to avtransport? I've left it empty, so you can just delete + recreate it.
_______________________________________________
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-07-10  6:57 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-28 21:25 Michael Niedermayer
2023-06-28 21:25 ` [FFmpeg-devel] [PATCH v6] " Michael Niedermayer
2023-06-29 15:43 ` [FFmpeg-devel] [PATCH v6 0/1] " Paul B Mahol
2023-06-30 14:08   ` Michael Niedermayer
2023-06-30 14:38     ` Jean-Baptiste Kempf
2023-06-30 17:40       ` Michael Niedermayer
2023-06-30 17:57         ` Paul B Mahol
2023-06-30 18:02         ` Michael Niedermayer
2023-07-01 15:28           ` Rémi Denis-Courmont
2023-07-01 18:56             ` Michael Niedermayer
2023-07-01 19:30               ` Paul B Mahol
2023-07-02  9:40           ` Nicolas George
2023-07-02 10:08             ` Paul B Mahol
2023-07-02 13:47               ` Rémi Denis-Courmont
2023-07-02 16:01                 ` Nicolas George
2023-07-02 18:21                   ` Rémi Denis-Courmont
2023-07-02 11:00       ` Michael Niedermayer
2023-07-02 16:11         ` Nicolas George
2023-07-02 18:55         ` Lynne
2023-07-02 21:14           ` Michael Niedermayer
2023-07-02 22:03             ` Lynne
2023-07-02 22:46               ` Michael Niedermayer
2023-07-10  6:57                 ` Lynne [this message]
2023-07-11 21:09                   ` Michael Niedermayer
2023-06-30 17:00     ` Kieran Kunhya
2023-07-01 15:20       ` Michael Niedermayer
2023-06-30 21:36     ` Martin Storsjö
2023-07-01 14:44       ` Michael Niedermayer
2023-07-01 19:41         ` Martin Storsjö
2023-07-01 19:56           ` Tomas Härdin
2023-07-01 20:06           ` Michael Niedermayer
2023-07-01 20:42             ` Kieran Kunhya
2023-07-01 21:25               ` Michael Niedermayer
2023-07-01 21:32                 ` Kieran Kunhya
2023-07-01 19:08       ` Anton Khirnov
2023-07-01 19:35       ` Michael Niedermayer
2023-07-02  9:58       ` Nicolas George
2023-07-02 10:10         ` Paul B Mahol
2023-07-02 10:43         ` Jean-Baptiste Kempf
2023-07-02 16:07           ` Nicolas George
2023-07-02 18:13             ` Jean-Baptiste Kempf
2023-07-02 18:20               ` Nicolas George
2023-07-02 18:32                 ` Michael Niedermayer
2023-07-02 18:52             ` Lynne
2023-07-02 19:52               ` Nicolas George
2023-07-02 20:29                 ` Lynne
2023-06-30 22:02     ` Tomas Härdin
2023-07-02  9:28       ` Nicolas George

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=NZy_qLq--3-9@lynne.ee \
    --to=dev@lynne.ee \
    --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