Right now, Mr Rambonnet's JJR-Sandify160 is playing. Queued after that is JJR-Sandify169...but first, of course (after carving up the beautiful doily with THE FERSHLUGGINER CONNECTING LINE back to rho=0) JJR-Sandify160 is REPLAYING. Cue "Arghh".

Maybe JJR-Sandify169 will play next. I hope so. Maybe it will play only once. All right, fine. I'll have another cocktail.

I also hope that this bug feature is moved to the very tippy-top of the action list up there in Marc-Andre Fleury's new home. I'm more than irritated and on the verge of jettisoning the urbane, genteel civility for which I am renowned*.

*On Planet Zyrgnñax in a galaxy far, far away.

I have created a simple two track playlist. The first track was written to begin at rho = 1 and end at rho = 0. The second track, (from Mr Rambonnet) was written to begin at rho = 0 and end at 1. In the playlist, though,  both tracks are supposed to run in reverse.

However, when I start the playlist with the ball at the center, the table first moves the ball to the perimeter, ignoring my instructions, as well as the notations in the app. (See attached).

Why is this so difficult? Why can we not have a command which simply states "play this track from the current ball position"?

But wait...there's more!

Sometimes, the table repeats a track when I have not specified that it should. This is particularly infuriating when I play one of jjr's doilies, and after waiting an hour, return hoping to see the lovely result, only to find the pattern spoiled by the ball plowing its way back to rho=0 to begin again.

Both problems are sporadic  

Arghhh.

I have tracks which are written to run from rho=1 to rho=0, and sometimes want to play them in reverse, but even when such a track has the "reversible" bit set in the app, the bot will often "insist" on running it as non-reversible. The result: starting with the ball in the center, instead of running (as desired) from rho=0 to rho=1, the bot will seemingly ignore the reversible bit and take the ball out to rho=1, and play the track from there! In other instances, the bot first takes the ball to rho=1 and then back to 0 before playing the track. There seems to be neither rhyme or reason in this behavior.

I will welcome an option in the app to force a track to run from the current ball position (with the exception, of course, of those tracks which by their nature cannot be reversed: those that are written to both begin and end at rho=1 or rho=0).

If I am nuts, or am overlooking something obvious, I know someone will apply the cluestick. 

Something is evidently b0rked, because the table (or app) does not recognize that the firmware has already been updated.

A certified bug it is. 

I have the table scheduled to sleep at 10pm and wake up at 6am. 

I have the option configured to pause between tracks for 5 min.

If the table is in a pause when it goes to sleep (at 10PM) it will not wake up at 6am. I have to hit play in the app.

Uncaught TypeError: Cannot read property 'split' of undefined - file:///android_asset/www/prod/models.js 2895

I get 2-3 of these in a row which I dismiss, after which the interface for the home and library tabs shows no tracks. If I kill the app I can see the tracks again until I get the error. Android 11 on a Pixel 4. 

"Error: The old format of this exec call has been removed (deprecated since 2.1). Chagne to: cordova.exec(null, null, 'Service', 'action', ); - file:///private/var/containers/Bundle/Application/273348F3-920B-494F-8467-0206D54E5255/Sisyphus.app/www/plugins/cordova-plugin-wkwebview-engine/src/www/ios/ios-wkwebview-exec.js - 104"

This error does not prevent me from downloading new tracks 100% of the time. Around every 10 to 15 tries I will hit this error message, but the track also successfully downloads. Most of the time when I see this error, the track does not download successfully. Either way, this error has effectively halted my ability to download new tracks.

I am using firmware version 1.10.70 on my metal coffee table.

Anyone else have this problem or know of a work around?

1. I tried setting a sleep time for night mode, with no wake time as I'm usually gone most of the day so I wake it when I'm home.  If night mode is enabled in this way, my table always wakes up at exactly 12 midnight.  It's done that through a few firmware updates

2. Occasionally when it's been sleeping for a while - at least a few hours but more likely if overnight - I will hear it making little motor noises just as it does when it's running but quieter, like barely audible.  Waking and sleeping it again will silence it for a while  

Neither is really a problem, just curious 

¯\_(ツ)_/¯

Does the table also sync with an Internet time server? I'm not even seeing a place where I could set the time or timezone if I wanted to.