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 :)

Adobe Announces Support for Mysterium X

David,

I think I've found a couple of bugs with these new plug-ins.

First - and I've only seen this on a 25fps timeline - if I import some older color science and set the source settings to Version 1 (I did this just out of curiosity), run the footage a bit, then return it to the new default of Version 2, the importerREDserver.exe plug-in dies. Premiere is still up and running but I've lost the new importer and have to restart Premiere to get it going again. This happens at least 50% of the time.

Second - and similar to what Paul Bates found here:
http://reduser.net/forum/showpost.php?p=607520&postcount=11

When I import a clip with the new color science, I cannot change to Version 1 which makes total sense. But I get one virtual core maxing out giving me a ~23% CPU usage when nothing is happening. If I run the footage, all cores react normally. But once I stop the clip, one core is maxed out again doing something, again giving me around 23% total CPU usage. However, this problem goes away and CPU usage goes to virtually zero when I go to the media browser and change View as: from RED to File Directory. From then on, all is well behaved even when View as: is returned to RED. So something is getting hung up on importing new color science clips that clear when selecting File Directory.

FYI, I am on a PC with an 8-core i7.
 
After a little more testing, the second problem appears that it has nothing to do with the new color science. It appears that the CPU "hang-up" is related to 23.976fps footage vs. 25fps. It doesn't matter what color science these clips are. (I was originally testing between newer 23.976 clips and an older 25fps clip and came to the wrong conclusion.)

The strange thing is, I can put a 23.976 clip in with the 25fps clip and sequence and the CPU will start the 23% thing now where it didn't before. When I delete the 23.976 clip and save and reopen the 25fps clip and sequence, they STILL have the 23% CPU problem! Only when delete and reimport the 25fps clip, save and reopen does the problem go away! Very odd. I had to do it a few times to prove that was happening as it seemed to make little sense. It's as if the 23.976 "contaminates" the 25fps clip so it has to go away and be reimported.

The crux of it though, is that changing that "View as:" menu from RED to File Directory in the Media Browser fixes the problem. I hope that's enough info to give it a look.

Cheers - Mike
 
BTW, I do want to say that CS5 is very cool. I like it a lot, despite the two niggly bugs mentioned above.
 
Mike Smith said:
David,

I think I've found a couple of bugs with these new plug-ins.

First - and I've only seen this on a 25fps timeline - if I import some older color science and set the source settings to Version 1 (I did this just out of curiosity), run the footage a bit, then return it to the new default of Version 2, the importerREDserver.exe plug-in dies. Premiere is still up and running but I've lost the new importer and have to restart Premiere to get it going again. This happens at least 50% of the time.

Second - and similar to what Paul Bates found here:
http://reduser.net/forum/showpost.php?p=607520&postcount=11

When I import a clip with the new color science, I cannot change to Version 1 which makes total sense. But I get one virtual core maxing out giving me a ~23% CPU usage when nothing is happening. If I run the footage, all cores react normally. But once I stop the clip, one core is maxed out again doing something, again giving me around 23% total CPU usage. However, this problem goes away and CPU usage goes to virtually zero when I go to the media browser and change View as: from RED to File Directory. From then on, all is well behaved even when View as: is returned to RED. So something is getting hung up on importing new color science clips that clear when selecting File Directory.

FYI, I am on a PC with an 8-core i7.
Click to expand...

I will try and repro these and let you know

Cheers

Dave
 
KETCH ROSSI said:
Cool guys, I think that we can definitely get a good number of Redusers in the Adobe Group buy, hoping that David can get Adobe to make this one time offering to our community, and give us a good discount, so to make the move less painful especially for those that are heavily invested in FCP with Plug ins and all, like Meryem.
Click to expand...

Ok, I have nothing to do with sales so I don't know what will happen and no promises. However, someone is looking into the possibility of helping RED users. No promises and I have no idea if anything will come of it. But I will let you know...

Cheers

Dave
 
David McGavran said:
Ok, I have nothing to do with sales so I don't know what will happen and no promises. However, someone is looking into the possibility of helping RED users. No promises and I have no idea if anything will come of it. But I will let you know...

Cheers

Dave
Click to expand...

Thanks David,

much appreciated, and totally understand, lets hope that Adobe says yes ;~)
 
sven said:
Would love to hear about a sollution to sync easily external audio to the r3d files
Click to expand...

David, its the only thing holding us back from jumping to your platform on multiple machines and recommending it to numerous clients. Look up Sync&Link for a complete list of features to include.

http://assistedediting.com/Sync-N-Link/

BTW - Kick ass on your developments in PP, I'm very happy you're offering a feedback portal unlike some other software companies...
 
Michael Romano said:
David, its the only thing holding us back from jumping to your platform on multiple machines and recommending it to numerous clients. Look up Sync&Link for a complete list of features to include.

http://assistedediting.com/Sync-N-Link/

