BTM_Pix

Packet Capture on Android and then some manual requests from a browser and/or something of my own creation! Any additional sessions can bring a bit more to the table if you invoke functions that the G80 has that the GX80 doesn't to see if it can be persuaded to implement them. I don't have a direct feature comparison list of what's missing but I'm sure there is one somewhere online

Though not motion, I put a post on the first page of two frame grabs from footage recorded with Cinelike D on both the GX80 and the G7. To my eye they show identical handling of the same scene. Only to my eye though so there may be some on much closer inspection but I think for all practical purposes they are the same. I don't know the exact family relationship senso and processor wise between the GX80 and the G7 so any small differences between the performance of Cinelike D on both are likely attributable to that. Its impossible to do a direct comparison between what official Cinelike D would look like on the GX80 of course as there is no official one but just to stress that no other parameters were harmed in the making of the hack. I agree that I would love to hear from people who have implemented it to see what difference if any its made to their output and any difference they've had to make to their workflow either capture or post to accommodate it. I'd be particularly interested if anyone has a Cinelike D based LUT to see that it maps across as expected.

Using the ruse of wanting to "compare its wifi control to my FZ1000" , I spent a few minutes packet capturing an FZ2000 app session in a camera store earlier to get some examples of it sending the 100 and 200mbps 1080p setting to the camera. The commands were formed exactly as I was expecting them to be so confirms my findings that although the camera will accept them it won't properly action them but it will change to 4K24p instead. This is a different behaviour to when you send an outright "illegal" setting (i.e. a PAL rate when its in NTSC region and vice versa) where it returns an error. Whether it simply reverts to its uppermost setting when given a request that it doesn't reject but can't find an actual match for I don't know but the end result is the same in that it doesn't get us anywhere. With regard to the LX100, the Cinelike D and V are acting almost completely the reverse to how you would expect them to in that it massively saturates the colour! However, it also completely and I mean completely canes the black level. I've got a hunch that with the LX100 being such a close relative of the GH4 that there might be something involving an interaction with the master pedestal level and/or the luma level which are changeable on the GH4 but not on the LX100. If someone who has an LX100 could try this and see what you think. It might be correctable with changing a combination of the saturation/contrast/shadow/highlight controls to bring it into line and if it is then it shouldn't be an issue for the Deploy function to combine the string of changes into one click. I stress might though ! And I can't look at anything to do with this for the next four or five days at least now while I'm away doing the day job assignment so don't hold your breath.

Just a heads up about the error logs from the other thread. Manual its from is GX7 but they are all common so should work with your GH5 and might give you some insight into where the error was.

I think I mentioned earlier in the thread but those are messages from the camera to the app to tell it what items to give the user access to. Its one piece of the puzzle in that you can still construct set commands based on them (or estimates of what they will be) but the camera will not necessarily action them and you will generally get an "err_parameter" message in your browser. An example of this would be to send : http://192.168.54.1/cam.cgi?mode=setsetting&type=videoquality&value=mp4ed_c24p_100mbps_c4K Sending this will be actioned by Panasonic cameras that have the functionality enabled but won't be by those that won't. In this respect, it is pure good fortune that although Cinelike D and V are not enabled in the app the camera will actually activate them if we send it the commands. There are other examples such as the ISO50000 mode and 23 point AF mode that aren't listed but I was able to get working. You will also see this selective rejection when you have the camera in PAL mode, you can send it NTSC based formats such as 1080p60 but it will reject them. If you then boot the camera using the multi button diagnostic mode into NTSC region you will be able to send them and it will action them. We can only presume that Panasonic had it in mind to have Cinelike D and V in the GX80 and left it in there. Something unusual happens when you tell it to go into one of the high bitrate 1080p modes in that it switches to 4K24p so its not entirely rejecting it but its also not doing it either. Again, I'll say that the LX100 is doing something odd with the Cinelike commands so there might be something worth tinkering with there. For now, I'm only concentrating on looking at command stuff for my hardware box (which is all I was originally intending to be tinkering with this stuff for anyway before I uncovered the Cinlike thing!) so hopefully now so many of you are using this you might all find some new stuff with your own experiments.

I was going to point you to this thread on BlackMagic forum as there is a discussion relating to what you want to do it. But I notice that someone with a very similar diagram to yourself has already asked this on there... https://forum.blackmagicdesign.com/viewtopic.php?f=4&t=40229

Glad you had the "Appetite" for it and that it worked out "Bonny"

