Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Rush

#1
Raw Video / Re: Any way to fix MLV header?
January 15, 2015, 03:47:48 PM
Quotewhich version did you use?
It is MLV_rec with build date about middle of August 2014
#2
Raw Video / Re: Any way to fix MLV header?
January 13, 2015, 09:37:06 PM
Thank you very much, g33g0!!!
I see, I need to point to the beginning of next frame...
Did that and fixed, but only one frame (right after half-corrupted frame from the screenshot posted earlier, sadly it remained corrupted) - after it there is again half-corrupted frame and black frames after...
Will try to fix it too, now I know what to do... But it will be hell lot of work if there is corrupted every other frame  :(

Here is uploaded 100mb fragment:
http://dropmefiles.com/Q6AuK

Do you know is it possible to recover half-corrupted frames? Which looks like I posted earlier

---
Yeee! Fixed MLV, it now plays till the end, just some random black frames in the end, but that 8GB footage is rescued. Thank you, g33g0!
#3
Raw Video / Re: Any way to fix MLV header?
January 13, 2015, 02:18:30 PM
Here is previous and next VIDF


#4
Raw Video / Re: Any way to fix MLV header?
January 12, 2015, 11:42:49 PM
g3gg0, thank you for your reply!!

Here is HEX content at 0x75ce0160


And here is the last visible frame, how it looks:

All frames after can't be viewed or exported.

Hope you can give me advice of what should I try to fix it...
#5
Raw Video / Re: Any way to fix MLV header?
January 12, 2015, 04:01:31 AM
Please, help, I am in a trouble...

Unknown Block: ┤С, skipping
BUG_ID_BLOCKSIZE_WRONG: Invalid block at 0x75ce0160, trying to fix it
[ERROR] BUG_ID_BLOCKSIZE_WRONG: Failed to fix
Processed 544 video frames


Full video is 95 seconds, but I can extract only 20 secs...
Is there a way to fix it? I can change MLV with WinHEX but I don't know what should I change. I see that MLV is full of data.
#6
Quote from: gary2013 on February 27, 2014, 06:18:05 PM
I drag n drop ML RAW files straight into PPro CC ver 7.0...
Yes, it is because Ginger HDR plugin... Very nice, thank you!
#7
Proxies are veru useful.
It's impossible to work with DNG in real-time.
So I edit ProRes and replace it with DNGs (making color correction) before final render.
Don't see any other way to work with RAW faster
#8
Bug report:

- on some MLVs - raw2dng error (don't processes those MLVs)
- sometimes ufraw error
- .tiff files don't get removed after converting
(end message is "convertion completed". I think that "conversion" is correct)
#9
Quote from: gary2013 on February 13, 2014, 07:34:16 AM
Thanx Rush. I am on windows 7 and that apps looks like Mac only.
There are legacy versions for Win too ;)
#11
Quote from: tonybeccar on February 11, 2014, 05:52:44 PM
Hey Rush, which OS do you have? Did you record the MLV with sound? If not, can you try with? It seems there are still a few bugs with it :S, hope they'll be fixed by sunday, but you gotta help me narrow them down!
Thanks!
Win 8.1, MLV with sound. It seems, like ffmpeg don't do it's work (can't say anything without log file. is there any option for ffmpeg to create debug-log?)
Can it be because it is 50 fps MLV? In queue window it shows like -15.5 fps. May be you pass fps value to ffmpeg and that's why it crashes? (because -15.5 fps is invalid)
Or may be there is restrictions in resolition? Source MLV have 672px height (1920x672)

UPD: yes, fps value or resolution is the reason of proxy creation problem. 25 fps MLV (w/o sound) 1920x1080 converted succesfully

Interesting, but prores 4444 is just 130 mbit, and 422 is 280mbit
#12
Thank you very much for your work, Tony!
I still don't get proxies and now I have .tif files (previously proxies didn't work but .tif's were deleted after conversion).

Feature that will be good for sure - drag-n-drop support + don't require to set output folder - by default use .mlv's path for DNGs and Proxies.
#13
Oh.. okay:)

What about simple DNG-extraction? mlv2dng is blazingly fast, but your tool looks like it processess every DNG (and it is up to 30x slower in fastest uncompress mode)...

(btw, I can't get prores proxies, but I see tiffs creating and removing)
#14
Thank you very much! It's a great tool!

Hope that it will became multithreaded some day  :)
#15
Tragic Lantern / Re: Tragic Lantern for EOS M
August 22, 2013, 11:24:22 AM
Quote from: cameron12x on August 22, 2013, 12:38:37 AM
Where is the "focus" tab?  I don't see it with my version of ML.  Thanks!
OH, It is not available for EOS M yet...
#16
Tragic Lantern / Re: Tragic Lantern for EOS M
August 21, 2013, 11:50:28 PM
Quote from: cameron12x on August 21, 2013, 08:57:36 PM
Does ML have a "hyperfocal" focus mode
check Focus tab. with most electronic lenses - it automatically calculates DOF and Hyperfocal distance, based on current lens settings and will report if you are in hyperfocal distance
#17
Tragic Lantern / Re: Tragic Lantern for EOS M
August 14, 2013, 12:15:18 PM
Quote from: mixer2 on August 14, 2013, 10:45:58 AM
of course line skipping makes it even worse, because it heavily reduces the sampling frequency.
the only reason why you don't see much aliasing at 100% is that the lenses aren't that sharp and act like a low-pass filter.
=> sharper lense = more aliasing
yes, I agree. But for me - without lineskipping aliasing is acceptable and hardly noticable (even with the sharpest lens I have), comparing to lineskipped image where aliasing become obvious.
#18
Tragic Lantern / Re: Tragic Lantern for EOS M
August 14, 2013, 09:28:33 AM
Quote from: feureau on August 13, 2013, 05:11:09 PM
Is this the same movie crop mode in ML? I still get moire with this on. Have you tried shooting a test chart?
I can get it, but it is very very little, comparing to non-crop mode.

Quotetechnically 100% crop doesn't mean no aliasing. i read that multiple times, but it's still a digital measurement, which means, if you're signal (the light that comes from the lense) has more detail than your sensor resolution you'll get aliasing effects.
technically 100% crop don't use lineskipping. aliasing and moire comes from the gaps of lineskipped pixels, and gaps becomes minimal in 100% crop mode.
#19
Tragic Lantern / Re: Tragic Lantern for EOS M
August 13, 2013, 05:00:00 PM
Quote from: JohnBarlow on August 13, 2013, 03:35:26 PM
Impressive!, what card did you use?
SanDisk 95 mb/s

QuoteCan you record avchd in 3x crop mode or is is just for RAW record?
Yes, moire/aliasing-free 3x H.264.
#20
Tragic Lantern / Re: Tragic Lantern for EOS M
August 13, 2013, 03:32:56 PM
Quote from: JohnBarlow on August 13, 2013, 02:58:37 PM
I dont have EOSM, so can someone say what is max number of frames @24p 1280x720 in crop mode?
unlimited
#21
SUGGESTION FOR COMPARISON CHART:
It is not correct to put EOS M to "bad", and 650D/700D/100D to "not bad" - they are equal in terms of RAW video capabilities.
Difference is only in VAF availability.
#22
Quote from: daSilva on July 19, 2013, 07:35:56 PM
And what Settings do you suggest in the "Slice CBR" Menu?
I had provided settings for CBR mode. I don't use Slice mode, so there is no any changes (slice control should be turned off. set slice to 0)
#23
Tragic Lantern / Re: Tragic Lantern for EOS M
July 19, 2013, 04:35:22 PM
Quote from: 1% on July 19, 2013, 03:38:45 PM
Maybe the image shifts? I saw this on 6D early on. Skips would change with fps override. No point in messing with it too much as it might behave differently depending on what the new fw changed.
Just checked - no, it looks like overlay border (which is recorded too).
If I turn off to mode without border - border place become like pink "lightup/add/screen/you name it" semi-transparent overlay for a few seconds, slowly disappearing...

(sorry again if it is known but:)
little bug in latest experimental 3x crop-mode raw recording - in 3x crop mode it thinks that it need to be unsqueezed and sets wrong resolution (it don't need unsqueezing for real).
#24
Tragic Lantern / Re: Tragic Lantern for EOS M
July 19, 2013, 10:11:46 AM
Sorry if I'm stating bug that is known:
Jun27 build, if I use fps override and it is not = 23.976 fps - it will produce black border from right side.
#25
QuoteWhat Version do you use? TragicLantern1  or  Nightly?
It is TL v1. It is sad, but TL v2 disables sound recording automatically, if GOP or flush rate is changed.

Quote from: jgharding on July 19, 2013, 09:17:53 AM
Cool! If I can repeat that ill change the post, is there a full settings list for up to 160 with audio?
TL v1, CBR 3.0x, 25p PAL mode (strange, but 24p and 30p don't work with audio), GOP not higher than 4 (i prefer GOP4), fast card like SanDisk 95mb/s.
There is no flush rate hacks in TL v1, but flush rate can be very useful - it will make possible to use GOP higher than 4 (default GOP12 for example, that is more effective than low GOP).

QuoteActually it's 21.875 (175Mbps)  :)
May be... but I see that my buffer start to filling up if bitrate reaches 170 mbps. It can peak at 170-180 mbps, but if it will be sustained for some seconds - it will overflow buffer (Card R/W tests don't go higher than 21.5 mbps for me with SanDisk 95 mb/s)