Tagged with sd-card - Personal View Talks http://personal-view.com/talks/discussions/tagged/sd-card/feed.rss Mon, 29 Apr 24 20:45:48 +0000 Tagged with sd-card - Personal View Talks en-CA Card reader. Best reliability/bang for buck? 2016 http://personal-view.com/talks/discussion/15214/card-reader.-best-reliabilitybang-for-buck-2016 Mon, 13 Jun 2016 21:12:13 +0000 gcb 15214@/talks/discussions The last thread i saw about this was from 2012 here. And my lexar 24-in-1 is waaaay overdue for replacement (it manages to read most SDHC but speed tops at 15mbps)

So, what is everyone using these days?

And are the USB3 models backwards compatible to usb2 in case i need to plug them to my phone?

]]>
Hacks and SD cards http://personal-view.com/talks/discussion/7116/hacks-and-sd-cards Fri, 31 May 2013 08:51:28 +0000 oscarsGH2 7116@/talks/discussions Hi, I have been hacking my GH2's for a while now, trying different cards and hacks but it always comes up saying that the camera cannot record due to the limitations of the writing speed of the card!! I am now trying both the vanilla 44 hack and undefined 88 hacks with sandisc extreme cards but this same message always comes up and the camera wont record for more that 30s. Just wondering if anyone has any suggestions.

]]>
Best Sd Card for the latest Apocalypse Patches? GH2 http://personal-view.com/talks/discussion/4665/best-sd-card-for-the-latest-apocalypse-patches-gh2 Fri, 21 Sep 2012 13:11:38 +0000 taipan 4665@/talks/discussions HI, I am asking this because I keep reading mix reviews... I just bought the GH2 and it is on it's way and I will really like to run the hacks without any problem...

thanks for the help

]]>
Importance of Proper Tests for Reliable In-Cam Playback: Lessons from the Field http://personal-view.com/talks/discussion/2017/importance-of-proper-tests-for-reliable-in-cam-playback-lessons-from-the-field Sun, 15 Jan 2012 14:35:26 +0000 qwerty123 2017@/talks/discussions ===NOTE: none of what I say below is meant belittle the fantastic and wonderful low gop patches that driftwood has produced (or any others with "extreme" patch settings). If anything, this is my fault for not testing thoroughly enough. But I think my experience is worth sharing===

==MY TEST==

I went on a shoot this weekend, and was using Sandisk Extreme 16gb 30mb/s cards. I wanted to ensure both spanning and playback in camera for the shoot, so I went with driftwoods "spanmybitchup" patch. I did just a few short preliminary tests: the test I did was to shoot the papasarts star chart (which I've attached--I also attached the more extreme codec test chart v2 2010), and let it run. I waved my hand around in the frame from time to time and also had some talking to get audio. Everything seemed good: I was getting spanning and smooth playback in camera with audio. (EDIT: also attaching Stray's death charts with color information!)

==MY SHOOT==

So during the shoot, after a few shots, I was getting the message "motion image cannot be played" for all my clips (or something like that I don't remember exactly)--my heart sunk! An actor asked me to check to see if we recorded something on a previous take, I had to say that "yes it was" without checking. I was worried about requests for playback--and this was only with one actor: imagine this on shoot with clients! For certain shots, I wanted to be sure that something was recorded since I wasn't at the camera, and I couldn't do this. The scene I was shooting was an actor in a car at night--he was lit and most everything else was dark. That's when I got the messages. I put in a new Sandisk card, and formatted it. Reshot the same scene and I was getting the same error.

==LESSONS==

1) In camera playback is important at least for some of us, and for some, like me, it is even more important than low gop. For me, I am willing to forego a very very high quality low GOP setting (awesome work driftwood!!) that doesn't have playback in camera on good SD cards for an improved long GOP with ultra reliable in camera playback. I'm NOT saying that everyone wants this or should want it (especially if you have the cash for more super high end SD cards or for extra harddrive space). But I'm guessing some people are in my situation as well.

