Yeah, from what I read (since I don't have any c-mount lenses myself) the typical scenario is shoot in 1080 and crop in post to 720 for final delivery as 720p24 or shoot 1080, crop out vignetting and upsample to 1080. IMHO, the benefit of cropping in camera, especially for the first scenario, would be more efficient workflow and potentially higher image quality, because bitrate bandwidth does not have to be spent on encoding stuff that will be cropped out anyway.
Emotions, crazy requests, donation messages go HERE
- Thread starter bwwd
- Start date
sweetdollar
New member
Barry_Green
Moderator
Wow... you go, Vitaliy!
Just wonderful. A new run on units and folks coming to the forum obfuscating the work we try to do. All the while we still *might* have the Panasonic counter-hack firmware to deal with..
I expect a lot more irate/disappointed/disillusioned people showing up soon.
raymondluo
Well-known member
How bout looking into hacking the LX5? It's got AVCHD Lite capabilities so it might be very similar to the GF-1. (But with built in Leica lens)
I don't think so.
The LX3 firmware is encrypted, and so will most likely be the LX5.
Will need to wait for firmware update to be sure.
low frame rates on GF1 with mjpeg. 1 frame a second (for easy timelapse)
yes i know it is not possible, but this is the crazy request thread after all
--
ShootPlanner for iPhone OS
A photographer’s assistant & PA rolled into one http://itunes.apple.com/us/artist/huwtudorware/id382310164
yes i know it is not possible, but this is the crazy request thread after all
--
ShootPlanner for iPhone OS
A photographer’s assistant & PA rolled into one http://itunes.apple.com/us/artist/huwtudorware/id382310164
Last edited:
also how about a list of the expected features being worked on for each next release of ptool, so if the next one is 3.41, have a sticky with what is expected to be in it.
should mean we can get excited even before the release, and keep the energy going on the forum
should mean we can get excited even before the release, and keep the energy going on the forum
Last edited:
I am not sure this is possible. How can you plan which hacks will work and which won't until after the hacks are released and tested? This is not like a regular software development project where you plan to release certain features at certain times.
Vitaliy may get up one morning and find something out in the code and you get the result right away. Other times, it may require dogged trial and error testing. We should be happy with whatever nuggets fall out of the process and stop trying to second guess where the progress will be made. We will get what is possible when it becomes obvious that it is possible. The GH1 and the software are very complex.
I for one, am thrilled with the features and tweaks that have already been unlocked. The camera is much more useful now and produces much better results. I bought my GH1 way before the hack began because I liked the camera and system better than the alternatives at the time. I am so pleased with the hacked camera that I probably will skip the GH2 and wait for the GH3 before upgrading. I am certain that is NOT what Panasonic wants to hear and that is why they will make it very inconvenient for the hack to continue.
Vitaliy may get up one morning and find something out in the code and you get the result right away. Other times, it may require dogged trial and error testing. We should be happy with whatever nuggets fall out of the process and stop trying to second guess where the progress will be made. We will get what is possible when it becomes obvious that it is possible. The GH1 and the software are very complex.
I for one, am thrilled with the features and tweaks that have already been unlocked. The camera is much more useful now and produces much better results. I bought my GH1 way before the hack began because I liked the camera and system better than the alternatives at the time. I am so pleased with the hacked camera that I probably will skip the GH2 and wait for the GH3 before upgrading. I am certain that is NOT what Panasonic wants to hear and that is why they will make it very inconvenient for the hack to continue.
i completely agree with that. i too bought my first gf1 a week after launch after seeing it in a shop in hong kong and liking it's specs. to then get 100mbs, 422 and manual has been an incredible ride, i now have 3 hacked gf1's set up for different shoot types 
rogar-Happy(DBG):
but it sometimes feels the board needs a bit of injection away from 'can i hack this camera i bought in thailand/zaire/guatamala' :love4:
rogar-Happy(DBG):but it sometimes feels the board needs a bit of injection away from 'can i hack this camera i bought in thailand/zaire/guatamala' :love4:
David Cole
Well-known member
The crazy request thread is certainly the right place for this....
There is some hope that two GH1s can be used for stereoscopic 3D. My organization, beampath3d, has shared our own 3D efforts in this forum. I'm not sure how many GH1 owners are interested in 3D, but, it seems like it's more than just us.
So...
It would be really helpful if the Gh1 could wiggle some external output (e.g. the data+ line on the USB port) when it's fully booted up. We'd measure the wiggle from two cameras to indicate the sync between them. This is similar to how a stereoscopic LANC controller works.
Any chance of a patch to do something like this?
There is some hope that two GH1s can be used for stereoscopic 3D. My organization, beampath3d, has shared our own 3D efforts in this forum. I'm not sure how many GH1 owners are interested in 3D, but, it seems like it's more than just us.
So...
It would be really helpful if the Gh1 could wiggle some external output (e.g. the data+ line on the USB port) when it's fully booted up. We'd measure the wiggle from two cameras to indicate the sync between them. This is similar to how a stereoscopic LANC controller works.
Any chance of a patch to do something like this?
Well there are certain long-term targets being worked on, as detailed in the Dev. forum. These may come to pass, however not guarantees or time commitments. And then there are unplanned discoveries.
Right,
I spent yesterday afternoon tweaking and trying some other people's settings. It seems that most people are testing on charts, which yes does something, but more than anything, to me, shows how the lens performs. I find that most of my video work has other issues, being with contrasted lighting or at gigs (also contrasted lighting): my concern is the fact that I cannot get the AVCHD to handle a gradient. So last night I was testing shooting a candle near a wall. In the Zacuto shootout (pre GH13), the GH1 showed serious issues with the candle and halo-rainbowing or mottling of the gradient. I still get this heavily, but have managed to almost eliminate it with MJPG.
Therefore, I was wondering why the MJPG compression settings are so abstract and yet broken down (as presumably I almost have the perfect balance of low compression in "low detail" areas, as I assume this is what I need), when the AVCHD, which is a much more complicated codec, just seems to have an overall bitrate. GOP should not even really be an issue, as with a static camera, where the detail i am after is in the elements that are not moving, even if it were keyframing every frame it would still not clean up the gradient as well as a simple jpeg shot of the same framing.
I spent yesterday afternoon tweaking and trying some other people's settings. It seems that most people are testing on charts, which yes does something, but more than anything, to me, shows how the lens performs. I find that most of my video work has other issues, being with contrasted lighting or at gigs (also contrasted lighting): my concern is the fact that I cannot get the AVCHD to handle a gradient. So last night I was testing shooting a candle near a wall. In the Zacuto shootout (pre GH13), the GH1 showed serious issues with the candle and halo-rainbowing or mottling of the gradient. I still get this heavily, but have managed to almost eliminate it with MJPG.
Therefore, I was wondering why the MJPG compression settings are so abstract and yet broken down (as presumably I almost have the perfect balance of low compression in "low detail" areas, as I assume this is what I need), when the AVCHD, which is a much more complicated codec, just seems to have an overall bitrate. GOP should not even really be an issue, as with a static camera, where the detail i am after is in the elements that are not moving, even if it were keyframing every frame it would still not clean up the gradient as well as a simple jpeg shot of the same framing.
michaelmonzon
New member
Crazy Requests; It would be lovely to turn the evf sensor off, I would also find the focus assist very useful during rec.
I have more of a question than a request. Is anyone still working on the GH1 hack or has interest moved to the GH2? I'm wondering if there is any chance of an HDMI feed whilst recording or whether to move to another camera because it won't happen. Does anyone have any idea? Thanks.
Hello Vitaliy,
I would only humbly add that all what I said in my previous post #2953
regarding the GF1 firmware 1.23
is obviously, still valid for GH1 firmware 1.33.
So if you would consider to give a look to these 1.x3 firmware files
I think that all the Gx1 users will be interested...
(I have checked and the files are still available for download)
Thanks for the attention.
I would only humbly add that all what I said in my previous post #2953
regarding the GF1 firmware 1.23
is obviously, still valid for GH1 firmware 1.33.
So if you would consider to give a look to these 1.x3 firmware files
I think that all the Gx1 users will be interested...
(I have checked and the files are still available for download)
Thanks for the attention.