 Ychydig, dyna i'w ddweud y ddweud o 64 Studio ar y cyfnod. Ac mae'r cyfnod yma. Rydyn ni'n ddweud y ddweud o 64 Studio ar y cyfnod. Rydyn ni'n ddweud y ddweud y ddweud o 64 Studio ar y cyfnod. Er yna y pethau'r ysgolwch yn y project a'r ddweud o'r ddweud o'r ddweud o'r oedd y ddweud o'r oed. Felly, we actually do some type of software and publishing software, the main office is so vast and has been on the audience for a long time, so the 64 studio is a custom debut and distribution. It's a one disk install, the 1.0 version, which came out the awesome last year was a single CD ROM, The 2.0 version, which will be out since later this summer, is a DVD, but it's just a one-disc stick-it-in reboot. It precedes most of the installable questions that you can only get with Debian, which has been a part of our annual link-in easier for non-tabical users because a lot of people who want to use their computers in a crazy point are not particularly technical. They know the applications that they do everyday inside out, but IT in general is not their area. So we took the decision to design it for stability rather than to be on the bleeding edge the whole time. So not all the packages will be the very latest, necessarily, but they will have at least gone through some quality assurance testing over at least a month or so to make sure we don't put out a number to release that's got lots of, you know, short stuff that's crushing by deciding to find the thing. Our ultimate aim is to go beyond stability and to achieve reliability. In other words, the machine not only doesn't crash, but you can rely on it to do its job everyday. You know, when you hit record, you expect the audio to actually be on there, but it's not always the case with computers, of course. So we want to go beyond just crushing bugs and achieve that sort of level of reliability. Basically, we're looking to make a correct desktop that is as good as a deviant server is in its role. You know, you can leave it behind for a couple of years, you can come back and it'll still be running, and you don't have to deal with the machine sliding down or giving it some corrected in the way that Windows machines tend to do in explaining them over long periods of time. Because a lot of these creative users who are targeting, they don't want to be uploading new packages every day, but we're down with the new packages in there. Upgrading every few months, you know, they want to install a machine or have it still for them and probably never trust the software side of things until they get a new machine. So we try and automate everything as much as possible. And the final point on the slide is that the distro is absolutely free as in there. The nearest equivalent to 64 Studio again is probably Adobe itself Creative Suite, which is, you know, graphics publishing, audio, video tools. And that runs into, I think it's a couple of thousand pounds for the full version, you know, with everything in it per seat. And obviously that makes it very difficult to afford for a lot of people in the creative industries of freelancers. They don't have a lot of money on the starting hours, a lot of students, a lot of people who have the technology and will to use their computers creatively. But the high cost of proprietary applications is a barrier to entry. And it's fair to say that hardware has come down in price a great deal over the last 10, 15 years. But the proprietary applications in the creative sphere haven't followed students who are still just as expensive as they were back in the digital play teams. You know, given like a desktop launching application, it can be around 100 pounds per seat, not like that. And so students and free ones, people like that, don't get access to all the tools they can actually use. Particularly in education, what that means is you get colleges and schools spending a great deal of money on proprietary software investing in it, effectively. But they are still not able to put that full set of creative tools in front of the student or people, which is unfortunate. If you really default and install Windows XP or something like that, it doesn't have a great deal of creative tools on board. The one that has a printed board, so we think we've got something to offer from there. So, what is 6-2-1-2-0? It's not fork. It's actually freshly built on a continuous basis for the dead-end sources. We actually fixed bugs in the dead-end itself rather than the 10-2-3-3. So, our lead developer for Ian Van Iker is a DD, and he's on multimedia, and he's quite fixing bugs in dead-end packages every day. And then what we do is, all we want to make a release, we take a snapshot, or in the case of our forthcoming 2.0 release, it will be edge-based as a development release platform. And so we're fixing bugs directly in dead-end and rather than creating something separate from dead-end. We don't strip out dead-end logos or trademarks or any of that kind of stuff. We put CD in it so it's welcome to dead-end and hit F1 or enter to the school world. So, there are a lot of derivative distributions that strip out the D-word, the sort of logo from the whole thing to give the impression that they're creating something other than dead-end or super-end. It's not what we know, the right trademarks. We don't do anything like that. So, another point, it's not just a platform for non-free apps, because I was giving a talk in Los Angeles. Where there are approximately 5,000 artists using GNU slash Linux on a daily basis in that city. And we're working mostly for the movie studios and the TV production, that kind of thing. But the vast majority are using almost exclusively proprietary applications on the Linux space. So, we've got maybe retail enterprise, whatever, and then we've got MIA or Nuke, or one of those kind of applications, which is some of them are proprietary for the small specialist proprietary software houses. Others are in-house apps that have been developed by some of the movie studios through the rules here about using Linux. And they never actually get released to the public until, you know, proprietary or for example. So, when we decided to create this digital like two years ago, it was important just to have full roster of free software applications running on free software platforms. So, it's not just a free software leading to people walking out of these proprietary apps. So, it's not just about music software. That seems to have been the main emphasis so far. I think that's partly because the stock distros don't have a great deal of music software on that. And they don't usually have things like a real-time kernel and check all your server and so on. So, if you're looking to make music with free software, there's more reasons for using a specialist distro for music and audio. Like, for example, if you're doing graphics, then you can get packages for Inkscape, DMC, and Blender and user app from most mainstream distros without having to do too much systems with them. And, yeah, hopefully, as we were saying, the creative user base is not necessarily very IT literate and, say, probably never used it before, and they've used it on a web server or something, but never actually used it on a desktop. So, we're trying to make it as easy as possible. We're going to use it for the next seven or eight years. So, you plug in a digital camera and, you know, through Gbuzz, you get a G-thumb watch to import your photos. And it's all in that sort of ease of use. I've actually tried a few OS X or OS X systems and found, you know, the thing these have used has actually found me quite confusing and difficult to go to Bristol. I used to use them quite ten years ago, and the way that OS X does its menus and applications and launching where to find your files, I didn't actually find that intuitive at all. And so I think there's still some work to be done there to actually achieve a sort of, you know, golden standard of usability, but I don't think that will actually happen to themselves. One of the things we do, for example, is we changed the known default configuration around a little bit, so that instead of having the menu at the top, we put it at the bottom. Now, the top menu is obviously the known default that's what it went to use as an edge, but we actually looked at what people were used to and, you know, maybe 95% of the user base is used to having the... The start menu in the bottom left hand corner happens to just a, you know, thing on the icon that comes with dead straight forward display applications and you can find the one you want in the category and click on it. And that's how most people, having come up through Windows 95 and 98 XP, expect them to just do that. So that's how we did it. So, who are we? FreeEconarca is the statistical leader of the project. He's originally from Italy, but he's actually living in Berlin in London. Tim Hall is the documentation guy. He's a musician, a background that has come into free software through the Muni project. And, you know, so he puts the... he asks us to view some manuals and things like that. Because I'm sort of the project founder, company director, I get to do the dummy user testing. So I, you know, I get a good result. That doesn't work when I make an edge, you know. You know, put a ticket on the website. You know, we've generated like 300,000 something tickets, I think, since we started. We've chained through quite a few of those. We've got fixes for most of them. I'm obviously going to do paperwork. So, you know, I think we're going to go on a deal, aren't we? Thank you. We have lots of people helping us in our music community. User district development community. Some people are just, you know, you know, trying this in the room in the store room. Other people are saying things like, oh, well, I found this problem. And here's a fix, which is great, you know, because we're getting that active involvement. And a couple of the projects that we package for the district, actually some of our users have gone on to become maintainers or co-maintainers, the first packages of packages, which have, you know, got un-maintained for whatever reason. To give an example, and slightly less obvious, there's a package in Nome for Tracking Times that are projects called Cnome Time. And it's not shipped by default with a lot of district. There's some slightly less, you know, obvious package. That's sort of not completely un-maintained, but, you know, development has slowed down a bit. And one of our users said, because he lives in South Africa, and they have, you know, the round of the currency, he said, well, you know, I'm a freelancer and I need to use Nome Time to generate invoices. So he noticed that the invoice-generating feature of that is actually quite handy if you're a freelancer has the dollar sign by hard coded in the invoice-generating code. So he actually worked up a patch to change that to a user of a settable currency symbol. But that's only a small change, but it makes that program now extremely useful for, you know, for the kind of people that we're talking to, many of whom are freelancers and need to track their project time and generate them in invoices. And that's a less obvious example, because it's not a multimedia application as such, but it's the kind of application that, once you get into it, it's so useful that you can't do without it. So you don't need, like, a full accounting system if you're one of our type of users necessarily. You just need to be able to track your project time in invoices and so on. So we're trying to think of the whole sort of a gishtout to fucking use that word of, you know, the creative new user. That's two, one German word, one French word. So anyway, how do we fund it? Well, we are a broad company, not for profit, sort of pure community project. And we've got a custom work offering that we have, and we've, you know, using the sort of platform that we've developed, building on that for various types of projects. Later in this year, we're going to be doing end-user support as well. So I guess people are actually coming in just saying, you know, I really want someone to be able to, like, answer my questions and so on. Because community support is great, but my questions are so dumb, you know, that nobody could be bothered to answer them all. My questions are, you know, people with the strangest hardware combination, you know, that nobody else has got. We need somebody to spend like three days on the work. That's, you know, community support has so many advantages, but it doesn't suit all people in all situations. And there are other people, like institutional users, you know, like ecologists at large times, where they feel better, you know, if they can have some, like, some paid support. And there are very few places where you can go at the moment for multimedia desktop support. You can get support from a bunch of them for your, you know, red hat or enterprise and so on. But there aren't any, sort of, any small, large media companies that are providing support services for the kind of software that we're doing. So we're also thinking about, seriously, about having any hardware-type website because you're going to, like, a PC world store or something like that. You know, is this, like, supported by getting an actual... I don't know. I don't even know if it's supported by Windows Vista, you know. You know, it's just, it's a frustrating experience trying to actually buy things, you know, buy a laptop with David and I or buy, you know, a piece of hardware like this. You know, you can go to an audio and make these USB audio interfaces and say, like, oh, doesn't that work with Linux? And they go, oh, yeah, yeah, it definitely works with Linux. There's some guy who did a driver somewhere, but, you know, they can't tell you about, like, kernel versions and outside versions or anything like that. They just know that there's Linux support for that or maybe if you use the right revision, you know, off the phone there and what do you like. So we're thinking about a website where we have things like this and you can just click on it by and you know that it definitely works with Debbie, that we've personally tested it. I don't know if it's useful or not, but I think I'll be happy to use it. So, the project's really where we're going. This is late in 2005 when we started on this one. This is the line-stracted media station. It's a very large workstation keyboard. It was the first instrument that was coming to be publicly launched as running Linux. Actually called Oasis, which is the sort of called one of the worldwide brand leaders in the system. They now also help doing Linux-based keyboard called the Oasis that's O-A-S-Y-S. But this was actually the first. Originally it ran, it approached that around Red Hat Linux 9, I think. It was going back about 3-4 years. The company switched to a stock Debbie in the store and so on. But the problem with making a dispara fit on it to an instrument like this, which is obviously not a standard PC. It has a PC motherboard inside it and it has a PC CPU, the artist and so on, but actually the PC's got a small touchscreen in the centre there and it's doing a full-size monitor. Obviously it's not a quality keyboard. So it's not altogether like a PC. So most companies in the road, there's another one that's worked at the Hartman Neuron which is also a new Linux base. So there's quite a few of these big sets now when you actually have a free software called. Now, the standard approach to this is to take a standard history like Debbie or Gen 2 or whatever and stick it on the machine and then get all your special apps you need for running the keyboard or the touchscreen or whatever, package them up with a giant marble. Then when it comes to installing the machine, stick on your distro, unpack your giant marble and versure up the software. So you run a couple of scripts and you overwrite all the defaults. The problem with that is when you've created essentially a fork because it's like a sort of a Debbie or Gen 2 version of whatever it is frozen in time at that point and then you've got a choice. You can update the underlying distro in which case the stuff that's in the table is probably going to break or you can leave the distro as it is and what you get is a horrendous thing out of date because as I say here when you buy one of these large expensive instruments you expect it to last for a great deal longer than PC's lifetime so PC's got 3 year lifespan laptop in 2 years of doing it because it will break in half but if you buy one of these instruments they are quite expensive and you might expect it to last as long as you're having an organ or you'll send you more back in the 80s so 10, 20, even 30 years is not uncommon. So the answer we came up with is to have a sort of a rolling platform that we keep maintaining for the distro and actually keep it up to date and package everything in depth so that what you've got is a custom delivery distribution that's tailored for this specific device it's not a it's not a fork but it's part of the tree mark of our main distro that was in some special settings because it was in a standard procedure and that seems to work quite well you end up with something that's pretty up to date with current distros whether it be adshore or whatever whatever it's based on and actually because you've got a new build being generated all the time and watching the breakages and things like that because the alternative if you free that distro in time nobody wants to buy backport stuff to a distro that's like 10 years old or it just wouldn't happen and so when we take a deviant a bit better on this instrument so that was more or less done now we've included that where late last year the small working at the moment it's about this is actually an 18 inch screen so the whole device is sort of that size I mean half the size of a laptop on average it's the first portable digital audio workstation for sure that is as far as we know it was running for itself and it's also the first sort of portable device that's optimized for audio so for example you get a standard laptop it has like an eighth of an inch mini jack with a pretty poor audio chip so on it because that's one of the things about a laptop manufacturer is cut costs on it so you end up having to buy an external box like this to actually get a proper microphone input so all this thing is a small one hopefully lighter not a battery life on the laptop and it actually has these kind of XLR sockets that will finish the panel so a proper microphone and the idea being that it's some smaller overall and more compact you don't have to have all these different wires that we've got going on here today to actually use it the idea being that if you're on a plane or something you can actually work on your project it's got no quality keyboard of course it's got a thumb pad on the right hand side and two mouse buttons on the left so you're actually holding it a bit like you would a small games console but you've got your headphone output and there's a back which you can't see there's the microphone inputs and the line outputs and the idea behind this is that you're working on a project on a plane or that's where we happen to be and then it's got FNA on the back as well and Wi-Fi and you can connect to the internet and upload your finished project to your studio server or your streaming website or whatever it is so this one's another branch of the distro that's optimised for this and it's a one question about the update so if somebody buys this instrument and does it get every year a CD with the update or is it done by a network? network, okay, yeah I mean both the media station and the tragedy it's both got FNA and user have to activate it or is it normal that if there's a new update available the instrument will just download it and it's not pushed out to the moment you actually have to run a distro upgrade on this one and what we'll probably have in the final question is just an update button we actually have a script called 64 studio-upgrade which basically does all your act get a distro upgrade and all that kind of stuff and it also pulls in any because we have scripts to reset configurations back to the default state so it runs the backup so it's basically like a pocket sized studio with the power of deviant in it so that's enough talking I'll do some showing this is our 1.4.0 development race that's actually a close-up of Steve Harris' guitar Steve Harris is the author of Jammin and a lot of DFP effects under the Ladsberg but because there's an extreme close-up so superficially it looks pretty similar to the 1.0 release which we're running on the machine by the window down in the middle but we've updated a lot of packages since then I mean the 1.0 release last September we were running a 2.617 kernel which is okay for most machines unless they're very new in which case it doesn't have support for the latest Saturn chipset things like that and we've made various bug fixes and tweaks and package updates since then so this will be the basically the 2.0 release which will be added later so notable updates actually we've got Arda 2 which is GTK 2 based rather than GTK 1 came out not long ago and we've got that in there this is another U1 that's an orbit emulator but not like a sort of a home organ it's a full-sized church organ so you can actually assign like banks of mini keyboards and foot pedals and a whole lot so you can do the whole you know phantom of the opera thing with that it's you've got the only things you do need a lot of keyboards to work with but that is a very very good project it's all done in the known software it's not solved at all because there are some Linux based church organs there's one in the World Trade Centre in New York that replaced the original church organ that was destroyed with the attack on the on the September 11th with a Linux based sample organ which is basically like a rack of 10 machines all running like these really big disc samples of real church organs but this one is all completely on the CPU it's all generated rather than sampled and it sounds pretty good so we've got a lot of things that were in the previous release like AMS which is the multiple synth running in the back there and all the sort of popular things like audacity and so on some instrument tuners instrument tuner and freewheeling which is like a looping sound and other things and it's what we've got the DSSI oscilloscope which is another handy tool and a date opting in Terminator X and we've also updated a new version of Inkscape Screwlist so we have general updates but the biggest advantage of the 2.0 at least I think of the 1.0 is the 2.0 is edge based whereas the 1.0 is not based on snapshot testing for my last September so in terms of actual package compatibility you know it's 2.0 because you won't have much less chance of getting a broken package and we also have security support for the first time we're now based on a stable release rather than testing it when we started Sarge was already 2.0 in terms of package numbers package unit versions to base on so we went with the snapshot up to another edge base so we're now based on the 2.0 but since we're talking about music today is there anything you can not use Jack? OK, I'll give a quick introduction to Jack most audio applications today have the approach of revving the sound card or the audio interface for its exclusive use and a lot of music applications on the proprietary platforms work the same way and don't let any of the other application use it now the problem with that is if you're taking a more modular approach we have lots of different applications doing different things they can't all access the sound card at once so you can go for a sound server now there are a couple of different desktop sound servers there's ASD and the Enlightenment sound server and KDE as well but Jack is somewhat different it's designed specifically for real-time operation the difference being that if you're running a serious set of music applications like a half of a second latency will be a big deal you don't want one app to be out of time with the other if you're just running like desktop sounds and like flash plugin or something like that there's no big deal so Jack is built for hard or close to hard real-time work so I just click on start button this is not actually the Jack server this is like a control application for it which we call Jack control it's a QJack tool and you can pronounce that or something called a jigger anyway so I've just pressed start and it's showing me up here real-time mode so that's good this is showing me my sample rate which is like contact disc sample rate and this is my DSP load so system is not exactly taxed here down here and then my connections are done this is my output so I've got playback 1 and playback 2 on this which are corresponding to left and right in this case if I have a multi-channel interface and 8 outputs there if I was running in ffmj I would also have 8 inputs running over the river side so let's start with the first Jack application there's a the Jack audio master in the place it's starting slowly for some reasons but it will get there this is a a dedicated application for processing audio in real-time mastering called in the audio world in the TV film mode it's called post-production but it's mounted to the same thing what you're doing is you're taking an audio signal and you're tweaking it up to make it sound better to make it loud and usually to make it clearer and so it will work on a variety of different sound systems from your giant club sound system to tell you something about this so in the sort of proprietary domain there are various plugins that do this kind of job and what jammy does is it collects all those plugins together and puts them into a single GUI so you've got one window I'll demonstrate how you actually use it with the very high so we're going to open a session I made already and because William's got one a rather shambolic and hyper-fersion so so so if I go back to my jack connections right now I've now got all my different arder tracks we've got separate outputs we'll see what it's like here all basically some of them we're going out to this is where it gets complicated arder's master bus in there and there oh there it is there we go that is actually connected to oh no no it's connected to jammy isn't it it is game copyrighted we've got all the different tracks in arder they're playing into arder's master bus that is going into jammy and then we're rooting the output of jammy and back to the sound quality so what that enables us to do is master our track in real time there we go we've got it's not connected to jammy interesting oh it's not connected to jammy yeah it's directed to it was earlier never deployed I'm sure I have that down here okay so jammy's not connected to jammy's it's going on soon what is it what is it oh yeah because it goes blue so you can't see that on the projector it needs to be the RTO there so it's getting around just the complicated one but it should work so you should save those sessions on this you're right to do that you should have done that you can save it it's a configuration so windows should we mix them the workspace yes there is another hatch way you can set up routes and save them when you call actually I'm not sure so if I set this up right you should be able to save that is so important they have to make up their own reports that's what I'm saying it's just a play I'm responsible for it and it's really the wrong time to press the solo button there we go because each of these tracks has an insert point so if I it is too much but for example when a studio is mixing a track like this it will do all kinds of tricks for making compression to actually make the instruments stand out better because these days if you're making music with a live band you can't achieve the same volume and clarity as synth based bands or using samples to generate two sounds so mixing is all about tweaking up stuff to make it louder harder so that's the kind of trick that we would use to track them up we go back through the track and transport them up another EQ plug in and there's a gate we've actually got a lot of noise on this track because these are the effects of the actual guitar button like here there's actually a lot of funds between which is actually spilled from our instruments and the guitar button's headphones where he's getting overdone and it's so loud in his headphones that you can actually hear it on the guitars so it doesn't just like it up loud if I go back to it quite a bit if I bypass that gate you will hear all the noise that's what Dave's got on his headphones you can hear it on the mic you can hear it on the guitar on the Marshall stand and you can find the loud headphones so it's on updated now and there's loads of lateral effects there's more than 100 so you've got EQs, limiters compressors reverb and delays lots of unknowns amplifiers oscillators phasers that's what I'm doing by the time distortions this is showing the frequency spectrum for this particular track I can actually do an automatic to extend out the volume the DSP figure is that this is all jack reports it's up here so obviously it's not doing anything at the moment but if I I mean jamming it is particularly CPU hungry by this standard it's doing quite a hard job it's doing a lot of real-time maths that would be the same figure that's not right it's definitely not 1.9% it's more like it's the better team 1.7% it's the same I think it's been I'm just doing the EQ voices as well it's where it's all in it's not it's not it's not strange that's a I think it's like the 1.4 gigahertz it's possible to arrange a churium 64 laptop processor so I mean I have dual-optron in my office and that barely breaks 30% in this kind of work but here I'm thinking of jamming which is particularly CPU hungry and one in my studio it's a single optron I already see everything about 50% so it can handle how do you manage the sound generated by the option by what sort how do you manage the sound generated by the dual optical machine oh, the noise the noise from the fans that is a problem, that's why I have only a single optron in my studio the dual optron in my office because the extra and process does make more noise ac wedi bod yn ddechrau, mae'n rhywbeth yn ddegol. Mae'n rhan o'r ddyn nhw'n ddegol yn gwneud y gwasanaeth. Felly oedd am ni'n ddegol yn ddegol, mae'n ddegol. Mae'r gwybod ychydig yn ddegol yn ddegol. Mae'r ddegol yn y gwasanaeth 35W, a'r ddegol yn 64W X2, ac rwy'n cwysig iawn. Ac dwi'n gwneud radio rwy'n cyffredinol mwy oherwydd yma. Rwy'n teimlo nhw'n cyffredinol, fe yma. Yn cyffredinol oherwydd eich dawn llym. A oedd eich cyffredinol, rywbeth, eich ddiwedd. Felly ar constraints, dyma rwy'n thrôl. Mae gael yn cydnod arンドfyrdd bachol. And there is actually two macro necessary hours. Here and it's running the Asa driver with the generic USB audio driver, because the good thing about these kind of devices is that, when they first came out they all had proprietary, vendor written drivers. And the vendors themselves discovered that it was a major pain so they actually started to make the devices more class- compliant. Mae'r ystyried o'r sgwrn amser, mae'r ddod yn ychydig o'r adeilach. Mae'r ddod yn ystod y Lennu'ch bobl yn ddechrau, mae'n ddod o'r ddod oes yn gweithio bod chyfnodol. Mae'n ddod i'r ddod i'r ddod o'n ddod o'r ddod. Felly mae'r holl sy'n amser o'r ddod o'r ddod o'r holl sy'n gweithio sydd gennymol, neu'r holl sy'n gweithio sy'n gweithio sydd gennymol. It adds a bloom panel on the front so with a green one. That one you have to upload�� waem. To make it work. There's no good reason for that other than that It's good. This is relativity of weld costs a piercing. About £90. ac mae'r ddarparu ei wneud, ond mae'n gwybod, ychydig y gallwn i'r un o'r ffordd. Felly mae'r ffordd yn y Gymraeg. Mae'r ffordd yn ysgrifetol yn yma, ac mae'n tyfu, ond mae'n gwybod, yn ymwneud eich gydag i'r ffordd, oherwydd yn ysgrifetol, i'r ffordd, i'r ffordd, i'r mhwyfiant, i'r ymarfer, ac yn ymwneud eich mwyfiant o'r ffordd, i'r ffordd, i'r ymwneud, i'r ffordd. ac ydych yn ddiweddol yn gweithio ar gyfer y dyfodol. Oherwydd mae'r ardal drwy'n dda o'r ysgolwch. Mae'r ddyweddol yn ddiyfodol pan yn gwneud i'r gweithio ar gyfer yr audience. I fod yn cyffredig huntingh wrth rhaid i ymgrifol, â'r amlwiydd dros y ddiwyddiad yn Caherfel Fredo. Diem ni'n rhan o'r nhw y gallu bob oth yr hyn ac mae'n gweithio ar gyfer y ddiwyddiad which we're based on that framework called BeBob. It's a freeob. It also supports the new And I've Diced to based firmware devices. What we can actually now do is take a like a Debbie Robert you've got sort of a box on the firebox. Stick in one of these interfaces and you can get it working out of the box. And the great thing about the Fata, which is a revision of a freeob, is that because it supports not only these original group of classical mind devices but also these new ones that come on the stream as well, is you can take two different firewall audio interfaces from two completely different manufacturers running two completely different chip sets and plug them in a sort of daisy chain between firewall and actually have the whole lot of work as one big virtual interface and are like, I'm going to have a proprietary network and drivers can't do that because they're all vendor-read and they're all different. So we actually have better, in a way, we have better support now than any other platform because of this federal driver. We've got the freebop driver in this version, which is supposed to be the first version, but obviously the federal user isn't going to want to put in later. The current state of firewall audio with this particular virtual administrator is that if you have a bebop-based interface that person must make one of the firebox from one small firepod, M-audio makes several, you just plug it in, and instead of selecting ALSA in chat control, you set up one of those. As we've got an interface here, and it shows the mobile provider, this is the onboard sound card, the laptop. Instead of selecting ALSA, you just select freebop, and you get firewire interface working just as we have on this one. And that covers, like, as I say, any of those original freebop interfaces because a lot of the manufacturers, although they have different brand names on their products, actually all by chipsets from the same smaller vendors, just like the netcars. So that's great because most of the products on the market now are supported by, for example. I mean, there are a couple of holdouts, we still have our own production firm on this and so on, but there is some reverse engineering going on, so even those can be supported by those. Any more questions? Yes, I think I've used up all my time. If there's anything anyone wants to see specifically, just come and ask me. I'll be here tomorrow as well. There's also a machine at the back there, which is, that's running this year, 1.0, and it's stable at least from last autumn, if you want to have a try on that. So, Ian, does anybody want to take a look over there now? I'm going to show you a couple of things on that. Well, this release, which is 1.40, the current release, is Edge, plus our sort of recipe for packages. What we have is instead of, like, hand-selecting packages all the time, we have, like, a recipe which says, OK, we want this synth, that synth, we want Arda, we want Jack and Janet, and these kind of things. And it pulls down those packages from a natural repository and into auto-hills, a nice old niche. So, you could replicate exactly the same thing, yourself, by starting with a natural store, adding all the packages and then having a real-time patch kernel, and then adding all the little tweaks that we've made, the scripts and so on. But they're just taking, like, a couple of days, and you can save this off the effort by just getting the install ISO from our website, installing that. It takes about half an hour because a lot of the questions are preceded. It speeds things up a lot. And then adding dead end packages from there. So, because this one is in sync with that, should I show you the packaging? So, you could do this off the... Well, you could do, but you shouldn't need to, strictly speaking, because we're keeping our distro up to date with Damian as well. So... What's the difference? Is it, sort of, co-instead of different? Well, it's not super different. What it is is some in-go-monar at Red Hat. We've been working for some time on our real-time patches for the 2.6 kernel. And we use those because to run them, Jack, in real-time, you have to have those. So, this is obviously synaptic. New setting of repositories. So, on this particular laptop, I've got... I've still got entries left over from the install CDI, actually, thanks to this machine, which was 1.3. This is our stable app source, which we use to write 1.0 upgrades and so on. And we also have this one, which I'm running on this laptop, is our testing branch. This is not Damian testing. This is our own testing branch, which is based on Edge plus backported packages. So, for example, we find a bug that's in Edge itself. We have a backport server, and we build packages against Edge from SID. So, it's the version that's in SID but built for Edge. And that keeps everything nicely synced up. And then, if you want to, you don't have to, but we actually put... These are pretty much our default packages that you get when you install the distro for the first time. You can just enable Edge, and then get all packages from Edge. I mean, I think the... Was it like... There's just under 1,000 packages at the moment in the 6th course to the old base install. So, that keeps it down to a manageable number that we can actually track and update. We try not to duplicate too much. For example, when we were looking for an instrument chain application, there were about five different ones to choose from. So, we went through all of them, and we found the one that we thought was the best, and we made that default. If you want one of those other four, whatever they are, that are up to Damian, then you just enable your Edge source and go and get it. What we found is that sometimes, you know, you go through that approach, and sometimes the best-of-free package isn't actually in Damian, in which case we make a Damian package, and we upload it to CID, and then eventually the product goes right down. So, also, of course, now we're based in Edge. You can use the security updates. This is something we wanted to have for a long time because although we've got a pretty good security record, nobody's ever complained about a major security or anything like that over the last two years. We want to keep people, especially non-technical users, updated with things like ISO updates and things like that. So, you know, because the people are least aware of security and the people who need it the most. So, we use Update Manager now, and you can set that to remind you, oh, you know that there's a new Firefox or else we use the package. So, yeah, that's pretty much the same as Damian. We're using a secure app in this release. So, a lot of these packages are straight from Damian. So, for example, this one is specific to people that are back into chipset, and it doesn't work properly without it. So, that's just, like, as is from the end. And then we've also got these packages here, which are all some dummy custom packages. This is our app data. This is our skill and stuff. Task cell. You know, and this is where a lot of the tweaks are in the utilities package as well. But we've made just to set things up the right way. It could be as simple as, like, enabling a menu entry or not enabling a window in a flat place in a hot tub. And then, yeah, a lot of these other packages are straight from Damian. There are a couple of exceptions. I think we, you know, up to Alasdair. Yeah, we do ship us a firmware, which Damian doesn't ship, because if you've got an RME sound card or some of the others, it actually needs that firmware upload to work with a free driver. Otherwise, it just won't work. You know, else it will get started in a day. So we took the decision to actually ship the firmware, because we, although there's a theoretical argument on whether it's, you know, it's free enough or not free or whatever, we thought that if we have a system that's, like, 100% pure and pure free software, but our target users can't actually use it, and that's not actually a step forward. So we came down on that side of the firmware date. And then, you know, I mean, I suppose it's a pragmatic review and prefer the system to be, like, 99.5% free software, 0% free software. Yeah, yeah, I think it is, it isn't on free, but you won't get it in the WMA. I mean, there are distributions, like, in any sense, which, you know, like, you know, the firmware whatsoever. You know, we don't think that's feasible for our target users, because if you've got, like, an RME interface, you've got a serious studio machine, and you pop in a 64 studio desktop, or a WMA, and it just doesn't work. You know, you've heard that, you know, you know, that it's, you know, also support your hardware, and yet it just doesn't work. You know, you're not really going to use it again. So that's the approach for taking. So we've got a lot of different powerful things, like spell check and diction and things like that. Things we never thought we'd actually need, but you go into an application, and you click, like, spell check, and it says, like, dictionary not found, you know, so these are things that we've filled in over the years. So, yeah, it's just under 1,000 packages in a standard install. We've only recently gone over a 700 megabyte install limit, which is why we switched to a DVD. It's about 750 meg. We tried to pack everything we can into that. We actually found, although some people said, oh, I don't have a DVD writer and I can't make install DVDs, we actually found that a DVD would write and install significantly faster when you're wrong for the same amount of data because of the higher transfer rates in a DVD drive. So, you know, it's a choice of, like, obsoleting a very, very old hardware, or having, you know, faster installs. We went for faster installs. Although we do, we took the decision fairly early on that although we'd originally intended just to support very new-est hardware by AMD64 CPUs and I'd like to be intel of the 64 ones, pretty soon people said, well, actually, I don't have an AMD64 issue and I'd really like to use this. And some people said, well, I've got, like, a college where we have, like, 10 AMD64 machines and we have, like, 50 32-bit AMD64 and we want to have the same environment running on both, so that when we come to upgrade the hardware later, we can just have a smooth transition. So that's when we started doing two ISOs, AMD64 and I386 ISO, which works on pretty much all 32-bit systems. That's running back right there was one of the 32-bit version because it's so 24. So, any more questions? We'll see you then.