Mobile suggestions

[just1man]

Enjoying the mobile usage a lot. Couple additional suggestions:
1) would be handy on the mobile app to be able to see the current artist and song, and less important, the assigned dance. If space is a concern, maybe volume and speed sliders could be moved to right and left of Play/Pause, etc. buttons?
2) be able to change/add a dance and rating from the browser version, similar to the QuickPlay menu where choose the Dance/Rating from a dropdown list - betting this would be challenging
3) what are your thoughts on creating a view-only web page dance participants could go to (different port than 9010, and no login required) so they could see, essentially, the marquee info? That way, if there isn't a projector/screen, people from anywhere in the hall could look up what is coming (maybe even next 10 dances and songs)? Just a thought - most useful in a situation where a playlist is set up, and just "runs" vs actual DJ. Could even have a little advertising image of the DJ, The difficulty here would be everyone needing to connect to the DJ's wifi - may be too technical for most people.

Low priority stuff for sure, but would be nice adds i think.
Cheers - thanks for all the work.

[bll]

For (1):

Something like this...

remdraft1.png (127.56 KiB) Viewed 33375 times

[bll]

#3

It's really sad.
It appears that neither the android nor the iphone (not entirely sure about it) support resolving multicast DNS .local addresses.
So I can't use http://bll-g7.local:9010 as a URL to put into the mobile phone and for which to print a QR code.
Which would be much, much better than using the IP address as it is now.

The problem being that every time I visit a studio and hook into their WiFi network, I may get a different IP address.
Which means I would need a new QR code for the dancers to scan.

The QR code idea will still work. It's just a problem if the computer running BallroomDJ gets a new IP address.

[bll]

It seems that (3) is rather more difficult than anticipated.
There are two main scenarios:

(a) The dance studio has its own wi-fi. The DJ has access to it, whereas the patrons may or may not have access.
The DJ's computer may not have the same IP address each time it is set up.

I think that in this case, sending the marquee data via the internet to the ballroomdj.org server,
and having the patrons connect via the internet to ballroomdj.org to view the marquee changes
would work. The DJ would print a QR code that the patrons can scan to connect.

Requirements:
- BallroomDJ has the mobile marquee set up to connect to the internet.
There is a unique id entered by the DJ that identifies the marquee that BallroomDJ connects to.
The BDJ player will send the marquee to ballroomdj.org whenever it changes.
- On ballroomdj.org, a program must be written to (a) accept marquee information from BDJ,
and (b) display the marquee to a dancer when they connect.
- A QR code will be printed that the dancers can scan. This will be something like:
https://ballroomdj.org/marquees/justdanceoakland , where 'justdanceoakland' is the identifying
tag entered into the configuration.
(May be able to use the sourceforge web server, which would be more robust).

(b) The dance venue does not have wi-fi.

The DJ would set up a wi-fi router at the dance venue. The DJ's computer would have a static IP address
assigned so that the DJ does not need to print a new QR code each time. The wi-fi is set up as open access,
no password, so that most mobile phones would automatically connect.

The dancers would connect to the DJ's wi-fi router, scan the QR code and view the mobile marquee.

Requirements:
- BallroomDJ has the mobile marquee set up to connect locally.
- A mini web server is started when BDJ starts that the dancers can connect to.
- A QR code will be printed that the dancers can scan. This will look like:
http://192.168.1.70:9009
- There are still some issues dealing with authentication that have to be figured out.
If the DJ has already connected to the 9010 port, the authentication information gets sent (authentication
is per IP address, not per port). I have a work-around for this.
But I have to do some further testing with connecting to the 9009 port fresh without any authentication and
make sure that my mini web server handles it properly.

[just1man]

For (1):

Something like this...

remdraft1.png

Yep, that would be great, thank you!

[bll]

#3 (b):

The "Local" mode is working on Windows.
I just tested with about 50 connections at once (from Linux to a Windows 10/32 VM), and it seems to work fine.
CPU usage was about 14% on the Windows VM.

I still have to write the "internet" version of the mobile marquee.

[bll]

#3, The "mobile marquee" is implemented with version 3.31.0 .

[bll]

I should have said both #1 and #3 are implemented in version 3.31.0 .

#2, being able to select a dance and play needs to be defined better.

The easiest way is to have this mode only work when the quickplay tab is open.
quickplay already has a method to play a particular dance, and receiving a message
to play a particular dance would not be too difficult.

An alternative possibility is when the player is open.
A special type of "request" that randomly chooses a song at random could be processed,
and the song moved to the top of the music queue.

One of the issues with putting a dance selection on the mobile remote control web page is
that different BallroomDJ users are going to expect different actions to happen.
A user might expect one of the two possibilities above, or something else I haven't thought of.

[bll]

The internet version of the mobile marquee is finally working properly in version 3.31.2.
Unfortunately, I broke the HTML code for the local mobile marquee, but that's fixed in 3.32.0.

Version 3.32.0 has a revamped quickplay screen, and the mobile remote control
has the ability to perform quickplay actions.

Let me know if the new mobile remote control suits your needs.