|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
[15:12]
So I think what we're doing is we're trying to take like - if for me this is sorta like three different different um inspirations, you know, one is that we want uh something that's high-tech but we want it to seem easy. And in spite of the primitive side of it and the very high-tech side, we want it to just be an appealing piece of equipment in people's hands. Um, # frustrations. They get lost a lot, s- as it came up in our last meeting. Um, takes time to learn how to use them. This is uh why I mention when Craig was uh showing us some ideas that we actually try and group controls, so d- it doesn't just look like a big panel, kinda like when you you look at, you know, a new computer keyboard, or something that is quite explanatory. If you want audio, if you want visual, then you have those. Um
[15:58]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
[23:37]
Cool, um. Okay. Um. Well this is just the working design um. Well this is just what - how I would go about it. Um I guess I try to define like what we're doing now, try to define what we're trying to get done. Um I think in a practical way, we kind of know what it is. We've used it, we're familiar with it, but we're - we can't n- we haven't narrowed down um exactly what the things we're trying to fulfil, like - Besides the basics, I think back - in the back of our minds we know what the basics are. Has to change channels, has to change volume, but in like specifics, right, which one of the basics are you trying to target. Um are there certain parts of the basics that are more important or less important than the basics? Um and I just - the idea is just to get everybody to um - I usually # have a have have a design that's there as a basic, so, you know, things that - to start everything going. But I guess everybody does have some idea, so I don't think um there's a need for that.
[24:36]
|
|
|
|
|
|
|
[24:36]
Um okay this finding things is a little bit confusing, so I'll go into the diagram first. It just explains how the process goes through, from a - from the basic technology point of view, the basic steps that you need um in the diagram and in this slide probably works better. Um okay, you need some power source. 'Kay, a battery or something, to keep it going. Um and that power source is important because it ties you down to um how long the device will last. Um it ties you down perhaps a bit later on in terms of the technologies um how far you can transmit the signal or the complexity of the functions that you want. Like for example, voice recognition, right. That might be constrained because that - you might need to power a microphone, you might need to power other things, so that's one perhaps constraint there. Um
[25:24]
|
|
|
|
|
|
|
[25:25]
# Th- Okay, the basic thing is there's a user interface where people punch a button or talk into it or smile to it or blink their eyes, whatever. You know, and that um picks up an input from a user, um uh a logic - a series of logic has to decide what the user is telling the device, and the device has to r- you know, based on you push button A_, so I will do something with button A_. So maybe button A_ is the power button, okay. Um and then it needs to be able to send the signal out to the device itself which is the receiver here. Um and I think that's about it in terms of my design um. It's fairly general, um and I guess the purpose of this is also not to restrict you in in the way you're thinking, like um voice recognition, right, um, if it's something which is important then we just add more power rather than having a thing that we don't have enough power. So it's not really a constraint in that sense, but I mean these are functionally, you know, the base, what the technology has to do. Um so I guess the rest of it - I think we should maybe you you wanna go back to what the functions are? I think that's more relevant to a discussion?
[26:34]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
[28:27]
There might be one other problem with the transmission, um in particular right now, since we're talking about voice recognition. Um if somebody's gonna h- talk to the device, you ideally want them to hold it to them. I- it - you may not require that, but you know, um it's it's it's something very natural, I guess, you know, to hold it, to signal to the user, and push a button maybe to start s- talking about it. Then you need to send the signal out, so because if you're using infra-red, the line of sight um say the T_V_'s at that chair, and I'm standing in front of here and the transmitter is here, it blocks it. So in that sense, there's not really a restriction but it's something which you may have to think about later on in the process. Not so much further down.
[29:6]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
[31:56]
Another thing that you were saying about categorising the controls? Um maybe I could suggest we we break them down into three simple categories. One would be audio controls, one would be video controls, and the other one would be a device. Um this may not map very well to advanced functionality especially, but I think that um from a manufacturer's point of view, from a person designing the device, but I think from a point of view of a person using the device, you know a T_V_ is something they see and something they hear, um it's something they do other things to like turn it on and turn it off. I mean like so what we could have is like three buckets, right, where we could throw things into, like if we want this feature, let's throw it into there, and then from there decide whether it's basic, or it's non-basic. I mean it might help with the visualisation. And it would actually help with the component build as well.
[32:45]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
[34:08]
Um things like on off. Because they don't have anything to do with what you see. I me- mean in terms of picture and the entertainment value, you know, um so um - And channel. Because the on off also goes, you know, like on off like power, not on off sound. Not on off video. Although you don't turn off the video on your T_V_, but um you might wanna you know turn off the sound, say you wanna pick up the phone, there's a mute button, right, so you you have you have a choice of putting it on to um others or a device. Device is basically anything which we can't categorise, right. We put it out.
[34:45]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|