Hello everybody HoodedCobraCommander788 here and I'm back with another vintage GI Joe toy review and in the last few review videos I have done some of my favorite vintage vehicles and action figures and that's pretty easy to do because I really loved GI Joe growing up as a kid. I love collecting it now so a lot of the figures and vehicles fall in the favorite category but they're not all my favorite and I do kind of need to mix it up a little bit so this time I thought I'd look at a figure that definitely is not one of my favorites. It would not be correct to say that I hate this figure. There's not a lot in GI Joe that I hate. There actually are a few figures that I actively hate and I will review those figures but I'm saving them for a special occasion. So we're going to review the 1985 Quick Kick and again I don't hate this figure but I do have a few things to say about it. Quick Kick was introduced in 1985. He was also sold in 1986. He was discontinued in 1987. In 1991 he was re-released as a mail order but that version of Quick Kick had some subtle color differences from the original. Quick Kick is the GI Joe silent weapons expert which seems a kind of odd because GI Joe already had a silent weapons expert. Snake Eyes. Quick Kick does not use guns and Snake Eyes does so Quick Kick kind of seems a little bit redundant. He's like Snake Eyes without guns. Well maybe he is a little bit redundant but I still like having Quick Kick as part of GI Joe but I'll talk about that more later. In 1987 Quick Kick was replaced as GI Joe's resident martial artist by Jinx, the female red ninja. Quick Kick's codename comes from an English language expression which means to kick things quickly. Let's not look at Quick Kick's bare feet first. Let's look at his accessories as we usually do and he comes with what the card contents call a samurai sword. This samurai sword is fairly well detailed. It has kind of a rougher wrapping on the handle than Storm Shadow's sword. You can see Storm Shadow's sword handle has a much more elaborate design, much more detailed, a less detailed in Quick Kick's sword handle. Also like Storm Shadow's sword it's all molded out of one solid color of plastic. We just didn't get paint apps on the accessories back in the 80s. Quick Kick's other weapon was not his bare feet. It was Nunchucks. Nunchucks molded out of the same color of silver plastic as his sword. Again another fairly well detailed accessory. It looks pretty good and Storm Shadow again also came with Nunchucks. His was molded in black. Quick Kick's Nunchucks are not just a silver remold of Storm Shadow's Nunchucks. They are different. So far we're doing pretty good on accessories. Both of these accessories are appropriate for a silent weapons expert and martial artists. So let's look at his third accessory, not his bare feet. His backpack and this is the accessory that makes the least sense. The backpack itself I suppose is fine. It's fairly well detailed and it provides a storage space for the sword. The sword slips right through there. You can see how it slides through the inside there on the back. And so I mean if it were just on its own there would be nothing wrong with this backpack. The problem with the backpack is how the hell does Quick Kick carry it? It attaches to his back through the hole there but he doesn't have any straps for it. He does have this red sash and I suppose you might think the backpack connects to the red sash but no way. The backpack only barely touches the edge of the red sash and if that were really attached and he wore it that way the backpack would kind of swing out and it would flop around. He wouldn't be able to quickly access his sword. So it looks like the backpack is just stapled to the skin on his back which makes absolutely no sense. He has a backpack with no straps. Honestly I don't think this character needs a backpack. It's nice to have a place to store the sword but it just doesn't make sense with the design of the figure. Let's not take a look at Quick Kick's bare feet. Let's take a look at his articulation and he had the typical articulation of 1985 G.I. Joe action figures most of which did not have bare feet which means he can turn his head from left to right but he can also look up and down. His neck was on a ball joint. He could move his arm at the shoulder up about so far and he could swivel it all the way around. He could bend at the elbow about 90 degrees and he had a swivel at the bicep so he could swivel his arm all the way around. The figure was held together with a rubber O-ring that looped around the inside so he could move at the torso a little bit. He could move his legs apart about so far. He could move his legs at the hip about 90 degrees and he could bend at the knee about 90 degrees. His bare feet are not articulated. Let's take a look at the sculpted design and bare feet of Quick Kick starting with the head. His head as you can see has black hair. His face I think is meant to evoke Bruce Lee. He looks somewhat like Bruce Lee but not exactly. He looks different enough that Hasbro would not get in copyright trouble for using Bruce Lee's image but I think the head and really the whole figure is supposed to bring back images of Bruce Lee. He's wearing a white headband that goes around and ties in the back. It has a red sun from the Japanese flag which is kind of interesting. Quick Kick is half Japanese according to his file card but he's also half Korean and his nationality is American. His chest as you can see is bare. Unfortunately my example has a bit of a scuff right there. He has a muscular chest and nipples which is something that was lacking on the bare chest of Zartan. Apparently something about Zartan's color changing ability made his nipples disappear. So the nipple is nice attention to detail but I suspect that the sculptor of this action figure knew I would be making this review video 30 years later and put the nipple on there as a way of tricking me into praising man nipples. Well played Hasbro guy well played. Quick Kick has a red sash that connects to his belt in the front and in the back. This sash is obviously some kind of cloth and it has some pockets where he has shuriken or throwing stars. I always wondered if you stored your throwing stars this way and you had to bend over or kneel down or something do you end up stabbing yourself with them. The waist piece has a gray belt with a buckle. It has some blue pockets on the side. Not a lot of detail on the waist piece but I think that's intentional. The legs are plain black trousers all the way around. There are no sculpted weapons on the trousers and I think that's intentional too. I think the black pants are meant to look like karate pants. They're light. They're loose and they're supposed to be comfortable for kicking and for unarmed fighting. And now we get to the bare feet. Quick Kick has bare feet. He's not wearing any shoes. While I suppose this might be appropriate for martial arts when you're practicing in the gym or something like that but there is no way anyone would go into combat like this. Quick Kick thinks that by going barefoot he will be more silent but Storm Shadow wears shoes and he doesn't seem to have any problem with that. I'm sorry but no matter how you cut it this is crazy. No matter how tough Quick Kick is he could be taken down by a sharp rock or a broken piece of glass on the ground. And it's not about toughing out the pain either because you're not going to tough out an infection on your foot. To make matters worse the flesh tone is painted on black plastic on these feet so you often run across Quick Kick's feet that have some of the paint worn off. There's a little bit worn off here and so it looks like he has black toes and that looks really ugly. Okay enough about Quick Kick's bare feet. Let's talk about his file card which does not have any bare feet on it. The file card was printed on the back of the card on which the figure was packaged on the other side of the card. You can see part of the front of the artwork on there. Oh look there's a bare foot. Quick Kick had two file cards. Originally it was this peach color but in 1986 they started issuing file cards with a gray background. The file card is the same otherwise but the background color is different. We have a nice portrait of Quick Kick here. It says his faction is G.I. Joe. His specialty is silent weapons and his codename is Quick Kick. His file name is Ito MacArthur S. His primary military specialty is infantry. His secondary military specialty is intelligence. First place Los Angeles California and grade is E6. This section says subjects Japanese father and Korean mother owned a grocery store in Watts. Not accepted by either the Japanese or Koreans because of his mixed ancestry and too short to play basketball, Quick Kick turned to martial arts. All martial arts. He's a ranking black belt in Taekwondo, Goju Ryu, Southern Prang Mantis Kung Fu, Tai Chi Sword, Zen Sword and Wing Chun. He was working as a stuntman in Hollywood when he was recruited for the G.I. Joe team. I find this highlight on Quick Kick's ethnic background really fascinating and maybe it mirrors the experience that a lot of children of immigrants have. This sort of inter-ethnic rivalry in American inner cities. Larry Hama, the writer of the G.I. Joe comic book and the writer of a lot of these file cards was himself an Asian American and he may know something about this sort of experience. In this section it says he's a qualified expert in all NATO and Warsaw Pact small arms. He doesn't come with any NATO or Warsaw Pact small arms but apparently he knows how to use them. This quote in the bottom section says, here's the situation. You want to gain access to a fortified villa, 12 foot tall continuous wall topped with razor spiral and only one gate through it. Two inch steel plate on the gate, two sandbag guard houses with direct telephone link to the main house, four guards with submachine guns, two dobermans, an asylum alarm hooked to a dead man switch that one of the guards is leaning on at all times. How do you do it? Have Quick Kick hit it, that's how. This file card is really well written. It gives the impression of a very interesting character. He's got a very fascinating background. He sounds like a total badass. He's an expert at what he does and it seems like he can overcome any odds with his martial arts ability. Kind of like another member of the GI Joe team and Quick Kick does all this without wearing any shoes. So what do I think of Quick Kick overall? First of all, he has no fricking shoes and that's really tough for me to get by. There's no way in any universe that that works. It's not that I don't want Quick Kick as part of the GI Joe universe. I really like the character and I like what he does. I like the way he's portrayed but I just like him to be a little bit more combat ready and wear some shoes. Quick Kick is definitely meant to evoke images of Bruce Lee. He's definitely supposed to make you think of Bruce Lee. Interestingly enough, Bruce Lee was neither Japanese nor Korean but nonetheless it's still the same idea. The whole shirtless design with the black pants fits with the way Bruce Lee appeared in some of his movies. So you're definitely supposed to look at Quick Kick and think that Bruce Lee has joined GI Joe. Bruce Lee, however, had the good sense to wear shoes. So there you have it. Quick Kick is a fascinating character. The action figure is actually pretty nice. Pretty well detailed where it needs to be with some subtlety. For what they were trying to do, I think they did a pretty good job. There are just some design choices in this that, to me, don't make any sense. For that reason, I cannot put Quick Kick in the top tier of GI Joe action figures. At best, he's middle of the pack because, well, he's not got any shoes on. It's very difficult for me to get past the bare feet. He's wearing bare feet and, fourthly, his feet are bare. That was my review of the bare footed Quick Kick. I hope you enjoyed it and if you're thinking of getting a Quick Kick who doesn't have any shoes, I hope you found this video informative. If you liked it, make sure you give it a thumbs up on YouTube and make sure you subscribe to the YouTube channel. I've got a lot of great new GI Joe toy reviews coming up. You don't want to miss them. Most of them are wearing shoes. And don't forget to like the Facebook page. You get a lot of updates there that you don't get anywhere else. Thanks for watching and I'll be back soon with another GI Joe toy review. I guess I wasn't too big of a hurry. Remember, anything worth doing is worth planning. If you don't plan, you're out on the land. Pulling is half the battle.


