Jump to content

agolex

Members
  • Posts

    351
  • Joined

  • Last visited

Everything posted by agolex

  1. You're probably right. I mean, if they advertised 8ms and delivered something really abysmal, that might be noticed. So it should be half-decent at least.
  2. I believe people are doing less and less for the heck of it. Everything has to lead into something. Also with companies like Samsung contacting underground software makers (if it's true), they might be working for the big players already.
  3. Rolling shutter in 4K has to be reeeally nasty -> shot at 40 seconds.
  4. I have no idea. Couple of entries about the audio, video and stuff. Possibly time code related, too?
  5. Premiere handles it nicely, Resolve (at least 12 and for me) is a PITA. No audio unless you rewrap into .mov and after that I'm having major issues as well (might be Windows 10 or the beta release, though). Sony uses some non-standard audio encoding and XML metadata files. Nothing major, though.
  6. Turns out I've had the wrong Quicktime version installed, it probably did an auto update. With the QT that comes with Resolve now everything is working like a breeze. EDIT: Well, on first try at least. Ah well, never mind, I'll just, um, sleep instead.
  7. I'm on 1.4, yeah. Sorry, but I have no time to test right now. It's no biggie, though, I'm not even sure anymore I had the issue, it might have been just the auto brightness of the display. Should have probably just shut up.
  8. Oh, I'm just retarded, I always use the newest stuff because I'm not happy with the old and hope for fixes and improvements in performance. To be honest, this is the first time in my life I find my PC sufficiently stable and fast to do any serious work on it (except writing, gaming or whatever). I wasn't content with Resolve 11 and I wouldn't have wanted to get into filming before because the image quality I could have afforded wouldn't have done it for me. Same goes for Windows. Before 10 I always felt it had too many bugs, was too slow, too many issues with USB and so on. I'm a strange person.
  9. So I've really been falling in love with Resolve during the last few weeks in terms of ease and smoothness of the edit, but I'm now experiencing grave issues that have are pushing me to the brink of despair. Shot an event on Sunday, started the edit, realized I had to do something to the files in order to be able to use the audio, rewrapped them to .mov with ffmpeg, started editing (extremely slow in 4K, tried to tweak settings, and it got better), then moved the files from my RAID to an SSD, because the HDs were just too slow. Relink seemed to work, but with the expansive timeline of around 20 mins worth of clips, I can now hardly work with it. At times is fine and speed is OK, too, but more often than not Resolve starts to put in a preview frame in the timeline here and there, gets stuck on one frame in the preview window and then does nothing. No playback editing possible, the playhead just doesn't do anything if I move it and press play. If I quit Resolve, QTDecoder keeps lingering. After relaunch, sometimes, it starts to work, but more often than not it doesn't. Here and there I get a green frame or red exclamation mark on a clip preview or two. Never had that before. Does anyone have suggestions for a fix? I've already put in quite a few hours trimming the clips, so it would be great if I didn't have to start from scratch. Have read about Resolve having issues with .mov clips in Windows, but I have no idea how to get it around it and have sound. Also I don't know whether, if I transcode to ProRes now and try to put the new clips in, I'm losing my timeline and progress. I've messed around with playback settings a bit, tried to change the pre-allocated RAM size and whathaveyou, but the issues keep coming back, even if I revert to default settings. My rig: Core i7-4930K @ 4.1GHz, 64G RAM, GeForce GTX 970, newest drivers, Windows 10 Any input is appreciated! Mattias, maybe you have a clue?
  10. That must have been quite the night. Thanks for sharing!
  11. Sweet, lovin the shots and grade!
  12. Think I've experienced something one of these days, too. Probably gonna happen everytime Samsung changes something major they don't have a full grip on (i.e.: almost everything). Still love what you can do with the DIS and vintage lenses, though. Thanks for your input anyways!
  13. Grats on that and getting the name right for the first time. Enjoy the new camera!
  14. Lookin' great! What settings and lens(es) did you use? EOSHD LUT, I suppose? Just got a Helios 44-2 f2 and it works so beautifully with the NX1. I'd appreciate more info on the stock business as well, might give it a go.
  15. It's really doable with the decent stabilization, but you have to hold pretty still. Shooting 1/4 25 fps and then speeding up in Resolve 400% (as I haven't figured out yet to speed it up 500%). Still trying around, though. Well, we have to go back to old techniques to get some freshness going.
  16. Went out with the RX10M2 yesterday and did the same. On horses at dusk. Went without a tripod and realized that at 1/4 it's really hard not to screw up the images, but it's kinda doable with SteadyShot.
  17. I do like the aesthetics very much, just not how it was filmed.
  18. Ditto on that. At times, 1600 even doesn't do. Too much nasty color noise.
  19. RX10 II works with it, but it's pretty limited (same goes for the A7RII probably). E.g. you cant't shoot video using a Picture Profile. I've told them in January when I got the A7s, but naturally nothing has happened since then. If more people requested this feature perhaps this would be implemented. It's a real shame, too, because the app has the best image of all the remote apps I've tried.
  20. RX10/100 only have contrast detect, no phase detect. http://***URL removed***/articles/1652088044/sony-an-eye-on-focus I always get eye cancer when reading dpreview, thanks to the nice white on black background...Who needs good UX?!
×
×
  • Create New...