Flicker on Dragon Sensor R3Ds - pulldown bug?

Since upgrading our RED camera to the Dragon sensor, we've been noticing a strange bug. R3Ds that were shot at 23.98 fps that are put on a 29.97 fps sequence (or exported from a 23.98 fps sequence to a 29.97 fps file) are having something wonky occur with the pulldown. The first three frames of a five frame sequence are very dark, and missing fields. You can actually see black lines that are missing fields. Then frames four and five look "normal", or set to whatever color grade settings have been applied. So the overall effect is a flicker from light to dark, etc. The workaround is a pain, we have been exporting a 23.98 file and then putting that back on the 29.97 sequence, and then exporting the whole thing one last time.
Has anyone seen something like this? More importantly, is Adobe aware of this bug?
Thanks!
Matt Ruby
Atomic Productions, Inc.

Yeah, considered the upgrade 8 months ago... deemed it wasn't worth the risk to do so mid-project. *bangs head on keyboard* I probably wouldn't have had any problems either.
Yeah, that workflow sounds an awful lot safer... I hope I ended up putting those files on my buddy's drive, but I'm not banking on it.
So in deinterlacing and going frame by frame, I've noticed that all I'm really doing is ending up with a duplicate frame instead of an interlaced frame every 3 frames, so it's dupe, reg, reg, reg, dupe, reg, reg, reg, dupe.
Instead of deinterlacing and losing resolution on that one frame, I'm just going to cut out every interlaced frame in the shot, and put a second layer just underneath of the same clip, but advanced a single frame, so that way I at least end up with a full resolution duplicate frame. Then I'm nesting everything. I'm then increasing my speed on the nested sequence to 150% using the FCP to eliminate the duplicate frames, and slowing it down to 75% using Twixtor to interpolate the missing frame and approximate the original speed. I've been up since yesterday, so please tell me if my math is horribly off.

Similar Messages

AE crash after importing premiere sequence with trimmed r3ds. (Bug report)

(all tested in premiere and AE cs6, up to date from creative cloud) Hello, I have RED footage raw as r3ds, that I have edited in premiere. If I try to send that to after effects in premiere, or if I try to import the sequence directly through AE, The machine continually locks up over and over again until I close out the application. I have figured out potentially what is wrong and I have figured out an annoying work around.
I believe what the problem is, is that after effects is having a hard time reading the renamed and trimmed r3d clip. Point being, if I hit caps lock disabling preview, I can right click on the RED footage that was imported from premiere, and reveal in explorer (or finder for Mac, and yes, I have tested this on both OS) Then drag the original footage back into after effects, and then alt drag and replace the footage that is trimmed in the AE sequence, and lastly delete the premiere versions of the RED clips, then I can use it just fine. No more lagging, all is well.
This is a huge pain in the butt...Can this bug PLEASE be looked into for AE CC or Premiere CC whichever is causing the problem. It is very useful to cut in premiere and keylight/ special effects in AE. But this workaround is quite a time saver.
Can anyone else confirm this issue? I hgave confirmed it on a mac and a PC of cs6.
And if anyone has an easier workaround, that would also be appreciated, although, this was the quickest work around I could come up with.
Thanks Adobe! Love your tools!

I have found another fix, which is much easier! But yes this is still broken and must be fixed. After you import the RED footage from the preiere file, with caps lock on, right click on the red footage and go to interpret footage> Main. At the bottome of the window that pops up, click more options, which should bring up the RED R3D Source settings. This is blank, with no video attatched...all you do is click reload from RMD, and the problem is solved.
This is still a massive pain, Can anyone from adobe confirm this problem, and confirm this work around?

[BUG] iOS 6 - BATTERY DRAIN : SIRI Raise to Speak/Proximity Sensor Always On/Flashing When Screen Active

