VERY COOL: the web app for review & approve

Question

VERY COOL: the web app for review & approve

I have downloaded the package at

http://developer.apple.com/samplecode/FinalCutServerIntegrationSample/

read the readme, which is actually a manual, and set up everything accordingly. And now I have a very cool web app for review & approve with the same look and feel as the client. This is such a great feature that I really have no clue why apple is hiding it. There are third party apps that are less cool and cost a lot and don't send comments and flag back to FCsvr as this web app does.

And the best thing: it's very easy to install.

willard

macPro, PPC Quad (2), Imac, Macbook Pro, Mac OS X (10.5.3), Final Cut Studio, Final Cut Server

Posted on Jul 2, 2008 5:12 AM

Reply

Answer 1

Jul 2, 2008 12:46 PM in response to Willard Jansen

Willard,

Thanks for the post! So far everything's going VERY smooth. I just ran into 1 issue. If you could, look at page 13 of the instructional pdf. I pulldown "Transcode Setting" in the response window and my only two options are: no "conversion" or "none".

Any ideas? I hate to go further without figuring this out.

THANKS!!!

Ryan 🙂

Reply

Answer 2

Jul 2, 2008 2:29 PM in response to ryansalazar

Ryan,

Did you install the compressor settings as explained op page 4. And more relevant to the stage where you are: in the the admin/transcode settings is the JPEG Thumbnail available? And did you ad the device Review in the preference pane as described on page 6? And did you flag the settings: No Conversion, JPEG Thumbnail, Web review - large and Web review - small?

Maybe you missed one?

good luck

Willard

Reply

Answer 3

Jul 2, 2008 4:34 PM in response to Willard Jansen

Willard,

You're right - Got it working now, thanks!

- Ryan

Reply

Answer 4

Jul 3, 2008 1:46 AM in response to ryansalazar

Good for you. Nice app right? I think the setting for Large video is a bit to heavy. I tweaked it down a little. I als found that you should not change the filename I did that and the the add_asset.rb script would crash on reading the xml file. Don't know why cause the write xml response is only passing '-t "Title"'. By the way don't forget the " " around Title, they are needed. The Title you can change though.

Now we have to figure out how we can make this work for different asset sets (different pages for different clients) and a login/password would be nice, kinda like the Leopard wiki. I'll be working on customization a bit now.

willard

Reply

Answer 5

Jul 3, 2008 9:05 AM in response to Willard Jansen

Thanks a million or the info !!

I have been sniffing around for this information for a while. Ok I have installed everything, got Ruby running, got all the transcoding and file creations running, I send to web, I can see the job in the jobs window, it creates the JPG, QT small and Large and spits out a XML, then nothing, I can see in terminal that it is rendering the assets, I can even goto the directory and see the thumbnails, QTs and XMLs, but the application @ :3000/clips doesn't show the assets. ????

Any ideas ?

Reply

Answer 6

andiron

Level 1

70 points

Jul 3, 2008 9:31 AM in response to craigrussillroy

You say you can see the thumbnails in the directory - in public/media/cache/thumbs or public/media/thumbs? The first is where FCSVR writes them to, but the latter is where Rails reads them from. The add_asset.rb script does the copy.

Is add_asset.rb runing properly? You have to look in Logs it doesn't show up in Jobs.

You can also use the Terminal to look at the database that backs the Rails site to see if records got added.

Reply

Answer 7

Jul 3, 2008 10:02 AM in response to Willard Jansen

Cheers for the prompt reply !!!!! you must be in London just about to go home or the East side of the states

Checked logs, ran fine, looked in fcsvr/public/media/.... & there is thumbs, qt in their respectable folders - weird.

how do you tap into the database via Terminal ?

Thank you in advance

Reply

Answer 8

andiron

Level 1

70 points

Jul 3, 2008 11:01 AM in response to craigrussillroy

If you are in the review directory the command is: sqlite3 db/development.sqlite3

After the 'sqlite>' prompt, type: select * from clips;

You should get one or more lines. If not, nothing actually got into the db. Type .quit to exit sqlite3.

Did you remember to reload the localhost:3000/clips page in your browser?

Reply

Answer 9

Jul 4, 2008 3:03 AM in response to Willard Jansen

Cheers for that - 1 small piece of info I forgot to mention I am on a Leopard Client - thus no sql !!!

Currently installing Server and trying it ...

Reply

Answer 10

Jul 4, 2008 9:25 AM in response to Willard Jansen

Ok reinstalled Server 10.5.4 - FCS 1.1 and still can't get it to work !!

Officially giving up ... ;-(

Reply

Answer 11

Jul 4, 2008 1:30 PM in response to craigrussillroy

Don't give up so soon..

Delete all XML files in the xmlin folder. try it again and when you see in "search all jobs" go to the administrator/log panel en double click on the upmost row (the one that inform you that the script has run). If it says cannot read XML file, the go to the xmlin folder and check if there is a new XML file. There probably is but not with the title you gave to the asset. This means that the script had problems assigning the title to the name of the XML file.

Try now uploading a new file. Don't change the filename and give a tite of something without spaces. See if it works then.

Also be aware that you set the priority probably to medium. A normal device scan would probably stop this.

willard

Message was edited by: Willard Jansen

Reply

Answer 12

Dr Greg

Level 2

450 points

Jul 5, 2008 8:56 AM in response to craigrussillroy

I've got this sample code running fine on Leopard Client - it does come with sqlite3. The trouble I had (and this might only apply to Client not Leopard Server) was updating the sqlite3-ruby gem: it would refuse to compile.

That's because Leopard's Xcode Tools need to be installed to compile the gem. Once they were installed the "sudo gem update sqlite3-ruby" command worked just fine.

Greg

Reply

Answer 13

Jul 5, 2008 2:37 PM in response to Dr Greg

You are right. I am sorry I didn't mention XCode. I probably assumed it to be installed. Does everything else work OK for you?

Willard

Reply

Answer 14

Jul 7, 2008 1:24 AM in response to Willard Jansen

WOHOOOO!!!!

The old Xcode in the hat trick ...

Should of thought of the reason the sqlite wouldn't build ...

Cheers for all your help !

Reply

Answer 15

Jul 7, 2008 4:12 AM in response to craigrussillroy

Be aware that this is a non-supported development release. But everything seems to work perfect. When running script/server mongrel starts up in the development environment which slows things down because it compiles every page on load. but in environments.rb you can force mongrel to start in the production mode, by un-commenting one specific line (it is explained in the file). Mongrel is the rails server that runs the application. Running it in production mode makes quicker.

The normal command for starting mongrel in the production environment ("script/server -e production") starts mongrel in the production environment alright, but the application doesn't work. Does anybody now why??

willard

Reply