Messages

[ATM]

Not yet. Now that MLV is working and I have a reliable post workflow to recommend I'll get it finished but time is always against me ATM. At last count it was 50+ pages without any images yet... still got to do all those bits.

I'd hate for time to be against me ass-to-mouth.

I'm going to be on vacation for a week, I might be able to make some images for you.

I meant it as when I read his posts I'm not sure if he's really serious or flippant.  These are what Yogi Berra said as a manager

'90% of the game is half mental"

About a restaurant: "Nobody goes there anymore. It's too crowded"

"It ain't over 'til it's over"

You're the one that the fat general called a, "cheeky fellow." 

1%, you are the Yogi Berra of Magic Lantern

Nobody likes a butt kisser.

Because there is no 720p mode on the 50D.

Not even a video mode (hinting aside)! It's nice to have accomplished SOMETHING, and 1080p is pretty impressive, all things considered. 

Ok, But when I change the resolution on my 50d in raw_rec module (for example to 1440x890) the shooting frame becomes smaller and don't cover the whole screen. And records only the image that stays within the frame. And it always been this way in every build I tried. Your experience is different?

Probably the same and different, at the same time.

You should spend more time reading in the forums, rather than posting. Everything you need to know is here, you just have to digest it.

The point is that it's capturing raw live feed as sequential images. If you capture smaller than the whole frame, where would you take it from? It's not resizing it, it's just capturing as many pixels as you tell it to.

[you get there by allowing frame skipping. What happens if you disallow frame skipping?]

Okay.  But you get there by allowing frame skipping.  What happens if you disallow frame skipping?  I can't make it when I disallow frame skipping.  20 second clips are fine for most of what I do.  Just trying to get a realistic sense of what the equipment and code can do.

FYI frame skipping has been off since you questioned this, and has made no difference. Buffer does its job until the card catches up.

Really? This was told to me by a ML developer. So what are you saying is that is possible to shoot RAW video with the RAW picture mode ON? Everyone told me that for the RAW video to work continually, it would be necessary to turn the "RAW" mode OFF in CANON menu and get "JPEG" ON.

So, Im not getting the best quallity? Is that it?

My guess is that it won't affect the image's quality, but it may affect the memory usage, limiting resources.

As for the statement, I tend to agree. I've been leaving the camera in RAW shooting mode, and I have yet to have a magenta frame on my 50D, whereas slow cards caused me plenty of bad frames on my 550D.

I would like to note that I leave GD and h.264 video mode off, which may relieve some resource strain.

Was discussed earlier in this thread somewhere.  Quite a few looked into it, but the 50D is missing the hardware on board to produce a similar beep that newer cameras give off.

any beep would be better than no beep, though, I'd say.

Is there any way to get the 50D to sync beep?   

Received a new Komputerbay 128 GB 1000X today and I can't get the card to do a firmware update on my 50D. Wondering if anyone has found a way to make the card work...

Long story short... I had bought a 128 GB 1000X back in July and it work with my camera. However, the write speeds were about 2 - 5 mb/s too slow. Started thinking that with the latest builds that that same card might be applicable...

Any help would be greatly appreciated.

Best I can recall, you have to use a card smaller than 64GB to do firmware updates and install ML. The firmware makes it possible to use the 64GB and larger cards.

In addition, you have to prepare 64GB cards a slightly different way, I believe. I suggest starting with step 1 on the ML Install Wiki, so you can see what it suggests, and why. 

Just traded in a 550D for a 50D.

Great! Many thanks again! I reached your same results, with max around 5500 frames = 3.5 minutes ! Many thanks to Andy600 !
Big achievement! We are so close to continuous! ml say "continuous ok" but it maxes to 5500 frames... so close !!!! 

EDIT: I tried to slow down to 23.7 fps, and it's really continuous: only 2 bars (one green and one blu) are displayed for some time, then something breaks and 5 green bars and 5 blue bars are constantly displayed for some time, then something breaks again... and so on, to the point where all the memory buffer is filled up. If we manage to understand what is "breaking" the writing process at constant intervals, we perhaps can try to solve it ! 

