Setting up a profile for accessing with rest API?

Hi all,

First, please forgive any stupid questions, I've been using serviio for a while but have never had to do much customization as it just sort of works out of the box for my needs. I recently upgraded to 1.0.1 and picked up the Serviigo android app. The problem I have is that whatever format is being fed to serviigo isn't hardware decodable on my Razr and I end up using less efficient software decoding and getting skipping. I've been searching the forums/faq/wiki and haven't been able to find out how profiles work for access that uses the rest API. I don't see my Razr showing up on the console as an accessing device when i use serviigo, so I'm assuming profiling works differently with DLNA access than the rest API. I want to define a profile for my phone that is used when I am outside my network accessing via serviigo. How do i do define a profile to be used with my phone over rest API or even can I?

[will]

Hi all,

First, please forgive any stupid questions, I've been using serviio for a while but have never had to do much customization as it just sort of works out of the box for my needs. I recently upgraded to 1.0.1 and picked up the Serviigo android app. The problem I have is that whatever format is being fed to serviigo isn't hardware decodable on my Razr and I end up using less efficient software decoding and getting skipping. I've been searching the forums/faq/wiki and haven't been able to find out how profiles work for access that uses the rest API. I don't see my Razr showing up on the console as an accessing device when i use serviigo, so I'm assuming profiling works differently with DLNA access than the rest API. I want to define a profile for my phone that is used when I am outside my network accessing via serviigo. How do i do define a profile to be used with my phone over rest API or even can I?

Hi,

They are in application-profiles.xml in the config folder and work the same as for normal devices except they have extra conditions for Medium and Low.

First thing to try is there is a commented out video block that remuxes videos, that solves the problem in some cases, uncomment that and have a go (have to restart the server). If you provide ffmpeg -i of the file then I can try and help. I would also be very interested in what you use in the end, and I'm thinking of providing a few profiles with an option to switch in the app for the next major serviio release, obviously the fewer profiles the better.

Hi Will, thanks for the quick reply. I uncommented the <video> tag for the serviigo profile, restarted the service and tried again. The video stutter is no better and now i get no audio. I'm using a Droid Razr and Mobi Player as my video player. Below is the output of ffmpeg -i

  Code:

god@legolas:/usr/local/bin/serviio$ ffmpeg -i /hdamedia/videos/TV/Game\ of\ Thrones/Season\ 02/Game\ of\ Thrones\ -\ s02e02\ -\ The\ Night\ Lands.mkv ~/test.m2ts
ffmpeg version N-42368-gbf53863 Copyright (c) 2000-2012 the FFmpeg developers
  built on Aug 11 2012 22:28:52 with gcc 4.6.3
  configuration: --enable-gpl --enable-libfaac --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libtheora --enable-libvorbis --enable-libx264 --enable-nonfree --enable-postproc --enable-version3 --enable-x11grab --enable-libvpx --enable-librtmp --enable-libxvid
  libavutil      51. 64.100 / 51. 64.100
  libavcodec     54. 33.100 / 54. 33.100
  libavformat    54. 15.102 / 54. 15.102
  libavdevice    54.  1.100 / 54.  1.100
  libavfilter     3.  1.100 /  3.  1.100
  libswscale      2.  1.100 /  2.  1.100
  libswresample   0. 15.100 /  0. 15.100
  libpostproc    52.  0.100 / 52.  0.100
Input #0, matroska,webm, from '/hdamedia/videos/TV/Game of Thrones/Season 02/Game of Thrones - s02e02 - The Night Lands.mkv':
  Duration: 00:54:57.71, start: 0.000000, bitrate: 3352 kb/s
    Stream #0:0(eng): Video: h264 (High), yuv420p, 1280x720, SAR 1:1 DAR 16:9, 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc (default)
    Stream #0:1(eng): Audio: ac3, 48000 Hz, stereo, s16, 384 kb/s (default)
[graph 0 input from stream 0:0 @ 0x9d28200] w:1280 h:720 pixfmt:yuv420p tb:1/1000 fr:24000/1001 sar:1/1 sws_param:flags=2
[output stream 0:0 @ 0x9d286c0] No opaque field provided
[graph 1 input from stream 0:1 @ 0x9d282c0] tb:1/48000 samplefmt:s16 samplerate:48000 chlayout:0x3
[mpegts @ 0x9d32440] muxrate VBR, pcr every 2 pkts, sdt every 200, pat/pmt every 40 pkts
Output #0, mpegts, to '/home/god/test.m2ts':
  Metadata:
    encoder         : Lavf54.15.102
    Stream #0:0(eng): Video: mpeg2video, yuv420p, 1280x720 [SAR 1:1 DAR 16:9], q=2-31, 200 kb/s, 90k tbn, 23.98 tbc (default)
    Stream #0:1(eng): Audio: mp2, 48000 Hz, stereo, s16, 128 kb/s (default)
Stream mapping:
  Stream #0:0 -> #0:0 (h264 -> mpeg2video)
  Stream #0:1 -> #0:1 (ac3 -> mp2)
Press [q] to stop, [?] for help
Input stream #0:1 frame changed from rate:48000 fmt:s16 ch:2 chl:stereo to rate:48000 fmt:s16 ch:6 chl:5.1(side)
[graph 1 input from stream 0:1 @ 0x9d63740] tb:1/48000 samplefmt:s16 samplerate:48000 chlayout:0x60f
[auto-inserted resampler 0 @ 0x9d285e0] chl:5.1(side) fmt:s16 r:48000Hz -> chl:stereo fmt:s16 r:48000Hz
frame=79067 fps=136 q=31.0 Lsize=  373303kB time=00:54:57.71 bitrate= 927.3kbits/s
video:276309kB audio:51528kB subtitle:0 global headers:0kB muxing overhead 13.868800%


[will]

Do these files play fine from the SD card? Could you provide an ffmpeg output for one that does if they don't. Maybe the ac3 audio is causing problems.

Are you using Original or Medium quality level, as that command didn't look like a full one for any of the qualities.

Can you give the full command you want me to run, I'm a total newbie to ffmpeg? As to your other question, I've tried running these on all three qualities and found that they all skip similarly. Also, it wasn't clear from my last post but after making the change to the profile, I'm still being forced to use software decoding.

[will]

Just ffmpeg -i path/to/file

And what about if you play them from an SD card?

The fact that even Low doesn't work is very odd, almost every device should be able to play back that quality level.