Recherche avancée

Sur d’autres sites (8812)

• Texture bound to texture unit 0 is not renderable

  2 décembre 2018, par Trying_To_Understand

  I followed this tutorial https://github.com/phoboslab/jsmpeg. I have an open wesocket that gets the data. Sometimes, it’s take a long time to the ffmpeg (on a remote computer) to get the data from my ip camera, so I wrote a setTimeout function that waites for 10 sec to be "sure" that the ffmpeg getting the data from the ip camera. If I remove this setTimeout function this error will show up :

  [.WebGL-0000020CFA5C04D0]RENDER WARNING : texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.

  This is my code for showing the stream to the client :

  this.dataService.getDataByParam(camera.CameraId.toString())
  
    .subscribe(
  
    (result: any) => {
  
  
  
      setTimeout(() => {
  
        this.ws = new WebSocket('ws://' + result);
  
        $(document).ready(() => {
  
  
  
          this.player = new jsmpeg(this.ws, {
  
            canvas: document.getElementById("canvas"),
  
            autoplay: true,
  
            audio: true,
  
            pauseWhenHidden: false,
  
          });
  
  
  
        })
  
      }, 10000);
  
    },
  
    (error: Error) => {
  
      this.streamErrorMsg = "Problem with the server, please try again after some time."
  
    });
  
   }

  How can i know for sure that the ffmpeg has connected successfully to the camera and started to convert the data on the client ? i want to avoid writting the setTimeout function.

• Linux : Create a file for writing with controlled flushing to disk in large chunks [closed]

  12 août 2023, par Pete

  On Linux I have a process (ffmpeg) that writes very slowly (even slower than 1kb / s sometimes) to disk. Ffmpeg can buffer this to 256kb chunks that get written infrequently but ffmpeg hangs occasionally and if I try to detect these hangs by checking that the file is being updated I need to wait a long time between updates, up to 10 or 15 mins, otherwise I can sometimes mistakenly kill the ffmpeg process when it appears to have stopped writing when it fact its still filling its internal buffer.

  


  Theres no way to detect this it seems unless I use strace (that I can find anyway). So I am wondering about turning off buffering in ffmpeg and writing unbuffered to disk from ffmpeg.

  


  This will result in the disk constantly making tiny writes and wasting power (and probably, if I use a SSD, mess with wear levelling too).

  


  So I would like to make ffmpeg write to a 'virtual file' (in memory - either kernel memory or a process) which I can specify the flushing characteristics of. The idea being to perhaps specify flush every 2 minutes, then I can keep an eye on the file size and make sure its still being written.

  


  I don't think I've missed any other ways to do this job - even if I could watch the socket stream incoming to ffpmeg the process itself could still stop writing and lose data. Doing the buffering outside of ffmpeg seems like the best way.

  


  Is there a built in way to do this in Linux or does it mean a custom process ? I guess I know how to do this with a small C program and pipe the data in but I wonder if theres a neater way.

  


• Revision 3265 : On passe un nouvel argument possible au formulaire permettant de lui ...

  18 avril 2010, par kent1 — Log

  On passe un nouvel argument possible au formulaire permettant de lui indiquer directement quel est le tri actuel Dans le cas d’une page recherche, on ajoute un critère de tri qui est points (pertinence)