If you got your hands on a v2.2 or v2.3 GH4 and then "rediscovered" where the particular version of the Android app was that did the "free" vlog upgrade before Panasonic closed it down then you'd be able to discover what command it was that was sent using the same process as the packet capture here. Unless the GX80 wanted to play ball though then you could be sending that command all day long and it wouldn't do anything. The GX80 does not throw an error when you send what I suspect is this right command and it does change the picture profile, just not to the one you are seeking. The LX100 changes it's profile to something entirely unusual when you tell it to use Cinelike D. If you've got an LX100, use my html page to make the changes as per the GX80 and you'll see what I mean

You can change those in the camera as per the original profiles Although the name of the profile appears blank if you select it in Menu>Photo Style and then cursor down you can change the contrast, saturation,NR an ld sharpness. Changed parameters persist on reboot and if stored in C1 etc

With the GX85 now having Cinelike D, a used one and a used BM Video Assist from B&H could be your friend if you only want 1080p for <$1000? Better monitoring, edit ready ProRes etc A real pity the smaller VA doesn't have XLR inputs like the bigger one as it would be a great combo. Although if you put up another $200 you could pair it with the G85.....

They were my instructions to be fair but no matter, we got there in the end!

I suspect this list of reasons is going to end up like this in reverse

Yes, its changeable in camera like the other profiles and the changes are persistent on power off and when stored in C1 etc

"Packet Capture" (free from the Play store) doesn't require root access if anyone wants to delve in. Not my experience with this at all. Its made no difference at all to the responsiveness of any of the controls of the camera. Are you referring to when you still have it connected to the wifi or something? This is expected and described earlier in the thread. Its actually the way to confirm its worked As per the recommendation, consider saving the Cinelike profile as C1 and then the Standard profile as C2. This makes it really simple to switch between them in camera if required. Hope that helps.

The LX100 accepts the Cinelike commands and changes it's colour profile to something unusual. I'll look at it again at some point as it would be a very cool thing to have on there I think.

OK, I've got a camera in front of me now, so I'll give you the exact steps 1) Press Menu button on the camera 2) Go to the Setup menu 3) Navigate to WiFi 4) Select WiFi Function 5) Select New Connection -- (This may be where its gone wrong as you may have been using your previous phone connection ) 6) Select Remote Shooting & View 7) Camera screen will now be showing the Wifi glowing beacon thing 8) Choose the SSID ID it is showing on the camera (Should be GX80-blah blah) to connect your phone or laptop to 9) Camera will show message saying 'If you have not launched the smartphone application.....' message 10) Load the html page into the browser of your phone or laptop 11) Select 'Handshake' 12) The browser will now display 'ok,GX80-xxxxx,remote,encrypted' (the xxxxxx will be your specific GX80 ID) 13) Hit 'Back' on your browser 14) Select 'Connect' 15) The browser will now display 'OK' and the camera will display 'Under Remote Control' 16) Wait until you see the live view image on the camera LCD 17) Hit 'Back' on your browser 18) Select 'Deploy Cinelike D' 19) The browser will now display 'OK' 20) On the camera display, the picture style will not be displayed (top left next to the Mode indicator) 21) To restore Standard profiles, hit 'Back' on your browser and select 'Restore' 22) The browser will now display 'OK' and on the camera display, the STD picture style will be displayed (top left next to the Mode indicator) 23) Repeat 17-22 to switch between enabling and disabling Cinelike D If it does NOT connect the first time, then just let it time out and repeat from the top. Once it has successfully connected it will store the connection and from thereon in will connect first time every time. By the way, just to be absolutely clear, the quote of mine that you've used there relates to a different conversation regarding trying to guess at additional commands to get them working. It has nothing to do with what I've shared regarding the Cinelike D stuff as rest assured I would not share something without testing that it didn't break my own camera first. OK, well that sounds like if you got the handshake going then the camera is timing out, dropping its wifi transmission and your phone is falling back to a different wifi network and giving the 404 error because its connected to the internet while the page is referring to the address of the camera. This is a positive sign as it should mean if you start the process again, the connection will have been registered and you'll be able to get through on the next attempt.

The unpredictable aspect is that I don't know if your other attempts when you had the app and the browser open at the same time had been successful. The only commands that get sent to the camera are ones that the app would send to it. The Restore function gets your picture profile back to Standard from which point you can then select your other profiles again. When you have Cinelike D enabled you can't then select these, hence why I put the option in there. As I detailed elsewhere in the thread, you can use the custom C functions to save the camera setting in both states so you only have to do this process once. If you are at all unsure, please do not proceed with it. At the end of the day, I'm just some stranger on the internet so as I said at the very start of this thread its entirely at your own risk. I've got no dog in the fight so to speak as to whether anyone does this or not as I have no financial or any other incentive. But if you brick your camera, I'll give you £20 for it When you go to previous connections on the phone, can you just list for me what they are? The connection is a direct one between the phone and the camera so you shouldn't be trying to connect through a router.

