[Barrie Williams]

Same here
2 minute fix…
Preferences, select no panel, close resolve

Reopen resolve. Preferences , choose your panel, close resolve

Reopen resolve

All is working again
Barrie

[Barrie Williams]

Site is swamped with downloads I guess

I found it slow today but managed to download ok.

Barrie

[Barrie Williams]

Great improvement here, thanks guys.

Especially like SDi burn ins. Have been asking Quantel for this on our eQ for the last FIVE years, and we still don’t have it!!!!

Barrie

[Barrie Williams]

Thanks Peter,

i agree with Sacha and Marcus.

And this is not new, this is pretty standard feature in this industry…

back 15 years ago on our old DPS system, not only could we add marks during playback (like fcp does now) but we could even add marks to clips DURING INGEST and batch capture.

So to sum up this thread, i believe the flag implementation could be improved by
1- improving the two ambiguous “mark” labels,

2- allowing some sort of flag, marker or tag to be added during playback

3- enabling a special timecode-based marker, so when the client says “mark that please”, as they have done in this industry for decades, we don’t have to grab a pen and paper.

The very best implementation of markers is Digidesign ProTools, please take a look at it. You can add a marker, flag is, color it, anmnotate it, all without interrupting playback. Clients do expect this.

thank you for listening
Barrie

[Barrie Williams]

Thanks Dwaine,

that is a partial workaround which i did not know about, so thank you for that.

Partial, becuase if i subsequently split a clip, perhaps because scene detect missed it, both clips are now flagged. If i try to add a new flag to the new clip, both clips now get flagged.

So i think currently flags may be trying to be too ‘helpful’, when i think most users are only asking for an electronic version of a colored thumb tack.

Thank you for the fast reply. For now the Markers work exactly as we need, albeit a bit small.

I have programmed “add marker” to a hardware button, because we need it very often.

thanks again

Barrie

[Barrie Williams]

Hello Dwaine,

can you please explain why there are 9 different flags when the first flag marks ALL my clips? what can i do with the other 8 flags?

i do hope i am doing something wrong here, because i can see the flags being a really useful feature if they worked on a clip basis.
;-/

Barrie

[Barrie Williams]

if flag worked on a clip by clip basis, that would be a GREAT feature.

Unfortunately i often work on single media and scene detect, so each clip on my Resolve timeline comes from somewhere in the SAME Quicktime…

… and for some unexplicable reason, in Resolve adding a flag to ONE CLIP flags EVERY CLIP from that media file, rendering the whole FLAG feature useless for us. It always flags all the clips!!

I do hope that this is not as it is designed to work.

If it is, we need another option to add a USER FLAG flag, rather than a media linked flag.

You can use Markers, but they are very difficult to see compared to the flag icon.

Barrie

[Barrie Williams]

One thing we may not be factoring in is the 10.7.5 OSX BUG.

when i updated i carefully read the config requirements, and updated to 10.7.5, which was a BIG mistake, because the Spotlight indexing was severely broken on that build, meaning that if your system started indexing, it would NEVER stop, using precious CPU resources for nothing.

I reported this to Apple who promised a quick fix.

THIS MORNING Oct 5th they released a 10.7.5 PATCH which has fixed the problem, so now i hope my system will be more responsive.

Barrie
pixelfantastic

[Barrie Williams]

i held off while it was officially in beta, and only upgraded after it was declared a ‘release’.

It’s looking very promising, but in reality it’s still beta code for 3D use.

Barrie

[Barrie Williams]

Our little fix only worked temporarily.

As of today (28 sept 2012) there are a few intermittent bugs in v9.0.1, especially in 3D stereoscopic.

Stuttering playback, playback changing 3D modes between pause and playback, Auto stereo color balance makes one eye pure white. Auto Color balance makes image less matched in upper luminance areas. CPU going sky high and causing the app to stop responding for quarter of a minute at a time. Audio waveforms hardly visible, yet consuming heavy resources. etc.

I like the new features, but v9 is not quite ready to be released yet.

We too are rolling back to v8 for a while.

Barrie