Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

The mini MetaFuze thread. Share your experience and findings

We need to do some work still to make that work since the metadata used for the filename inside the R3D file does not match the filename outside. We are adding options to choose which way to go. Until there is one that matches the outside name, then it won't match.

Michael
 
On my yesterdays session to transcode RED files into DNxHD36 MXF with MFuze I figured that the RLX file doesn't took any effect to the transcoded MXF file. It looked the very same with and without that RLX file (badly flat and "grey"). Exporting a RED file with that RLX setting in REDAlert looks different. Is there another switch in Metafuze or setting to make to have the RLX working?

Another issue are the Metadata MFuze is creating: in REDCINE it shows a difference between EDGE TC and TC TOD - REDCINE uses the EDGE TC (e.g. for burning in) meanwhile MFuze uses the TC TOD. In MFuze I can't read out the EDGE TC. I'm a bit confused now how to deal with these different TC's to avoid messing up the project for the upcoming conforming.

Thanx for any idea - alex
 
We will be adding both timecodes as we get in REDrushes. As far as RLX - MetaFuze currently takes the settings and makes it REC709 since DNxHD is an HD format. Perhaps that is what you are seeing. We are looking to change that behavior and give more flexibility but for now we are protecting for REC709.

Michael
 
MichaelP said:
...MetaFuze currently takes the settings and makes it REC709 since DNxHD is an HD format. Perhaps that is what you are seeing....

Michael
Click to expand...


well... i am not sure this is rec709 either. it's just "something".

i cannot agre about REC709. it's so flat and washed...

i checked and compared with redrushes' REC709 , and it looked different (better). but maybe this result is somehow correlated with my footage?

anyhow, maybe someone can check this also and compare redrushes' REC709 space vs metafuze REC709 - and send some thoughts.


filip
 
filip kovcin said:
well... i am not sure this is rec709 either. it's just "something".

i cannot agre about REC709. it's so flat and washed...

i checked and compared with redrushes' REC709 , and it looked different (better). but maybe this result is somehow correlated with my footage?

anyhow, maybe someone can check this also and compare redrushes' REC709 space vs metafuze REC709 - and send some thoughts.


filip
Click to expand...

Are you taking a RLX from Redalert and applying it to MetaFuze? If there is any difference, could it be due to gamma display differences? I've seen MetaFuze look flat and washed, but only if I don't apply a RedAlert RLX.
 
Does the RLX contain a REC 709 already or is there a different one being used in the chain?

Michael
 
Thanks Forrest - forgot the quote part. Not to make you test it all, but if you change gamma before creating the RLX, do you find a combination that matches what you get out of the other tools?

Michael
 
Today I created a REC709 RLX file and set the Gamma as well as the Colourspace to REC709. The rest of the REDAlert settings I didn't even touch. The preview monitor in MFuze displayed a little difference by adding this RLX. After transcoding the MC revealed a minor difference in colour between with a REC709 transcoding and a "plain" transcoding without RLX but the Gamma seemed as flat as before. After that I pushed the "black" slider in MFuze to the nearly end (from 850 to 1800), skipped the RLX file since I assume MFUZE will transcode to REC709 colorspace anyway and finally the picture didn't looked washed any more and comes close to what REDCINE was exporting. I even skipped the RLX file because I hope that way the colour temperature which differs from shot to shot will be preserved. If you are going to create a RLX setting with REDAlert the colour temperature will be within this setting, or am I totaly wrong?
Anyway ... tomorrow, if I don't forget my mem-stick again, I'll load up some sample pictures with the different kind of transcodings.

alex
 
sample pics

sample pics

here are sample pics.

file entitled "no rlx.jpg" is without using RLX file - nothing touched

second one "WITH RLX.jpg" is just used RLX file. nothing else touched. (black is on default - 850 level).

i must say that when using different monitors (maybe this is just subjective opinion) - the difference between the two looks (regarding pic WITH RLX) - is greater than here. but, anyhow - it's not the same, and definitelly looks washed and more flat then the picture from the left side.

but... who knows, maybe i am doing something wrong somewhere...

filip
 
Does anyone have any suggestions in the meantime??

Does anyone have any suggestions in the meantime??

I'd like to go to lunch too...

I find having to individually select each group (i.e. every single shot) to transcode 1 by 1, infuriating, (is there another way?!!) there must be another way?! And I get back from lunch and it's crashed my 8 cores (PC Avid) or has only made it to the 7th shot (of 200 in just one folder) an nth of the rushes. And on my bootcamped dual Quad core MacPro it atleast doesn't crash but is painfully slow....
Sooo shloooohw I've reverted back to RedRushes to Avid DnxHD and then importing, which atleast makes me feel like I'm getting more done, even if it's self-delusion once it's crahsed several times, and then I've imported it into Avid and it keeps stopping due to Audio compatability errors (even with avid compatability ticked) so I can't just leave it and go home, and sleep easy with the knowledge that it will all be just peachy in the morning...

