On Tuesday 05 January 2021 18:36:00 William Morder via tde-users wrote: I've been starting to think about it Bill, but losing my wife to COPD on Pearl Harbor Day has interfered with my giddyup. But now I'm still trying to clean up the final stuff, insurance and bank accounts etc, all by meself. That and getting used to rattling around in this house by myself. So I'm not inclined to do the upgrade, and recover all my stuff until I can see a few months down the road to do it. Scheduled for another ticker inspection in a few days, which will probably stretch into a session in the cath lab. A 30% ticker already running on a pacemaker needs TLC IOW. And I can't believe SS.gov, tried to setup an account on their web page, gave them my phone number and my email, confirmed my address. But they are going to MAIL me the verification code, estimated at 10 days. What the hell are they thinking? And I am not going anywhere near the office 25 miles up the superslab because the last time I was there 19 years to get my SS started, they kept my belt because it had a metal buckle and my glasses for the same reason. so I'm in there, holding up my pants, and blind enough I can't read the forms they want me to sign. That is so NOT going to ever happen again. All I want to do is change the auto-deposit account number and they are making it efing impossible. Same at the bank, gotta make an appointment at least a day in advance. Can you imagine an old fart like me with smoke coming out of his ears? Thanks Bill. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>

William Morder via tde-users wrote: I must disagree - no one is changing the standards. At least I am not aware of things changing in already released formats. What may not work are new formats where you may not have the new codec. --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting

On Wednesday 06 January 2021 02:59:33 am William Morder via tde-users wrote: Bill is right. For whatever reason updates to software players using codecs do sometimes 'break' the ability to play existing (older) files. I've experienced this multiple times (100s probably) since the '90s (and my mother has lost some family videos to this phenomenon). I've experience all of these situations: - Software no longer includes the older codec and you can hunt down and re-install the codec manually and it will play again. - Software no longer includes the older codec and you can hunt down and re-install the codec manually and it still will NOT play. - Software claims to have the codec, but, while newer created files will play correctly, older created files will NOT play. Add in a bunch of situations to the above of mangled playing of older files (think old VHS playbacks). Bit rot is probably responsible for some of it, but I’ve experienced cases (saved one of mom’s holiday videos) where copying the file to an ‘old’ machine (was literally stuck in a closet and hadn’t been updated in 5+ years) allowed the file to play ‘fine’ and was also able to convert the file to another format which then played correctly on the ‘new’ machine. My rule of thumb is to convert any codec using file that I care about into 3 different formats for archiving. HTH, Michael

William Morder via tde-users wrote: Yes indeed - I can use a VM as a guinea pig, but not my own PC, so usually I would wait a bit after a release updating my production system(s). The good thing is that many people use testing and report back issues, so that these issues get solved. I do not see a reason not to upgrade to stable couple of months before it becomes old stable. Just install and try mplayer from the command line - I am sure it was working fine with mp4 files under stretch. read this: https://wiki.debian.org/MultimediaCodecs --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting

On Wed, Jan 06, 2021 at 05:04:39AM -0500, Gene Heskett via tde-users wrote: Define "none work". Does nothing launch at all? Do you get a "busy" mouse cursor but no window opens? Does a window open but then it crashes? Something else? What happens if you launch the player from the command line? mplayer myvideo.avi Will the players play *any* multimedia formats at all? https://filesamples.com/categories/video -- Steve

On Wed, 6 Jan 2021 18:50:34 -0500 Gene Heskett via tde-users &lt;users(a)trinitydesktop.org&gt; wrote: Apparently it's the bit of the mp4 file that tells the player what codecs were used on the streams inside, plus some other constants. Without it, the player doesn't know what codecs to use. You may have a truncated or bit-rotted file on your hands (the moov atom is usually at the end of the file, it seems), or the encoder may simply have been standards-incompliant or outright broken. The error above is bubbling up from ffmpeg, which is a pretty low-level library, so I wouldn't bet on finding a player that will accept this particular file without help. If you know what the audio and video codecs inside are, you *might* be able to find a player that can reconstruct the moov atom if you specify the codecs at the command line. http://vcg.isti.cnr.it/~ponchio/untrunc.php may or may not be helpful. E. Liddell

On Thursday 07 January 2021 04:58:56 Steven D'Aprano via tde-users wrote: Not likely since Intel has proably cleaned house 5 year+ back, it is a long since discontinued motherboard. Over a decade old now. But your reference to using file on them gives odd results indeed! root@coyote:dwhelper$ file "Intel® Desktop Board D525MW — Product Guides.mp4" Intel® Desktop Board D525MW — Product Guides.mp4: PDF document, version 1.4 root@coyote:dwhelper$ file "Intel® Desktop Board D525MW — Quick Reference Poster.mp4" Intel® Desktop Board D525MW — Quick Reference Poster.mp4: PDF document, version 1.5 root@coyote:dwhelper$ file "sample_1920x1080.mp4" sample_1920x1080.mp4: ISO Media, MP4 Base Media v1 [IS0 14496-12:2003] So its no wonder at all why mplayer fails. I should rename them and see if evince can render. Which it does flawlessly, about 130 pages of them. And Copyright 2010... Thank you very much. file has earned its keep. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>