Support playback on Raspberry Pi about mediacenterjs HOT 13 CLOSED

any reason why your not using flowplayer with fragmented mp4? This could allow for all devices to play "in browser" as long as their html5 compatible. Flowplayer also has a flash fail back for older browsers which could be used with a browser/device check...

from mediacenterjs.

Hej Karnith,

Thanks for offering a solution.

Currently the browser already recieves a fragemented mp4 (in a flv container due to some duration parsing issues) but transcoding movies on the fly takes a lot of processing power. The raspberry sadly does not have very much CPU power so a alternative most be used. And as omxplayer is both compatible with the ARM chip and can play movies with very little CPU power it a perfect solution.

About flowplayer: MediacenterJS currently uses VideoJS which has the same functionality as flow player (including Flash fallback) but personally I like the API a bit more. :)

from mediacenterjs.

Hi Jan,

Take a look at http://serviio.org.

Although java based, it seems to run on the raspberry pi without issue using ffmpeg. It’s presentation is flash container, but the principle is that it is able to stream using ffmpeg for on-the-fly transcoding.

Karnith

From: Jan Smolders [mailto:[email protected]]
Sent: Sunday, November 10, 2013 10:09 AM
To: jansmolders86/mediacenterjs
Cc: Matthew Marino
Subject: Re: [mediacenterjs] Use OMXPlayer for Raspberry Pi (#27)

Hej Karnith,

Thanks for offering a solution.

Currently the browser already recieves a fragemented mp4 (in a flv container due to some duration parsing issues) but transcoding movies on the fly takes a lot of processing power. The raspberry sadly does not have very much CPU power so a alternative most be used. And as omxplayer is both compatible with the ARM chip and can play movies with very little CPU power it a perfect solution.

About flowplayer: MediacenterJS currently uses VideoJS which has the same functionality as flow player (including Flash fallback) but personally I like the API a bit more. :)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/27#issuecomment-28156189.

from mediacenterjs.

That is very exciting news, thanks Karnith. I'll have a look how they did that!

from mediacenterjs.

On hold due to the fact browsers on Rasbian do not work very well and will nbot work well untill the distro uses something like wayland or a browser can be started without the need of X.

from mediacenterjs.

Have you looked into nodewebkit? If I remember correctly it has an integrated browser based off chrome. I have used it to create nodejs desktop apps...

-------- Original message --------
From: Jan Smolders
Date:03/30/2014 11:07 (GMT-08:00)
To: jansmolders86/mediacenterjs
Cc: Matthew Marino
Subject: Re: [mediacenterjs] Support playback on Raspberry Pi (#27)

On hold due to the fact browsers on Rasbian do not work very well and will nbot work well untill the distro uses something like wayland or a browser can be started without the need of X.

Reply to this email directly or view it on GitHubhttps://github.com//issues/27#issuecomment-39033622.

from mediacenterjs.

Hej Karnith,

I did actually and it's really amazing. It's a lot of work though from what I understand to make a functional node-webkit application when using express/jade like mediacenterjs currently does. Also I have doubts if it will help in the case of the Raspberry Pi since the bottleneck is the dependency to X which slows down the front end drastically. Thanks for thinking with me on this though! Your thoughts and ideas are always welcome!

from mediacenterjs.

Well, not really that hard. I made an app using nodewebkit and SailsJS. Sailsjs uses express, I used ejs for my app. All that really needs to be done is an html file created, nodewebkit module installed and some edits to the package.json. If the issue is X, I could see how that could be a problem.

-------- Original message --------
From: Jan Smolders
Date:03/31/2014 12:29 (GMT-08:00)
To: jansmolders86/mediacenterjs
Cc: Matthew Marino
Subject: Re: [mediacenterjs] Support playback on Raspberry Pi (#27)

Hej Karnith,

I did actually and it's really amazing. It's a lot of work though from what I understand to make a functional node-webkit application when using express/jade like mediacenterjs currently does. Also I have doubts if it will help in the case of the Raspberry Pi since the bottleneck is the dependency to X which slows down the front end drastically. Thanks for thinking with me on this though! Your thoughts and ideas are always welcome!

Reply to this email directly or view it on GitHubhttps://github.com//issues/27#issuecomment-39130576.

from mediacenterjs.

Hej Karnith,

I would love to see an example of that html file if that is possible. I'm still investigating if the node-webkit footprint is smaller than chromium.

Thanks again!

from mediacenterjs.

In the HTML file I have

In the package.json I have

"scripts": {
"start": "nodemon",
"debug": "node debug server.js"
},
"node-main": "app.js",
"main": "server.js",
"//": "Change main from app.js to index.html when using nodewebkit",
"window": {
"show": "false",
"title": "Warehouse",
"toolbar": false,
"frame": true,
"width": 961,
"height": 760,
"position": "center"
},

So, basically when I use nodewebkit, I change main to nodewebkit. Node-main is needed and tells nodewebkit what js file is app main.

Since I use sailsjs, I have this in the app.js

var bLoaded = false;

exports.callback0 = function (win) {
var gui = window.require('nw.gui');
gui.Window.get(win).on('loaded', function() {

                           if (bLoaded == true) return;
                            window.location.href = "http://localhost";
                            bLoaded = true;
           });

/* Start sails and pass it command line argument */
require('sails').lift(require('optimist').argv);
}

Since my app works as a server app and desktop app I made a server.js file with just (as standard)

/* Start sails and pass it command line argument */
require('sails').lift(require('optimist').argv);

in it so I could start it without needing to change the app.js file.

IF nodewebkit is installed globally you can run with nodewebkit command in the app folder, otherwise you should be able to run with npm start which will call the local nodewebkit module of the app.

Hope this helps,

Matthew

From: Jan Smolders [mailto:[email protected]]
Sent: Tuesday, April 01, 2014 8:10 AM
To: jansmolders86/mediacenterjs
Cc: Matthew Marino
Subject: Re: [mediacenterjs] Support playback on Raspberry Pi (#27)

Hej Karnith,

I would love to see an example of that html file if that is possible. I'm still investigating if the node-webkit footprint is smaller than chromium.

Thanks again!

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/27#issuecomment-39216761.

from mediacenterjs.

Sorry Matthew for adressing you with your nickname this whole time, I got your nickname mixed up so I didn't know it was you. :) Great explanation! I'm going to try it out asap. And let you know what my findings are. Thanks again!

from mediacenterjs.

No problem. Karnith, Matthew, it’s all the same me.

From: Jan Smolders [mailto:[email protected]]
Sent: Tuesday, April 01, 2014 11:04 AM
To: jansmolders86/mediacenterjs
Cc: Matthew Marino
Subject: Re: [mediacenterjs] Support playback on Raspberry Pi (#27)

Sorry Matthew for adressing you with your nickname this whole time, I got your nickname mixed up so I didn't know it was you. :) Great explanation! I'm going to try it out asap. And let you know what my findings are. Thanks again!

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/27#issuecomment-39237792.

from mediacenterjs.

Closing issue as it is now possible to choose the transcoding quality and hence tune the experience to work with the Raspberry Pi. (The javascript rendering issues are more pressing anyway)

from mediacenterjs.