Reply to thread

Message

<blockquote data-quote="Drek77" data-source="post: 233185" data-attributes="member: 67074">Wow, that was a quick response! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin&nbsp; &nbsp; :D" loading="lazy" data-shortname=":D" /> I was afraid of that...&nbsp; I'm no dev so I guess my concept of how a media player works is incorrect.The way I was thinking was that as the program (MP) opens a file, it decided what to do with that information, be it, output it to the display or queue up some frames that will then be sent to the display....I thought that once the program had the information that is in the file (be it in part or in full) that IT decided how to use that information....I'm showing off my newbishness <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite10" alt=":oops:" title="Oops!&nbsp; &nbsp; :oops:" loading="lazy" data-shortname=":oops:" /></blockquote>

[QUOTE="Drek77, post: 233185, member: 67074"] Wow, that was a quick response! :thx: I was afraid of that... I'm no dev so I guess my concept of how a media player works is incorrect. The way I was thinking was that as the program (MP) opens a file, it decided what to do with that information, be it, output it to the display or queue up some frames that will then be sent to the display.... I thought that once the program had the information that is in the file (be it in part or in full) that IT decided how to use that information.... I'm showing off my newbishness :ooops: [/QUOTE]

Verification