Hi, i see that karma read usd diretcly this means that when i working with it in solaris don' traslate usd files when i use with hydra right?

Right, Karma is getting input scene description from Hydra, not USD directly. But theres no translation to some other file format happening under the hood.

Piledriver
Hi, i see that karma read usd diretcly this means that when i working with it in solaris don' traslate usd files when i use with hydra right?

Translate how? Solaris keeps everything in .usd format, so no further translation is needed even if you apply some modifications

But as far as I know Karma doesn't render usd directly
It depends on Hydra to be fed the translated usd as any other Hydra delegate
You can use Husk to render .usd from disk using Karma "directly", but it will still run through Hydra and will depend on how Hydra presents the data, which makes it for example challenging for any Hydra delegate to access raw information from the .usd stage, at least until Hydra 2.0
So "can read usd directly" is a stretch, but since the Hydra translation layer is automatic you can possibly think about it that way for simplification

what i meant before with directly was that karma read usd as a native right? like arnold does for instance with .ass files, so if possible to render directly without translation, and for what you said there is a bit of translation because of hydra.
Hydra 2.0 something change?

Piledriver
what i meant before with directly was that karma read usd as a native right? so if possible to render directly without translation and for what you said there is a bit of translation because of hydra
Hydra 2.0 something change?

karma renders usd via husk as a hydra delegate, so yes it uses hydra translation. The 'karma' standalone command is just a wrapper for husk.

ok so its not possible currently render directly

Piledriver
ok so its not possible currently render directly

no, usd always goes through hydra for rendering.

ok, but in future will be some way to do that?

All renderers need an input scene and Karma is using Hydra/Usd. Half the point is to avoid a propriety format for scene input so my guess would be it'll always be Hydra/Usd. Anything that appears to be rendering directly will always be going through something like Hydra to translate, even if it's invisible and doesn't have a catchy name.

Oh and it's also worth mentioning that I'm pretty sure sop geometry into lops is implemented as a usd file format plugin. So even though in lops it looks like everything has been translated to usd, the actual data is in whatever format sops data is stored in, not usd crate or ascii. It's just getting re-represented as usd prims and properties on the fly.

ok, i just afraid that this translation with hydra will reduce a it the performance, sorry guys i'm not a techincal people and i don't really know a lot about hydra, but in g
eneral when i use something i want to know more about it

Always good to ask questions In general, if hydra wasn't translating usd there would have to be something else do it. Whether or not some alternative might have better performance is hard to say without a direct comparison. There has however been concerns raised about the original hydra design and work has been underway for a while (what tamte referred to as hydra 2) to improve things. How that will then compare to ass or rib files etc is hard to say, however usd is a lot more than a renderer file format so it's somewhat an apples to oranges comparison.