I don't think it's really fair to say the pi is underpowered for the use case for which it is intended. If you want to drive more hardware you'd obviously not use the GPIO approach, and build a break out board which could be driven by the pi. Other solutions exist, horses for courses.
Regarding the video, sounds like you're either hitting a bottleneck with the video you're trying to play, or are playing a codec the pi doesn't have hardware acceleration for. The pi should by default use its GPU to decode video. I've been using it to play back 1080p video since the first release. There are even distros specifically for using the pi as a HTPC (OSMC, ibreelec etc). If you're playing content encoded in a format not supported by the GPU (e.g. h265, Hi10P) the CPU may struggle to play it back smoothly, though IIRC OSMC have recently made improvements with h265. Either some problem like that or you don't have the licence for the codec. If you are still having problems feel free to post the output of ffmpeg -i filename here and I'll see if anything jumps out.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