Seems like it's just slight inconsistencies in write speed due to the manufacturing process. I would expect even the tightest quality control to yield slight inconsistencies. Fortunately the buffer handles it very well.

As @Walter mentioned before, your USB2 will simply not allow you USB3 speeds. But that alone is not a huge issue, you'll simply wait more when you dump stuff off your CF card.
Now, regarding which CF card to buy, it's easy... If you have the money, go for a Lexar/SanDisk (assuming you're chasing ML RAW). If you feel that's too much, you can play with KomputerBay/Transcend. There's a new Toshiba Exceria in the mix, but it's expensive...
Hope that was some help...

Valid in every sense. It's a solid suggestion. There are failures in every brand, we just tend to see more complaints with KBs--doesn't mean they all fail. At least you got suggestions on ML of what to avoid, if you have a little time to research.

The writing speed in order to achieve success is important. While that does not mean you must have the newest 100000x card, it does mean that the controller must be able to sustain a high write speed. If that didn't quite make sense, then this might clarify: the reason CF Cards have been around so long is because they have built in memory controllers. When CF reached speed limitations, they upgraded to faster controllers. You get some super fast cards, but those bleeding edge controllers are EXPENSIVE.

I spent some time searching for card benchmarks and learning about the capabilities of cameras before I settled on the 50D and a Lexar 1000x 32GB. I had to know if the 2008 50D could really keep up with the Lexar 1000x speeds. I ended up taking an educated gamble and being successful. I still knew, coming in to the fray, that the 50D supported UDMA7, and that it was initially reporting 60/s on the ML RAW chart. I knew that it did not support ExFat. I learned all this here. The gamble was that I guessed it was the same as the 5D mkII CF Card interface, and my gamble paid off, as I get 82.9/s continuous with the right ML release. I owe that to patience and research, and not frustrated whining in forums because nobody had all the answers. Forums are about sharing information, not just pleading for it.

If you have more money than sense, don't settle for less than the Lexar 1000x 32GB. Expect to pay $120 for it. Maybe more. That being said, there are plenty of KomputerBay success stories, even if some come with a little effort. It seems vintage has been a concern. If that's something you don't have the wisdom to deal with, nor the patience to learn, Lexar, Hoodman, and SanDisk need to be names you spend a lot more money on in order to gain a bit more peace of mind.

[you get there by allowing frame skipping. What happens if you disallow frame skipping?]

Okay.  But you get there by allowing frame skipping.  What happens if you disallow frame skipping?  I can't make it when I disallow frame skipping.  20 second clips are fine for most of what I do.  Just trying to get a realistic sense of what the equipment and code can do.

In my case, nothing. I set frame skipping in case the card never caught up, and I ran out of buffer. It was a personal preference.

I never ran out of buffer. There was a little wavering at the beginning of each file, then the card eventually caught up, which cleared or stabilized the buffer. No frames were skipped.

I turned on frame skipping back when I was using my T2i, because it let me continue recording, rather than just killing a shot and making me start over. Chances are, you'll actually gain a little memory back by turning it off. Maybe it'll switch to continuous faster on the 50D with all other settings the same. I'm going to try it, since I've found the rest to be consistent.

Good suggestion, even if it's really not.

Thanks .. It was really helped me.

Mac and Linux users who aren't sure how to tackle this, you can patch the files back together by doing this in Terminal.

Code Select Expand

cat file.raw file.r00 file.r01 > file.raw

It's pretty handy, because you can combine the files directly to another drive without having to move the files over first.

Code Select Expand

cat /location/flash/file.raw /location/flash/file.r00 /location/flash/file.r01 > /location/hdd/file.raw

Of course the actual location is a real path, not the made up path.

Okay thanks. What about how many frames I would get before it stops recording? Or is the 16GB version capable of continuous, I think not?

With the Go Faster Tragic Lantern build, I've been recording continuously, using the Lexar 1000x 32GB.

If you want to find that, search the thread.

I'm new to raw video and trying to decide on a memory card. If I bought the Lexar 16GB 1000x, how long would I be able to record 1920x1080? I've got a 50D.

1920x1080 at 23.976 is 82.9mb/s. Looks to be about 3 minutes and 20 seconds.

