New Vero?

[sam_nazarko]

We will charge in GBP as we did in the past.

[mark22]

Double the price

[sam_nazarko]

About 170 euros.

[skank]

thx for the info

[sam_nazarko]

This is now available as a soft launch.

[DAlba]

What does soft launch mean? How do I purchase? I never got newsletter announcement.

[gpmc]

There is a clear statement by Sam on top of the Forum explaining “soft lunch” and providing also the link for direct purchase.

[angry.sardine]

@DAlba

How do I purchase?

Read the first post in this thread:

Vero V soft launch

We’re still working on readying our website for the new Vero and we’re packaging as many devices as we can every day so that we don’t have a large backlog like we did with the Vero 4K + when it was first released. As some users are keen to get their hands on devices, we’re doing a soft-launch. This means no blog post announcement or newsletter email just yet. If you’re interested, you can place your order here. Thanks for your patience and understanding As of 5th November 2023, resellers see…

(There’s a link in that post which you can use to order).

[sam_nazarko]

No newsletter has been sent yet.

[gpmc]

Dear OSMC Team,
Today I read about the new Alpha 3 build of Kodi 21 that is going to implement settings which make Kodi convert Dolby Vision profile 7 (single track/video) files into profile 8.1 but on Android OS (Dolby Vision Compatibility/Quality Improvements).
Is this something that could be also introduced into future versions of OSMC?
Thanks

[grahamh]

There’s a reason why the DV work on Kodi is concentrated on Android and, I think, is confined to devices that already support DV, just not under Kodi. quietvoid is doing some great work uncovering the way DV works but I don’t think the approach followed there translates to OSMC devices.

[gpmc]

Noted. Thanks

[angry.sardine]

I think it is safe to assume that the Vero V will never support Dolby Vision output, and it’s likely that no subsequent OSMC device ever will either. From what Sam has said, there are legal issues which cannot be overcome without compromising OSMC’s open source nature to such an extent that it renders the entire project pointless.

[sam_nazarko]

Things can change, but this device for sure doesn’t support it.

We are looking at tonemapping as discussed though.

[angry.sardine]

@sam_nazarko

We are looking at tonemapping as discussed though.

Well, sure, that’s why I said it won’t support Dolby Vision output.

[gpmc]

@gpmc

convert Dolby Vision profile 7 (single track/video) files into profile 8.1

Agreed, but I was guessing that this conversion of Dolby Vision profile 7 (single track/video) files into profile 8.1 could have been done at software level without any native DV implementation.

[angry.sardine]

@gpmc

Agreed, but I was guessing that this conversion of Dolby Vision profile 7 (single track/video) files into profile 8.1 could have been done at software level without any native DV implementation.

Do you have reason to believe doing that would bypass Dolby’s licensing requirements? DV itself is proprietary IP, now matter how it’s implemented.

[gpmc]

Originally it seemed to me to be a workaround to manage only specific DV profile and not the full specs, that’s why I supposed not to break the DV license terms.

[sam_nazarko]

You can’t break license terms if you don’t license something.

There are other implications we need to look in to.

[Rossi]

Just to confirm, is the Vero V remote the same used by the Vero 4K+?

I’m planning to order one and keep the 4K+ as a backup for the V and the other 4K+. If it’s the same remote it makes it much easier and I do not have to order a spare remote.