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.

Similar Messages

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.

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

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.

Any need for conversation from big endian and little endian?

Hi,
I am planning to migrate an Oracle 9i Database on AIX 5.3 to Oracle 11g R2 Windows 2008, and have planned to use transportable tablespace. But prior to that task is the conversation required from big endian and little endian using RMAN?
Appreciate any suggestions, comments and hints
Thanks

Hi,
Check V$TRANSPORTABLE_PLATFORM, it shows the ending for each supported platform. Given the results on my 11g, I suspect that you'll have to convert the tablespaces...
SYSTEM@oracle11 SQL>select *
2   from V$TRANSPORTABLE_PLATFORM
3 ;
PLATFORM_ID PLATFORM_NAME                                                                                         ENDIAN_FORMAT
          7 Microsoft Windows IA (32-bit)                                                                         Little
          6 AIX-Based Systems (64-bit)                                                                            Big
          8 Microsoft Windows IA (64-bit)                                                                         Little
         12 Microsoft Windows x86 64-bit                                                                          LittleHtH
Johan

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

Little- och big-endian problem?

Hi!
I'm writing a program which will run on Windows, Mac OS and Linux. The program will be used for opening binary files created by a program in Windows.
Because the files are created in Windows i guess they will be created according to the little-endian system. The program that will open them will read them in to the memory as a byte array.
My question is: will there be a problem to get the right information from these files if I open them on a big-endian system? (There are no magic numbers in the binary file which indicates the used endian system)
Lina

I have to admit that I get the meaning of big/little endian confused.
As JosAH says; Big endian means the big end is first,
NOT that the big value is at the end.And I have to admit that I find that whole big/little-endian jargon quite confusing
too, I mean the most significant byte is stored at the lowest address and we
call it big-endian ... If the number is stored 'backwards' we call it little endian.
In the old days when computers were made of wood and ran on steam, we
used to call it 'low-byte-first' and 'high-byte-first'. Sigh ... those were the days ;-)
kind regards,
Jos

VDI 3.1 Big Endian vs Little Endian: VDI Cluster to Remote mysql server

Hello,
We are implementing a Dual Data center VDI environment and with that, will be using VCS to Cluster a remote Mysql instance. My question, if the VDI Cluster is on x86 (Little Endian), can the remote Mysql DB be on Sparc (Big Endian)?
Thanks,

The endian matching is only a requirement for the management and data nodes of a MySQL cluster. If you are going to be using a remote MySQL DB, the VDI servers will be connecting to that remote MySQL DB as a client connection, and there is no requirement for clients to match the endian type.
http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-limitations-exclusive-to-cluster.html

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.

Oracle guids little endian, big endian problem

hello every one,
I am having an strange issue. I am developing a .net app against an Oracle DB. Well, when I insert a guid into a raw oracle changes the order of the byte array.
In VB.net I see (with all the representations of guids, with or without {,- or whatever):
ac6d5c4f-542e-4fc8-b8b6-f53821811be3
In Oracle I see (tested with toad and sql tools):
4F5C6DAC2E54C84FB8B6F53821811BE3
It goes ok with the rightests numbers but fails the the leftests.
Any suggestion?

I have to admit that I get the meaning of big/little endian confused.
As JosAH says; Big endian means the big end is first,
NOT that the big value is at the end.And I have to admit that I find that whole big/little-endian jargon quite confusing
too, I mean the most significant byte is stored at the lowest address and we
call it big-endian ... If the number is stored 'backwards' we call it little endian.
In the old days when computers were made of wood and ran on steam, we
used to call it 'low-byte-first' and 'high-byte-first'. Sigh ... those were the days ;-)
kind regards,
Jos

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.

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.

Codec:HDV1080i60, integer (Big Endian), Timecode

Similar Messages

Maybe you are looking for