Best practice for exporting a dps folio so a third party can work on it?

Hi All,
Keen for some thoughts on the best practice for exporting a dps folio, indd files, links and all, so a third party can carry on the work. Is their a better alternative to packaging each individual indd file and sharing the folio through adobe?
I know there have been similar questions here in the past, but the last (that i've found) was updated mid 2011 and I was wondering if their have been any improvements to this seemingly backwards workflow since then.
Thanks in advance!

Nothing better than packaging them and using Dropbox to share. I caution you
on one thing as far as packaging:
http://indesignsecrets.com/file-packaging-feature-can-cause-problems-in-dps-
workflows.php

Similar Messages

Best practice for exporting from iMovie '08 to iDVD

I am looking to find out what is the best practice for exporting from iMovie '08 to iDVD. I have read the other postings that give the basic howto (export to Media Browser then select the video in iDVD). However, my question is a little more technical. I have 1080i HD projects. I am interested in burning them to DVD in the best possible quality. What setting should I be using when I publish to Media Browser?
I am wondering about quality loss due to more than one conversion/compression. I suspect that when I export to the Media Browser then this is occurring. If I am not mistaken iMovie is using something like H.264 for this. Then, when I run iDVD I suspect it will it do another conversion/compression, I think to get to MPEG2. Not only could this result in a loss of quality but also it will take extra time. I am interested to know what others think about this.
Finally, I am looking to create DVDs for a lot of video. I am wondering if there are any USB or firewire hardware devices out there that could speed up the compression. I use the Elgato Turbo.264 when I want to encode to H.264 but I wonder if there is something similar for DVD creation.
Thanks in advance.

the standards for videoDVD are 720x480, and usually mpeg2 encoded..
so, your HiDef project HAS to be 'downsampled' somehow..
I would Export with Qucktime/apple intermediate => which is the 'format' your project is allready, and you avoid any useless 'inbetween encoding'..
iDVD will 'swallow' this huge export file - don't mind: iDVD cares for length, not size.
iDVD will then convert into DVD-standards..
you can 'raise' quality, by using projects <60min - this sets iDVD automatically to highest technical possible bitrate
hint: judge pic quality on a DVDplayer + TV.. not on your computer (DVDs are meant for TVdelivery)

Best Practices for Export

I have recently begun working with a few AIC-encoded home movie files in FCPX. My goal is to compress them using h.264 for viewing on computer screens. I had a few questions about the best practices for exporting these files, as I haven't worked with editing software in quite some time.
1) Is it always recommended that I encode my video in the same resolution as its source? For example, some of my video was shot at 1440x1080, which I can only assume is anamorphic. I originally tried to export at 1920x1080 but then changed my mind as I assumed the 1440x1080 would just stretch naturally. Does this sound right?
2) FCPX is telling me that a few of my files are in 1080i. I'd like to encode them in 1080p as it tends to look better on computer screens. In FCPX, is it as simple as dragging my interlaced footage into a progressive timline and then exporting? I've heard about checking the "de-interlace" box under clip settings and then doubling the framerate but that seemed to make my video look worse.
3) I've heard that it might be better practice to export my projects as master files and then encode h.264 in Compressor. Is there any truth to this? Might it be better for the interlaced to progressive conversion as well?
Any assistance is greatly appreciated.

1) yes. 1440 will display ax 1920.
2) put everything in a 1080p project.
3) Compressor will give you more options for control. The h264 from FCP is a very high data rate and makes large files.

Best Practices for Exporting Files??

I'm new to Premiere (coming from FCP). I used Premiere months ago to compress some ProRes files to h.264 files for the web. I sent the files through Media Encoder and everything seemed fine. However, I realized after several weeks that the audio in all of the files was a few frames out of sync. Having not been a Premiere user at the time I did not do much research and decided to just use MPEG Streamclip from then on.
Now that I'm learning how to use Premiere, I looked up the issue on the forums and found that many people have had similar issues with the audio being out of sync after exporting. However, there are tons of different scenerios in which it seems to be occuring. The one common variable that I've noticed (among many of the threads, but not all) is that many of the people are exporting to a Quicktime format.
While I don't remember all the details of my export and sequence settings from my issue months ago (so I don't want to address that specific case), I am curious as to what are some "Best Practices" when exporting from Premiere Pro? Is there any advantage/disadvantage to use AME rather than exporting directly from Premiere Pro? In general, I will just be exporting as H.264 files for the web, MPEG-2 for DVD, and ProRes 422 for After Effects (or sometimes to bring into MPEG Streamclip).
I shoot almost entirely in AVCHD, and usually at 1080p 30fps. I'm running CS5 on a Macbook Pro 15" 2.0 Quad Core i7 8GB RAM.
While the question may seem broad, my main concern that I want to avoid is having the audio out of sync. But also I just want to know of any important details to keep in mind to prevent other issues.
Thanks,
Mike

> I'm running CS5...
What specific version? We're up to 5.0.4 now.
There have been bug fixes for audio/video synch in the updates. One of the fixes was for a bug in the conforming of audio and indexing of MPEG files, so you need to delete your media cache files and let Premiere Pro create new ones for this fix to take effect.

Best practice for exporting a .mov file for YouTube

I am using FCPX 10.0.9 with a MacBook Pro. We are needing to upload relatively small-size high school football videos as .mov files to YouTube for my newspaper. I have been choosing the Export File option with the setting set to h.264, exporting the file to the desktop and then uploading that .mov file to YouTube. (I do not have Compressor installed on this Mac.) The other night the first of three files done like this uploaded fine, but the next two just kept processing and processing at YouTube and never finished. The following morning the files processed fine. Any thoughts about why ths might be happening?
And would it be better to export in another file format --.mp4 files -- instead that might cause less of a problem and which of the export options would be best?
Thanks,
Douglas

douglas i wrote:
Am I correctly uploading a .mov file to YouTube by using the Export File command with the export setting set to .h264 then if I wish a reasonable size file for upload?
Sure. There are many ways to get videos to YT and yours is a reasonable approach.
"Reasonable size" should be thought of in terms of upload time. Again, YT will re-compress whatever you give it. So depending on how quickly you need to get it up on the Web, it's better to upload files that have more information than less information. (To that end, some folks upload very large Pro Res files; they also have a lot of patience.)
Just to let you know, the majority of FCPX users follow one of two workflows:
1) Share>You Tube option and have FCP handle the uploading;
2) Export as a Pro Res Master File; bring the master file into Compressor and apply the user's custom settings; upload using YT's uploader.
FWIW, I prefer the second workflow.
Russ

Best practice for exporting an 8-channel Quicktime's audio into stereo and 5.1 files for Encore BD?

The subject pretty much says it all. A client has given me a Quicktimde ProResHQ with 8 channels of audio.
I understand how to export the stereo channels (1 and 2) from Premiere but how are channels 3-8 normally handled for proper 5.1 surround authoring in Encore?
Thanks for any advice - I was unable to find specifics when searching previous posts.

how are channels 3-8 normally handled for proper 5.1 surround authoring in Encore?
You must create the 5.1 outside Encore. Note that from Premiere it requires the optional Surcode.
Encore essentially passes the 5.1 through to the build process; you do not get preview of the 5.1 audio.

Best practices for exporting for digital signage?

I am exporting video clips to be displayed in a PC-based digital signage system. My video was shot in 1080i60, and I imported and edited the footage using HDV sequence settings. My final export size needs to be 1920 x 1080.
I have tried a couple of export strategies (export using Quicktime conversion) and just haven't been happy with how the video clips look on the PC system -- way too much interlacing. When I realized that the HDV codec is not cross platform, I started taking the additional step of opening and re-saving the .mov file in Quicktime. Now I'm fiddling around with Compressor, just to add more complications. I have tried so many different settings and codecs that I have completely lost my way! Can anyone recommend a workflow for this situation?
I am using FCP6 and Compressor 3 on an iMac OS 10.5.8.
Thanks for any help.

Terry Burton1 wrote:
I still see interlacing on the H.264 export that I don't see when I export the sequence as HDV. Of course, I can't get the HDV export to play on a PC.
I'm trying to read between all of the lines here...I'm going to assume there is a fundamental lack of understanding about what interlacing is and how you're going to remove it. The display either handles interlaced or progressive video files; one or the other. Let's assume it's progressive only. Since you shot interlaced, you must decide how you're going to remove the interlacing; you either throw away one filed or your combine them. If you combine them, you will see combed edges on anything that moves horizontally because every other line of pixels was captured 1/60th of a second later in time. If you throw away one field, you might as well have shot 720.
Where do you want o make this compromise?
bogiesan

Best practice for exporting the same disk to multiple guests?

