Open GoogleCodeExporter opened 9 years ago
Hi,
Sorry for the slow reply. I have just moved house and it has taken me six
weeks to get the cable reconnected.
I have just updated itunes to 11.0.1 and am not having any issues connecting
with tunesremote-se.
Are you able to test the connection with either the Apple Remote App for
iPhone/iPod Touch/iPad? Or failing that one of the clients for android phones?
Regards
Nick
Original comment by nick.gl...@lycos.com
on 5 Jan 2013 at 5:44
no problem, slow on my side too...
went back to 10.x for other reasons, but have another installation with 11 and
that doesn't show up in the list either (all firewall disabled, home-sharing
works. appleTV works ipad remote works).
the machine with the 10.x now works without any other changes.
RCadmin
Original comment by ad...@runningcontacts.net
on 12 Jan 2013 at 11:53
Hi,
I seem to have the smae problem. One Server has Mountain Lion 10.8.2 and iTunes
11.0.1 (12) (64-bit) running. The other server is Windows 7 64-bit with iTunes
11.0.1.12. Firewalls are disabled on both servers. Homesharing via Apple Remote
App works fine on iPhone.
Tunesremote-SE r108 won't list any of the iTunes Library. Firewall is disabled.
But Can connect from iTunes via homesharing.
Any ideas?
Thanks,
toffi
Original comment by toffimei...@gmail.com
on 5 Feb 2013 at 12:14
Hi,
If you click the pair button in the "Select Library Dialog", does TunesRemote
show up as a device in iTunes? You may need to click view->show sidebar to see
the list. Screenshot attached of what to look for.
If you enter the pair code, does the library become available?
Also can you post the tunesremote-se Session.log file please. This is located
in the .tunesremote-se folder in your home directory. (In Finder select Go->Go
To Folder and enter ".tunesremote-se"
Regards
Nick
Original comment by nick.gl...@lycos.com
on 10 Feb 2013 at 8:28
Attachments:
This was my issue too - I didn't realize I needed to select the device in the
host iTunes app. Perhaps you should add this step to the install RTFM. ;)
Original comment by Editin...@gmail.com
on 28 Nov 2013 at 1:00
Original issue reported on code.google.com by
ad...@runningcontacts.net
on 21 Dec 2012 at 11:17