BTW - Kick ass on your developments in PP, I'm very happy you're offering a feedback portal unlike some other software companies...
Click to expand...

A non ideal workaround (sorry) is to make a nested sequence and manually sync your audio there. Then use the nested sequence as a master clip... We will make some baby steps soon to help with this workflow and hopefully have a full workflow in the near future.

Cheers

Dave
 
It`s pretty cool to watch this real time interaction/development..nice one David and Adobe,thankyou.I can`t imagine that the end result won`t be just what everyone dreams about..
 
Mike Smith said:
After a little more testing, the second problem appears that it has nothing to do with the new color science. It appears that the CPU "hang-up" is related to 23.976fps footage vs. 25fps. It doesn't matter what color science these clips are. (I was originally testing between newer 23.976 clips and an older 25fps clip and came to the wrong conclusion.)

The strange thing is, I can put a 23.976 clip in with the 25fps clip and sequence and the CPU will start the 23% thing now where it didn't before. When I delete the 23.976 clip and save and reopen the 25fps clip and sequence, they STILL have the 23% CPU problem! Only when delete and reimport the 25fps clip, save and reopen does the problem go away! Very odd. I had to do it a few times to prove that was happening as it seemed to make little sense. It's as if the 23.976 "contaminates" the 25fps clip so it has to go away and be reimported.

The crux of it though, is that changing that "View as:" menu from RED to File Directory in the Media Browser fixes the problem. I hope that's enough info to give it a look.

Cheers - Mike
Click to expand...

So far we haven't seen this... We are on a slightly newer build. We will keep trying though...

Cheers

Dave
 
Ok Dave,

Can I just emphasize that this only happens on first opening up a project. Once it's fixed by changing that menu setting, it stays good until you close and reopen it. In fact, I only noticed it because I had Task Manager open. Everything works fine. It's just that one core that's running pretty much maxed out until the menu thing which, incidentally, I found out by accident. If it hadn't been for Paul Bates seeing the same thing, I'd have suspected I was doing something wrong.

Cheers - Mike.
 
Last edited:
as professional Photo retoucher and RED user i thank adobe for being there for all my passions!!!!

looking forward to use it!


diego querzoli, EPIC on its way!
 
David, if you want to collect wishes, there are two things which I miss in the R3D importer panel. First of all, if there was a gamma curve adjustment preferable separately to each R,B, and G channel, then there were less need for grading with Redcine-X. Second, I find the monitor size of the panel bit small and therefore a switch to make the image better would be helpful. Perhaps other people have noticed the same that for some reasons reading color from a small image is inaccurate. I've several times noticed that when have looked some clip in a bigger window, the color balance have appeared different.
 
I want to take this opportunity to thank David, Lori and everyone else at Adobe for making this happen!

It's been a great experience working together and we're all committed to delivering a great RED workflow for our customers!

Alright, back to programming for me ;)
 
I'd like to say that Adobe seems to be changing their point release paradigm to be far more proactive in releasing both bugfixes and updates, such as this latest Mysterium-X plugin.

This is an awesome change and is rapidly going to propel Adobe into the minds of a lot of new customers.

It's 2010 and monolithic software development and one release every two years is no longer going to cut it in today's fast-changing digital cinema environment.

So kudos to Red for starting that paradigm and kudos to Adobe for taking it on board as well. This is a partnership that can lead to some amazing results if continued and I for one am looking forward greatly to it!

Cheers all,

Paul
 
Paul Leeming said:
I'd like to say that Adobe seems to be changing their point release paradigm to be far more proactive in releasing both bugfixes and updates, such as this latest Mysterium-X plugin.

This is an awesome change and is rapidly going to propel Adobe into the minds of a lot of new customers.

It's 2010 and monolithic software development and one release every two years is no longer going to cut it in today's fast-changing digital cinema environment.

So kudos to Red for starting that paradigm and kudos to Adobe for taking it on board as well. This is a partnership that can lead to some amazing results if continued and I for one am looking forward greatly to it!

Cheers all,

Paul
Click to expand...

Well said my friend.
 
David McGavran, thank you so much for being active here at Reduser.

Is there any way to support R3D files in Bridge? Unless I am missing something, right now, there is basically no way for Red shooters who use Windows to see thumbnails that can be deleted, moved, organized, etc. It would be awesome if I could use Bridge to manage and maybe even preview my R3D files.

Also, is there any way that we can ingest R3D files through Adobe Camera RAW? I think it would be tremendous to add RedRAW to the list of RAW formats supported by ACR. I love a lot of the tools in ACR and I use ACR/AE for all my Canon CR2 timelapse processing. For example, I would love to be able to use the "RAW Grad ND" effect on my R3D footage, and many of the other useful tools found in ACR.

Oh, and one last thing... can you please add the ACR plugin to Premiere!!! I have been emailing Adobe about this for years, and never heard back from them.

Thanks!!

Tom
 
You must log in or register to reply here.
Back
Top