[Mario Mattei]

I can’t change ISO or White Balance in the Cine EI shooting mode… strange and frustrating!! Anyone else having this issue?

There’s two shooting modes: Custom and Cine EI. We want Cine EI because that allows for the Slog3 color spaces. The Custom mode allows only the “matrix” color space and gives a “conventional video camcorder look” according to the manual.

When in Cine EI, we cannot change the white balance. There are three preset settings, 3200, 4300, 5500. There’s no dial for the ISO or way to change it. There are the low, medium, and high presets. We can custom set those. However, when changing from the lowest to the highest, there’s NO change in exposure. This is strange.

When in Custom shooting mode we can see exposure changes as we change the ISO. We can change the White balance preset and also use the White Balance Set button on the front of the camera set custom settings on the A & B presets.

Basically custom mode functions normally. Cine EI mode is very limiting, but we bought this camera to shoot in Cine style with wide gamut range. There’s got to be a way to control ISO and White balance. I don’t see anyone online talking about this.

And yes, we did the firmware update. Perhaps our camera is malfunctioning in some way? I’ve got a gig in Vegas. We’re shipping the gear on Sat Jan 3rd. So we need to resolve this.

Thanks for anything and everything,

[Mario Mattei]

Well, from one editor to the next, my heart goes out to ya!

When you say “saving a second back up”, do you mean that you’re copy-pasting a version of the project file into a separate location?

You can’t count on the auto-save files. So, how is the manual back up doing anything different? Seems like, if the project won’t open, then it just won’t open no matter which file it is… if we knew what was corrupting it, then that would help.

For me, it was LOOKS that corrupted my project. I was able to start a new project and import the broken one. Once that opened it was all funky, visuals were jacked. But I deleted all LOOKs fx, and that solved it.

You might be able to try starting a new project then importing your broken one… see what happens…

[Mario Mattei]

Yeah, that was my first move. Then I restarted.

The problem was with Magic Bullet LOOKS… this is about the 5th time I’ve issues with LOOKS. I will NOT be using it again.

I created a new project, imported the previous project, saw that LOOKS was jacking up every clip (weird graphic clutter and noise everywhere), then removed all LOOKS fx, problem solved.

thanks,
Mario

[Mario Mattei]

I am having the EXACT same problem right now. Literally exactly the same. I could have written your issue myself. Did you figure it out? I’m feeling pretty stuck!

[Mario Mattei]

iMac 2.7Ghz Intel Core i5
16GB RAM
OS 10.7.5

CS6
WAV 48hz files

[Mario Mattei]

Thanks.

I found an update to audition. But I can’t find anything for “dynamic link”.

Mario

[Mario Mattei]

Ryan, thanks. Quick clarification for point 3.

“(3) Verify storage locations inside of Audition (Preferences–>Media & Disk Cache)”

What am I verifying?

There’s one cache location, assuming it’s default. Library/Caches/TemporaryItems/Adobe/Audtion/5.0 And it appears to be empty.

[Mario Mattei]

Did some more tests after restarting my iMac. Strange. Some files would send to Audition. The same file that first gave me issues still crashed Prem. Another file send to Audition with no wave form. Another sent like that then crashed Prem. A different file opened okay. A different file crashed Prem.

These are just normal wavs from a Zoom H4n, either mic or lav. Doesn’t seem to matter which mic it came from. I always use the same equipment and haven’t run into this before.

Maybe this helps or maybe it further confuses us… ugh…

Thanks for helping me again yawl.

Mario

[Mario Mattei]

**bump**

same thing… Prem crashes when I rt. click “edit in audition”

[Mario Mattei]

Yes, 95% of the clips have combinations of Colorista II, Misfire vignette, & Cosmo, all Magic Bullet effects.

My 360p video (a 1080p sequence, nested into a 360p one, then exported ‘same as sequence’) just took 3 hours 45 mins.

It’s 3.7GB and now I’ve got to get it uploaded to vimeo for the client within 6 hours. Maybe the 1080p would have exported faster (as per the logic discussed in this thread). I just thought the 360p would be a smaller size to begin with and that ensuing 360p exports for web would also be smaller… so that’s the direction I’m going right now.

thanks for your help… any thoughts or tips is always much appreciated!

Mario