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 - ariaelf

#1
Broken features have nothing to do with "my work", or it's relative "greatness" either way. And unlike straight answers to users questions about the remaining time and elapsed time functions, my work is easy enough to find online with a simple search.

Fact are facts. If you can't bear to hear rational feedback, without ranting and raving about supposed lack of "appreciation," and trying desperately to bully the messenger, that's your problem.

No one is getting ML to record in H.264. The "elapsed time" and "remaining time" recording indicator feature is broken for RAW video recording and should be clearly listed as such in the help files, and removed from the menu when RAW video is "ON".

Those who ask questions on the forums about why these features aren't working in RAW mode should be given a straight answer, instead of being dismissed or ignored. At least now they can find my comments on the matter, and not waste as many hours as I did wondering why selecting "elapsed time" or "remaining time" did absolutely nothing, searching through these forms for non-existent answers, reading help documents, trying different builds, etc.

And I think you've made it very clear to everyone how end users are treated here.
#2
Quote from: Danne on January 08, 2021, 11:24:52 PM
Where´s your portfolio? Please share all your work for us to see.

Rest assure that if something was easy work it would have been in the ml builds already. Even if it´s hard work it would be.

Also:
http://www.catb.org/~esr/faqs/smart-questions.html

I'm perfectly happy to share my work, but it would be off topic in this thread.

We've done incredible things in spite of the limitations of hacked ML cameras, learned lots along the way, and no doubt captured an image quality that would have been impossible without it. Do I need to restate this every time for the delicate egos? I had no idea that respectfully pointing out a critical flaw would cause such a defensive, emotional backlash from the team. This isn't personal. It's rational feedback from a film maker. Chill.

Yes, I understand it "isn't easy". So then remove the fake feature from the menu and stop pretending it exists when it never has. Or is that also impossible to implement??

#3
Quote from: wib on January 08, 2021, 11:56:57 AM
It's more complicated than that. It all depends on what resolution, what bit, if raw or h264... with or without sound... all of that use different amount of space. It's not possible to quantify it as in "time".

Yes, I understand that it would be very difficult to make it exact, but users have been asking for even a rough ballpark (plus or minus a minute would be totally fine for my workflow) since 2014.

I know that a 64G card will hold roughly 12 minutes of footage for me. Just having a simple time counter on the display keep track of how many minutes/seconds of actual recorded takes on the camera so far would be a game-changer. Instead I see how many seconds long each individual take is while it's recording, but then the information disappears. I'm asking for those numbers to be added together and a running total be visible for the user.

There is a lot that happens between takes and it's impossible for me to try to keep track in my head whether 30 short takes in we're close to the limit of the card or not, whether the recording was accidentally left to run after saying "cut" or whatever. No one is going to stand there with a stopwatch to keep track of how many minutes and seconds have added up between each "action" and "cut" so that we don't screw up a sequence when the card finally runs out.

Therefore a ballpark timer of live recording time elapsed on the ML menu would be extremely helpful, so that takes aren't potentially ruined when the card is near capacity.


If no one wants to work on this, or it's for some reason impossibly difficult, at the very least, remove everything in the recording indicator menu and the help documents that doesn't actually exist as a real feature, so creators are not mislead about what ML can actually do. "Elapsed time" "Remaining Time" flat out don't work, but instead of admitting that fact, I'm being called "a troll" by devs.

There's no excuse for this. Grow up. Be honest. Fix mistakes. Listen to users. Move forward. ML was an amazing community when I first started using it, it's sad to see this is the current state of affairs.

#4
Quote from: Walter Schulz on January 08, 2021, 11:49:55 AM
That's the kind of post making devs think about dropping out from the project

If my respectful, honest feedback about a broken, miss-advertised feature which included heaps of praise and appreciation makes devs want to quit, then they probably should find something else to do.

