00:17	%
00:37	So um nice to see you again. Uh. So, uh.
00:46	Tod- uh for this meeting I will take the notes and do the minutes.
00:52	Uh so we will see our three presentations.
00:58	Um we will start with the uh Manager Expert wi- who will talk about uh user re- requirements, whats user needs and what it desire for this devi- device.
01:14	Okay, can I have the laptop over here, or? Okay. Have to get up. $
01:17	Yep. Oh, I don't think so. I think you have to come here.
01:21	I dunno.
01:23	I think it should stay.
01:24	Excuse me. $ Okay.
01:25	Yeah, that's it.
01:28	@
01:32	Should stay in the square here. $
01:33	Okay.
01:45	Oh, maybe.
01:57	Okay, so basically I'm gonna present some findings of a study we conducted uh into uh what users want in this remote control. Um so first of all we - what we did is we um conducted a an experiment with a hundred test subjects. Um we put them in a- in our um usability laboratory and got them to, you know, um play with remote controls, and also to complete, after they'd done that, to complete a questionnaire uh to tell us what they like and what they don't like in remote controls. # %
01:59	Oh, you can put it here. Oh that's okay, it's jus-
02:36	So basically um the major things we found out was that um basically users don't like the look and feel of of most remote controls that are currently on the market. Um they, you know, seventy five percent of the people we we uh did the experiments on, found that rem- remote- the remote controls that they'd used in the past were ugly. Completely ugly. Um they they didn't match the operating behaviour of the user, that is, you know, the the way users use remote controls when they're watching T_V_. Um, that the layout of the remote controls didn't match they way that they used it. Um and
03:18	thirdly they say that w- half of the users that we um tested said that they only used ten percent of the buttons that uh are on remote controls. Um so we collect- we also some collected some usage statistics uh based on how these test subjects were using their remote control. And from this we basically came up with the figure that
03:44	the channel buttons, the channel selection buttons are the most - by far the most used buttons on the remote control. Um and you can see they're used a hundred and sixty eight times per hour on average, um, while the user's watching T_V_. Um the closest button that was used, well the cl- the button that was used that was closest to the channel button was the teletext button, um which was used fourteen times per hour, followed by the volume button, which was four times per hour, um,
03:56	$
03:59	$
04:16	all the other, all the other um buttons, such as ch- um audio and picture selection- um configuration buttons and things were used, you know, l- approx- well less than or equal to one times per hour. Um we also asked users um which buttons had the most importance to them, you know, which which buttons they felt were the most important buttons on on the remote control.
04:39	And basically they came - they said the channel, volume, and power buttons had the highest relevance to users, um note that only power was very infrequently used, it only had a b- a a fr- usage frequency of about one times per hour, but users ranked it as having a very very high relevance. Um and the audio and picture settings had a very - that well the users thought that um w- the audio and picture settings were very uh weren't very important to them um, and they used them very infrequently a- as well.
05:13	% So we asked users what what um frustrates them the most about um current remote controls. And
05:24	fifty percent of the users said that uh what frustrates them is losing the remote control um somewhere in the room and not being able to find it. Um # they also said that it um it takes a lot of time to learn a new remote control, especially when there's many buttons and it's a, you know, a c- a a unintuitive interface. Um and then thirdly, they - some users commented on the fact that the the- you know the way that you have to hold and press buttons on a remote control ar- are bad and um cause u- repetitive strain injury.
06:03	# We also asked some users about some specific features that they'd like to see in the - on the remote control. In particular, do they want an L_C_D_ d- display, and secondly, do they think speech recognition uh is a useful feature to have on a remote control. Um basically our findings are that um amongst a- younger age groups uh the answer is umv- overwhelmingly yes. They want these features, they want these high technology features. Um for instance, ninety one percent of pe- of people aged between fifteen and twenty five said yes, they want these features.
06:16	$
06:28	$
06:36	Whereas um % the the trend was as users as users um became older and older uh they were less likely to want these sort of features in a um in a remote control. So I guess it depends on where we're focusing our our market. Um and as our company motto is putting fashion in electronics, um I think we're focusing on the younger younger um target demographic, and so maybe we should think about adding these sort of high technology features into our remote control. That's my dic- that's my presentation. Thank you.
07:08	Hmm.
07:12	Thank you.
07:15	#
07:21	Okay.
07:23	So, um
07:28	maybe now we can talk about a user interface and uh about the technical function of this device. So uh Pet- Peter, can you talk- say something about that?
07:41	Well, okay, yeah. Yeah, but the user user interface is responsible.
07:44	No.
07:44	B- you think uh I I'm User Interface Manager. $ Okay. Okay. If I could go there with this cable.
07:47	Ah. $ Sorry, I'm - Sorry. Sorry.
07:47	Okay, so @.
07:48	$
07:53	@
08:01	You're scaring me with L_C_D_ man. And speech recognition in remote unit, it will be very e- expensive.
08:07	$ Yeah, it's true, but, you know, they're features that users want, so it's - And our production cost of twelve fifty Euros per per unit is fairly high I think, so I think we can afford to to add these sort of features into our remote.
08:10	$
08:14	Yeah.
08:18	@
08:21	Yeah.
08:25	At least we have couple of months t- to work on it so so it will be cheaper finally. $
08:26	#
08:28	Sh- okay. @
08:29	It is true.
08:32	Where's delete button? Okay.
08:36	Oh I'm sorry. # @
08:41	$
08:53	@
08:53	@
08:59	Okay.
08:59	That's the wrong one, I think.
09:01	Yeah, it's still Bob Morris. $ Yeah you should have put yes.
09:02	Oh. Presentation three?
09:04	Because you cancelled* it.
09:07	Yeah.
09:07	Oh. $
09:07	Click on yes.
09:12	@ yeah.
09:12	Yep.
09:21	Okay, so here is my presentation about technical function design. I will talk about different components and s- of system and how they react together. Okay, uh, first what is a remote control? Simply it's a device, as you know, for uh, for sending some commands by some waves to uh another device to to tell different commands uh with this device. And the main idea we don't use any cable and we can rec- react simpler with the device. Uh i- it has different blocks, different blocks. Uh first is remote control have sh- ha- should have some electric circuits uh making interface with uh keyboard and uh r- reading uh keyboard and reading the keyboard uh commands.
10:13	And then inter- then make uh these keyboard commands, uh in- interpret these int- uh keyboard commands. And then there should be uh an electronic circuit making uh electronic signals according to these commands and uh finally there is a transmitter which is a cord or a a diode making uh making uh waves to transmit through the air and uh uh this air this uh wave uh will be received by the by the other device like a television or whatever, to uh r- to realise the command.
10:53	Okay, # uh about - what I found about uh different uh these different blocks are uh, usually there are two different methods uh to - for designing a remote control. They are based on infra-red uh waves or uh uh radio waves. There are two different uh uh solutions I mean. This is uh this can be uh uh the the differences the th- between different kind of waves, infra-red or radio waves.
11:10	You still want me the presentation.
11:23	And uh also as uh I understood, and uh I think it was a part of uh Bob, uh uh presentation, people prefer to have uh to have uh the remote control with less button. So for the electronic part, working and interfacing, with button, we should we should try to t- try to design a remote control having uh some some simpler buttons or some rolling buttons to just to just to search between different options, and showing o- something on T_V_ and putting less lesser stuff on the uh on the remote control.
12:05	And uh personal preferences, uh uh uh uh certainly a remote control with - uh working with radio waves is uh preferred because uh you can pr- you can take it in any direction and you don't need to tune it any way. And uh uh again, using bigger buttons and less number of buttons are also preferred, as I see. Okay. That was my presentation.
12:34	Okay.
12:44	I have a question.
12:45	Uh-huh.
12:46	Do you think radio waves um will interfere with other appliances in the home?
12:52	Uh, I don't think so, because uh we can make uh we ca- we can make this wave in a specific frequency. So they can be in a range which is not inter- interfering with the # with other devices inside the home.
13:08	Okay.
13:09	So can we use any any frequency? We have the right to use any frequency?
13:09	Yeah, it should be okay @.
13:14	Uh no but as I know, there is a range for uh for this uh f- for for uh for this stuff, for designing this circuit. We can we can we can tune our uh transmitter to work in this range, and for this range we don't need to ask any permission.
13:32	Okay. And what happen with uh radio waves when two neighbours have the same - have our remote control, for example? And so do they have the same frequency, or?
13:44	Uh for this I'm not uh I I don't know the solution, but one solution can be something like putting uh p- password or something inside the wave, so the only your T_V_ can understand it- Yeah, identification code inside the -
13:58	Okay. A kind of identification @, okay.
14:00	Yeah f- # uh I know about this, since it's my - it's exactly my field, so. It's uh kind of handshaking, uh, when starting to - uh when you start to communicate with the your T_V_ then then it's like an handshaking protocol with your your remote. So so if two two devices are trying to go to communicate with the T_V_ set then the the the one which has the more energy in the wave is chosen. Well it can be a problem sometimes, but most of the time it works okay.
14:02	So -
14:12	Yeah.
14:14	So -
14:34	Okay.
14:34	The password may simply - uh or uh i- identification code may simply solve this problem. A specific uh remote control has a specific f-
14:42	$
14:44	Yeah but we we don't have to think uh about this because I think as a function designer that we will use the already made uh circuits which we probably bu- buy. It's worth to buy. And they have these problems solved so. So we don't have to think about these.
14:56	Hmm.
15:00	Okay.
15:00	Mm.
15:01	Mm-hmm.
15:01	Okay. So, maybe you can talk about the function, and -
15:02	Okay.
15:05	Yes. I have only a couple of things because I had - I struggled a bit with the software that I'm supposed to use in this uh
15:17	uh
15:19	in this company. I was used to use Linux before, so. But I tried to
15:25	tried to break through this @ too, I guess.
15:35	Open.
15:35	Mm. Ah.
15:35	#
15:37	Okay.
15:40	# How to make it big?
15:44	Slide show.
15:44	Five. @
15:45	Slide show. Okay, thanks. $
15:46	It should work, so you can @.
15:50	Okay. Oh so I will speak about working design. That's the first slide. Uh what uh I have to do? A look at what the other company - Okay so uh presently I am looking what is possible to use, what circuits to use and stuff like that because uh I didn't work uh with these uh circuits so far so I have to look what what is a v- a v- available on the market for for the communication - for the I_R_ circuits and so on, so I'm currently looking what is available on the web. And uh I wanted to ask you m- maybe afterwards, after after our discussion, if we have some contacts in some companies, so, which can report on what is going on there, so, I would be glad if you can tell me about them. So, you know.
16:41	Mm.
16:42	Yeah.
16:46	Uh, okay findings, that's @ the point that I'm working on currently but uh so far I I was uh looking what what are the blue circuit, I mean radio wave - radio frequency circuits* are available now, but the prices I read are high. So, I know that uh the user interface people and these speak about radio frequency waves because you can you can uh you can make the T_V_ do what you want even if you are in the bathroom or so on, but you know, when you are not close to the T_V_ you probably won't need to to change the program and so on and so I am I am voting for s- to stick to the um infra-red control instead of R_W_ but we will discuss it later maybe.
17:01	Mm-hmm.
17:17	Mm-hmm.
17:21	Hmm.
17:41	Uh. Components to use, I'm not exactly sure what I will use for the design of the circuit. It depends uh on whether we will use the L_C_D_ and mainly the speech recognition, because the speech rec- Yeah?
17:51	#
17:57	Are we um are we planning to take an off the shelf an O_E_M_ component for the radio wave circuit, or are we planning to construct our own circuit board?
18:05	No no no no no. This we this we buy I think, because it's rather cheap nowadays and it's not worth to construct ourselves.
18:11	Okay s-
18:12	So we just buy a circuit board and # Okay.
18:14	Exactly.
18:17	But I'm not sure about the circuit which is responsible for speech recognition. This I prefer that we should make ourselves.
18:23	Okay.
18:24	But it depends whether we take a decision to use it. Same thing. It's fairly expensive to use these circuits. So, speech recognition - well, L_C_D_ it's okay because it's common nowadays to use L_C_D_, so I agree on using any kind of L_C_D_, less buttons good for me as a as a designer of the circuit. But the speech recognition we have to compare whether the price and the - what does it offer, you know.
18:35	#
18:44	Yeah.
18:49	Mm.
18:51	Yeah.
18:52	So what do you think would be the price, it would be out of range? Or it would be maybe feasible?
18:54	Yeah, I'm -
18:59	Oh. I was not thinking too much about the price. But if we use the L_C_D_ uh even the radio frequency communication with the T_V_ set and the backlight and uh related things like the photo diodes and stuff, it should be okay. If we decide to use the speech recognition, then we probably could struggle but we'll see afterwards. It depends of you if if the M_E_ or U_I_D_, I'm sorry about the names, I don't really know, uh want to have it like in metal or in plastic, these things, it it depends on you not - Because the the the electronic device's price is not not so big in comparison to to the overall shape and stuff like that, so. We will discuss it afterwards.
19:26	Okay.
19:33	Mm.
19:51	Okay.
19:54	Oh, this is nothing. This is just my notes on what to use. And uh my personal preference is yes, I would like also preferably to use R_W_ circuit, but from the point of view uh of the design and price, I would stick to I_R_s. That's my opinion. Uh I mean if infra-red uh circuit not not the radio frequency.
20:19	Why? Because it's simpler?
20:21	Because because the the range where you can use it is fair. It's okay I think. And the price is fairly cheap for this. Well, depends.
20:25	Yeah.
20:28	Mm.
20:31	Okay. It's a a price matter.
20:35	Yeah.
20:36	Jus- just the price. Otherwise I don't care what I put there because it's the chip which I buy or which we buy.
20:38	Mm.
20:42	Okay.
20:45	So I I I think it's o- y- o- #. Well, three to- three to five. N- not ten times, but it depends what what we -
20:47	What- how much more expensive? Are we talking three times more expensive? Or ten times more expensive? Or -
20:51	@
20:54	Okay.
20:56	Yeah yeah. That's still a lot. I think it's it's probably not worth spending the extra money, because I mean all the other remote controls on the market have infra-red, so people don't expect anything other than infra-red. So it's not worth spending the extra money.
21:00	Hmm.
21:03	Yeah.
21:09	@
21:10	Yeah. Well I @, oh -
21:11	Yeah. Th- they are used to use it when they can see the T_V_ so, I don't know.
21:15	Yeah.
21:15	On the other side, we want to have something new. You know, where
21:19	Yeah.
21:21	we want to
21:23	to have something new and- So we- I think we should still thinking about it. But maybe @.
21:28	But I think, based on my usability studies I th- I feel that users are - prioritise the look and the feel and the trendiness above, you know, the difference between infra-red or radio waves. So I think we're better off spending money in the usability phase.
21:35	Okay.
21:43	@ You the user interface, and management man, uh $ -
21:46	Okay.
21:47	Mm.
21:47	Yeah.
21:49	Okay.
21:51	Uh okay, that's it for me.
21:54	Okay, thank you Peter. So um I have to inform you I receive an email from the management bon- board today and they have new requirements for the for the remote control. Um
21:57	'Kay.
22:11	Mm.
22:14	first um, they say that's uh about something about t- teletext. Uh apparently it becomes from - according to them it becomes out of date. Out-dated. And uh -
22:29	Because of the internet popularity and everybody has internet at home, and
22:35	actually it's not useful to have teletext.
22:39	Um.
22:43	So I think we can avoid the teletext. Um the second thing is uh
22:51	they suggest that that we should uh use the remote control only for T_V_, not for D_V_D_ and other devices, because it make it - it makes it's too complex and uh because we have not much time for this project we should stay on T_V_ on the - only specific T_V_ remote control.
23:12	I agree. $
23:14	The third $ the third one is uh about the the the image of the company. So um uh we should we should keep uh - The the product should be recognisable. Uh, uh
23:35	It's - That mean we should use the colour of our company and maybe put somewhere the s- the slogan of the company, which is uh, we put fashion of - in electronics.
23:46	So, when people see the the remote control, they should say oh it's from Real* Reaction and he s- they should recognise the company.
23:58	So, um -
24:04	So now we we should take the decision what we are going to - what function we will have on this uh on this remote control. So, mm, are we going to use L_C_D_, speech recognition?
24:22	Uh.
24:24	Well, should we start with just the core, the basic functions that we need.
24:29	Yeah.
24:29	And then we can move on to the more advanced features.
24:30	Mm. Yes.
24:30	Maybe, maybe.
24:32	Okay, so the available things are L_C_D_, the buttons and everything. Uh radio frequency depends. And, well the recognition it depends on you guys. You should probably speak.
24:44	Yeah but first maybe what is - what are the usual function of a standard remote control? I mean
24:52	Okay.
24:53	what do -
24:55	Okay, well, I mean the obvious one is changing channels. $
24:56	Yeah.
24:57	Yeah. $
24:58	Yeah. $
25:07	I think we should stick on very useful functions, because we want less button. So, yeah.
25:10	Yeah.
25:13	Yeah, okay.
25:16	So, turning channel, of course. Volume setting.
25:19	@
25:22	Uh just one note to the chan- channel changing. Do we - will we use only two buttons, or or like numbered buttons? I mean those nine plus one or two?
25:33	Yeah.
25:35	Mm-hmm.
25:35	I think it would be a b- @
25:38	Because it's many buttons and we were speaking about lowering the number.
25:42	Mm. @
25:42	Yeah. On the other side we have more and more channels, and if you want to pass through all the channels to get the channel you want, it's -
25:42	Yeah, I -
25:47	Yeah.
25:51	Okay so so we keep all these all these buttons.
25:53	Yeah yeah, at least nine, ten button.
25:53	Maybe maybe we could think of something more betweens*, like
25:58	uh -
25:58	Like ten plus, five plus, one plus, one minus or something.
26:01	Yeah. Maybe something like that.
26:03	Or using the names and the keyboard $ I dunno.
26:04	@ Ah yeah. $
26:05	$ Uh.
26:08	Or -
26:11	Or something @.
26:11	Maybe - Oh I don't know.
26:14	Oh.
26:17	Maybe we could have key* buttons, like uh discovery channe- like documentary* channel, and movies channel and -
26:26	Mm-hmm.
26:26	You mean like hierarchical structure.
26:27	And inside this this thing you can move, maybe switch. If you want to see a movie you click on the movie button so you have all the movie channels and after you've- you plus plus plus. I- It just an idea. I don't know what you think about that but.
26:28	Okay. Like categorising channels.
26:35	Okay, so s- Oh sorry.
26:36	Mm-hmm.
26:38	Okay.
26:41	So it requires the use of L_C_D_ probably, to to tell you -
26:44	To have some feedback. Yeah.
26:45	Yeah, probably, yeah, yeah.
26:46	Okay, so I'll make a note on L_C_D_.
26:46	Mm-hmm.
26:51	We could maybe also c- um incorporate Petre's idea of the um slider for the volume, with the channel. So we c- you could quickly just [whizzing sound] $ through many channels. $ For the channels, perhaps.
26:57	Okay.
26:59	Okay.
27:02	Yeah. Like roller for the - Yeah. Okay.
27:21	# Anything else?
27:23	So we've got channel and volume. Um.
27:25	Yeah.
27:26	So we are still s- speaking about the common devices or we are inviting the new one?
27:28	@
27:31	I think so. I think basically the core functions we want, and then more advanced ones.
27:32	Yeah.
27:37	What about the settings of the T_V_? Because it's button we don't use very often, but
27:43	it's - we need it anyway. So -
27:44	Yeah.
27:44	So uh we don't have any uh we don't have uh - we should just design the remote control and we sh- we don't have any access to the to the T_V_ design or we can change some design. Because one solution for this um uh uh ch- changing channels is to see a summary of all channels, some some preview of all channels and then you can - Yeah. Yeah b- # Not on the control, on the screen, on the T_V_ screen. And then -
28:07	On the screen, you mean? Not on the control, but on the screen.
28:12	Well, this would avoid L_C_D_, then.
28:13	I don't-
28:14	Oh, I don't but I don't think we're we're the ones. I mean this remote control we're developing is a generic control for all T_V_s, I think.
28:21	Yeah, yeah. I don't know if it's possible to to watch something on T_V_ -
28:22	Mm-hmm.
28:23	Oh.
28:26	W- I I think it it would be better to to stick to the remote control and not to bother the T_V_ to to to print these things. Well it wi- it will be still more expensive*, but for the L_C_D_ and this stuff is no problem in the price*.
28:30	Yeah.
28:33	Yeah.
28:33	Mm-hmm.
28:34	@
28:39	Mm-hmm.
28:41	So, what are we doing with the settings? Because settings - if we want to do settings we need buttons for that and we want less buttons, so. Maybe with the L_C_D_ we can do something with less buttons, but -
28:41	Okay.
28:53	Yeah.
28:57	But then you don't want to make the L_C_D_ display too complicated at the same time.
29:00	Mm. $
29:01	$ Two T_V_s.
29:02	$
29:04	I mean there's always - we can always have these l- less often used functions hidden somewhere, under a cover or at the back of - under a slide or some-
29:12	Yeah. Oh yeah. Oh, the @.
29:13	Like ma-
29:15	We we could have for example two buttons like simple mode and advanced mode. $ Or I dunno. Or like children and grandfather's mode, and the, well the the user
29:16	#
29:19	@ $
29:19	$
29:19	Yeah. $ Yeah.
29:23	$
29:24	Mm.
29:26	#
29:29	not the user, the man- mana- T_V_ manager mode $. Ah, I dunno.
29:32	Okay.
29:33	Mm-hmm.
29:34	So we have five minutes left. Um.
29:35	Yeah.
29:37	Uh.
29:37	So I think s- the settings we th- we are agreeing - are agreed that they're required. It's just how to a-
29:43	Mm-hmm.
29:43	Yeah.
29:43	Yeah.
29:45	# We should hide them somewhere. In the menus of the L_C_D_ or in the back of the remote control, or something like that.
29:48	Hide them, okay.
29:49	Yeah.
29:51	Okay.
29:54	Yeah.
29:56	Uh, okay, what else?
30:01	Um.
30:06	I mean a power button's obviously
30:06	@ Yes. $ This I was thinking. Do we need a power button at all? Should should shouldn't we do it like sleep mode after five minutes of not using it? Because generally -
30:09	uh required.
30:18	It's it's a kind of setting, I think. It should fit in those settings functions. Because it's not a very current useful function.
30:21	Mm.
30:23	Settings.
30:28	Uh, well I think when they say power button they mean to turn the T_V_ on and off.
30:34	Yes.
30:34	No, I think it's after after five minutes or something @ a timer - I I think, no?
30:36	Well I I uh-
30:38	But if you're watching T_V_ for two hours, you don't want your T_V_ to turn off after five five minute- $
30:38	#
30:39	$
30:41	$
30:41	You don't need to - every five minutes to keep it alive. Uh probably. Okay, so we should keep this button.
30:41	$
30:43	$
30:44	$
30:48	I mean based on our usability studies again, um # pe- um people said that the power button was v- a very relevant button. Um, you know, it was nine out of ten
30:48	Yeah.
30:54	Oh okay, yeah.
30:56	Mm-hmm.
30:58	Okay, so we we could p- what we could probably do is to keep also to keep uh keep the L_C_D_ and all the buttons and stuff, we could make it like a opening opening style that if you open it you are - you just turn on the T_V_ and if you close it, it will
30:59	re- relevance.
31:11	Yeah.
31:17	Yeah.
31:17	@
31:18	turn off the T_V_. If if you like this, #
31:20	Okay.
31:21	B- Okay.
31:23	Because, well @ - it's maybe question for you t-
31:25	I think we need to concentrate on the, you know, the major usage of the th- of the control, which is you sit down, you turn on your T_V_, you change channels, you change the volume, you turn the T_V_ off. Um and all the other f- functionality is
31:27	Mm-hmm.
31:30	Yeah.
31:37	Yeah. So s- yeah.
31:43	#
31:43	Yeah, they can yeah they can be hide somewhere by a cover or something like this. Like covering cu-. Yeah, like mobile phone covering.
31:43	not used very often.
31:47	Yeah.
31:48	Yeah.
31:50	On the back, or -
31:50	Yeah. I mean like the -
31:53	Yeah but since we have the L_C_D_, we didn't need too much button- too many buttons.
32:01	#
32:01	Um, okay, just um the decision of the power button. Should we make it a button, or some some something which would be -
32:11	For what?
32:12	Uh power button.
32:12	I think a button.
32:13	A button is better.
32:14	I think it should be a bu-
32:15	Ah oh yeah, yeah. Yeah a button, yeah I guess so.
32:15	If it if it's a button or - Okay.
32:16	Yeah.
32:17	Its own button on the front.
32:18	Mm.
32:20	Okay, one nice big button. Old fashioned button, to satisfy the grandmothers.
32:22	$
32:24	$
32:24	$
32:27	$
32:27	$
32:27	$
32:29	Hmm.
32:32	Okay.
32:34	Mm.
32:34	S-
32:34	So, any other suggestions or functions?
32:48	What about things like the clock and um timers?
32:54	Do we still have the time? I I just wonder.
32:56	Yeah, we have still one or two minutes to talk, yeah.
32:58	Okay.
32:59	Oh. Well what w- what was the question?
33:01	Clock* or -
33:01	Uh um, you know, some func- some features on the control to display a time, or t- to display -
33:07	Usually it's already on T_V_ or something like that.
33:10	Yes.
33:11	Yeah but since we want to control all the televisions,
33:17	and and it would probably be worth to to set the timing on the remote, no?
33:17	Yeah.
33:24	Because if if the T_V_ turns on itself, it well you know, if the time- The timer should be there.
33:24	Mm.
33:26	Yeah.
33:29	Yeah. If we if we add the time, we have to have maybe a bigger display or something like that, and is it very useful? I mean, are users wants to have the time on the on the remote?
33:44	Mm.
33:44	Probably not. It's a questi- yeah, it's a trade-off.
33:44	This is the question. Is it useful?
33:46	Yes.
33:47	W- In my opinion we should have only useful thing and- Because apparently they want - The simpler it's* is better.
33:52	'Kay.
33:54	Ah, yeah.
33:55	Okay simple.
33:56	Did you did you ever use the- like the timing of turning on the T_V_, well - And based on your -
34:00	$
34:01	$
34:01	$
34:03	Very, yeah okay, very occasionally. But I do use the I do use the display of the time quite often, but -
34:05	#
34:09	Mm.
34:09	Yeah but it can be on the display in in a corner all the time on the remote.
34:12	Yeah.
34:13	#
34:14	Yeah that's okay, that's true. Okay, so no time button @. Okay.
34:17	No time on @.
34:18	@
34:18	And uh do we need to include anything about the speech recognition and the speech commands, or?
34:22	Yes yes.
34:24	I think -
34:25	I I thin- I think it will not take lots of place, we just need a microphone and the software, so, and it sh- and it will be a little bit new and interesting, so people may be attracted to buy this stuff and it's not very difficult to uh put a software inside the the electronic device and put a microphone*. It doesn't take that much place and also that much - It doesn't cost that much.
34:52	Yeah but we we should be careful about the battery life, then. If we use the speech recognition.
34:52	Yeah.
34:57	# So maybe we think - we can think more about that, and discuss that maybe last time - next time. And uh yeah, now the meeting room is busy. Somebody booked the meeting room just for - at one P_M_, and so we should leave.
35:02	Mm-hmm.
35:03	# Yeah.
35:13	Uh.
35:16	So, um. So now we are going for for a small lunch. It's uh funded by the company. And uh after we have uh thirteen minutes to to do indevel- individual works. And uh I will do the minutes. And uh
35:38	you are going to work on your individual works. And uh you will receive as usual your specific instruction and so on. Thank you everybody.
35:47	Okay, cool. Okay
35:51	Thanks.
35:52	Thank you.

---