Hey, welcome back everybody. Jeff Frick here with theCUBE. We are live in Las Vegas at AWS re-invent. 32,000 people, I think the cloud thing is real. It's packed wall-to-wall. You can't hardly move around. We're excited to be here, our fourth year coming to the show. And we're excited by our next guest, Praveen Ragnath, the Director Cloud Marketing Explunk. Welcome, Praveen. Thank you. And with him, Gary Stokes, Director of Product Engineering, Family Search. Welcome. Thank you. So I think most of our audience knows a little bit about Splunk, but we don't know so much about Family Search. So Gary, give us kind of the quick, what's Family Search, what are you guys up to? Family Search is a genealogical organization, the largest in the world. We have about two billion records of historical records that are out there that we publish online. That represents five and a half billion people. With those records, we have 17 million registered users. We put about two million new images out a day of historical records. So we have a lot of new things coming online there to help people as they look for their families and try and learn about ancestry. That's a lot of big numbers. You're saying I'm faster than writing them down. So how long has the company been around? Well, it's been an organization ever since the late 1800s. We've had a website ever since the middle of the 1990s. Wow, so you collect data from all different disparate data sources, I assume. That's right.  So you're here at AWS. I presume you've made the move to the cloud. We have. About five years ago, we decided that we needed to figure out how to handle our hardware, our machines, how to accelerate our development. And as we went through and looked at that, the cloud became the obvious place for us to move to a platform that we could adapt as fast as our developers needed. So we've gone pretty much all to the cloud. So was it mainly just for scale? Was it for growth? Was it for flexibility? What were kind of the primary drivers that were breaking down in your own internal systems? I think it was all three of those. Particularly scale, where we vary quite a bit over the course of a week and so we didn't want to have the maximum number of machines all the time. And our development efforts were varied quite a bit and so we didn't want to be purchasing machines that wouldn't work for other development just for a specific project. Okay. And Praveen, was Splunk involved with Family Search then?  Oh, we were not. They've been a long time customer of Splunk. Oh, okay, great. Yeah, they actually have a tremendously interesting use case with us. What they've done is actually emblematic of digital transformation. They've had a model and they've completely transformed how they service their customers, how they deliver features to their customers. They were releasing code once a month on their website before and now they've transitioned to 900 times per day. And they've done that through AWS and they've done that through the visibility of Splunk. 900 times a day. Okay, so there's DevOps defined right there, right? 900 times a day. So that is a massive change. Not only in what the physical function, but the culture had to be a huge change to move to that. Tell us a little bit of the story of who decided to make this change. And then the part I always think is interesting is how do you sell it internally? Because we went to the developers and asked them, what are the things that frustrate you the most as you're trying to do development and get products out? And there were a couple of things that really bothered them. One was the amount of time it took from when they coded a feature until that feature actually showed up and they could get feedback on it. Which was how long, kind of? Well, we were doing, we were at once a month. Once a month. When we did it, yeah. And then the other thing that they were frustrated with was when there was an outage. It took them forever to figure out in this system of multiple services, which services that's causing that. And so we created this mindset of DevOps that said as soon as a developer makes a change, checks it in, we'll build it and we'll put it on the production site so it immediately exposes what's there. And that's where Splunk came into play because we needed something that would tell us, allow us to be checking that system and say, is it still valid all the time? That's good to say. I presume some of the pushback was, wait, wait, wait. We're going to break something, the old Zuckerberg, right? Develop fast, break fast, fix fast. So this is where Splunk comes in. This is really what you put systems in place to make sure that you could actually execute on this vision. That's right. The developers, you hit it right on. The developers were really nervous about, well, we don't want to push out code if it hasn't been completely tested. And so part of changing the culture was putting automated tests around everything. So every check-in runs through all the automated tests and then putting Splunk doing checks on the production system. So if it made it all the way through that, then we would still catch it with one of the checks later on. So Praveen, we've been going to Splunk.com for years and years and years. It's not really something I guess I think of as top of mind is that an application for Splunk. Is this new? Is it a different twist? Is it a new application? How does this fit within kind of your product portfolio and what you guys are delivering to customers? Yeah, you know, it fits quite squarely into what we do. So we have customers, as you know, using us for security use cases, IT operations use cases. That's the one we think about all the times, the security and logs and all that stuff. Exactly, and even in the AWS world, it's the same thing. It's the visibility into what's going on AWS to IT ops. Now, the key thing of what organizations use in the cloud now for is digital transformation, changing entirely how they run their business, how they go to market. Now, what's exciting to us about working with Gary is you can't deploy 900 times a day unless you have real time visibility into the impact of each and every single one of those 900 changes. So you can know what's working, what's not working. So we have customers using us in that application delivery DevOps use case. And I think this quite frankly is one of the pinnacle examples of an organization that's been able to make that transition by leveraging the visibility that we provide. So Gary, how long did it kind of take once you decided to make the move to kind of get through what you would define as transition? We made the move and we announced the development organization. Then it took us about eight months to tool up to build the tool set that we needed, get them ready. And then we started moving products over time. It's been kind of a transition because to move them to AWS, we didn't just want to pick them up and drop them on AWS. There was some rewriting. And so we've been about three and a half, four years in the process of moving things. And was the move to AWS kind of the catalyst to go ahead and let's make this other move to more of a DevOps centric way of doing things because we're going to rearchitect some of these applications? It was the move to DevOps. Oh, it was the DevOps that caused us to want to move fast enough that we were looking for a house of solution there and AWS was the right answer. All right, that's great. So law of unintended consequences, right? Always bears its head. Sometimes positive, sometimes negative. We heard in the keynote today from the guy from Italy and from Andy about some of these huge benefits that come that you don't necessarily plan for. Well, I wonder if you could share some stories of things that now that you've moved into this 900 times a day release cycle. But what are some of the things that you didn't think that now you guys are doing? That it's like, wow, really rethinking the way that you deliver service to your clients. Yeah, so two of the things we were trying to solve was how much time does it take us to get something out there? And the second one was when something breaks, how quickly do we know about it and how quickly can we identify and fix it? We used to be, if we had an outage, that that would be hours for us to figure out which services that's misbehaving and to fix that. Now we're down to minutes on that because we can use Splunksy across the system see how the correlation of the different services is happening. Right. So that's really important to us and the ability to deliver really fast has made it so that we're pretty sure we know what check-in happened if it was a change related. But culturally that's changed because we only get maybe once every month or two a change related error now. And that's because the developers are much more disciplined. They know it's going to end up really quickly on production. It breaks fast, right, though, no. And then just, again, the growth trajectory of the company, has it impacted your growth? Has it enabled you to grow faster? Can you pull in more data size, more data on the supply side? How has it really impacted the company from a strategic point of view? It makes it so that our users always have a system available. And what we've found is since all of our users are volunteers, essentially, they don't get a benefit except what they like. Then they want the system up and when it goes down they don't come back for a while. Right. And so for us to keep the number of users there, we have to always be available when they want to use it. Okay, so looking back, if you're talking to a peer who's thinking of making this move, what advice would you give them? Is there something you might do different? There's something that worked really well. You know, really, what we talk about a lot is you know, find little wins. You know, find little wins and then move the organization along. What if you could share some tips and tricks with a little benefit of hindsight? Probably a couple. One was jump in. If you keep saying, well, once we fix this two or three things, you never get there because there's always this set of hurdles that look too big in front of you. Second one was get all the data there that you need because this is data driven. Gotta make the decisions on are we improving based on data? And so what we did was we pushed everything into Splunk and then backed off things that weren't important rather than trying to identify from the beginning everything that was important. Yeah, we are alive. They are making a lot of noise here at the conference hall. You know, I'd love to add one thing to what you said, Gary. Yeah, absolutely. I was going to ask you. Yeah, which is to think big, which is something I think that you did in this whole effort. When the effort to move to DevOps and move to continuous delivery came in, you know, I don't think you envisioned going to 900 deploys per day when the process first started, but they thought big and they let the process go and they discovered what the technology enabled them to do for the business. And that mentality is what I think has driven those breakthrough results for you guys. And I wonder for me, from your point of view, as kind of the supplier of some of this underlying technology, you've seen this over and over and over. How are you seeing your landscape change as people move to this DevOps mindset, really adopted? Oh gosh, we are thrilled to be in the center of this. When just here at the show at AWS, when we see the customers that are on stage at the event, Finner CIO spoke. Finner spoke with us last year here. They do all their security and compliance monitoring for AWS as well as their application monitoring as well as their cost management using Splunk. We have family search talking about their cost management use case. Travis Perkins was a $6 billion home improvements manufacturer, well retailer out of the UK doing their operational security management for AWS using Splunk. We have Eastman Chemicals, a $10 billion plastics chemicals manufacturer doing their operations, applications monitoring using Splunk. We have large global organizations doing their DevOps application delivery using our tool to just be successful in AWS. And we're just thrilled about that. Right. Well unfortunately we have to leave it there. We are on a super tight schedule here at the show. So Praveen, thanks for stopping by Gary. Great to catch up. Thanks for sharing your tips. Basically jump in and think big. That's the takeaway. I'm Jeff Rick. You're watching theCUBE from AWS Reinvent. Thanks for watching.