Yes, it's a variant of JEPG2000.
It has wavelet compression, which leads to virtually zero artifacts and no blocking.
And stores info at 16 bit, allowing for RAW-like grading.

Compression ranges from 3:1 to 15:1 or 18:1, I don't remember, But usually it's used around best quality settings.

Even the long-time hoped 10bit RAW conversion while writing data would be a huge benfit on file size without affecting quality in a visible way, but all efforts went wrong..

As far as I'm concerned, being able to convert RAW to R3D RAW would be a wonderful thing. From the card, to a console based binary or GUI, to the drive in R3D would be pretty neat, I'd say. Premiere works well enough with R3D files, as do other NLEs.

Even if it means I just have to delete the files on the cards more frequently, preventing unnecessary disk usage could surely be a help to many.

I don't mind creating a more film-like workflow, resulting in tight slating--editing would be a breeze, and it breathes new life into creative storyboarding.

Just to clarify for everybody, because there's a general misunderstanding here:

File size comparison between CinemaDNG and REDCINE at 1920x1080 24P

CinemaDNG: 4GB / minute for 14bit RAW
REDCINE: from 0.4 to 1.5 GB / minute (depending on compression option) for 16bit RAW

So a compression factor would really really be helpful, now we have a "mini"RED that records 4x heavier files (at less quality).

Isn't RAW R3D a series lossless jpeg2000 frames?

Having a bootable card with no firmware or ML files will simply run stock. It'll be fine.

As far as the process, real camera firmware first, then format card, put ML files on and "update" again to enable ML and set it bootable. Spend some time getting used to the interface, and you may prefer it. It's generally stable until you start messing with nightly builds for special modules and such.

Great! Many thanks for this info! Can you give me the link? I cannot find this build. Many thanks again!!!!

https://bitbucket.org/andy600/tl50d/downloads/Tragic_Lantern_50D109-Andy600.2013Sep28.go_faster.zip

I'm using the "2mb more" build on page 144(?) of the official 40D/50D thread. GD is off, small hacks is on. Crop mode at 1920x1080. The camera actually runs with the expectation that it is going to get 1200 frames, but then pushes it back and back to around 5500, eventually saying continuous OK at 82.9 MB/s, so I apologize for that

Movie tab, movie record off, raw video on.

FPS override set to 24000/1001.

GlobalDraw off, 1920x1080. 82.9 MB/s continuous on bottom.

With 50d? With same camera and card, ml says 81mb/s is not enough for fullhd continuous, and infact i am able to record only 1900 frames. I disabled gd and all other ml and canon stuff and jpeg low resolution mode on canon setting and all ml hackering on, "small hacks" OFF, otherwise only few frames are recorded. I can reach 82 Mb/s with 2500 frames, and special CF preparation, but not at all CONTINUOUS. What are your magic settings? And what build you use? (I'm using the last nightly build at time of this writing). Many thanks!

Yeah they work great. I have the 32 gb.

Agreed, 81 MB/s out of the box. Consistently.

Currently running 82.9MB/s continuous crop mode in [email protected], and it brings a tear to my eye.

http://www.ebay.com/itm/64GB-Compact-Flash-Memory-Card-1000X-Professional-UDMA-7-/181174615381?pt=LH_DefaultDomain_123&hash=item2a2ed93d55&_uhb=1

I just found this brand on ebay. No mention on the internet. It is cheaper for me than ordering KomputerBay from the USA, but is it worth the risk?

i wouldn't say that the KomputerBay is worth the risk. Considering this is riskier, it's just asking for trouble.

I just got Komputerbay 32GB 1000x from ebay. It goes up to 79MB/s, giving me continuous full frame 16:9, crop 2:35 1920/2000. Perfect for the price. 

I got the Lexar 1000x 32gb for $114 on eBay.

While I wouldn't bother justifying the extra cost in order to get another ~2MB/s over the KomputerBay, I would like to say it CONSISTENTLY runs 81MB/s, which is definitely worth the difference. The extra speed is gravy to me.

With the GlobalDraw off, I'll run crop 1920x1080 until the card runs out. No drops or pink frames.