vasile
-
Posts
95 -
Joined
-
Last visited
Reputation Activity
-
vasile got a reaction from BrorSvensson in Petition for Samsung NX1 hack
No idea but I doubt it w/o replacing the codec. Chant might eventually be able to do something about it but don't hold your breath. At the moment I see a slight chance to get:
more resolutions (i.e. 2.5K on NX1) the high rate 2.5K on NX500 (subject to dangerous manipulations on burner cam) maybe higher res and rate MJPEG out of NX1 (although TBH I do not think it would reach the quality of 150-160 Mbps hevc) with a lot of luck disable or reduce video NR (I might take a look at this at some point in the future but this will definitely involve weeks of work so not too keen to start). Basically Chant is looking into adding true new stuff.
I have been looking more on the side of tweaking what's already in there - easier than Chant's ambitions but I already picked the low and medium hanging fruits.
-
vasile got a reaction from lucabutera in Petition for Samsung NX1 hack
No idea but I doubt it w/o replacing the codec. Chant might eventually be able to do something about it but don't hold your breath. At the moment I see a slight chance to get:
more resolutions (i.e. 2.5K on NX1) the high rate 2.5K on NX500 (subject to dangerous manipulations on burner cam) maybe higher res and rate MJPEG out of NX1 (although TBH I do not think it would reach the quality of 150-160 Mbps hevc) with a lot of luck disable or reduce video NR (I might take a look at this at some point in the future but this will definitely involve weeks of work so not too keen to start). Basically Chant is looking into adding true new stuff.
I have been looking more on the side of tweaking what's already in there - easier than Chant's ambitions but I already picked the low and medium hanging fruits.
-
vasile got a reaction from Marco Tecno in Petition for Samsung NX1 hack
No idea but I doubt it w/o replacing the codec. Chant might eventually be able to do something about it but don't hold your breath. At the moment I see a slight chance to get:
more resolutions (i.e. 2.5K on NX1) the high rate 2.5K on NX500 (subject to dangerous manipulations on burner cam) maybe higher res and rate MJPEG out of NX1 (although TBH I do not think it would reach the quality of 150-160 Mbps hevc) with a lot of luck disable or reduce video NR (I might take a look at this at some point in the future but this will definitely involve weeks of work so not too keen to start). Basically Chant is looking into adding true new stuff.
I have been looking more on the side of tweaking what's already in there - easier than Chant's ambitions but I already picked the low and medium hanging fruits.
-
vasile got a reaction from vaga in Petition for Samsung NX1 hack
Battery pull means no battery whatsoever, the camera should have no power source. Turning off is not enough. If you have two batteries you need to pull both.
Will add this clarification to the next mod version.
-
vasile got a reaction from RieGo in Petition for Samsung NX1 hack
Useful (I hope) for both NX1 and NX500 users: http://***URL removed***/forums/post/57583300
-
vasile got a reaction from Marco Tecno in Petition for Samsung NX1 hack
Useful (I hope) for both NX1 and NX500 users: http://***URL removed***/forums/post/57583300
-
vasile got a reaction from samuel.cabral in Petition for Samsung NX1 hack
Read the README.txt ;-) and also take a look at nx-bitrate-map.png
-
vasile got a reaction from saintsimon2016 in Petition for Samsung NX1 hack
Useful (I hope) for both NX1 and NX500 users: http://***URL removed***/forums/post/57583300
-
vasile got a reaction from SMGJohn in Petition for Samsung NX1 hack
Read the README.txt ;-) and also take a look at nx-bitrate-map.png
-
vasile got a reaction from Hanriverprod in Petition for Samsung NX1 hack
Useful (I hope) for both NX1 and NX500 users: http://***URL removed***/forums/post/57583300
-
vasile got a reaction from SMGJohn in Petition for Samsung NX1 hack
Useful (I hope) for both NX1 and NX500 users: http://***URL removed***/forums/post/57583300
-
vasile got a reaction from SMGJohn in Petition for Samsung NX1 hack
Poll: burner NX500 for a chance [NB not a guarantee] to get "production" 2K5 high bitrate?
http://***URL removed***/forums/post/57572799
rgds
-
vasile got a reaction from RieGo in Petition for Samsung NX1 hack
resolution [show, name] means you can use resolution show or resolution name.
Presumably resolution show would list available names to be used as "name" parameter for resolution "name"
-
vasile got a reaction from samuel.cabral in Petition for Samsung NX1 hack
http://***URL removed***/forums/thread/3988168
-
vasile got a reaction from lucabutera in Petition for Samsung NX1 hack
http://***URL removed***/forums/thread/3988168
-
vasile got a reaction from RieGo in Petition for Samsung NX1 hack
1. read this: http://www.magiclantern.fm/forum/index.php?topic=5827.25
2. read this too: http://www.magiclantern.fm/forum/index.php?topic=6278.0
3. format (in your PC) the SD card with larger block sizes
4. test
/done exfat test
5. If you are a Windows [the horror, the horror, I pity you] user, either go here: http://www.ext2fsd.com/ or here: http://www.paragon-drivers.com/extfs-windows/ [if you like proprietary stuff]
6. then format your SD card in ext4, without journal and with a largish block size (8192 or 16384)
7. test again
/done ext4 test
8. report back here
There, I just gave you a replacement for tonight's sleep :-), and therefore a chance to join me in missing sleep :-)
rgds
PS. I have high hopes for ext4 since it is a native Linux format whereas exfat is Microsoft and may well be implemented as a fuse filesystem which performs much much worse.
-
vasile got a reaction from sidi in Petition for Samsung NX1 hack
http://***URL removed***/forums/thread/3988168
-
vasile got a reaction from Geoff CB in Petition for Samsung NX1 hack
http://***URL removed***/forums/thread/3988168
-
vasile got a reaction from Pavel Mašek in Petition for Samsung NX1 hack
1. read this: http://www.magiclantern.fm/forum/index.php?topic=5827.25
2. read this too: http://www.magiclantern.fm/forum/index.php?topic=6278.0
3. format (in your PC) the SD card with larger block sizes
4. test
/done exfat test
5. If you are a Windows [the horror, the horror, I pity you] user, either go here: http://www.ext2fsd.com/ or here: http://www.paragon-drivers.com/extfs-windows/ [if you like proprietary stuff]
6. then format your SD card in ext4, without journal and with a largish block size (8192 or 16384)
7. test again
/done ext4 test
8. report back here
There, I just gave you a replacement for tonight's sleep :-), and therefore a chance to join me in missing sleep :-)
rgds
PS. I have high hopes for ext4 since it is a native Linux format whereas exfat is Microsoft and may well be implemented as a fuse filesystem which performs much much worse.
-
vasile got a reaction from saintsimon2016 in Petition for Samsung NX1 hack
There's your answer: HEVC is low bitratre, AVC... not so low :-)
-
vasile got a reaction from hirsti in Petition for Samsung NX1 hack
There's your answer: HEVC is low bitratre, AVC... not so low :-)
-
-
vasile reacted to Pavel D Prichystal in Petition for Samsung NX1 hack
Dude, Tommix. Could you maybe not?
How about no to you acting like bully to all of us? Just stop. Either start contributing and stop being a dick to us, or just watch what is happening or lets ask Andrew to get you banned?
PS: This is not an invitation for you to flame spam this topic so be that kind to us, fellow cinematographers, and get better, friendlier.
-
vasile got a reaction from Pavel Mašek in Petition for Samsung NX1 hack
I think someone needs to do some more in-depth tests. I do not know how the codec works but based on previous analyses (seen in this thread) of my fish tank video, the codec uses a variable rate. This is supported by @SMGJohn codec info screenshots.
What this means is that the 160Mbit is not really the true rate, it is merely the target average rate for the codec, and that, based on the complexity of each frame, the codec will use less or more bits to encode it.
It is likely that the codec uses something like this: target rate => [min_rate .. max_rate] where min_rate and max_rate are fixed multiples of target rate.
For example (and this uses numbers coming from my hat): 160Mbit/s rate == in reality [0.5x160 .. 2x160] == [80 .. 320] Mbit/sec.
This could be easily be proved with your Lexar card by recording a static scene vs a dynamic scene - the static scene should allow higher bitrates (presumably because it would hover near the lower limit) before the crash.
-
vasile got a reaction from hirsti in Petition for Samsung NX1 hack
http://***URL removed***/forums/thread/3988168