Forum Replies Created

Page 3 of 4
  • Sounds like a hardware solution version of screen scraping (ala Camtasia.) Probably works better than software only – Camtasia really falls down if you set the frame rate too high, and especially if it’s a rather large SWF. It, too, mostly looks blocky and such. You’d think an export from the Flash development environment itself would be the best bet – but it really doesn’t work very well either. It just may be the inherent differences between a computer and video. Sometimes ya just can’t mess with physics. Most often I find myself taping it myself.

  • Tim Mirande

    July 14, 2006 at 9:50 am in reply to: reassigning Preview Files???

    Thanks for the response. I’ve been tempted to try that but haven’t yet. Glad to hear that it works. Your point about backing up the project file is well taken. I generally back up the project file (even external to the auto backups that Premiere does itself) because I need multi-generational backups on my schedule. Just because I’m paranoid doesn’t mean they’re not really after me!

    Thanks again for the advice. I’ll try that this weekend to see how it works. This really seems like something that Adobe could rather easily add — and keep it safe for us.

    Regards,

    Tim

  • I’ve done a boatload of this kind of thing. There’s no easy answer to your question.

    I am generally given an SWF (small web format) Flash file created by a Flash developer and I need to either convert it to MPG1 (for delivery apprpriate for a PowerPoint presentation) or I need to incorporate the Flash piece into a larger video that demonstrates something or other. Obviously, they are looking for is a video that replicates the end-user experience that they see when the Flash piece is viewed on the web via a browser.

    There are a bunch of software packages that do this (swf2avi, etc.) You can Google find a lot. However, there isn’t one that always works. It depends on the techniques used by the Flash developer. It seems like the trickier they are, the less likey the conversion will go well. Some developers use a lot of scripting code to accomplish all kinds of fancy effects. Plus, they don’t normally use frame rates and sizes that are video friendly. Many times this means that the conversion program messes up the audio timing with the visuals, jerky video, etc. Keep in mind that the SWF isn’t truly compiled code. The browser still renders a fair amount on the fly, which is why a lot of converters can’t seem to duplicate the feel.

    Generally, I take an SWF, run it thru a couple of converters to see how they look. If they look good, I’ll use them. If not, I set up a nice large flat panel display and do it the old fashion way, I carefully set up the room lighting, white balance, zooming, etc. and video tape it (while capturing the sound.) This comes as close to capturing the typical end user experience as possible (if the converter fails to do a decent job.)

    This is at least my personal take – based on experience. My favorite definition of the word ‘experience’ is: Experience is what you get when you don’t get what you want.

    As always, your mileage may vary…

    Tim

  • Tim Mirande

    July 13, 2006 at 11:59 am in reply to: reassigning Preview Files???

    On a similar topic, in my workflow I like to begin projects with a base folder that has a few key pieces of info like the date, client, project number, such as: [d:\20060712-AbcCompany-005]. Under that folder, I use approprate folders for all the assets needed for that project (i.e. ..\Graphics, ..\Titles, etc.) I’m sure this isn’t a lot different than a lot of folks use. When the project is complete, I typically copy the whole folder to an archive drive (I currently use Maxtor OneTouch drives for this) Then, if a change is needed in the future, I simply copy the entire folder back to by main editing drive and I’m off and running. However, there are times when I’d like to change the base folder name to indicate that this is a new project with the appropriate date and code. I may even want to copy one client’s project as a starting point for an entirely new client & project. My question: is there any way to effect a name change en masse in the main project file? It seems that you have to do this one asset at a time & is cumbersome enough to make me not want to do that. Now that Premiere supports sequences, I generally have only one project file per client project (albeit with lots of sequences), so you would think a mass change to the XML project code wouldn’t be that big a deal.

    Does your previous answer follow for my question as well? That is, request a change to Adobe? Thanks for your help!

    Regards,

    Tim

  • Whoops. Check that. I mentioned I bought the 500 GB drive for $225.00. It was $325.00, not $225.00. Sorry, finger check…

    Tim

  • Hello Bruce,

    Okay, I’ve re-read all of your posts. I’m now thinking that you may have a bandwidth issue. Where is the DV clip located that you’re trying to copy to miniDV tape? Is it on an external firewire drive? If so, the symptoms you’re experiencing seem to be consistent with your system’s inability to both read the DV clip from the firewire port as well as pushing it out to tape.

    The system I’m currently using isn’t all that special. It’s a Dell Pentium 4, 3.4 GHz., 2 GB RAM, 2 400 GB internal 7200 RPM SATA drives, Canopus ADVC-300 analog to digital bridge, XP Pro with latest SP & patches. As I mentioned, I do use a lot of Maxtor firewire drives – but for storage and archival only, not for editing. I recall I had a similar issue when I tried to use a PreSonus Firebox (firewire) audio solution. It seemed like the system couldn’t keep up with both firewire driven audio as well as the ADVC-300. Flakey things were happening – stuttering video, out of synch audio, etc. – but again it was intermittent. No special drivers or codecs – just the MS-DV default.

    So, bottom line question is – are you copying your DV clip on an internal 7200 drive or trying to go from an external firewire drive? If external firewire, can you copy it to an internal drive and try again?

    You had also asked about my recent purchase of the Maxtor 500 GB drive. I bought it at Microcenter.
    (https://www.microcenter.com/byos/byos_single_product_results.phtml?product_id=234803)
    When I was in their store, they had it on the shelf for $225.00. I don’t know if that was a special price, as the online one is $334.00. Still, a good deal though. As I mentioned before, this model only connects via USB2, not my preferance, but I need the space.

    Hope this helps.

    Tim

  • Hello Bruce,

    Okay, I just tried copying a clip edited in Premiere Pro to my GL-2 using Scenalyzer 4.0. Worked like a charm. I also tried to do this using the Export to Tape option within Premiere Pro and was less than successful in doing this. I did get it to work once but I haven’t a clue what was different between the one that worked and the 5 times that failed. I suppose this goes back to whatever the problem Premiere Pro has with the GL-2 in general. However, it does work consistenly using Scenalyzer.

    The steps were very simple. First connect your GL-2 to your system via firewire. Next, fire up Scenalyzer. Click on the long button on the top (capture-folder) to navigate to the folder where your DV clip exists. When you do this, you’ll see thumnails of each DV clip in that folder in the main section of the screen. Select the clip(s) you want to copy to tape. Make sure the ‘enable recording’ checkbox is selected. Double click on the option: What can you do now/record the selected clips to tape. Press record on your GL-2 and answer the prompt. It seems to copy the clip(s) to the GL-2 without incident. I’m also led to believe that this is a frame accurate copy.

    Hope this helps.

    Tim

  • Aha! Gotcha. Now I know where you’re having your issue. When I return from some family fun today, I’ll get my GL-2 and dust off a miniDV tape and I’ll go thru the steps & document them for you. At this point, I know I’ve done it several times before but can’t recall the exact steps – and I don’t want to give you an misinformation. For some reason I thought you were having difficulty moving from the tape to the hard drive. Now I understand it’s the other way – from your final edit to another miniDV tape. Shouldn’t be a big deal.

    As an aside, there is a lot of info on the Cow regarding project archival. It’s a real issue for all of us, and considering the movement to high def, it only compounds the problem. I’ve been buying a lot of the Maxtor OneTouch drives lately to archive projects. I just bought a 500 GB drive for about $325. Unfortunately, this particular model only does USB2, not firewire – which in my tests is a lot faster. Of course, as you’ve mentioned, you can archive raw footage to inexpensive miniDV, but if you have the need to do future re-edits, you need to have all the project files (footage, transitions, pictures, titling, composites, etc.) I’ve also considered Iomega’s Rev drives but the cost per gig is still pretty high.

    Anyway, as I said I’ll get to your issue this evening. I’m actually looking forward to doing the test because of a project I’m currently working on. Back at ya later…

    Tim

  • Hello Bruce,

    To preface my comments, I’ll also mention that I now generally shoot using a Focus Enhancements FireStore FS-4 portable DTE recorder with my GL-2 instead of mini-DV tape. See (https://www.focusinfo.com/solutions/catalog.asp?id=3) It has saved me many hours of capture time. It still captures in the same DV-25 format, so there isn’t any change or loss by doing so. It can even record both the the hard drive as well as a tape for backup if desired.

    Prior to my purchase of the FS-4 I shot a load of miniDV tape and edited with Premiere, so hopefully I’ll be able to answer your questions. I’ve learned a truckload from others on this forum so if I can do my small part to help, I’m more than willing. This stuff changes about every 12 minutes so there’s no such thing as a stupid question.

    Let me try to address your questions one at a time.

    I’m not exactly sure what you’re saying here. Scenalyzer is a program that is a capture from tape and copy to tape utility. I believe that it only works with DV (specifically Microsoft DV) and not analog. With your GL-2, this should be no problem. Simply hook your GL-2 to your computer to a compliant 1394 port (aka firewire) and so long as your computer recognizes it, Scenalyzer should as well. At least that’s been my experience.

    So, the workflow is to essentially copy from miniDV tape to your hard drive, which yields MS-DV files. Import those files into Premiere’s bins. Edit as needed. Output/export as needed (DVD, DV, MPG-1, WMV, etc.)

    Rendering and preview files are simply Premiere’s way of storing intermediate files that have been ‘pre-rendered’ so it doesn’t have to do it again. This way it can keep things more in real time while editing and exporting. Depending upon what you’re doing, this can be a little time or a lot. There are hardware cards out there that can offload this (such as the Matrox RT.X2 or the Axio cards.) They’re a bit expensive but can sure save a load of time.

    I really don’t think Premiere’s rendering or preview files are a part of your problem.

    Sure, no problem. Yes, Scenalyzer has the watermark thing but only until you purchase the software – and as you indicated, it’s pretty inexpensive for what you get.

    Let me be clear about what Scenalyzer does. As I mentioned before, it’s designed to get your data off the miniDV tape and into your computer in a format in which Premiere can easily process. My understanding is that this is a lossless process. IOW, this is more a ‘copying’ process than an ‘encoding’ process.

    Here are the steps I’d recommend (not the only way but it works for me.) This is to copy the contents from the miniDV tape to your hard drive in DV format.

    1. Put your miniDV tape in read-only mode (always a prudent step)
    2. Rewind the tape
    3. Connect your GL-2 to the computer via firewire
    4. Put the GL-2 in Play/VCR mode
    5. Fire up Scenalyzer
    6. Scenalyzer has a fairly simple interface. On the top, you can select the capture folder. On the left, it gives you a simple list under “What can you do now?” If all things are connected properly, you should see “capture video to your harddisk” as one of the options. On the bottom of the screen, you’ll see a button that says “Capture”. You should also go to the File/Options section and make sure that the Capture Settings are “Type2 DV-AVI”. This is the default setting, I believe.
    7. Once you adjust the options and locations to your liking, press the “Capture” button
    8. Scenalyzer should read the contents of your tape and copy it to the hard drive. Note that the default behavior is to create a separate file for each time the start and stop button was used in recording. I really like this feature, as it makes it easy to delete out bad takes. You can index the tape first and then only capture the takes you want, but I find it’s easier to capture the whole enchalada to disc and delete and edit from there. I would also recommend checking the box called “Mute” while capturing, unless you want to hear what’s being captured.
    9. Your files should be located in the folder you indicated. There will be as many DV-AVI files as you have takes on the tape. It will also break large contiguous files (over 2 gigs, if memory serves) into separate files but with no frame loss. Simply stack them on the timeline and it will be just fine.

    Now, reversing this process (i.e. copying DV to miniDV tape) is just about as easy. You just need to check the box called “enable recording” and put your camera in record mode.

    No problem. If I didn’t address your exact problem just say so and I’ll try to take another crack at it.

    Tim

  • Hi Bruce,

    I’ve used a GL2 with Premiere (from 6.5 to Pro 2.0) and never could get Premiere to truly recognize it. Way back when, I went to a trade show and discussed the problem with Adobe and others. I finally tried a standalone product called Scenalyzer (https://www.scenalyzer.com/) and it works flawlessly with my GL2 via firewire – both directions. It’s inexpensive and works very well. I still don’t have a clue why an inexpensive product like Scenalyzer works with the GL2 and Premiere cannot. I guess since I have a reliable workflow, I’ve stopped complaining to Adobe. And, BTW, Premiere Pro 2.0 is much, much better than 6.5. If you can swing it, I’d certainly recommend the move up. HTH.

    Tim

Page 3 of 4

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