You don't need to use the Panasonic app, its all done through your browser. 1) Turn the wifi function on on the camera 2) In your wifi settings on the phone, connect to the camera. (NB Depending on how easy it is to load html files from a file on your particular phone, it might be easier to use a computer but there's no reason it won't work with a phone browser) 3) Load the html file attached here (the original one has now been updated to have both types of Cinelike) 4) Select Handshake 5) Depending on how successful your previous attempts have been the camera will accept the connection and you hit Connect. 6) If it hasn't connected first time the camera will time out. This is perfectly OK, it is waiting sometimes for a return authorisation which it wont get as we're not using the app. If this happens, just start the process again from step 1 and it will work second time round. 7) Once its connected the camera will say under remote control, then wait for it to show a live view on the LCD screen. 8) Select which version of Cinelike that you want. 9) For all subsequent connections, you won't have to do the two step handshake, it will just be > Turn on wifi on camera, connect wifi on phone, load html page, hit Handshake, hit Connect, wait for live view and then choose which Cinelike you want or select Restore to go back to Standard setting. DEPLOY CINELIKE D AND V.html

The advantage to using the doubler is that you can shoot in 4K and have a bit more reach on top as well. Not that it needs any more reach though !

At this moment in time I wouldn't bank on it. The Image App supports a huge range of Panasonic cameras with varying features, hence why all of their functions are listed there. Here is the list of supported cameras by the way http://av.jpn.support.panasonic.com/support/global/cs/soft/image_app/ The process is basically the camera tells the app "I'm a GH4843985739, populate your menus with the following stuff because I can do that..." so the app will only show you what the camera can do. You can have an educated guess at how the commands would be formed to be sent back to the camera if it did have those features that you can't see in the menu and by logging what it sends when it does have such a camera connected, hence how I could get the Cinelike D and V working and the higher ISO as well as a couple of other bits that I haven't mentioned (Non thrilling so you're not missing much) But if the camera doesn't like or understand the command it will reject it so its not fully predictable or even changeable. I think the bit rate stuff would be worthwhile and there might be something there but my theory about going at it when the camera is booted up in the diagnostic region change mode didn't come to anything but I'll keep trying. My focus is going to move on to using this stuff for a hardware gadget though but everyone else is more than welcome to keep pushing commands at their cameras with the structures I've listed as every bit of info we can all share will be worthwhile. And there is a big clue in that sentence as to what my little gadget will be getting used for......

No, its slightly misleading (see above regarding menus) as that is a request return from the camera rather than a set command. Its buried inside the G7 as vlog_gamma so that is the correct command parameter (which makes you curious about the G7 right?) So sending this will not be rejected : http://192.168.54.1/cam.cgi?mode=setsetting&type=colormode&value=vlog_gamma But it won't be actioned other than changing you to the Standard profile. So the camera understands it but just wont do it (see the making tea analogy earlier) If you use the command as listed in that menu (i.e. vlog_l) you would send it like this http://192.168.54.1/cam.cgi?mode=setsetting&type=colormode&value=vlog_l This returns "err_param" from the camera

Just remember to use the mode as 'setsetting' for the parameter you want to try and change and the value= to whatever you want to set it to if you want to have a poke around. The getinfo is from the camera back to the app to let it set up its menus which makes the Cinelike a bit of a mystery as they definitely don't appear in the app.

In the 70s in the UK the government used to make a series of public information films with varying degrees of sinister or judgemental tone and this one has always stuck with me. The pay off line at the end is exactly right for this situation when someone like me is being wise after the event !

As a by product of my recent research, I've come across something in a service manual that might be useful if you've had something funky happen with your Panasonic cameras. This is from a GX7 manual but - like the region change boot mode - the process is common across their range so should work for all models. Not the most thrilling of discoveries but it might be useful if you have a problem and definitely would have shed some light on the Lexar card failure discussion as it will have been written into the GH5 log It'll probably still be in there actually.... panasonic-gx7-service-manual.pdf

For anyone who wants to try Cinelike V as well, just use this updated html file and you'll now be able to switch between Cinelike D, Cinelike V and back to Standard. Just a heads up to anyone who is about to try this for the first time is that you may have to initiate the handshake procedure twice when you first connect to your camera but every subsequent connection after that will only require it once. The situation with vlog by the way is that the camera is pretty much acting like my missus when I ask her to make a cup of tea. Hears the request, replies 'OK' so appears to understand it and then does absolutely nothing about it There is maybe something there with trying to persuade it to do higher bitrate HD though but don't build your hopes up. DEPLOY CINELIKE D AND V.html