[Mel Matsuoka]

I’ve reported this bug to BMD already…I’m only seeing this problem when I play the timeline while the Windows panel is open.

If you switch away from the Windows panel restores full realtime playback (at least on my system).

[Mel Matsuoka]

Here ya go:

I mapped this to ⌃⌥⌘E (I like to map custom shortcuts using the “⌃⌥⌘” modifiers combined, since it’s easy to remember and easy to press), but you can map it to whatever key-combo you want.

Also be aware that the ellipses after the “Export Project” Menu Item is NOT simply three consecutive periods. You have to type this as an actual ellipses character, by typing “⌥;”

You’ll obviously have to change the save location for the “Resolve Projects Backup” folder to where you want it (I also have an associated Hazel rule which automatically copies any backups that are dumped into this folder to their respective specific main project folder, so when I archive my main project folder, I dont have to manually copy the backup projects out the original backup-dump folder

[Mel Matsuoka]

Thanks for the confirmation, Dwaine. Looking forward to a quick fix to this!

Aloha,
mel

[Mel Matsuoka]

[andrew smith] “Kinda surprised it could be released with this many bugs and a kind of “send us your project file, xml, footage, crash report, etc. nope we don’t see that issue on our end” response without actually telling users that YES many others are also experiencing all these bugs and you are not alone.

To be constructive here because I do actually think they are doing great work, I think it would help greatly for BMD support to share what bugs people are finding as soon as its a consensus among enough users or have a section on the forum for bug reports or something so users can get an idea of what is going on. Being left in the dark on this stuff i think is the most troublesome thing for me as a DaVinci user..I dont have this issue with Adobe, Maxon, Imagineer, Autodesk, etc. whom I have also invested in greatly.
“

I’m gonna take a conjecturing “pundit” role here, and assume that the reason why R9 was shipped in the state its in is because of it’s marketing tie-in with the BMD Cinema Camera. In other words, it HAD to ship if they didn’t want to hold back the release of the camera any further.

This is a bit disconcerting to me, as this sort of strategy is giving me flashbacks to the way Apple handled the ProApps right before and during the FCP-X debacle. BMD are marketing and engineering geniuses, but it’s pretty clear at this point that they are taking the Razor vs. Razor Blade approach to Resolve. In other words, Resolve is the free razor that gets everyone through the door, and the BMD Cinema Camera is the razor-blade through which they actually make their money.

It’s an absolutely sound business model. But history has proven over and over that this model is not good for “professionals” who depend on this software for their livelihoods. This is why it’s worth paying the more expensive costs associated with brands like Autodesk and Adobe, because you know that money is going directly into sustaining the product itself, and isn’t just a little strategic cog in a greater business plan that may ultimately find your favorite product killed or neglected later on down the line because it no longer fits in that business model.

This is why I feel that while making a “Free” version of Resolve is good for BMD and the art of color-grading in general, it’s probably not good for the product itself, because it may collapse under the weight of the priorities of the “free” users, and excuses can be made by BMD that certain non-glamorous features can’t be implemented or fixed because they don’t have the resources to dedicate to niche needs. Having a paid user base is the only way I can see to ensure the continuing quality and support of any software product.

I hope this doesn’t come off as “biting the hand that feeds you,” because I love love love Resolve, and am so impressed with where BMD has taken it so far, but I think it’s a good idea to keep a reasoned perspective on the future of the product, considering how cheap they’ve made it, as well as the marketing tie-in with the Cinema Camera.

[Mel Matsuoka]

[Rohit Gupta] “There is a checkbox in the Camera RAW section to store the Red decode settings with the version. This should let you have different Red settings for each version of the grade.”

Ah, that’s awesome. Amazing how you can totally overlook something that’s right in front of your face all day long!

Thanks Rohit.

[Mel Matsuoka]

Thanks Peter!

BTW, is there any chance within this millennium that we’ll get Sparkle-based software-updates (or at least auto-checking update notifications, or even an old-school email notification) in BMD software?

It’s kind of a drag to always have to check a message board or drilling down into the BMD support pages just to find out if there’s a software update to Resolve or the Decklink drivers.

[Mel Matsuoka]

[Sascha Haber] “I am also avoiding the database for now as it has proven to be much easier to backup single projects.
“

Is it just me, or have you also found that the file-based projects both load and save much slower than the traditional database method?

I was excited about the standalone projectfiles in R9, but I found that on large projects, it takes forever to save and load, so Im still using database based projects, and setting up a keyboard maestro macro to periodically save my projects to selfcontained .drp files every so often…

[Mel Matsuoka]

Thanks for making this new std. candle!

Here’s my results:

2010 Mac Pro (2×2.4 GHz Quad-core)
24GB RAM
GUI: GTX570 (MacVidCards 2.5GB)
GPU: 2x GTX570 (MacVidCards 2.5GB) in external Cyclone 2707 chassis
Mac OS X 10.7.4
CUDA driver: 5.0.24

V01 04 blur nodes: 24 fps
V02 08 blur nodes: 24 fps
V03 16 blur nodes: 24 fps
V04 32 blur nodes: 12 fps
V05 64 blur nodes: 6 fps
V06 01 NR 2 nodes: 24 fps
V07 03 NR 2 nodes: 9 fps
V08 06 NR 2 nodes: 5 fps

[Mel Matsuoka]

For some reason, I keep getting this error when installing the update on my Mac Pro running 10.7.4 (I also get this same error when trying to install the CS6 Extension Manager update on my Macbook Pro running 10.8.1):

Adobe Premiere Pro CS6 6.0.2 Update
There was an error installing this update. Please quit and try again later. Error Code: U44M1U5

Adobe Media Encoder CS6 6.0.2 Update
There was an error installing this update. Please quit and try again later. Error Code: U44M1U5

I get the error regardless of whether I use the Adobe Applcation Manager/Updater, or I download and run the standalone updaters from the Adobe site.

And of course, I’ve done the requisite Repair Permissions and flushed system caches, but to no avail…

[Mel Matsuoka]

Late followup to this problem, but for the sake of our future children, I wanted to report that my Kernel Panic’s were being caused by a “Revised” version of the Cyclone PCIe2-426 HBA card, which connects my external Cyclone 2707 PCIe chassis to the Mac Pro.

When I originally had problems running the Cyclone chassis with a 2008 MacPro3,1, the guys at Cyclone sent me a “revised” version of the HBA card, which supposedly had improved channel-switching from the original card that came with the unit. After grasping every available straw, I decided to see what would happen if I swapped out this “revised” (and ostensibly improved) PCIe2-426 card with the original card.

This absolutely did the trick. I still get the occasional Kernel Panic once a week or so, but nowhere near the multiple, random, daily KPs that I had before.

So it turns out “new” doesnt necessarily mean “improved”!