-
back again, guess why
-
[Joe Moya] “I didn’t know that CS4 used 64bit… I looked at the specs and don’t see any mention of it being a 64bit application.”
It’s not a 64 bit app…but running a 64 bit OS will give PPro access to a full 4 GB instead of what’s left over after the OS and all the background Adobe apps take their portion of even the 3.5 GB of RAM you can access with the hack… (Boxx and other reputable workstation builders do not recommend this practice for stability reasons, so I stick to the 2.5 GB available method on my XP systems).
A fast processor will run software fast…but more RAM will help it stabilize as paging that data on and off of a drive is simply not as easy as having it all in RAM.
On the HDV renders…again, I don’t even know if I have any HDV data around here to try, so I can’t troubleshot that.
As fast as your system may be, there are a lot of possible incompatibility issues in there…the memory hack, all the other components we’ve mentioned. I know it sounds like a cop-out, but I haven’t seen loads of this sort of feedback for PPro users working with HDV (to be fair, I have heard from some others however), so somebody must be making it work…somewhere.
TimK,
Director, Consultant
Kolb Productions, -
Where do your M2T files come from?
-
Canon HV30
-
[Joe Moya] “Canon HV30”
The Canon HV30 is HDV on miniDV tape, if captured into Ppro it usually is a .mpeg file, if you are have .M2T you captured with a 3rd party software/hardware which maynot be totally compatible with Ppro, some M2T files can be proprietary, Ppro will recognize M2T files from Sony HD Harddisk cams, no other type listed, check your Ppro help file for allowable file types, other types can be iffy.
FYI, Below is a PDF describing 64bit use with CS4
https://www.adobe.com/products/creativesuite/production/pdfs/cs4_production_premium_64bit_wp.pdf -
Jason,
I’m an Adobe employee and curious to learn exactly which news group you are with and to learn some of the specifics of your current system that is giving you problems. Tim’s first response is valid (I especially find the bits about Avid/Apple system requirements vs Adobe requirements to ring true) but it would be good to get a handle on what you’re actually using.
As for news organizations, you might check out these semi-recent press releases.
Hearst (20% of North America with 25+ stations)
https://www.adobe.com/aboutadobe/pressroom/pressreleases/200909/HearstTelevisionAdoptsAdobeVideoProductionSolutions.htmlTurner’s News organization
https://www.adobe.com/aboutadobe/pressroom/pressreleases/200909/AdobeandTurnerBroadcastingSystemInc.ExpandAlliance.html -
If I could add my two cents worth, I think CS4 is the most unstable, crash-ridden NLE app I have ever used. I switched from discreet edit (one of the best NLE’s ever made) to Premiere in 2003 and even being involved with the beta team for many years, I’ve never been able to understand why it crashes and hangs so damn much. Maybe the DV guys haven’t seen this, but I saw it enough times working with HD-SDI uncompressed to switch the Final Cut Pro a couple of weeks ago.
That in itself has been problematic from a re-learning point of view, but at least I don’t get the unstability that makes Premiere unworkable (for me) in a real world situation. I’ve got CS4 on my brand new 8-core Mac and it still crashes and siezes up on that box! (I was a Window CS4 user before)
There are a lot of great thinbg that Premiere has over FCP, starting with the title generator. It has such potential. But geez, I’d run out of patience…
Peter Corbett
Powerhouse Productions
http://www.php.com.au -
I seem to have two problems with your post…
1) according to Adobe… they fully support the HV30 without mention of requiring the capture with Adobe or conversion of file format to mpeg.
2) according to Adobe… they support the import of the M2T file format.**
Why would Adobe convert the native M2T file format of Cannon to mpeg if it claims to be able to work with the M2T file format? Unless, Adobe knows it actually has problems with the M2T format and prefers the mpeg format. My experience seems to indicate that using M2T format and CS4 is at best a shot in the dark and very problematic (or as you put it – iffy).
Therefore, even if Adobe supports captures of video from the HV30 it doesn’t fully support the camera since it is dumbing down the quality of the video by converting to the mpeg format. And, doing this while also claiming to support the import of M2T file formats. Am I missing something here?
BTW, I was going to ref. the Adobe sites indicating they offer “FULL” support of the HV30 and import of M2T file format… but it appears that Adobe’s site is down.
Temporarilly I am sure.**Special Note:
After more carefull research, I did find one reference to support of M2T that was noted by Adobe as this… M2T(Sony HDV) … but, I could not find this “(Sony HDV)” notation at any other Adobe help page or anywhere else on the Adobe site for that matter. All other references simply indicate support of M2T – that’s it. I think most would assume that Adobe would support M2T as in all types of M2T files when the “(Sony HDV)” is missing in it’s literature.I do not think Adobe makes this important M2T limitation very clear. If so, they need to stop making the claim that the M2T file is support but rather say the Sony HDV M2T (only) file format is support for import. I guess you need to read the fine print…
Bottom line, Adobe Premeire Pro CS4 does NOT support M2T files unless it’s original source is Sony HDV… unless I a missing something then Adobe should remove the claim to support importing M2T files. They should also mention that when rendering, they simply convert the M2T file to an mpeg and do not use M2T natively. Plus, they should note that this conversion from M2T may or may not work and only supports the Sony HDV M2T formats.
If this is incorrect… please post… since I am having a hard time verifying my information since Adobe’s site seems to not be working very well and I can’t get complete information.
-
Interesting.
Even on underpowered XP systems, I’ve found CS4 to be less generally unstable than CS3 was (particularly under heavy loads with big projects)…which was surprising to me as it seems like CS4 uses far more resources. I’ve only edited DV a couple times, otherwise I’m primarily working with EX1 footage and a little bit of ProRes, odd size screen captures, etc.
I’ve only had CS4 check out a couple times…when I first installed it I found out that Panda antivirus was simply fatal with PPro CS4 on XP 32, and the other day I did manage to accumulate a page file of better than 2.7 GB on a 2 proc, dual core AMD machine running XP 32 and it fell over… Otherwise there hasn’t been much to report since about 4.1.
My workstation has a Vista boot partition, but I have a unique display setup and could never properly configure the Vista 64 NVIDIA drivers to light up all four displays…so I’ll be leapfrogging to W7 due to non-Adobe issues on that machine and see what we can do with that.
I’ve had my share of complaints with Premiere Pro over the years…and I think you’d be hard-pressed to find an NLE user community that would state that their app was perfect (other than the *edit people…I have heard few complaints about that piece of software…but of course it was gone before formats like P2, SxS and AVCHD even hit the scene), but with CS4 my experience has been OK.
…now my AJA drivers and various other third party relationships have all been CS3 until such point where I felt I had all the update issues worked out to move forward, so that’s one caveat I have. I keep all systems in multi-boot to preserve the last viable system until I’ve confirmed it all works together, and the OS is just another variable in that process…
What was the Windows configuration that was under your deal-breaker system Peter?
TimK,
Director, Consultant
Kolb Productions, -
[Joe Moya] “Why would Adobe convert the native M2T file format of Cannon to mpeg if it claims to be able to work with the M2T file format?”
You seem to be confused between what a M2T style file format is and what a .m2t file extension is, HDV as its refered to is a format used by Sony, canon and others to record Mpeg 2 in Transport style packets to miniDV type tape, when Adobe transfers the tape data to a computer it adds a .mpeg extension to its files for computer use.
If you need further you need to do research, one place to start is Adobe and seach for “primers” another place is wikipedia, search for mpeg2, hdv, transport stream, etc. -
…let me try again…
… I have a m2t file that is 11,491,547 KB in size (yea… it’a a huge file… but, helps makes the point I am trying to make).
…the rendered preview file in Adobe is 10,030,031 KB….
That appears to be a compressed m2t (…or, a compressed original Canon mpeg-2 file if you want to call it that instead of m2t). After rendering the Adobe properties indicate a mpeg file (…other editing software indicate m2t).
It is this compression/rendering that sometimes works and sometimes does not when I am using Adobe and the m2t file from the Canon HV30. Rendering the work area with m2t files is not very reliable.
When I can’t view a rendered m2t file, I can’t edit… which means, that Adobe has problems with m2t files (…or files captured from an HV30 using Canon’s Capture software, Avid Liquid or Vega… each with same rendering problems in Adobe). I haven’t tried capturing this with Adobe (…specially since I have such bad luck getting Adobe to work with m2t files even if imported). But, that would make the most sense and the next thing to try… then, I could narrow down this issue – hardware or software problem.
Until then, I can’t see how anyone would want to go through this much trouble when there are other NLE’s whom seem to work fine without issues.
Reply to this Discussion! Login or Sign Up