Recherche avancée

Sur d’autres sites (8783)

• How to adjust mpeg 2 ts start time with ffmpeg ?

  29 juin 2015, par Maxim Kornienko

  I’m writing simple HLS (Http Live Streaming) java server to live cast (really live, not on demand) screenshow + voice. I constantly get chunks of image frames and audio samples as input to my service and produce mpeg 2 ts files + m3u8 playlist web page as output. The workflow is the following :

  1. Collect (buffer) source video frames and audio for certain period of time
  2. Convert series of video frames to h.264 encoded video file
  3. Convert audio samples to mp3 audio file

  4. Merge them to .ts file with ffmpeg command

     ffmpeg -i audio.mp3 -i video.mp4 -f mpegts -c:a copy -c:v copy -vprofile main -level:v 4.0 -vbsf h264_mp4toannexb -flags -global_header segment.ts

  5. Publish several .ts files on m3u8 playlist.

  The problem is resulting playlist interrupts after first segment is played. VLC logs following error :

  freetype error: Breaking unbreakable line
  
  ts error: libdvbpsi (PSI decoder): TS discontinuity (received 0, expected 4) for PID 17
  
  ts error: libdvbpsi (PSI decoder): TS duplicate (received 0, expected 1) for PID 0
  
  ts error: libdvbpsi (PSI decoder): TS duplicate (received 0, expected 1) for PID 4096
  
  core error: ES_OUT_SET_(GROUP_)PCR is called too late (pts_delay increased to 1000 ms)
  
  core error: ES_OUT_RESET_PCR called
  
  core error: Could not convert timestamp 185529572000
  
  ts error: libdvbpsi (PSI decoder): TS discontinuity (received 0, expected 4) for PID 17
  
  ts error: libdvbpsi (PSI decoder): TS duplicate (received 0, expected 1) for PID 0
  
  ts error: libdvbpsi (PSI decoder): TS duplicate (received 0, expected 1) for PID 4096
  
  core error: ES_OUT_SET_(GROUP_)PCR is called too late (jitter of 8653 ms ignored)
  
  core error: Could not get display date for timestamp 0
  
  core error: Could not convert timestamp 185538017000
  
  core error: Could not convert timestamp 185538267000
  
  core error: Could not convert timestamp 185539295977
  
  ...

  I guess the reason is that start time of segments do not belong to one stream, but it’s impossible to concat and resegment (with ffmepg -f segment) whole stream once new chunk is added. Tried adding #EXT-X-DISCONTINUITY tag to playlist as suggested here but it didn’t help. When I ffprobe them I get :

  Input #0, mpegts, from '26.ts':
  
  Duration: 00:00:10.02, start: 1.876978, bitrate: 105 kb/s
  
  Program 1
  
  Metadata:
  
    service_name    : Service01
  
    service_provider: FFmpeg
  
  Stream #0:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p, 640x640, 4 fps, 4 tbr, 90k tbn, 8 tbc
  
  Stream #0:1[0x101]: Audio: mp3 ([3][0][0][0] / 0x0003), 48000 Hz, mono, s16p, 64 kb/s   

  Where start value in line Duration: 00:00:10.02, start: 1.876978, bitrate: 105 kb/s is more or less equal for all segments.
  When I check segments from available proven-to-work playlists (like http://vevoplaylist-live.hls.adaptive.level3.net/vevo/ch1/appleman.m3u8) they all have diffrenet start values for each segment, for example :

  Input #0, mpegts, from 'segm150518140104572-424570.ts':
  
  Duration: 00:00:06.17, start: 65884.808689, bitrate: 479 kb/s
  
  Program 257
  
  Stream #0:0[0x20]: Video: h264 (Constrained Baseline) ([27][0][0][0] / 0x001B), yuv420p, 320x180 [SAR 1:1 DAR 16:9], 30 fps, 29.97 tbr, 90k tbn, 60 tbc
  
  Stream #0:1[0x21]: Audio: aac (LC) ([15][0][0][0] / 0x000F), 44100 Hz, stereo, fltp, 115 kb/s
  
  Stream #0:2[0x22]: Data: timed_id3 (ID3  / 0x20334449)

  and the next after it

  Input #0, mpegts, from 'segm150518140104572-424571.ts':
  
  Duration: 00:00:06.22, start: 65890.814689, bitrate: 468 kb/s
  
  Program 257
  
  Stream #0:0[0x20]: Video: h264 (Constrained Baseline) ([27][0][0][0] / 0x001B), yuv420p, 320x180 [SAR 1:1 DAR 16:9], 30 fps, 29.97 tbr, 90k tbn, 60 tbc
  
  Stream #0:1[0x21]: Audio: aac (LC) ([15][0][0][0] / 0x000F), 44100 Hz, stereo, fltp, 124 kb/s
  
  Stream #0:2[0x22]: Data: timed_id3 (ID3  / 0x20334449)

  differ in the way that start time of segm150518140104572-424571.ts is equal to start time + duration of segm150518140104572-424570.ts.

  How could this start value be adjusted with ffmpeg ? Or maybe my whole aproach is wrong ? Unfortunately I couldn’t find on the internet working example of live (not on demand) video service implemented with ffmepg.

• How to adjust mpeg 2 ts start time with ffmpeg ?

  24 juillet 2019, par Maxim Kornienko

  I’m writing simple HLS (Http Live Streaming) java server to live cast (really live, not on demand) screenshow + voice. I constantly get chunks of image frames and audio samples as input to my service and produce mpeg 2 ts files + m3u8 playlist web page as output. The workflow is the following :

  1. Collect (buffer) source video frames and audio for certain period of time
  2. Convert series of video frames to h.264 encoded video file
  3. Convert audio samples to mp3 audio file

  4. Merge them to .ts file with ffmpeg command

     ffmpeg -i audio.mp3 -i video.mp4 -f mpegts -c:a copy -c:v copy -vprofile main -level:v 4.0 -vbsf h264_mp4toannexb -flags -global_header segment.ts

  5. Publish several .ts files on m3u8 playlist.

  The problem is resulting playlist interrupts after first segment is played. VLC logs following error :

  freetype error: Breaking unbreakable line
  
  ts error: libdvbpsi (PSI decoder): TS discontinuity (received 0, expected 4) for PID 17
  
  ts error: libdvbpsi (PSI decoder): TS duplicate (received 0, expected 1) for PID 0
  
  ts error: libdvbpsi (PSI decoder): TS duplicate (received 0, expected 1) for PID 4096
  
  core error: ES_OUT_SET_(GROUP_)PCR is called too late (pts_delay increased to 1000 ms)
  
  core error: ES_OUT_RESET_PCR called
  
  core error: Could not convert timestamp 185529572000
  
  ts error: libdvbpsi (PSI decoder): TS discontinuity (received 0, expected 4) for PID 17
  
  ts error: libdvbpsi (PSI decoder): TS duplicate (received 0, expected 1) for PID 0
  
  ts error: libdvbpsi (PSI decoder): TS duplicate (received 0, expected 1) for PID 4096
  
  core error: ES_OUT_SET_(GROUP_)PCR is called too late (jitter of 8653 ms ignored)
  
  core error: Could not get display date for timestamp 0
  
  core error: Could not convert timestamp 185538017000
  
  core error: Could not convert timestamp 185538267000
  
  core error: Could not convert timestamp 185539295977
  
  ...

  I guess the reason is that start time of segments do not belong to one stream, but it’s impossible to concat and resegment (with ffmepg -f segment) whole stream once new chunk is added. Tried adding #EXT-X-DISCONTINUITY tag to playlist as suggested here but it didn’t help. When I ffprobe them I get :

  Input #0, mpegts, from '26.ts':
  
  Duration: 00:00:10.02, start: 1.876978, bitrate: 105 kb/s
  
  Program 1
  
  Metadata:
  
    service_name    : Service01
  
    service_provider: FFmpeg
  
  Stream #0:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p, 640x640, 4 fps, 4 tbr, 90k tbn, 8 tbc
  
  Stream #0:1[0x101]: Audio: mp3 ([3][0][0][0] / 0x0003), 48000 Hz, mono, s16p, 64 kb/s   

  Where start value in line Duration: 00:00:10.02, start: 1.876978, bitrate: 105 kb/s is more or less equal for all segments.
  When I check segments from available proven-to-work playlists (like http://vevoplaylist-live.hls.adaptive.level3.net/vevo/ch1/appleman.m3u8) they all have diffrenet start values for each segment, for example :

  Input #0, mpegts, from 'segm150518140104572-424570.ts':
  
  Duration: 00:00:06.17, start: 65884.808689, bitrate: 479 kb/s
  
  Program 257
  
  Stream #0:0[0x20]: Video: h264 (Constrained Baseline) ([27][0][0][0] / 0x001B), yuv420p, 320x180 [SAR 1:1 DAR 16:9], 30 fps, 29.97 tbr, 90k tbn, 60 tbc
  
  Stream #0:1[0x21]: Audio: aac (LC) ([15][0][0][0] / 0x000F), 44100 Hz, stereo, fltp, 115 kb/s
  
  Stream #0:2[0x22]: Data: timed_id3 (ID3  / 0x20334449)

  and the next after it

  Input #0, mpegts, from 'segm150518140104572-424571.ts':
  
  Duration: 00:00:06.22, start: 65890.814689, bitrate: 468 kb/s
  
  Program 257
  
  Stream #0:0[0x20]: Video: h264 (Constrained Baseline) ([27][0][0][0] / 0x001B), yuv420p, 320x180 [SAR 1:1 DAR 16:9], 30 fps, 29.97 tbr, 90k tbn, 60 tbc
  
  Stream #0:1[0x21]: Audio: aac (LC) ([15][0][0][0] / 0x000F), 44100 Hz, stereo, fltp, 124 kb/s
  
  Stream #0:2[0x22]: Data: timed_id3 (ID3  / 0x20334449)

  differ in the way that start time of segm150518140104572-424571.ts is equal to start time + duration of segm150518140104572-424570.ts.

  How could this start value be adjusted with ffmpeg ? Or maybe my whole aproach is wrong ? Unfortunately I couldn’t find on the internet working example of live (not on demand) video service implemented with ffmepg.

• 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.