Bynder vs. Perforce P4

We have numerous renderings for some of our properties that are constantly being updated. It was hard to keep track of the most current rendering since it lived in multiple locations with various employees. Creating a central location where we can regularly update the renderings without having to add a new file and re-upload solved the issue of questioning whether the rendering you were looking at was correct.

Incentivized

For large-scale codebases with fixed and regular releases that do not follow a continuous delivery paradigm, Perforce is certainly well suited. In projects that are small and distinctly separated from other discrete (though potentially dependent) units, the benefits of the Perforce tool may not be as clear of a victor over other systems.

Incentivized

• User-friendly interface, clean and easy to navigate - this has helped with adoption and training so that staff feel empowered to use the portal.
• Completely customizable filters - particularly helpful for locating specific photos quickly.
• Storage - safe and secure web based storage, frees up tons of space on our org Google drive and server.

Incentivized

• Merge algorithm is smart and utilizing the visual interface to do merges makes them easier to digest.
• Easy to set up on multiple platforms and architectures and is well supported on all of them.
• Visual interface has many tools and customization options that help to optimize and personalize workflow.

Incentivized

• The search functionality sometimes is challenging
• Many reminders about cookies - more than normal in the US at this time (due to EU compliance) - can be frustrating and confusing for our end users as not all US platforms have this

Incentivized

• I was having a hard time learning it. Even if you are an experienced developer, there is some learning curve.
• Can be slow when working with large data sets at once.
• When working on multiple workspaces on the same machine, Perforce can make it difficult not to mess up the code.

We have a need to consolidate into a single package, and have such a large variety of technical proficiency among our users that Perforce seems less suitable. Many would like to remain using it, however, even those who use Perforce are the minority, and are often limited to our development teams.

Incentivized

It is incredibly user-friendly and easy to navigate. Once you poke around, you intuitively learn how to use the platform. Our company provided training sessions for all employees during our official roll-out, and everyone seemed to have a good grasp on how to navigate this platform. We have yet to hear about an employee having difficulty using Bynder, which is a big win

Incentivized

With Perforce Helix, you can use it via the command line, via P4V, or any of the other APIs included with the product. It is extremely easy for new users to get up and running. Users of Perforce Helix only have to pull in the files of interest to them. Also, Perforce is very easy to script and integrate into your CI/CD pipeline. Streams allows you to have pinpoint control of your workflow, and P4Search is the absolute best--I wish Perforce (the company) would talk more about this. It is absolutely fabulous!

Incentivized

In our large environment, Perforce is rarely "down". We have regular maintenance windows and from time to time Perforce can feel a little slow, but its always available. Tech support has always worked with our engineers and IT department to make sure that any real performance or stability issues are addressed quickly.

Incentivized

When we were getting ready to switch vendors, WebDAM wasn't very responsive to my questions or my needs. They also sent me all the files on an external drive that was formatted for Mac and didn't even think to verify whether I had a PC (which I did) so the external drive was useless and I had to wait another week to get the updated external drive that was formatted for a PC that I could then use.

Incentivized

I had two representatives from Perforce contact me after downloading it but never responded when I had questions. I also had a difficult time finding good training material for getting started. There is a lot of available support material when running into issues, though, because of how many large companies use it.

Incentivized

This rating is related to setting up an environment from an existing Perforce repository. Initial setup of Perforce as the repository for the company was done by a separate team long prior to my inception.

Incentivized

Once the issue was identified we looked at a damn lot of DAMs. Bynder, Media Valet, Webdam, Canto, Cumulus... I can't even remember them all. But that was the problem. There were too many. When one of our team evaluated Bynder he reported back vis a vis the legacy tools of Box/DropBox/Evernote... all of which had their adherents within our team and NONE of which came close to matching Bynder. So, the decision really became "do we switch now to Bynder, which everyone accepts, or do we spend a year thoroughly testing every other tool until we've broken up again into rival camps?" It was easy. If and when Bynder fails we may look again. But everything's going great now, so why open this can of worms?

Incentivized

New users of Perforce Helix can be up and running in less than thirty minutes. It is easy to use, but also very powerful. Bitbucket is slow, prone to outages, and (for large teams) requires a team of dedicated administrators. I've had request for information from Bitbucket that requires hours to pull together that would take me less than 30 seconds in Perforce Helix. Large file storage in Bitbucket is clunky and requires you to jump through too many hoops. It's not even something you have to think about with Perforce Helix, as you are only limited by your OS. Perforce Helix is very easy to use even for non-developers. I wouldn't dare ask a non-developer to store their documentation in Bitbucket.

Incentivized

• Bynder has saved our creative and Marketing departments hours of time overall by minimizing the amount of time we are searching for asset requests and empowering employees to find what they need themselves.
• Bynder has given us a platform to share lifestyle and product imagery that costs several thousand dollars overall; whereas before it was hard to share those assets in a way that they were utilized to their full potential. Now we don't have to wonder if we're wasting money on styled imagery or whether people are using it.
• Overall the peace of mind Bynder gives us in terms of employees only using approved assets is pretty priceless.

Incentivized

• Locking assets make us have no merge problems which are harder to manage on other versions control without locking
• Almost no need to give support to artists or non-tech folks because the operations are very straightforward
• There's no way to do interim checkins without going to the process of creating a stream

Incentivized