Forum Replies Created

Page 19 of 212
  • [David Roth Weiss] “BTW, it tuns out that Google bought On2 and the merger was just consummated. “

    Ah hah! I knew there was something more to this. Doesn’t this put an interesting light on Adobe and its Flash products? Definitely be worth the time to see what comes of this.

    _______________________________

    Wayne Carey
    Schazam Productions
    https://web.mac.com/schazamproductions
    schazamproductions@mac.com

  • I’m sure it will still work, if you want to use it. But like I said, you can encode an H.264 Quicktime and just change the extension to .flv and you have a Flash video for free.

    _______________________________

    Wayne Carey
    Schazam Productions
    https://web.mac.com/schazamproductions
    schazamproductions@mac.com

  • Kinda sounds like everyone has started to catch onto the fact that they can encode their videos using H.264 and just changing the extension to make it a Flash video. I would have to say that would put a serious bind onto On2. Maybe they finally had the economy to catch up to them. Could be anything.

    _______________________________

    Wayne Carey
    Schazam Productions
    https://web.mac.com/schazamproductions
    schazamproductions@mac.com

  • Mark Maness

    June 22, 2010 at 1:19 pm in reply to: how to make a Blue Ray HDV

    One word of caution…

    Be prepared to wait an eternity for this operation to take place. While it does work, it can take many hours just to perform this feature. I have used this feature only twice and it took me about 5 hours to output a 30 minute episode to DVD, not Blu-Ray, from a DVCProHD 1080i29.97 timeline.

    I can export a Quicktime of my timeline in a few minutes and import this into Roxio’s Toast to create a Blu-Ray in about 45 minutes.

    _______________________________

    Wayne Carey
    Schazam Productions
    https://web.mac.com/schazamproductions
    schazamproductions@mac.com

  • Mark Maness

    June 3, 2010 at 2:45 pm in reply to: FLV Export Component

    Wow! Its so simple, you’re going to slap yourself when you hear it.

    Export your program and compress in Compressor as a Quicktime H.264 file. When its done, you’ll have a quicktime movie with a .mov extension. Now, here’s the neat part… Just change the extension to .flv, the OS will ask you if this is OK, click on OK. That’s it. You now have an H.264 flv movie that can be used on a Flash website.

    _______________________________

    Wayne Carey
    Schazam Productions
    https://web.mac.com/schazamproductions
    schazamproductions@mac.com

  • Mark Maness

    June 1, 2010 at 2:51 pm in reply to: aliasing from live type to finacl cut pro

    When editing, always match any of your project settings with programs. This will cut down on any aliasing issues and render issues.

    As a rule of thumb, never use any DV settings with Uncompressed projects. This is more than likely where you are getting your aliasing issues. I assume that you are working with SD video resolution. In that case, use CCIR 601 NTSC for your LiveType project.

    _______________________________

    Wayne Carey
    Schazam Productions
    https://web.mac.com/schazamproductions
    schazamproductions@mac.com

  • Mark Maness

    May 27, 2010 at 1:32 pm in reply to: XML Bug or Maybe a Quirk?

    Normally, this is what we would do. But in this case everything is already digitized and the program was partially edited.

    I’m going over to that system now and trashing the prefs while the editor is on a quick shoot. But my quandary with this issue is that this issue pops up from time to time, not all of the time, but some of the time and usually trashing the prefs is the solution.

    My reason for posting this is to find out if others have seen this issue and hopefully, with a lot of positive thinking, maybe Apple will fix this, if its a common bug.

    _______________________________

    Wayne Carey
    Schazam Productions
    https://web.mac.com/schazamproductions
    schazamproductions@mac.com

  • Mark Maness

    May 23, 2010 at 3:16 am in reply to: Bad XDCAM HD Import Bug – FCP 7

    I have to admit… I would not have guessed or tried to export to XML v1 or v2. But, I’ll try that next time. Thanks for that tip.

    Now, the Batch List trick… That one has worked only sometimes for us. So, that one just added to my frustration.

    One would have probably thought that a newer version of the Sony software might have done the trick, but… nope… it doesn’t seem to matter. Therefore, it has to an FCP 7 issue.

    Thanks for the help, Andy. Sometimes it’s just good to vent.

    _______________________________

    Wayne Carey
    Schazam Productions
    https://web.mac.com/schazamproductions
    schazamproductions@mac.com

  • Mark Maness

    May 23, 2010 at 1:54 am in reply to: Bad XDCAM HD Import Bug – FCP 7

    Yes, we did, Andy. But as you can see, nothing hs been done about this serious error. We should we have to do this now when we did not go this pain in FCP 6. Can you expalin that?

    Is Apple not listening?

    _______________________________

    Wayne Carey
    Schazam Productions
    https://web.mac.com/schazamproductions
    schazamproductions@mac.com

  • Mark Maness

    May 20, 2010 at 1:57 pm in reply to: Bad XDCAM HD Import Bug – FCP 7

    Well, EX1 and EX3 footage is primarily listed as XDCAM EX and XDCAM HD is disc based footage.

    We are using the disc based format. And, I’m also using XDCAM Transfer 2.12.0 on Snow Leopard 10.6.3.

    The issue is that when FCP 7 became available, Apple decided for us that all XDCAM footage was card based with no option to recapture disc based. I say this because we still have a G5 system running FCP 6.0.6 and everything works great with it.

    Just try it. Import some XDCAM HD (disc based), delete the media and try to recapture into something like ProRes422 or DVCProHD (like we use, because of the fast render times).

    Here’s the ONLY work around for this crap… You have to take the clips you want to Batch Capture, copy them into a new project. Export out a Batch List. Open this Batch List into Excel and delete all of the data in the Pixel Aspect column. Save as a text file. Now, import that Batch List into FCP and Batch Capture works fine and all is good again. Except that you just wasted about 15 minutes on this work around.

    _______________________________

    Wayne Carey
    Schazam Productions
    https://web.mac.com/schazamproductions
    schazamproductions@mac.com

Page 19 of 212

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy