Steve M.
-
Posts
171 -
Joined
-
Last visited
Content Type
Profiles
Forums
Articles
Posts posted by Steve M.
-
-
he
i dont have a shogon but on there website i can read
4K 2160p30 only
No clean out with HDand at dpreview...
For NX1 owners there isn't as much of a beneift over in-camera recording (8 bit 4.2.0 vs 8 bit 4.2.2 and no compression), but I....
maybe this is helping?
It does help, Thank you! The question still remains, Hypothetically, if NX1 did output clean 1080, and you hooked to a Ninja Star, which states it records 10bit 4:2:2, so if I hook the NX1 up would it record 8bit?
The benefit is not transcoding the H.265, That in my mind is worth the cost.
-
I have a stupid question that is probably common knowledge for most of you, but here goes...
I've read the NX1 does not output a clean HDMI 1080p signal, okay I understand that part, but lets say it did, and you wanted to use a Ninja Star to record that 1080p to ProRes. The Ninja Star records to 10bit 4:2:2 in all the ProRes flavors, however, the NX1 shoots at 8bit, correct? So, my question is, if that's true and you could record to the Ninja, are you getting a true 10bit 4:2:2 file? It would seem to me that's like importing ProRes proxy files into your NLE and outputting to ProRes HQ, you gain nothing in that uprez. Second question, the NX1 records to H.265, would the NInja Star even record that codec? Does the Shogun record that codec? I appreciate your input!
-
I'm confused as to what you're proposing we steal?
That makes two of us!
1.) if the licensing fees for these codec are reasonable
Can't we just steal the codecs that need to be of a reasonable cost? I was being facetious of course!
-
It's means that:
- If the licensing fees for these codecs are reasonable
- and there's a market to recoup the cost of licensing and development time
- I can relatively quickly create a transcode tool which is much faster than anything based on ffmpeg
Can't we just steal it!!!!!!!!!?
-
Without seeming to look like an idiot, what the hell does any of this mean in terms of how it can or cannot be used right now for the H.265 transcode?
-
I agree, it's almost eerie, perhaps you are right, listen in on customers via their own devices....brilliant, I'm glad I thought of that! I don't know what your take is, but I'm thinking Samsung had a meeting sometime ago, after looking at this market, and decided they could take a chuck of it by giving people what they want, or at the very least, giving it one hell of an effort.
-
I've read this newest update doesn't remedy the floating line issue that some of the NX1 users are experiencing. I only hope Samsung fixes this soon before adding features that we all want, but first things first. If they can do that, they are going to win over an even larger portion of this market.
-
Samsung releases yet another NX1 firmware update 1.21 this morning. I've been accused of being a Samsung fan boy, which is ridiculous, but I will admit, I am definitely a fan of a company that not only listens, but acts upon it. You have to stop and wonder what they're going to do for an encore.
-
I am here because I’m interested in the minutiae of technical camera specifications and capabilities.
That was sort of the point of my response. That you are criticising behaviour that is the entire purpose for most people even being here.
Its like going to an antique website and saying “What do you care how old it is”?
It’s perfectly acceptable to hold that point of view, but then why go to an antique website?
And you could hardly expect to go to an antique website with that point of view and not be told to fuck off.It doesn’t matter why I want to learn about the minutiae of technical camera specifications and capabilities. I do it for my own reasons. I certainly do not do it with any concern to providing you with material you may or may not care about.
Your comment was supercilious and a pathetically transparent attempt to belittle peoples interests and curtail their passion for knowledge. Therefore, it deserved nothing but antipathy.
No, not true, it was merely an observation. I would hardly call arguing over nothing a passion for knowledge. Read through those posts, there's nothing constructive about it. Although, I will admit, everyone is entitled to their opinion. That's all you'll hear about this from me, I certainly don't want to hurt your feelings in your quest for knowledge!
-
Fuck off! That is my response to that.
This is a gear head website, if we weren't interested in the minutiae of technical camera specifications and capabilities, then why would we be here?
That's intelligent. I ask myself that same question, why are you here?
-
Based on what I see on Vimeo and in comment sections the answer is "random hand held street scenes with a music bed"
Precisely. Yet, you'll read on and on how the camera won't do this or that, and that is exactly what those individuals are shooting.
-
I have a question, what the hell are you guys all shooting that's so significant that you'll sit here and split hairs over DR, gamma, this, that, and the other thing? Are you producing a multi-million dollar blockbuster, or, rather is it something like some shots of a trash can, may be the sky and a few trees posted on Vimeo? You take one persons findings and opinion of a camera and suddenly you're all high ranking DP's of the world, trash talking this and that because it isn't 10 bit, it doesn't have enough DR, it doesn't compare to this camera or that camera. Who cares? Show me something you've done that's so significant that I should care. I'll be waiting!
- MatthewP, iamoui, fuzzynormal and 1 other
-
4
-
why?
Because there are those jobs that I just don't need a 4K master, and the added resolution of 2.5, the little bit of reframe of 2.5, the faster transcode from H.265 with 2.5, that's why!
-
It appears they changed the 2.5k spec to 4k (DCI 4k and UHD)
Depending on the image quality, I might consider an nx500 + nebula 4000 lite combo.
Exactly. I wished they would have stuck to that 2.5K spec. Bummer.
-
I get the H.265 codec is the future, but man I wish this offered H.264 recording as well, if that's even possible to have both? Or, perhaps the 2.5k isn't possible without the H.265? It would be a nice B cam for the NX1
-
What are your output settings. If you output to the setting they say to use ( If source is 4K H.265 (30P) --> Select 1920x1080 option.) at 1920x1080 it is faster but then you are not editing with full 4k files. I did that for many of my first videos but when changing it to quality (same as Source) it takes a lot longer and creates files 10 times larger.
But if you are not going to do any zooming in when editing the 1920x1080 option looks the same as long as you are editing to export to HD 1920x1080 so you are changing it to 1920x1080 to start with so it will edit more easy and have smaller file size. It still keeps the great quality of the 4K files just down to 1920x1080 to edit with and use.
The only thing you mess is if you want to do a digital edit zoom in the file is all ready at 100% VS the larger files that you can then zoom in on a lot. So if you are not going to zoom in when editing then i see no reason to convert to the larger files when you are going to export to HD in the end.
But even if you do zoom in on the converted 4k to 1920x1080 option file it still has so much info in it doing a edit zoom still looks ok.
Here is what it looks like this is the full 4k file size zoomed in
Here is the the same file zoomed into 200% but from a converted file to 1920x1080 you can see a little loss but with a moving video it is super hard to see any difference.
I did try that option and when I compared the 1080P & ProRes LT (same as source) 4K image, sized the same in QT7, to my eye the 4K sized down was sharper. So, the real test is transcoding to 1080P then seeing, is it the same as doing a 4K to 2K timeline edit, as far as resolution output. Yes, of course you lose the re-frame capability with 1080P, but save a lot of transcoding time, if you do not care about a 4K master.
-
Concerning multiple passes, you're probably right about that and for good reason, a 3-4 minute NX1 H.265 clip transcoded in iffmpeg, you could practically grow a beard before that would be complete!
-
Okay, I'll buy into that, makes sense. So, basically this guy has figured out a series of settings that make for a faster transcode, which you could duplicate within Iffmpeg IF you knew that particular code? Good luck, getting that from iffmpeg, they are extremely vague in there replies to the use of their product, which isn't a bad thing, it's just a thing. Bottom-line, even if it is a front end to iffmpeg........it's free!
-
So in theory it should be the same speed as IFFMPEG.
Meaning, you've tested it and are getting faster speeds? Put it this way, every person that has this, posts the same comments, it's way faster than any other transcoder at present, and I can confirm that on my end.
-
Thanks for the link, but this converter is just another front-end for ffmpeg.
Okay, then explain why it's significantly faster than iffmpeg on my MAC? Image quality? I can't see a difference.
-
Kind of a vital piece of info missing from your post Steve. What's the app!?
Damn, I guess in all my enthusiasm, I did forget that link, sorry about that!
http://sourceforge.net/p/rockymountainsmovieconverter/wiki/Home/
Andrew, let me know what you think about this application.
-
Ran across a new FREE H.265 transcoder created by an NX1 user. I would not have believed this if I didn't try it myself. Here's the scoop; a one minute UHD - 4K, 23.98 file, converted to ProRes 422 LT., this on a 2009 iMAC, 2.8GHz- i7, 16 GB RAM. Transcode time; 3 minutes - 51 seconds @2.71GB output file. I don't know about your experience with this file, but that is 3-1/2 times faster than iFFMPEG. The file looks clean to my eye, as clean as anything from any other transcoder.
-
iFFMPEG is not slow.
H.265 is complicated.
There's not a faster converter available and there's not really the combined hardware / software support available to improve performance for H.265 yet.
Intel's performance has flattened out since 2012, they are shrinking the chips, running cooler... but they're not giving us much extra performance.
Okay, you'd know better than I would, but just for laughs, give Bigasoft's video converter a try. I'm only trying the trail version but it would seen that encodes faster.
-
Well, I did give the Brorsoft converter a try, and the only thing It will output is the audio. Can't get it to output video? Perhaps operator error, but everything looks set correct.
Samsung NX1 -Ninja Star - Atomos Shogun
In: Cameras
Posted
I think I grasp that. So, anything coming out of the NX1 externally would be uncompressed, which throws the H.265 out of the equation. I guess all of which is a moot point since the NX1 doesn't offer a clean 1080 output. At the price the Star is going for, It would only make sense to record to that an avoid the transcode, especially for the slo-mo aspect. Let me guess, the camera wouldn't output the slo-mo!?