Native AVCHD support

We need native AVCHD support with no transcode option. if you have a quad or 8 core mac pro it will edit fine.. AVCHD is what the majority of prosumer cameras are and are going to be.. we want tapeless to save us the time and money, we shouldn't have to transcode it (though it should be an option)..
I think apple should realized a free update to support it.. Avid has realized this already and has both native import and AMA support for AVCHD.. now when will Final cut pro? it's making me want to switch to Media composer.

AVCHD not an editing codec. Supporting it would just mean your computer
is wasting processing power doing something silly. It's smarter to
transcode to an editing format and use your processor to do cool
effects and stuff.
geek3 wrote:
everyone is going tapeless.
DVCPRO HD is a professional tapeless codec
that also works well as an editing codec.
So is AVC-Intra.
But not AVCHD.
most people are getting avchd or dslr cameras
It's a great way to get started in video, but
the professionals who sometimes use AVCHD cameras
know the difference between an acquisition codec
and an editing codec.
Here's some interesting discussion on the subject:
http://forums.creativecow.net/thread/280/529
And here's how to "fix" the moiré problems with DSLR footage:
http://www.dvxuser.com/articles/article.php/20

Similar Messages

Does iMovie 11 support native AVCHD (.mts) files?

Native AVCHD file support is the first thing I expected for the new iMovie. Does iMovie 11 support native AVCHD (.mts) files? Or it has the same painful way of importing and converting AVCHD files to the other format like iMovie 09?
Is there any improvements for AVCHD file supports in iMovie 11?

I don't think it does. I picked up a copy this afternoon after the keynote (I like the way that Apple stores have them in stock right away - and at $49 it wasn't really a painful experiment) hoping this would be the case, but it does not appear to be so.
After installing, I tried to import some loose .mts files, but they are greyed out. Some brief exploring turned up nothing to help.
This is really too bad. It would be so nice to be able to save the individual .mts file on my hard drive, and access them when necessary. I'm fine with the intermediate encoding iMovie does before editing, but forcing me to use the silly file structure of my camera's hard drive, or an iMovie archive (basically the same thing) is frustrating.
Allowing the import of naked .mts files would be a huge step forward.
Assuming I'm not wrong about this, what is the best way to work around this? What is the best way to bring loose .mts files into iMovie? (And I hope I'm not hijacking the thread by asking this.)

Finally AVCHD Support in FCPS2

checkout this:
Note: Final Cut Pro does not have native editing support for AVCHD footage. However, the Log and Transfer window automatically transcodes AVCHD footage to the Apple ProRes 422 codec (or Apple Intermediate Codec) during transfer.

Welcome to the forums...
and...we know. Mere hours after it came out we were talking about it:
http://discussions.apple.com/thread.jspa?threadID=1013565&tstart=50
http://discussions.apple.com/thread.jspa?threadID=1013627&tstart=50
http://discussions.apple.com/thread.jspa?threadID=1014033&tstart=50
It is mighty cool.
AVCHD to ProRes right away. VERY smart.
Shane

Avchd support yet?

Is anyone getting AVCHD support in FCP? Is it working properly and natively? Thanks!
I am looking to buy a Panasonic HMC150.

A file conversion is not limited by the linear time factor of capturing from a tape. The process is dependent on the speed of your machine, but on my MacPro it runs much faster than real time. About 30% of real time. Plus, the log & transfer function can be continued while one clip is transferring. So you log a clip, start the transfer, then go log your next clip and start it when you're ready. You can be logging clips while others are transferring. It's a much faster process than capturing tapes.
As far as DVDSP creating BluRay discs, you are correct. It doesn't. But you don't use DVDSP to create an archive disc of your raw AVCHD cards. You burn them as data, via Toast. Or, as you said, just keep them on a hard drive.
When you edit from MiniDV or DigiBeta, do you archive all your captured files? I hope not. That's what log & capture is for. You get rid of the files and keep the tapes. Your SD cards are your tapes. Keep the cards, or keep the files from them on a drive.

