From Super 8 to FCP

Hi there,
I would like to use QT file that was made from a super 8 mm movie.
I don't know what settings were used to make the QT.
Could someone help me and tell me what would be the recommended settings to get the best results ?
I also have a question that is probably silly but ....let me try...
The movie was shot in 18fps.
Must I change the settings to take this frame speed into account or was it already taken care of when the QT was made ?
Many thanks in advance
Ivan

You could just import the QT file and drop it into the timeline.
If it is not one of the "usual" formats FCP will give an error message to that effect offering to change the sequence settings to match.
Accept the offer and see how the editing goes.
Regarding the 18fps of the original cine material, it all depends on how the QT file was made.
If a video camera was simply pointed at the movie screen your QT file will probably be NTSC DV shot at 30fps, in which case there will be no problems editing because the camera will have "altered" it to the appropriate 30fps (or 25fps if you are using PAL).
Actually the FCP settings are the least of your problems as even professionally copied 8mm film is somewhat dodgy and amateur copying can be quite appalling.
However, as these films are usually of long-gone members of the family, most people are not too concerned about quality as long as they can see their relatives.
Message was edited by: Ian R. Brown

Similar Messages

  • How to setup Compressor to create video from multiple sequences within FCP?

    I am wondering how I can set compressor up to create videos from multiple sequences within FCP. When I click file -> export - > compressor for a sequence and go into the program, it doesn't allow me to go back into FCP. I just get a spinning beach ball. Is there no way to set it up so I can prep a bunch of fcp sequences within compressor and then click submit and walk away? I have over 100 sequences that need to be exported so it would be a little difficult to do this one at a time. Thanks.

    Batch processing
    *Step one. Make sure everything in every sequence is rendered.*
    *Step two. Make a folder somewhere and name it something relevant.*
    *Step three. In FCP select all you sequences that you want to compress and right click (option), choose Batch Export from the contextual menu.*
    *Step three point one. In the batch export window click on settings and choose the folder you made in step two for the destination. Make sure Make Self-Contained is not check and include Audio and Video.*
    *Step four. Click export in the batch window.*
    Once that is done you can close FCP.
    Now in Compressor
    *Step five. Make a setting that will give you the output that you want (mpeg2, AC3, h.264, whatever). Make a destination for where you want to save the output.*
    *Step six. Make a droplet from the settings you made in step five.*
    You can quit Compressor now.
    *Step seven. Take the files that you batch exported from FCP in step three and four and drop them on the droplet you made in step six.*
    o| TOnyTOny |o

  • Cannot import voice over from garage band into FCP-X

    cannot import voice over from garage band into FCP-X

    Try:
    Share > Send Song to iTunes. In the dialog, turn OFF compress. That will create an .aiff version of your GB project.
    Alternately, you can Share to iTunes. When iTunes opens, right click on the selection and select Create AIFF version.
    When iTunes opens, right click on the selection and select Show In Finder -> drag it out to a more convenient location (or option-click-drag to make a duplicate in the new location you drag to.)
    Import that file into FCPX.

  • Problem importing footage from Canon XF305 into fcp

    I have footage from a card having recorded on a Canon XF305. I literally dragged and dropped card onto my desktop making sure not to change any file names. I am now trying to import this footage from my desktop into fcp. I have downloaded the canon fcp plugin but everytime I try to import the footage using the canon plugin preferences I get an error message which reads... "AA0229" contains unsupported media or has an invalid directory structure. Please choose a folder whose directory structure matches supported media. Can anyone help me??

    Hi there,
    I've had no joy with this. Have tried everything. Just can't get footage into fcp any way I try. I have downloaded the plugin but I still get the same error message. "AA0229" contains unsupported media or has an invalid directory structure. Please choose a folder whose directory structure matches supported media.
    My work flow is as follows.
    Open final cut pro. Go to log and transfer. Go to preferences within the log and transfer window and click on Canon XF plugin. Then go to import. Click on file on my desktop which is labeled as CLIPS001. Then error message comes up.
    Memory card was dropped directly onto my laptop and onto a back up drive without changing any file names. Was thinking this would be straight forward.
    Any help will be hugely appreciated. Am I missing something simple?

  • Upgrade to G5 and FCP 5 from a series of FCP upgrades, 1 through 4

    I will be upgrading to FCP 5 on a new G5. I bought FCP 1.1, and have steadily upgraded to FCP 2, 3 and 4. Since the new G5 will NOT have OS9, and since I would need OS9 to install FCP 1.1 in order to upgrade to 2, 3, 4, etc., will I be forced to buy a FULL version of FCP 5, rather than simply upgrading? Has anyone else worked around this problem? Thanks, Michael Lengel

    If you've bought the Final Cut Studio Upgrade, then
    you'll need the serial numbers for all the apps that
    were in Produciton Suite.
    Production Suite consisted of FCP HD, Motion 1, DVDSP
    3.
    An FCP 1, 2, or 3 serial number will not allow an
    upgrade to Final Cut Studio. Only an FCP HD serial
    number (which is the same as an FCP 4 serial number.)
    I'm afraid this is not entirely accurate, Brian.
    If you're buying the $499 FC Studio upgrade (aka 'from Production Suite'), then yes, you'll need to provide the serial numbers for the 3 apps.
    However, if you're buying the $699 FC Studio upgrade (aka 'from any verision of FCP'), then all you'll need to provide is your original, standalone FCP serial number.
    In my case, was the latter (upgrade from FCP) and my original serial number is from FCP 3. Since I did an erase and install of Tiger prior to installing FC Studio (aka no FCP on my system, just like a fresh G5), I was only asked for my FCP serial number. I plugged in my FCP 3 SN and was good to go.
    Of course, my original reply reflected the fact that Michael only mentions upgrading to FCP 5. (You're saying that path is different than upgrading to Studio, Brian?)

  • PROBLEM SOLVED "export clips from Color back into FCP & add transition"

    If I have two clips that you cannot place a transition in between here is the only thing that worked for me.
    I discovered this problem after I exported my movie clips from FCP 6 to Color and imported the color corrected files from Color back into FCP 6. I could no longer add transitions to any of my clips unless I made the following changes.
    1. 1st check to see if the video clip has an audio track underneath it. If they are not linked Select the audio and the video track to be linked, hit Command "L" and you will see an underline under the audio and video name to show that they are now linked. Do the same for the adjoining video and audio track.
    2. Next select all of the clips after the video clip you just selected by typing "tttt" this changes to the "Select All Tracks Forward Tool". Click on the track after the video track you just linked and it will select all of the tracks thereafter. Hit the "A" button to change back to the selection tool and move all of the selected tracks away from the previous video/audio track.
    3. Next type "RR" this will change to the "Ripple" tool. Now click on end of the video track on the previous video clip and type -15 (for negative 15 frames). Then click on the beginning of other video clip to the right that you linked and type +15 (for plus 15 frames).
    4. Type "tttt" to change back to the "Select All Tracks Forward Tool" the hit the "A" button to change back to the selection tool and drag all tracks back together again.
    5. You may then drag and drop your transition in between both video clips.
    I hope this helps someone...this is the only thing that worked for me!!!
    Number1talent

    I am working with mostly DVCPro ftg, with a few clips in MiniDV.  I did have roughly 10 clips with speed changes, but they exported fine two weeks ago, when I did this the first time.  (Actually, it didn't keep the speed changes, but it did export with media to FCP). 
    The clips do have reel numbers and seem to be of the right length per clip but there's just no picture and no assoicated media with which to relink the clip.
    I'm on Color 1.5.3
    Any possible ideas?  Thank you for your help...

  • How to fetch data from SUP

    Hello experts ,
    I am developing a po-list application using sybase unwired workspace 2.0 and Blackberry JDE .
    I have developed the mbo , generated the code for it and imported it in blackberry jde .
    I have followed the steps mentioned in reference guide for blackberry development .
    The application is getting build successfully but i am unable to see data anywhere .
    can anyone please help me with UI part in blackberry jde for displaying output fetching from sup .
    Thanks in advance .
    Rockky .

    I am not sure if the Sync method is working properly .
    One more thing i am able to see data in the output window of the blackberry jde but unable to see any data on simulator .
    Also there is some problem with synchronize method .
    In the output window it says "on synchronize is called with user context : null "
    Also it says "source code is not available" and the app comes out
    Please help .
    Badly stuck at this point
    Thanks for the replies !!
    Regards ,
    Rockky

  • Problem while pinging Webservice from SUP 2.0

    Hi ,
    i am developing an SUP application using webservices.
    I am unable to ping the webservice from SUP.
    Using the following webservice: [http://www.currencyserver.de/webservice/currencyserverwebservice.asmx?WSDL]
    I get the following error on pinging it.
    com.sybase.sup.tooling.xml.XmlException: java.net.UnknownHostException: www.currencyserver.de
    at com.sybase.sup.tooling.wsdl.WsdlParser.parseURL(WsdlParser.java:589)
    at com.sybase.sup.tooling.wsdl.WsdlParser.parse(WsdlParser.java:68)
    at com.sybase.uep.tooling.eis.WsEISOperationBuilder.<init>(WsEISOperationBuilder.java:70)
    at com.sybase.uep.tooling.eis.WsEISOperationBuilder.<init>(WsEISOperationBuilder.java:51)
    at com.sybase.uep.datasources.ws.views.WSConnection.initialize(WSConnection.java:154)
    at com.sybase.uep.datasources.ws.views.WSConnection.<init>(WSConnection.java:38)
    at com.sybase.uep.datasources.ws.views.WSConnectionFactory.createConnection(WSConnectionFactory.java:28)
    at org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(Unknown Source)
    at org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(Unknown Source)
    at org.eclipse.datatools.connectivity.ui.PingJob.createTestConnection(Unknown Source)
    at org.eclipse.datatools.connectivity.ui.PingJob.run(Unknown Source)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
    Caused by: java.net.UnknownHostException: www.currencyserver.de
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:195)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
    at java.net.Socket.connect(Socket.java:529)
    at java.net.Socket.connect(Socket.java:478)
    at sun.net.NetworkClient.doConnect(NetworkClient.java:163)
    at sun.net.www.http.HttpClient.openServer(HttpClient.java:394)
    at sun.net.www.http.HttpClient.openServer(HttpClient.java:529)
    at sun.net.www.http.HttpClient.<init>(HttpClient.java:233)
    at sun.net.www.http.HttpClient.New(HttpClient.java:306)
    at sun.net.www.http.HttpClient.New(HttpClient.java:323)
    at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:970)
    at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:911)
    at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:836)
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1172)
    at com.sybase.sup.tooling.wsdl.WsdlParser.parseURL(WsdlParser.java:578)
    Please let me know the solution.
    Regards,
    Jitendra Kansal

    Hi Guru,
    i saved that page in form of .WSDL file and it worked. thanks for it.
    but the problem is while creating MBO
    step 1. i selected a data type as webservice and connection profile CurrencyConversionServices
    step2. then i selected the "GetCurrencyvalue" operation that import a provider agency, a source and destination currency      and            exports the exvhange rate.
    step3. when i am giving some default values for
    provider >> "AVERAGE"
    Source Currency>> "ARS"
    Destination Currency>> "USD"
    when i am moving on next screen it is throwing the following error.
    Error occurred during execution, please check the default Values of the selected input parameters and refresh again.
    Reason:  www.currencyserver.de
    when i am clicking on Details to check it is showing...
    www.currencyserver.de
    www.currencyserver.de
      java.net.UnknownHostException: www.currencyserver.de
      java.net.PlainSocketImpl.connect(PlainSocketImpl.java:195)
      java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
      java.net.Socket.connect(Socket.java:529)
      java.net.Socket.connect(Socket.java:478)
      java.net.Socket.<init>(Socket.java:375)
      java.net.Socket.<init>(Socket.java:249)
      org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:79)
      org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:121)
      org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:706)
      org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1321)
      org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:386)
      org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
      org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
      org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
      org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:560)
      org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:199)
      org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:76)
      org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:400)
      org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:225)
      org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:435)
      org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:402)
      org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
      org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
      com.sybase.vader.da.ws.soap.SoapInteractionOperation.execute(SoapInteractionOperation.java:498)
      com.sybase.vader.statistics.MonitoringOperation.execute(MonitoringOperation.java:65)
      com.sybase.vader.service.interaction.PipelineCompositeInteractionOperation.execute(PipelineCompositeInteractionOperation.java:55)
      com.sybase.uep.tooling.eis.BaseEISOperation.execute(BaseEISOperation.java:265)
      com.sybase.uep.tooling.eis.BaseEISOperation.execute(BaseEISOperation.java:165)
      com.sybase.uep.tooling.eis.WsEISOperationImpl.execute(WsEISOperationImpl.java:808)
      com.sybase.uep.tooling.ui.ModelsUtil.getEEISOperationMetaData(ModelsUtil.java:255)
      com.sybase.uep.tooling.ui.mappertree.common.AttributesMapperDataBuilder.constructTargetRoot(AttributesMapperDataBuilder.java:104)
      com.sybase.uep.tooling.ui.mappertree.common.AbstractMapperDataBuilder.build(AbstractMapperDataBuilder.java:37)
      com.sybase.uep.tooling.ui.wizards.common.AttributesBottomUpWizard.createAttributes(AttributesBottomUpWizard.java:767)
      com.sybase.uep.tooling.ui.wizards.common.AttributesBottomUpWizard$3.run(AttributesBottomUpWizard.java:643)
      org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
    Regards,
    Jitendra

  • Can't capture HDV from Sony z1 on FCP 7

    Hi,
    I have set 'easy setup' to HDV (I have also tried HDV Fire wire basic) I've followed tutorial on all the set ups to capture.  But when I go to capture, FCP can control the play buttons and I can see the time code on screen but there is no picture or sound coming through to capture and is says 'Capture was aborted due to no incoming data from device'.
    I have checked everything.
    I followed all the suggestions in an older discussion in this forum -
    Unable to capture HDV footage with FCP 5.1
    This was the last post in that discussion: 
    "Re: Unable to capture HDV footage with FCP 5.1
    May 23, 2010 4:37 PM (in response to MrMajesticMole)
      I just got off the phone with a friend of mine who was having the same problem as you. Although you say the camera playback is set properly, please recheck this. go into your camera's playback menu>menu>standard set>VCR HDV/DV. Unplug your firewire from the camera. Make sure camera is set to HDV NOT auto. replace firewire cable. Now open FCP. Go in Audio/video settings>A/V devices (farthest tab on right). In box for playback edit to tape different from video output (make sure it's checked) mirrored (checked) Video playback 1080i50, Audio HDV. I hope that works now."
    I followed all these tips and nothing has changed.  This is the first time I am using HDV in FCP.  I have used the same Sony z1 camera to shoot and capture DV footage in my current FCP set up and I've had no problems.
    The only wierd thing is that under easy set up I selected HDV first with 'all rates' under frame rate.  When that didn't work I tried "HDV fire wire basic".  Then I tried to put the frame rate in a 50fps.  When nothing made any difference I put the frame rate back to all frame rates and while still on Format: HDV selected HDV 1080i50  and also have tried HDV 1080i50 with 'all frame rates' and everythime I go back, it's defaulted to  'HDV 720p50' in the 'use box and frame rate  50fps. 
    I would really appreciate help with this.

    Hi Russ,
    Thanks for getting back so quickly.
    I was feeling hopeful because I realised I had the fps rate set to 50 and when you said 25fps I thought that must be it.  Unfortunatly it hasn't worked at all.  It keeps saying there's no data incoming data from device, yet it acknowledges the timecode and I can control the camera from FCP.
    I double checked my settings and made sure the camera was on before launching FCP.  I am going to study the document you included to see if there is anything else I am doing that isn't working.  I am wondering if there are some audio settings mucking it up.
    If you have any other thoughts let me know.  I will let you know if I figure it out.
    Cheers,
    Carolyn

  • Importing a project FROM Premiere Pro to FCP - Any alternative to EDL ?

    Hi, when I google this issue - trying to get a project from Adobe Premiere Pro (for instance CS4) to Final Cut I am always terribly frustrated to find only references to the fact that APP imports XML (and now in 4.01 with better support for Final Cut Pro XML). But APP only exports EDL, and that is a very limited platform for talking accross the programs. Does any one have a better solution? Is there any external software for converting an APP project into XML? Can anyone hint as to why Adobe doesn't include "export to xml" in the export menu (like Final Cut Pro so elegantly does) other than fear of people taking their projects and running away to Final Cut Pro (which doesn't make any sense at all, and is no way of dealing with users' needs). Because it would seem that they only want us to be able to move stuff from FCP to APP. But what about us, who desperately need to move in the other direction?! Any light on this matter would be greatly appreciated.
    Cheers and a happy 2009.

    +I would indeed like to do this test. To what email do I send a zipped file to?+
    http://www.automaticduck.com/contact/
    +And also, if I may keep bothering you on this issue: Granted that APP projects are XML, still, Final Cut Pro projects and Avid Projects are NOT XML, they can just interact well with certain forms of XML (type 1,2,3 etc, but apparently not prproj), correct? (a curiosity)+
    Correct, Final Cut Pro project files and Avid project and bin files are not XML. Final Cut Pro has the ability to export and import XML files that are formatted as XML. XML is a flexible file format, the files can web pages, preference files, document files, just about anything. Apple has defined an XML format that can be used to interchange project data with Final Cut Pro. For a lot of good reasons it doesn't make sense for third parties to write or read FCP project files directly so Apple developed a method to write and read project data through another format. XML is an excellent choice because it is so easy to work with, XML files are simply text, easily read and edited and written. Avid systems use another file format for interchange with other manufacturers, AAF. AAF is not XML.
    A lot of editors first heard of "XML" via Final Cut Pro's use of it as an interchange format, so it isn't surprising that these editors equate XML with FCP. It is a bit pedantic of me to drive home the point, but I just want you to clearly understand the issue.

  • Ann: SuperReport - a new member from Super 1.7

    Announcement: Super 1.7 - an EJB/J2EE monitoring tool with
    SuperEnvironment
    SuperLogging
    SuperPeekPoke
    SuperStress
    has got a new member: SuperReport
    You can anomyously down load it free from:
    http://www.acelet.com.
    Super is a component based administration tool for EJB/J2ee.
    It provides built-in functionality as well as
    extensions, as SuperComponents. Users can install
    SuperComponents onto it, or uninstall them from it.
    Super has the following functions:
    * A J2EE/EJB monitor.
    * A gateway to EJB servers from different vendors.
    * A framework holding user defined SuperComponents.
    * A PeekPoke tool to read/write attributes from EJBs.
    * A full-featured logging/tracing tool for centralized, chronological logging.
    * A Stress test tool.
    * A global environment tool.
    * A report tool.
    It is written in pure Java.
    The current version support:
    * Universal servers.
    * Weblogic 5.1, 6.0
    * Weblogic 6.1 with EJB 2.
    What is new:
    Version 1.70 January 2002
    Enhancement:
    1. SuperLogging: Scope can dynamically change both for upgrade to downgrade (for
    weblogic 6.1, need download an application).
    2. Add alias names for log threshold as new Java suggests.
    3. New component: SuperReport.
    Change:
    1. SuperLogging: Log database parameters are specified in a properties file, instead
    of EJB's deployment descriptor. It is more convenient and it avoids some potential
    problems. No change for development, easier for administration.
    Bug fix:
    1. Add Source Path Panel now accepts both directory and jar file.
    2. Bug in SuperEnvironment example (for version 1.60 only).
    Version 1.60 December 2001
    Enhancement:
    1. SuperPeekPoke and SuperStress can use user defined dynamic argument list.
    2. Add timeout parameter to logging access.
    3. New installation program with A). Easy install. B). Remote command line install.
    4. Support EJB 2.0 for Weblogic 6.1.
    5. Support SuperPeekPoke, SuperEnvironment and SuperStress for Websphere 4.0 (SuperLogging
    was supported since version 1.5).
    Change:
    1. Poke: argument list is set at define time, not invoke time.
    2. Default log database change to server mode from web server mode, booting performance
    to 10-20 times.
    Bug fix:
    1. If the returned object is null, Peek did not handle it correctly.
    2. If the value was too big, TimeSeries chart did not handle it correctly. Now
    it can handle up to 1.0E300.
    3. Help message was difficult to access in installation program.
    4. Source code panel now both highlights and marks the line in question (before
    it was only highlight using JDK 1.2, not JDK 1.3).
    5. Delete an item on PeekPoke and add a new one generated an error.
    Version 1.50 August, 2001
    Enhancement:
    1. Source code level tracing supports EJB, JSP, java helper and other
    programs which are written in native languages (as long as you
    write correct log messages in your application).
    2. Redress supports JSP now.
    3. New installation with full help document: hope it will be easier.
    4. Support WebSphere 4.0
    Version 1.40 June, 2001
    Enhancement:
    1. Add SuperEnvironment which is a Kaleidoscope with TableView, TimeSeriesView
    and PieView for GlobalProperties.
    GlobalProperties is an open source program from Acelet.
    2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView and PieView.
    Changes:
    1. The structure of log database changed. You need delete old installation and
    install everything new.
    2. The format of time stamp of SuperLogging changed. It is not locale dependent:
    better for report utilities.
    3. Time stamp of SuperLogging added machine name: better for clustering environment.
    Bug fix:
    1. Under JDK 1.3, when you close Trace Panel, the timer may not be stopped and
    Style Panel may not show up.
    Version 1.30 May, 2001
    Enhancement:
    1. Add ConnectionPlugin support.
    2. Add support for Borland AppServer.
    Version 1.20 April, 2001
    Enhancement:
    1. Redress with option to save a backup file
    2. More data validation on Dump Panel.
    3. Add uninstall for Super itself.
    4. Add Log Database Panel for changing the log database parameters.
    5. Register Class: you can type in name or browse on file system.
    6. New tour with new examples.
    Bug fix:
    1. Redress: save file may fail.
    2. Install Bean: some may fail due to missing manifest file. Now, it is treated
    as foreign beans.
    3. Installation: Both installServerSideLibrary and installLogDatabase can be worked
    on the original file, do not need copy to a temporary directory anymore.
    4. PeekPoke: if there is no stub available, JNDI list would be empty for Weblogic5-6.
    Now it pick up all availble ones and give warning messages.
    5. Stress: Launch>Save>Cancel generated a null pointer exception.
    Changes:
    1. installLogDatabase has been changed from .zip file to .jar file.
    2. SuperLogging: If the log database is broken, the log methods will not try to
    access the log database. It is consistent with the document now.
    3. SuperLogging will not read system properties now. You can put log database
    parameters in SuperLoggingEJB's deployment descriptor.
    Version 1.10 Feb., 2001
    Enhancement:
    1. Re-written PeekPoke with Save/Restore functions.
    2. New SuperComponent: SuperStress for stress test.
    3. Set a mark at the highlighted line on<font size=+0> the Source Code
    Panel (as a work-a-round for JDK 1.3).</font>
    4. Add support for WebLogic 6.0
    Bug fix:
    1. Uninstall bean does physically delete the jar file now.
    2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
    Version 1.00 Oct., 2000
    Enhancement:
    1. Support Universal server (virtual all EJB servers).
    2. Add Lost and Found for JNDI names, in case you need it.
    3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDI name (mainly
    for Envoys which do not support JNDI list).
    Version 0.90: Sept, 2000
    Enhancement:
    1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
    and alike) as input values.
    2. Reworked help documents.
    Bug fix:
    1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
    further time-out.
    2. MDI related bugs under JDK 1.3.
    Version 0.80: Aug, 2000
    Enhancement:
    1. With full-featured SuperLogging.
    Version 0.72: July, 2000
    Bug fix:
    1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
    Version 0.71: July, 2000
    Enhancement:
    1. Re-worked peek algorithm, doing better for concurent use.
    2. Add cacellable Wait dialog, showing Super is busy.
    3. Add Stop button on Peek Panel.
    4. Add undeploy example button.
    Bug fix:
    1. Deletion on Peek Panel may cause error under JDK 1.3. Now it works for both
    1.2 and 1.3
    Version 0.70: July, 2000
    Enhancement:
    1. PeekPoke EJBs without programming.
    Bug fix:
    1. Did not show many windows under JDK 1.3. Now it works for both 1.2 and 1.3
    Changes:
    1. All changes are backward compatible, but you may need to recompile monitor
    windows defined by you.
    Version 0.61: June, 2000
    Bug fix:
    1. First time if you choose BUFFER as logging device, message will not show.
    2. Fixed LoggingPanel related bugs.
    Version 0.60: May, 2000
    Enhancement:
    1. Add DATABASE as a logging device for persistent logging message.
    2. Made alertInterval configurable.
    3. Made pace for tracing configurable.
    Bug fix:
    1. Fixed many bugs.
    Version 0.51, 0.52 and 0.53: April, 2000
    Enhancement:
    1. Add support to Weblogic 5.1 (support for Logging/Tracing and
    user defined GUI window, not support for regular monitoring).
    Bug fix:
    1. Context sensitive help is available for most of windows: press F1.
    2. Fix installation related problems.
    Version 0.50: April, 2000
    Enhancement:
    1. Use JavaHelp for help system.
    2. Add shutdown functionality for J2EE.
    3. Add support to Weblogic 4.5 (support for Logging/Tracing and
    user defined GUI window, not support for regular monitoring).
    Bug fix:
    1. Better exception handling for null Application.
    Version 0.40: March, 2000
    Enhancement:
    1.New installation program, solves installation related problems.
    2. Installation deploys AceletSuperApp application.
    3. Add deploy/undeploy facilities.
    4. Add EJB and application lists.
    Change:
    1.SimpleMonitorInterface: now more simple.
    Version 0.30: January, 2000
    Enhancement:
    1. Add realm support to J2EE
    2. Come with installation program: you just install what you want
    the first time you run Super.
    Version 0.20: January, 2000
    Enhancement:
    Add support to J2EE Sun-RI.
    Change:
    1. Replace logging device "file" with "buffer" to be
    compliant to EJB 1.1. Your code do not need to change.
    Version 0.10: December, 1999
    Enhancement:
    1. provide SimpleMonitorInterface, so GUI experience is
    not necessary for developing most monitoring applications.
    2. Sortable table for table based windows by mouse
    click (left or right).
    Version 0.01 November., 1999:
    1. Bug fix: An exception thrown when log file is large.
    2. Enhancement: Add tour section in Help information.
    Version 0.00: October, 1999
    Thanks.

    Announcement: Super 1.7 - an EJB/J2EE monitoring tool with
    SuperEnvironment
    SuperLogging
    SuperPeekPoke
    SuperStress
    has got a new member: SuperReport
    You can anomyously down load it free from:
    http://www.acelet.com.
    Super is a component based administration tool for EJB/J2ee.
    It provides built-in functionality as well as
    extensions, as SuperComponents. Users can install
    SuperComponents onto it, or uninstall them from it.
    Super has the following functions:
    * A J2EE/EJB monitor.
    * A gateway to EJB servers from different vendors.
    * A framework holding user defined SuperComponents.
    * A PeekPoke tool to read/write attributes from EJBs.
    * A full-featured logging/tracing tool for centralized, chronological logging.
    * A Stress test tool.
    * A global environment tool.
    * A report tool.
    It is written in pure Java.
    The current version support:
    * Universal servers.
    * Weblogic 5.1, 6.0
    * Weblogic 6.1 with EJB 2.
    What is new:
    Version 1.70 January 2002
    Enhancement:
    1. SuperLogging: Scope can dynamically change both for upgrade to downgrade (for
    weblogic 6.1, need download an application).
    2. Add alias names for log threshold as new Java suggests.
    3. New component: SuperReport.
    Change:
    1. SuperLogging: Log database parameters are specified in a properties file, instead
    of EJB's deployment descriptor. It is more convenient and it avoids some potential
    problems. No change for development, easier for administration.
    Bug fix:
    1. Add Source Path Panel now accepts both directory and jar file.
    2. Bug in SuperEnvironment example (for version 1.60 only).
    Version 1.60 December 2001
    Enhancement:
    1. SuperPeekPoke and SuperStress can use user defined dynamic argument list.
    2. Add timeout parameter to logging access.
    3. New installation program with A). Easy install. B). Remote command line install.
    4. Support EJB 2.0 for Weblogic 6.1.
    5. Support SuperPeekPoke, SuperEnvironment and SuperStress for Websphere 4.0 (SuperLogging
    was supported since version 1.5).
    Change:
    1. Poke: argument list is set at define time, not invoke time.
    2. Default log database change to server mode from web server mode, booting performance
    to 10-20 times.
    Bug fix:
    1. If the returned object is null, Peek did not handle it correctly.
    2. If the value was too big, TimeSeries chart did not handle it correctly. Now
    it can handle up to 1.0E300.
    3. Help message was difficult to access in installation program.
    4. Source code panel now both highlights and marks the line in question (before
    it was only highlight using JDK 1.2, not JDK 1.3).
    5. Delete an item on PeekPoke and add a new one generated an error.
    Version 1.50 August, 2001
    Enhancement:
    1. Source code level tracing supports EJB, JSP, java helper and other
    programs which are written in native languages (as long as you
    write correct log messages in your application).
    2. Redress supports JSP now.
    3. New installation with full help document: hope it will be easier.
    4. Support WebSphere 4.0
    Version 1.40 June, 2001
    Enhancement:
    1. Add SuperEnvironment which is a Kaleidoscope with TableView, TimeSeriesView
    and PieView for GlobalProperties.
    GlobalProperties is an open source program from Acelet.
    2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView and PieView.
    Changes:
    1. The structure of log database changed. You need delete old installation and
    install everything new.
    2. The format of time stamp of SuperLogging changed. It is not locale dependent:
    better for report utilities.
    3. Time stamp of SuperLogging added machine name: better for clustering environment.
    Bug fix:
    1. Under JDK 1.3, when you close Trace Panel, the timer may not be stopped and
    Style Panel may not show up.
    Version 1.30 May, 2001
    Enhancement:
    1. Add ConnectionPlugin support.
    2. Add support for Borland AppServer.
    Version 1.20 April, 2001
    Enhancement:
    1. Redress with option to save a backup file
    2. More data validation on Dump Panel.
    3. Add uninstall for Super itself.
    4. Add Log Database Panel for changing the log database parameters.
    5. Register Class: you can type in name or browse on file system.
    6. New tour with new examples.
    Bug fix:
    1. Redress: save file may fail.
    2. Install Bean: some may fail due to missing manifest file. Now, it is treated
    as foreign beans.
    3. Installation: Both installServerSideLibrary and installLogDatabase can be worked
    on the original file, do not need copy to a temporary directory anymore.
    4. PeekPoke: if there is no stub available, JNDI list would be empty for Weblogic5-6.
    Now it pick up all availble ones and give warning messages.
    5. Stress: Launch>Save>Cancel generated a null pointer exception.
    Changes:
    1. installLogDatabase has been changed from .zip file to .jar file.
    2. SuperLogging: If the log database is broken, the log methods will not try to
    access the log database. It is consistent with the document now.
    3. SuperLogging will not read system properties now. You can put log database
    parameters in SuperLoggingEJB's deployment descriptor.
    Version 1.10 Feb., 2001
    Enhancement:
    1. Re-written PeekPoke with Save/Restore functions.
    2. New SuperComponent: SuperStress for stress test.
    3. Set a mark at the highlighted line on<font size=+0> the Source Code
    Panel (as a work-a-round for JDK 1.3).</font>
    4. Add support for WebLogic 6.0
    Bug fix:
    1. Uninstall bean does physically delete the jar file now.
    2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
    Version 1.00 Oct., 2000
    Enhancement:
    1. Support Universal server (virtual all EJB servers).
    2. Add Lost and Found for JNDI names, in case you need it.
    3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDI name (mainly
    for Envoys which do not support JNDI list).
    Version 0.90: Sept, 2000
    Enhancement:
    1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
    and alike) as input values.
    2. Reworked help documents.
    Bug fix:
    1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
    further time-out.
    2. MDI related bugs under JDK 1.3.
    Version 0.80: Aug, 2000
    Enhancement:
    1. With full-featured SuperLogging.
    Version 0.72: July, 2000
    Bug fix:
    1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
    Version 0.71: July, 2000
    Enhancement:
    1. Re-worked peek algorithm, doing better for concurent use.
    2. Add cacellable Wait dialog, showing Super is busy.
    3. Add Stop button on Peek Panel.
    4. Add undeploy example button.
    Bug fix:
    1. Deletion on Peek Panel may cause error under JDK 1.3. Now it works for both
    1.2 and 1.3
    Version 0.70: July, 2000
    Enhancement:
    1. PeekPoke EJBs without programming.
    Bug fix:
    1. Did not show many windows under JDK 1.3. Now it works for both 1.2 and 1.3
    Changes:
    1. All changes are backward compatible, but you may need to recompile monitor
    windows defined by you.
    Version 0.61: June, 2000
    Bug fix:
    1. First time if you choose BUFFER as logging device, message will not show.
    2. Fixed LoggingPanel related bugs.
    Version 0.60: May, 2000
    Enhancement:
    1. Add DATABASE as a logging device for persistent logging message.
    2. Made alertInterval configurable.
    3. Made pace for tracing configurable.
    Bug fix:
    1. Fixed many bugs.
    Version 0.51, 0.52 and 0.53: April, 2000
    Enhancement:
    1. Add support to Weblogic 5.1 (support for Logging/Tracing and
    user defined GUI window, not support for regular monitoring).
    Bug fix:
    1. Context sensitive help is available for most of windows: press F1.
    2. Fix installation related problems.
    Version 0.50: April, 2000
    Enhancement:
    1. Use JavaHelp for help system.
    2. Add shutdown functionality for J2EE.
    3. Add support to Weblogic 4.5 (support for Logging/Tracing and
    user defined GUI window, not support for regular monitoring).
    Bug fix:
    1. Better exception handling for null Application.
    Version 0.40: March, 2000
    Enhancement:
    1.New installation program, solves installation related problems.
    2. Installation deploys AceletSuperApp application.
    3. Add deploy/undeploy facilities.
    4. Add EJB and application lists.
    Change:
    1.SimpleMonitorInterface: now more simple.
    Version 0.30: January, 2000
    Enhancement:
    1. Add realm support to J2EE
    2. Come with installation program: you just install what you want
    the first time you run Super.
    Version 0.20: January, 2000
    Enhancement:
    Add support to J2EE Sun-RI.
    Change:
    1. Replace logging device "file" with "buffer" to be
    compliant to EJB 1.1. Your code do not need to change.
    Version 0.10: December, 1999
    Enhancement:
    1. provide SimpleMonitorInterface, so GUI experience is
    not necessary for developing most monitoring applications.
    2. Sortable table for table based windows by mouse
    click (left or right).
    Version 0.01 November., 1999:
    1. Bug fix: An exception thrown when log file is large.
    2. Enhancement: Add tour section in Help information.
    Version 0.00: October, 1999
    Thanks.

  • Problem about .xml file from PPro CS5 to FCP with RED and P2 file.

    I have create a Project in Premiere Pro CS5.
    I import the RED file R3D or P2  file XMF and editing my media.
    From menù File i select Export to "Final Cut Pro XML.."
    I open FCP and Import file XML but the media are not reconnect.
    "Warrnig: Non-critical error were found while processing an XML document.
    Would you like to see a log of these error now?"
    I want see the log file and...
    "<file>: Unable to attach specified media file to new clip."
    Where is the problem?

    Hi Dennis I re-format my MACPRO 8 Core and I installed Final Cut Studio Suite and CS5 Premium (no CS4)
    I install Blackmagick driver Decklink 7.6.3
    If I open the After Effects  and setting preview card blackmagic, I see the preview in external monitor.
    If I open the Premiere Pro and setting preview, I don't see the blackmagic card but the second monitor, DV....etc.
    In Premiere I see the blackmagic preset, but no the preview card.
    I have a second question.
    About Red file I want editing in Premiere Pro and i whant color correct in Apple Color from FCP.
    My problem is: my color program crash when I send file form FCP to Color (random mode)
    The sequence is:
    I import file red in PPro5 -- editing file --- export file xml.
    Close the PPro5.
    Open FCP import xml (no re-link media)
    Save de project in FCP
    Select sequence and send to Color.
    In this moment the Apple Color crash.
    I shutdown the MAC.
    I power-up the MAC
    Open FCP select the project and send the sequence to Color.
    Color see the project but no media.
    I re link the media and I editing in color my media.
    Why Apple Color program crash?
    Sorry for my English
    Many Thanks
    Distinti saluti
    Gianluca Cordioli
    Alchemy Studio'S di Gianluca Cordioli
    Via Pacinotti 24/B
    37135 VERONA
    cell.:+39 3385880683
    [email protected]
    www.alchemystudios.it

  • Importing video from Sony HDR-CX410 FCP 6.0.6 will not recognise AVCHD files. what is the solution?

    First I have to admit I'm not technical in any way so I'm easily confused so please forgive me if my question sounds unprofessional.
    The computer is a Mac desk top tower with Lion OS x 2x2.66 GHz Dual-Core Intel Xeon with an  internal hard drive plus a number of remote hard drives.
    I'm using Final cut pro 6.0.6 to edit video.
    The question is, up until now I've been using material shot on mini DV tapes, then digitised into the computer via the camera. As this format is getting long in the tooth I decided to get one of the latest DVCAM cameras, I went for the Sony HDR-CX410.
    It was not until I had purchased the camera & shot a few test seq. & then tried to down load into the computer that I found out that Final cut does not recognise the AVCHD files on the SD card.I've tried importing from the camera as well as a card reader with no result.
    I've looked at a number of sites including Apple support community where it looks like this is a major issue for many people but I can't find anyone who is using the same camera. I wondered if this issue is something you have covered in the magazine, if so please let me know which copy, if not can you help in any way. It appears that Final cut proX may be able to translate the AVCHD files but I'm not sure. Am I right in thinking that if I do upgrade to FCPX I will still have to convert the files, if so would you recommend a suitable software program.  Is there any reason why Apple make it so difficult to edit this AVCHD format when all the latest cameras are using it, perhaps its time to change back to a PC?

    Eric,
    FCP 6.0.2 (compared to previous version) comes with the latest improvement and support for AVCHD.
    However, here is a suggestion:
    In Log&Transfer (top frame) on the right of *search field* there are three buttons, click on the one showing a little arrow-down and a sort of little star. Choose preferences then in the *transcode to* section click on those two tiny arrows pointing one up and the other down and choose Apple Intermediate Codec. Can you now transfer? (Add selection to queue)
    Once again 6.0.2 might provide better support for your camera.
    Use the search tool for more info.
    G.
    PS. Please note that some people have had problems with 6.0.2 so get us much info as you can before updating.

  • How do I restore a new Hard drive from Super Duper clone ?

    The Hard Drive in my 2010 iMac died and was replaced with a new one. Thankfully I have a clone made with Super Duper of the old drive. Do I just clone back on to the new internal drive ? The new drive, installed by Apple has OS10.6.8 installed on it now (by Apple ), which is the OS on the clone. Do I need to completely wipe the drive before restoring with my clone ? All that's on the new drive is the OS. Don't want to make any mistakes here.....

    1. Boot from your install DVD or Bootable Clone and open Disk Utility.
    2. Highlight the new HD in the list of drives and select the Partition tab.
    3. Under Volume Scheme select 1 Partition and click on the Options... button.
    4. Select GUID Partition Table in the drop down window and click OK.
    5. Set the Format to Mac OS Extended (Journaled) and click the Apply button.
    6. Once thats done then you can do a clean Install, restore from TM or the Bootable Clone.

  • Is there a way to transfer video from Aperture 3 to FCP 7?

    When i first recieved my SLR i transferred all my video to aperture 3, thinking it'd be easy to connect it to FCP 7...while it is, i realize the codec differences/it lagging when i try to edit the footage. it's frustrating! I've since realized that Logging and Transferring is the way to go, editing is a lot smoother that way.
    Is there any way I can get those video from aperture (v3) to Final Cut Pro 7? I don't have the original files anymore so the ones in the Aperture Library is all i've got left!
    please help!

    Not within iTunes, no. You'd need to use other software to do that (QT Pro, for example).

Maybe you are looking for