Kinsky 3.3,22 problem

[FredKDY]

I just upgraded from Kinsky 3.3.6 to 3.3.22. The old version used to remember where it was when it was closed down e.g. Album view, 3.3.22 goes back to folders. Is this a flaw, normal or am I doing something wrong.

[Pollensa1946]

(2010-10-02 22:05)FredKDY Wrote:  I just upgraded from Kinsky 3.3.6 to 3.3.22. The old version used to remember where it was when it was closed down e.g. Album view, 3.3.22 goes back to folders. Is this a flaw, normal or am I doing something wrong.

The v22 does not find my Twonky server (on QNAP NAS) at all. Reverted to v13 and all OK. So there is a problem for sure.

[Briain]

Hi

I've been using 13 for a while and it seems to be all okay (not tried 22).

Bri

[stevens Linn Staff]

Hi FredKDY,

This feature where the browser remembers its location was temporarily removed for this version, but will be re-added shortly.

Pollensa1946, could you update to the latest version and post the contents of the debug console (right click-> Tools -> Debug Console) to this thread. If your server does not appear, you can try hitting F5 to rescan the network. If you could send the contents of the debug console after hitting F5, that would be very helpful.

Many thanks

Steven

[Pollensa1946]

(2010-10-04 10:58)stevens Wrote:  Hi FredKDY,

This feature where the browser remembers its location was temporarily removed for this version, but will be re-added shortly.

Pollensa1946, could you update to the latest version and post the contents of the debug console (right click-> Tools -> Debug Console) to this thread. If your server does not appear, you can try hitting F5 to rescan the network. If you could send the contents of the debug console after hitting F5, that would be very helpful.

Many thanks

Steven

I downloaded from here...
Stable
v3.3.22
Win32: KinskyDesktop_3.3.22_all.exe (2.9MB)
...after install (on top of 3.3.13) problem persisted. I then uninstalled completely and did a "clean" install of 3.3.22 and problem has gone. So now 3.3.22 is good for me.
Thanks.

[Pollensa1946]

(2010-10-04 11:44)Pollensa1946 Wrote:  

(2010-10-04 10:58)stevens Wrote:  Hi FredKDY,

This feature where the browser remembers its location was temporarily removed for this version, but will be re-added shortly.

Pollensa1946, could you update to the latest version and post the contents of the debug console (right click-> Tools -> Debug Console) to this thread. If your server does not appear, you can try hitting F5 to rescan the network. If you could send the contents of the debug console after hitting F5, that would be very helpful.

Many thanks

Steven

I downloaded from here...
Stable
v3.3.22
Win32: KinskyDesktop_3.3.22_all.exe (2.9MB)
...after install (on top of 3.3.13) problem persisted. I then uninstalled completely and did a "clean" install of 3.3.22 and problem has gone. So now 3.3.22 is good for me.
Thanks.

Spoke too soon, it worked only once then after next reboot it reverted to the problem of not finding Twonky. Here's the console log...

