Hello everyone, I installed plex (1.14.1.5488) on banwogon and vultr’s kvm vps using ubuntu 1604 x64. It can be played live. Any file transcoding will report an error. I installed it in aws ec2 and gcp using ubuntu 1604 x64. Plex, the same file transcoding is normal, why is this?
Plex Media Server.log (1.2 MB)
Log on banwogon
xml
Media
- Video Resolution SD
- Duration 32:02
- Bitrate 312 kbps
- Width 480
- Height 272
- Aspect Ratio 1.78
- Container RM
- Video Frame Rate NTSC
Part
-
Duration 32:02
-
File 1.rmvb
-
Size 71.50 MB
-
Container RM
-
Codec RV40
-
Bitrate 437 kbps
-
Bit Depth 8
-
Chroma Subsampling 4:2:0
-
Frame Rate 29.97 fps
-
Height 272
-
Ref Frames 1
-
Width 480
-
Display Title SD (RV40)
-
Codec COOK
-
Channels 2
-
Bitrate 32 kbps
-
Audio Channel Layout stereo
-
Sampling Rate 22050 Hz
-
Stream Identifier 1
-
Display Title Unknown (COOK Stereo)
The above file can only be transcoded, transcoded on banwogon and vultr, and reported errors, but the transcoding is normal on aws ec2 and gcp.help me pls
please create full DEBUG (not VERBOSE) logs.
- Verify logging settings
- Start Playback
- Play until failure.
- Wait 30 seconds for logs to flush
- Collect logs Settings - Server - Troubleshooting - Download Logs
- Gather XML (Get into - View XML )
- Paste XML (use code formatting or triple-back tick bracketing to protect)
- Attach ZIP
Plex Media Server Logs_2019-02-24_00-26-33.zip (956.7 KB)
34.xml.rar (907 Bytes)
Thank you for your reply, I followed your prompt
upupup,help me
Thank you for that… Sorry to have missed replying.
Do you realize this is a Real Media encoded file?
Real Media formats do not work well with Plex at all.
I suggest you encode to H.264. It will not take long with handbrake. This file should be done in perhaps 60 seconds ?
<?xml version="1.0" encoding="UTF-8"?>
<MediaContainer size="1" allowSync="1" identifier="com.plexapp.plugins.library" librarySectionID="5" librarySectionTitle="其他影片" librarySectionUUID="c0799ff7-1a4a-48fd-a2c8-6da9e47cf106" mediaTagPrefix="/system/bundle/media/flags/" mediaTagVersion="1544818278">
<Video ratingKey="34" key="/library/metadata/34" guid="com.plexapp.agents.none://75188751e31e68fb5017aba1e89ec1962fcf758e?lang=xn" librarySectionTitle="其他影片" librarySectionID="5" librarySectionKey="/library/sections/5" type="movie" title="1" summary="" userRating="2.0" year="2016" thumb="/library/metadata/34/thumb/1550940852" art="/library/metadata/34/art/1550940852" duration="1922611" originallyAvailableAt="2016-05-18" addedAt="1463550328" updatedAt="1550940852">
<Media videoResolution="sd" id="33" duration="1922611" bitrate="312" width="480" height="272" aspectRatio="1.78" audioChannels="2" audioCodec="cook" videoCodec="rv40" container="rm" videoFrameRate="NTSC">
<Part accessible="1" exists="1" id="33" key="/library/parts/33/1463550328/file.rmvb" duration="1922611" file="/download/1.rmvb" size="74973184" container="rm">
<Stream id="31" streamType="1" codec="rv40" index="0" bitrate="437" bitDepth="8" chromaSubsampling="4:2:0" frameRate="29.970" height="272" refFrames="1" width="480" displayTitle="SD (RV40)" />
<Stream id="32" streamType="2" selected="1" codec="cook" index="1" channels="2" bitrate="32" audioChannelLayout="stereo" samplingRate="22050" streamIdentifier="1" displayTitle="Unknown (COOK Stereo)" />
</Part>
</Media>
<Extras size="0">
</Extras>
</Video>
</MediaContainer>
The above file on the ec2 server can be successfully transcoded. But on the banwogon or vultr server, all files cannot be transcoded.
Then you have issues with those providers.
I don’t find this the least bit funny.
Banwogon shows QEMU Virtual CPU version, but ec2 shows Intel® Xeon® CPU E5-2676 v3 @ 2.40GHz, perhaps a different guide transcoding problem for vps virtual technology.
QEMU is an emulated environment.
Now that you mention it, I’ve never seen HW transcoding work on QEMU VMs because the layer of abstraction is too great.
The other is likely a para-virtualized VM (like VirtualBox)
I found that banwgon uses kvm technology, and Ec2 uses xen, xen-hvm technology. Is it common to not transcode on kvm machines?
If the KVM is QEMU-based, which that one is, it will not be able to because the hardware is actually emulated through different API layers. Those won’t work.
Paravirtualized systems usually allow direct hardware access. This is what you’ll see on VirtualBox on x86_64 systems. VirtualBox, ESXi, and several others, allow hardware passthrough.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.