Recherche avancée

Sur d’autres sites (8446)

• Mixing a FLV audio stream with a WAV background track, and converting to MP3 with SoX and FFmpeg

  7 septembre 2012, par tubbo

  I'm building a Flash-based recording application for a contracted web site. It streams the recorded voice (via SWF) to a Red5 server, then uses a combination of FFmpeg and SoX to compile the vocal audio with a lower-in-volume background music track. This all has to happen on-demand, that is, when a user "saves" his or her vocal recording.

  Here is an example command I will be running. Names have been changed to protect the innocent. The filenames describe their role in the final file :

  sox --combine mix -p --no-show-progress --norm "|ffmpeg -i /usr/share/red5/webapps/audiorecorder/stream/SPOKEN_VOICE.flv -t wav pipe:1" /var/www/ufiles/music/BACKGROUND_MUSIC.wav - | ffmpeg -i pipe:1 /var/www/ufiles/recordings/COMPILED_AUDIO_RECORDING.mp3

  When I run this command in the shell, this is what happens :

  $ sox --combine mix -p --no-show-progress --norm "|ffmpeg -i audioStream_1321399534128_21.flv -ar 44100 -ac 2 -t wav pipe:1" wrong.wav - | ffmpeg -i pipe:1 ~/www/trauma101.com/compiled.mp3
  
  ffmpeg version N-34884-g7575980, Copyright (c) 2000-2011 the FFmpeg developers
  
    built on Nov 15 2011 14:06:49 with gcc 4.4.5
  
    configuration: --enable-gpl --enable-version3 --enable-nonfree --enable-postproc --enable-libfaac --enable-libmp3lame --enable-libx264 --enable-x11grab --enable-libspeex
  
    libavutil    51. 25. 0 / 51. 25. 0
  
    libavcodec   53. 34. 0 / 53. 34. 0
  
    libavformat  53. 20. 0 / 53. 20. 0
  
    libavdevice  53.  4. 0 / 53.  4. 0
  
    libavfilter   2. 48. 1 /  2. 48. 1
  
    libswscale    2.  1. 0 /  2.  1. 0
  
    libpostproc  51.  2. 0 / 51.  2. 0
  
  ffmpeg version N-34884-g7575980, Copyright (c) 2000-2011 the FFmpeg developers
  
    built on Nov 15 2011 14:06:49 with gcc 4.4.5
  
    configuration: --enable-gpl --enable-version3 --enable-nonfree --enable-postproc --enable-libfaac --enable-libmp3lame --enable-libx264 --enable-x11grab --enable-libspeex
  
    libavutil    51. 25. 0 / 51. 25. 0
  
    libavcodec   53. 34. 0 / 53. 34. 0
  
    libavformat  53. 20. 0 / 53. 20. 0
  
    libavdevice  53.  4. 0 / 53.  4. 0
  
    libavfilter   2. 48. 1 /  2. 48. 1
  
    libswscale    2.  1. 0 /  2.  1. 0
  
    libpostproc  51.  2. 0 / 51.  2. 0
  
  [libspeex @ 0x1e36b20] Missing Speex header, assuming defaults.
  
  Input #0, flv, from 'audioStream_1321399534128_21.flv':
  
    Metadata:
  
      novideocodec    : 0
  
      server          : Red5 Server 1.0.0 RC2 Rev: 4295
  
      creationdate    : Tue Nov 15 15:25:41 PST 2011
  
      canSeekToEnd    : true
  
    Duration: 00:00:06.77, start: 0.000000, bitrate: 43 kb/s
  
      Stream #0:0: Audio: speex, 16000 Hz, 1 channels, s16
  
  Invalid duration specification for t: wav
  
  sox FAIL formats: can't open input pipe `|ffmpeg -i audioStream_1321399534128_21.flv -ar 44100 -ac 2 -t wav pipe:1': premature EOF

  I think the issue is stemming from the conversion from FLV to WAV in FFmpeg, and since it's being piped in it causes the whole process to fail. I always get that duration warning, but when FFmpeg outputs to a .wav file and the SoX command is run separately, I can still get a WAV from SoX and convert that to MP3 manually. I'd like to do all this in one line, piping the data between applications.

  What do I do ?

