Recherche avancée

Sur d’autres sites (10624)

• Issue restreaming with ffmpeg if source/destination drops

  7 septembre 2022, par omega1

  I am using the following command to restream a video stream to another server, but if the source/destination momentarily drops, ffmpeg gives up.

  



  ffmpeg \
-i http://source_stream_ip:port \
-reconnect_at_eof 1 \
-reconnect_streamed 1 \
-y \
-shortest \
-c: libx264 \
    -crf:v 22 \
    -preset:v fast \
    -pix_fmt yuv420p \
    -x264opts keyint=10:no-scenecut=1 \
    -maxrate:v 256k \
    -bufsize:v 512k \
-c:a aac \
    -ac 2 \
    -b:a 96k \
    -maxrate:a 96k \
    -bufsize:a 192k \
-f flv \
rtmp://destination_stream_ip:port


  



  I've tried this as a batch command, but it also eventually gives up.

  



  #!/bin/bash
while :
do
ffmpeg \
-i http://source_stream_ip:port \
-reconnect_at_eof 1 \
-reconnect_streamed 1 \
-y \
-shortest \
-c: libx264 \
    -crf:v 22 \
    -preset:v fast \
    -pix_fmt yuv420p \
    -x264opts keyint=10:no-scenecut=1 \
    -maxrate:v 256k \
    -bufsize:v 512k \
-c:a aac \
    -ac 2 \
    -b:a 96k \
    -maxrate:a 96k \
    -bufsize:a 192k \
-f flv \
rtmp://destination_stream_ip:port
done


  



  Could anyone recommend an improvement to doing this or even another way of doing this even without ffmpeg by using another command line tool ? At the moment it is too unreliable to use on a permanent basis.

  


• Interfacing to an Xbox Optical Drive

  1er octobre 2013, par Multimedia Mike — xbox

  The next generation Xbox is going to hit the streets soon. But for some reason, I’m still interested in the previous generation’s unit (i.e., the original Xbox). Specifically, I’ve always wondered if it’s possible to use the original Xbox’s optical drive in order to read Xbox discs from Linux. I was never curious enough to actually buy an Xbox just to find out but I eventually came across a cast-off console on a recycle pile.

  I have long known that the Xbox has what appears to be a more or less standard optical drive with a 40-pin IDE connector. The only difference is the power adapter which I surmise is probably the easiest way to turn a bit of standardized hardware into a bit of proprietary hardware. The IDE and power connectors look like this :

  
  
  

  Thus, I wanted to try opening an Xbox and plugging the optical drive into a regular PC, albeit one that supports IDE cables, and allow the Xbox to supply power to the drive. Do you still have hardware laying around that has 40-pin IDE connectors ? I guess my Mac Mini PPC fits the bill, but I’ll be darned if I’m going to pry that thing open again. I have another IDE-capable machine buried in my closet, last called into service when I needed a computer with a native RS-232 port 3 years ago. The ordeal surrounding making this old computer useful right now can be another post entirely.

  Here’s what the monstrosity looks like thanks to characteristically short IDE cable lengths :

  
  

  

  Click for larger image

  
  

  Process :

  1. Turn on Xbox first
  2. Turn on PC

  Doing these things in the opposite order won’t work since the kernel really wants to see the drive when booting up. Inspecting the 'dmesg' log afterward reveals interesting items :
  

  <br />
hdd: PHILIPS XBOX DVD DRIVE, ATAPI CD/DVD-ROM drive<br />
hdd: host max PIO5 wanted PIO255(auto-tune) selected PIO4<br />
hdd: UDMA/33 mode selected<br />
[...]<br />
hdd: ATAPI DVD-ROM drive, 128kB Cache<br />

  Why is that interesting ? When is the last time to saw disk devices prefixed by ‘hd’ rather than ‘sd’ ? Blast from the past. Oh, and the optical drive’s vendor string clearly indicates that this is an Xbox drive saying ‘hi !’.

  Time To Read
  When I first studied an Xbox disc in a normal optical drive, I noticed that I was able to read 6992 2048-byte sectors — about 14 MB of data — as reported by the disc table of contents (TOC). This is just enough data to play a standard DVD video animation that kindly instructs the viewer to please use a proper Xbox. At this point, I estimated that there must be something special about Xbox optical drive firmware that knows how to read alternate information on these discs and access further sectors.

  I ran my TOC query tool with an Xbox Magazine demo disc in the optical drive and it reported substantially more than 6992 sectors, enough to account for more than 2 GB of data. That’s promising. I then tried running 'dd' against the device and it was able to read… about 14 MB, an exact quantity of bytes that, when divided by 2048 bytes/sector, yields 6992 sectors.

  Future (Past ?) Work
  Assuming Google is your primary window into the broader internet, the world is beginning to lose its memory of things pertaining to the original Xbox (Microsoft’s naming scheme certainly doesn’t help searches). What I’m saying is that it can be difficult to find information about this stuff now. However, I was able to learn that a host needs to perform a sort of cryptographic handshake with the drive at the SCSI level before it is allowed to access the forbidden areas of the disc. I think. I’m still investigating this and will hopefully post more soon.

• lsws/ppc/yuv2rgb_altivec : Fix build in non-VSX environments

  10 octobre 2020, par Chip Kerchner

  lsws/ppc/yuv2rgb_altivec : Fix build in non-VSX environments
  Add inline function for vec_xl if VSX is not supported. vec_xl intrinsic
  
  is only available on POWER 7 or higher.
  Fixes ticket #8750.
  Signed-off-by : Andriy Gelman <andriy.gelman@gmail.com>
  

  • [DH] libswscale/ppc/yuv2rgb_altivec.c