Linear PCM Little Endian

I have a bunch of MOV files that are
Video is H264 MPEG-4 AVC (part 10) (avc1)
Audio is PCM s16 LE (sowt) Mono 32khz 16 bit
The files worked fine in 10.8 and earlier, but in 10.9 they stopped working in Quicklook, QT10, etc. They still work in QT7.
It appears the problem is the audio codec.... I'm wondering if anyone has found a way to get these files working in QT10 again?
Thanks!

I suppose no transcoding is good news... now I just need a free batch tool that I can use to update all my files :-) Plus all the new files coming off the camera.
MPEG Streamclip includes batch processing (see "List" Menu) and uses the same QT 7 32-bit structure embedded in Mavericks. (Just tested a "Save As... " copy of your original file and it works the same as the previous test file posted.)
If the issue is just a container problem (i.e. needs to be AVF compatible), does that also explain why is there no audio in iMovie? Seems like there is a audio codec issue here too.
Yes. basically it means that any player using the AVFoundation will have a problem. Since virtually all video playing apps now access the AVFoundation from within the running app (e.g., QT X, iPhoto, iMovie, GarageBand, etc.) or OS (e.g., QL), they all exhibit the same issue—either the file will not open or it won't play the audio. I don't believe this is a codec issue as such but rather a security issue for which the structure is not properly programmed to cope and you should be filing bug reports to bring this issue to the attention of Apple.
The more I learn about Mavericks... the more I think Mountain Lion is the answer.
I personally downgraded my system back to Moutain Lion and was quite happly until recent updates forced a return in order to properly stream thousands of movie and TV episodes to various devices/computers requiring Mavericks/IOS 7 compatibility. Other mavericks issues include the loss of certain features like the Safari Command-I/Share Menu option to create working HTML newsletters in the Mail app. (I.e., you now have to Command-C copy the HTML newsletter to memory and manually paste it back into a newly composed message to get all of the links and image references to save/work properly in a sent mesxsage.) Also have to frequently relaunch the Finder to reclaim memory allocated to apps even after I have closed them following latest updates since I normally leave my system on 24-7 for access by members of my family living in other cities.

Similar Messages

Linear PCM - Big Little Endian

Sorry - I'm at a loss.
Assumptions:
Linear PCM is the correct format for exporting audio for FCP - ie Lossless
Ok...
Big Endian seems to be a default with Little Endian wanting a checkbox.
IS there a reason FCP wouldn't accept one or the other?
CaptM

