peonel wendyah rosebelle

0 views
Skip to first unread message

Azalee Freas

unread,
Aug 2, 2024, 10:54:15 PM8/2/24
to doormumolef

I have to run a virtual machine with VMware Player (version 16) on a HP ProLiant ML350 G6 Server. I already had some hardware compatibility problems in the past, so before installing anything I want to be sure that the machine is compatible. Here you can find the specs. I think that the most critical component should be the processor, which is a Intel Xeon Processor L5506 (2.13 GHz, 4 MB L3 Cache, 60W, DDR3-800).

The latest release of many Adobe products is not fully compatible with Catalina. OSX 10.15 completely dropped support for any 32-bit apps so Adobe is not the only casualty. Most of the components in most complex apps are now 64-bit apps, but all it takes is one block of code somewhere deep inside an app to kill the process. The problem with some forms of Quicktime is that Apple didn't exclude the QT player from the 64-bit spec so if you render to a codec that uses only 32-bit technology Catalina

When rendering, I had to click 'lossless' and then click the format options and change the Video Codec to something else (e.g. Apple ProRes 422 HQ) and QuickTime played it fine. Apparently QuickTime just doesn't like when the it is set to Animation but obviously if you need to use that I'm not sure what the fix would be. Hope this helps

The latest release of many Adobe products is not fully compatible with Catalina. OSX 10.15 completely dropped support for any 32-bit apps so Adobe is not the only casualty. Most of the components in most complex apps are now 64-bit apps, but all it takes is one block of code somewhere deep inside an app to kill the process. The problem with some forms of Quicktime is that Apple didn't exclude the QT player from the 64-bit spec so if you render to a codec that uses only 32-bit technology Catalina won't play it. It's that simple, and there is nothing that Adobe can do to change how QuickTime works. Your only option is to render to a compatible format. If you use a lot of 3rd party plug-ins and even scripts you will also have to wait for those to catch up to 64-bit. Don't count on everyone that has ever made a plug-in for AE to spend the money and time required to update their product to 64-bit.

Apple warned everybody that this change was coming and that you had to be careful. That's why I have not upgraded yet. I won't for a while. Just before I do I will make a mirror fresh backup (mirrored copy) of my boot drive so that if there are any apps critical to my business that stop working after the upgrade I can revert to the previously working OS in a matter of minutes. I do this automatically every 30 days with my machine all the time anyway. I have for years. I use a boot drive cloning app that I start on the last Saturday evening of the month so I am never without a way to boot to a backup that was working fine. My whole computer could burn down and I could buy a new one, turn it on, and boot to the cloned drive and be right back to where I started in just a little more time than it takes to turn on the machine. It's not a good idea for anyone that makes their living to update to the next generation of their OS without doing a lot of research.

Could you share the Boot drive cloning app that youre using? I'm interested in preventing apple's future 'innovations' on my system. I too avoid any updates where ever possible, but not possible when purchasing a newer mac from apple. Although I might return this 16 inch Macbook pro as I'm upset on the daily with its issues.. like the .mov files not playing on quicktime. It's one of many so far. You know, usual annoying stuff.. uneeded touch bar, running super hot, battery seeming to drain quickly, powered by thunderbolt hence no signal that its charging on the outside, it also seems to press keys or the track pad when i dont want it. Disabled the deep 2nd click on the trackpad, you know.. usual apple stuff. But, I'm also getting a weird screen scramble when i apply too much glow effect in AE. 5 days into owning this and there's already several isses. Arg, apple.

Quicktime is in a weird halfway world at the moment, where it still deals with older legacy formats, but thewir more recent player doesn't cope with those formats well. Prior to Catalina, you could still install the legacy Quicktime 7 player, which would play any old Quicktime file without argument. But the player no longer works in Catalina. Adobe apps still recognise most of them.

Apple is crazy to be abandoning so many codecs that are still used widely in production workflows, but I've given up trying to understand Apple's approach to professional users. If they had opened up their codecs to multiplatform use years ago they would own the codec market today, but... Apple.

I found my way out by exporting .mov from after effects, taking it into premiere and exporting h264 (mp4). Because for some reason its not allowing me to export through Media Enconder when i try it in After effects. Crazy.

I also can't understand when QuickView was usually the go-to for when something did not open...Now can't even save us from the process of having to import a file into a third-party tool just to preview a plain Animation (previously formatted with Quicktime7).

"Posting a little tip that corrects a little annoyance with Mavericks and Yosemite. It is no longer possible to preview DNxHD Quicktimes (and all other QTs in codecs other than Prores or H264) with the space-bar.

It turns out that the old behavior can be recovered by "transplanting" the quicklook components that handle quicktime files from a copy of OS X 10.8.5. It works fine - although you need to redo the steps when you update the OS, and you need access to a machine with 10.8.5 to grab the files."

Hear Hear! CD players became obsolete with the advent of ripping CDs to a local server - NAS - which was in turn obsoleted by streaming services. The only caveat is that one should have a reliable connection to these via the net.

I suggest getting at lease one 5 unit, simply because it offers the additional feature of a line in jack that can be very useful for incorporating third party kit like turntables or Echo Show into the Sonos system. Kit so wired in can be then heard on all or any Sonos speaker in the system.

My problem is that I get the error no compatible source found for the current browser environment (0x10600003). In fact, I get that error when I go to as well (i.e. an official azure media player demo).

It seems the 0x10600003 error code implies Autoselect failed to find a player. Note that Youtube videos work perfectly in my environment. My OS is Ubuntu 14.04, and the browser is Mozilla Firefoz 41.0.1. A previous unaccepted answer guided the op to install and enable Silverlight. I can't expect all my users to do that. How do I get playback to work?

Azure Media Player is built on 4 different players, a DASH player, a Flash player, the Silverlight player, and the native implemented player for the browser you're watching the video on. These different "Player Techs" playback different protocols supported my Azure Media Services- DASH, Smooth, and HLS.

AMP intelligently decides which player/playback protocol to use for a specific/device or browser by looking at what technologies/features the browser supports. First, it'll check if the browser supports Media Source Extensions. MSE allows the browser to playback adaptive bitrate streams without the use of plugins like Flash and Silverlight, it's supported in most modern browsers, but not always in older versions of those browsers. If MSE is supported,AMP will playback your content using the MPEG-Dash protocol and you're good to go. If MSE isn't supported, AMP will check and see if Flash is installed and then if Silverlight is installed. If either of these are true it will play back using the installed plugin and the Smooth Streaming protocol. If neither of them are installed, it will try to play back via the native html5 video tag implementation of the browser. This is completely dependent on the browser, and most do not support ABR streams natively (except, for example, Safari via HLS)

Your short answer, given this background information, is that because you are using an older version of FF that does NOT support MSE, you need to install either Flash or Silverlight to play back your adaptive bitrate streams.

a few mitigations for you/customers:1) install Flash/Silverlight2) download an up-to-date version of FF, we recommend this for sure because MSE is supported in v42 but in v47+ Google Widevine protected content is supported, which means you can playback DRM encrypted content without Silverlight

NLS audio books can be played using Android devices with Android OS 4.1 or later (smart phones, tablets, Kindle Fire). These devices use the BARD Mobile Android app to download and read books on the device. Second-generation Kindle Fire devices can download the BARD Mobile Androip app from the Amazon Appstore. BARD Mobile will not work on Kindle e-book readers, only on the Kindle Fire tablets (Fire, Fire Phone, Fire HD 10, Fire HD 8, Fire HD 6, Fire HD 7, Fire HDX 8.9, Fire HDX 8.9 WAN, etc.)

Other commercial devices available for purchase from Third-Party vendors are also compatible for playing NLS downloadable audio and braille books. A complete list of devices with features, prices, and vendor contact information is located at the NLS website for Digital Audiobook Players.

Please be aware that in providing this information to our patrons we are not endorsing or recommending these products or suppliers. We will provide similar information on other devices or suppliers as we become aware of them.

I've been running ubuntu 19 (64 bit) on VMWare Workstation 15 Player for 2 months now. There was no problem in running the virtual machine till now, but today when I tried running the machine, it gave me the following error:VMware Player and Device/Credential Guard are not compatible. VMware Player can be run after disabling Device/Credential Guard. Please visit _CG_DG for more details.Following are the screenshots for the error:Error regarding device credentialsError code after returning to home screen

c01484d022
Reply all
Reply to author
Forward
0 new messages