OneLicense and other licensing agencies
![Tyler Rasmussen](https://us.v-cdn.net/6038263/uploads/avatar/n8549102.png)
OneLicense wouldn't bring in text like CCLI does, but in the place where it says "CCLI License Number" if we could simply and easily switch that on songs to other licenses and FaithLife saved those licenses, that would be a time saver. Plus then FaithLife could generate a list for reporting to OneLicense. Again saving time.
Another simple example is CCLI Streaming Plus. When we use an master track (which we do regularly at one of our services), we not only need to report Digital Usage, but also Master Tracks used. FaithLife could list not only digital, but also Master Tracks.
Comments
-
Still disgruntled that OneLicense isn't included as a default "Licensed by" in Proclaim. Our contemporary service uses CCLI, but our traditional service uses OneLicense, and why it can't be the same level of easy, I don't know...0
-
Still strongly desire this!0
-
After 2 years, still very much wishing we could simply click "Licensed by OneLicense". But also, we use other licenses (namely Augsburg Fortress) and if we could save custom save custom license lines and then simply select the licensing agency (including Public Domain), that would make everything so much simpler. Then you'd always just verify the right license was selected for each song.0
-
RE-UPPING. I imagine a lot of hymnal-based congregations use Proclaim, and a simple checkbox for OneLicense like CCLI would be really nice. Especially if we could then print out a quick report for songs to report to OneLicense. Please add!0
-
Again, please at OneLicense in addition to CCLI. It would make things so much easier.
0 -
@Tyler Rasmussen I'll join you in the request for OneLicense to be added into the feature set. For me, the CCLI integration is rarely helpful. Most of my hymns are covered by OneLicense. I imagine though that there are two issues at play. I don't know that OneLicense has an autoreporting feature which CCLI does (maybe it does and I've just not seen it.) The other issue is I don't know if the main client base of Proclaim (and Logos in general) would rely on OneLicense titles as much CCLI. My limited experience has been that OneLicense is great for hymns from liturgical traditions, and CCLI is much better at hymns from non-liturgical traditions. I've long thought that Logos in general has lagged in supporting the use cases in liturgical churches. (I don't know your tradition, and I'm happy to hear if your experience is different from mine.)
0