Drew13 had this to say:
Little Endian and Big Endian is how the data is stored with the most signifcant byte on one end or the other (taken from Gulliver's Travels and how the egg should be cracked.(ETA) One of the conflicts in the book is between people who preferred cracking open their soft-boiled eggs from the little end, and the people who preferred the big end.). For the most part you do not need to concern yourself with this (unless you like finding out about those things more) it is transparent in your workflow on the Mac using these apps.(FCP, FCE etc.)
PPC Mac > Big Endian (default)
WIndows PC > Little Endian (default)
• Endianness
This is all well and good except when it comes to the Intel Macs and Dolby AC3 creation with Compressor.
At the moment there's a byte-order compatability Problem mixing UB versions of AC3 with PPC versions of AC3 within the same DVD SP 4.1 project.
Read this:
http://discussions.apple.com/thread.jspa?messageID=3130608&#3130608
MaxR says:
Apple's developer site specifically cites byte-order as a concern for developers of Universal binaries, but seems to have let this slip out anyway. Shame, shame, Apple.
G5 1.8 DP (PCI-X) Mac OS X (10.4.8) ATI X800 XT, 4GB RAM, 20" & 23" ACDs, M-Audio Revolution 5.1, Fostex D15 DAT

Premiere 6 Linear PCM audio

Hi,
i am trying to export a quicktime mov from Premiere 6 with the following specs:
XDCAM HD422 1080i60 (50mb/s) upper field first
Linear PCM audio - 24bit, little-endian signed integer, 2 channels, 4800khz
But I do not see an option for Linear PCM audio.... Can you help? What am I missing?

What does Little Endian and Floating Point actually do?

Exporting audio to video using Linear PCM format brings along two mysterios options called "Little Endian" and "Floating Point". I did my research but all I could dig out was that the first one, Little Endian, has to do with addressing subcomponents of a file etc.
Does anyone know what these two actually mean in terms of exporting audio and why do I only see them in logic and not in Protools for example?
Thanks...

Big Endian is most significant byte (bit) first, Little Endian is most significant byte (bit) last. When we write down a number, we use big endian: one million threehundred and twentyfivethousand ninehundred and fiftyfour we'd write as 1 325 954. in little endian notation that would be 459 523 1.
I don't know why they show up when exporting audio to video, maybe it is to adaprt the audio to some other (older?) formats?

Codec: MPEG-2 Video, Linear PCM doesn't function in iMac 10.8.3

I have recently purchased an iMac OSX version 10.8.3 which has Quicktime v10.2. Today while working to edit some old digitized footage I opened up some files that were shot on a Sony FX1 shot in HDV 1080i60 and digitized through FCP (Final Cut Pro) which made them into MPEG-2 Video, Linear PCM, Timecode files files. On my older MacBook Pro 10.5.8 I can open them with Quicktime 7.6.9 and play the files without a problem (it also has FCP with Qmaster, etc). In my research I found I can open and view the files on my iMac, if I open them with VCL. Also note I can open them on the QT player in the iMac and hear the audio just no video.
Now I did read some responses that include converting the footage to H.264 or some other format, however I am dealing with over 500gb of footage so that's not really a viable issue. My assumption is that I am going to need to purchase some upgrade to QT to get this stuff to play or hopefully download a compatible software that will make this all go away with little trouble...
Does anyone know of the software that could solve this problem? Any personal experience out there for solving this?
Thanks in advance for your time and consideration.

I think the answer to this in no-not that I know of, unless it was installed as part of the stock purchase. However I am NOT getting a message from MPEG StreamClip to install it or anything for that matter. Instead when I drag and drop the file into MPEG StreamClip I get a white screen from which I can play audio, but no video.
The QT MPEG-2 Playback component is sold by Apple so I assume you would know if you had purchased and installed it. The lack of a message from the MPEG Streamclip app would tend to indicate that either the file you are trying to open does not contain MPEG-2 compressed data or that the data is not being read/loaded to the application. Since you indicate the file opens in apps like VLC, the QT Player, and MPEG Streamclip, can you post a copy of the "Media Information", "Inspector", and "Show Stream Info" windows. (Am assuming here that the MPEG-2/PCM data is not "muxed" within the MOV container which is a separate problem.)
I reviewed the article and downloaded QT7 on this version of iMac, which I gather that it was not there before. However the footage problem is not resolved. I did read where the article suggests I purchase QT7 Pro...is this the next step in the trouble shooting? Do I need to purchase this? It this what you are referring to as the component that need be purchased or is there another? And if no, do you know where can I find the Apple playback component?
a) If you upgrade an older operating system to Snow Leopard, Lion, or Mountain Lion and had QT 7 Pro installed on the older system, then the system installer should normally install a 32-/64-bit compatible version of QT 7 and apply the "pro" key automatically. Systems purchased with Snow Leopard, Lion, or Mountain Lion pre-installed do not have a QT 7 player installed.
b) It would be expected that QT 7 v7.6.6 would not play the file if MPEG Streamclip (which you previously tried) could not play the file. Both apps access the same embedded QT structure within the operating system and employ the same codec component configuration installed on your system.
c) It would be a waste of time and money to purchase a QT 7 "Pro" key if you cannot play the file using the standard player since the "Pro" key only adds editing features and not new playback components. Once playback is working you can consider your need for the "pro" features.
d) See http://store.apple.com/us/product/D2187Z/A/quicktime-mpeg-2-playback-component-f or-mac-os-x?fnode=62 You will note that this component is not required for/not used by QT X based apps but is still required for QT "classic" based apps such as QT 7/QT 7 Pro, GarageBand, MPEG Streamclip, etc. once you get it installed—which is another problem.
I do want to purchase and install...can I find this within this Apple site or are there other Apple supported sites I can find it?
See Apple Store link above. However, my personal recommendation at this point would be to hold off on this purchase until it is determined just what your current playback problem is. For instance, can you post a sample problem file for download in order to examine/test on my system?
I am not sure I understand how to answer this completely, however I trancoded/imported these files from tape through the capture feature in FCP5 and the files have been living and transfered from drive to drive over a series of 8 or so years. They have never NOT played on my MacBook Pro which was not actually the computer they were created from, but since they functioned here I didn't think twice about. However I don't think this is answering your question. It may be best to ask how do I learn about if they are orphaned or not, so I can properly answer?
Basically, a media file consists of a container in which data is placed. In some cases only certain foms of compressed data can be contained in a specific container type. In other cases, multiple or any form of compressed data can be contained. For instance, an MOV file container may hold any form of compressed data that was compatible with the codec component configuration for the system on which the file was created. Unfortunately, this does not mean the file will be compatible with other systems. Since you indicate the files were imported or captured by FCP5, their compression format would depend on both the tape device and/or "Easy Setup" software option used to store the original digitized data which thereafter may or may not have been re-rendered to another compression format during or after your project was completed as part of the "output" process. Since there seems to be some question as to the actual compression format of the data you are trying to access, the first thing you need to do is reconfirm this information. Here are the usual medods of doing this:
a) If files do not open in any media player, use the Finder "Info" window to see what it can tell you about the file. This information may be minimal.
b) If the file opens in a media player app, then use that app's "Media Info", "Inspector", "Stream", "Properties" or similar window to see what it can tell you.
c) You can also use a dedicated utility app like MidiaInfo (free) to examine the file characteristics. These apps usually provide the most information.
(NOTE: In the case of most of these apps, it is usually best to simply screen capture the information window and post it to the forum since most users fail to provide suplementary details about the file which may or may not become significant later.)
d) "Orphaned" files usually refer to "reference" files. Reference files do not contain all of the data needed for playback. Instead, they contain a resource pointer to another file that actually contains the needed playback data, as well as, playing instructions telling how the resource data is to be played. When a reference file is moved to a different drive, the resource data must also be moved. It it isn't, then the data will become "orphaned" when the reference file tries to locate and play it. Reference files are usually very small and are handy for the passing of data from one application to another—such as when sending data from FCP to DVDSP for burning or from iMovie to iDVD. If your files play in VLC then either they are unorphaned reference files or they are standalone files. So, once again if the files play in VLC but not in QT, then we need to look at the specific compression formats involved to determine just what the problem is.
THIS IS GREAT NEWS! This is an issue of great interest to me. I copied FCP6 from my MacBook Pro to my iMac, but the files did not function. I also attempted to install them from disk, but I received a message that the software is not supported. I was under the impression FCP 6 was not compatible with this iMac and Mountain Lion, then I had heard from a friend that they corrected that but I haven't seen any change on my system and I have update my software to current at this point. Do you have thoughts on this and/or how I can get my FCP 6 to function on my iMac? I would love to be able to make use of it.
In my case, I migrated the everything (including the FCP Suite installation) from my Leopard system to my new iMac while it was operating under Snow Leopard and updated the iMac to Lion and later to Mountain Lion. Based on what you say, it appears the FCP installer, like the QT MPEG-2 Playback Component installer package, is not compatible with Lion or Mountain Lion. This does not mean the apps are not compatible with these systems but it does likely mean you would have to use a third-party app like Pacifist to install the FCP software package. (Pacifist can also be used to install the QT MPEG-2 Playback component instead of the "helper" intaller utility provided in the MPEG Streamclip download mentioned above.) Have not really tested this method of installing FCP on Mac OS X v10.8.3, but it does seem logical that it would work since I can still use FCP still operated under Mountain Lion.

