[Will Duncan]

I’ll second this feature request.

Learning the actual editing workflow of CatDV has been the largest challenge for editors that I work with. Almost all of them import their first subclip and then ask why they don’t have handles or can’t drag out on the clip at all.

[Will Duncan]

I disabled signing on the MacOS clients and speeds went from about 180mb/s to 850mb/s over SMB3 on a 10GbE network to a 12 bay NAS unit configured in RAID6, btrfs. It was a breathe of fresh air discovering this a few weeks ago, since I’ve been battling this issue for a lot longer than most people have been writing about it publicly on the internet. There’s a lot chatter about disabling .DS_Store on network volumes for faster folder loading…

I still see speeds over 900mb/s on the same server over AFP though. For the time being, most of our client machines are still set to what has been working fine for a long time. I’m not a formally educated network engineer or systems administrator, I’ve just learned my tools well enough over the years.

Is there a major advantage of SMB3 in MacOS over AFP at this point though?

AFP has been working fine for a long time, and I haven’t burned enough hours or throughput on the servers to really see actual results over one or the other. I know AFP support is going to fade with time. But other than that, I’m not seeing a performance boost, unless that’s something I’ll see with time as the server starts to get hammered and filled with more and more complex media.

[Will Duncan]

We have over 50 Adobe CC licenses and a full crew working on a multi episode television production and everybody who is exporting multichannel audio is having the problem. I wish I could say I’ve narrowed it down to hardware or a configuration, but the reality is, it’s a bug in the software as far as I can tell.

We were aware of the audio pop problem going into production, but I never assumed 2 months down the road Adobe would still be radio silent about the problem. Customer Support instructs me to file a ticket. Filing a ticket just leads me to the Adobe forums, and the forums are just full of people explaining the same problem while customer support says to file a ticket.

For our needs, we’re exporting audio out for mastering as an OMF and bringing it back into a timeline with a baked video in 2014. Far from ideal, but it works.

If we didn’t have a ton of effects inside a complex multicamera production, exporting an XML and opening in CC 2014 does work, it’s just a little leg work to polish the timeline back up. I also lose my project organization structure, which is annoying when there are multiple hands working on a single project / production.

[Will Duncan]

We’re working on a large television production and seeing the same issue, so are a lot of people. I was aware of the audio pop export problem going into our production, but I didn’t expect Adobe to still be radio silent and not have a fix.

Depending on how complicated the edit is, exporting an XML and opening it in CC 2014 is probably your easiest solution.

For our needs, we’re exporting an OMF of the audio out for mastering and marrying it to a baked video export (no audio) in CC 2014. Far from ideal but we already have a step we have to take for audio and exporting as OMF took care of the beeps for our audio crew.

[Will Duncan]

Sorry for the confusion. I think I just want to convert the subclips (which are just metadata at this point?) to actual self contained movies in that project. And then write those to tape, without having to export, drop them back into CatDV (worker node or manual). Right now, when I export a subclip it’s outside of CatDV and I have to reimport it. It’s fine, but it’s a hassle when you’re talking about 150 subclips that have to be retagged.

[Will Duncan]

I’m on OS X 10.8.5, if that helps.

[Will Duncan]

We have multiple clients and a single worker, but I’m only seeing a way to keep one item in the queue. Are you suggesting using each client for proxies as well as the worker? or do the clients all offload to multiple workers?

[Will Duncan]

I’m running it on the Mac Pro with CS 6 and Nvidia Quadro 4000, CUDA drivers notified me of an update right away.

https://www.nvidia.com/object/macosx-cuda-5.0.45-driver.html

No issues so far. But I haven’t done any heavy lifting as of yet.

[Will Duncan]

I typically just connect them with a simple switch bought at any electronic store via ethernet and use screen sharing to access them. If you already have a wireless / wired router this is already possible.

https://mobilemeandering.com/screen-sharing-mac-osx-lion/

The only downside is that it’s often slow running high-res video off a machine you’re screen sharing into. But that depends on the network setup. If you’re wired you’re typically fine.