[John Vaudin]

If you look to the left of each term you’ll see two checkboxes. One for OR and one for NOT. Tick the NOT checkbox and select “is blank” as the operator.

[John Vaudin]

One of the issues with these very long paths, as I previously mentioned, is that it is very easy to miss little differences. In your case one path has Eastman’Media and the other has Eastman_Media – so the paths aren’t the same, which means the rule, which expects Eastman_Media won’t match, which is why you got that error saying you needed a valid path mapping – because for those files there wasn’t one.

I’m afraid it’s one of those things where you have to be very precise. A single character difference in a path will break it.

[John Vaudin]

Assuming you are using the built-in web server on the default port then navigating to:

https://localhost:8080

should take you to the CatDV Server home page. There are links on there to the current Web Client and CatDV Web 2.

If you need the direct link (for example if you are using Tomcat) then it is:

https://localhost:8080/catdv-web2

[John Vaudin]

In the screenshots I can see that you are running CatDV 11, so you should have access to the FFMPEG transcoding. There is no difference in terms of licensing between 32 bit and 64 bit versions, you can use either.

Again from the screenshot I can see that CatDV is playing the proxy for the selected asset, so it has obviously found it. However I strongly recommend that you place your proxies in a compatible folder hierarchy to the original media, rather than having loads of mappings – one for each folder. It will become a nightmare to maintain.

But I’m glad to see you got it working.

[John Vaudin]

The Proxy paths need to be the identical relative to the common root defined by the path mapping.

In the screenshot the media path is

/Volumes/Wyoming/Drobo/Eastmans_Media/HUNT MEDIA/2011 HUNT MEDIA/2011_Time_Lapse/Complete_Lapses/2011_Bench_Lapses/xxxx.mov

The Proxy mapping rule is:

/Volumes/Wyoming/Drobo/Eastmans_Media/HUNT MEDIA => /Users/EHTV_iMac/Google Drive/Volumes/Wyoming Drobo/

What this means is CatDV will take media path and substitute “/Volumes/Wyoming/Drobo/Eastmans_Media/HUNT MEDIA” for “/Users/EHTV_iMac/Google Drive/Volumes/Wyoming Drobo/”

Ending up with

/Users/EHTV_iMac/Google Drive/Volumes/Wyoming Drobo/2011 HUNT MEDIA/2011_Time_Lapse/Complete_Lapses/2011_Bench_Lapses/xxxx.mov

So that is where the Proxy media must live, but you’ve put it in:

/Users/EHTV_iMac/Google Drive/Volumes/Wyoming Drobo/2011_Time_Lapse/xxx.mov

which is completely different.

The mapping defines the common root. So the paths under “/Users/EHTV_iMac/Google Drive/Volumes/Wyoming Drobo/” must be identical to the paths under “/Volumes/Wyoming/Drobo/Eastmans_Media/HUNT MEDIA”.

There is no need to move all your original media, but the proxies do need to be moved. Obviously if you use CatDV to generate them then it would put them in the right place. I would hope Adobe Media Encoder can do the same thing, but I’ve not really used it.

CatDV itself is not the ideal tool to generate proxies – it’s fine for doing small numbers, and for testing out different formats, but if you want to generate lots then CatDV Worker is right tool to use, at it will chug away in the background.

CatDV 11 and Worker 6 (currently in beta) can use FFMPEG to do the actual transcoding, rather than QuickTime, which is what CatDV 10 and Worker 5 use. FFMPEG is generally much faster than QuickTime and makes better use of multi-core CPUs. It does take a bit of fiddling to get all the settings right with FFMPEG though.

But I’m sure Media Encoder is fine as long as you can convince it to put the proxies in the right place….

[John Vaudin]

Which of the two proxy mapping rules are you expecting that asset to trigger?

The Media Path of:

/Volumes/Wyoming_Dropbo_2/Eastmans’ Media/…..

won’t match the first rule, as it starts:

/Volumes/Wyoming_Dropbo_2/Google Drive/

So that means it will fall through to the second catch-all rule, which will try and find a proxy at:

/Users/EHTV_Mac/Google Drive/VtDV/Video_Proxies/Volumes/Volumes/Wyoming_Dropbo_2/Eastmans’ Media/…./P10800009.mov

Even if you did intend it to match the catch-all rule then that double /Volumes/Volumes looks suspicious.

So I suspect the path mappings are slightly wrong. As a general point I think I’d try and move your stuff higher in the filesystem tree to avoid these massively long paths. I would also avoid special characters such as ‘ in the paths. Also if you keep your media tree and you proxy tree common at the highest level then you can reduce the number of rules.

Ideally I’d like to see something like:

/Volumes/MyVolume/Media => /Volumes/MyVolume/Proxies

as it makes it much easier to see what is going on and makes it less likely that mistakes will creep in.

-john

[John Vaudin]

Hard to tell without seeing it. Can I ask you to email support@squarebox.com please and we’ll arrange for an engineer to remote in and take a look.

[John Vaudin]

No – I’m afraid CatDV Workgroup Server does not support users or roles. Any user can connect to the server and has access to all catalogs and assets. To be able to set up distinct users and permissions you would need the Enterprise Server.

[John Vaudin]

We apologise for the delay – I’m afraid this is because of a delay in getting some of the paperwork processed that is required to sign the plug-in. It seems that with newer versions of Premiere it simply isn’t possible to install an unsigned plugin, so until we can get the paper work through we can’t release it. Sorry.

[John Vaudin]

The mismatched schema error is caused when you have a database created by one version of the server and you try and use a different version of the server to talk to it. I’m not quite sure how you ended up with a database with a newer schema than the server you were using, but the second issue – where you updated to a newer server, and then restored the database from the older server, is expected.

In that case you should have seen an “Update Database” button in the Database tab of the Control Panel. If you’d clicked that then it would have updated your existing database to the correct schema. (Or if you just click Next in the Setup Wizard it would do that automatically) You definitely didn’t need to go back to the older server version.

In general it is definitely worth using the latest version of the server that your license allows, so that you get the latest bug fixes and features.