No AVCHD support for me! :-( on 4.2 or 4.1 why??? full version installed!

Hi Guys
I have two issues
One I don't have AVCHD support and yes I have a full version but do have the new AVC-Intra support.
Two Whenever I import .avi files they seem to play much faster than the audio. This second problem would not matter as much if I could get my AVCHD data into the sytem without it saying file not supported,
Any ideas?

Here's what you have to do:
Uninstall the entire CS4 suite.
Download the CS4 Clean Script and run it at least 2 times, rebooting between each run.
Install the CS4 suite from your original installation discs.
Update the software.
That you have no AVCHD presets indicates a smurfed installation, either from installing updates or from uninstalling older suite app version. A complete uninstallation, running of the clean script, and re-installation and update is the only sure way to get everything back to normal.
-Jeff

Re: Native Language Support in Forte

[email protected] wrote:
I've been posed a question in the abstract about Forte's native language
support. Does Forte support any languages other than C/C++? And if so,
what are the limitations or caveats?
Native Language Support could also mean the NLS standard which Forte supports. This
provides for Internationalization (I18N) of a Forte application. This means a client
application deployed in french, german, and english (for example), could all be making
requests of the same Forte shared service and getting responses in the native language.
We provide for changing the language/character set displayed both statically before the
application starts, and dynamically change it while the application is running.
If support native language support means ability for Forte to call existing application
logic written in C/C++, then today you can "wrapper" C functions in a Forte Class,
instantiate the class and "call-out" to the member functions (your c functions) directly
from the 4GL object.
C++ functions are a challenge due to cross platform C++ compiler issues which at a
minimum include "name mangling" being non-standard for all the C++ compilers.
However, you can "export" C++ class member functions as external "C" functions so that C
code can call the function as if it was regular K&R or ANSI C.
If other language support is required, I have customers on the East Coast which have
successfully wrappered MicroFocus Cobol on HP-UX, and the ADA language. This is due to
the concept of all 3GL languages today support the concept of allowing for their
language to be called from 'C' (other possibilities are Pascal, Fortran, etc).
Here the only caveat is you need to be aware of the other language's "boot-code" may be
registering for operating system "signals" and not handling them appropriately. This
rarely is an issue these days.
If other language support means do we code generate our 4GL language to any language
other than 'C++', the answer is currently "no".
However, we do support exporting Service object definitions to environments like DCE,
CORBA, Encinca (a TP monitor), and the WWW. In our next release we will complete our
support for exporting services objects to Java. This will allow for Java applications to
call upon the power of Forte's Shared Services architecture. Using this exporting
concept, applications written in various other languages would be able to "call-in" to
the Forte shared service from the ourside world.
Didn't know what you were looking for. Hope the above hit the mark. If not, write me, or
give me a call.
Regards,
jim

Not exactly sure what you are asking. Can you rephrase your question?
If your other server's locale is same as the one you configured then it should be ok.

Enabling (native) write support for NTFS

I used NTFS-3G for writing on NTFS before, but because of this (https://discussions.apple.com/thread/4187322) i had to uninstall it.
A while ago i heard something about OSX having native write support for NTFS.
Is that even true? And if so, can i (and how) enable it on Mountain Lion?

Tbassist4 wrote:
Thank you. I've been looking at these two a little bit. NTFS-3g seemed like a pretty good choice at first, but I question the stability a little bit, as they do warn you that the project is experimental. Paragon actually looks like a good, safe solution, and also generally inexpensive, but I am trying to find out whether or not it will run on intel-based Macs, as it only lists system specs for running the program on a PPC-based Mac. I'll report the results as soon as I find out.
On the System Requirements Page for Paragon it does say Intel. Actually it says x86 which are Intel processor architecture, plus on the box it shows the Universal logo on it (hard to see but it's there).
David L.

AVCHD support in Premiere Pro CS3

I just noticed there is a KB technote, kb403297, regarding avchd support in premiere: http://www.adobe.com/go/kb403297 .
As you can see, the technote says nothing. Is there something afoot? Will Premiere FINALLY support avchd ?

Could you please read this new tech note about AVCHD and advise what you think: kb403297 ( just posted today) link: http://kb.adobe.com/selfservice/viewContent.do?externalId=kb403297
In particular, I would like to know if anyone has experience with the blackmagic Intensity Pro card, about which the tech note says:
Blackmagic (recommended)
Blackmagic Intensity Pro card offers real-time capture to the PC from the camera using the HDMI cable into the Intensity card. This provides Premiere Pro CS3 editable format, but the sound is stereo only.
I like the sound of this solution for AVCHD editing (it is $250 to $350).....would like to know if anyone has tried it

MSI Bluetooth & XP SP2 native bluetooth support

I am getting sick and tired of Widcomm's software stack, my bluetooth device will stop working if the computer has been on for a while, it needs frequent resets, etc.
XPSP2 has native bluetooth support. Does this work with the MSI bluetooth devices, without installing any Widcomm stuff?

Thanks to the Secunia security mailing list for this bulletin:
Pentest Limited Security Advisory
WIDCOMM Bluetooth Connectivity Software Buffer Overflows
Advisory Details
Title: WIDCOMM Bluetooth Connectivity Software Buffer Overflows
Announcement date: 11 August 2004
Advisory Reference: ptl-2004-03
CVE Name: CAN-2004-0775
Products: WIDCOMM Bluetooth Connectivity Software
Vulnerability Type : Buffer Overflow
Vendor-URL: http://www.widcomm.com
Vendor-Status: Fixed in release 3.0
Remotely Exploitable: Yes
Locally Exploitable: N/A
Advisory URL: http://www.pentest.co.uk/documents/ptl-2004-03.html
Vulnerability Description
WIDCOMM's products provides a full range of Bluetooth connectivity
solutions for PCs, PDAs, mobile phones, headsets, digital cameras,
access points, and various output devices.
An unauthenticated remote attacker can submit various malformed service
requests via Bluetooth, triggering a buffer overflow and executing
arbitrary code on the vulnerable device.
On Windows platforms this allows arbitrary code execution under the
context of the currently logged on user account.
Vulnerable Versions
WIDCOMM supply their Bluetooth Communications software to other
companies to allow them to integrate Bluetooth technology into their
devices. They also supply Bluetooth SDK's to enable developers to create
applications that use Bluetooth. Therefore it may not be immediately
apparent that you are using the WIDCOMM Bluetooth software and version
numbers may vary.
WIDCOMM's website (http://www.widcomm.com/Partners/index.asp) reports
the following companies as customers or partners with WIDCOMM:
Logitech
Samsung Electro-Mechanics
Sony
Texas Instruments
Compaq Computer Corporation
Dell
National Semiconductor
Matsushita Electric Industrial Co., Ltd.
Wistron NeWeb Corporation
TDK Systems Europe
Zeevo
Cambridge Silicon Radio
Billionton
Broadcom Corporation
LG Innotek
MSI
Fujitsu Siemens Computers
Philips
Silicon Wave
Seiko Instruments Inc.
TECOM
Plantronics
Mobilian
Fujitsu Media Devices Limited
OKI Electric Industry Co. Ltd.
FIC
Costar
Brother
Alcatel
Atmel
Conexant Systems, Inc.
Microtune
OSK
Pentest Limited have tested for the reported vulnerabilities against
BTStackServer version 1.3.2.7 and 1.4.2.10 on both Windows XP and
Windows 98 which ships with MSI Bluetooth Dongles. We have also tested
this against an HP IPAQ 5450 running WinCE 3.0 with Bluetooth software
version 1.4.1.03.
Pentest Limited have also written a proof of concept exploit for Windows
XP.
Whilst the above platforms are the only platforms tested and confirmed
to be exploitable by Pentest Limited, discussions with the vendor lead
us to believe that are all versions prior to version BTW & BT-CE/PPC 3.0
are affected by this vulnerability.
WIDCOMM has not confirmed whether BT-PPC/Phone Edition, BT-Smartphone,
BTE-Mobile or BTE are vulnerable.
Vendor Status
WIDCOMM:
14-11-2003 - Initial Pentest Limited Notification
14-11-2003 - Notification acknowledged by WIDCOMM, request more detail
20-11-2003 - Pentest notify WIDCOMM of another vulnerability
06-01-2004 - Pentest send chase up Email without reply
13-01-2004 - Another email
13-01-2004 - WIDCOMM reply saying they are still working on it
21-01-2004 - Pentest email WIDCOMM that they have written a POC exploit
23-01-2004 - WIDCOMM reply saying they have resolved issue and fix
will be available in next release.
10-02-2004 - Pentest ask for an update on expected release date
11-02-2004 - WIDCOMM plan February/early March realease date
29-03-2004 - Pentest ask for update
12-05-2004 - Pentest ask for update
12-07-2004 - Pentest send chase up Email without reply
26-07-2004 - Pentest ask whether a patches will be released for older
versions
03-08-2004 - WIDCOMM respond. No date set for new release and no patch
will be made available for older versions.
Fix
Until version 3 of the WIDCOMM software becomes available from WIDCOMM
or their customers/partners Pentest Limited recommend that end users
stop using the vulnerable WIDCOMM Bluetooth software or set their
Bluetooth device configuration to be non-discoverable or hidden. This
will not stop the device from being vulnerable but it may limit the
exposure.
Credit
These vulnerabilities were discovered by Mark Rowe and Matt Moore from
Pentest Limited.

Is native AVCHD editing finally working in FCP6?

I read somewhere that FCP 6.06 will finally work natively with AVDHD. I've been itching to get a Panasonic AVCHD HMC150 but don't want the hassle of transcoding to giant ProRes files, but rather work with native files.
Anybody had success with this combo?

What is the problem with using ProRes (apart from size of files)? It is an awesome codec. On my humble Mac Pro I can play back 3 streams with a couple of filters applied to clips and transitions in rt.
I have tried native avchd editing in Vegas - got about 3 streams to work, but frame rate only stays full frame at preview (half). Edius playback of avchd is nil for me - although converting to canopus HQ gives similar results to FCP. FCP's log and transfer is also a very elegant way of transferring and transcoding clips on the fly. Also, read the adobe forums for posts on avchd - very variable responses with many reporting lots of crashes!
For me, the bigger issue with FCS2 is the lack of a HD distribution format, ie bluray!

Native iSCSI support in OS X

Is there any chance Apple will add native iSCSI support in OS X?

You will not get any answers from Apple about future products or enhancements. Don't waste your breath asking them. You can send them feedback for an enhancement request using the Apple Feedback site. But you won't get any reply from them.
If you wish to discuss rumors then try one of the many Mac rumor sites like macrumors.com

[Solved] Can't send mails using mutt's native smtp support

I read the wiki and interested in mutt's native smtp support, so I installed extra/cyrus-sasl and decided to give it a try.
After search the online manual of muttrc, I add a few lines to my ~/.muttrc as follows:
set my_pass='mysecretpass'
set my_user=[email protected]
set smtp_authenticators="digest-md5:cram-md5"
set smtp_url=smtps://$my_user:$[email protected]
Everything looks fine, until I sent a test mail. The mutt's status bar is always showing "sending message ..." for a long time, but nothing is sent. I felt frustrated.
Can anyone give me a suggestion? So much thanks.
=======
Edit: The problem resulted from improper options in muttrc, which I've commented. Because I'm using the native IMAP support of mutt, some original options have to be commented, such as:
#set postponed=+drafts
#set record=+sent
P.S.
The SMTP port of Google is 587, while the SMTPS port is 465. It's not necessary to set this port manually.
Last edited by cwjiof (2009-11-25 13:26:15)

try adding a :587 on the end of the url. i'm also not sure you even need /cyrus-sasl or the _authenticators bit. i didn't, back before i moved to an msmtp mutt setup.

Native Library Support OS X Lion

The OS X Mac install of Weblogic does not include support for native libraries that I can tell (no ../server/native directory after install). I can work around this issue by specifying false for the NativeVersionEnabled flag, but wondered if/when native library support was going to be supported on the mac platform (OS X Lion). We are running the very latest version (I believe) of WebLogic.
J

No it is hard to tell when a specific bug gets fixed and in which release such a fix is included.<br />
Bug fixes always first land on the Nightly trunk branch where they can be tested and 'bubble' down to the Aurora and Beta channels and only after that they may get approved for a release.
*[https://bugzilla.mozilla.org/show_bug.cgi?id=639705 bug 639705] - [10.7] add fullscreen support for Mac OS X 10.7 Lion
*[https://bugzilla.mozilla.org/show_bug.cgi?id=668953 bug 668953] - [10.7] Support two-finger horizontal swipe on OSX Lion
*[https://bugzilla.mozilla.org/show_bug.cgi?id=673675 bug 673675] - [10.7] browser.gesture.swipe.up and browser.gesture.swipe.down don't work in Lion

Does Final Cut Pro X have native XDCAM support?

Looking to find out from someone if Final Cut Pro X does indeed have native XDCAM support?

EXDCAM EX yes, is native. No conversion

Native FCP support for AVCHD

Hi,
Does anyone know if Apple has indicated that it plans to eventually support the AVCHD codec natively? If so, could someone point me to where that information might be posted?
Thanks,

There was a FCP Supermeet at IBC in Amsterdam last September.
Apple representatives were at the meet, and indicated somewhat vaguely that native editing would be supported.
Whether that will be done or not remains to be seen, as well as when and if the revised version of FCS will be released.
There is a video of the presentations at LAFCPUG.org that you can view.
http://www.lafcpug.org/ibc08_podcast.html
Actually, I prefer working in pro res HQ due to its 10-bit and better color space capabilities.
HDD space is cheap.
But it's your call, and remember that if it is supported, expect to get the fast CPU you can. It just won't work on anything but.

Native AVCHD support

Similar Messages

Maybe you are looking for