DNG file work-around PrPro/Sg/Pro

So there are the irritations with PrPro not being able to work "natively" with the footage put out by many of the RAW -capable cameras. Yes, having the video equivalent of Adobe Camera Raw in PrPro would be wondrous. However, there is a way that seems to be able to get around this, using PrPro with Sg. I've not tested this but I've seen the comments of those who've done things like this on other forums, and from my knowledge of Sg, suggest this be tried by people as a workable temporary solution until Adobe manages to get ACR into PrPro.
I'd suggest shooting a few seconds of a "normal" contrast scene with a good histogram-filling range of luma tonalities under lighting with a decent color to white-balance to. Also shoot a few seconds of a neutral such as a gray-card or white through black video test card.
1) Load into ProPr & Direct Link to Sg, or simply create a new project in Sg and bring in the above footage. Work on the base footage, not in a layer.
2) Using both monitor & scopes, correct the gamma and contrast for an "appropriate" look on both monitor and scopes;
3) using the neutral scene center the signal on the vectorscope;
4) save as a LUT or Look with an appropriate title, such as MkV_iiidRAW or whatever so you know what camera that is "built" for.
For future work, you should be able to load footage in PrPro, first thing is Direct Link to Sg, then apply the Look of LUT, back to PrPro for editing, back to Sg for corrections/grading as normal.
Not optimal, but for many it might just work ...
Neil

This is in reply to your last paragraph...
This is the Mac OS default Save As... dialog:
Notice that there is a downward pointing disclosure triangle to the right of the Save As: field. If you click on the disclosure triangle, a full Finder window will be exposed, and this will enable you to place downloaded files wherever you like.
Notice, also, that in the bottom left hand corner of the exposed finder window, you are able to create a new folder (in any location on your system) to which you are able to download files.
This works the same way in any Save As situation, using any app, and the app you are in will remember where you last chose to save a file so that repetitive navigation in these dialog boxes is somewhat reduced.

Similar Messages

DNG files are importing into premiere pro cc with heavy pink tint what to do?

I have tryed many things to remove the pink to no avail, out side of importing through After Effects cc. What else Ican i try? Is there a fiix in the works?

This happens with certain video DNG files from particular cameras. Search here for dng import problems and you'll find threads about it ... including a recent one where someone found a look or LUT that could be applied to make the footage usable apparently.
Neil

Soundtrack Pro import AIFF files Work Around

I saved my AIFF Apple audio files from the earlier version of Soundtrack Pro. I dragged an AIFF into Favorites in the Browser lower right side of UI, worked with it, and "Saved As" send to Desktop and it works.
It won't let you export, but you can bring it into Final Cut from the desktop, by Selecting File & Import.

