Just a quick insert to say that my USB MIDI module now supports MIDI device insertion, and other stuff. It has also been tested on both the Raspberry Pi and the Beagle xM; with both the Roland E-16 and the Yamaha PSR e-333.
It is still alpha, it has not had much in the way of solid testing, however with the test programs supplied and !Maestro, it does work as expected.
The module does not support multiple MIDI devices at this time (it's a big job to insert that), however otherwise, it should (hopefully) provide the documented API. There are likely to be bugs and minor updates, but this is what I wanted to finish this summer holiday. So here it is. I just hope there are people with an interest in MIDI music who will use it and provide me with feedback!
API/documentation PDF (to save reading that OCR'd one from the Acorn era on ChrisWhy's site). The documentation differs, I wrote this one myself, but the API (except for USB extensions) is the same.
Things to Do with a Pi in France when you're Bored.
The title about sums it up.
The reality? That's the NOOBS package from the RaspberryPi site.
Frankly, it couldn't have been simpler. The NOOBS file was a 1.1GB archive that I needed to download, then simply decompress on to a fresh (shop-new) SD card of at least 4GB size. It would appear that the Pi is the exact opposite to the Beagle in terms of booting from its media (recall - the Beagle is reported to sulk if the "MLO" file isn't the first thing written to the boot partition). But to say "dump this stuff here and then plug it in", really, I'm surprised people are actually selling these SD cards premade, it can't get simpler than that!
Upon starting up, the Pi enters a sort of windowing environment. Actually, for me it does nothing so I need to press '
2' (selects HDMI safe mode, does nothing!) and then '
1' (selects preferred HDMI mode, read from EDID). Then something appears on the screen. But fret not, that's an issue with the HDMI to VGA adaptor, not NOOBS itself.
There are several Linuxes (Linuxen? Linixii?) listed, with RISC OS at the bottom. The recommended distro was "Raspbian", so I installed that.
Installation was dead easy. No complicated questions, no piles of questions to answer. It basically unpacked a prebuilt image and dumped it on to the free part of the SD card and screwed around with the partitioning so it all "just worked". Damn, this is how operating systems ought to be installed.
I looked at stuff like this for a while...
...and then it was done and Raspbian booted.
Again, no display. Ho ho. So I rebooted my Pi and held
Shift as it started up. That's the secret keypress to drop into the installer instead of the chosen operating system. I saw an option to edit the Config files, so I opened the "config.txt" and pasted in the commands necessary to drive the monitor to 1280×1024. Then I restarted Raspbian again, this time it worked.
I'll be honest here. It was unexciting. I mean, what's the deal with an operating system that appeared to offer two versions of Perl, three web browsers, and nothing that resembled an office productivity suite of any sort? This was not something I felt could be used "out of the box". Perhaps I could get a lot of stuff from the Internet, but my Pi is not connected, and I wasn't sure what I could do with Raspbian.
I did have some fun playing around with Scratch. This simple "programming language" which would be great for introducing children to what programming is and how it works. Programs are created by simply dragging elements and 'clipping' them to what is already there.
I liken this to a 21st century version of the LOGO Turtle.
Given that there didn't seem to be much else to do with Raspbian, I rebooted the Pi with
Shift held down, and picked something else.
It is worth pointing out that the NOOBS package is intended for 'testing' the various options available. Installing one of those options will destroy anything that was previously there. If you create files in the various operating systems offered, these files would be best copied to a USB device so they aren't lost if you decide to try something new. Your settings and such, unfortunately, won't persist.
That something else was RaspBMC. As before, I needed to reboot and poke the config.txt file for the correct monitor size, then the adaptor was happy.
RaspBMC loaded up with a red themed style designed for the Pi. It might have been good if it wasn't so horribly low-resolution and pixelated that it looked like my 17" monitor had turned into an old fashioned TV.
There was another 'skin' to pick, one called "Confluence", that was sort of blue bubbles and it looked a hundred times better.
My first test was a simple one. That snippet of "Kara no Kyōkai" that so utterly failed to play under RISC OS on the exact same hardware. This wasn't much of a test really, but certainly demonstrates the difference between trying to decode video in ARM code, and slinging it at the GPU instead. There's no way a 700MHz ARM (actually, RaspBMC upclocks the Pi to 800MKz) is going to decode XviD in realtime. The Beagle xM (1GHz) can't do it fluidly. This is one of the lamentable things about these SoCs and RISC OS - there are no cool video drivers. RISC OS ought to be capable, the hardware is certainly capable, but the manufacturers are sufficiently paranoid about their GPUs and such that the video drivers are a binary blob, not source. So the only way to get that working with RISC OS is likely something that can load Linux kernel modules and 'fake' a Linux-like environment so RISC OS applications can call Linux code. Go back and read that sentence again and you'll understand why nobody has done it yet.
- Note - the following screenshots are that in the most literal sense... photos of the screen.
Test two was "Red Data Girl" in 720p HD. With an overlay too, to demonstrate the Pi holding steady at 48-52°C. No, really:
The reason for the mocking attitude was that my eeePC, clocking 1.6GHz as standard (and 1.8GHz in mega-whoo mode) sometimes struggles with HD content. But, here, note the GPU temperature rose about two degrees (as opposed to 15-20 for the PC) and the CPU usage is barely even registering... while displaying an overlay over top of video that is playing.
I then thought I'd try a 1080p FullHD video. I saw mostly a black screen, with this every so often. Sound played okay.
I believe the problem to be the HDMI to VGA adaptor not liking whatever settings are in use for the FullHD playback. I needed to reboot to get out of this mess. I also believe, going by the flawless sound, that 1080p FullHD playback is possible on the Pi.
Which is really quite incredible.
So I stepped back to a 720p version of the same file. No problems whatsoever. Completely fluid.
And another 720p file, this time displaying an srt formatted subtitle file that I created:
Again, completely fluid. I should add that there is no obvious way to 'attach' a subtitle file to a video. It will, however, pick up and auto-display subtitles if the video and subtitle have the same leafname (in other words, meh.mp4 and meh.srt).
I tried a number of different files, and that all seemed to work fine. In fact, the only two types I think do not work is MPEG2 and VC1 which require a licence from Broadcom to unlock the functionality in the GPU. It's such a ridiculously low price that you wonder why they bother - and who uses MPEG2 these days when you can easily transcode to XviD or H.264 at a fraction of the filesize for similar quality. I suppose it might be an issue to you if you rip DVDs to VOB files, but if you rip to something more modern, no problems.
The RaspBMC interface is simple, clear, and has been dumbed down sufficiently that there's not a lot you can do other than play videos and music. In this respect, it does its job admirably. While I am running this off the NOOBS package, I don't really have much inclination to try any of the other options. The Pi has suddenly become like a hundred times more useful.
By way of comparison, I saw this in a supermarket the other day:
The recommended retail price on iomega's site is €129.
Let's see what it offers (copied from product info page), and compare:
So. A hundred euros for a fancy box that does it all? Or less than half that to roll your own and have a useable computer as well (the Pi runs several flavours of Linux as well as RISC OS). Take your pick!
- Video CODECs: H.264; WMV; RMVB (SD), MPEG-1/2/4 (part 2, ASP), VC1, DivX®, DivX Plus™ HD (NKV), Xvid
MPEG2/VC1 needs a dirt cheap licence. I've tested it with H.264, DivX, and XviD. The others? Don't know. I would imagine "most likely".
- Video File types: .avi, .asf, .iso, .vob, .mp4, .flv, .mov, WMV, FLV, .mkv, AVCHD, M2TS
I can vouch for AVI, FLV, MKV and MP4. The rest? As above, "most likely".
- Photos: JPEG, BMP, GIF, TIFF, PNG
No reason to suspect these won't work, they're pretty standard. Tested with a few JPEGs.
- Wireless Ready: Supports Iomega USB Wi-Fi adapters for wireless access up to 802.11b/g/n
Didn't test (can't remember where my WiFi dongle is!) but as far as I know RaspBMC supports WiFi and AirPlay out of the box.
- Audio: MP3, WAV, WMA, OGG, AAC, AC3, PCM, M4A, DTS
Tested with MP3; and video with AAC audio. The others? Fairly standard, ought to work.
- Playlists: PLS, M3U, WPL
It can make M3U playlists, but I found the playlist (for videos) to be a bit klutzy so I didn't play with it much.
- Subtitle: SRT, SSA, SUB, SMI
Tested with stand-alone SRT and MKV-embedded SSA.
- Connections: HDMI, Ethernet, Composite Video, Optical Audio, USB 2.0
HDMI, Ethernet, composite video, USB2, electrical audio. The iomega box might score a win for having optical audio, but what happens if you have a simpler setup with composite video and you want somewhere to plug your 3.5mm audio jack?
- Playback Resolution: Up to 1080p High-Definition (60fps)
FullHD didn't work for me for technical reasons. It apparently does work. For me? 720p looked great on my 1280×1024 display (which is the width of 720p anyway). RaspBMC was smart enough to realise the display is 4:3 and letterbox the widescreen content and place subtitles below in the black part instead of on top of the video.
- External HDD Formats: NTFS (default), HFS+, FAT32, Ext2, Ext3
Don't see why these wouldn't work - doesn't Debian support them? I tested with an SD card formatted FAT32.
Now, seriously... If you have a Pi and wish to play media files - you can't go wrong with RaspBMC. Hell, it's almost good enough to justify buying a Pi and taping it to the back of your TV!
Please note that while I check this page every so often, I am not able to control what users write; therefore I disclaim all liability for unpleasant and/or infringing and/or defamatory material. Undesired content will be removed as soon as it is noticed. By leaving a comment, you agree not to post material that is illegal or in bad taste, and you should be aware that the time and your IP address are both recorded, should it be necessary to find out who you are. Oh, and don't bother trying to inline HTML. I'm not that stupid! ☺
You can now follow comment additions with the comment RSS feed. This is distinct from the b.log RSS feed, so you can subscribe to one or both as you wish.
|Zerosquare, 17th August 2013, 12:53|
"the only way to get that working with RISC OS is likely something that can load Linux kernel modules and 'fake' a Linux-like environment so RISC OS applications can call Linux code. Go back and read that sentence again and you'll understand why nobody has done it yet." -> this isn't as far-fetched as it sounds; for example : http://en.wikipedia.org/wiki/NDISwrapper
|« August 2013 »|
| || || ||1||2||3||4|
Japanese Red Cross
Earthquake relief donations have closed.
Read about the JRC
Make a general donation
List all b.log entries
Return to the site index
PS: Don't try to be clever.
It's a simple substring match.
Last read at 03:30 on 2019/01/19.
© 2013 Rick Murray
This web page is licenced for your personal, private, non-commercial use only. No automated processing by advertising systems is permitted.
RIPA notice: No consent is given for interception of page transmission.