Local Area Connection (192.168.1.7) is supported
MS TCP Loopback interface is loopback - ignored
05/10/2010 17:05:51: Network interface event received. Available interfaces:
05/10/2010 17:05:51: Local Area Connection (192.168.1.7)
05/10/2010 17:05:51: Network interface event received - interface changed from (None, ) to (Local Area Connection, 192.168.1.7)
Local Area Connection (192.168.1.7) is supported
MS TCP Loopback interface is loopback - ignored
TcpServer+ 192.168.1.7:49832...Success
05/10/2010 17:05:55: Upnp List Rescan Type{ServiceType{linn.co.uk:Product:3}}
05/10/2010 17:05:55: Upnp List Rescan Type{ServiceType{upnp.org:AVTransport:1}}
05/10/2010 17:05:55: Upnp List Rescan Type{ServiceType{upnp.org:ContentDirectory:1}}
05/10/2010 17:05:55: Stack started successfully (Local Area Connection, 192.168.1.7)
Starting HTTP Server at http://192.168.1.7:50008/Kinsky...Success
05/10/2010 17:05:55: Device+ Device{Udn{fc33877c-cd66-c456-80c6-d6bffb18bfda}UpnpLocation{http://192.168.1.7:26126/}UpnpIpAddress{192.168.1.7}}
05/10/2010 17:05:55: Device+ Device{Udn{7076436f-6e65-1063-8074-00089bac9021}UpnpLocation{http://192.168.1.3:9000/DeviceDescription.xml}UpnpIpAddress{192.168.1.3}}
05/10/2010 17:05:55: Device+ Device{Udn{fc33877c-cd66-c456-80c6-d6bffb18bfda}UpnpLocation{http://192.168.1.7:26126/}UpnpIpAddress{192.168.1.7}}
Loaded plugin Folder
05/10/2010 17:05:56: Entered Room(Main)
05/10/2010 17:05:56: Selected Preamp(Group(Room(Main), UpnpAv))
05/10/2010 17:05:56: Selected Source(Group(Room(Main), UpnpAv), UpnpAv (dBpoweramp Reference), UpnpAv)
05/10/2010 17:05:56: Selected Preamp(Group(Room(Main), dbPoweramp Renaissance))
05/10/2010 17:05:56: Selected Source(Group(Room(Main), dbPoweramp Renaissance), dbPoweramp Renaissance (Playlist), Playlist)
05/10/2010 17:06:05: Upnp List Rescan Type{ServiceType{upnp.org:ContentDirectory:1}}
05/10/2010 17:06:05: Upnp List Rescan Type{ServiceType{linn.co.uk:Product:3}}
05/10/2010 17:06:05: Upnp List Rescan Type{ServiceType{upnp.org:AVTransport:1}}
05/10/2010 17:07:17: Upnp List Rescan Type{ServiceType{upnp.org:ContentDirectory:1}}
05/10/2010 17:07:17: Upnp List Rescan Type{ServiceType{linn.co.uk:Product:3}}
05/10/2010 17:07:17: Upnp List Rescan Type{ServiceType{upnp.org:AVTransport:1}}
05/10/2010 17:07:17: Upnp List Rescan Type{ServiceType{linn.co.uk:Product:3}}
05/10/2010 17:07:17: Upnp List Rescan Type{ServiceType{upnp.org:AVTransport:1}}
05/10/2010 17:07:17: Upnp List Rescan Type{ServiceType{upnp.org:ContentDirectory:1}}

Once again I reverted to v13 and all is OK.

[stevens Linn Staff]

Hi Pollensa1946,

this is a strange one. In the debug output you posted, the line

05/10/2010 17:05:55: Device+ Device{Udn{7076436f-6e65-1063-8074-00089bac9021}UpnpLocation{http://192.168.1.3:9000/DeviceDescription.xml}UpnpIpAddress{192.168.1.3}}

is your Twonky server. KDT has, therefore, discovered it but, for some reason, is not displaying it in the browser window. This brings us to believe that it may be some issue with refreshing the display. Note it is also being discovered on the startup of the application, before the F5 button is clicked to refresh.

When you have time, could you go back to 3.3.22 and try the following: when you are in "Home > Library" in the left hand browse window and your Twonky server is not visible, can you then go back up to the top level "Home" folder and then go back into "Library" to see if it appears then? This should force the display to be refreshed and will give us a hint as to whether this is the problem or not.

Steven

[Pollensa1946]

OK, I have reproduced the steps I took previously.
Uninstalled v13. Clean install of v22. Invoked KDT and Twonky library was displayed OK. Powered down entire system (NAS, PC & Router), then powered up again. Invoked KDT and Twonky was found and displayed (this is the point at which it failed before, leading to my post above). I have stopped/started KDT a number of times and each time everything is OK, I am unable to reproduce the problem. If it appears again I will go thru the procedure you posted above and post here.

[Pollensa1946]

(2010-10-06 10:55)stevens Wrote:  try the following: when you are in "Home > Library" in the left hand browse window and your Twonky server is not visible, can you then go back up to the top level "Home" folder and then go back into "Library" to see if it appears then? This should force the display to be refreshed and will give us a hint as to whether this is the problem or not.
Steven

After a reboot of everything I had the problem again of KDT not finding Twonky. I followed the procedure you gave me (above) and it worked. It found Twonky.
Here's the log...

Local Area Connection (192.168.1.7) is supported
MS TCP Loopback interface is loopback - ignored
07/10/2010 15:59:24: Network interface event received. Available interfaces:
07/10/2010 15:59:24: Local Area Connection (192.168.1.7)
07/10/2010 15:59:24: Network interface event received - interface changed from (None, ) to (Local Area Connection, 192.168.1.7)
Local Area Connection (192.168.1.7) is supported
MS TCP Loopback interface is loopback - ignored
TcpServer+ 192.168.1.7:49832...Success
07/10/2010 15:59:29: Upnp List Rescan Type{ServiceType{linn.co.uk:Product:3}}
07/10/2010 15:59:29: Upnp List Rescan Type{ServiceType{upnp.org:AVTransport:1}}
07/10/2010 15:59:29: Upnp List Rescan Type{ServiceType{upnp.org:ContentDirectory:1}}
07/10/2010 15:59:29: Stack started successfully (Local Area Connection, 192.168.1.7)
Starting HTTP Server at http://192.168.1.7:50008/Kinsky...Success
07/10/2010 15:59:29: Device+ Device{Udn{7076436f-6e65-1063-8074-00089bac9021}UpnpLocation{http://192.168.1.3:9000/DeviceDescription.xml}UpnpIpAddress{192.168.1.3}}
07/10/2010 15:59:29: Device+ Device{Udn{fc33877c-cd66-c456-80c6-d6bffb18bfda}UpnpLocation{http://192.168.1.7:26126/}UpnpIpAddress{192.168.1.7}}
07/10/2010 15:59:29: Device+ Device{Udn{fc33877c-cd66-c456-80c6-d6bffb18bfda}UpnpLocation{http://192.168.1.7:26126/}UpnpIpAddress{192.168.1.7}}
Loaded plugin Folder
07/10/2010 15:59:30: Entered Room(Main)
07/10/2010 15:59:30: Selected Preamp(Group(Room(Main), UpnpAv))
07/10/2010 15:59:30: Selected Source(Group(Room(Main), UpnpAv), UpnpAv (dBpoweramp Reference), UpnpAv)
07/10/2010 15:59:30: Selected Preamp(Group(Room(Main), dbPoweramp Renaissance))
07/10/2010 15:59:30: Selected Source(Group(Room(Main), dbPoweramp Renaissance), dbPoweramp Renaissance (Playlist), Playlist)

[FredKDY]

Thanks stevens for the info. I just wanted to say that I dont have any problem with Kinksy finding the server. Its been off a few times as I had my electric meter changed and everything just works. Only dislike is that it doesnt remember where it was but as you say, this will be added in the near future. It even positions itself on the screen where you left it and the scroll works first time. That was two niggles I had with 3.3.6. So 3.3.22 seems a good improvement.