Audio drop-out in FCPX with 1920x1080 & 2048x1240p @ 24p (codec Apple ProRes 4444 (Linear PCM))24p

Hi all...
I'm new to this forum.
Is there an audio issue (drop-outs) with FCPX (ver 10.1.2) for 1920x1080 24p, 1080p HD & 2048x1240 24p (2k) - note: films in FCPX are in codec Apple ProRes 4444, Linear PCM?
Very recently I've been working on a show reel and I have imported a file (short film) to snip out a section to add to the show reel.
I set the project to the film's settings i.e.. "set based on first video clip"...(1920x1080 24p, 1080p HD). When I play the film in FCPX the audio "hic-cups"..."dips to silence"..."drops-out" briefly (up to 0.5 secs in duration) and very frequently all the way through (approx 15 mins long film)...note: audio set is at stereo 48kHz. The audio monitors on the right hand side also show the dip taking place (if it's a long enough drop-out).
I also have a version of the film in 2048x1240 24p at 2k, again Stereo 48kHz...and this does the same audio "drop-out" all the way through. I'm unsure what other formats will create this problem i.e. higher or lower aspect ratios than those above.
Is this a software and/or OS issue? Or a hardware issue? Or both!?
About This iMac details:
iMac 27 inch: OS X ver 10.9.4
Processor: 3.5 GHz Intel Core i7
Memory: 32 GB 1600 MHz DDR3
Graphics: NVIDIA GeForce GTX 780M 4096 MB
Fusion Drive 3.12 TB
Final Cut Pro X was bought & installed with this iMac back in Feb 2014
FCPX version: 10.1.2
Note also: I used Compressor (ver 4.1.2) to convert the files (movies) above to Apple ProRes 422 HQ, Linear PCM and the issue disappeared - the audio and visuals played with no problems. All films play with no issue when opened in QT player. They are also fine when exporting from FCPX. The issue only occurs (as far as I can tell) within FCPX when editing or playing the audio there.
Has anyone encountered this problem?
Kind Regards,
Hakan