The goal is to make the files accessible to an Avid Media Composer. Turns out that the only format the MC will import is 44.1K AIFF. It doesn't know what to do with Apple lossless. Maybe it can work with WAVs -- I didn't try that. (And you can't drag and drop to import...)
So what I'm doing is using Libra to point iTunes to a library on a firewire drive, and then importing the CDs as AIFFs. This seems to work.
I will then bring the firewire drive to my place of work and import the files into iTunes on the Mac there.
The only question I have now is whether I needed Libra. What happens when you tell iTunes to change the location of the library? Does it read in an existing library and index it, or do you have to re-import?
Thanks to both of you for your help--
Steve

.mov files work on my Quicktime Pro 7.1.5 but not on others

I have .mov videos on my website that are working fine when I look at them in Firefox or IE but only show an audio track for others on older Macs and Windows machines with no video. I am using Quicktime Pro 7.1.5 for Windows, and some of those movies were created using this version but others are older and were working fine before. Any ideas?

Works just fine for me (Tiger and Safari).
PC viewers would only need QuickTime 6 (or higher) to view.
Your file uses MPEG-4 Video codec and AAC audio. The hint tracks are not needed as any .Mac page merely downloads.
http://homepage.mac.com/sammscript/.Movies/Miami%20Impeachment%20Protest%201.mov
Copy (do not click) the URL above and use QuickTime Player's Open URL menu to paste.
BTW, MPEG Streamclip (free) could crop out the black and some html "tricks" could display the same file at twice the dimensions. That would require "custom" page code not offered by .Mac but very easy to do.

Patch or Work Around for Mac Pro Version 1.1?

It may not be available yet, but please let us know if any patch or programs get released allowing older Mac Pros, v1.1, to run Mountain Lion.
My Mac Pro is stable, works great, has over 3 TB of HD Space and 12 gig ram. Runs fine...may just leave it alone.
But it won't accept a Mountain Lion update and I suspect this will not be the first OS killing off older machines.
Plus, I can't believe my bottom end Mini updates just fine!
Intentional Obsolescence needs to be fought, imho.

"It may not be available yet"
This question may not be answered in the immediate future.
But at some point, there may be alternatives.
Yes, 10.7.4 is running fine so far on my old Mac Pro.
"De-Contenting" hasn't killed it off yet.

Bridge 'get photos from camera' stopped working and Bridge won't recognize my DNG files anymore

So, I've got Bridge set up to get pictures from mem.card whenever I insert one in my laptop (win. 8.1). A week ago I installed Sony's PlayMemories. Without asking me it hijacked Bridge's task of getting pictures from my cards. What's worse, I tried to fire the 'get photos from camera' function manually from Bridge. Bridge starts working, but nothing happens. I uninstalled PlayMemories and reset Bridge, also told my laptop to run Bridge whenever I insert a card. Still nothing happens and I still can't get the 'get photos' function to run manually from Bridge. Anyway, I can still rund the DNG converter to get my pictures, but today Bridge won't recognize my DNG files - worked fine yesterday. I downloaded CS6 from this link https://helpx.adobe.com/x-productkb/policy-pricing/cs6-product-downloads.html and tried to run the installer, but it doesn't seem to do anything. Maybe I need to do a full uninstall off CS6 for it to do anything..? Anyway, if any of you guys could help me with my Bridge/CS6 issues I'd be grateful. I've got 3 sets of concert photos and a snowboard comp. shoot I need to finish this week
CS6 running on windows 8.1

Re-install of PS CS6 resulted in the following errors:
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 3 error(s), 1 warning(s)
----------- Payload: {CFA46C39-C539-4BE9-9364-495003C714AD} Adobe SwitchBoard 2.0 2.0.0.0 -----------
WARNING: DF029: ARKServiceControl::StartService: Service not started/stopped SwitchBoard. Current State: 0 Exit Code: 0 Service Specific Exit Code: 0(Seq 1)
----------- Payload: {C41A769E-27ED-44F7-8A11-F2E32F538E05} Adobe Linguistics CS6 x64 6.0.0.0 -----------
ERROR: DF024: Unable to move file at "C:\Program Files (x86)\Common Files\Adobe\Installers\adobeTemp\{C41A769E-27ED-44F7-8A11-F2E32F538E05}\_249_92e651345849 4a10e8de711f4c5be8e5" to "C:\Program Files\Common Files\Adobe\Linguistics\6.0\Providers\Proximity\11.00\araphon.env" Error 1392 The file or directory is corrupted and unreadable.(Seq 251)
ERROR: DW063: Command ARKMoveFileCommand failed.(Seq 251)
ERROR: DW050: The following payload errors were found during install:
ERROR: DW050: - Adobe Linguistics CS6 x64: Install failed
This doesn't really tell me much, anybody else got a clue what this is...?

Photoshop CS5 photomerge with dng files crashes

hello and greetings from Finland,
I have constant problems with photomerge tool when using dng files converted from Nikon´s nef files. Photomerge loads all pictures, normally 4-6, starts to align them etc. process seemst to be running just fine. Just before finished panorama picture should appear to screen, photoshop returns to default state. With original nef files, everything works just fine. This happens only with dng files. I´m using iMac (i5 processor with 12 GB RAM, cache for Photoshop in separate HD etc.)
So far I have tried following tricks for this problem; several resets for Photoshop settings file and reboot after that. Uninstalled and reinstalled whole Ps twice. Used two different, formatted memory cards in camera (Nikon D700).
After those, no help. Maybe second reinstall gave some relief for this, dng files worked fine couple of times, but now I have that same error again and I´m running out of ideas what to do next. And once again, I have this problem only with dng´s.
Any similar experiences? Did you managed to get things work again? How?

I don't mean to break your rocks, Chris, but try to keep some perspective... A component of Photoshop exiting abnormally (and delivering no results) is a crash to any user who doesn't have a deep insight as to how it's implemented. Maybe it's not as serious as a "whole Photoshop crash with loss of data", but it's not an unreasonable interpretation.
"Not finishing" could be your internal definition of it, and I might even agree with your terminology if it just popped up a message saying "The price of tea in China has risen too high - Photomerge must exit", but just quitting without any message is a crash by any reasonable definition.
Regardless of what Adobe may say, rillumarei, I personally have come to believe Camera Raw leaves some corruption of memory somewhere as I've found any editing session after a Camera Raw run seems a little more likely to fail than one where a PSD or other "normal" image format is opened (without Camera Raw).
-Noel

Insane XML Import, Huge Project, Duplicate file names work around...

I planned on kicking off my journey attempting to edit a massive multi year documentary on FCPX with a nice introduction of the blog I'm going to keep about the experience, but I've run into a bit of a roadblock, or maybe major speed bump at least before even getting to that point. I wanted to share what is working as a work around for me and you guys can tell me how I'm doing it wrong.
Ok, I will try to explain this as succinctly as possible. I'll write in somewhat stream of consciousness just to try and get through it quicker... Basically, after discovering the work around below, I am now utterly confused on how FCPX handles the relationship between its own database of where media is stored, and the actual media itself. I have plenty experience on FCPX now, probably done 30-40 pro commercial jobs on it over the last year since XML became doable as I'm also a Resolve Colorist and all the FCPX projects where hardcore coloring product spots. For commercial work, I never needed to worry about splitting up footage up over multiple Events. Everything, all in one, FCPX handled it no problem. (well the occasional beach ball, but that seems to be a thing with FCPX in general)
This will be my 10th feature documentary as an Editor. Every one before it was either on Avid's many flavors over the last 12 years or FCP Studio. When this new film came along, I made the decision a few months ago to use FCPX for a few reasons, but mostly because I'm insane and I like to try to mix it up for myself in a career that can get stale quick if you aren't willing to be that way. The film was shot over 2+ years, every shoot was multi cam 5D (yes i know, looks great, but please kill me), I haven't done the math on length, but there is over 10,000 clips of video (this is actually medium in size compared to what I've dealt with before). Its 5D, so theres external audio for everything. FCPX's syncing is great, but I've learned that theres an unsaid window of heads and tales clips must fall within to sync properly with the nearby clips, if they are too far apart FCPX gives up. One shoot day could have 3 cams, 50 clips each, and 2 audio files to sync to, FCPX simply cannot handle this, so off to Plural eyes they went, no problems.
Ok, all this is relevant eventually I swear! Again, in the past, all in one event, no problem. I tried for fun to bring all media into one Event on this film. It worked, but there is a 10+ second spinning beach ball for every single move you make, so thats no good. Ok, I'll separate the Events out to, lets say, each shoot month. Well that's dumb, in verite documentary, any shot could be the first, any shot could be the last, you need a command over all searchable footage at all times. Shift selecting all events to search *****, and it actually takes longer for FCP to reload each event each time than it does to just have the one massive one. So no go there. Next hair brained idea... What if make a new Event that is just Compound Clips of all the other Event's contents and do more with Markers and Favorites in logging that I was planning to parse it all out. That way I'm working with and FCPX is dealing with 50-60 clips instead of 10,000+ Quick test, Cmd-A, Opt-G, boom, boom, boom, move all to dedicated to Event, hide huge Event, BEHOLD, that works! FCPX chokes a little bit on the insane length of some of the clips, but searching, and general performance is back on par!
So your saying to yourself "Ok *********, sounds like you figured it out, what's the problem." Well to you I say, "Not so fast!" Remember, that was just a quick test using the media I had imported into the massive 10,000+ clip Event. To do this project proper, I am having to import Multicam sync'd XMLs from Plural Eyes. And this is where it all starts to fall apart. A little foreshadowing for your eager eyes. 10,000+ files all shot with multiple 5D's over the course of years. What does that mean? many, many duplicate file names!
FCPX as well all know irritatingly imports XML's as new Events, not into existing ones. This obviously takes a lot of burden off media management because with a new Event comes a new database referencing its own version of the raw media. All well and good, and I'm betting its starting to click for some if you advanced users where I'm finally going with this. So I have 50 or so XMLs to bring in, all done no problem. Now I want to replicate that singular Event like I did with the Compound Clip test and have it all in one place to be my master as extensive logging begins for easy searching once editing begins. Highlight the Events, click Merge Events. NOPE. I get a new "Kill Yourself Now" error (a term I coined for Out of Memory and General Error messages in FCP Legacy meaning there ain't much you can do about it): "Two or more files have the same name. Change the names and try again, because I don't know what the **** to do with them." Ok I made up that last part but that's basically what it's saying. Just take the variable out of the equation, this happens with every which way you could try to get the clips together. Merge Events, dragging events on top of each other, dragging just the Multicam clip alone, nothing gets passed that message. What's worse is that while Batch Renaming seems like a solution, the renames do not populate inside the created clips and there is no way to Batch Rename those. Renaming everything at the finder level isn't so great because then I'd have to resync and theres an offline/online thing going here where the film has to be reconformed eventually.
Basically, I've found that FCPX handles media management in completely different ways depending on whether you are importing into one Event yourself or doing essentially what is a new import with FCPX moving or merging Events. If you bring in all the media to one Event, on a macro level FCPX goes through file by file making aliases referencing the master file. If it hits a duplicate, it makes a parenthesis counter, and keeps going. And with the genius of FCPX metadata, that file name doesn't even matter, you can change it at the Finder level and FCPX will keep the link intact. BUT for some reason if you try to do this outside the realm of a single Event and combine files after the fact a different process takes over in creating this database system and can't handle the duplicates. I can't totally figure the reason other than it probably is scared to change the originally referenced alias to something else (which it shouldn't be scared of since Merge Events deletes the original anyway).
This is where it gets INSANE and where I lose all understanding of what is going on, and believe me it was a delicate understanding to begin with. It comes in to play with the work around I figured out. I make the master Event with the 10,000+ clips. Then I import all the XMLs as dedicated Events. Now, I then drag the Multicam clips into the master Event, it WORKS! just takes it, no "Kill Yourself Now" error. Stranger still, now with the switched referenced Event, it even takes into account which aliased duplicate file name it's referencing in the Original Media folder. Somehow, it's taking into account the original file path and saying "Ok, I see 5 instances of MVI_5834.mov. Based on the original file path or maybe creation date or god knows what, it must be MVI_5834 (fcp3).mov." It connects perfectly. I can even remove the old XML imported Event with no problem. Crazier yet, I can now move those again to the dedicated Event I wanted originally that only contains those Multicam or Compound Clips.
So instead of going straight from A to C, going from A to B to C works even though that actually seems way more complicated. Why can't FCPX handle Merge Events and dragging clips the same way it handles media imported into a single Event. And weirder still, why can't FCPX handle the (fcp1,2,3...) appending in the same scenario. But if the appended links are already there, No Problem. And for the love of god, it'd be nice to important XML's into existing Events and make the correct referencing happen right from the get go, which is really the source of all the above headache. I'd have no problem helping FCPX with a little manual pointing in the right direction just like any other NLE needs.
Ok, having said all of that crap above, my question is, have I missed something completely simple I should have done instead? Now that I have everything in place how I originally envisioned, I think I will still play around a little bit more to make sure FCPX is really going to be able to handle this project. I'm at a stage right now where going another direction is still an option, although the dare devil in me wants to make this work. Media management aside, once you start editing on a FCPX timeline, its hard to go back to anything else. Apple is going to have to figure out some way not to access to everything at all times to work fluidly or big projects like this are never going to be practical in FCPX.
Sorry for the long confusing post....

I'm having the exact same problem, but I know nothing of ruby scripts. I've exhausted my resources with tech support, and after literally hours of work with them it seems I now am faced with either re-rating each individual song, or pointing iTunes to each song that it can't locate. Is yours a solution that could help me? How can I find out more about Ruby Scripts? Thanks for your help, hellolylo (or anyone else who might also be able to help...)
Kenn

Work-around for lack of cut and paste for files in finder

I am new to Mac and have observed some past but closed discussions about the annoying lack of cut and paste in Finder. I too find it very time-consuming to move a file into the folder where I want it to live - especially from downloads. Using a MacBook Pro 13", my open windows are naturally on top of each other and using drag and drop with a touch-pad for file organisation is very cumbersome. Four finger behaviour on touch pad only helps so far.
The approach I adopt is to use cmd c to copy the files or folders in question. cmd ` to flick between finder windows (usually more than one is open) and cmd v to place the files or folders where I want them after navigating through to the destination folder. Shift cmd N gives me a new folder if required. cmd ` takes me back to source folder (usually downloads) so I can cmd delete the files and keep things tidy. This is lengthy to write down. It is however reasonably quick if your fingers know the keyboard shortcuts.
Is there a more efficient way for me to work around this inhibitory feature of Finder? "Save as" is only good if you know you have a folder in your file structure already created and named and suitable to receive the file you want to file away (usually an attachment to an email).

This is in reply to your last paragraph...
This is the Mac OS default Save As... dialog:
Notice that there is a downward pointing disclosure triangle to the right of the Save As: field. If you click on the disclosure triangle, a full Finder window will be exposed, and this will enable you to place downloaded files wherever you like.
Notice, also, that in the bottom left hand corner of the exposed finder window, you are able to create a new folder (in any location on your system) to which you are able to download files.
This works the same way in any Save As situation, using any app, and the app you are in will remember where you last chose to save a file so that repetitive navigation in these dialog boxes is somewhat reduced.

Will Premiere Pro CC support Cinema DNG files?

Will Premiere Pro CC support Cinema DNG files?

That would be nice, but my guess is that if support was built in, Adobe would have made mention of it as a new feature.
Given that Blackmagic is releasing a $1000 DC camera that records CinemaDNG to SD cards, it sure would be nice if PP cold work with them natively. People, please keep filing that feature request.
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

I upgraded my macbookpro hard drive to 1 TB then migrated my files from time machine. I'm now locked out of the computer because the password is not the same as my usual one and one that was years old and not retreivable. How do I work around this?

I upgraded my macbookpro hard drive to 1 TB then migrated my files from time machine. I'm now locked out of the computer because the password is not the same as my usual one and one that was years old and not retreivable. How do I work around this?

Whether or not you are able to recover the data off the drive yourself will depend on if the drive suffered any impact damage in the crash. You can buy USB SATA or IDE adapters (Intel and almost all G5 use SATA) that will let you connect your hard drive to a computer (like a flash drive) to see if you can recover the data. If the drive has suffered physical damage if may not mount.
If you know someone who has one of these adapters you could try using theirs, otherwise you could buy one but you take the risk of the data on the drive being non recoverable. Regardless, both are much cheaper than $1699!
(Alternatively, if you know of someone with a Mac Pro or PowerMac G5 they may be able to install the drive in their machine and try to boot from or mount it and copy the data off.)

Premier Pro CS6 AVCHD work around

After installing CS6 and using may applications I removed CS5. I then discovered the problem with Panasonic AVCHD files being functionally unusable. After looking at the threads here, it appears I am not alone and there is no word on an target date for a fix. I decided to use the media encoder to rewrap the .mts files as .mp4. They are about 25% smaller and everyting appears to work as advertised. I have the luxury of having computers everywhere and simply set this task up on an idle box. It takes some preplanning, but I will simply start the process of converting all the raw footage scheduled to edit and wack away at it.
Is there a downside?
Is there any news on a target date for a fix?
Editing Computer Specs:
Intel Core i7-2600 @3.4GHz
16.0 GB Memory
NVIDIA GeForce GTX570 Display Adapter driving dual monitors
Patriot Wildfire Solid State 120GB working drive (Media Cache also directed here)
Premier Pro version 6.0.1

Hi Guys,
I've got NO problem whatsoever bringing AVCHD files into Premiere Pro CS6. It works great. I can do it all day long.
I've noticed that no one here has mentioned a very basic detail. That is what operating system you all are using. There are some changes around the way that OS 10.8 (Mountain Lion) handles AVCHD files, but those changes don't stop CS6 from importing the files. It can however, cause some issues with older projects that were created before installing 10.8, but those can be worked around.
The most common cause for not being able to import AVCHD files (you get a file format is not supported error), is that you haven't activated Premiere Pro CS6 (or you are running in the trial mode). Until you activate, you are unable to import ANY mpeg compressed file. This has to do with paying mpeg licensing fees to MPEG LA.
If you've activated your software and you still can't import AVCHD files, trash the Premiere Pro CS6 prefs file, trash the plugin cache and relaunch the program. Or...call Adobe technical support.

No media Data \ BMPCC .dng file \ Premiere Pro 7.2.2

Hi there.
So, I just watch this cool demo explaining that now, I can finally import my raw .dng file from my lovely BlackMagic Pocket Cinema Camera into Adobe Premiere Pro CC ( version 7.2.2).
But... it still not working.
I still get the same message:
"Error Message"
"The file appears to have no media data."
The file opens up just fine in Photoshop camera raw.
So... what's going on?
Merci.

The Error is back!!!
Yesterday it worked today it crashes when I export from premiere via media encoder. I tried it with all the things you told me:
1. Bars+Tone => export => crash
2. Video Project with 2 short h264-files => export => crash
3. Software only renderer => crash
These are the two logs that I found:
Ereignis-ID 1000
Die Leistungsindikatoren für den Dienst WmiApRpl (WmiApRpl) wurden erfolgreich geladen. Die Eintragsdaten im Datenbereich enthalten die neuen Indexwerte, die diesem Dienst zugeordnet sind.
System
Provider
[ Name]
Microsoft-Windows-LoadPerf
[ Guid]
{122EE297-BB47-41AE-B265-1CA8D1886D40}
EventID
1000
Version
0
Level
4
Task
0
Opcode
0
Keywords
0x8000000000000000
TimeCreated
[ SystemTime]
2014-04-16T08:25:51.922502600Z
EventRecordID
3402
Correlation
Execution
[ ProcessID]
19984
[ ThreadID]
24964
Channel
Application
Computer
Schnittplatz
Security
[ UserID]
S-1-5-18
UserData
EventXML
param1
WmiApRpl
param2
WmiApRpl
binaryDataSize
16
binaryData
38270000DE27000039270000DF270000
So it would be great if you have any idea what to do...

"Edit In" Photoshop CC not working for RAW or DNG files after applying LR 5.3 and Camera Raw 8.3

I just applied the Lightroom 5.3 and Camera Raw 8.3 updates and now am no longer able to open RAW or DNG files into Photoshop CC. When I select a file and choose "Edit In" Photoshop, photoshop will launch, then nothing will happen. After 2 to 5 minutes, an error will popup in Lightroom saying "The file could not be edited because Adobe Photoshop CC could not be launched." An error I've never seen before. When I click "Ok", Lightroom will show that it's "preparing a file for editing" in the upper left, it will create and save a psd to disk and in the catalog (another new behavior), then it will open in photoshop. All other file types (jpgs, tiff, psd) seem to work/open fine between applications. No difference if I open photoshop prior to selecting "Edit In". Selecting "Edit In" other applications, like Viveza, work fine.
I tried first deleting preference files in both applications. No luck. Ditto for plugins. Notta. Eventually I completely uninstalled and fresh installed Photoshop, Lightroom, and Bridge from the cloud. Same deal...can't open raw/dng files into Photoshop.
I'm at a complete loss, dead in the water, with a mountain of editing work piling on top of me. Kicking myself for applying the upgrades, which I had been delaying for some time to avoid just such a cluster%#$. Ugh.
I'm on a PC running Windows 7 64bit.
Any suggestions would be greatly appreciated.

In the normal situation, LR needs to see a PS installed for it to detect the Edit In PS option is possible, so if you uninstall both, then install PS, first, then LR. Of course with this release there may be some hiccup that requires installing either one or the other, again, but if you've uninstalled both and are reinstalling both, then install PS, first.

Is there a work around for my Akai Pro EIE Pro interface to work with mountain lion

Does anyone have a work around for the Akai EIE Pro Audio interface that just stopped working after the mountain lion upgrade. Akai has no response currently.

Yep,
They say they're working on it.
It ***** though
effo

DNG file work-around PrPro/Sg/Pro

Similar Messages

Maybe you are looking for