I've got a T4-4 with two service domains. Each service domain has access to the same pool of SAN disks.
primary service domain has vds primary-vds0
secondary service domain has vds secondary-vds0
So far I've sucessfully built a single backend service for each SAN disk on each service domain and used the MP group operation to enable multipathing, i.e.
ldm add-vds primary-vds0_a primary
ldm add-vds secondary-vds0 secondary
ldm add-vdsdev mpgroup=target1 /dev/dsk/c0t6target1 target1@primary-vds0
ldm add-vdsdev mpgroup=target1 /dev/dsk/c0t6target1 target1@secondary-vds0
ldm add-vdisk id=0 bootdisk target1@primary-vds0 guest_a
Now, I have database datafile LUNS that I need to present to two guests at once since they're using Veritas clustering. As I understand it, what I have to present to each guest is a unique volume (volume@vds) export, and I can do it one of two ways:
Build mutiple exports of the same disk on the same vds:
ldm add-vds primary-vds0_a primary
ldm add-vds secondary-vds0 secondary
ldm add-vdsdev mpgroup=db1a /dev/dsk/c0c6target5 db1_server_a@primary-vds0
ldm add-vdsdev mpgroup=db1a /dev/dsk/c0c6target5 db1_server_a@secondary-vds0
ldm add-vdsdev mpgroup=db1b /dev/dsk/c0c6target5 db1_server_b@primary-vds0
ldm add-vdsdev mpgroup=db1b /dev/dsk/c0c6target5 db1_server_b@secondary-vds0
ldm add-vdisk id=6 database_disk db1_server_a@primary-vds0 guest_a
ldm add-vdisk id=6 database_disk db1_server_b@primary-vds0 guest_b
Build a separate vds for each guest domain, and then add the vdsdevs to each vds:
ldm add-vds primary-vds-server_a primary
ldm add-vds primary-vds-server_b primary
ldm add-vds secondary-vds-server_a secondary
ldm add-vds secondary-vds-server_b secondary
ldm add-vdsdev mpgroup=db1a /dev/dsk/c0c6target5 db_disk@primary-vds-server_a
ldm add-vdsdev mpgroup=db1a /dev/dsk/c0c6target5 db_disk@secondary-vds-server_a
ldm add-vdsdev mpgroup=db1b /dev/dsk/c0c6target5 db_disk@primary-vds-server_b
ldm add-vdsdev mpgroup=db1b /dev/dsk/c0c6target5 db_disk@secondary-vds-server_b
ldm add-vdisk id=6 database_disk db_disk@primary-vds-server_a guest_a
ldm add-vdisk id=6 database_disk db_disk@primary-vds-server_b guest_b
The end result is the same, but is there any advantage (performance, configuration management, whatever) to doing it one way versus the other?
Thanks!
Tim Metzinger

the standards for videoDVD are 720x480, and usually mpeg2 encoded..
so, your HiDef project HAS to be 'downsampled' somehow..
I would Export with Qucktime/apple intermediate => which is the 'format' your project is allready, and you avoid any useless 'inbetween encoding'..
iDVD will 'swallow' this huge export file - don't mind: iDVD cares for length, not size.
iDVD will then convert into DVD-standards..
you can 'raise' quality, by using projects <60min - this sets iDVD automatically to highest technical possible bitrate
hint: judge pic quality on a DVDplayer + TV.. not on your computer (DVDs are meant for TVdelivery)

Anyone know the best resoluton for images in DPS folios?

Do I recall hearing somewhere that they are automatically sized appropriately so as to avoid contributing to unnecessarily large folios?
Thanks in advance.

Hello,
I believe PDF-compressed folios will resample placed bitmap images to 108 dpi -- sort of a compromise resolution between standard def and high def.
Pass-through overlays will not resample images, however, so those would need to be compressed to whatever degree you feel is appropriate.
Best,
Jim

Best Practices for Exporting with Bug overlay

I'm trying to optimize a bug graphic so as to speed up exports from FCP. I'm working at XDCam 1080i/60 (timeline + footage) and have experimented with different types of bugs, all PSD files. Here's what I've found exporting a 10 min. segment:
No bug = 3 min. export
96x96 pixel PSD of the bug positioned in the corner (semi-transparent)= 15 min. export
1920x1080 PSD with the bug pre-positioned in corner (semi-transparent) = 15 min.
1920x1080 PSD with the bug pre-positioned in corner (opaque) = 15 min.
It seems such a simple overlay shouldn't demand so much reprocessing and take so long. Any ideas how to make this more efficient? I don't want to add a bug via Compressor as I want to retain control of what moments in the program the bug displays.

