Joe Moya
Forum Replies Created
-
Agree… without specifics… a post like this only becomes a rant…
However, to take the edge off of the original post… I have posted my specific issues with Prem Pro in the past but it hasn’t help… and this is also true even when I attempted to get help from Adobe’s technical “support”.
As far as Adobe not working because of substandard hardware… I beg to differ. Below are my specs and I have NEVER been able to get Adobe to work well with HD files. Instead, to make PP work I have to dumb down the codec before editing with PP… which is why I don’t use it as an editing software.
All that being said, I do wish Adobe could find solutions to the many problems with Prem Pro and HD editing before they create a 64bit ONLY NLE and make third party 32bit plug-ins obsolete. Plus, it wouldn’t hurt so much to buy the Production Premium Package if Prem Pro worked as efficiently and effectively as certain other professional level software.
System specs:
WinXP, ASUS W6T6 WS Rev., Intel i7 3.2Ghz 8X32bit CPU, 6G Corsair DDR3 (low lat.) RAM, GeForce GTX 280, LG DVD, Realtek AC97 Aud., Adaptec 5405 RAID SAS controller for 2 Stripes of 2xHD 15k rpm Fujitsu 300G ea., 2×20″Samsung 204t -
HD or SD video? If HD m2t files, then rendering can be a problem with Prem Pro regardless of whether it is 64bit or 32bit…this is specially true if you use more than one track or try and stacking tracks with Look on seperate tracks.
The best solution (besides avoiding PP and HD m2t video) is to color correct using Looks first… then, render Look applied project as a new video file… use this new color corrected video file and edit using the new file…and, edit from that point. It’s not the most versitile way to solve this problem… but, it works.
-
If you want to scale down the size of the video/pics on a sheet without loosing HD quality, then what you need to do is not scale the size of the pic/video down… but, rather move the camera away from the pic/video. The appearance is of a smaller sized pic/video but no down scaling is done.
Don’t scale the pic/video… instead, move a camera away from the pic/video.
-
I understand your concern… Stefan Minning over at minning.de does a good job explaining this 32 bit vs. 64 bit plug-in issue.
-
The only way to not jump to any conclusion is for CS5 to support 32bit…
Other than that… whether the 32 bit plug-ins will work depends upon how the third party plug-in providers decide to adapt there current 32 bit plug-ins for CS5’s intended 64 bit ONLY application.
The third party providers of older 32 bit may adapt to 64bit or they may not… it may be a free upgrade or it may cost as an upgrade or priced at a higher new plug-in price. Anyone can draw there own conclusion as to how third party creators of plug-in will adapt to the 64 bit only CS5. However, the only way to say for certain that a 32 vs. 64 bit plug-in conflict will not be an issue is for Adobe to include 32 bit compatibility to it’s CS5. And…unless that happens… then additional potential costs should be concidered when buying or upgrading to CS4 and/or CS5.
If I am incorrect on this point… please elaborate.
-
Unless the original developer of the plug-ins provide free (or charge for) upgrades for 32 bit plug-ins… they will not work in a 64 bit only CS5 version of Adobe software.
-
A side note of interest… according to recent information from Adobe, if your intention of upgrading any (or purchase new) plug-ins for CS4… the current intention by Adobe is to no longer support 32bit plug-ins and only support 64bit.
If you plan to make a significant investment into CS4 (and its plug-ins) and have past investments in plug-ins that are 32bit based (which is pretty much all plug-ins that exist today)… you might be aware that future versions of Adobe software will not support these 32bit plug-ins. Chances are you will need to make future futher purchases/re-purchases of 64 bit versions of plug-ins not made by by Adobe.
On that note, you might consider the option of switching to a different compositing software all together or at least be prepared to spend on a 64 bit (only) upgrading of plug-ins once you have commited to CS4 with the intent of upgrading to CS5 in the future.
-
Well then…. somone needs to tell this to Adobe software engineers and needs to file a truth in advertising complaint….because the manual says that CS4 can use these natively.
At the same time, this explanation doesn’t seem to be universally accurate since I do have a number of m2t files that work fine.
All that being said…now, I need to find the best conversion format to help produce the most lossless final results… unless someone knows of a file codec that is absolutely lossless when converting the m2t file… anyone?
Until then, I think I am going to try and find out why these particular group of m2t will not render/import and the others will.
-
Scenes are detected just fine when I capture with Avid Liquid… and, the other m2t files work fine… it seems to be just this group of m2t files that do not seem to want to render or import correctly.
I tried changing directories… clearing caches… deleting render files… changing file names… even changed the file extension from m2t to mpg… nut’n seems to work… PP will not make a pek or cfa file and AE will not render/recognize the files either.
-
Thanks… that was it!
The problem was that the shortcut wasn’t created during the install… and, I assumed it was a standard plug-in… located where other plug-ins would normally be. Instead, it is it’s own directory with it’s own shortcut.
Thanks for the help…As for Adobe’s support… well, the problem is that I spoke to 6 different support personal over 3 days and NOT ONE even knew that Mocha was a part of AE (in fact, a few said it was a plug-in not included and tried to sluff the problem off to Imagineer). In every contact, I had to navigate the customer support person on the Adobe site to prove it was a part of AE.
This problem should not have been a difficult question to answer. However, I am feeling the language barrior and lack of knowledge regarding the very basics regarding Adobe software is definately not good for the products reputation and a waste of Adobe’s money.
I don’t want to make this post sound like a rant… but, I would strongly suggest that someone at Adobe call and audit there own support lines and verify the quality of the people working the phone lines. The past few days indicates that the support personal (on a large scale) does not fullfill the concept of “support” even on a basic knowledge level.
Thanks – again…you have been very helpful.
Joe Moya
Side Note: As for escalating this problem… that too was a problem. It was supposedly escalated, but I never recieved any reply. Plus, I could not log into the support system… a seperate problem in and of itself… of which, that problem was also beyond there ability to help me with. I decided I would work with one problem at a time and chose to simply solve the Mocha problem first and work on the log-in issue second.