Re: [FFmpeg-user] the trim filter

2024-07-05 Thread Hans Carlson via ffmpeg-user
On Fri, 5 Jul 2024, Mark Filipak wrote: Well, I separated video & audio into separate streams but got the same result: "Media type mismatch between the 'Parsed_split_0' filter output pad 1 (video) and the 'Parsed_atrim_2' filter input pad 0 (audio)" So, the video stream is going right through

Re: [FFmpeg-user] the trim filter

2024-07-05 Thread Mark Filipak
On 05/07/2024 15.41, Mark Filipak wrote: On 05/07/2024 14.34, Jim DeLaHunt wrote: On 2024-07-04 15:50, Mark Filipak wrote: ...Here's the interesting terminal output (slightly beautified): [Parsed_trim_1 @ 00620040]  Media type mismatch between the 'Parsed_trim_1' filter output pad 0 (

Re: [FFmpeg-user] the trim filter

2024-07-05 Thread Mark Filipak
On 04/07/2024 17.11, Paul B Mahol wrote: On Thu, Jul 4, 2024 at 10:44 PM Mark Filipak wrote: On 04/07/2024 14.22, Paul B Mahol wrote: On Thu, Jul 4, 2024 at 8:05 PM Mark Filipak wrote: Is there some secret to the trim filter? --filter_complex "split=2[i5][i6], [i5]trim=start_frame=481

Re: [FFmpeg-user] the trim filter

2024-07-05 Thread Mark Filipak
On 05/07/2024 14.34, Jim DeLaHunt wrote: On 2024-07-04 15:50, Mark Filipak wrote: ...Here's the interesting terminal output (slightly beautified): [Parsed_trim_1 @ 00620040]  Media type mismatch between the 'Parsed_trim_1' filter output pad 0 (video) and the 'Parsed_atrim_2' filter in

Re: [FFmpeg-user] the trim filter

2024-07-05 Thread Paul B Mahol
On Fri, Jul 5, 2024 at 7:29 PM Mark Filipak wrote: > On 05/07/2024 07.54, Paul B Mahol wrote: > > On Fri, Jul 5, 2024 at 2:09 AM Mark Filipak > > wrote: > > > >> On 04/07/2024 17.12, Paul B Mahol wrote: > >>> Its in documentation: asetpts=N/SR/TB, assuming everything starts from > 0, > >>> so ad

Re: [FFmpeg-user] the trim filter

2024-07-05 Thread Jim DeLaHunt
On 2024-07-04 15:50, Mark Filipak wrote: ...Here's the interesting terminal output (slightly beautified): [Parsed_trim_1 @ 00620040]  Media type mismatch between the 'Parsed_trim_1' filter output pad 0 (video) and the 'Parsed_atrim_2' filter input pad 0 (audio) [AVFilterGraph @ 0

Re: [FFmpeg-user] Convert audio to CSV

2024-07-05 Thread Bouke / edit 'B
Pff, copy / paste from a Hex editor would do the trick, and then, a C coder need to fall back to this raises eyebrows. Bouke > On 5 Jul 2024, at 17:29, Danny Mitchell wrote: > > On Sun, 30 Jun 2024 at 15:38, Michael Koch > wrote: >> >> Hi, >> >> is it possible to convert an audio waveform

Re: [FFmpeg-user] Convert audio to CSV

2024-07-05 Thread Danny Mitchell
On Sun, 30 Jun 2024 at 15:38, Michael Koch wrote: > > Hi, > > is it possible to convert an audio waveform to a CSV list? > I want to insert 2048 samples of a waveform into the C source code for a > microcontroller. > > Michael > > ___ > ffmpeg-user maili

Re: [FFmpeg-user] the trim filter

2024-07-05 Thread MacFH - C E Macfarlane - News
As Paul has had over an hour to respond to my PM and has failed to do so, I'll repeat it here ... On 05/07/2024 12:54, Paul B Mahol wrote: On Fri, Jul 5, 2024 at 2:09 AM Mark Filipak wrote: On 04/07/2024 17.12, Paul B Mahol wrote: Its in documentation: asetpts=N/SR/TB, assuming everything s

Re: [FFmpeg-user] the trim filter

2024-07-05 Thread Mark Filipak
On 05/07/2024 07.54, Paul B Mahol wrote: On Fri, Jul 5, 2024 at 2:09 AM Mark Filipak wrote: On 04/07/2024 17.12, Paul B Mahol wrote: Its in documentation: asetpts=N/SR/TB, assuming everything starts from 0, so add it after each atrim. For both video & audio, time_base=1/9 start_

Re: [FFmpeg-user] the trim filter

2024-07-05 Thread Paul B Mahol
On Fri, Jul 5, 2024 at 2:09 AM Mark Filipak wrote: > On 04/07/2024 17.12, Paul B Mahol wrote: > > Its in documentation: asetpts=N/SR/TB, assuming everything starts from 0, > > so add it after each atrim. > > For both video & audio, >time_base=1/9 >start_pts=1048560 > > So, there are '