Does anyone have any suggestions in the meantime of any updated software for one exasperated Red'Software'User?

Thank you in advance %^)
Anna
 
This was one of the limitations listed with this version and is being addressed with the next release. The next release will also have audio and optimized speeds. What version of MC are you using? Anything v3.1 or later does not need the compatible audio checked.

Michael
 
filip kovcin said:
here are sample pics.

file entitled "no rlx.jpg" is without using RLX file - nothing touched

second one "WITH RLX.jpg" is just used RLX file. nothing else touched. (black is on default - 850 level).

i must say that when using different monitors (maybe this is just subjective opinion) - the difference between the two looks (regarding pic WITH RLX) - is greater than here. but, anyhow - it's not the same, and definitelly looks washed and more flat then the picture from the left side.

but... who knows, maybe i am doing something wrong somewhere...

filip
Click to expand...
In looking at my R3D files in RedAlert and MetaFuze, they look the same, flat and washed out with a Rec709 applied. I added contrast, brightness and saturation to get them to look similar to RedCine and Avid DS with Rec709 applied. I'm still figuring some of this out, but at the same time, clients are waiting so I'm going with what's looking good.
 
Anna Fuller said:
I'd like to go to lunch too...

I find having to individually select each group (i.e. every single shot) to transcode 1 by 1, infuriating, (is there another way?!!) there must be another way?! And I get back from lunch and it's crashed my 8 cores (PC Avid) or has only made it to the 7th shot (of 200 in just one folder) an nth of the rushes. And on my bootcamped dual Quad core MacPro it atleast doesn't crash but is painfully slow....
Sooo shloooohw I've reverted back to RedRushes to Avid DnxHD and then importing, which atleast makes me feel like I'm getting more done, even if it's self-delusion once it's crahsed several times, and then I've imported it into Avid and it keeps stopping due to Audio compatability errors (even with avid compatability ticked) so I can't just leave it and go home, and sleep easy with the knowledge that it will all be just peachy in the morning...

Does anyone have any suggestions in the meantime of any updated software for one exasperated Red'Software'User?

Thank you in advance %^)
Anna
Click to expand...
Hi Anna, as Michael has said, this selection 1 by 1 is a current limitation. Hopefully the next version will arrive soon.

I've found that if I send more than 20 transcodes at a time, MetaFuze will crash (XW8400 8core, 10gigs ram). I put Logmein on all my systems and can set off additonal files remotely (try finding a restaurant with Wifi for lunch:) )

As far as Redrushes, on our 4core Mac, it takes a looong time. And I have to keep a careful eye on it for crashes. I also had the audio compatibility issue with our Symphony 1.8, so I ended up digitizing on the Mac and moving the project and media after. Even then, on the Mac, the MediaComposer didin't like some of the files and would error with "file format not useable" or something similar. If I chose to batch import again, the file would come in fine. All in all, it took about 12 hours to transcode and import about 50 .R3D files, although only half were 3 minutes or longer. The other half were under a minute.

We were going to transcode on PC with MetaFuze, but since they formatted the drives for Macs, and there isn't a XP 64bit version of MacDrive, we ended up using RedRushes. It was going to take 7 hours to copy the files over to an NTFS formatted drive. I'll be advising our clients to format the drives NTFS and run NTFS Paragon on the Macs.

Logmein (or a similar VPN software) could be a good fit for you. At least it lets you check your system from home. As long as the machine doesn't lock up. I even have it running on my IPhone for emergencies.
 
Forrest said:
We were going to transcode on PC with MetaFuze, but since they formatted the drives for Macs, and there isn't a XP 64bit version of MacDrive, we ended up using RedRushes. It was going to take 7 hours to copy the files over to an NTFS formatted drive. I'll be advising our clients to format the drives NTFS and run NTFS Paragon on the Macs.
Click to expand...

Have you tried MacFUSE in combo with ntfs-3g? It's all free and really good imho. :biggrin:

...interesting new smileys on the forum. :nerd:
 
Forrest said:
...I'll be advising our clients to format the drives NTFS and run NTFS Paragon on the Macs.
Click to expand...


PLEASE!!!!


please, check and TEST it for yourself BEFORE any project starts...
avid MAY NOT work very well with ntfs for macs software.

i mean - ntfs works ok on macs itself, but within avid - i found that it is not stabile behavior, especially when ntfs disk is used to WRITE something on it.
generally - in my situation, i was not in position to predict it's behavior - i.e. will it work slower or not, will receive error or not.

if you need to use this combination (avid+ntfs for macs) in critical situation - TEST TEST TEST before.


filip
 
MichaelP said:
Don't know for sure - depends on engineering resources with other projects - but since there is no revenue recognition with a free product - I am going to go optimistic with 4'ish weeks.

Michael
Click to expand...

Only 3'ish more weeks, if I'm going to go optimistic. ;)
 
You must log in or register to reply here.
Back
Top