Why list something as a feature if it doesn't work? I spent countless hours looking for information and answers on these forums, wondering if I somehow had the wrong settings or a bad build... Everytime the exact same question came up by a user on these forums, it was ignored and skipped over. Shame on you guys... just remove the non-existent feature from the menu, and be honest that it doesn't exist instead of explaining how something works in the help documents which in actual fact does NOT work for anyone! What is the point of pretending it's "a thing" if it isn't??
#5
I am surprised at the extremely cranky replies given that my last paragraph was nothing but praise for ML and the hard work of the development team.

@masc I am offering feedback from the front lines - this is essential to creating anything great. If you can't handle honest feedback from actual users, then don't make anything.

Telling me to do it myself is childish. I am an indie artist, not a programmer.

ML was designed to empower "no-budget" artists and creators just like myself who are getting started, and don't have the $$$ for high end professional film cameras. The beauty of ML was that it can do so much of what far more expensive cameras can do, while costing nothing. But this is one of those critical features that makes it highly impractical for production work.

Wouldn't it be better to fix it, so that creators COULD use it on their productions without driving everyone crazy?

If I had to do it over again, maybe I would have gone a different route, but switching cameras and workflows mid-production isn't really an option either. When I started, I had no idea the features which were LISTED IN THE MENU simply didn't work!

Why list them as features in the recording indicator menu if they don't exist or are impossible to implement? ML should be transparent about what it can and can not do. You have no idea how many hours of my life I have wasted searching these forums for an answer as to why the listed features didn't work, and wondering if I was the only one with this problem.



#6
Quote from: tuckertota on November 23, 2015, 11:51:55 PM
Would be great if this could be implemented in some way. Even a ballpark figure would be helpful. I use the Canon format menu to check space and that's a little dangerous, one small click from accidentally formatting my card.

I second this motion.

I'm surprised there's been no solution since it was first brought up years ago, but to reboot your camera constantly to know how much space is left on the card. That's bananas!  :o

"Time remaining" indicator is critical for film work. Trust me, there's nothing worse then telling your actors "....OOOPS.... CARD RAN OUT..." in the middle of a brilliant, emotional take.
#7
Quote from: hungrygeneraiton on September 06, 2020, 06:45:33 PM
I am using the latest 1.2.3 experimental build for 3.5k / compression. When I select record indicator (REC Indicator) and select "remaining time" it is still showing elapsed time I believe. Is there a way to get an estimate on remaining  card?

I haven't been able to find any way to show "remaining time" on the 5Dmk3 with the latest 1.2.3 build. Nor "elapsed time".

Back when I was using ML on the 7D it didn't work then either. I thought a few years after others have requested this simple feature multiple times surely it would be implemented, but no such luck?

No matter which setting is selected under the "REC indicator" in the Movie menu, it doesn't work.

"Elapsed time" and "Remaining time" don't show either of those things.

"Avg Bitrate" and "Instant Bitrate" also don't seem to have any effect.

The bitrate (which is far less practically useful to creators) appears to be the only possible default option with the recording indicator. Whether it's "instant" or "average" I can not say. Maybe someone would like to see this in a debug mode for troubleshooting, but as long as the card status is "green" while recording, as a film maker I don't need the bitrate taking up my screen real estate. But I definitely need to know how much (approximately) recording time is left on the card, before messing up a critical long take because the card ran out of room.

The only indicator available is total GB used on the card, in the upper righthand corner BUT it DOES NOT UPDATE unless the whole camera is rebooted. This is very problematic for film work.

"Time Remaining on Card" feature has been requested multiple times, going back to 2013. Is there some reason why "time remaining" presents a particular challenge for the ML team, or do the developers just not realize how important this is for indie film makers, and therefore it hasn't been a priority?

My cast is ready to strangle me with how many times I've had to say "....OOPS, CARD RAN OUT..."  in the middle of a great take. It's very demoralizing to performers to have equipment failures get in the way of performances.

That said, I don't want to sound like I'm complaining. As a tiny no-budget indie film producer, I don't take what you've done for us lightly. We are beyond grateful for all the work you've put into ML - and I hope this feedback is helpful in making ML even more amazing for the creators it was designed to empower.

