param secondspersegment question

Dev Community Dev/API Corner
1

hi


i am wondering if there are some information about the secondspersegment param.


any backgroundinformation or bestpractice how to use this param in which case?


greets

2

no dev here around with some information :frowning:

3

This is part of the old transcoder, which we don't recommend using at this point.

If you have another mobile client (e.g. iOS/Android) try the new transcoder and have a peek at the parameters/endpoint. It'll produce much better results. Let us know if you have any other questions about it!

4

how much segments are used as default with the new transcoder? any idea? is this value changing depending to the quality?

please let me know.

enigma2 seems to have a limit. over 2000 segments it does not start playback. :-(

5

It depends on the duration of the media and on the resolution.

6 
May 28, 2013 21:31:02 [0x182d001c] DEBUG - Job running: /volume1/@appstore/Plex Media Server/Resources/Plex New Transcoder -i http://127.0.0.1:32400/library/parts/6555/file.mkv -threads 0 -y -segment_format mpegts -f segment -loglevel quiet -loglevel_plex error -map_metadata -1 -progressurl http://127.0.0.1:32400/video/:/transcode/session/d3cd9e54-0b1f-4692-8c14-727253c184f1/progress -vcodec libx264 -crf 22 -maxrate 8000k -bufsize 16000k -vsi 0x0 -preset veryfast -x264opts cabac=0:me=dia:subme=0:me_range=4:no_chroma_me:8x8dct=0:bframes=0:rc_lookahead=1:qcomp=0.50:qpmin=10:qpmax=51:qpstep=4:partitions=none:bframes=3:cabac=1 -flags -global_header -segment_time 1 -segment_start_number 0 -force_key_frames expr:gte(t,n_forced*1) -map 0:0 -burnsidx 4 -burnsscale 1 -acodec aac -strict -2 -cutoff 15000 -ac 2 -ab 154k -map 0:1 media-%05d.ts

i am going crazy.

a complete normal file played with the new transcoder want to use secondspersegements =1. the correspondig param above from debug is...

-segment_time 1

the used params are ...

May 28, 2013 21:30:45 [0x182c401c] DEBUG -  * videoQuality => 60
May 28, 2013 21:30:45 [0x182c401c] DEBUG -  * videoResolution => 1920x1080
May 28, 2013 21:30:45 [0x182c401c] DEBUG -  * maxVideoBitrate => 8000

sorry to ask again.

why is he calculating that he has to split in segments of 1 second.

the movie has the following details...

Medien

    Dauer 1:47:48
    Bitrate 17969 kbps
    Width 1920
    Height 816
    Seitenverhältnis 2.35
    Video Auflösung 1080p
    Container MKV
    Video Bildfrequenz 24p

Datei

    Accessible Yes
    Exists Yes
    Dauer 1:47:48
    Datei /volume1/Video/Movies/Blockbuster/XYZ.mkv
    Size 13.53 GB
    Container MKV

Video

    Codec H264
    Bitrate 15623 kbps
    Sprache English
    CABAC 1
    Dauer 1:47:48
    Bildrate 23.976 fps
    Height 816
    Ebene 4.1
    Profil high
    Ref Frames 5
    Width 1920

i found tons of debugs of plex and i didn't found any with a duration of one second.

please give me a helping hand on this.

7

The server uses heuristics to compute an appropriate number of seconds per segment. The old transcoder had "secondsPerSegment=X" to override, the new one doesn't (yet). I'll add an issue internally.

8

that would be awesome :-) hopefully this could be implemented easy and fast. crossing fingers :-)

beside this workaround with the segments.

the mentioned heuristics depends only on the media or is there something else used for calculations. i mean for example something like capabilities or profile or something else that is content of the request sended to the plexserver?

i appreciate your help very much. thank you very much

9

Sorry for bringing such an old thread back from the dead, but I'm having a transcoding issue (https://forums.plex.tv/topic/149276-transcoding-issues-with-dedicated-server-quad-core-xeon/) that would really benefit from having the ability to override the HLS segment time with the universal transcoder.

Has this been implemented yet? If so, how?

Thanks.

10

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.