Advanced search

On other websites (4349)

• React-Native FFmpeg-kit VideoCompress command not working

  6 September 2024, by Brian

  I'm Using FFmpeg-kit's React-Native Kit

  


  And I want to encode H264 to HEVC.
But the Videotoolbox in ios not working

  


  I use "ffmpeg-kit-react-native": "^6.0.2"
And here is my Code

  


          // hevc_videotoolbox
        await FFmpegKit.execute(`-i ${videoUri} -c:v hevc_videotoolbox  -c:a aac -tag:v hvc1 -movflags +faststart -y ${outputUri}`);
      } else {
        await FFmpegKit.execute(`-i ${videoUri} -c:v hevc_omx -c:a aac -tag:v hvc1 -movflags +faststart -y ${outputUri}`);
      }


  


  But I got the error follwed like this

  


   LOG    libavutil      58.  2.100 / 58.  2.100
 LOG    libavcodec     60.  3.100 / 60.  3.100
 LOG    libavformat    60.  3.100 / 60.  3.100
 LOG    libavdevice    60.  1.100 / 60.  1.100
 LOG    libavfilter     9.  3.100 /  9.  3.100
 LOG    libswscale      7.  1.100 /  7.  1.100
 LOG    libswresample   4. 10.100 /  4. 10.100
 LOG  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 
 LOG    Metadata:
 LOG      major_brand     :
 LOG  mp42
 LOG  
 LOG      minor_version   :
 LOG  1
 LOG  
 LOG      compatible_brands:
 LOG  isommp41mp42
 LOG  
 LOG      creation_time   :
 LOG  2024-08-29T02:42:24.000000Z
 LOG  
 LOG    Duration:
 LOG  00:00:23.10
 LOG  , start:
 LOG  0.000000
 LOG  , bitrate:
 LOG  1223 kb/s
 LOG  
 LOG    Stream #0:0
 LOG  [0x1]
 LOG  (und)
 LOG  : Video: h264 (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 640x360 [SAR 1:1 DAR 16:9], 1220 kb/s
 LOG  ,
 LOG  30 fps,
 LOG  30 tbr,
 LOG  600 tbn
 LOG   (default)
 LOG  
 LOG      Metadata:
 LOG        creation_time   :
 LOG  2024-08-29T02:42:24.000000Z
 LOG  
 LOG        handler_name    :
 LOG  Core Media Video
 LOG  
 LOG        vendor_id       :
 LOG  [0][0][0][0]
 LOG  
 LOG  Stream mapping:
 LOG    Stream #0:0 -> #0:0
 LOG   (h264 (native) -> hevc (hevc_videotoolbox))
 LOG  
 LOG  Press [q] to stop, [?] for help
 LOG  [hevc_videotoolbox @ 0x11af89120] Error encoding frame: -12905
 LOG  [hevc_videotoolbox @ 0x11af89120] popping: -542398533
 LOG  [vost#0:0/hevc_videotoolbox @ 0x11af88e50] Error initializing output stream: Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height
 LOG  Conversion failed!


  


  How can I fix this error?

  


  I read the
stack overflow

  


  

  1. Error while opening encoder for output stream #0.0 - maybe incorrect parameters such as bit_rate, rate, width or height

  


  


  2.https://stackoverflow.com/questions/77734601/react-native-ffmpeg-producing-unplayable-hevc-videos-that-still-have-audio

  


  But that links doesn't work for me
I want to compress video's compressing with react-native on ios and android for reducing server cost

  


• I cannot play a mp3 file on Discord's voice channel using discord.py

  1 December 2024, by ra1ned

  I am creating a discord bot that plays lofi for me. It does not play a song for me even though it shows a green indicator on a voice channel.

  


  Here's what I've written:

  


  if message.content == "!join":
    await message.author.voice.channel.connect()
    await message.channel.send("Successfully connected")

if message.content == "!play":
    if message.guild.voice_client is None: 
        await message.channel.send("use !join")
        return
    
    await message.channel.send("playing a song rn")
    print('*** playing a song rn')
    
    message.guild.voice_client.play(discord.FFmpegPCMAudio('lofi.mp3'))


  


  I put FFmpeg.exe and lofi.mp3 in the same directory as this script.
Also, it is strange that FFmpeg does not return any exception nor output on console although it seems to have failed to load the file. I have seen people who had the same problem, but it seems like that they get some error messages, unlike me.

  


  Here's the output on console after using !join

  


  2024-12-01 16:59:39 INFO     discord.voice_state Connecting to voice...
2024-12-01 16:59:39 INFO     discord.voice_state Starting voice handshake... (connection attempt 1)
2024-12-01 16:59:40 INFO     discord.voice_state Voice handshake complete. Endpoint found: japan8946.discord.media
2024-12-01 16:59:40 INFO     discord.voice_state Voice connection complete.


  


  after using !play, it only displays the message I wrote:

  


  *** playing a song rn


  


  Can someone help me with this?

  


• Different container duration between ffmpeg versions which causes audio gaps

  4 September 2024, by blits

  I'm trying to make a looped RTMP stream from a single video (in this
example - YouTube), but starting with version 6.0 it introduces a gap in-between loops in the audio which is quite audible. Version before 6.0 (I
tried 5.1.6 and 4.4.2) work as expected and don't introduce any gaps.

  


  The difference I spotted is that the master version (7.0.2) and the 5.1.6, for
example, report a different duration time. Is there any reason why that might happen?

  


  v5.1.6:

  


   Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'demo-video.mp4':
   Metadata:
     major_brand     : isom
     minor_version   : 512
     compatible_brands: isomiso2avc1mp41
     creation_time   : 2024-09-03T15:30:51.000000Z
     encoder         : Blackmagic Design DaVinci Resolve Studio
   Duration: 00:00:05.00, start: 0.000000, bitrate: 35440 kb/s


  


  v7.0.2:

  


  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'demo-video.mp4':
  Metadata:
    major_brand     : isom
    minor_version   : 512
    compatible_brands: isomiso2avc1mp41
    creation_time   : 2024-09-03T15:30:51.000000Z
    encoder         : Blackmagic Design DaVinci Resolve Studio
  Duration: 00:00:05.01, start: 0.000000, bitrate: 35346 kb/s
  Stream #0:0[0x1](und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 2560x1440 [SAR 1:1 DAR 16:9], 35240 kb/s, 24 fps, 24 tbr, 12288 tbn (default)
      Metadata:
        creation_time   : 2024-09-03T15:30:51.000000Z
        handler_name    : VideoHandler
        vendor_id       : [0][0][0][0]
        encoder         : H.264 NVIDIA
        timecode        : 01:00:00:00


  


  As you can see, v5.1.6 report duration of 00:00:05.00 (which is correct) and v7.0.2 is 00:00:05.01 (1ms longer), which is what I think is causing the issue (but I'm not so sure about that). The original file is 5 seconds long which is what can be checked by ffprobe as well, but some streams report a 00:05.01 duration time.

  


  I tried to remedy this issue in many different ways by trimming the video/audio, using different flags, like -shortest, but that didn't help in any way - there's still a gap in the audio which is noticeable when looping the video. And like I said versions such as v5.1.6 work fine and there's no such gap.

  


  I guess what changed between versions is how ffmpeg interprets these streams but in the end I spent 2 days trying to avoid gaps in audio when streaming and nothing helped.

  


  How to reproduce:

  


  You can just stream the video in any RTMP destination of your liking, like YouTube and observe that there would be gaps (audio break-ups) in between every 5 seconds (once video ends). Video is accessible through the link from the curl command

  


  curl -o stream-audio-gap-issue.mp4 https://r2v.streamloop.app/obj_01j6y0pk83fy8vp06a9mmkkqah.mp4
ffmpeg -re -stream_loop -1 -i stream-audio-gap-issue.mp4 -c copy -f flv rtmp://a.rtmp.youtube.com/live2/[your-key]


  


  Expected: there are no gaps every 5 seconds, like in old versions of ffmpeg

  


  Instead: there are tiny audio gaps which are quite noticable

  


  ffprobe outputs is available on gist: https://gist.github.com/blitss/1e221b4fa8885b1df8ac2096746239cf

  


  I'm looking for literally any workarounds that will help avoid audio gaps whilst still preserving the latest version of ffmpeg.