Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[skarsol]

A large percentage of the time (especially when it is started automatically, like from a command from my watch) Gizmo will hang at "Connecting..." with a cancel button. If I hit cancel and then Go, it connects quickly, and none of the messages in that process are "Connecting...". Is there a way to see why it's getting stuck there? Is this something I can change on the media server end to resolve? I don't see any option in Gizmo to address it.

[JimH]

The drive on the server may need to spin up.

[skarsol]

The OS/App drive on the server is SSD. The drives the files are on are spinning disks though, but they never spin down. Would that show in the JRiver logs?

When I manually start Gizmo, it does "Looking up access code" then "Attempting connection to XXXXXX" then "Completing connection". If my connection is spotty, it will go through a cycle of the attempting connection dialogs while it tries different IPs (due to NAT). I only ever see the "Connecting..." dialog when Gizmo is start by a different app/process than me manually touching the icon, and once it is in the "Connecting..." state, it will never resolve until I hit cancel. It seems like it might be taking a different code path when not opened manually?

[skarsol]

FYI I've given up on trying to get music to stream to Gizmo automatically when entering the car.

[JimH]

Did you ever try telling MC to cache some songs?  It's in the Gizmo settings.

[skarsol]

Yes, the issue is that I can't get gizmo to connect to my home server automatically most of the time. So regardless of the state of the cache, it never gets there.