"el.wubo" wrote:
I plan to have something ready for everyone to try out in about 2 weeks. This is finals week for me and it's been really hard to fight off the distraction of writing cool code so I can focus on my masters. I'll have more time next week.
mkdir -p /opt
mount --bind /mnt/HD_a2/ipkg/opt /opt
export PATH=/opt/bin:/opt/sbin:$PATH
ipkg update
ipkg install python26
#!/ffp/bin/sh
set -x
export PATH=/opt/bin:/opt/sbin:$PATH
cd /opt/exec/roku_media_server/server
python2.6 ./rss_server.py </dev/null >/tmp/rokud.$$ 2>&1 &
#!/ffp/bin/sh
# PROVIDE: rokud
# REQUIRE: SERVERS
# BEFORE: LOGIN
. /ffp/etc/ffp.subr
name="rokud"
command="/ffp/bin/rokud"
run_rc_command "$1"
HandBrakeCLI -i "$file" -o "$file".m4v -X 1280 -Y 720 -O -Z Universal -2 -T -q 0.62 -r 29.97 -E faac,ac3
"Timmy Likes to Click" wrote:
I just changed my port and now it works again. Any thoughts as to why 8001 is not working?
I have always used 8001 as default...It was never blocked by firewalls.
export PATH=/opt/bin:/opt/sbin:$PATH
ipkg update
ipkg install python26
#!/opt/bin/sh
export PATH=/opt/bin:/opt/sbin:$PATH
cd /opt/etc/roku_media_server/server
python2.6 ./rss_server.py </dev/null >/tmp/rokud.$$ 2>&1 &
#!/bin/sh
prefix="/opt"
PATH=${prefix}/bin:${prefix}/sbin:/sbin:/bin:/usr/sbin:/usr/bin
cd /opt/etc/roku_media_server/server
python2.6 ./rss_server.py </dev/null >/tmp/rokud.$$ 2>&1 &
"aamster" wrote:
I have My Media setup and followed the handbrake conversion of files to mp4 format. I'm struggling because when I open the mp4 file streamed from my computer, in my media, the player displays "retrieving" for about 30 seconds and then aborts. When I try to open it again, nothing happens. Causing additional frustration, the file played fine just last week! I have not altered settings. Does anyone know what I should try?
We’re upgrading Roku Community to bring you a faster, more mobile-friendly experience. You may notice limited functionality or read-only access during this time. Read more here.
Planned Downtime:
Community will be unavailable for up to 24–48 hours during the upgrade window during the week of May 19th and you may notice reduced functionality.
In the meantime, for additional assistance, visit our Support Site.
We're sorry for this disruption — we’re excited to share what’s next!