Cheers to you all,

~Aria
#8


I am getting non-stop crashes from raw2cdng, which was working fine before...  here is a screenshot and cut & page of the problem signature. Ideas? Suggestions? Alternatives?

In full production mode and pulling my hair out...  :-[

https://ibb.co/iKpOfv

Problem signature:
  Problem Event Name:   CLR20r3
  Problem Signature 01:   raw2cdng.exe
  Problem Signature 02:   1.7.9.0
  Problem Signature 03:   585a6be9
  Problem Signature 04:   mscorlib
  Problem Signature 05:   4.0.30319.34209
  Problem Signature 06:   534894cc
  Problem Signature 07:   4527
  Problem Signature 08:   23b
  Problem Signature 09:   System.IO.IOException
  OS Version:   6.1.7601.2.1.0.256.48
  Locale ID:   1033
  Additional Information 1:   0a9e
  Additional Information 2:   0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:   0a9e
  Additional Information 4:   0a9e372d3b4ad19135b953a78882e789
#9
I'm happy to report that using a lower resolution for the HDMI output (force HDMI-VGA) completely solved the problem.  :D After a brief home test with the new lower resolution output settings, ML was battle tested last night filming three more scenes for our indie feature. Everything looks great - no other changes were made.

Now we have the benefit of raw footage from the camera AND a working 7" monitor while shooting. Couldn't be happier  :)
#10
Thanks I'll give that a try and report back! :)
#11
That's a good idea - not sure where to find that setting. Would it be in the Canon menu, the Magic Lantern Menu, or in the monitor menu?

#12
I wanted to update this thread, as I've been dealing with the "shearing" issue for a long time and I'm sure others might run into the same problem, and search the forums for answers.

It seems that the sheared frames ONLY happen when using HDMI out from the camera for monitor viewing.

I don't have a great solution for this, as any professional behind a camera would want to use a monitor for accurate framing, focus-pulling, etc - but at least I've identified the cause after trying and tweaking a million different settings! (The big clue was that it would only happen on location, and never at home when I attempted to troubleshoot this... sans camera rig.)

For now the only thing I can think of is setting up the shot with the monitor, then unplugging it before hitting the record button, then plugging back in for the next take, etc. It's a bit maddening, but better than going through it frame by frame in post to fix jacked up image capture...

Does anyone have any other ideas???
#13
After hunting for a solution for two days to the round-trip Resolve 11/Premiere CC issues I was having, I just wanted to share the first thing I found that actually worked. It seems that Premiere CC no longer exports reel/tape names in it's XML files, and this is a known bug that still hasn't been fixed... or so I heard on the Adobe forums.

I went through a lot of different websites, blogs and youtube tutorials to figure out how it could be done without reverting back to Premiere CS6.5 (which worked as it should with the XMLs). Finally I found this...

http://dcinema.me/2015/01/cinemadng-premiere-offline-davinci-resolve-round-trip-workflow-mac/

Even though I am using a PC it worked perfectly. Now my workflow is RAW MLV files from a 7D, convert to DNGs with MLVMystic, import DNGs into Resolve and make smaller sized proxies for editing in Premiere CC, then follow the rest of the tutorial in the link above to relink to the RAW DNGs for color grading, even with the reel names missing in Premiere's XML file.

Hope this helps someone else!
#14
beauchampy, I've tried following your workflow and the hangup is in exporting the XML from Premiere CC.... Premiere CC fails to include reel/tape names in the XML file so no relinking happens when back in Resolve.

Are you sure you're using Premiere CC and not Premiere CS6.5?? This bug has been confirmed with Adobe and it's been driving me up the wall.... trying to figure out a workaround - forcing individual clips to conform is not efficient with a feature film :/
#15
Anyone find a solution?

I can't imagine hacking the XML file manually just to force Premiere CC to do what it should be doing already... unbelievable.

May have to revert back to Premiere CS 6.5 just to be able to link up to DNGs in Resolve. I hate to let go of the new editing improvements and features in CC, but this is fundamental... 
#16
Raw Video / Re: ML RAW Colorspace?
February 15, 2015, 03:15:55 AM
Thanks for the reply reddeercity, I am on a PC so I guess I will have to find other methods ;)
#17
Raw Video / Re: ML RAW Colorspace?
February 15, 2015, 02:04:44 AM
Thanks for all the replies... though I still don't understand the details, it sounds like doing green screen work with ML RAW on a 7D won't be a problem?

