Recherche avancée

Sur d’autres sites (4836)

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

• FFMpeg copy stream SEI type 162 error

  13 juillet 2015, par Vishal Shah

  I am using FFMpeg to copy an RTSP stream to an RTMP stream. Both of which are network streams. This is the command I am using.

  ffmpeg -re -i rtsp ://url.to/rtsp/stream -c copy -f flv rtmp ://target.rtmp/uri/stream

  I am receiving data on the youtube live control room. But After a point I get an error like this in my FFMpeg console and then the data transfer on youtube live stops.

  SEI type 162 size 1496 truncated at 1280

  Can someone throw light on what this error means and how to resolve it ?

  Note that the RTSP stream is over the network

• Getting ffserver && ffmpeg to work of Debian with Logitech C270 [closed]

  14 mars 2013, par Joseph Baldwin Roberts

  I'm having real trouble getting my webcam to work and I wonder if anyone can help. Im running Raspian on a raspberry pi.

  When I run lsusb I get :

  pi@raspberrycar ~ $ lsusb
  
  Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
  
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  
  Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
  
  Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
  
  Bus 001 Device 005: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter
  
  Bus 001 Device 006: ID 046d:0825 Logitech, Inc. Webcam C270

  When I run v412-ctl —all I get :

  pi@raspberrycar ~ $ v4l2-ctl --all
  
  Driver Info (not using libv4l2):
  
          Driver name   : uvcvideo
  
          Card type     : UVC Camera (046d:0825)
  
          Bus info      : usb-bcm2708_usb-1.2.4
  
          Driver version: 3.6.11
  
          Capabilities  : 0x04000001
  
                  Video Capture
  
                  Streaming
  
  Format Video Capture:
  
          Width/Height  : 640/480
  
          Pixel Format  : 'YUYV'
  
          Field         : None
  
          Bytes per Line: 1280
  
          Size Image    : 614400
  
          Colorspace    : SRGB
  
  Crop Capability Video Capture:
  
          Bounds      : Left 0, Top 0, Width 640, Height 480
  
          Default     : Left 0, Top 0, Width 640, Height 480
  
          Pixel Aspect: 1/1
  
  Video input : 0 (Camera 1: ok)
  
  Streaming Parameters Video Capture:
  
          Capabilities     : timeperframe
  
          Frames per second: 5.000 (5/1)
  
          Read buffers     : 0

  When I run v412-ctl —list-formats I get :

  pi@raspberrycar ~ $ v4l2-ctl --list-formats
  
  ioctl: VIDIOC_ENUM_FMT
  
          Index       : 0
  
          Type        : Video Capture
  
          Pixel Format: 'YUYV'
  
          Name        : YUV 4:2:2 (YUYV)
  
  
  
          Index       : 1
  
          Type        : Video Capture
  
          Pixel Format: 'MJPG' (compressed)
  
          Name        : MJPEG

  My ffserver settings file is /etc/ffserver.conf

  Port 80
  
  BindAddress 0.0.0.0
  
  MaxClients 10
  
  MaxBandwidth 50000
  
  NoDaemon
  
  
  
  <feed>
  
  file /tmp/webcam.ffm
  
  FileMaxSize 10M
  
  </feed>
  
  
  
  <stream>
  
  Feed webcam.ffm
  
  Format mpeg
  
  VideoSize 640x480
  
  VideoFrameRate 10
  
  VideoBitRate 2000
  
  VideoQMin 1
  
  VideoQMax 10
  
  </stream>
  
  
  
  <stream>
  
  Format status
  
  
  
  ACL allow 192.168.2.0 192.168.2.255
  
  </stream>

  My ffmpeg run string is /usr/sbin/webcam.sh

  ffserver -f /etc/ffserver.conf & ffmpeg -v verbose -r 5 -s 640x480 -f video4linux2 -i /dev/video0 http://localhost/webcam.ffm

  When I run this is the output :

  pi@raspberrycar ~ $ sudo /usr/sbin/webcam.sh
  
  ffmpeg version 1.0.5ffserver version 1.0.5 Copyright (c) 2000-2012 the FFmpeg developers
  
    built on Mar 14 2013 18:37:40 with gcc 4.6 (Debian 4.6.3-14+rpi1)
  
   Copyright (c) 2000-2012 the FFmpeg developers
  
    built on Mar 14 2013 18:37:40 with gcc 4.6 (Debian 4.6.3-14+rpi1)
  
    configuration:
  
    libavutil      51. 73.101 / 51. 73.101
  
    configuration:
  
    libavutil      51. 73.101 / 51. 73.101
  
    libavcodec     54. 59.100 / 54. 59.100
  
    libavformat    54. 29.104 / 54. 29.104
  
    libavdevice    54.  2.101 / 54.  2.101
  
    libavfilter     3. 17.100 /  3. 17.100
  
    libswscale      2.  1.101 /  2.  1.101
  
    libavcodec     54. 59.100 / 54. 59.100
  
    libavformat    54. 29.104 / 54. 29.104
  
    libavdevice    54.  2.101 / 54.  2.101
  
    libavfilter     3. 17.100 /  3. 17.100
  
    libswscale      2.  1.101 /  2.  1.101
  
    libswresample   0. 15.100 /  0. 15.100
  
    libswresample   0. 15.100 /  0. 15.100
  
  [video4linux2,v4l2 @ 0xfa5620] [3]Capabilities: 4000001

  I can see the stream on the status page and my webcam light is on but it never loads. Does anyone know what I am doing wrong ?

  Thanks in advance

  Joe