Re: [FFmpeg-user] Forced upmixing scheme with no way to disable

2022-06-23 Thread Jeremy F
desired. I should be able to override that filter but retain a 5.1 channel layout designation. On Thu, Jun 23, 2022 at 5:22 PM Paul B Mahol wrote: > On Thu, Jun 23, 2022 at 10:30 PM Jeremy F wrote: > > > Unfortunately due to platform limitations, AAC is the only > > mutli-c

Re: [FFmpeg-user] Forced upmixing scheme with no way to disable

2022-06-23 Thread Jeremy F
Jun 23, 2022 at 8:43 PM Jeremy F wrote: > > > That's what I thought! However, here are some commands showing this. I > set > > the lowpass to be 10khz on channel4 just to prevent any confusion (it > > should clearly _not_ sound like any kind of real low pass filter). With

Re: [FFmpeg-user] Forced upmixing scheme with no way to disable

2022-06-23 Thread Jeremy F
ass filtered version of the audio, despite me never specifying that. On Thu, Jun 23, 2022 at 1:48 PM Paul B Mahol wrote: > On Thu, Jun 23, 2022 at 7:09 PM Jeremy F wrote: > > > A more succinct way of putting it: if I channelsplit (or any other type > of > > upmixing as far as I'm

Re: [FFmpeg-user] Forced upmixing scheme with no way to disable

2022-06-23 Thread Jeremy F
6:45 PM Jeremy F wrote: > > > Hi I'm probably using ffmpeg in an edge-case way, but I simply want to > take > > 2 channels/stereo, and end up with 6 channels of audio, where I can > > apply/modify/filter each channel as I please. And I figured out the > ffmpeg >

[FFmpeg-user] Forced upmixing scheme with no way to disable

2022-06-23 Thread Jeremy F
0dcaa4daa2848670a6530c6ba26a/libavfilter/af_surround.c So, if possible, how can I disabled the upmixing scheme? Thanks! -- Sincerely, Jeremy ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, vis

Re: [FFmpeg-user] crop values are incorrect and seemingly random

2018-08-16 Thread Jeremy
620x248 is what windows 10 says the video dimensions are.  When I roll over the file it says "620x248" and also if I right click on the file in windows and go to properties it says video frame width 620 frame height 248 On 8/16/2018 1:45 PM, Gyan Doshi wrote: On 16-08-2018 11:06 PM,

Re: [FFmpeg-user] crop values are incorrect and seemingly random

2018-08-16 Thread Jeremy
I just checked its meta data with adobe media encoder and it has the correct dimensions according to adobe media encoder.  It seems the problem is actually a bug in windows, not a bug in ffmpeg! On 8/16/2018 1:45 PM, Gyan Doshi wrote: On 16-08-2018 11:06 PM, acowbear wrote: Output #0, mp4,

Re: [FFmpeg-user] Any Insight Into Validation Error?

2015-06-13 Thread Jeremy
Thanks for the info, Carl. I'll review your notes. -j On Sat, Jun 13, 2015 at 12:01 AM, Carl Eugen Hoyos ceho...@ag.or.at wrote: Jeremy genericinbox at gmail.com writes: ERROR[mediaValidation.mpeg2.programPack.insufficientBytes] at 889326276289_USQY51571375.mpg: Insufficient number

Re: [FFmpeg-user] Cropdetect Broken since 2.6

2015-05-04 Thread Jeremy
That's great news Carl. Thank you for the fantastic support. -j On Mon, May 4, 2015 at 2:00 PM, Carl Eugen Hoyos ceho...@ag.or.at wrote: Jeremy genericinbox at gmail.com writes: Cropdetect seems to be broken since 2.6. The issue (cropdetect did not work correctly for 8 bit) should

Re: [FFmpeg-user] Cropdetect Broken since 2.6

2015-05-03 Thread Jeremy
Your workaround works, thank you. I'll keep that in mind. For future questions: Please understand that you should (and must) only test current FFmpeg git head, nothing else is relevant here. Understood, will do. On Sun, May 3, 2015 at 4:30 AM, Carl Eugen Hoyos ceho...@ag.or.at wrote: Jeremy

Re: [FFmpeg-user] Cropdetect Broken since 2.6

2015-05-02 Thread Jeremy
Sorry, I misread the original request. The command being used is : ./ffmpeg -i /Users/jeremylk/Dev/Ruby/workspace/video_encoder_app/Breathing_5s.mov -vf cropdetect=24:16:0 dummy.mov On Sat, May 2, 2015 at 3:29 PM, Jeremy genericin...@gmail.com wrote: Sure thing. Below is the output from 2.5.6

Re: [FFmpeg-user] Cropdetect Broken since 2.6

2015-05-02 Thread Jeremy
Sure thing. Below is the output from 2.5.6 (the last working version) followed by the output for the same command / same file using 2.6, when the behavior for cropdetect changed. Notice how the values for the 2.6 output show no crop detected. This is consistent in everything post-2.6. Everything

[FFmpeg-user] Cropdetect Broken since 2.6

2015-05-02 Thread Jeremy
Hi all, Cropdetect seems to be broken since 2.6. I noticed this the other day with a new build for my encoding app, which pulled 2.6.2. Cropdetect no longer worked with 24:16:0 variables. Pushing the threshold variable up to 65 created different values, but they were negative an incorrect. 2.5.6

Re: [FFmpeg-user] -timelimit not working.

2015-01-23 Thread Jeremy Buseman
Is my command placement wrong? Is there something I'm not seeing here? Anything? On Thu, Jan 22, 2015 at 11:01 AM, Jeremy Buseman naviat...@gmail.com wrote: I'm trying to limit the amount of time my stream runs for but adding -timelimit or -t doesn't seem to do anything. Anyone have any

[FFmpeg-user] -timelimit not working.

2015-01-22 Thread Jeremy Buseman
I'm trying to limit the amount of time my stream runs for but adding -timelimit or -t doesn't seem to do anything. Anyone have any suggestions? ffmpeg -timelimit 30 -r 15 -rtsp_transport tcp -i rtsp:// source.com:557/streaming/channels/0 -an -vcodec copy -f flv rtmp:// 127.0.0.1/live/stream

[FFmpeg-user] ts discontinuity indicator

2014-11-17 Thread Jeremy Greene
issue? I see that the default for ffplay is to ignore the pcr, but if the afc discontinuity indicator is set, then the pts and dts should also be allowed a discontinuity. Jeremy ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman

Re: [FFmpeg-user] HLS for Apple TV?

2014-07-29 Thread Jeremy Turner
How are you playing the streams in the Apple TV? Regards, Jeremy On 29 Jul 2014, at 19:01, david reid zathrasor...@gmail.com wrote: On 29 Jul 2014 18:13, Luke Davis l...@newanswertech.com wrote: On Tue, 29 Jul 2014, david reid wrote: On Tue, Jul 29, 2014 at 5:13 PM, Luke