reddeercity, that's awesome :) Using AE for your keying/FX work presumably? I'd love to know the details of your process!
#18
Raw Video / ML RAW Colorspace?
February 14, 2015, 10:16:15 PM
Some of my indie film friends are debating about this - so I thought I'd ask. What is the colorspace of ML RAW on a DLSR camera like the 7D? Is it still the original 4:2:0 that you get with H.264 compression, or does it improve?

I have tried searching the forums with keywords and couldn't find an answer. Would a 7D with ML RAW be suitable for green screen work?
#19
Will do, it's too bad because I <3 the ML histogram for setting up proper exposure. To turn it on and off before every single take, especially when I'd prefer to see those levels while recording, is a bummer to say the least. Kind of like being the sound recorder on set, and having to be blind to your meters throughout the take... so you have no idea if you've clipped and ruined your audio or not.

Is this issue corrected in newer builds, or is it just impossible to have a working histogram and raw video at the same time from the 7D processor?
#20
Gotcha, let me try that with a test and see if that fixes the problem. (as tedious as that would be to do shot by shot by shot, it's better than tearing frames!)

Okay, I turned off the ML menu and did a test with plenty of motion and went through frame by frame looking for shearing. Woohoo!! Looks like turning off the ML info overlay is the solution. It's just a bummer you can't see a waveform, histogram, CPU core temp, etc WHILE actually filming, that's sort of the point of the menu.

Perhaps this has been resolved in a more recent build?
#21
Thanks for the replies -

Histogram off, no HTMI out, global draw off, NOT crop mode, 24fps raw.

I have tried disabling just about everything that could take extra processing power, I'll try the suggestion of the latest nightly build. My build is from April 20th of this year. 

Curious, without the ML preview, how do you set up the shot? I would be bummed if I couldn't use live preview, or HTMI out or a histogram and had to "guess" at the information I need. Just trying to figure out what's causing the problem for now though, so running tests...
#22
Hey Everyone,

I keep seeing tearing/shearing in the RAW video off my 7D, examples bellow. Using 64GB 100x Komputer Bay Cards, they all test at around 67-69mb/sec with the ML benchmark test on camera.

Any help would be greatly appreciated, this is for a "no-budget" production. Should I try installing a more recent version of ML, changing settings, or do you think it's the cards being too slow?


screen shot pc



photo storage


uploading images
#23
Raw Video / Re: New and Old Banding Issues
November 02, 2014, 09:44:45 AM
Would this be in the general category of "banding" or is there another word for what's going on here? Has this been seen before?

I wonder if it's an issue with the card, or the firmware. Haven't seen anything like this with my other cards, so perhaps the latest batch of KomputerBay64's was just too slow to handle RAW... shooting with 7D.


windows 7 screenshot
#24
Quote from: Frank7D on June 09, 2014, 01:40:13 AM
If you just need DNGs, there's MLV Mystic...
http://www.magiclantern.fm/forum/index.php?topic=10466.0

Thanks for the heads up Frank! I will definitely give Mystic a try right now. Fingers crossed!

*UPDATE* Mystic worked great! YAAAY! Thanks again Frank - you saved my workflow bacon! ;D
#25
This converter is working great for me as far as exporting to DNGs, but I'm wondering is there a way to do batch conversions with it or something else? I was using M L RAW Video Converter 1.9.1 previously, but now it's spitting out errors and not working now...