All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Mort <gary@mort.net>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: 3dsp sample app and Bluez v5
Date: Tue, 2 Jun 2015 00:26:42 -0400	[thread overview]
Message-ID: <556D3082.5060403@mort.net> (raw)
In-Reply-To: <4CBFCC0A-794F-4F78-A499-DFD083F29378@holtmann.org>



On 06/01/2015 09:13 PM, Marcel Holtmann wrote:
>>> Also I would really urge to read the 3DSP specification and understand that the only thing 3DSP is doing is synchronising shutter timings.
>> That's all you need to make a pair of "Joo Janta 200 Super-Chromatic Peril Sensitive Sunglasses"...well that and some form of 'agitation' sensor[ie blood pressure, pulse, heart rate, etc].
>>
>> Instead of running them as alternating 3D, I plan on running them as 'two player mode' and then I just need to control the time period they are "open" for based on agitation such that the more 'peril' you are in, the better they will shield you from actually observing the danger - a real life saver when faced with the Ravenous Bugblatter Beast of Traal and much cooler looking then a silly towel.
>>
> If you want to control the glasses from a different machine, then you also need to get the Bluetooth clock information. Getting the proper clock in relation to the frame sync signal is hard. Normally it means you need some sort of extra wired trigger signal.


I'm going to take a guess that you have never read Douglas Adams 
Hitchhikers Guide to the Galaxy?

The sunglasses I'm referring to are a comic device designed "keep the 
user calm" when they are in danger.  To do this, they darken, eventually 
to the point of pitch black, so as to keep the wearer from seeing the 
danger[and thus the wearer is not frightened].

I don't need to get a clock in relation to the frame sync signal - 
instead I am creating a fake timing signal.  To use large, unreasonable 
numbers:  The base signal would be designed for a perfect 50/50 split on 
open and closed.

Using a pulse monitor, as the users pulse increases, the ratio is 
modified.  Ideally, it would scale from 
50/50...40/60...30/70...20/80...10/90...0/100

In this case, the open/close ratio is not being used to create a 3D 
effect - instead it is used to create a set of computer controlled 
variable sunglasses[over incredibly short periods of time, there is not 
much difference between glasses which absorb/reflect 80% of all incoming 
light or glasses which block 100% of incoming light 80% of the time]

Note: based on my reading of the 3DS spec, 0/100 is likely not possible 
- if the frequency for shut/open exceeds certain limits, then the 
glasses are supposed to open both shutters and ignore the timing 
information.   However, just because they are supposed to do that 
doesn't mean they do, so I can start with a a "reasonable" fake timing 
schedule and play from there.

While all of this is for learning and my own personal amusement, there 
actually is a real world use case - some people promote using glasses 
which obscure part of your vision in one eye in order to "exercise" the 
eye....mind you the people promoting this seem to be peddling very 
expensive custom designed glasses..  If I can get a reasonable range of 
shutter timing for cheap 3d glasses, it would be relatively simple to 
then port that over to a smartphone application so instead of spending 
lots of money on these glasses, people can use a cheap pair of 3DS 
bluetooth glasses.

  reply	other threads:[~2015-06-02  4:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-01 21:05 3dsp sample app and Bluez v5 Gary Mort
2015-06-01 21:23 ` Marcel Holtmann
2015-06-02  0:09   ` Gary Mort
2015-06-02  1:13     ` Marcel Holtmann
2015-06-02  4:26       ` Gary Mort [this message]
2015-06-02  5:00         ` Marcel Holtmann
2016-08-08 15:50           ` Bastien Nocera
2016-08-17  3:03             ` Gary Mort
2016-08-17  3:33               ` Gary Mort

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=556D3082.5060403@mort.net \
    --to=gary@mort.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.