2) It seems there's a relatively standard procedure for patch development (using streamparser, tweaking settings incrementally, etc etc). BUT there seems to be no standard procedure for testing spanning and in-camera playback. You might not think that makes a difference, but it seems that it does: it seems to matter what you shoot when you are testing things like spanning and in-camera playback. Or, at least the number of clips you shoot or the ISO you shoot at makes a difference: otherwise, I don't know how to explain the divergence between my pre-shoot tests and what happened on the shoot. I welcome some constructive thinking about standardizing spanning and camera playback tests.

==DESIRES==

The ideal for me would be to get a hack that improves quality over the stock settings, that has very very reliable spanning and in-camera playback with audio, and works on good quality cards like the Sandisck 30 mb/s (16gb). I know some people are getting the SandDisk extreme pro 64gb cards... but a lot of people (like me) already have a stash of good quality cards and don't want to fork over even more money to get these super high end cards.

I did test w/ @cbrandin 's (Chris's) 66M patch. We know that this doesn't span (but getting around 10 or 11 minutes is okay for me, although I'd love spanning). But what I did notice is that I couldn't get in camera playback with this either. I'm going to try the 44M patch.

Thoughts?

]]>
Card formatting for better reliability http://personal-view.com/talks/discussion/685/card-formatting-for-better-reliability Tue, 16 Aug 2011 15:00:35 +0000 allenswrench 685@/talks/discussions it is my first post so be gentle.
Ever since the hack came out, I have mostly been trying the highest bitrate settings and have spent most of my time with 65000 with no card read/write errors. This was really great since I only have 1 card.
I have used my card for other things too (watch movies reformatting to NTFS etc) and have noticed the performance going down....
To cut the long story short, if you need (and I know you do) your card to be as good as new or better, you need to do a THOROUGH format every now and then. Use the CCleaner's Drive Wiper option (takes about 25 minutes on my one and only great 16GB card) and it really will wipe the s**t out of it. Then you just pop it into your GH2 and format to it's heart's desires and it is fast as hell.
CCleaner is free, you just need to go to the "drive wiper" section and format your card.
Hope this helps, as many people have been complaining about the write/read errors and I have never had them. My card is the el cheapo Transcend 16GB 10 class BTW.
QUESTION: Anyone has this card in the 32GB version? Please advise if the performance is the same.
Thanks all and all the best!]]>
GH2 max speed write http://personal-view.com/talks/discussion/1107/gh2-max-speed-write Wed, 05 Oct 2011 14:12:13 +0000 humpman 1107@/talks/discussions I suggest you to test max bitrate what gh2 can handle, with this way.

1. Get the fastest sd-card wich present at this moment.

2. Make firmware.
In ptool enter this settigs
E1 Quality=200
E1 Table=4
E2 Quality=200
E2 Table=4
E3 Quality=200
E3 Table=4
E4 Quality=200
E4 Table=4

3. Shoot
Of course choose on your camera 720p MJPEG mode.
Then try to shoot, if record time is > 15 sec, that mean it's ok (this is my guess), note what bitrate you have got
Shoot every time same scene!

After, enter this settings (Every Quality setting is higher by 100)
E1 Quality=300
E1 Table=4
E2 Quality=300
E2 Table=4
E3 Quality=300
E3 Table=4
E4 Quality=300
E4 Table=4
Try to shoot, if record time is > 15 sec, it's ok, note what bitrate you have got

Repeat this until the errors start to happen, after you should take last successful settings, and start new tests, but now you should test with litle steps, let plus every Quality settings in every step by 10, for exemple:
You have got successful settings
E1 Quality=600
E1 Table=4
E2 Quality=600
E2 Table=4
E3 Quality=600
E3 Table=4
E4 Quality=600
E4 Table=4
And you further actions:
E1 Quality=610
E1 Table=4
E2 Quality=610
E2 Table=4
E3 Quality=610
E3 Table=4
E4 Quality=610
E4 Table=4
Do it untill the errors start to happen

Shoot every time same scene!]]>