You are making the assumption that DrCWO is on the radar of the Roon team. I’d be surprised if RooExtend family of products are known by anyone at Harman or the Roon Team who was hired post-acquition.
I know about RooExtend because he msg’d me back in the day trying to use the Roon trademark, and renamed to RooExtend when I said he’s not allowed to use Roon like he originally wanted. I, for one, had no idea he did a headphone thing.
Creative Commons for the data, MIT for the code.
Agreed. Our OPRA license does not require anyone to notify us, nor will we be offended if someone does not.
Uh… you announced rooPlay in August 2022. A few weeks later, we released an API on github for a project that had already been in production Roon releases for months prior. In fact, another user had been working with this and released a working Spotify Connect to Roon Zones bridge product.
Because this all took time to develop, you can imagine it was started many months before that spotify thing was created. My guess is late 2021 or early 2022 (guessing without digging through our code repo).
It took some time to find a partner, and we started working wtih Victrola and another partner in 2023, but the acquisition was very distracting, so this took this long to get released properly.
It’s really unfortunate you’ve had 2 projects made obsolete, but copying you is not the reason. In some cases, we started before you, in other cases, maybe around the same time, and then again in other cases, we weren’t even aware of your stuff.
For example, we never released prototype we had for a physical Roon Remote Control If we had released it, I’m sure you would say we heisted your RooDial project. However, we did that project before you even had seen Roon, and then again 2 additional times after RooDial. All never made it to market because we couldn’t get it to the place where I was proud of the end result.
As much as you feel targeted, I can confidently say we are not