Cyberduck Mountain Duck CLI

#8423 closed defect (worksforme)

Interoperability with Russound Media Server

Reported by: peter charlesworth Owned by:
Priority: normal Milestone:
Component: core Version: 4.6
Severity: normal Keywords:
Cc: Architecture:
Platform: Windows 7

Description

I am completely new to Cyberduck, which was recommended to me by technical support at Russound, who I approached for help with a problem with my SMS3 Smart Media Server.

Basically, this is a computer and hard drive which manages stored music on an integrated home audio system. My problem is that originally the media server allowed me to access the individual album and track files and, if necessary, modify their titles or names. This is only necessary if for whatever reason, this information does not come through (perhaps due to non-recognition of the particular album in a data-base search conducted automatically by the media server) when a CD is loaded onto the system.

The Russound technical support recommended that I use Cyberduck, which interfaces with the Media Server. However, although I can view all the albums and tracks via Cyberduck, I am unable to rename any of them. I note that the "Edit" button on the relevant Cyberduck page is the only button in the tool bar which is "unlit", and whenever I attempt to rename an item, I receive an error message "550 Create directory operation failed. Please contact your web hosting service provider for assistance."

I have asked the Russound guy for further advice, but have not heard back from him. I wonder whether anyone can possibly help me with this issue. Any comments or suggestions would be greatly appreciated. Peter

Change History (1)

comment:1 Changed on Dec 13, 2014 at 9:20:02 AM by dkocher

  • Resolution set to worksforme
  • Status changed from new to closed
  • Summary changed from Problem with Cyberduck and Russound Media Server to Interoperability with Russound Media Server

Enter Return or choose File → Rename… to rename a file or folder. Refer to Rename a file or folder.

Note: See TracTickets for help on using tickets.