• How to make that video module can generate readable files for the module JW Player ?

  4 janvier 2015, par Dvex

  I use Drupal 7.x with Video Module, Video Pressets for FFMPEG and JW Player.
  I install FFMPEG with this Guide : https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu in Ubuntu 14.04

  I’m using jQuery 1.8

  I downloaded the files that the JW Player module requires and renamed some files, as the guide tells me.

  I set the video module so you can use FFMPEG and established the necessary pressets (FLV, MP4 and WebM) for any browser (web and mobile).

  I changed the default settings of these pressets. I put check the option : Force one-pass Encoding. Because if not me error message :

  PHPVideoToolkit error: Execute error. It was not possible to encode "/var/www/html/sites/default/files/private/videos/original/reel para web en loop_2.mp4" as FFmpeg returned an error. Note, however the error was encountered on the second pass of the encoding process and the first pass appear to go fine. The error is with the video codec of the input file. FFmpeg reports the error to be "Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height".
  
  
  
  /usr/bin/ffmpeg -i '/var/www/html/sites/default/files/private/videos/original/reel para web en loop_2.mp4' -strict experimental -vcodec 'h264' -acodec 'aac' -vprofile 'baseline' -ac '2' -pass '1' -passlogfile '/tmp/1420389438-54a96c3eda9fc-multipass'  -y /tmp/1420389438-54a96c3eda8c1.mp4
  
  ffmpeg version 1.2.6-7:1.2.6-1~trusty1 Copyright (c) 2000-2014 the FFmpeg developers
  
    built on Apr 26 2014 18:52:58 with gcc 4.8 (Ubuntu 4.8.2-19ubuntu1)
  
    configuration: --arch=amd64 --disable-stripping --enable-avresample --enable-pthreads --enable-runtime-cpudetect --extra-version='7:1.2.6-1~trusty1' --libdir=/usr/lib/x86_64-linux-gnu --prefix=/usr --enable-bzlib --enable-libdc1394 --enable-libfreetype --enable-frei0r --enable-gnutls --enable-libgsm --enable-libmp3lame --enable-librtmp --enable-libopencv --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-vaapi --enable-vdpau --enable-libvorbis --enable-libvpx --enable-zlib --enable-gpl --enable-postproc --enable-libcdio --enable-x11grab --enable-libx264 --shlibdir=/usr/lib/x86_64-linux-gnu --enable-shared --disable-static
  
    libavutil      52. 18.100 / 52. 18.100
  
    libavcodec     54. 92.100 / 54. 92.100
  
    libavformat    54. 63.104 / 54. 63.104
  
    libavdevice    53.  5.103 / 53.  5.103
  
    libavfilter     3. 42.103 /  3. 42.103
  
    libswscale      2.  2.100 /  2.  2.100
  
    libswresample   0. 17.102 /  0. 17.102
  
    libpostproc    52.  2.100 / 52.  2.100
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/var/www/html/sites/default/files/private/videos/original/reel para web en loop_2.mp4':
  
    Metadata:
  
      major_brand     : mp42
  
      minor_version   : 0
  
      compatible_brands: mp42mp41
  
      creation_time   : 2013-09-12 17:30:22
  
    Duration: 00:00:39.32, start: 0.000000, bitrate: 3190 kb/s
  
      Stream #0:0(eng): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 720x480 [SAR 40:33 DAR 20:11], 2991 kb/s, 29.97 fps, 29.97 tbr, 29970 tbn, 59.94 tbc
  
      Metadata:
  
        creation_time   : 2013-09-12 17:30:22
  
        handler_name    : Mainconcept MP4 Video Media Handler
  
      Stream #0:1(eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 189 kb/s
  
      Metadata:
  
        creation_time   : 2013-09-12 17:30:22
  
        handler_name    : Mainconcept MP4 Sound Media Handler
  
  [libx264 @ 0x164dec0] using SAR=40/33
  
  [libx264 @ 0x164dec0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX
  
  [libx264 @ 0x164dec0] profile Constrained Baseline, level 3.0
  
  [libx264 @ 0x164dec0] 264 - core 142 r2389 956c8d8 - H.264/MPEG-4 AVC codec - Copyleft 2003-2014 - http://www.videolan.org/x264.html - options: cabac=0 ref=1 deblock=1:0:0 analyse=0x1:0 me=dia subme=2 psy=1 psy_rd=1.00:0.00 mixed_ref=0 me_range=16 chroma_me=1 trellis=0 8x8dct=0 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=0 threads=6 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=0 weightp=0 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
  
  Output #0, mp4, to '/tmp/1420389438-54a96c3eda8c1.mp4':
  
    Metadata:
  
      major_brand     : mp42
  
      minor_version   : 0
  
      compatible_brands: mp42mp41
  
      encoder         : Lavf54.63.104
  
      Stream #0:0(eng): Video: h264 ([33][0][0][0] / 0x0021), yuv420p, 720x480 [SAR 40:33 DAR 20:11], q=-1--1, pass 1, 11988 tbn, 29.97 tbc
  
      Metadata:
  
        creation_time   : 2013-09-12 17:30:22
  
        handler_name    : Mainconcept MP4 Video Media Handler
  
      Stream #0:1(eng): Audio: aac ([64][0][0][0] / 0x0040), 48000 Hz, stereo, fltp, 128 kb/s
  
      Metadata:
  
        creation_time   : 2013-09-12 17:30:22
  
        handler_name    : Mainconcept MP4 Sound Media Handler
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (h264 -> libx264)
  
    Stream #0:1 -> #0:1 (aac -> aac)
  
  Press [q] to stop, [?] for help
  
  frame=   88 fps=0.0 q=29.0 size=     483kB time=00:00:02.96 bitrate=1335.6kbits/s dup=1 drop=0    
  
  frame=  190 fps=189 q=29.0 size=    1916kB time=00:00:06.33 bitrate=2477.6kbits/s dup=1 drop=0    
  
  frame=  289 fps=192 q=29.0 size=    3001kB time=00:00:09.64 bitrate=2549.5kbits/s dup=1 drop=0    
  
  frame=  395 fps=196 q=29.0 size=    3732kB time=00:00:13.31 bitrate=2296.7kbits/s dup=1 drop=0    
  
  frame=  495 fps=197 q=29.0 size=    4481kB time=00:00:16.66 bitrate=2203.1kbits/s dup=1 drop=0    
  
  frame=  591 fps=196 q=29.0 size=    5152kB time=00:00:19.98 bitrate=2111.4kbits/s dup=1 drop=0    
  
  frame=  690 fps=196 q=29.0 size=    6329kB time=00:00:23.01 bitrate=2252.4kbits/s dup=1 drop=0    
  
  frame=  790 fps=197 q=29.0 size=    7184kB time=00:00:26.32 bitrate=2235.6kbits/s dup=1 drop=0    
  
  frame=  890 fps=197 q=29.0 size=    8532kB time=00:00:29.73 bitrate=2350.3kbits/s dup=1 drop=0    
  
  frame= 1000 fps=199 q=29.0 size=    9398kB time=00:00:33.42 bitrate=2303.0kbits/s dup=1 drop=0    
  
  frame= 1106 fps=200 q=29.0 size=   10423kB time=00:00:37.01 bitrate=2306.8kbits/s dup=1 drop=0    
  
  frame= 1178 fps=199 q=-1.0 Lsize=   11404kB time=00:00:39.31 bitrate=2376.1kbits/s dup=1 drop=0
  
  video:10752kB audio:618kB subtitle:0 global headers:0kB muxing overhead 0.302603%
  
  [libx264 @ 0x164dec0] frame I:87    Avg QP:24.23  size: 21823
  
  [libx264 @ 0x164dec0] frame P:1091  Avg QP:25.90  size:  8351
  
  [libx264 @ 0x164dec0] mb I  I16..4: 50.9%  0.0% 49.1%
  
  [libx264 @ 0x164dec0] mb P  I16..4: 14.8%  0.0%  0.0%  P16..4: 51.3%  0.0%  0.0%  0.0%  0.0%    skip:33.9%
  
  [libx264 @ 0x164dec0] coded y,uvDC,uvAC intra: 43.9% 38.7% 10.2% inter: 23.0% 14.4% 0.8%
  
  [libx264 @ 0x164dec0] i16 v,h,dc,p: 31% 39% 19% 11%
  
  [libx264 @ 0x164dec0] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 18% 44% 14%  5%  4%  4%  4%  4%  4%
  
  [libx264 @ 0x164dec0] i8c dc,h,v,p: 57% 22% 17%  4%
  
  [libx264 @ 0x164dec0] kb/s:2240.77
  
  /usr/bin/ffmpeg -i '/var/www/html/sites/default/files/private/videos/original/reel para web en loop_2.mp4' -strict experimental -vcodec 'h264' -acodec 'aac' -vprofile 'baseline' -ac '2' -pass '2' -passlogfile '/tmp/1420389438-54a96c3eda9fc-multipass'  -y /tmp/1420389438-54a96c3eda8c1.mp4
  
  ffmpeg version 1.2.6-7:1.2.6-1~trusty1 Copyright (c) 2000-2014 the FFmpeg developers
  
    built on Apr 26 2014 18:52:58 with gcc 4.8 (Ubuntu 4.8.2-19ubuntu1)
  
    configuration: --arch=amd64 --disable-stripping --enable-avresample --enable-pthreads --enable-runtime-cpudetect --extra-version='7:1.2.6-1~trusty1' --libdir=/usr/lib/x86_64-linux-gnu --prefix=/usr --enable-bzlib --enable-libdc1394 --enable-libfreetype --enable-frei0r --enable-gnutls --enable-libgsm --enable-libmp3lame --enable-librtmp --enable-libopencv --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-vaapi --enable-vdpau --enable-libvorbis --enable-libvpx --enable-zlib --enable-gpl --enable-postproc --enable-libcdio --enable-x11grab --enable-libx264 --shlibdir=/usr/lib/x86_64-linux-gnu --enable-shared --disable-static
  
    libavutil      52. 18.100 / 52. 18.100
  
    libavcodec     54. 92.100 / 54. 92.100
  
    libavformat    54. 63.104 / 54. 63.104
  
    libavdevice    53.  5.103 / 53.  5.103
  
    libavfilter     3. 42.103 /  3. 42.103
  
    libswscale      2.  2.100 /  2.  2.100
  
    libswresample   0. 17.102 /  0. 17.102
  
    libpostproc    52.  2.100 / 52.  2.100
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/var/www/html/sites/default/files/private/videos/original/reel para web en loop_2.mp4':
  
    Metadata:
  
      major_brand     : mp42
  
      minor_version   : 0
  
      compatible_brands: mp42mp41
  
      creation_time   : 2013-09-12 17:30:22
  
    Duration: 00:00:39.32, start: 0.000000, bitrate: 3190 kb/s
  
      Stream #0:0(eng): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 720x480 [SAR 40:33 DAR 20:11], 2991 kb/s, 29.97 fps, 29.97 tbr, 29970 tbn, 59.94 tbc
  
      Metadata:
  
        creation_time   : 2013-09-12 17:30:22
  
        handler_name    : Mainconcept MP4 Video Media Handler
  
      Stream #0:1(eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 189 kb/s
  
      Metadata:
  
        creation_time   : 2013-09-12 17:30:22
  
        handler_name    : Mainconcept MP4 Sound Media Handler
  
  [libx264 @ 0x161eec0] using SAR=40/33
  
  [libx264 @ 0x161eec0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX
  
  [libx264 @ 0x161eec0] constant rate-factor is incompatible with 2pass.
  
  Output #0, mp4, to '/tmp/1420389438-54a96c3eda8c1.mp4':
  
    Metadata:
  
      major_brand     : mp42
  
      minor_version   : 0
  
      compatible_brands: mp42mp41
  
      Stream #0:0(eng): Video: h264, yuv420p, 720x480 [SAR 40:33 DAR 20:11], q=-1--1, pass 2, 90k tbn, 29.97 tbc
  
      Metadata:
  
        creation_time   : 2013-09-12 17:30:22
  
        handler_name    : Mainconcept MP4 Video Media Handler
  
      Stream #0:1(eng): Audio: none, 48000 Hz, stereo, fltp, 128 kb/s
  
      Metadata:
  
        creation_time   : 2013-09-12 17:30:22
  
        handler_name    : Mainconcept MP4 Sound Media Handler
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (h264 -> libx264)
  
    Stream #0:1 -> #0:1 (aac -> aac)
  
  Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height

  When I save a node and add its corresponding video, the module generates the 3 files with their respective formats. But when thrown at the JW Player module, only plays FLV in every browser.
  But not the MP4 or WebM.

  I checked the log and status report and all I get in order.

  So I assume that the MP4 and WebM formats generated are not what the JW Player waiting.

  Does anyone have the solution to this problem ? I tried to recompile FFMPEG with more codecs but it does not solve the problem.

  This is my FFMPEG Configuration :

  ffmpeg version 1.2.6-1~trusty1 Copyright (c) 2000-2014 the FFmpeg developers
  
    built on Apr 26 2014 18:52:58 with gcc 4.8 (Ubuntu 4.8.2-19ubuntu1)
  
    configuration: --arch=amd64 --disable-stripping --enable-avresample --enable-pthreads --enable-runtime-cpudetect --extra-version='7:1.2.6-1~trusty1' --libdir=/usr/lib/x86_64-linux-gnu --prefix=/usr --enable-bzlib --enable-libdc1394 --enable-libfreetype --enable-frei0r --enable-gnutls --enable-libgsm --enable-libmp3lame --enable-librtmp --enable-libopencv --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-vaapi --enable-vdpau --enable-libvorbis --enable-libvpx --enable-zlib --enable-gpl --enable-postproc --enable-libcdio --enable-x11grab --enable-libx264 --shlibdir=/usr/lib/x86_64-linux-gnu --enable-shared --disable-static

• Dreamcast SD Adapter and DreamShell

  31 décembre 2014, par Multimedia Mike — Sega Dreamcast

  Nope ! I’m never going to let go of the Sega Dreamcast hacking. When I was playing around with Dreamcast hacking early last year, I became aware that there is such a thing as an SD card adapter for the DC that plugs into the port normally reserved for the odd DC link cable. Of course I wanted to see what I could do with it.

  The primary software that leverages the DC SD adapter is called DreamShell. Working with this adapter and the software requires some skill and guesswork. Searching for these topics tends to turn up results from various forums where people are trying to cargo-cult their way to solutions. I have a strange feeling that this post might become the unofficial English-language documentation on the matter.

  Use Cases
  What can you do with this thing ? Undoubtedly, the primary use is for backing up (ripping) the contents of GD-ROMs (the custom optical format used for the DC) and playing those backed up (ripped) copies. Presumably, users of this device leverage the latter use case more than the former, i.e., download ripped games, load them on the SD card, and launch them using DreamShell.

  However, there are other uses such as multimedia playback, system exploration, BIOS reprogramming, high-level programming, and probably a few other things I haven’t figured out yet.

  Delivery
  I put in an order via the dc-sd.com website and in about 2 short months, the item arrived from China. This marked my third lifetime delivery from China and curiously, all 3 of the shipments have pertained to the Sega Dreamcast.

  
  

  

  Click for larger image

  
  

  I thought it was very interesting that this adapter came in such complete packaging. The text is all in Chinese, though the back states “Windows 98 / ME / 2000 / XP, Mac OS 9.1, LINUX2.4”. That’s what tipped me off that they must have just cannibalized some old USB SD card readers and packaging in order to create these. Closer inspection of the internals through the translucent pink case confirms this.

  Usage
  According to its change log, DreamShell has been around for a long time with version 1.0.0 released in February of 2004. The current version is 4.0.0 RC3. There are several downloads available :

  1. DreamShell 4.0 RC 3 CDI Image
  2. DreamShell 4.0 RC 3 + Boot Loader
  3. DreamShell 4.0 RC 3 + Core CDI image

  Option #2 worked for me. It contains a CDI disc image and the DreamShell files in a directory named DS/.

  Burn the CDI to a CD-R in the normal way you would burn a bootable Dreamcast disc from a CDI image. This is open-ended and left as an exercise to the reader, since there are many procedures depending on platform. On Linux, I used a small script I found once called burncdi-dc.sh.

  Then, copy the contents of the DS/ folder to an SD card. As for filesystem, FAT16 and FAT32 are both known to work. The files in DS/ should land in the root of the SD card ; the folder DS/ should not be in the root.

  Plug the SD card into the DC SD adapter and plug the adapter in the link cable port on the back of the Dreamcast. Then, boot the disc. If it works, you will see this minor corruption of the usual Sega licensing screen :

  
  
  

  Then, there will be a brief white-on-black text screen that explains the booting process :
  

  
  
  

  Then, there will be the main DreamShell logo :

  
  
  

  Finally, you will land on the DreamShell main desktop :

  
  
  

  Skepticism
  At first, I was supremely skeptical of the idea that this SD adapter could perform speedily enough to play games reasonably. This was predicated on the observation that my DC coder’s cable that I used to use for homebrew development could not transfer faster than 115200 bits/second, amounting to about 11 kbytes/sec. I assumed that this was a fundamental limitation of the link port.

  In fact, I ripped a few of my Dreamcast discs over a decade ago and still have those rips lying around. So I copied the ISO image of Resident Evil : Code Veronica — the game I personally played most on the DC — to the SD card (anywhere works) and used the “ISO loader” icon seen on the desktop above to launch the game.

  It works :

  
  
  

  The opening FMV plays at full speed. Everything loads as fast as I remember. I was quite surprised.

  Digression : My assumptions about serial speeds have often been mistaken. 10 years ago, I heard stories about how we would soon be able to watch streaming video on our cell phones. I scoffed because I thought the 56K limitation of dialup modems was some sort of fundamental speed-of-light type of limitation for telephony bandwidth, wired or wireless.

  The desktop menu also includes a ‘speedtest’ tool that profiles the write and read performance of your preferred storage medium. For my fastest SD card (a PNY 2 GB card) :

  
  
  

  This is probably more representative of the true adapter bandwidth as reading and writing is a good deal faster through more modern interfaces on PC and Mac with this same card.

  Look at the other options on the speedtest console. Hard drive ? Apparently, it’s possible, but it requires a good deal more hardware hacking than just purchasing this SD adapter.

  Ripping
  As you can see from the Resident Evil screenshot, playing games works quite nicely. How about ripping ? I’m pleased to say that DreamShell has a beautiful ripping interface :

  
  
  

  Enter a name for the disc (or read the disc label), select the storage medium, and let it, well, rip. It indicates which track it’s working on and the Sega logo acts as a progress bar, shading blue as the track rip progresses.

  I’m finally, efficiently, archiving that collection of Sega Dreamcast demo discs ; I’m hoping they’ll eventually find a home at the Internet Archive. How is overall ripping performance ? Usually about 38-40 minutes to rip a full 900-1000 MB. That certainly beats the 27-28 hours that were required when I performed the ripping at 11 kbytes/sec via the DC coders cable.

  All is well until I get a sector reading error :

  
  
  

  That’s when it can come in handy to have 3 DC consoles (see ?! not crazy !).

  Other Uses
  There’s a file explorer. You can browse the filesystem of the SD card, visual memory unit, or the CD portion of the GD-ROM (would be more useful if it accessed the GD area). There are FFmpeg files included. So I threw a random Cinepak file and random MPEG-1 file at it to see what happens. MPEG-1 didn’t do anything, but this Cinepak file from some Sierra game played handily :

  
  
  

  If you must enter strings, it helps to have a Dreamcast keyboard (which I do). Failing that, here’s a glimpse of the onscreen keyboard that DreamShell equips :

  
  
  

  Learning to use it is a game in itself.

  There is an option of installing DreamShell in the BIOS. I did not attempt this. I don’t know if it’s possible (not like there’s a lot of documentation)– perhaps a custom BIOS modchip is needed. But here’s what the screen looks like :

  
  
  

  There is also a plain console to interact with (better have a physical keyboard). There are numerous file manipulation commands and custom system interaction commands. I see one interesting command called ‘addr’ that looks useful for dumping memory regions to a file.

  A Lua language interpreter is also built in. I would love to play with this if I could ascertain whether DreamShell provided Dreamcast-specific APIs.

  Tips And Troubleshooting
  I have 3 Dreamcast consoles, affectionately named Terran, Protoss, and Zerg after the StarCraft II stickers with which they are adorned. Some seem to work better than others. Protoss seemed to be able to boot the DreamShell disc more reliably than the others. However, I was alarmed when it couldn’t boot one morning when it was churning the previous day.

  I think the problem is that it was just cold. That seemed to be the issue. I put in a normal GD-ROM and let it warm up on that disc for awhile and then DreamShell booted fine. So that’s my piece of cargo-culting troubleshooting advice.