[00:13:44 CET] <faLUCE> kepstin: the API example I made two years ago works perfectly with opus... with very few changes [00:15:06 CET] <faLUCE> so, there's something wrong elsewhere in the "big" program. but not in the procedure we described [01:48:14 CET] <retal> kepstin, sorry i was out of office when you wrote. I dont think i have different versions of x264 [01:56:14 CET] <faLUCE> retal: check the id in you x264 version [01:56:50 CET] <retal> faLUCE, how i can check it [01:56:51 CET] <retal> ? [01:57:32 CET] <damdai> why can't mkvtoolnix support wmv as source but ffmpeg CAN? [01:59:13 CET] <faLUCE> retal: execute version.sh inside the x264 dir [01:59:57 CET] <damdai> why doesn't this work? ffmpeg -i R:\9-3000.wmv -vcodec copy -acodec copy -movflags faststart R:\1.mp4 [02:00:25 CET] <retal> faLUCE, #define X264_REV 2970 [02:00:25 CET] <retal> #define X264_REV_DIFF 0 [02:00:25 CET] <retal> #define X264_VERSION " r2970 5493be8" [02:00:25 CET] <retal> #define X264_POINTVER "0.157.2970 5493be8" [02:00:26 CET] <damdai> oops made a mistake [02:01:01 CET] <faLUCE> retal: you can also execute "x264 -h" [02:01:07 CET] <faLUCE> it will show the version [02:02:54 CET] <faLUCE> you also have the version in x264.h : #define X264_BUILD ... [02:05:14 CET] <damdai> why can't mkvtoolnix support wmv as source but ffmpeg CAN? [02:06:53 CET] <retal> faLUCE, x264 -h [02:06:57 CET] <retal> sorry [02:07:15 CET] <faLUCE> retal: look inside x264.h [02:07:21 CET] <retal> X264_BUILD 157 [02:07:44 CET] <faLUCE> retal: now, look inside libx264.c of your ffmpeg source [02:08:08 CET] <faLUCE> find the line with if (x4->params.i_bitdepth > 8) [02:09:32 CET] <faLUCE> and see if it is defined something like "#if X264_BUILD >= 153" [02:13:55 CET] <retal> faLUCE, its strange . but look like i dont have line if (x4->params.i_bitdepth > 8) [02:14:14 CET] <faLUCE> retal are you looking into libx264.c ? [02:14:21 CET] <faLUCE> (of ffmpeg src) [02:14:47 CET] <retal> yes , /ffmpeg/libavcodec/libx264.c [02:15:11 CET] <faLUCE> ok, let me git the latest, I check [02:19:49 CET] <faLUCE> retal: just checked, line 293 [02:20:16 CET] <faLUCE> (latest git version) [02:21:48 CET] <faLUCE> retal: where/how did you download the ffmpeg version? [02:22:04 CET] <retal> faLUCE, empty line :( [02:22:28 CET] <retal> let me reinstall celan system on Monday i try again [02:22:37 CET] <faLUCE> retal: can you write how you downloaded ffmpeg? [02:22:44 CET] <faLUCE> that line MUST be in the source code [02:23:16 CET] <retal> as i remember yetorday it cloned from git [02:23:37 CET] <faLUCE> in which way? [02:23:41 CET] <retal> git clone git://source.ffmpeg.org/ffmpeg.git [02:24:41 CET] <faLUCE> retal: pastebin the content of libx264.c .... this is weird :-) [02:24:49 CET] <retal> :))))) [02:25:38 CET] <faLUCE> that line must be either in the latest git, either in the last stable version. Unless you seriously messed up something [02:26:50 CET] <retal> faLUCE, https://pastebin.com/aFfrfZHd [02:28:58 CET] <retal> one intresting tink, today before this error i was compiled successful couple times with different options [02:29:46 CET] <faLUCE> retal: which configure cmd did you use? [02:29:54 CET] <faLUCE> (the last one) [02:30:23 CET] <retal> --enable-nonfree --enable-nvenc --extra-cflags=-I../cudautils --extra-ldflags=-L../cudautils --enable-gpl --enable-libx264 [02:30:55 CET] <retal> but error i recived with nvresize [02:31:52 CET] <retal> also i remember aplyed patch for session count limitation remove, maybe it broke someting ? [02:34:16 CET] <faLUCE> retal: the only thing you can do is to git again the src. Then check if that line is in libx264.c (and it will be there) [02:34:21 CET] <faLUCE> then configure again [02:35:33 CET] <faLUCE> i will solve your problem but it won't explain why that line disappeared :-) [02:37:10 CET] <faLUCE> I don't know which patch you applied, but: was it for libx264.c ? [02:37:44 CET] <faLUCE> retal: ^ [02:38:06 CET] <retal> faLUCE, thank you so much for your help, now i should go, on Monday i will do clean setup and let you know [02:38:17 CET] <faLUCE> ok [02:38:30 CET] <retal> faLUCE, thank you again ! [02:38:36 CET] <faLUCE> np [02:38:47 CET] <retal> :) [05:19:13 CET] <brimestone> Anyone still awake here? [10:41:00 CET] <rememberYou> hello friends, I would like to only record my microphone and save the record to a file. Any idea how I could achieve that? [10:41:17 CET] <rememberYou> NOTE: the microphone is internal to my laptop [10:51:35 CET] <Foaly> rememberYou, have you tried https://trac.ffmpeg.org/wiki/Capture/Desktop [10:52:28 CET] <rememberYou> well, I don't want to capture my screen, I just would like to record the audio from my microphone [10:52:56 CET] <Foaly> have you read the article? [10:53:20 CET] <rnmhdn> we have so many videos [10:53:46 CET] <rnmhdn> but there is a mistake in the end part of them all [10:54:01 CET] <rnmhdn> so we want to replace the last 3 minutes off all videos with something else. [10:55:12 CET] <rememberYou> Foaly: thank you, it seems that https://trac.ffmpeg.org/wiki/Capture/ALSA answer the question [10:55:45 CET] <rnmhdn> we have already exported some of the videos [10:56:16 CET] <rnmhdn> but some are still in a premier project [10:57:08 CET] <rnmhdn> should I ask my people to fix the videos and export them then [10:57:55 CET] <rnmhdn> or should I ask them to export the wrong videos and later I replace the last 3 minutes of all videos with the correct one without any re encoding(so fast) [11:01:04 CET] <rnmhdn> when I do [11:01:06 CET] <rnmhdn> ffmpeg -i N1.5_6.mp4 -ss 0:0 -to 0:30 -codec copy b.mp4 [11:01:28 CET] <rnmhdn> the first second of the b.mp4 video becomes problematic while the original file was just fine [11:03:59 CET] <rnmhdn> problematic means that when I play it one second is black but the audio is fine(starts automatically in the right way) [11:04:32 CET] <rnmhdn> but the first second of the video is fine [11:04:42 CET] <rnmhdn> not fine! lost! [11:22:33 CET] <iTommix> Hi @ all. I try to record a TV-Stream (RTP) to mp4 in linux for later watching on a AppleTV. But even the Stream is in SD the output quality is bad (artefacts etc.). Here is my log from capture and with wich command i use it. Maybe anyone see a mistake i do: https://pastebin.com/76RQ8NnJ [11:27:52 CET] <iTommix> maybe because of the input is already in h264 i dont have to send the stream trough the libx264 codec? [11:28:14 CET] <iTommix> just copy the video stream? [12:34:06 CET] <phinxy> I'd like to compile ffmpeg with libmp3lame statically lined. --extra-cflags='-static-libmp3lame' did not work because the command is unrecognizeable by gcc. "did you mean -static-libmpx"? [12:38:01 CET] <phinxy> I have a libmp3lame.a (not an shared object). That is why. [13:04:53 CET] <lezsakdomi_> Hi! I have issues using a V4L2 device. The video captured is nice and dandy, but there is a constant ~2s delay. It looks like the delay is caused because of the slow opening of the device. [13:05:25 CET] <lezsakdomi_> Is there an option to wait for opening all inputs and starts muxing them after? [13:14:26 CET] <faLUCE> lezsakdomi_: paste the command [13:19:21 CET] <lezsakdomi_> ffmpeg -f v4l2 -video_size 800x600 -input_format yuyv422 -i /dev/video0 -f pulse -i alsa_input.usb-046d_0825_AF679DA0-02.analog-mono test.mkv [13:19:26 CET] <lezsakdomi_> or just: [13:19:42 CET] <lezsakdomi_> ffplay -f v4l2 -i /dev/video0 [13:20:40 CET] <lezsakdomi_> Cheese and OBS studio can show the camera picture with almost zero latency which I can't reproduce using ffplay :( [13:21:09 CET] <durandal_1707> ffplay is demo [13:21:46 CET] <lezsakdomi_> Yes, but I think 2s is a bit much. [13:22:20 CET] <lezsakdomi_> When recording and then playing back that test.mkv the delay is clearly seen. [13:22:54 CET] <faLUCE> lezsakdomi_: add --fflags nobuffer [13:23:51 CET] <faLUCE> (-fflags nobufer, one "-") [13:24:42 CET] <lezsakdomi_> Whoa, it solved it! [13:24:54 CET] <lezsakdomi_> Thank you really much! [13:24:59 CET] <faLUCE> :-) np [14:39:06 CET] <lezsakdomi_> Interestingly `ffmpeg -i /dev/video0 -f opengl -pix_fmt rgba "Webcam"` removes latency too. [14:40:12 CET] <phinxy> Why is there a wingcommander III .c in ffmpeg? [14:40:15 CET] <lezsakdomi_> While there's still a delay when I try to save multiple streams to a file: https://termbin.com/4g8b [14:41:12 CET] <JEEB> phinxy: because someone thought it would be cool to be able to play those videos in that game [14:41:25 CET] <JEEB> a lot of stuff in FFmpeg is purely due to someone's tastes and likes :D [17:10:06 CET] <astericks> Hi just wondering if I can set the "Writing Applicaiton" metadata to something custom [17:10:16 CET] <astericks> in mp4 or mov [19:18:27 CET] <damdai> does ffmpeg support encoding to wmv ? [19:18:48 CET] <JEEB> on some level yes [19:19:12 CET] <JEEB> there are some wmv encoders (I think at least wmv2 which is I think known was "windows media 8" [19:19:41 CET] <JEEB> what you most likely want is wmv3 aka windows media 9, which then also morphed into vc1 [19:19:56 CET] <JEEB> but I'm not sure how good the encoders are for any of those formats [19:20:03 CET] <JEEB> or if we even have a vc1 encoder [19:24:04 CET] <damdai> i am only interested because to test the difference between wmv2 and wmv3 [19:25:10 CET] <JEEB> not sure how good either of those encoders were compared to whatever other encoders there were from MS etc [19:27:20 CET] <damdai> is it true that vc1 was better than h264 when there was only 1st generation encoders [19:28:27 CET] <JEEB> I'm not sure what you mean with 1st gen [19:28:48 CET] <JEEB> what would be considered first gen because f.ex. x264 development was started around 2003 [19:30:02 CET] <damdai> not sure about vc1 was included in bluray [19:30:10 CET] <damdai> not sure but vc1 was included in bluray [19:30:17 CET] <JEEB> yes, it was. just like mpeg-2 video was [19:30:29 CET] <JEEB> I hvae some 2005 MPEG-2 Video blu-rays :P [19:30:34 CET] <damdai> but now h264 is way better than vc1 [19:30:36 CET] <JEEB> delicious macroblocking [19:30:56 CET] <JEEB> (also enabling mpeg-2 video basically meant you could stick DVD SD stuff as-is to blu-rays) [19:31:10 CET] <damdai> right [19:31:36 CET] <JEEB> I think the reason for various formats to be in blu-ray can be due to various factors like politics between companies etc [19:31:39 CET] <JEEB> and the age of the format [19:31:57 CET] <JEEB> I don't remember when the first blu-ray specs were ratified [19:32:50 CET] <damdai> somebody in x264 told me it was because there weren't any good h264 encoder at the time and vc1 was actually better [19:33:45 CET] <JEEB> I'm not 100% sure about that, but it depends on the age [19:34:00 CET] <JEEB> because from circa 2006 you could say that even x264 already was going better [19:34:33 CET] <JEEB> but if the spec is older than that (it probably is) it might have been a political thing to get HD-DVD mastering places etc on board [19:34:34 CET] <damdai> circa 2006 ? [19:36:52 CET] <damdai> btw, wmv3 is decent but i've seen so many bad videos of wmv2, just horrible [19:40:47 CET] <Hello71> also I'm sure it's partly design-by-committee [19:41:05 CET] <JEEB> also VC-1 was actually standardized in 2006 [19:41:20 CET] <JEEB> of course the format was available as more or less WMV3 since 2003 [19:42:43 CET] <damdai> why does wmv2 sucks so much? wmv2 @ 4500 bps is worse than wmv3 @ 2000 bps [19:43:30 CET] <damdai> sorry kbps [19:43:54 CET] <JEEB> shitty encoders? [19:44:06 CET] <JEEB> I mean, without making a proper comparison we wouldn't know [19:44:17 CET] <JEEB> but you're probably not in posession of the proper encoders etc to do a test [19:44:21 CET] <JEEB> thus there is no answer [19:44:31 CET] <damdai> i am going to test how good ffmpeg's wmv is [19:44:54 CET] <JEEB> probably shit :P [19:45:25 CET] <JEEB> lossy encoders were never the forte of FFmpeg, even if the mpeg4 one could be configured nicely and in some tests beat xvid [19:45:51 CET] <JEEB> they generally are made for "I just need a video in this format because windows media player or something else cannot play my MPEG-4 Part 2 or H.264" [19:47:41 CET] <damdai> i don't understand, shouldn't ffmpeg's x264 exact same as x264.exe ? [19:48:27 CET] <JEEB> libx264 in FFmpeg utilizes the x264 library yes, it's a wrapper around an external library. what I meant are lossy encoders *within* FFmpeg itself [19:49:04 CET] <JEEB> there are some OK ones, but esp. if it's a minor format they probably are not really good :P [19:50:10 CET] <damdai> ffmpeg is so powerful though, did you know that mkvtoolnix doesn't even support wmv as source? [19:50:56 CET] <JEEB> I don't see any reason for it to do so? its focus is on getting raw media into matroska [19:51:12 CET] <JEEB> it has an AVI support, but that sucks as it uses the VFW compatibility mode [19:51:22 CET] <JEEB> which you don't want to use in 99% of all cases [19:57:00 CET] <damdai> pretty much every video encoder before h264 sucks i wonder how youtube survived before h264 existed [20:17:34 CET] <another> h264 is not an encoder but a standard [20:17:54 CET] <another> youtube was using flash video before [20:19:03 CET] <JEEB> vp62 basically :P [20:19:13 CET] <furq> weren't they using flv1 [20:19:48 CET] <JEEB> they probably utilized different things at different times. I do remember them using VP6 at some point since I think flash supported that? [20:19:53 CET] <JEEB> or do I remember completely incorrectly [20:19:59 CET] <furq> you might be right tbh [20:20:07 CET] <furq> i know it was flv1 when they first launched and then h264 as of about 2007 [20:20:40 CET] <furq> but flash tried to deprecate flv1 in favour of vp6 at some point [20:20:49 CET] <furq> so it's totally plausible [20:20:59 CET] <JEEB> > Flash Video FLV files usually contain material encoded with codecs following the Sorenson Spark or VP6 video compression formats. [20:21:05 CET] <damdai> another: pretty much every video format before h264 sucks [20:21:06 CET] <furq> right [20:22:35 CET] <damdai> youtube was using vp6 ? i wonder how good/bad is vp6 [20:22:48 CET] <furq> it's two worse than vp8 [20:23:06 CET] <damdai> wmv9 was best format before h264 but seeking is slow [20:27:24 CET] <damdai> <furq> it's two worse than vp8 , that doesn't tell me much [20:39:59 CET] <TSaari> (JEEB: pm pong, making sure) [20:48:07 CET] <ossifrage> I've been playing with trying to compile a minimal ffmpeg, I'm only using libavformat. If you build with --disable-avcodec --enable-avformat, it doesn't actually build avformat. [21:13:54 CET] <ossifrage> Also, even though I don't have jpeg turned on, I'm picking up a symbol dep for avpriv_mjpeg_bits_dc_chrominance [21:17:45 CET] <faLUCE> ossifrage: because formats are linked to codec contexts [21:18:45 CET] <ossifrage> Yeah, but I'm running with --disable-{encoders,decoders,muxers,demuxers,parsers,..} and only turning on what I need [21:19:29 CET] <ossifrage> faLUCE, and none of them are *jpeg* [21:20:20 CET] <faLUCE> ossifrage: which compiler error do you have? [21:20:33 CET] <ossifrage> undefined reference to `avpriv_mjpeg_bits_dc_chrominance' [21:20:57 CET] <ossifrage> and several other avpriv_mjpeg_bits_* [21:21:41 CET] <faLUCE> ossifrage: paste the error. I don't understand if is it a linker or a compiler error [21:21:49 CET] <ossifrage> link time [21:22:13 CET] <ossifrage> ...../libavformat.so: undefined reference to `avpriv_mjpeg_bits_dc_chrominance' [21:23:02 CET] <faLUCE> are you compiling ffmpeg or a program with libavcodec ? [21:23:47 CET] <ossifrage> a program linking against ffmpeg, ffmpeg itself compiles just fine [21:24:05 CET] <faLUCE> so, a program with libavcodec, right? [21:24:33 CET] <ossifrage> The program only links with .. -lrt -lavutil -lavformat [21:25:37 CET] <ossifrage> (which worked when I had a big ffmpeg, compile, but it picked up a huge pipe of dep libraries) [21:26:31 CET] <faLUCE> but how did you disabled the codec? [21:26:39 CET] <faLUCE> but how did you disabled the codecS? [21:27:22 CET] <faLUCE> I mean: you can disable separate codecs, but I don't think you can disable the codec library [21:27:26 CET] <ossifrage> You can't do --disable-avcodec, but you can do --disable-encoders --disable-encoders [21:27:42 CET] <ossifrage> (err --disable-decoders) [21:27:47 CET] <JEEB> also probably parsers? [21:27:51 CET] <JEEB> unless you need those :P [21:28:33 CET] <ossifrage> It doesn't help that I'm cross compiling this with buildroot which complicate things [21:28:59 CET] <ossifrage> Yeah, the goal is to get a starting point that is the minimal set to do h264/hevc -> mp4 muxing [21:29:00 CET] <faLUCE> ossifrage: then, you just have to add lavcodec to the linker [21:29:13 CET] <JEEB> just means that you want to first optimize it outside of that natively :P atl east that IMHO would be a faster way of iterating [21:29:33 CET] <JEEB> anyways, you can start figuring out what exactly brings what in [21:29:44 CET] <faLUCE> ossifrage: the linker shows that you did not link avcodec. [21:30:07 CET] <ossifrage> JEEB, I did do that but just to compile ffmpeg, but I didn't bother testing the library because what I'm building won't build on the host [21:30:24 CET] <JEEB> the symbol you mentioned is in lavc's jpegtables [21:30:31 CET] <JEEB> and actually the table is being utilized from libavformat! [21:30:38 CET] <JEEB> rtpdec_jpeg [21:30:41 CET] <JEEB> needs that for some reason [21:31:00 CET] <ossifrage> faLUCE, previous when the ffmpeg had a big pile of stuff in it I did *not* need to link against -llibavcodec, that dep got picked up by the linker [21:31:21 CET] <ossifrage> I do have --enable-muxer=rtp [21:31:32 CET] <JEEB> configure:rtpdec_select="asf_demuxer jpegtables mov_demuxer mpegts_demuxer rm_demuxer rtp_protocol srtp" [21:32:01 CET] <JEEB> the RTP "demuxer" needs that stuff [21:32:33 CET] <JEEB> also rtpenc *also* uses jpegtables.h... [21:32:56 CET] <JEEB> ok, so I just didn't notice it with the first git grep [21:33:04 CET] <ossifrage> JEEB what turns on jpegtables? [21:33:06 CET] <JEEB> both the RTP JPEG demuxer and muxer in libavformat [21:33:14 CET] <JEEB> include and utilize that symbol that you noted [21:33:20 CET] <faLUCE> ossifrage: then, in the previous situation, you did not link against libavcodec but you did not use --enable-muxer=rtp, right? [21:33:39 CET] <JEEB> ossifrage: but it seems like rtpenc doesn't have a dependency on jpegtables [21:33:42 CET] <JEEB> that might be a bug [21:34:01 CET] <JEEB> if you look at configure and grep "jpegtables" which is what provides that symbol [21:34:04 CET] <ossifrage> The previous working build did not have any --disable-{codec,muxers,...} [21:34:14 CET] <ossifrage> It was just the whole thing [21:34:25 CET] <faLUCE> ossifrage: ok, but it did not have --enable-muxer=rtp, right? [21:34:25 CET] <JEEB> yes, thus something else brought the dependency in most likely [21:34:34 CET] <JEEB> like rtpdec [21:34:46 CET] <ossifrage> Yup no --enable-{muxer,demuxer,...} lines [21:35:03 CET] <faLUCE> ossifrage: then it's the --enable-muxer=rtp thant wants libavcodec [21:35:27 CET] <JEEB> ossifrage: anyways so what your actual issue is? "extraneous" symbol requirements or something else? does the pkg-config file get generated with correct dependencies? [21:35:51 CET] <JEEB> (the RTP muxer does not that symbol you mentioned so it's not extraneous as long as you have the RTP JPEG muxer enabled) [21:36:05 CET] <JEEB> *RTP muxer needs that symbol [21:36:13 CET] <JEEB> multitasking and English are not good :P [21:36:16 CET] <ossifrage> I thought the extra deps came from the .so [21:36:39 CET] <JEEB> .so will have deps too [21:36:42 CET] <JEEB> for the runtime linker [21:36:50 CET] <JEEB> (as opposed to the build-time linker) [21:37:27 CET] <JEEB> and yes, my question would also be regarding if there's a missing dep if you disable RTP "decoder" in libavformat since the RTP "encoder" uses the jpegtables thing as well but configure doesn't seem to have it listed [21:37:56 CET] <faLUCE> ossifrage: so, consider to use another rtp library [21:38:14 CET] <JEEB> wat [21:39:01 CET] <faLUCE> I mean: if you can't modify the code, you could use another rtp library [21:39:05 CET] <ossifrage> I'm not using rtp right now, I just added it for future use. [21:39:18 CET] <faLUCE> so you won't have linker errors [21:39:58 CET] <ossifrage> Patching is just fine and very common for cross compile builds like this [21:40:31 CET] <ossifrage> I'm trying without the rtp stuff [21:41:17 CET] Action: JEEB sighs [21:41:51 CET] <ossifrage> My point for bring this up is that the ./configure hell seems to be missing some deps [21:42:00 CET] <JEEB> yes, which is what I tried to confirm [21:42:11 CET] <JEEB> but I didn't get a reply [21:42:12 CET] <JEEB> :V [21:42:32 CET] <JEEB> because it seemed like mjpegtables was being utilized from the RTP "encoder", but only marked as a dependency for the RTP "decoder" [21:42:55 CET] <ossifrage> I had rtp enabled for the muxers [21:42:56 CET] <JEEB> thus it was a valid dependency from libavcodec, even if by the symbol name you might have thought of it as an unnecessary thing [21:43:22 CET] <JEEB> yes I know, that's the goddamn reason why I am trying to confirm what your goddamn issue was [21:43:38 CET] <JEEB> if there was a dependency on another lib's symbol which wasn't getting done through the dynamic linker or whatever [21:44:15 CET] <JEEB> you can also check if it gets fixed by enabling the RTP demuxer [21:44:24 CET] <JEEB> because that one has the dependency marked [21:44:26 CET] <JEEB> if it does, it's a bug [21:44:27 CET] <JEEB> :P [21:45:14 CET] <faLUCE> JEEB: but rtp jpeg needs that table, so why do you think it could be a bug? [21:45:52 CET] <ossifrage> Removing the --enable-muxer=rtp fixed the problem [21:46:03 CET] <faLUCE> ossifrage: as I said before ;-) [21:46:08 CET] <ossifrage> I had --disable-demuxers set [21:46:17 CET] <JEEB> faLUCE: THE LACK OF DEPDENDENCY [21:46:23 CET] <JEEB> vittu saatana read what I said [21:46:24 CET] <JEEB> please [21:46:35 CET] <JEEB> if it uses a symbol and doesn't depend on what provides it [21:46:59 CET] <JEEB> and of course disabling the rtp muxer fixes it as well, but I was more interested in if it gets fixed by enabling the demuxer [21:47:06 CET] <JEEB> because then marking the dependency fixes it [21:47:07 CET] <JEEB> vittusaatana [21:47:44 CET] <faLUCE> JEEB: afaik mjpeg tables are needed both by the demuxer and the muxer [21:47:50 CET] <JEEB> I KNOW [21:47:52 CET] <JEEB> I JUST FUCKING SAID THAT [21:48:04 CET] <faLUCE> JEEB: be calm [21:48:18 CET] <ossifrage> JEEB, sorry, but this crap compiles pretty slowly, I had already started the build without the rtp stuff [21:48:32 CET] <ossifrage> I'll go back and try again with the muxer and demuxer [21:48:47 CET] <JEEB> faLUCE: I knew that in theory enabling the dependency should fix it, but I was still fucking not sure what was ossifrage's actual issue [21:48:55 CET] <JEEB> so if adding a component that rightly has that dependency [21:49:03 CET] <JEEB> fixes th eissue [21:49:11 CET] <JEEB> then adding that dependency to rtpenc would fix it [21:49:20 CET] <JEEB> I was just fucking trying to get that fucking confirmation for fuck's sake [21:49:46 CET] Action: JEEB goes away to calm down for a bit [21:52:56 CET] <JEEB> ossifrage: also you can just build locally without doing cross-compile or anything. the issue should be visible without all that [21:53:15 CET] <JEEB> also, most cross-compiles to ARM or otherwise have actually had zero patching [21:53:41 CET] Action: JEEB has done ARMv7 standard lunix, ARMv7 and aarch64 android, win32/64 [21:53:47 CET] <ossifrage> JEEB, I thought everything was ready to go when I compiled it locally, which is why I switched to the cross build [21:54:18 CET] <JEEB> I was mostly referring to you saying it takes long to compile :P [21:54:18 CET] <ossifrage> Yeah ARM stuff cross compiles really well [21:54:33 CET] <JEEB> so you don't have to test with whatever you're compiling for [21:54:42 CET] <JEEB> you could just do a local x86_&4 build with similar params [21:54:53 CET] <JEEB> unless you meant that as taking time [21:55:33 CET] <ossifrage> The minimal x86_64 compile is fast, but it wasn't actually compiling something that linked against the library [21:55:59 CET] <JEEB> you should be able to check with ldd or something [21:56:10 CET] <JEEB> although that only has the dependencies there [21:56:16 CET] <JEEB> I don't think it checks for missing symbols? [21:56:29 CET] <JEEB> although I would have thought that would get a failure during link phase in building? [21:56:33 CET] <JEEB> (of FFmpeg that is) [21:56:55 CET] <ossifrage> BR2_PACKAGE_FFMPEG_MUXERS="dash,hls,h264,hevc,mov,mp4,m4v,smoothstreaming,segment,webvtt,rtp" [21:56:55 CET] <ossifrage> BR2_PACKAGE_FFMPEG_DEMUXERS="dash,hls,h264,hevc,mov,m4v,webvtt,rtp" [21:57:28 CET] <ossifrage> That results in the jpeg tables dep, it worked without rtp [21:57:44 CET] <ossifrage> Adding -lavcodec does not help [21:58:02 CET] <JEEB> rtpdec should have the jpegtables dep [21:58:22 CET] <JEEB> (you can look at git grep "jpegtables" -- configure [22:01:22 CET] <ossifrage> is rtpdec the same as the demuxer/muxer? I only turned on the muxer/demuxer, not the encoder/decoder (none of the encoder/decoders are enabled at ./configure) [22:01:53 CET] <JEEB> yea, the nomenclature is just used for (de)muxers as well in some file names etc [22:16:49 CET] <damdai> anybody who is video expert who can maybe help me? [22:17:53 CET] <damdai> i have like 6 1920x1080 2 are sharp/looksgood 2 are grainy/non-sharp 1 = grainy/sharp [22:18:14 CET] <damdai> they are all 1920x1080 so they are all HD [22:18:50 CET] <damdai> but 2 of them just looks bad [22:18:53 CET] <damdai> why is that [22:22:54 CET] <Mavrik> damdai, did the camera have the wrong focus set? :) [22:23:39 CET] <damdai> mavrik maybe, i am trying to figure out, if it's lighting/wrongcamerasetup/editing [22:23:46 CET] <damdai> or something else [22:24:04 CET] <Mavrik> Also, besides resolution, the quality of an encoded video is also determined by the bitrate [22:24:17 CET] <Mavrik> But before you go look at that, first figure out if your source was the same :) [22:24:32 CET] <damdai> they all use h264 with similar bitrate [22:25:08 CET] <damdai> Overall bit rate : 10.2 Mb/s [22:25:08 CET] <damdai> Encoded date : UTC 2010-12-14 01:52:31 [22:25:08 CET] <damdai> Tagged date : UTC 2010-12-14 01:52:31 [22:25:08 CET] <damdai> Writing library : Apple QuickTime [22:26:00 CET] <damdai> they all are 10.2Mb/s apple qt [23:31:37 CET] <ncouloute> So I have a slight variable fps interlaced file that I converted with ffmpeg the resulting file seems to have frames missing and the time stamp is off. Any advice on that? I dont have an deinterlacing settings in play but it seems it was deinterlaced automatically which is what i want anyways. Using fps filter to convert to 60000/1001 [23:55:56 CET] <KombuchaKip> What is the current state of the relationship between libav and ffmpeg? I know it was bad in the past. [23:59:03 CET] <JEEB> nobody really cares at this point. The loud people from both sides are long gone. Libav is at this point a hobby project of a few people who know what they want from the thing, and FFmpeg is the mess it is (in both good and bad) [23:59:28 CET] <JEEB> speaking as someone who has contributed to both [00:00:00 CET] --- Sun Mar 17 2019