Ok, it's not as simple as adding a couple of extra fields to the existing system, but to change to a new piece of software, create a routine to export, re-map, re-import and populate the additional fields is a fairly routine process. Meridian have the ability to rebuild our Sooloos database remotely already so I can't see any real barrier.
The key difference is that the Sooloos Library would need to populate Fields with Extra Information for every Track in the Library.
By my estimate, Meridian would need to add about 20 Fields for true Track Level Metadata (some would demand even more).
For the sake of argument, assume that the average Sooloos user has 5,000 Albums at 13 Tracks per Album
That means that a minimum of 5,000 x 13 x 20 = 1,300,000 Pieces of Information would need to be ADDED to each User's database.
Of course, many will say that this can be done "automatically", but given many Users' experience of how AMG (and others) wrongly identifies already Tagged Albums, which in turn need to be corrected by the User, I for one wouldn't be happy with this.
In simpler terms, ask yourself "Would I have been happy to allow Sooloos / AMG to
Automatically Import my 5,000 Albums and accept the Default Metadata they arrived at"?
If your answer is Yes, then maybe you would be happy with such a Track Level Metadata Conversion Routine
If the answer is No, as it likely would be for many here seeing how the Metadata wrongly identifies Albums (and Versions) then essentially the User would need to Supervise or Audit each Album as it's re-imported into Sooloos, repeating what they have already done to create their Libraries initially
Track Level Metadata can be achieved, but only after some considerable ReDesign from Meridian and then a lot of Re-Import work by each User, essentially duplicating the Import process they have already gone thru to create their current Libraries.
Google Search
|
Meridian Systems
|
Meridian Streaming
|
Restaurant
|
WiKi
|
Duncan's Meridian Info
|
Board Rules
|
Restaurant Rules
