Hi...
I am just starting with Rivendell, so please pardon my total lack of
knowledge at this point which may result in my asking meaningless or
impossible questions.
I had set up a CentOS 7.5 system in advance and then followed the
Rivendell CentOS installation document to install Rivendell (the only
difference from the document's recommendation being that I did not
define a separate partition for /var, as I followed the standard CentOS
install recommendation).
As I want to get to know Rivendell for a while and continue to use an
existing Windows playout system in the meantime, the machine dual-boots
into CentOS or Win 10. A 1.5 TB partition on the drive is formatted as
NTFS and contains the music library, which is accessed by the Windows
playout system currently. The library is mounted with ntfs-3g on boot
into CentOS so it can be accessed by Rivendell.
It appears that Rivendell requires to make a complete copy of the music
library on ingestion with rdimport. This is inconvenient. There is
insufficient space on the current drive to allow Rivendell to store a
copy of the music library. Now of course I could attach an external
drive, copy the library on to it and then let Rivendell ingest it from
there and copy it back to where it is now. In which case, two questions
arise:
1. If I follow the copy-back-and-forth course outlined above, will the
Rivendell-ingested copy of the music library still be able to be
used by the Windows playout system or would I need to have /two
/active copies of the music library, one for Windows playout and the
other for Rivendell?
2. Does Rivendell require to make a copy of the library at all, or can
it simply ingest the metadata and populate the database without
copying the actual audio files?
Any observations or advice would be greatly appreciated, and thanks in
advance.
--Richard Elen
radioriel.org
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
