I am working on content-finance and content tokenization. Using NFT for monetization of existing culture. I started with music, but I will go into multimedia.
I am focusing on modernization of patronage for now. Current features: Patron Slot (utility for owners to be recognized as patrons under musical track represented by token) and something dev heavy: IBindableToken.
It work by deploying CREATE3 factory that will deploy every collection. Salt '0' is used for core (discography), incrementally initialized salts are used for albums.
Core collection tokens will be created from: [tokenId][groupId], which adds additional gas optimalization.
For now I released deployers, factory and ERC721PairedBinderPrelaunched (OpenZeppelin extension) and very thin mockup of core to test ERC721PBP. Prelaunch work as independent collection before core is released. After: binding mechanism will be unlocked and core will mirror transfers.
My take on IBindableToken is highly flexible. Diagram describe something that was build on IBindable: IERC721MultipairedBinder, IERC721PairedBinder.
IBindable could even work on IERC1155 
You could deploy your own factory: https://basescan.org/address/0x59b9f15621fa999fcb305dc7ee65f99d2ee428ac#writeContract
Ready to deploy collection: https://github.com/sebasky-eth/content-finance-contracts/blob/master/src/release/1-first-patrons/FirstCrossCollectionalSingle.sol