How to watch HDV 1080i50, Integer (Big Endian), Timecode, QT exp. from FCP

Hi,
i have the above named files but cant watch them at all. They are exported from FCPro to QT; i only have FCpro 4.1 which does not open or import the files. I cant find any ways to watch these files, but need to open and extract stills from them. Audio is played, but only black screen. I tried perian etc, nothing openes the files correctly. Thanks

Sorry, you either going to need FCP 5 or 6 to work with these videos.

Similar Messages

  • Codec:HDV1080i60, integer (Big Endian), Timecode

    I want to play quicktime files. I have Quicktime Pro, but when I play my files, I can hear audio but not see video. The screen is blank white. the codec is: HDV1080i60, Integer (Big Endian), Timecode.
    Does anyone know a plug-in that will resolve this issue?
    thanks.

    HD formats require more ommph than your G4 can muster. 1080i requires at least a dual G5.
    The codec was probably set using Final Cut or some other high end video editor and is too "raw". Normally QuickTime would use the Apple Intermediate codec to help convert it for viewing.
    The data rate for your file is probably in the 30 to 50 MB's per second rate. Almost ten times more than regular DVD's.

  • Problem with Integer (Big Endian) XD Cam EX 1080i60 Codec

    I am trying to open up .mov files created with the Integer (Big Endian) XD Cam EX 1080i codec. I am running version 4.5 of FCP and my OS is Mac OS X 10.4.11.
    Is there a cost effective way for me to upgrade and have the ability to edit these files in FCP? If I upgrade to QT7Pro will that fix it? Will I even be able to run QT7Pro on Mac OSX 10.4.11?
    I have been racking my brain trying to figure out a fix, the footage is for my brother's wedding and I am strapped for cash, this was going to be my wedding gift to him.

    I am trying to open up .mov files created with the Integer (Big Endian) XD Cam EX 1080i codec. I am running version 4.5 of FCP
    Not gonna happen. That camera and format were made YEARS after 4.5 came out. There is no way you will get that raw footage to work on your version of FCP. ONly if someone else converts the footage to DVCPRO HD will it work.
    Is there a cost effective way for me to upgrade and have the ability to edit these files in FCP?
    Buy a used copy of FCS2, that includes FCP 6. That is the cheapest way. Or, find someone who has that and can read the files, and convert to DVCPRO HD for you.
    If I upgrade to QT7Pro will that fix it?
    Nope.
    Will I even be able to run QT7Pro on Mac OSX 10.4.11?
    Yeah, but that won't solve it.
    Sorry, the only solutions are upgrade or get someone to convert the footage for you. Not to XDCAM Qt files, nor to ProRes...FCP 4.5 won't be able to read those formats either. DVCPRO HD is the only solution if you stick with that version.
    Shane

  • How to judge the platform is little or big endian ?

    I have a c code, but anybody has a Java code?
    Thanks.
    #include <stdio.h>
    //little-endian or big-endian
    bool IsLittleEndian()
    int i = 1;
    char* p = (char*)&i;
    return *p;
    int main()
    if(IsLittleEndian())
      printf("LittleEndian\n");
    else
      printf("BigEndian\n");
    return 0;
    }

    http://www.codeproject.com/cpp/endianness.asp
    I got one, but how to translate into Java code.
    Auto detecting the correct Endian format of a data file
    Suppose you are developing a Windows application that imports Nuclear Magnetic Resonance (NMR) spectra. High resolution NMR files are generally recorded in Silicon or Sun Workstations but recently Windows or Linux based spectrometers are emerging as practical substitutes. It turns out that you will need to know in advance the Endian format of the file to parse correctly all the information. Here are some practical guidelines you can follow to decipher the correct Endianness of a data file:
    Typically, the binary file includes a header with the information about the Endian format.
    If the header is not present , you can guess the Endian format if you know the native format of the computer from which the file comes from. For instance, if the file was created in a Sun Workstation, the Endian format will most likely be Big-Endian.
    If none of the above points apply, the Endian format can be determined by trial and error. For example, if after reading the file assuming one format, the spectrum does not make sense, you will know that you have to use the other format.
    If the data points in the file are in floating point format (double), then the _isnan() function can be of some help to determine the Endian format. For example:
    double dValue;
    FILE* fp;
    fread(&nValue, 1, sizeof(double), fp);
    bool bByteSwap = _isnan(dValue) ? true : falseNote that this method does only guarantee that the byte swap operation is required if _isnan() returns a nonzero value (TRUE); if it returns 0 (FALSE), then it is not possible to know the correct Endian format without further information.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • HDV 1080i50 to SD MASTER Workflow

    Hello all.
    I am working now on a documentary, shot on Sony HDV 1080i50, 70 hours material, to be delivered in DIGIBETA PAL, and I am looking to the best approach to edit and finish it. Coming from the AVID World (yes, I confess...) and having worked not so much with FCP, I really need some help with this project. I will tell you what I do have in mind, and I kindly ask you to tell me if I am crazy or it makes some sense. I do have some specific questions as well. Thank you for your help. Here is my plan:
    1 – CAPTURE.
    70 hours captured in DV (already have!) in order to monitor easyly and work without long GOP.
    2 – OFF LINE EDITING.
    Normal documentary editing. I will zoom/resize the picture a lot. As I shoot in HDV and will deliver in SD PAL, I understand I have a big margin to zoom in an image without any quality loss when downsizing back to PAL. For instance, I only made one wide shot for the interviews. I will use this shot and then zoom the picture for a close up of the face... That is the main idea. How should I do these frame resizes, direct with FCP or should I use some special plug in?
    3 – ONLINE.
    Recapture all material in the Sequence in HD. Now I do not know if I should do it on HDV (remember: we are going back to SD for output) or should I use one of the PRORES 422 Apple codecs. What do you think? All the frame resizes and picture effects will be kept on the recapture, or?
    4 – IMAGE FINISHING.
    Do the colour correction and image finishing (with the HD material). Control and finish all the image movements, zooms and resizes. Apply effects, we do have to make some face blur and things like that. Should I do the colour correction on HD or should I make it once I have already downsized to SD, after step 5?
    5 – RENDER TO SD FOR OUTPUT.
    Here I do not know how to do it, but I want to convert my HD (HDV or PRORES 422) Sequence to an SD Uncompressed PAL 4:2:2 10bit Sequence. How do I do this? Here I do not have nay idea… Could you please help me? Will all the resizes and zoom be kept with the correct resolution when I downsize?
    6 – AUDIO FINISHING.
    Audio mixing and audio effects.
    7 – OUTPUT IN SD
    Export of a Quicktime SD Uncompressed PAL 4:2:2 with 10bit and print to tape.
    Should I export direct from FCP or use Compressor or something?
    That’s it!
    Please, I would ask you to take some time an help me. If thewe is something that is not clear or you need more information, fell free to write me or post and I will answer as soon as I can. Thanks again.

    Fantin,
    Not the exact answer to your question but hopefully helpful.
    My workflow with HDV is as follows:
    -Capture as HDV (same data rate as DV so might as well)
    -Do a basic picture edit, avoiding anything fancy (long render times with long GOP as you know)
    -Use Media manager to up convert to DVCProHD
    -Apply all my dissolves, effects etc.
    -Do sound mix in FCP
    -Use FCP and Color to grade
    -Export to SD DVD using Compressor via FCP timeline.
    or you could presumably
    -Drop onto tape using a Kona or Blacmagic card
    Don't think you'll get any better quality going 10 bit uncompressed if you're starting with HDV - might as well stick with DVCProHD.
    In terms of zooming into HDV footage to achieve a good quality SD frame, Im not sure the method above would accommodate that. I've always done this in the past by dropping my HDV footage directly into an SD timeline and then zooming from there - this might mean of course that you'll need to export you're entire project as DV50 Anamorphic and then replace the zoomed in wide shots onto that.
    I suspect if you just zoom into the HDV on a HDV or ProRes timeline this wouldn't translate well in SD.

  • What is Little Endian / Big Endian in Sound settings for Apple Intermediate

    Hi.
    In Final Cut Express, I am trying to splice together multiple video clips, combining footage from:
    1) HDV camcorder imported into iMovie 08 as 960 x 540 (the "lower resolution" option from iMovie '08 import), 16-bit @ 48 KHz (Big Endian), 25 FPS
    2) AVI files (DiVX 512 x 384, MP3 at 44.1 KHz, 23.98 FPS)
    3) Canon Camera "movie" files (Apple OpenDML JPEG 640 x 480, 16-bit Little Endian, Mono @ 44.1 KHz, 30 FPS)
    Questions
    1) What is this little endian / big endian thing?
    2) What is the best codec for me to edit in? My targets are NTSC DVD and also a HD version served via iPod connected to HDTV.
    I am not sure what codec to convert everything to, so that I can edit without having to RENDER every time I do something. I tried to export using QuickTime Pro to convert to Apple Intermediate Codec but am not sure about the option for "Little Endian" (I am using an Intel Mac; I assume I do NOT use little endian? Can someone help clarify?)
    Many thanks!!!

    1. They're compression formats. Different codec use different compression schemes.
    2. You should convert your material to QuickTime using the appropriate DV codec and frame rate.
    None of your material is HD. Some of it is low resolution, lower than even DV. There is no good way to make this material HD.

  • Mathscript: read big-endian & case lists

    Hi all,
    I'm using a MathScript node to read contents from a file. The binary data is stored as big-endian floats, but I only figured out how to read little-endian data.
    In Matlab you can specifiy the number formatting when opening a file using fopen. In MathScript I didn't see any option for that, neither in fopen nor in fread. Is there a way to read big-endian floating point data?
    Second question, I use a switch/case statement. In Matlab I can specify lists of items to match in a case, is there a way to do this in MathScript?
    Something like this (a is a string):
    switch a
    case {'a', 'b'}
    Thanks,
    Daniel

    Hello Daniel,
    Currently the MathScript fopen function does not support the different options to specify reading data in big- or little-endian format.  I will file a bug report to add those options.
    When specifying multiple options for a case, the cell array syntax is used.  Currently, MathScript does not support cell arrays.  As a workaround, you can duplicate your cases for each option.
    Grant M.
    Staff Software Engineer | LabVIEW Math & Signal Processing | National Instruments

  • Compressor settings for HDV 1080i50?

    hi,
    i have to export 1h30 of HDV 1080i50 to make it play on a dvd.
    could you, please give me some suggestions how to make this?

    ok...this is my first use of this kind of material and i don't know witch compressor settings i could use.is it possible to burn an HD DVD with my imac or i can use a SD DVD preserving a maximum quality? the answer will determinate the compressor settings i could use... for know i have tried,the last 4 days, to use H.264 so it can fit into a sd dvd (changing the average bit rate) but after more than 24h the encoding process is 1/4 of the entire video...and i've stopped it. i don't know if it's a normal to take soo much time or if i'm making a mistake doing it.so please, help

  • New line in Big Endian format

    How do I represent a new line character in Big-Endian format ? I have a third party utility which reads a text file in Big Endian format. I am creating this text file with one word per line kind of format. When I try to add a new line
    using
    FileOutputStream fs = new FileOutputStream(fileName);
    PrintStream pos = new PrintStream(fs, true,"UTF-16BE");
    inside a while loop(
    // get each word and write to file
    pos.print(word);
    ********* I want to add a new line to this file after every word.
    If I use a '\n' its creating wierd characater inside the file
    If I use the property line.seperator, its causing the same as above
    println also gives the trouble
    I am looking for the new line string or char in Big Endian format
    Any ideas ? Thanks in advance

    In ANSI, if I'm not mistaken a \n is represented by
    Carriage Return(CR) as a character.
    While in unicode \n is a combination of a Carriage
    Return(CR) and Line Feed(LF) which
    shows up as a rectangle.I'm afraid you are mistaken: '\n' is the line feed character (LF) and '\r' is the carriage return character (CR). They are single characters, neither is a combination of two other characters. There is no difference between Unicode and ANSI ASCII here.
    And besides, it is the line feed character that appears as a block in MS Notepad if a carriage return character doesn't precede it. The only line separator that MS Notepad accepts is "\r\n".

  • Is Labview handling automatically big endianness?

    I am working with a Labview Application that communicates through a serial line with another computer. I am using VISA subroutines.
    My PC has an Intel processor which is Little Endian. I have read that Labview is Big Endian. My question is: Is Labview handling automatically the endianness of the processor or do I have to handle the conversion to Big endian myself?
    I have also read that network communication is normally Big endian. Another question is: the data I send through the serial line will be Big endian (like Labview) or Little endian (like Intel processor) or it doesn't depend on them and handles itself the endianness of the data?
    For the serial line I am using a RSR-232 bus.
    Thanks very much!

    As you can see from the VISA Write and VISA Read functions they have String as input and output. And these functions are not polymorph so you can use only this type.
    There are only two functions with which you can convert data to String. One is the "Byte Array to String" in the String >> String/Array/Path conversion palette. In this case the bytes must be already in the correct order. The other is the "Flatten to String" in the Advanced >> Data Manipulation palette.
    Using this function you will get flattened data. This data is always in big endian form. This data will be converted correctly into the representation the machine has which runs the "Unflatten from string" function.
    Think of sending a cluster of a I16 followed by a I32. The I16 has the value 0x0102 and the I32 has the value 0x11121314.
    Using "Flatten to string" you get the data string containing 0x01 0x02 0x11 0x12 0x13 0x14. This is the Big endian representation. If you need the Litte endian representation you have to unbundle the cluster, split number and build array.
    The VISA functions do not have any type information so they do not know which bytes/words to swap.
    If you have the bookshelf installed go to Help>>Search the LabVIEW bookshelf >> Application Notes and white papers >> LabVIEW Data Storage to learn about the Flatten and Unflatten functions and how LabVIEW generates the data strings.
    So connecting two LabVIEW applications with serial line and using flatten and unflatten you do not need to worry about endianness because these functions do this for you. If you connect a LabVIEW application together with a non LabVIEW application you have to provide the correct endianness by yourself if you do binary transfers. You can format your data into a string with the string functions and scan the string on the receiving part. This way you will transfer text and you do not have to worry about endianness because the format and scan function will do this for you.
    The Byte order attributes are only valid in the VXI classes and are used for low level memory access of VXI devices. This is described in the NI-VISA programmers reference manual which is installed with your VISA.
    Waldemar
    Waldemar
    Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
    Don't forget to give Kudos to good answers and/or questions

  • Big-endian or little-endian

    Hello,
    Is JVM big-endian or little-endian? Or is it platform dependent?
    How does one check this?
    Regards.

    I also saw over the internet that java is big-endian. But when you run this small piece of code,
    class Test {
         public static void main(String[] args) {
              short x = 10;
              byte high = (byte)(x >>> 8);
              byte low = (byte)x;/* cast implies & 0xff */
              System.out.println( "x=" + x + " high=" + high + " low=" + low );
    The output is:
    x=10 high=0 low=10
    This sample code I have taken from "mindprod.com" site only.
    Is storage different from display? Or am I missing something here?
    Regards.

  • From little Endian to big Endian

    Hi guys, Is there a function in LabView 2010 to go from little endian to big endian? I want to change for example 'B0011000' to '001001B0'.

    how about this
    Labview user

  • Little endian & big endian format system

    Hi,
    I have code which works fine for Little endian format system, can somebady please tell how to get data from big endian format system.
    or is sap has setting where i can turn on and than run my code on that system.
    Thanks,
    John.

    hi
    chk this
    OPEN DATASET dset IN LEGACY TEXT MODE [(BIG|LITTLE) ENDIAN] [CODE PAGE cp]
    Effect
    Data is read or written in a form which is compatible to BINARY MODE in Releases <= 4.6. This addition is primarily used to convert a file into the code page format specified already when it is opened. At runtime, the system uses the format of the system code page of the application server. The system saves the file then again in the code page specified. This procedure is important if data is exchanged between systems using different code pages. For more information, see READ DATASET and TRANSFER.
    Notes
    on BIG ENDIAN, LITTLE ENDIAN
    These additions specify the byte sequence in which to store numbers (ABAP types I, F, and INT2) in the file.
    These additions may only be used in combination with the additions IN LEGACY BINARY MODE and IN LEGACY TEXT MODE. If these are not specified, the system assumes that the byte sequence determined by the hardware of the application server is used in the file.
    If the byte sequence specified differs from that determined by the hardware of the application server, READDATASET and TRANSFER make the corresponding conversions.
    These additions replace the language element TRANSLATE ... NUMBER FORMAT ... which must not be used in Unicode programs.
    on CODE PAGE cp
    This addition specifies the code page which is used to represent texts in the file.
    This addition may only be used in combination with the additions IN LEGACY BINARY MODE and IN LEGACY TEXT MODE. If this addition is not specified, the system uses the code page defined by the text environment current at the time a READ or TRANSFER command is executed (see SET LOCALE LANGUAGE).
    This addition replaces the language element TRANSLATE ... CODE PAGE ... which must not be used in Unicode programs.
    open datset ... IN LEGACY BINARY MODE [(BIG|LITTLE) ENDIAN] [CODE PAGE cp]
    Effect
    Data is read or written in a form which is compatible to BINARY MODE in Releases <= 4.6. This addition is primarily used to convert a file into the code page format specified already when it is opened. At runtime, the system uses the format of the system code page of the application server. The system saves the file then again in the code page specified. This procedure is important if data is exchanged between systems using different code pages. For more information, see READ DATASET and TRANSFER.

  • Watching HDV content on computer and/or HDTV

    What are the options for watching HDV projects that are stored on the computer? Obviously the new AppleTV box will be one option. What exactly does the Matrox box do? And how do these options compare to simply playing an FCP project from the timeline on a suitable computer?
    I say "suitable" because I am still editing with a dark ages G4 Powerbook which does surprisingly well with HDV in Final Cut, but is not quite fast enough to play back HD material without skipping some frames resultng in jumpy video.
    So what are the best solutions? (Obviously printing back to tape and playing to an HDTV from the camcorder works very well, but is time consuming. I am eager to be able to play good quality video direct from a computer.
    Comments?
    - Tom

    Well, since you have an older G4 (does it have DVI out?) the only option you have is the Matrox MXO. If you have the DVI out that is.
    What the Matrox box does, rather nicely, is extract the information coming out of the DVI connection, YUV, Audio, timecode...and convert it into SDI (HD SDI), component and composite signals. AND...I love this...AND...it sends a signal to an Apple 23" display that is color accurate. With the MXO and the Apple monitor you can color correct...or simply see a true representation of what your footage looks like.
    I saw this in action at MacWorld and was REALLY impressed. And I will be gettig a unit to play with in a week.
    Shane

  • Related to Big-endian

    Respected sir,
    I write a code for range search, it is working properly only if is in Big-endian.
    Little endian it is not an expected result.
    sample code is shown below.
    Db* ObjDatabase =0;
    ObjDatabase = new Db( NULL, 0 );
    int p;
    int Ret = ObjDatabase->get_lorder( &p );
    Ret = ObjDatabase->set_lorder( 4321 );
    Ret = ObjDatabase->get_lorder( &p );
    ObjDatabase->open( NULL, "Patient.attr", NULL, DB_BTREE, DB_CREATE , 0 )
    Ret = ObjDatabase->get_lorder( &p );
    This code is not produce expected result.
    First get_lorder function returned 1234.
    Second get_lorder function returned 4321.
    After database open method, i again use get_lorder() function for verification.
    But get_lorder method return 1234.
    pls give me any soln.

    Hi there,
    There is a FAQ that is explaining this behavior and how you'll have to use Berkeley DB in order for the search operation to return the expected results.
    "I'm using integers as keys for a Btree database, and even though the key/data pairs are entered in sorted order, the page-fill factor is low": http://www.oracle.com/technology/products/berkeley-db/faq/db_faq.html#33
    One more thing to add here is that posting the same problem twice will not help you in having a faster answer. If the problem description is well done and with enough details, you can be sure that you'll be answered.
    If you have a support license for Berkeley DB with Oracle, you can also raise a Service Request on http://metalink.oracle.com , and this will help you in having timely answers. The duplicate thread is: Key sorting
    Thank you,
    Bogdan Coman

Maybe you are looking for