Hi Luis,
Thank you for that.
Seems like you have a point about the "hardware" issue. I'm unsure (new to it all) at what data rate my (er...wonderful) fusion drive provides FCPX for smooth playback - or where I can find that info on the iMac. Playing back movies in the 422 HQ codec seems to have no issues (when I converted the movie from 4444 HQ).
But playing the full 4444 HQ, the picture is smooth, but the audio has these drop-outs - even with "best performance" option ticked. Interesting that the audio suffers, not the picture in FCPX - so not sure what's going on there. I also read - perhaps - that to play a smooth ProRes 4444 HQ movie in FCPX the data rate should be min of 500 Mbs (based upon About Apple ProRes) for HD movies and up (i.e. 2k). ProRes 422 HQ needs a data rate of 220 Mbs - so that is my upper-limit to smooth video&audio playback with the current system I have, I guess.
Does anyone recommend a fast USB3 or Thunderbolt drive (500Mbs+) where I am able to run 4444HQ movies with no issues to picture or sound (away from the fusion drive)?
KR
H.

Using "Save As" execCommand in IE8 to save XML file in ANSI format instead of UCS2-Little Endian

I am currently trying to save an XML data using "SaveAs" execCommand from Javascript in Internet Explorer 8 only.I am using document.write(xml) to write the xml content after i open a window.The document object in IE8 uses a saveAs Exec
Command to allow the user to save the xml file in the local folder.The XML file is generated but it doesnt set the encoding to my preferred type for a different interface where i need to send this XML which is ANSI/UTF-8 encoding.I can only save
the XML in UCS2 little Endian encoding format.Below is the code i am using.
var location = "D:\\export_to_MCT"+dateTime+".xml";
var xml = tmpSelectedConfigurationXML.transformNode(xslDoc);// XML Is generated here
alert(xml);
**var testlink = window.open ("about:blank","_blank","toolbar=no,status=no,menubar=no,scrollbars=no,resizable=no,left=10000, top=10000, width=10, height=10, visible=none");
testlink.document.write(xml); //fileData has contents for the file
testlink.document.close();
testlink.document.execCommand('SaveAs', false, location);**
testlink.close();
My purpose is to save the xml in ANSI/UTF-8 encoding without BOM format.I cant use Scripting.FileSystemObject method of ActiveX object.Please suggest