Words appear. Making an accessible video. I'm Terrell Thompson. I'm an IT accessibility specialist at the University of Washington. Video is a really powerful medium and benefits a lot of people, but also creates some barriers. So if somebody who is unable to hear the video, then they need some equivalent to the audio. So that's where captions come in. Words appear. My name is Doug Heyman. I work at the University of Washington in the Accessible Technology Services group. And my function here at this group is working around captioning efforts. More and more people are using videos in their technology instructions or even providing information about their groups if they're using an outward facing webpage and they're relying on YouTube clips or Vimeo or Facebook or a whole variety of different modes and they're maybe not thinking about the end users benefiting from captions. And that could be not only people who are deaf, hard of hearing, but also people who English is, you know, not their primary language or somebody that's in a distracted environment where they can't turn up the volume, they can turn the captions on if they're available and be able to take in the same information. On a video monitor. In Spring 2017, a popular new class was offered at the University of Washington. Although there were no requests for captions from students in the class, its instructors decided that all lectures would be posted online with captions. All right, today we're going to talk about fake news. I'm Carl Bergstrom. I'm a professor in the Department of Biology. University of Washington. I'm Jevin West. I'm an assistant professor in the Information School. In a lab. So this class is a brand new class that we're teaching called Calling Bullshit in the Age of Big Data. And it's something we've been wanting to teach for a long time. We've kind of been dreaming about doing it and we've actually been able to put together for this quarter. The main idea of the class is to teach people how to see through BS in quantitative forms because these days instead of just getting fancy rhetoric, we're getting an awful lot of misleading graphs and figures and tables and models and algorithms. And the point of this course is to help students learn to challenge those and see when they're being misled by that kind of information. For this class, we wanted to move beyond just the 160 students in our classroom. We wanted to scale to the world and we're thinking big about this class just because we think these skills are really, really important. So if you're scaling to the world and you want to have a world audience, we wanted to make it as accessible to as many people as possible. Not only are they useful when they're hearing challenges, but it can be useful when English is not your first language. I'm not the easiest to understand when I'm speaking. And so I've had people email and say they appreciated the captioning because it was much easier for them as an English's second or third or fourth language person to be able to follow what was going on in the classes. So that was this added bonus and really contributed, I think, to this worldwide accessibility that we're aiming for. Because the class uses a sometimes jargon, just like any class on a university, someone can go back and try to hear exactly what that word was. They can see it in print. Students, including Austin Wright Pettibone, say the captioned lectures have been a bonus. They're like another set of notes. It really helps me engage with the material because I can be in lecture and just have my entire focus on what's being told to me. And then I can go back and really come and supplement my learning with the videos themselves. I think it's critical to helping us to process that information because as we're getting so much of this being thrown at us, we need to make sure we can take that step back. And that's what those videos help us do. When you create captions, be sure to leave enough room on the screen so the captions won't cover people's faces or important content. This is a good way to frame interviews, so there's enough room on the screen for captions and other graphics. Two red rectangles frame the speaker's torso. My name is Cheryl Bergstahler and I direct accessible technology services at the University of Washington in Seattle. The name graphic is to the right. But this interview is framed too tight for captions and name graphics. Cheryl's face fills the smaller frame. My name is Cheryl Bergstahler and I direct accessible technology services at the University of Washington in Seattle. Words appear. When you create captions, use one or two lines of text. Caption the exact wording of speakers, including slang. Synchronize captions with the audio content. Use both uppercase and lowercase letters. On the monitor. Another recent video, Best of UW 2016, included captions for a very different reason. I'm Gina Hills. I'm the web communications director for university marketing and communications. This year's video was all visual with music. We did close caption the video. The first stage was we put a little thing that said music on there. But then one of the people in our department went a step further. They described the music in captions. If you watch that video, the music contributes significantly to the emotion that the video creates. So it is featuring a lot of the really wonderful things that have happened at the university over the last year in 2016. And the music builds and swells and just becomes much more dramatic as the piece grows. Captions over various images. Music swells as piano is added. Crescendo. Music returns to its original intensity. And so they revised the captions and really did an excellent job, I think, of capturing exactly what the music is doing throughout this piece as it grows and swells. Piano takes precedence as the music begins to slow and fade out. Words appear. Audio description. The other thing that's interesting about the best of UW 2016 is that it was entirely music. There's no spoken audio.  So they hear the music and it's a wonderful piece, but to them it's just a music video. They have no idea that all these wonderful things happened at the university. So all those details are missing for them. And so that particularly is a video that requires audio description. Words appear. Hashtag best of UW 2016. The Nobel medal next to David J. Tholes. 2016 Nobel Prize in Physics with President Obama, Mary Claire King, National Medal of Science, UW and Microsoft break record for DNA data storage, a collage of photos inaugural Husky 100. We covered all bases, all audiences and didn't leave anybody out in terms of experiencing the previous year at the university. I think that this is a good model for what we can do and what we should do and what we should aspire to. Final thoughts. One suggestion I have to other institutions is to think clearly about what they're going to do proactively and what they're going to do reactively. For instance, when it comes to captioning videos, we believe strongly that every video should be captioned on our campus, but that's probably not going to happen, at least overnight. So we have two approaches. One is we make sure that our disability services offices caption videos immediately, like within a day or two, when they're asked for an accommodation from a person who's deaf. But that's not where we end. That's not where we stop because there are a lot of people that look at videos that are not even enrolled in courses. So on the publicly available videos, we have a service where we will find funding centrally to caption those videos. We're very appreciative of the help we're getting. We know how difficult it is to add these extra features and we've had tremendous support. We send in the videos, they come back captioned, they look great and people are consuming them. It's a win for everybody. Words appear. To find out more about creating accessible videos, consult uw.edu. This video was funded by UWIT, Copyright 2017, University of Washington. Permission is granted to copy these materials for educational, non-commercial purposes provided the source is acknowledged. Described by Audio Eyes.