Forums
Search
 
Notifications
Clear all

Search result for:  https://onhour.ru

 Search Phrase:
 Search Type:
Advanced search options
 Search in Forums:
 Search in date period:

 Sort Search Results by:

Page 4 / 4
#Post TitleResult InfoDateUserForum
File informations suggestion  1 Relevance9 years agoLionSpeckFeedback
  I have some features request on the new release of the codec: firstly, file previews. For the 8-bit files (both YUV and RGB(A) as far as I've tried) previews work just fine, just as you'd expect; for 10/12/14 bit files, previews don't work, you just see the "video" icon (or in my case the VLC icon). Of course it's not a dealbreaker, but it'd be nice if solved. The second request I have is some sort of "dictionary" implemented in the codec itself that tells QT which preset you chose when encoding the file, to distinguish between YUV (444, 422, 420, 400), RGB(A) and different bit depths. With "dictionary", I mean the actual name corresponding to the format ID that you can see with a program like MediaInfo, which (as you can see in the image) tells you only the format ID instead of a "full and understandable" name. Attachment : mediainfo.png
RE: MagicYUV not encoding  1 Relevance9 years agoLionSpeckHelp & Support, Troubleshooting
  I just tried saving the PSD 32 bpc grayscale to 32bit floating-point TIF, but same result as the PSD file itself (and the EXR file I also tried): Fusion will see 8 bits color depth only. In the photo you can see on the left the Ps "real" 32 bpc image, on the right, there's what Fusion makes me see; and again, I set "float32" in the loader node. Attachment : ps32bpc.png
RE: MagicYUV not encoding  1 Relevance9 years agoLionSpeckHelp & Support, Troubleshooting
  Ok, so I know little about code, so I unfortunately have to leave you the AE's internal troubleshooting to you; what I can help you with is testing, so let's begin: I tried opening a 14-bit RGBA (64bits total) MYUV file exported from Fusion in AE and it told me "Millions of colors+ (Premultiplied)". I made some researches whithin the program itself and I'm pretty sure the plus means it's got Alpha and the "Premultiplied" means it's not a "Straight" Alpha channel, but it's combined with RGB.I then imported a tif file containing a 10-bit image (the same I used in the Fusion comp) and it told me "Trillions of colors", so I have the same behaviour you experienced: it thinks the MYUV file is only capable of 8-bit. I fixed it with the piece of code you provided above, thanks a lot for that :3It lets me export high bit depth MYUV files now, but in MOV only. That's not an issue for me, but it's just so you know, AVI is still maxed out at "Millions of colors", which means that it probably isn't caused by the QT encoder.As for the crazyness of the so called "professional" system, I know, that's incoherent, but when you have to work whith Apple's "closed" ecosystem, bad things happen a lot of times. I remember once there was a QT plugin that used to make a lot of formats compatible for Mac, but Apple decided to change how plugins got handled and everything got screwed up. And that's just an example. How do you explain that QT's encoder/decoder is 32 bit only for Windows?!About the last bit you wrote: AE will still refuse to import a .mov saved by Fusion as Trillions of Colors.I just imported a 14-bit RGBA file exported from Fusion into AE and it tells me it's "Trillions of Colors+" as it should be, so either it's really magical or we have some differences somewhere. For instance, I still have AE version CC 2015, you might have the 2017 one.I also have some interesting news on the last problem I had: AME wouldn't export high bitrate MYUV videos. The XML file I modified is not in an AE folder, it's in an Adobe common folder, so its settings are shared between all programs, included AME. Now, I don't think the problem I had was caused by the piece of XML code missing, because I noticed I forgot to set an important value: I put as an export format 10/12/14 bpc, but whithout modifying the overall output bit depth, so I was trying to export 10-bit (or 12 or 14) RGBA whith 24 bits of total throughput. I'm a genius. So, fixing that, solved the issue.Thanks again a lot for the help! Attachment : ae.PNG
RE: MagicYUV not encoding  1 Relevance9 years agoLionSpeckHelp & Support, Troubleshooting
  In case you were wondering about the "3D text" composition, here's the screenshot of the nodes flow. Attachment : flow.PNG
RE: MagicYUV not encoding  1 Relevance9 years agoLionSpeckHelp & Support, Troubleshooting
  Here I'm providing the AME log with the errors.I also tried again with Fusion to check if I was using a 10/12/14 bit output format, but I wasn't, so it seems to be a different kind of problem. Attachment : amelog.PNG
RE: MagicYUV not encoding  1 Relevance9 years agoLionSpeckHelp & Support, Troubleshooting
  I tested the codec further, discovering that (on my machine) it won't transcode anything using higher than 8 bit presets. I exported a Fusion comp to CineForm AVI (so AME had to forcefully convert to QuickTime), 24 bit RGBA. I created one by one presets taken from CineForm ones (i double checked and no options were avoiding the codec to use 8+ bits per channel), replacing the codec with MYUV for each one and using different file names to identify the actual bit depth and color space. It turns out that all of the 8 bit exports worked just fine, while all of the others failed. -LionSpeck Attachment : ame.PNG
MagicYUV not encoding  1 Relevance9 years agoLionSpeckHelp & Support, Troubleshooting
  I was thinking about buying the Ultimate MYUV codec, but I wanted to try the trial out first to check if it was compatible. My usage of the codec would be lossless AE exports (through Adobe Media Encoder) and BMD Fusion renderings. When I attempted to export a Fusion composition (it uses QuickTime's codecs), it started giving me errors about "not being able to write the frames", eventhough (after enabling logging and retrying) MYUV didn't write any log / error. I tried using AME, succesfully (only with some presets). Apparently, it transcodes (from CineForm) with no issue, but it won't encode.OS: Windows 10 64-bit; CPU: i5 4690K (tried both enabling and disabling the "CPU optimization" during installation)I was wondering if I could solve this problem to be able to upgrade to the latest version of MYUV; if you need any additional information or test, just ask! -LionSpeck Attachment : fusion.PNG
New article - Video codec benchmarking done right  1 Relevance9 years agoBalázsNews and Announcements
  I recently published a new article on the site: Video codec benchmarking done right. It details the method how the benchmark figures for MagicYUV were obtained and how can you also run your own accurate video codec benchmark. Enjoy!
Page 4 / 4