@panda Boy--
But my intention isnt that .I need to download the xml in ANSI format

MPEG-2 Video Linear PCM Timecode no longer working in FCP7

I edit daily with Final Cut Pro 7.0.3 on my MacBook Pro. I have several projects in which I imported files from an MR HD-100 hard drive. Not only did I successfully edit several projects, but I could open the individual files in QuickTime. They are 1280 x 720 MPEG-2 Video, Linear PCM, Timecode HD (1-1-1) files. Now suddenly they will not open. All I get is a white screen in Final Cut. Even the old finished projects I open in Final Cut show a white screen where this footage used to be. When I try to open one of the files in QuickTime I get the message, "An invalid public movie atom was found in the movie." I have not needed any type of conversion to make these files compatible before. They just worked. Any ideas as to why they suddenly won't work now?

I finally had time yesterday and today to tackle this problem. I read the link you sent and jedi knights had the solution if you had access to a mac still running 10.6.7 which I did not. So.....I bought a 32gb flash, intalled osx 10.6.3 from my disc, reinsalled QT7, did the 10.6.7 update, installed FCP7 so the codecs would load into QT and then transferred the one file (System/Library/QuickTimeComponents.component/Contents/MacOS/QuickTime Components) onto my laptop. ALL IS NOW RIGHT WITH THE WORLD!
Thank you for your help.

How do I install Adobe Flash Player on Ubuntu 32bit ARMv7 Little Endian machine?

How do I install Adobe Flash Player on Ubuntu (12.04) 32bit ARMv7 Little Endian machine? The .tar.gz and .deb files contains shared libraries for i386 target.

Hello,
There is a procedure of Manual Installation of Adobe Flash Player on Ubuntu, follow these steps :
Open http://get.adobe.com/flashplayer/otherversions/
Choose Linux 32-bit on Step 1
Choose Flash Player 11.2 (tar.gz) on Step 2, download the file
Once download is complete, right click on the flie (tar.gz) and click on "Extract here"
Launch Terminal (Keyboard Shortcut : Ctrl+Alt+T)
Go to that location where you extracted the file
Run this command : sudo mv libflashplayer.so \/usr/lib/firefox-addons/plugins
Launch Mozilla Firefox and check do you have Adobe Flash Player
Thanks,
Vikram

How to extract a double from a little endian stream?

I want to support Java 1.3.1, which means that I cannot use class ByteBuffer.
I would need ByteBuffer with the methods order and getDouble.
I read the socket in little endian format (thus I cannot use the getDouble method of the class DataInputStream). Is there any solution in Java 1.3.1 to extract a double from 8 bytes?
In other words, if I want to keep my code compatiple with Java 1.3.1, do I have to change the order of the bytes manually and then also extract the double value manually (extracting the sign-bit, the exponent and significant to calculate the double value is possible but quite stupid if there is another way...)
It would also help to have the release notes for Java 1.4.2. ( the link on the SUN pages points to nowhere). I am especially interested in the history of the development of ByteBuffer. Did the functionality of order (LITTLE_ENDIAN / BIG_ENDIAN) exist in any other way in Java 1.3.1?
Ps. I put another case to this Forum earlier today, and even added it to my watch list, and even got an answer BUT after relogin there was not even a sign of that case... I sent feedback to SUN but I'm sorry for not being able to get back to the person who answered my case.

Thank you for your help, meloro77!
I modified your masks and shifts and then finally created the proper method for the double values.
There was one more trick needed: each byte MUST be converted into a long value before running the shift! The byte and the result is otherwise treated as int (32 bytes and any bytes higher than this would be discarded.
For your and everybody else's fun and joy, I include here the code which I used:
byte []   doubleData = new byte[8];
             reading the bytes
      double myDouble = 0.0;
      // Create a long value of the bytes
      long doublebits;
      short MASK_TO_BYTE = 0xFF;
      doublebits = ((long)doubleData[7] & MASK_TO_BYTE)
                  | ((long)(doubleData[6] & MASK_TO_BYTE) << 8)
                  | ((long)(doubleData[5] & MASK_TO_BYTE) << 16)
                  | ((long)(doubleData[4] & MASK_TO_BYTE) << 24)
                  | ((long)(doubleData[3] & MASK_TO_BYTE) << 32)
                  | ((long)(doubleData[2] & MASK_TO_BYTE) << 40)
                  | ((long)(doubleData[1] & MASK_TO_BYTE) << 48)
                  | ((long)(doubleData[0] & MASK_TO_BYTE) << 56);
       * Let method Double.longBitsToDouble convert the value to a double
      myDouble = Double.longBitsToDouble(doublebits);

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.

How to download the videos from my olympus linear pcm recorder?

how can I download my videos from my olympus linear pcm recorder?

You need a good program to import and organize. You can purchas iPhoto or download the free Picasa app from google.
http://picasa.google.com/mac/
Regards,
Captfred

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

TCP Programming / Why do not need to worry about Big and little Endian?

Please help, I do not understand this concept please explain.
The architecture of a CPU is either little-endian or big-endian; some modern CPU's allow a choice via software.
The TCP/IP protocol standard specifies that all the bytes that make up an item must be sent in "network order", which happends to be big-endian. Intel Pentium CPU's are little-endian.
This implies that on an Intel machine the TCP software will have to chop an int into bytes and then reverse the bytes before transmitting them.
Why does the JAVA TCP software does not need to perform the reversal?
Thanks,
Alex

But why would I need to use the DataOutputStream,You don't have to.
But that's what the Java API provides for sending java primitives over a stream. You wouldn't have to use that. You could chop the int into bytes yourself, and send the bytes, and your Java code still wouldn't have to worry about the endiannes of it, because the VMs handle that.
DataOutputStream just does the chopping and reassembling for you, so it's easier than doing it yoursefl.

Why do not need to worry about Big and little Endian in Java

Please help, I do not understand this concept please explain.
The architecture of a CPU is either little-endian or big-endian; some modern CPU's allow a choice via software.
The TCP/IP protocol standard specifies that all the bytes that make up an item must be sent in "network order", which happends to be big-endian. Intel Pentium CPU's are little-endian.
This implies that on an Intel machine the TCP software will have to chop an int into bytes and then reverse the bytes before transmitting them.
Why does the JAVA TCP software does not need to perform the reversal?
Thanks,
Alex

Java doesn't give you direct access to the individual bytes of a larger data item such as an integer. For this reason you don't have the usual endian problems that occur in C. The actual handling of this is in the DataOutputStream and DataInputStream where the integer is coverted to and from bytes using arithmetic, not by fiddling with the internal structure.
Note that regardless of the machine architecture the operation value%256 will return the low order 8 bits. It's less efficient than assigning an int* to a char*, but it's not fraught with the endian problems or any of the other hardware baggage.

Linear PCM Little Endian

Similar Messages

Maybe you are looking for