Patent Application
20200379641
The present disclosure relates to a media player and a method of operating a media player.
Various different types of media player, that is, a device that is able at least to play back media, are known. The media may be for example audio only, or video or still images only, or video/still images and audio. The media may be in digital form. The media may be stored on the device and/or streamed to the device from some server or other storage, over for example the Internet or a local area network, etc.
Many media players have a touchscreen. The touchscreen enables video and still images to be displayed by the device, and also provides an interface by which a user can input commands to the device by “taps” (a typically rapid, brief touch on the screen, typically by a user's digit such as a finger or some other input device) or a “swipe” (which is typically brought about by a user's digit or other input device touching the screen and then being drawn along a portion of the screen before being released from contact with the screen).
According to a first aspect disclosed herein, there is provided a media player for playing media, the media player comprising:
a controller; and
a touchscreen operable to receive a touch input and configured to output corresponding touch input data to the controller;
the controller being configured to control the media player in accordance with touch input data received from the touchscreen;
the controller being configured such that, in the case that the touchscreen is in an inactive display state and touch input data received from the touchscreen indicates that the touch input concerns a media control function, the controller operates to control the media player in accordance with the touch input data received from the touchscreen without causing the touchscreen to enter an active display state.
In examples, a user can control the media player (or control the media player functions in the case that the media player is part of some other device, such as a smartphone, etc.) without waking the screen and therefore without using electrical power unnecessarily.
It may be noted that in general and in some examples, in the inactive display state, which may be regarded as a power-saving state, the touchscreen is not displaying any image at all or may be displaying an image at a dim or reduced brightness. In the inactive display state, the media player, and in particular the touchscreen, may or may not be able to receive and act on touch inputs, depending on the set up of the media player. On the other hand, in general and in some examples, in an active display state, the touchscreen will typically be displaying an image (at high or full brightness) and is able to receive and act on touch inputs, i.e. is responsive to a touch input.
In an example, the touchscreen has plural touch-sensitive input regions, the different touch-sensitive input regions being associated with different media control functions. As just one example, one touch-sensitive input region might be associated with a “play” control and a “pause” control and another touch-sensitive input region might be associated with a fast forward control and a fast backward or rewind control.
In an example, the media player is configured such that a double-tap on the touchscreen is required as a touch input for at least one media control function in order to cause the touchscreen to output corresponding touch input data to the controller. This can help to avoid or minimise inadvertent or unintentional control of the media player functions.
In an example, the media player may be configured such that the touchscreen is responsive to a tap on the touchscreen when not in the active display state. This is particularly useful when a double-tap is required as this tap can be the first tap of a double-tap. The touchscreen may be for example be continuously responsive or periodically responsive to a tap on the touchscreen when not in the active display state.
In an example, the media player comprises a movement sensor configured to be responsive to movement of the media player as a result of a tap on the touchscreen. This is particularly useful when a double-tap is required as this tap can be the first tap of a double-tap. The movement sensor may be for example one or more of an accelerometer and a gyroscope.
In an example, the media player comprises a proximity sensor configured to be responsive to proximity of a user's digit or other input device during a tap on the touchscreen. This again is particularly useful when a double-tap is required as this tap can be the first tap of a double-tap.
In an example, the media player is configured such that two simultaneous touches of the touchscreen is required as a touch input for at least one media control function in order to cause the touchscreen to output corresponding touch input data to the controller.
According to a second aspect disclosed herein, there is provided a method of operating a media player which has a touchscreen, the method comprising:
putting the touchscreen in an inactive display state;
receiving a touch input whilst the touchscreen is in the inactive display state;
determining that the touch input concerns a media control function; and
controlling the media player in accordance with the touch input data received from the touchscreen without causing the touchscreen to enter an active display state.
To assist understanding of the present disclosure and to show how embodiments may be put into effect, reference is made by way of example to the accompanying drawings in which:
As mentioned, various different types of media player, that is, a device that is able at least to play back media, are known. The media may be for example audio only, or video or still images only, or video/still images and audio. The media may be in digital form. The media may be stored on the device and/or streamed to the device from some server or other storage, over for example the Internet.
The media player may be a dedicated media player, which is only able to operate as a media player, i.e., can play back media, with other related functions such as pause, rewind, fast forward, skip forward to the next track or backwards to the previous track, volume control, etc. The media player may be part of or built into some other device that can perform other functions, such as a personal computer, a tablet computer, a smartphone, a so-called “phablet” (a large smartphone, having a size that is more like the size of a typical tablet computer), etc.
Many media players have a touchscreen. The touchscreen enables video and still images to be displayed by the device, and also provides an interface by which a user can input commands to the device. The commands may be input for example by “taps” (a typically rapid, brief touch on the screen, typically by a user's digit such as a finger or some other input device such as a stylus) or a “swipe” or “slide” (which is typically brought about by a user's digit or other input device such as a stylus touching the screen and then being drawn along a portion of the screen before being released from contact with the screen), etc.
It is common for the screen of a media player to be put into some inactive or power-saving state after some period of time following an input to reduce power consumption. This is particularly important for battery-powered media players in order to prolong battery life. For example, the screen may be put into a state where it is completely blank and not displaying any image. As another example, the screen may be put into a state in which the brightness is reduced compared to a full or high brightness “active” state. In the case of the screen being a touchscreen, the touchscreen may or may not be able to register and act on touch inputs whilst in the inactive or power-saving state, depending on the set-up and configuration of the device. In general, this state of the media player will be referred to herein as an “inactive display state”, recognising that whilst the display is in some power-saving mode and may be displaying no image or displaying an image at reduced brightness, the touchscreen may or may not be able to register touch inputs depending on the set-up of the device.
In contrast, in an active display state, the screen is displaying an image (possibly at full or high brightness, in contrast to a dim screen in a power-saving inactive display state). Moreover, typically and in the case of the screen being a touchscreen, the touchscreen is able to register and act on touch inputs, i.e. the touchscreen is responsive to a touch input, whilst in an active display state.
A problem is that in order to control operation of a media player that uses a touchscreen for receiving control inputs for controlling the media player, the user has to touch the touchscreen (again, using for example a finger or some stylus or other input device). But in many existing media players, including in particular smartphones or tablets or the like that have a media player function, touching the touchscreen whilst the screen is in an inactive display state may have no effect whatsoever: the user often has to press some button in order to “wake” the screen in order for the touchscreen to be responsive to touch inputs. In other existing media players, including in particular smartphones or tablets or the like that have a media player function, touching the touchscreen whilst the screen is in an inactive display state may be sufficient to cause the touchscreen to be responsive to touch inputs. However, in either case, causing the touchscreen to become responsive to touch inputs results in the screen entering an active display state in which the screen is displaying images (possibly at full or high brightness). The media player is therefore consuming electrical power at a high level, even though the user may for example simply have wanted to increase the volume of an audio track being played back, or fast forward to the next audio track, etc.
In examples described herein, a media player for playing media has a controller and a touchscreen operable to receive a touch input and configured to output corresponding touch input data to the controller. The controller is configured to control the media player in accordance with touch input data received from the touchscreen. The controller is configured such that, in the case that the touchscreen is in an inactive display state and touch input data received from the touchscreen indicates that the touch input concerns a media control function, the controller operates to control the media player in accordance with the touch input data received from the touchscreen without causing the touchscreen to enter an active display state. Accordingly the user can control the media player (or control the media player functions in the case that the media player is part of some other device, such as a smartphone, etc.) without waking the screen and therefore without using electrical power unnecessarily.
Referring now to
The media player 1 has a touchscreen 2. The touchscreen 2 may be for example a capacitive touchscreen or a resistive touchscreen. The media player 1 may have one or more control buttons 3 which the user must press to activate the relevant control. The media player 1 has a controller 4, which may be implemented by one or more processors. The media player 1 has some form of storage (not shown), at least for temporarily storing files, such as media files, and which may be permanent storage for permanent storage of files, such as media files. The media player 1 has some form of memory (not shown) for running programs under control of the controller 4. There will typically be some form of controller or control circuitry for controlling operation of the touchscreen 2, including providing image data to the touchscreen 2 for display, receiving and processing touch inputs received at the touchscreen 2, etc. The controller for the touchscreen 2 may be provided as part of the main controller 4 or as a separate controller for the touchscreen 2.
The media player 1 may also have for example transceiver circuits and processors and the like to enable the smartphone/media player 1 to connect wirelessly via WiFi, Bluetooth, etc., to a network. In the case that the media player 1 is provided as a function on a smartphone or the like, the smartphone/media player 1 will have transceiver circuits and processors and the like to enable the smartphone/media player 1 to connect to a cellular network.
The media player 1 is arranged to enter some power-saving mode if the media player 1 or at least the touchscreen 2 has not been used for a certain period of time. This is particularly important in the case that the media player 1 is battery-powered in order to prolong the battery life, i.e. the time before the battery is exhausted and needs recharging. As a particular example, if no touch input has been received by the touchscreen 2 for a certain period of time, the touchscreen 2 enters an inactive display state. For example, the touchscreen 2 may be put into a state where it is completely blank and not displaying any image. As another example, the touchscreen 2 may be put into a state in which the brightness is reduced compared to a full or high brightness “active” state. The touchscreen 2 may or may not be able to register and act on touch inputs whilst in the inactive or power-saving state, depending on the set-up and configuration of the media player 1.
In addition, as well as the touchscreen 2 being in an inactive display state, the media player 1 as a whole may be in some deeper sleep or idle state. As a particular example in the case of the media player 1 being a smartphone or the like, as well as the touchscreen 2 being in an inactive display state, the smartphone/media player 1 as a whole may be in some idle state or some other low power state in which signalling with the cellular network is low or minimal.
In contrast, in an active display state, the touchscreen 2 is displaying an image (possibly at full or high brightness, in contrast to a dim screen in a power-saving inactive display state). Moreover, the touchscreen 2 is able to register and act on touch inputs, i.e. the touchscreen 2 is responsive to a touch input, whilst in an active display state.
The media player 1, in particular the controller 4, is configured such that, in the case that the touchscreen 2 is in an inactive display state and touch input data received from the touchscreen 2 indicates that the touch input concerns a media control function, the controller 4 operates to control the media player 1 in accordance with the touch input data received from the touchscreen 2 without causing the touchscreen 2 to enter an active display state. The media control function may be for example one or more of play, pause, rewind, fast forward, fast backward or rewind, skip forward, skip back, volume up or down, etc.
The media player 1 may be configured so as to respond to different types of touch input on the touchscreen 2 corresponding to different types of media control functions. Some specific examples of this are described further below.
In general though, the media player 1 may be configured for example such that a double-tap on the touchscreen 2 is required as a touch input for at least one media control function in order to cause the touchscreen 2 to output corresponding touch input data to the controller 4. Requiring a double-tap can help to avoid or minimise inadvertent or unintentional control of the media player 1 and activation of the touchscreen 2 to an active display state. A double-tap can be differentiated from two successive single taps (which may control some other function of the media player 1 or device more generally) by for example measuring a time difference between two taps detected by the touchscreen 2 and deciding whether this time difference is above or below a time threshold.
The media player 1 (in particular the main controller 4 and/or a dedicated controller for the touchscreen 2) may be configured such that the media player 1 is responsive to a (single) tap on the touchscreen 2 when not in the active display state. This is particularly useful in the case that a double-tap on the touchscreen 2 is required as a touch input for at least one media control function in order to cause the touchscreen 2 to output corresponding touch input data to the controller 4, as it enables the media player 1 to register the first tap of the double-tap. A number of ways of achieving this are possible.
For example, the touchscreen 2 may be responsive to a (single) tap on the touchscreen 2 when not in the active display state. The touchscreen 2 may for example be continuously responsive or periodically responsive, the latter resulting in greater power savings when the media player 1 is not in an active display state.
Alternatively or additionally, the media player 1 may have a movement sensor which is configured to be responsive to movement of the media player 2 which occurs as a result of a tap on the touchscreen 2. The movement sensor may be for example one or more of an accelerometer and a gyroscope.
Alternatively or additionally, the media player 1 may have a proximity sensor which is configured to be responsive to proximity of a user's digit or other input device during a tap on the touchscreen 2.
In general, the media player 1 may alternatively or additionally be configured such that two simultaneous touches of the touchscreen 2 is required as a touch input for at least one media control function in order to cause the touchscreen 2 to output corresponding touch input data to the controller 4. This can again help to avoid or minimise inadvertent or unintentional control of the media player 1 and activation of the touchscreen 2 to an active display state. The two simultaneous touches of the touchscreen 2 may be achieved by for example touching the touchscreen 2 with two fingers or other input devices simultaneously.
The touchscreen 2 may be (notionally) divided into two or more regions. In the example shown in
The correspondence between different regions 2A, 2B, 2C of the touchscreen 2 and certain media control functions or set of media control functions may be arranged in one of numerous different ways. As just one specific example to illustrate this:
first region 2A performs “skip to next” function with double tap with two fingers
first region 2A performs “fast forward” function with double tap and hold with two fingers
second region 2B performs “play/pause” function with double tap with two fingers
third region 2C performs “skip to previous” function with double tap with two fingers
third region 2C performs “fast backwards” or “rewind” function with double tap and hold with two fingers
As further examples of different touch inputs for different media control functions, the media player 1 may be configured such that for example sliding two fingers from the bottom to the top of the touchscreen 2, or at least generally from the bottom to the top of the touchscreen 2, performs a “volume up” function. Likewise, in an example, sliding two fingers from the top to the bottom of the touchscreen 2, or at least generally from the top to the bottom of the touchscreen 2, performs a “volume down” function.
At 20, the media player 1 is in an inactive display state and is responsive to a single tap on the touchscreen 2. (As discussed above, this may be by virtue of the touchscreen 2 being responsive to touch inputs and/or by the user of movement or proximity sensors, etc.)
At 22, it is determined whether or not a tap is detected. If a tap is detected, flow moves to 24. Otherwise, the media player 1 remains at 22 and continues to determine whether or not a tap is detected.
At 24, it is determined, in this example, whether the tap is with two fingers. If not, flow returns to 22. If yes, flow passes to 26.
At 26, it is determined which region 2A, 2B, 2C of the touchscreen 2 has been tapped. If it is the first region 2A, flow passes to 28.
Continuing the flow from 28, the media player 1 waits for a second tap. If a second tap is detected at 30, flow passes to 32; otherwise, if no second tap is detected (within for example a predetermined period of time), then flow returns to 20 described above.
At 32, it is determined whether the second tap which has been detected is a tap in the same region as the previous, first tap, in this example the first region 2A of the touchscreen 2. If not, then flow returns to 20 described above. If yes, then flow continues to 34.
At 34, it is determined whether the user's fingers or other input device are still touching the touchscreen 2. If no, then it can be concluded that the input to the touchscreen 2 by the user is a double-tap on the first region 2A of the touchscreen 2. In accordance with the specific example discussed above, this corresponds to a “skip to next” media control function 36. The controller 4 then controls playback of the media accordingly.
If at 34 it is determined that the user's fingers or other input device are still touching the touchscreen 2, flow passes to 38. At 38, it is determined whether the user's fingers or other input device are moving up or down along the touchscreen 2. If not, then this is determined to be a “hold”. As such, in accordance with the specific example discussed above, this corresponds to a “fast forward” media control function 40. The controller 4 then controls playback of the media accordingly.
On the other hand, if at 38 it is determined that the user's fingers or other input device are moving up or down along the touchscreen 2, then, accordance with the specific example discussed above, this corresponds to a “volume up” or a “volume down” function respectively, and the controller 4 controls the playback volume from the media player 1 accordingly.
If at 26 it is determined that it is the second or third region 2B, 2C of the touchscreen 2 that has been tapped, a similar logic flow proceeds, resulting in, in this example, one of a “play/pause” function, a “skip to previous” function, a “fast backwards” or a “rewind” function, and a “volume up” or a “volume down” function. This is shown clearly in
It will be understood that the processor or processing system or circuitry referred to herein may in practice be provided by a single chip or integrated circuit or plural chips or integrated circuits, optionally provided as a chipset, an application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), digital signal processor (DSP), graphics processing units (GPUs), etc. The chip or chips may comprise circuitry (as well as possibly firmware) for embodying at least one or more of a data processor or processors and a digital signal processor or processors, which are configurable so as to operate in accordance with the exemplary embodiments. In this regard, the exemplary embodiments may be implemented at least in part by computer software stored in (non-transitory) memory and executable by the processor, or by hardware, or by a combination of tangibly stored software and hardware (and tangibly stored firmware).
Reference is made herein to data storage for storing data. This may be provided by a single device or by plural devices. Suitable devices include for example a hard disk and non-volatile semiconductor memory.
The examples described herein are to be understood as illustrative examples of embodiments of the invention. Further embodiments and examples are envisaged. Any feature described in relation to any one example or embodiment may be used alone or in combination with other features. In addition, any feature described in relation to any one example or embodiment may also be used in combination with one or more features of any other of the examples or embodiments, or any combination of any other of the examples or embodiments. Furthermore, equivalents and modifications not described herein may also be employed within the scope of the invention, which is defined in the claims.
| Number | Date | Country | Kind |
|---|---|---|---|
| 17166189.5 | Apr 2017 | EP | regional |
This application is a US 371 Application from PCT/EP2017/075495 Oct. 6, 2017, which claims priority to EP Application 17166189.5 filed Apr. 12, 2017, the technical disclosures of which are hereby incorporated herein by reference.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/EP2017/075495 | 10/6/2017 | WO | 00 |
