WiSo Wrote:Of course XBMC uses an internal protocol to access the shares which an external program doesn't have. How should an external player access a share if it doesn't have an internal smb client (not mentioning the syntax).Ok, unfortunately this is a little bit too "technical" for my skills and understanding. I thought that XBMC could pass to the external player the correct networked path, but this is an uneducated thought, I admit.
Mapping the shares to local letters is the only choice here.
If the external player call will ever be implemented is not yet clear. I heard different opinions from the team and finally the team decides about the architecture.
In any case I posted on the Trac system.
To be honest, I think this is just a stopgap solution (albeit a really good one). People clamoring for external codecs, etc. are IMO missing the point about what made XBMC great in the first place.
XBMC has to handle all files internally, with the right performace, the right feature set, etc. This is what it's always been all about. And I'm confident it'll get there.