Ops 0.23 is out.
Changelog excerpt follows..
Ops 0.22->0.23
- added camcorder settings option to enable or disable the battery indicator. -*test*-('")ed on 53.14 and 53.18 camcorders. please report back!
Worked perfect on my 53.14. Thats the last thing I was needing to do to my camcorder - adding the battery indicator. Thanks so much - nicely done.............
Battery Indicator update works for 53.05 (M230), 53.12 (M230) and 33.19 (M220).
Keep up the great work.
Hold on a minute. After seeing
forumer.com/viewtopic.php?t=6511>this thread:
update to the newest version of ops.......you are about 9 versions off
i went to ops .23 and got a much more numbery string, worked with burning man, and i just downloaded a video.
ops .23 is all i could find, but the ops post talks about an ops .3,.4,.5, couldent find them anywhere... this is working, so i dont know if i need a newer one, or are they more brick proof?
thanks again!
Am I late to notice this, or has everyone overlooked that BillW jumped from Ops v0.9 to Ops v0.10? Obviously, 0.10 < 0.9 <0.90>
And now we've gone all the way up to v0.23. Seeing v0.3 and v0.4 instead of v0.03 and v0.04 can surely be confusing to noobs.
So the question is: Are we on Ops v0.23 or Ops v2.3?
How dangerous is the Battery Indicator update to our cams? If there is a problem, does disabling it restore it to out-of-the-box condition?
I spent a lot of time modifying them for a Motion Camera setup and don't want to take any unnecessary chances!
Yep, Im a chicken for sure LOL but this is a great enhancement for my setup. Thanx a million for all the work on these things guys!
Tinhorn
How dangerous is the Battery Indicator update to our cams? If there is a problem, does disabling it restore it to out-of-the-box condition?
I spent a lot of time modifying them for a Motion Camera setup and don't want to take any unnecessary chances!
Yep, Im a chicken for sure LOL but this is a great enhancement for my setup. Thanx a million for all the work on these things guys!
Tinhorn
it's literally a bitflip. changing it on my older cams did nothing whatsoever to it. changing it on newer ones shows the indicator. unchecking the box restores its state.
it would be dumb of me to say that it's without risk, but with the amount of -*test*-('")ing i've put into this, plus having many people enable this by manually hexediting their usp.bin by hand, i'm fairly confident in my work.
thanx for the quick response SN's, I flipped my bit on a M230 53.05 and it worked just find (as reported by rocketsmith57)
Thanx again, I'll do the other's tomorrow and report the results for everyone's information
Tin
I flipped the bit on 5 cams, 2 of which were the same models noted by RocketSmith57 (and they worked) so I'll list those that didn't display the battery condition indicator below. I've got 3 more cams but not here so will check them another day.
as you said SN, these cams still worked ok
M200 3.40 Nope
M200 23.82 Nope
M220 33.04 Nope
thanks very much for the analysis. hopefully more people will try it out, seeing there's no apparent risk if the cam doesn't support it.
....... so i'm trying to port everything i see from the windows one into the linux one, then release it also as ops 0.23
also, i'm pretty bad at gtk gui programming. no ide.
Thanks for doing that. I am a new user of Gutsy 7.10 Kubuntu and would be very thrilled to get that. Much appreciation to you. Thanks again.
I'd also be willing to give it a try. I just successfully built ops-for-linux 0.15 on Mac OS 10.4, but the "unlock" phase does not seem to be working (at least it does not work like avidownload or mediadownload). But the UI launches under X11 with no problems.
I've been away for a while. Has there been any progress on the mass storage hack for 53.18?
only progress on my own workstation. it's difficult working through the instructions provided...it's like they're purposely ambiguous. anyways, it's on its way.