Wmv export directly from Shake?

hi
caused off short production time, i need to export wmv´s directly out of shake. For a recoding in Quicktime won´t be time at the end of the production workflow. The clips i generate will be part of an realtime »PC« 3d engine. That´s why it must be wmv.
I know about a macro called MPEG writer 1.3, allowing to export mpeg1 directly out of shake. I need a way for wmv.
hear is the link for the MPEG writer 1.3:
http://www.fxshare.com/shake/downloads/plugins/image_generation/MPEG-writer-766. html
I´ve got flip4mac components
I need help and time is running out
thanks for quick answering.

thank´s for the hint.
this is a good wmv component for qt but it does not allow to write a wmv container out of shake. In shake only the codecs and components are available, that are used in a .mov container. (and of course a lot of other things like picsequ).I need the cabability to write out into a wmv container. I need something like a macros. A wmv sdk would also help.

Similar Messages

  • CS5: Bug when exporting directly from PPro with hardware MPE?

    For the record, I'm using:
    A GTX-480 (unsupported)
    The hardware MPE-enabling hack (unsupported)
    The latest version of the nVidia drivers (257.whatever)
    I discovered an issue, of sorts, when exporting directly from Premiere CS5, versus using the "Queue" option to send to AME. I was exporting from an NTSC DV Standard sequence to a 320x240 H.264, in which I had enable cropping and trimmed a bit off the sides and top and bottom of the source; the Output tab was summarily set to "Scale to Fit". With hardware MPE enabled in the Project Settings, the export would be the proper final dimensions (320x240), but any area that was cropped off was instead padded with black. The actual video content was then squeezed and malformed into the area not occupied by the black bars.
    I found that, if I disabled hardware MPE or sent the export through AME by use of the Queue button (instead of Export), then the export was performed properly--the video was cropped correctly and then the video stretched to the borders of the exported video, maintaining the desired aspect ratio.
    As I mentioned at the outset, I'm breaking a couple rules and perhaps tempting fate with others, but before I go about rolling back my drivers and the like, has anyone noticed a similar issue?
    ADDENDUM: By the way, the export doesn't need to come from a sequence. If I load up a source clip into the Source Monitor, and export from there using the process outlined above, I get the same issue. This would seem to indicate, to me, that this is due to some incompatibility with my card, its driver and hardware MPE...

    Did he demo renders or exports?
    About 11 minutes in, he [Dave] demos accelerated H.264 renders.
    Harm Millaard wrote:
    AFAIK MPE only works with renders, not with encoding.
    Well, he did both, actually--but the quote above is a typo on my part. I meant to say "exports" or "encodes." The last couple minutes of the aforementioned demo video are dedicated to exporting a sequence directly from Premiere, and having the benefit of hardware MPE. That's where I'm getting the issue I've outlined above; with hardware MPE enabled, and using the "Export" versus AME "Queue" button/function, I get the strange black outline. With software MPE or through AME, all is well.

  • Exporting direct from FCP vs. sending to Compressor?

    I've done both, but the choice ends up being a coin toss. So I'm curious if there's any accepted wisdom as to the Pros & Cons of each workflow (using the current versions of each app, and in a hypothetical All Things Being Equal scenario)?
    In other words, if you were to create the exact same "Master File" from a given FCP Project using each route (in terms of the finished file's dimensions, frame rate, etc), and you selected the exact same codec/quality options to create that file (assuming the identical options exist to be chosen), would there still potentially be any significant difference between the two files? Either in terms of file size, length of time it takes for the file to be created, or any appreciable difference in image quality (despite the theoretically identical file settings)?
    Because a difference in any one of those three categories might be enough to tip the scales towards using one workflow vs. the other, depending on the priorities  in a given situation.
    (And for the sake of this comparison, I'm leaving aside the issue of which app could still be used for other tasks while the export is in progress. Let's just assume for the sake of argument that in both cases the machine would not be being used for ANY other work during each of the exports.)
    Any theories? Real-world experiences? Or has some 3rd-party test site already attempted this kind of direct comparison (using the latest versions of FCP-X and Compressor 4.x)?
    Thanks,
    John B
    Toronto

    Without considering every possibility, here are a couple of general thoughts.
    Given the same Compressor preset there should be no quality difference between the output from a master fie to Compressor and sending it from the timeline  to Compressor. There are speed differences and exporting from FCP X is the fastest workflow.  Lately, I've found second fastest to be Send to Compressor. But the inferences  differences aren't great.
    Most of this depends on one's workflow preferences. The most lengthy workflow is to first export a master file and then bring that into Compressor;. Funnily enough, that is how I work because I want to have an iFrame master file that I can compress for different purposes over time.
    One user recently posted that he used Send-to-Compresssor because it gave him the opportunity to pause the processes without losing his work.
    In the past (particularly with legacy FCP) the Send-to-Comnpressor workflow was something I avoided. It was slow and unreliable.  10.0.x to 4.0.x was faster but troubled in other ways. The latest versions, however, seem to get it done efficiently.
    Final thought: if you do your own tests, check o ensure you have similar amounts of free memory. Otherwise, it's not a "fair fight"/
    Russ
    edit: override the auto complete

  • Poor quality when exporting HD project directly from Final cut Express

    I am doing some HD projects in Final Cut Express HD. I filmed with the Sony HRD-HC1 in 1080i. I import into FCE using the 1080i 60 preset from Easy setup. I completed the project and it looks great from FCE full screen. I export as Quicktime (not Using Quicktime conversion), and I get a perfect looking output file using the Apple intermediate codec, 1440x1080. The problem is that the client needs to play back the video on windows machine using Quicktime. The windows Quicktime does not support the AIC apple intermediate codec, so I have to export to another format. I tried everything exporting from FCE, MP2, H.264, DivX, everyone option. They all look terrible. Blurry, especially parts that have quick motion. Really terrible. I called Apple support, no love. I then tried taking the AIC version of the file and used compressor. It took forever, but came up with am OK MP2 HD file. It still doesn't look that great, but it is way better. So, is their something broken with the FCE exports using Quicktime conversion? Anyone have similar experiences or workarounds? I don't want to use compressor as I don't have it on my Mac Book pro, I had to move it to another machine to do that.

    Being that the dimentions you suggested should be widescreen, I re-ran the conversion to your parameters, this time un-checking "Preserve aspsect ratio.. as letterbox" and this time it is widescreen. Not sure why, but it was putting the black bars on the left and right, not the top and bottom, scrunching to 4:3ish with that box checked. Strange.
    Anyway, the quality is the best H.264 I have seen exporting directly from FCE. It still blurs quite a bit on the fast moving video parts, my MP2 version from compressor still looks lots better. Seems like there is some problem with exporting HD from FCE. It just is not coming out sharp, like the Apple intermediate codec version you get with Export - -> Quicktime movie or if you wait for compressor to do the work rather than FCE. Does compressor use a different engine, or does it use the same QT and just take more time to do a better job in the export? Something just isn't right.

  • Trouble Exporting MXF from PP Cs6

    Hello,
    I am having a lot of trouble exporting a sequence of mxf footage out of premiere pro cs6. Whenever I try to export directly from Premiere the program stalls out. I tried sending it to adobe media encoder, which worked temporarily. Now, the sequence doesn't show up in adobe media encoder. I then tried sending turning the sequence into an AE composition, which again worked seamlessly temporarily. I am working with multi-clip sequences and last night I noticed that when I turn my sequence into an AE comp, after effects began referencing the wrong angle. After Effects also began giving me error messages saying that it was having trouble conforming some of the mxf files. Any insight into how I can fix this would be most helpful. I am working on a Mac Pro Ghz-6 Core Intel Xeon.
    Thanks!

    What exactly do you mean by "multi-clip sequences." Multicam?
    If so, try dropping the same source content into a sequence without any multicam edits and see if that exports. That will help determine if the problem is limited to multicam sequences.
    Have you tried closing all the apps, confirming through Activity Monitor that all the processes shut down (including pproheadless and dynamiclinkmanager), and then relaunching the apps? Or simply rebooting the system. This feels a bit like a problem where the initial failure to export left things in a bad state, so that you need to clear the decks.
    What are your export settings? Do you have similar problems exporting to other formats?
    And just to confirm the reference in the thread's title, you're running PPRO CS6, not CC, right?

  • Exported mixes from STP drift out of sync

    STP seems to have a mind of it's own. Mixes that use to export fine are now drifting out of sync over time, about 2 seconds over fifteen minutes. If I export the mix either directly from STP or through Compressor, it drifts.
    However if I export with video (through Compressor), the audio is in sync properly.
    Does anyone on the STP team have a clue as to what this might be? It's driving us nuts!
    Michael Buday

    Thanks Gavin. I often do the same thing, export projects with a large number of tracks through Compressor because exporting directly from STP is just too unreliable (missing EFX, keyframe levels/pans missed entirely, etc.)
    I tried exporting as usual through Compressor using the standard 48:16 preset, but again - drift. When I then switched to PRESERVE VIDEO with the same audio settings, the sync was fine. This is a workaround, but a real pain in the butt because I then have to extract the audio out of the .mov file. Not rocket science, but just too many steps to do all the time.
    The weird thing is, this has happened only three times out of about 50 projects, but once it occurs, it's as if the project is corrupted in some way and it never exports properly again.
    Michael Buday
    G5 Dual 1.8 GHZ   Mac OS X (10.4.3)   FCP 5.03, STO 1.01

  • NTSC to PAL - Export straight from FCP or use an mpeg file?

    I was reading this
    http://www.macworld.com/article/49306/2006/02/marchcreate.html
    however it does not mention what to bring into compressor.
    Should I export my ntsc sequence straight from FCP into compressor, or should I drag an ntsc mpeg file I aldeady made into compressor? Ive been trying the latter but can't do much as each step gives me the spinning beach ball for anywhere from 5 to 10 minutes. Thanks much.

    Yes, you should export directly from FCP Using Compressor. Exporting to a heavily compressed MPEG-file, and then converting that from NTSC to PAL makes no sense. You would want your video to go through as few conversions/generations as possible.

  • How to export photos from iphone directly to website??

    I have problem. My company start new web site with photo gallery. I have Iphohe and Ipad. When I go to this website i can't export photos directly from iphone. Do you know ane solution?

    There are a number of methods including:
    Via iTunes and USB cable: iTunes: Syncing photos - Apple Support
    Via Photo Stream: http://support.apple.com/en-us/HT201317
    Via 3rd party app: http://www.photosync-app.com
    Via 3rd party cloud services such as Dropbox

  • Can the exported video from FCP X play in WMV?

    (1) Can the exported video from FCP X play in WMV?
    (2) If not, can I convert with the help of Compressor 4 to make it to play in WMV?

    No to both. You need third party software to create WMV. Telestream has tools for this.

  • Exporting Jpeg2000 for DCP directly from Premiere

    Hello everyone,
    I have to export a jpeg2000 sequence for a dcp. I`ve just installed the j2k plug in in premiere and after effects. My question ist do I have to export the jpeg2000 sequence from AE or can I do it directly from premiere? The problem is that I can`t change the color space to xyz in premiere, which I can do in AE, but is it necessary if the plug in seems to have a XYZ Conversion as an option? Did someone used it before that way?
    my second question: in my timeline I have a dpx sequence, some psd graphics and titles made in Premiere Pro. Everything in Rec709. Do I have to convert everything to XYZ before exporting as jpeg2000 sequence in XYZ color space?
    thanks in advance!:-)

    hi there, so I made some tests with exporting a jpeg2000 sequence
    1. directly form Premiere Pro, through the j2k plugin, with convertion to xyz color space
    2. from After Effects with convertion to xyz
    3. first I exported a tiff sequence from Premiere Pro and then exported it from OpenDCP as jpeg2000 sequence
    the problem is that all of the final results are slightly different. the brightness is a little bit different and the colors too. any idea why?
    btw. I`m using Premiere Pro CC 2014.0.1

  • How can I export 1920x1080 Mp4 directly from FCP

    How can I export 1920x1080 Mp4 directly from FCP

    Thanks Russ.
    I wasn't thinking about the Apple Devices so much as the Master File set to Audio & Video which produces a .mov file.
    I have normally used the Master File to export my videos but will experiment in future with "Computer".
    I've taken a closer look with VideoSpec and notice that the data rate of the .mov file is about 70% of the .mp4 and the file size is correspondingly smaller.
    The export/render time of the .mov is also somewhat quicker.

  • Export flv directly from Photoshp cs5.5 MAC

    Hi i'm searching a method to export flv from photosohop cs5.5 . I've used adobe media encoder, but in an external software, i need a method via Photoshop.
    Can anyone help me
    thanks

    oh. thank, so the method is media encoder.
    thanks a lot

  • Exporting contacts from webex connect?

    Does anyone know of a way to export contacts and groups from webex connect?
    I have way to connect with pidgin and get them into the pidgin contact file then put script together to make a CSV to import into IM&P for each user. I'm looking for a better way to do this with WebEx connect or the Cisco webex connect/jabber client directly if possible. On the Cisco webex connect admin web tool there is not a way to export contacts in mass either. I'm thinking of opening ticket with them to get a export of all users contacts hopefully.
    Sent from Cisco Technical Support iPhone App

    Replying to my own post... for the better of the communirty here. I reached out to WebEx and there is no way to export contacts from WebEx Connect and they don't have a way either currently. Left to third party clients and piecing your own solution (script) together currently and running it with each user manually.
    Would be nice if they would add Export/Import Contacts option to the Jabber client then when you imported contacts it pushed them to the server from client PC instead of an admin having to bulk import a bunch of user contacts.

  • CR2008 Not enough memory while exporting reports from Crystal Reports 2008

    I have recently upgraded our Crystal Reports version from Crystal Reports Basic for Visual Studio 2008 to Crystal Reports 2008. After upgradation I am facing the problem "Memory full.OtherErrorFailed to export the report. Not enough memory for operation" when I am trying to export the report from Crystal Reports 2008 Report viewer, or directly from the code behind. The application is hosted application. The problem occurs in our production environment.
    Server details:
    OS: Windows 2003 Enterprise Edition R2 with SP2
    IIS: IIS 6
    .Net Framework: 3.5
    Application details:
    Hosted application using Crystal Reports 2008 SP 3
    Crystal Reports Viewer version: 12.0.2000.0
    The data binding of the report object is done through an ADODB dataset.
    Web.Config:
    <configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">
      <configSections>
        <sectionGroup name="businessObjects">
          <sectionGroup name="crystalReports">
            <section name="printControl" type="System.Configuration.NameValueSectionHandler" />
            <section name="crystalReportViewer" type="System.Configuration.NameValueSectionHandler" />
          </sectionGroup>
        </sectionGroup>
      </configSections>
      <businessObjects>
        <crystalReports>
          <printControl>
            <add key="url" value="http://myserver/mysite/PrintControl.cab" />
          </printControl>
          <crystalReportViewer>
            <add key="documentView" value="weblayout" />
          </crystalReportViewer>
        </crystalReports>
      </businessObjects>
      <appSettings>
        <add key="CrystalImageCleaner-AutoStart" value="true" />
        <add key="CrystalImageCleaner-Sleep" value="60000" />
        <add key="CrystalImageCleaner-Age" value="120000" />
      </appSettings>
      <system.web>
        <httpHandlers>
          <add path="CrystalImageHandler.aspx" verb="GET" type="CrystalDecisions.Web.CrystalImageHandler, CrystalDecisions.Web, Version=12.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304" />
        </httpHandlers>
        <compilation debug="false">
          <assemblies>
            <add assembly="CrystalDecisions.Data.AdoDotNetInterop, Version=12.0.2000.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304" />
            <add assembly="CrystalDecisions.Shared, Version=12.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304" />
            <add assembly="CrystalDecisions.ReportAppServer.ClientDoc, Version=12.0.1100.0, Culture=neutral, PublicKeyToken=692fbea5521e1304" />
            <add assembly="CrystalDecisions.Web, Version=12.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304" />
            <add assembly="CrystalDecisions.Enterprise.InfoStore, Version=12.0.1100.0, Culture=neutral, PublicKeyToken=692fbea5521e1304" />
            <add assembly="CrystalDecisions.Enterprise.Framework, Version=12.0.1100.0, Culture=neutral, PublicKeyToken=692fbea5521e1304" />
            <add assembly="CrystalDecisions.ReportSource, Version=12.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304" />
            <add assembly="CrystalDecisions.CrystalReports.Engine, Version=12.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304" />
          </assemblies>
      </system.web>
      <system.webServer>
         <handlers>
             <add name="CrystalImageHandler.aspx_GET" verb="GET" path="CrystalImageHandler.aspx" type="CrystalDecisions.Web.CrystalImageHandler, CrystalDecisions.Web, Version=12.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304" preCondition="integratedMode" />
         </handlers>
      </system.webServer>
    </configuration>
    Sample Code:
    Report = new CrystalDecisions.CrystalReports.Engine.ReportDocument();
    Report.Load(Server.MapPath(strReportPath));
    Report.SetDataSource(dsReport);
    Creportviewer.ReportSource = Report;
    For exporting the report to PDF
    string Filename = Path.Combine(Environment.GetFolderPath(Environment.SpecialFolder.InternetCache).ToString(), Guid.NewGuid().ToString() + ".pdf");
    Report.ExportToDisk(ExportFormatType.PortableDocFormat, Filename);
    Clean Up Code: (Page_UnLoad event)
    if (Report != null)
         Report.Close();
         Report.Dispose();
    Creportviewer.ReportSource = null;
    Creportviewer.Dispose();
    dsReport = null;
    GC.Collect();
    GC.WaitForPendingFinalizers();
    Can someone help me resolve the issue.

    The .rpt file size is 14MB with the Data Save option enabled, 12MB without Data Save.  Presumably the 12MB file size is because of the 24bit PNG we have as our background.
    The Designer executes the report in less than a second and we can scroll through all pages and see the image fields perfectly.
    When we Export to PDF, the Designer takes a long time, eventually gets to the 77%, the 7th record and returns "Export report failed" followed by "Memory full".  If we export only page 1 of the 3 pages, it also returns a Memory full error.  However, when the same report is run with only 1 page, that page exports to PDF but with a ridiculously large size and export time.
    The machine has 2GB of physical memory with an 8GB pagefile with Windows 2003 (latest everything).  The process runs up to about 1GB before reporting the memory full error.
    We've also tried a variety of other suggestions posted in the other thread with no success.
    We're happy to provide the RPT file to the Report Team to diagnose the problem.  Ultimately, we need to be able to produce a 15 page report with approximately 45 images.
    Our preferred scenario is fixing problem 2.  The CR Designer seems quite capable of rendering our report and printing it to our third party PDF printer in a timely manner with small size.  However, the API reports memory full.
    The API resides in a dedicated reporting web service with NO other code except for loading the report, setting parameters and printing.  When executing, it uses up to about 1.1GB before reporting the error.
    Are there any other suggestions for fixing what we have?  Are there known problems with large images in reports?  Do we need to lodge a formal support request?
    Regards,  Grant.
    PS.  Grr and my message formatting is lost when I edited this message!!!
    There is a 1500 character limit and then all formatting is removed to save space. Break you posts into separate entries.
    Edited by: grantph on Sep 30, 2009 2:49 AM

  • How do you export messages from Ovi Suite?

    As the title says, how do you export messages from Ovi Suite?
    I know how to export messages from Nokia PC Suite, but it doesn't seem to be possible in the new Nokia Ovi Suite.
    Here is how I would do it in the Nokia PC Suite.
    1. I click the Messages icon to open Nokia Communication Center.
    2. I click on the Messages option on the left pane to view only messages.
    3. In the main window I mark the messages I want to export.
    4. Then I go to File menu and chose Export.
    5. Choose destination folder and I'm all set to export my messages from my Nokia.
    I can chose between the formats CSV and VMG (vMessage) for export. If more than one message is marked only the CSV format is available. But what you can do to export several messages in the VMG format is to mark them all in the main window and press CTRL+C or right click and chose Copy to copy them all to RAM memory. Then all you have to do is create an empty folder on the desktop and paste them in there by pressing CTRL+V or right clicking and chosing Paste.
    That's all there is to it, using Nokia PC Suite. So how do you do this in Nokia Ovi Suite? You don't, right?
    And this **bleep** Ovi Suite is supposed to replace PC Suite?
    Thank God I won't be needing neither of them much longer. I am switching to Android and HTC. Good luck with Ovi, the Ovi Player, the Ovi Suite, the PC Suite, the Symbian, the S60, the Symbian^1 (S60 5th edition), the Symbian^3, the Symbian^4 and what not.

    I believe OVI took a step in the right direction with this option. I also believe it was made available due to the fact that OVI Suite cannot take a huge number of messages altogether. This option was made available so that the messages could be backed up.
    However, I'd like to suggest the following, if possible.
    1. Make Nokia OVI Suite be able to handle a huge number of messages.
    2. Have the option to export only selected messages.
    Nokia 701 Dark Steel on Belle FP2

Maybe you are looking for

  • Touchscreen won't accept a signature on a PDF.

    I just bought a Windows 8 Tablt(HP Envy X2) and want to be able to have my customers Sign a PDF. The problem is, I can use the mouse to Draw a Signature, but the Touchscreen will not Draw a Signature( I can add "dots"). Can anyone help me fix this? I

  • If cisco "openh264 video codec" is so great that Mozilla packages it automatically, why is it disabled (Never Activate) as an Add-on?

    It seems that every software manufacturer has to write a plethora of little gimmicks into their installation and setup files that loads trash onto my computer. I'm not talking about programs like _Chrome_, that gives me a chance to decline. I'm talki

  • Decimals Confusion ?

    Hi, I declared a variable in this manner <b>data : w_zkprs(15) type p decimals 4.</b> My guess is the total length is 15 of which 4 are for decimals and 1 for dot and rest for the number . Is that right ? Regards, Ben.

  • Problem with CO54

    I am processing an inbound IDOC using WE19. The Idoc has a segment called material quantity and its value is 00000000.000(ZERO). After this i am supposed to go to transaction CO54 and execute it. On executing it a report is displayed.On selecting one

  • Nokia map 3.0 doesn't work with n95 any solution

    after downloading nokia map 3.0 i get this error " not enough memory to start application" i also have deleted qf files & cities after i've started map again but still get the same error...anyone can help please?