Was it right?

Feedback
22

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

8 Likes
23

I mailed to partners@roonlans.com so send me information on how I can participate in the Roon Ready program regarding this new Roon input functionality. I’m excited to see what comes out of it and will report back…

1 Like
24

Hello @danny ,
I’m glad you’re joining us.

To be clear:
I have not accused anyone of violating licenses or copying ideas. What I have said is that I would have been happy if you had included me or Jaakko Pasanen.

Right, but you’re still part of the Harman team even after the merger. Also with @enno who visited me at the HighEnd Show in Munich 2023 I had a long conversation about rooExtend and especially rooAIDJ that I released at the show. Therefore, I am not sure I can agree with your statement that you did not know what I’m doing :face_with_raised_eyebrow:

Not quite :wink: rooHead offers further options for customizing the target function that Roon has not (yet) built in. rooPlay is an end-user product and not an API. But I don’t know exactly what you’re planning with “Next evolution of Roon Ready tech!”.

Thank you for your clarification. I am not one of those guys who likes to argue about little things from the past. That includes who started what first and when. That’s useless and doesn’t help any of us in moving forward.

I now see that my post with the desire for a more personal collaboration has aroused quite a bit of interest :wink:

I hope that - as the only commercial developer of Roon extensions - I might now receive a little more attention from you and that the new Harman team will also take note of my work.

To look ahead to put our collaboration on a more solid footing, I wrote to partners@roonlabs.com yesterday. I asked them to tell me what I need to do to be able to use the Roon Ready label with my rooExtend-Box, rooPlay and other future products.

I would be happy if you might positively support my attempt :pray:

Best DrCWO

25

You seem to be accusing Roon of not reaching out to you when you’ve done the same. You posted in a public forum when maybe a private email would have been more appropriate.

2 Likes
26

Why escalating this verbally from different angles and creating possible damages to the reputation of Roon fellows that have substantially contributed with their work?
Let’s Roon and DrCWO sort this among themselves.

9 Likes
27

As an already happy customer of @DrCWO I’d love to see a full Roon Ready version of RooPlay.

So I hope this collaboration works out.

28

I don’t think Roon wants or needs a collaboration.

29

Maybe you can let Roon think and decide for themselves.

30

I said what I THINK (or don’t think).

2 Likes