Render to full before you export and all the times will match. The bug image size does not effect the render time as each frame has to be compressed separately. The only time it will make a difference is if you're scaling and positioning the bug to fit the screen, but if you position and size it correctly in Photoshop it will speed by the render time. XDCAM BTW is a dog to process because of its GOP structure.

Best Practice for setting bind variable when application loads

I am using JDeveloper 11.1.2.3.
When my application loads, the first unbounded page has a table populated by a named query.
I would like to set the parameter used by the named query when the page loads, to populate the initial data that is displayed.
What is the best practice for a solution to this issue?

user6003393 wrote:
I am using JDeveloper 11.1.2.3.
When my application loads, the first unbounded page has a table populated by a named query.
I would like to set the parameter used by the named query when the page loads, to populate the initial data that is displayed.
What is the best practice for a solution to this issue?Hi,
You can set the bind variable on VO by overriding prepareSession() method in Application Module check this http://docs.oracle.com/cd/E37975_01/web.111240/e16182/bcservices.htm#sthref357
Setting bind variable on runtime http://docs.oracle.com/cd/E37975_01/web.111240/e16182/bcquerying.htm#CHDECJHD
Zeeshan

Best practice for heirachical data

First off, I have to say that JMX in Java 6 is terrific stuff. Bundling jconsole in with Java has made JMX adoption so much easier for us.
Now, to my question. We have read-only hierarchical data (think a DOM tree) that we would like to publish via JMX. What is the best practice? We see two possibilities:
1. Publish each node of the tree with it's own object name and type. This will allow jconsole to display the information in the tree control.
2. Publish just the root of the tree with an object name and type and then use CompositeType to describe the nodes of the tree. This means you look at the tree in the "Attribute Value" panel of jconsole.
Is there any best practices for such data? We have implemented #2 and it works but we are wondering if long term this might lead to unforeseen consequences.
Thanks in advance.
--Marty

Path,
I did go with #1 and it worked out great. Every node in our tree is an ObjectName node. Works very well for us.
--Marty

Best practices for deploying EMGrid Control

Can i use one db for OEM & RMAN repository? Looking for Best practices for deploying EMGrid Control in our environment, I have experience working with EMGrid control it was very slow , how to make it fast ? Like i enjoy the speed of EMDBControl....

DBA2008 wrote:
Is this good idea to put RPM recovery catalog & OID schema in OEM Repository DB? I am thinking just to consolidate all these schema's in one db.Unless you are really starved for resources, I would not recommend storing the OID and OEM repositories in the same database. Both of these repositories support different products, and you risk creating unnecessary dependencies when patching or upgrading. As a completely fictitious example, what if your OID installation has a critical issue that requires a repository database upgrade to version 10.2.0.6, and the Grid Control repository database is only certified for version 10.2.0.5?
Regards,
John P.
http://only4left.jpiwowar.com

Best practices for image compression in dps

Hi! I have been reading up on best practices for image compression in dps, and I have read that the source assets of panoramas, image sequences, pan and zoom images, and audio skins are not resampled on upload. So you therefore need to resize them and compress them before dropping them into your article, because dps doesn't do it for you. Okay can do!
So then Im also reading that the source assets of slideshows, scrollable frames, and buttons ARE resampled as PNG images. Does this mean that DPS will compress them for you when you build the article? So does that mean I shouldn't bother going to the trouble of resizing these images at all? I can just pop in the 15mb 300dpi files used in the print magazine and dps will compress them upon building the article - and this will have no affect on file size?
And this is also the case with static background images?
Thanks for your help!

All images are automatically resampled based on the size of the folio you make. You can drop in whatever resolution image you want, it doesn't matter.
Neil

Latest best practice for folio renditions

Hi!
I released my first folio last year (http://www.psaltiki.org/journal/) and added renditions.
With the release of CS6 I can see in inDesign how there seem to be some special tools for preparing documents in multiple formats.
My question is if there is some documentation out explaining the best practice for preparing and uploading redintions of a folio that I could review before beginning the layout of my second folio?
Thanks!
kt

http://tv.adobe.com/watch/learn-indesign-cs6/working-with-alternate-layouts/?go=13244
http://www.adobe.com/aboutadobe/pressroom/pressmaterials/pdfs/ID_CS6_WN_20120320.pdf
http://help.adobe.com/en_US/digitalpubsuite/using/WS4cb2576c7954973c18306752136e6c6200d-80 00.html

Best practice for exporting a dps folio so a third party can work on it?

Similar Messages

Maybe you are looking for