Recherche avancée

Sur d’autres sites (5341)

• Live streaming and simultaneous local/server video saving with Insta360/Theta 360 camera [closed]

  13 août 2023, par Fornow

  I'm currently working on a project that involves live streaming video from a 360 camera, specifically the Insta360 and Theta models, while also saving the streamed video either locally or on a remote server. I'm relatively new to both live streaming and working with 360 cameras, so I'm seeking guidance on the best approach to achieve this.

  


  My primary goals are as follows :

  


  


  1. Live Streaming : I want to be able to stream the real-time video captured by the 360 camera to a web platform or application, allowing users to experience the immersive 360 content as it happens.

     


  


  2. Simultaneous Video Saving : In addition to live streaming, I also need to save the streamed video. This can either be saved locally on the device running the streaming process or on a remote server. The saved video should ideally retain its 360 nature and high-quality resolution.

     


  


  


  I've been researching various technologies and frameworks like WebRTC for live streaming, but I'm unsure about the compatibility and best practices when dealing specifically with 360 cameras like Insta360 and Theta. Additionally, I'm uncertain about the most efficient way to save the streamed video while maintaining its immersive properties.

  


  If anyone has experience with live streaming from 360 cameras and simultaneously saving the content, could you please provide insights into the following :

  


  

  • Recommended libraries, SDKs, or frameworks for live streaming 360 video from Insta360 or Theta cameras.

  


  • Tips for ensuring the streamed video retains its 360 attributes and high quality.

  


  • Best practices for saving the streamed video either locally or on a remote server while the live stream is ongoing.

  


  


  Any code examples, tutorials, or step-by-step guides would be greatly appreciated. Thank you in advance for your help !

  


• iOS Objective C Opus audio stream kAudioFormatOpus — specification / conversion query

  16 avril 2022, par deffodeffo

  I'm working on a React Native voice app wanting to record straight to an Opus stream.

  


  On the iOS side at device level, I'm working in Objective C and I'm using an AVAudioSession recorder with formatID set to kAudioFormatOpus. The recorder captures audio data in the specified format and passes packets for upstreaming to the React Native app.

  


  This is all working well and emitting a stream of audio data when I run my code on an iOS Simulator or real device.

  


  My problem is when I receive the audio stream in the backend, I find I'm unable to reliably decode the Opus stream using ffmpeg. (I wish to decode to PCM.)

  


  Whilst I could post up specific code to show what I'm doing in more detail, my question at this stage is more generic in nature :

  


  Is anyone familiar with the format of Opus audio stream that is generated by iOS AudioSession recorder under audio format kAudioFormatOpus ? Is anyone able to suggest proven conversion techniques ? (e.g. some ffmpeg commands), or else hook me up with some links to format specs so I can figure out what is going on here ?

  


  The Apple Developer documentation contains zero useful information : https://developer.apple.com/documentation/coreaudiotypes/1572096-audio_data_format_identifiers/kaudioformatopus?changes=la__2&language=objc

  


  I have looked all over the internet, but I'm unable to find any useful spec info that corresponds to the stream that AVAudioSession recorder is outputting. I have seen a few posts which say Apple have not fully complied with the Opus spec, but I don't know enough about the proper structure of Opus to ascertain this for myself.

  


  Any help would be very much appreciated.

  


  Thanks all

  


• lavc/aarch64/fdct : add neon-optimized fdct for aarch64

  17 avril 2024, par Ramiro Polla

  lavc/aarch64/fdct : add neon-optimized fdct for aarch64
  The code is imported from libjpeg-turbo-3.0.1. The neon registers used
  
  have been changed to avoid modifying v8-v15.
  Reviewed-by : Martin Storsjö <martin@martin.st>
  

  • [DH] libavcodec/aarch64/Makefile
  • [DH] libavcodec/aarch64/fdct.h
  • [DH] libavcodec/aarch64/fdctdsp_init_aarch64.c
  • [DH] libavcodec/aarch64/fdctdsp_neon.S
  • [DH] libavcodec/avcodec.h
  • [DH] libavcodec/fdctdsp.c
  • [DH] libavcodec/fdctdsp.h
  • [DH] libavcodec/options_table.h
  • [DH] libavcodec/tests/aarch64/dct.c