What is a decoder, which ones do I need, and where do I get them?
module.exports = { serviceName: 'my-service', port: 3000, database: null, logging: 'info' } Run:
npm run dev or, if the CLI provides a serve command:
npm install -g veneissecom (If a scoped package or different registry is required, replace the command with the correct package name.) Create and scaffold a minimal project:
veneissecom init my-service cd my-service If the CLI doesn’t include an init command, use the repo template:
veneissecom serve Visit http://localhost:3000 to confirm the service responds. Create a health-check endpoint (e.g., src/routes/health.js):
It depends on the country you're in, the television system you're using, and sometimes the device you use. If you don't have a decoder you require, NextPVR will tell you what type of decoder it's missing. Here are some example decoder requirements for common user groups:
module.exports = { serviceName: 'my-service', port: 3000, database: null, logging: 'info' } Run:
npm run dev or, if the CLI provides a serve command:
npm install -g veneissecom (If a scoped package or different registry is required, replace the command with the correct package name.) Create and scaffold a minimal project:
veneissecom init my-service cd my-service If the CLI doesn’t include an init command, use the repo template:
veneissecom serve Visit http://localhost:3000 to confirm the service responds. Create a health-check endpoint (e.g., src/routes/health.js):
NextPVR is a 32bit application so will only see 32bit decoders on the machine. It can't see 64bit decoders, so these will not be listed.
NextPVR's decoder settings only apply to Live TV, and the playback of .ts recordings. For playback of other file types, like .mkv/.mp4/.avi, it's left to Windows to decide what decoders etc are used during playback. Installing LAV from HERE will often resolve issues with playback of these other file types.