Jump to content

slonick81

Members
  • Content Count

    26
  • Joined

  • Last visited

About slonick81

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. So Natron we go! As you can see, latest win version with default settings shows no subsampling on enlarged view. The only thing we should care about is filter type in reformat node. It complements original small 558x301 image to FHD with borders around, but centering introduces 0.5 pixel vertical shift due to uneven Y dimension of original image (301 px) so "Impulse" filter type is set for "nearest neighbour" interpolation. If you uncheck "Center" it will place our chart in bottom left corner and remove any influence of "Filter" setting. The funniest thing is that even non-round resi
  2. Shure. Exactly this image has heavy compression artifacts and I was unable to find the original chart but I got the idea and recreated these pixel-wide colored "E" and did the same upscale-view-grab pattern. And, well, it does preserve sharp pixel edges, no subsampling. I dont have access to Nuke right now, not going to mess with warez in the middle of a work week for the sake of internet dispute, and I'm not 100% shure about the details, but last time I was composing something in Nuke it had no problems with 1:1 view, especially considering I was making titles and credits as well. And wh
  3. The attached image shows 1px b/w grid, generated in AE in FHD sequence, exported in ProRes, upscaled to QHD with ffmpeg ("-vf scale=3840:2160:flags=neighbor" options), imported back to AE, ovelayed over original one in same composition, magnified to 200% in viewer, screengrabbed and enlarged another 2x in PS with proper scaling settings. And no subsampling present, as you can see. So it's totally possible to upscale image or show it in 1:1 view without modifying original pixels - just don't use fractional enlargement ratios and complex scaling. Not shure about Natron though - never used it. Ju
  4. Color saturation is defined not by variety of values of any single (R, G, B) channel arcross the image but by difference between channels in given pixel. Thus color fidelity is defined by amount of steps this difference is digitised. If you have image with (200, 195, 205) RGB values in one point, (25, 20, 30) in other, (75, 80, 70) in third that doesn't mean the image color range is 25-200, it's 10 and it's lacking color badly.
  5. I was trying it when it was late beta. The core functionality worked well at that time, it was playing BMCC 2,5K raws on average quad-core CPU an 760-770 nVidia cards, debayering quality was good and after some digging I was able to dial the look I wanted to get. The interface was clumsy to a degree - panel management was painful sometimes, some sliders were off scale so it was hard to set proper values. But it wasn't too unbearable or irritating. The main show stopper for me was it's inability to efficiently save results to ProRes/DNxHD for proxy edits. It was technically possible to stream P
  6. So, some nice films were shot with Canon's high end cinema cameras, thus we should accept limitations and marketing crippling of EOS RP and buy it in desire to be assosciated with talented winners?
  7. What do loosers choose? Do winners win because of Canon? Will someone win for sure just by choosing any Canon product (specifically, EOS RP)?
  8. Set "Mismatched resolution files" (in "Input scaling") to "Scale full frame with crop". Or you can set it individually for any clip on timeline: Inspector - Retime and scaling - Scaling - Fill.
  9. 1) After russian internets it's like a victorian gentlemen's club here. But problem is present, so better take some measures. 2) Total prohibition of any political topics is overkill, as for me. You won't choke it to death, it'll still rise in indirect and ugly forms. Besides, Andrew himself has started some discussions on political topics, I guess it's important for him, too. 3) So I voted for subforum. All hot heads can quarrel there and should be banned from any other threads for trying. It will take more moderation efforts but it's lesser evil among those three.
  10. slonick81

    All things RAID

    I meet this idea from time to time, and it's reasonable, but somehow isn't proved by real life. I mean there is RAID5 made of several 2TB drives in this article as example and controller needs to read 12TB of data to rebuild it, so there is a significant chance to get unrecoverable read error during rebuild process and lose some data. But it also apllies to simple data reading. Like every 20TB of data read you should get such error, no matter is it raid6, raid1 or single drive. Then (in case of ZFS, as example) the system will detect it as checksum error, mark array as degraded and try to rebu
  11. slonick81

    All things RAID

    Random thoughts: 1) RAID should have consistency check procedure that you can assign on schedule (so it won't interfere with your work), set up priority (you may get some urgent work right in the middle of self-check), and get readable output (so you don't need to guess which drive became corrupted, at least). Most of cheap disk enclosures, as well as many cheap quasi-RAID cards don't have it and you'll notice data rot only when you fail to read it. 2) HW RAID consistency != FS consistency. I've seen some systems showing healthy RAIDs with badly corrupted NTFS/ext3 at the top. If you
  12. 1) Memory. Get MB with 4 RAM slots. This CPU has 2 memory channels, so buy 2 sticks to get the amount of memory you need. The general rule for long term run is to buy the largest capacity ones - 16GB in your case. You'll get 32GB RAM, a sufficient amount to start editing in AP/Resolve/Avid or whatever. And you can always add another 2 sticks to get more RAM (up to 64GB RAM for your platform) 2) CPU. 8700 is top one for this Intel platform so you can't get better niether now nor later (next gen Intel CPU will most likely require new chipset/MB). If you're thinking about CPU upgrade pass -
  13. I guess there is some lossless compression for "uncompressed" raw. Because 3:1 and 4:1 data rates more or less correspond to ~400MB-s of 4K30p
  14. I'm really curious to read this thread in october'18...
  15. Is it about raw or industry standart part? Compressing raw is just common practice - Red, Cineform, cDNG, Canon raw lite, it's rational to compress before debayer and leave it to post. It would be strange if Apple ignores this opportunity. Standarts... Apple introduced intermediate codec not only with obvious vendor lock-in but with platform lock-in as well. And it's fine, it's Apple in their right to follow thier business model. But somehow the industry abandoned the idea of open standard intermidiate codec, ignored other intermidiate codecs and here we now: "- We need masters in Pr
×
×
  • Create New...