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

Snow Leopard Testing Report Thread

XD

XD

Cameron,

XDCam does not work at all ?
XDCam 422 and XDCam EX ?
Sony Transfer does not work or see clips?
XDCam L&T plug-in does not function?
QT Wrapped XDCam files cannot be viewed?
All of the above?

Thanks for extra details.
 
Boy do I ever love my Macs! :001_tt1: Snow Leopard is running great on both of my MacBook Pro 17's.

Really fast...it only takes 2 1/2 seconds to turn off my computer.

Everything is much more responsive than ever before.

I highly suggest all Mac owners to upgrade ASAP.
:attention9ha:
 
Joseph,

The Intel Mac owners can really take advantages of not having unnecessary codes, boot faster and all. This is a big step for us to get into 64-bit environment.

MOTU had posted updates for all of their software (except one) and hardware drivers on the same day. So there might be some incompatibilities with software that doesn't get updated. I'm doing everything today on SL.
 
I was testing MXO with its beta driver today with LP and FCS3.

Aside from R3D support, I took the colorbar from the effect tab in FCP7, place it on ProRes422HQ timeline. The scopes on FCP7 shows identical readings on my TVLogic XVM245W's vector scope and the waveform. Sent it to Color 1.5, set the project to match to ProRes422HQ and turn off the Broadcast safe option, the scopes on the Color 1.5 and the scopes on XVM245W look identical. Now we have consistent gamma and color balance on FCP and Color. Finally, render out from Color 1.5, sent it to FCP, the rendered clip looks identical in the scope.

Only glitch I see is in Color, I see thicker line towards 75% green signal where the original doesn't have, then when it's rendered, the same glitch shows in the file when you place that on FCP timeline. I assume something happening in Color's interpretation. This also happened with KONA LHe, so it's not depending on the hardware, it seems to be Color software issue.

This also happens on uncompressed 422.
 
Hi Kaku,
incredible you always the first with reports!!

About the gamma:

re you saying that now everything in Snow Leopard is 2.2 Gamma ?
Even the desktop?
And there is o differences between play a clip on QT or FPC or color?(like Prores i mean?)
Didi you try cineform?in QT e FCP?

Thanks a lot!!!

G
 
jhodges said:
Correct me if I'm wrong but isn't the only thing holding Adobe back from bringing the creative suite into 64-bit the support of the codecs (mainly quicktime). With quicktime being rewritten with this version of OS X, does it mean that we are getting all our CS5 apps in 64-Bit?
Click to expand...

I was under the impression that the main reason we mac users weren't getting 64-bit anytime soon was that Apple kinda came out of nowhere and screwed Adobe with the whole "We're not going to support 64-bit Carbon anymore" thing.
 
jhodges said:
Correct me if I'm wrong but isn't the only thing holding Adobe back from bringing the creative suite into 64-bit the support of the codecs (mainly quicktime). With quicktime being rewritten with this version of OS X, does it mean that we are getting all our CS5 apps in 64-Bit?
Click to expand...
somebody is paying attention ....
 
Gabriele Turchi said:
Hi Kaku,
incredible you always the first with reports!!

About the gamma:

re you saying that now everything in Snow Leopard is 2.2 Gamma ?
Even the desktop?
And there is o differences between play a clip on QT or FPC or color?(like Prores i mean?)
Didi you try cineform?in QT e FCP?

Thanks a lot!!!

G
Click to expand...

Gabriele,

In the Monitor preference, if you try to adjust the color profile and the at the gamma selection it does say gamma 2.2 (standard). The system gamma is 2.2 (but I wonder why not 2.22).
 
Ben Brainerd said:
I was under the impression that the main reason we mac users weren't getting 64-bit anytime soon was that Apple kinda came out of nowhere and screwed Adobe with the whole "We're not going to support 64-bit Carbon anymore" thing.
Click to expand...

Carbon was 32-bit only. Apple announced pre-Leopard they were no longer developing Carbon APIs, which basically forced Adobe to re-write all their software as Cocoa (not a small task) before Apple totally drops Carbon support in a future operating system. But it needs to be Cocoa to be 64-bit anyway.

As I understand it Carbon was only adopted in order to make the transition to OSX easier for developers who had been writing for previous OS versions. It was fairly inevitable that they would stop supporting it at some point - it hardly "came out of nowhere".
 
Kaku Ito said:
I worked entire Saturday but never had a crash yet.
Click to expand...

The crashes both happen when installing various Plug ins for CS4, FCS3 is just fine, also it would not load the LR2 installation??

It has been working well so far, will contact Adobe on Monday to see what up with LR2.

ciao
 
Ah, to me CS4 always crash when it gets associated with thirdparty video hardware presets or selections.
 
Compressor 3.5 (FCS) quits unexpectedly at startup under Snow Leopard... After a clean install of Snow Leopard and installing the new Final Cut Studio, all apps work fine except Compressor 3.5. It just won't boot. I just get a "Compressor quit unexpectedly" message.

Anybody else seeing this and is there a fix?
 
I did a clean install of SL today (first leopard then SL), the gamma seems really consistent between applications. Color 1.5 works fine and prores 4 is really a good codec for me. I did a test on a mac pro Nehalem dual 8-Core, 3 drives of 1 gb each internal raid 0. Clipfinder transcoded 4k R3D files to prores proxy 1k high 720p faster then realtime and to prores 4 at 10 fps. In Color I had real time playback with 2k prores 4 without video output and 20 fps with video output to MXO. And now my question Kaku, what mxo output do you choose in Color? I use uncompressed 23.98 720p and the mxo feeds an apple cinema display and a jvc SD broadcast monitor and it works quite fine but it works quite bad with uncompressed 1080p. Any suggestion?
I remember when all of us started these threads on the forum about the gamma issue, fcp workflow and so on and after a year it seems the things are getting really better.:smile5:
 
Luca Immesi said:
And now my question Kaku, what mxo output do you choose in Color? I use uncompressed 23.98 720p and the mxo feeds an apple cinema display and a jvc SD broadcast monitor and it works quite fine but it works quite bad with uncompressed 1080p. Any suggestion?
I remember when all of us started these threads on the forum about the gamma issue, fcp workflow and so on and after a year it seems the things are getting really better.:smile5:
Click to expand...

Luca, I'd say that's pretty much the case, if you want to get the best frame rate with most resolution during the playback, 1280 x 720 output is probably the highest. At 1920 x 1080 output, setting the playback proxy as Half Resolution provides you pretty smooth playback and full resolution when you stop, so I usually do this when I work on Color.
 
You must log in or register to reply here.
Back
Top