Bug: Raise to Speak sensor for Siri remains on whenever the screen is active - regardless of Siri Raise to Speak Setting (enabled or disabled).
After updating to iOS 6 (via iTunes - not OTA), I noticed that my battery was taking quite a bit of a hit. Granted I was checking out the new features but aside from a very short call, nothing major in the way of activity.
I had also noticed that Siri sounded quite a bit different with iOS 6 (10A403) than with 5.1.1 (9B206). Not only did the Siri Voice change but also the responses vary between the two iOS versions.
Example: What is the weather like in Alaska?
iOS 5.1.1 response:
Here's the forecast for Juneau, Alaska through Monday
iOS 6.0 response:
Here's the weather for Juneau, AK through Monday (note: Siri does not say "Alaska", instead Siri says 'A-Kay'
With iOS 6, Siri sounds more robotic. After looking at speech rate settings and comparing between the two versions, I could find nothing different. I decided to post a video and this is where the Siri bug became interesting and tied into the battery drain with iOS 6.
Remember with 5.0.1 we saw a hit on battery drain and one of the fixes was a fix to the proximity sensor (http://hottipscentral.com/could-siri-be-hurting-iphone-4s-battery-this-little-li ght-might-mean-something/). Well, it appears this bug is back in iOS 6. When I went to do the video, I noticed that my 4s had a flashing light near the earpiece. It remained on continuously. The only time it would stop flashing was when the phone was locked and the screen inactive. As soon as I hit the lock button to bring the phone out of lock, the sensor would begin to flash again.
Give it a shot, hold up your iPhone to a webcam and see if your result is the same.
Submitting this to Apple via the feedback form. Please do the same if you are seeing the same behavior.
http://www.apple.com/feedback/iphone.html

I dont believe so Amy. Phone has not sustained any damaging drops nor any liquid spills. Was not an issue before but I figured I'd post as I believe this is a definite bug. I neglected to mention that I have my wife's 4s (5.0.1 build) which I am using as a comparison.
Based on the issues folks are reporting with the ambient light sensor, its either the proximity or the ambient light sensor causing the drain. I've turned auto brightness AND raise to speak both off and the sensor continues to flash as I described in my opening post.
If others can confirm, this will definitely need to be looked at by Apple and fixed.
I just found this - same behavior (posted 7/24/2012 on another forum - source link below).
Hi folks, remember the proximity sensor (always on bug) I reported here in iOS 6 Beta 1 bugs/feedback thread? It continues to happen in beta 3, I reported to Apple and the answer I got from them is that it behaves how it's intended to do
Thing is, when you turn Raise To Speak feature off, and use your webcam (no IR filter) to verify if it turned infrared proximity sensor off, results that it didn't. Since iOS 5 this bug has been present, power cycling, or doing a soft reset solves this issue but this solution does not apply in iOS 6. Don't have an idea on how hard it is on battery draining, but it makes no sense that this sensor stays on forever even when you turn this feature off. Unless it has to do with constantly display brightness adjust feature that we have noticed came with iOS 6 version. Doing some test of this feature (some of you commented about a brightness bug in earlier posts) I noticed that ambient light variations make that display brightness adjust accordingly to brighter or darker ambiences. Previous to iOS 6, the sensor samples the ambient light, and adjusts the brightness; it does this only once--each time you unlock the phone after waking it. Now in iOS 6 you can easily watch how brightness slider adjusts itself when display senses light variations. If you open Passbook app it raises brightness to full (it is supposed to act this way for easy reading of barcodes) but getting out of Passbook app makes that brightness readjusts itself responding to actual ambient light intensity (this adjusting task occurs slowly until brightness slider stops to right level).
I've checked and ambient light sensor and proximity sensor are separate and work differently but if Apple says that an always on proximity sensor in this iOS version is behaving how it is intended to do; all that I could think of is that it has to do with ambient light "sensing"??
Source: http://forums.imore.com/1894808-post55.html

Video Playback Flicker Windows 7/8 Media Center? Disable Intel Dynamic Contrast to stop it

If you bought a Mac Mini for use as a Windows Media Center DVR Computer like me, you'll notice a background flicker on live tv or recorded tv.
Mine is the Mac Mini (Late 2012 Model) with Intel HD 4000 Graphics
If you go into the Intel Graphics and Media Control Panel. (icon in lower right) Go to Graphics Properties, Advanced Mode, Media, Image Enhancement, and UN-check the box for "Adaptive Contrast Enhanscement"
Video will then be flicker free! (aka 29/59 bug)
Here's a video that walks you through it.
http://youtu.be/9g6Z1sWOOIA
Also, if you have white snow, or video blank outs their is a firmware update for the Mac Mini 2012 model itself. I use Boot Camp, so my Mac OS X Mountain Lion side could update things when needed. (but leave the machine running 99% of the time in Windows 8 as my DVR)
I learned this from:
http://www.thegreenbutton.tv/forums/viewtopic.php?f=7&t=4022
http://www.avsforum.com/t/1439885/screen-flickering-in-wmc-during-video-playback -have-intel-hd-4000-graphics

Great tip/post, thanks!

Confused proximity sensor?

my iphone 3GS is doing the opposite of what it's supposed to do: when i hold it to my ear, the screen stays lit, and when i take it away, the screen goes black.
this has two negative consequences: one, my ear tends to press random "keys" on the screen, and when i take the phone away from my face to hang up, the screen goes blank and unresponsive. (i can sort of work around this by putting my thumb over the sensor, which activates the screen - exactly the opposite of what it's supposed to do - and then press a button.)
it's possible that this is being caused by my screen protector, although i can't imagine how or why (and i'm not the only iphone user with a screen protector), or by something wrong with the phone. (faulty sensor or firmware bug, etc.)
has anybody else had this problem, or more importantly, found a fix for it?

i am using a (very nice) speck skin-pro case, which i thought was 3gs compatible - guess it's not. until i can order a new case, i'll just cut a larger hole in this one.
i would have expected the proximity sensors to not work at all if they are covered in black rubber, but instead they sometimes they actually work backwards - with a call active, and the phone away from my face, the display blacks out, but the display turns on when something (face or thumb) gets close. very strange.
but this at least allows for a bit of a workaround: to hang up calls or push other buttons, i stick my thumb over the sensors, which turns the screen back on.

MOVED: CPU temp sensor hitting 255C during stress test

This topic has been moved to Overclockers & Undervolting & Modding Corner.
https://forum-en.msi.com/index.php?topic=155824.0

Quote from: Bas on 12-January-12, 16:02:07
I doubt TMPIN0 is connected to anything, ergo your program is reading nothing.
If something was 255C then you would see flames comming out of the system.
Exactly, and the heatsink is cool to the touch and the fans slow down.
255 is simply the maximum value of 1 byte - a value that goes from 1 to 256 or in this case, 0 to 255. For some reason the sensor seems to bug out and report a value as high as it can report.

Firefox flickers during ADF PPR

Hi,
When a PPR event is fired on ADF page element, which sets values to other fields, the panel or page is going grey for a while before re-rendering. Did anyone face this? This 'flicker' is supposed to be firefox bug as per some forums. Also, this flicker is not seen on IE.
Thanks
Chinni

PPR causes a repaint, so in my opinion, if you put a partial trigger on the page component, then the page component is redrawn resulting in a flicker.
- Ansuman

Exporting R3D and Dslr footage, getting flicker/strobing on export. What is going on?

Has anyone experienced a flicker or strobing like bug when working with R3D footage?
I am currently using an ultra key effect for the green screen keying, the DSLR footage is fine no flicker or strobing, also applied ultra key effect to DSLR.
I am not sure what the problem is, my next steps would be either to check if AE green screen keying or transcoding the R3D footage to Pro-Res 1080p.
Hope people can help me out. Have a deadline and would love to figure this out before another night of exporting.

I nested the sequence and that worked.
Is it possible that my cheap dell monitors are not good enough to display video off my new Mac Pro?
If so any recommendation for monitors.
Thank you
Sergio

Flicker footage in Premiere Pro CC 2014.2. Tested on different computers. When waiting for fixes this bug?

Flicker appears solely the fault of Premiere Pro CC 2014.2. Tested on different computers. Used as nVidia Quadro and GeForce GTX770. Drivers were different. Everywhere equally evident flicker. Incidentally, it defies logic and may occur at different film pieces. If re-render that flicker may occur on another spot in the video.
It can occur even in the parts without filters !!! But no all time.
ver 2014.2 - win 7 - intel i7-4770 - gtx 770 - flicker!
ver 2014.2 - win 7 - intel i7-4770 - Intel HD Graphics 4600 - flicker!
ver 2014.2 - win 7 - intel i7-2700K - quadro 2000 - flicker!
MERCURY PLAYBACK ENGINE work fine! But still flickering in preview and render.
When waiting for fixes this bug?

Hi Aleksey,
Flicker appears solely the fault of Premiere Pro CC 2014.2. Tested on different computers. Used as nVidia Quadro and GeForce GTX770. Drivers were different.
Have you tried with the Mercury Playback Engine set to "Software Only?" More info please: FAQ: What information should I provide when asking a question on this forum?
Everywhere equally evident flicker. Incidentally, it defies logic and may occur at different film pieces. If re-render that flicker may occur on another spot in the video.
Is this a brand new project or one you updated from an earlier version? What kind of footage are you exporting? Which preset are you using?
When waiting for fixes this bug?
If I can repeat the case here with the same hardware, GPU, and drivers, that would be easier to fix the bug. Currently, I cannot recreate the bug. If you or anyone else can provide me with steps to recreate the bug, that would help immensely. It sounds like this will be the difficult thing.
Thanks,
Kevin

Verizon, please help! LG G2 proximity sensor bug!

Verizon, please help, the update that you required me to do on 09/23/14 has a huge bug in it and I am fearful it has not only screwed up my proximity sensor but who knows may even have compromised the security of the phone. The proximity sensor does not respond in dimly lit rooms at all. You have to trick it by slowly swiping your finger across it just to hang up a phone call. The power off button does not respond unless you hold it down to do a soft reset. The "knock-on" feature does not work in dimly lit rooms either. This is so frustrating as it was working perfectly before the update. Please either send a fix update or allow us to resort back to the old software. This phone is less than a year old and I do pay for the warranty, however have been warned that all replacement phones are just "refurbished" phones that may have worse problems.
So, please VERIZON, step up and fix this issue. I have been into your store to discuss with sales guy and he said he would not file a warranty claim just yet. This is crap.....please advise.

https://community.verizonwireless.com/mobile/mobile-access.jspa#jive-content?content=%2Fapi%2Fcore%2Fv3%2Fcontents%2F1967494
If you repair your phone it is a refurb phone.

"Why Apple do not fix light sensor bug in ios 6 ipod touch 4g plz give me update for this"

Light Sensor increase but not Decreas light

As you have been directed in the other posts you've made on the issue, this is most likely a hardware problem with your particular iPod, and you won't get different answers by posting more threads on the topic. If this was a bug in iOS 6, I'm sure we'd have seen many more posts on the problem, so this is more likely to be a problem with your iPod, not with iOS 6 itself.
Regards.

Nokia E5 Light sensor bugs/problems SW: v042.010 (...

Hello nokia support! I have buy my new Nokia E5 in Germany VODAFONE.DE and, I just wont report about, bug wich ligt sensor in firmware v042.010.RM-612 Please See my recorded video on youtube VIDEO i hope that you fix this bug wich new firmware version as son as possable!
please sorry for my english, my language is russian...
Best greats your Nokia user

Nokia E5 has many bugs, im an experienced Nokia and Symbian user, i feel sorry that nokia doesnt car about even answering or at least get us an firmware update. I still buiyng nokia phones even if i know that android phones is much better, cause im still want to give nokia my support..but im really tired of it and im making the switch today.... the list of bugs that noki e5 have is enormous and theese bugs are really serious bugs since the functionality of the phone is almost completely useless if your into buisness..
Nokia .... sucks even at this....not answering and follow up the support.... not updating their firmwares in time....
Nokia is a singking boat....!!! THATS THE TRUTH !!!

Signatures Missing in Pulldown. Me or Bug?

Sorry to post this twice, but I never got a response and can't find a solution myself.
I am adding signatures via Mail > Prefs > Signatures
But they are not showing in the pulldown when I create a new email to send.
What am I doing wrong? Or is this a bug?
Thanks, Steven

are you adding the signatures to particular accounts? they won't show up in the pull down menus without that. after you create a signature drag it to a particular account right there in the signatures pane. then it should become available in the pull down menu for that account. you can also make a signature default so that you don't have to use the pull down menu every time.

Bug: Adobe Muse Menus Flicker At Every Click

I'm a big fan of Muse. In the latest version that I downloaded today, whenever I click a menu, or navigate to a menu via the keyboard, or type a keyboard shortcut like control-d, the menus will flicker, sometimes for 3+ seconds before the menu shows or the action completes. This bug is unfortunately making Muse nearly unusably slow.
Here's a video of the bug in progress:
Does anyone have any suggestions on how to work around this or if Adobe's working on fixing this bug?

It is an issue known to the Muse dev team and is slated to be fixed in coming releases.
Thanks,
Vikas

Nokia N8 Firmware Bug(Sensor Setting)

Whenever I filp over my N8 on an incoming call it goes into silent mode even though the sensor setting is set to off.
I forced my friend to buy a N8 and this problem was also found in his N8 Grey.
Are nokia developers aware of this?
Video:
http://www.youtube.com/watch?v=WFk0DSjaxIc

It happened to me again, but I managed to make it work again. It seems when you restart the phone this option stops working properly. So what I did to make it work again is:
1. I ticked the silence calls box, then
2. I restarted the phone,
3. With the ticked box tried calling to see if it worked – it did what it was supposed to do (it silences the calls when I turn the phone over), and
4. Then I un-ticked the box and it started to work properly i.e. it does not silence the calls.
From trial and error, I noticed that step 3 is important!
Good luck.

Flicker on Dragon Sensor R3Ds - pulldown bug?

Similar Messages

Maybe you are looking for