Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix st30p ffmpeg plugin, #986

Merged

Conversation

tszumski
Copy link
Contributor

@tszumski tszumski commented Sep 30, 2024

"ar" and "ac" are standard FFmpeg parameters and shall not be used as plugin parameters. For this reason the user could not customize commands
Change "ar" to "sample_rate" audio sample rate
Change "ac" to "channels" number of audio channel
change "at" to "ptime" audio packet time

Copy link
Collaborator

@skolelis skolelis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@ko80
Copy link
Contributor

ko80 commented Sep 30, 2024

Consider using the same names for these arguments as in FFmpeg MCM audio plugin:

    { "channels", "number of audio channels", OFFSET(channels), AV_OPT_TYPE_INT, {.i64 = 2}, 1, INT_MAX, DEC },
    { "sample_rate", "audio sample rate", OFFSET(sample_rate), AV_OPT_TYPE_INT, {.i64 = 48000}, 1, INT_MAX, DEC },
    { "ptime", "audio packet time", OFFSET(ptime), AV_OPT_TYPE_STRING, {.str = "1ms"}, .flags = DEC },

https://github.com/OpenVisualCloud/Media-Communications-Mesh/blob/4d87a2d1aa514903f4125b394d033c1a1503d6ce/ffmpeg-plugin/mcm_audio_tx.c#L206

@DawidWesierski4
Copy link
Collaborator

Consider using the same names for these arguments as in FFmpeg MCM audio plugin:

    { "channels", "number of audio channels", OFFSET(channels), AV_OPT_TYPE_INT, {.i64 = 2}, 1, INT_MAX, DEC },
    { "sample_rate", "audio sample rate", OFFSET(sample_rate), AV_OPT_TYPE_INT, {.i64 = 48000}, 1, INT_MAX, DEC },
    { "ptime", "audio packet time", OFFSET(ptime), AV_OPT_TYPE_STRING, {.str = "1ms"}, .flags = DEC },

https://github.com/OpenVisualCloud/Media-Communications-Mesh/blob/4d87a2d1aa514903f4125b394d033c1a1503d6ce/ffmpeg-plugin/mcm_audio_tx.c#L206

i believe this is a great idea
everything going to tiber should be as "cross compatible" as possible

… and should not be used as plugin parameters
@tszumski tszumski force-pushed the tszumski-fix-ffmpeg-audio-plugin branch from b46b9fa to a908a2e Compare October 1, 2024 09:55
Copy link
Contributor

@ko80 ko80 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me

Copy link
Collaborator

@DawidWesierski4 DawidWesierski4 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

HI i belive the -ac argument is also mentioned in
Media-Transport-Library/doc/usdt.md:582
Media-Transport-Library/doc/usdt.md:604
Media-Transport-Library/doc/usdt.md:1522
Media-Transport-Library/doc/usdt.md:1544

@tszumski
Copy link
Contributor Author

tszumski commented Oct 1, 2024

HI i belive the -ac argument is also mentioned in Media-Transport-Library/doc/usdt.md:582 Media-Transport-Library/doc/usdt.md:604 Media-Transport-Library/doc/usdt.md:1522 Media-Transport-Library/doc/usdt.md:1544

In location you mentioned, we do not use MTL ffmpeg plugin, those are just example how to convert audio samples, thus "ar" and "ac" standard FFmpeg parameters shall be used

@DawidWesierski4
Copy link
Collaborator

HI i belive the -ac argument is also mentioned in Media-Transport-Library/doc/usdt.md:582 Media-Transport-Library/doc/usdt.md:604 Media-Transport-Library/doc/usdt.md:1522 Media-Transport-Library/doc/usdt.md:1544

In location you mentioned, we do not use MTL ffmpeg plugin, those are just example how to convert audio samples, thus "ar" and "ac" are standard FFmpeg parameters shall be used

ooooki doki
yuuup makes sense thank you

lgtm then

@PanKaker PanKaker merged commit f33cc15 into OpenVisualCloud:main Oct 1, 2024
28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants