![]() Also you won't be able to play back non-DXV. mov files in other software, including Adobe and MPEG Streamclip. So for now, if you want to follow the US government's advice and de-install QT, you won't be able to create DXV. Yay.) No, we can't give an indication on when R6 will be done. The good news is that R6 will be completely QT free (and, by extension, also 64 bit. Quicktime is too much a part of our internal guts that we can't yank it out and replace it. The bad news is that that's not going to happen in R5. dxv container, it's all a bit potahto/potayto. mov files as well record from Resolume and create DXV encoded files in other software. In the future, you will still be able to playback. Since Apple deprecated QT, we've been working on getting rid of it completely. MOX is an open source alternative started in 2014, but has been pretty quiet since then. MXF is an option, but not nearly as well known or well supported. At the moment, there is no real alternative for such a professionally supported container. Magic! Of course, that all changed when Apple retired Quicktime in 2013. You could install a 3rd party codec on your computer, and then each and every app that used Quicktime could read and write files with that codec. The only thing that made Quicktime so great was its widespread support. Also, the Adobe apps can still read and write the majority of. It's our own codec, so we don't need anybody's help to read it. When you de-install Quicktime, Resolume can still read DXV encoded. You just need to be able to understand the data in that container. An application doesn't need to have Quicktime installed to be able to read and write files in a. mov is a container format and not necessarily tied to the Quicktime Player or even the Quicktime playback system. I want to eventually use Win 10 again and all my problems really started with QT. But with my experience and now this vulnerability announced, I will be happy when QT is gone for good. I am not reckless when I am online with my gig machine. Last, I also am not super worried about the current security issue QT. Also not sure if Squeeze requires QT, I am looking into this now. Not wild about the price on Sorenson Squeeze if I can avoid it. So I am cautious of any free tools as AME should be pretty solid (not the best but solid). AME was good for the most part, but a few clips after AME came out completely unacceptable for playback after re encoding and I could never fix that. Unfortunately, I found the QT player did a way better job at re encoding than Adobe Media Encoder (less artifacts). With the install method in my first paragraph, possibly we can come up with a good way to re encode videos and then buy some time as we work toward eliminating QT totally. I get that it is useful or maybe avoids extra licensing, but I am super happy to hear Joris say " we've already been working on getting rid of QT completely for the past 2 years". But I went down this road to say, QT does not really play nice in Windows for Live playback situations. Both sides have been patched now from what I read. ![]() ![]() I did see that DX12 had some BSOD issues with NVIDIA drivers. The screen tearing also went away for me when I disabled DXVA in my DJ application or if I disabled my NVIDIA card for Resolume. ![]() Win 7 was fine, so I went back to 7 for a while. I actually got some bad screen tearing with MOV files on Windows 10. I never could understand why Adobe, Serato DJ and many other big name live video playback applications all rely on QT for Windows. It is a small work around for a much bigger issue. ![]() QT no player.JPG (40.59 KiB) Viewed 12640 times In regards to the specific Quicktime vulnerability here is the official line for those who know this kind of stuff (which I certainly don't.) Note what has to happen for it to work though. So as long as QT continues to function under the hood I am not really worried about the hype around the vulnerability with using the QT program itself (which I never do anyway on the PC rig). My media server is rarely online, other than to download software from reputable companies or live upstreaming. Unless you are doing a lot of torrenting, opening a lot of unknown file attachments, or visiting these "malicious websites" then it's virtually impossible to be exposed to most of these types of exploits.but yeah, if you are using your media server on torrent sites and going to random "click here for money" and "free porn!" links then I suppose there is a risk. I think these types of security concerns, in general, at least in terms of remote hacker vulnerabilities are simply over-hyped. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |