Parse a long file

Hello,
I have to parse a long file....the concept of that file it is that there are several billings included, and for each billing it is separated for an special escape character ( FF character , i tihnk it tells the printer to skip page )
Well, I have some java experience , but I dont know regular expressions in java...I need the following for instance:
COORSERPARK LTDA                                        NIT :      800,215,065-4
                                                            FACTURA DE VENTA No.   :  F-003-00000060466
                       SANTAFE DE BOGOTA, FEBRERO    01 DE 2008
                       SENOR(ES)
                       CAVIDA                                                  NIT :      830,100,838-5
                       CAVIDA                                                  NIT :      830,100,838-5FOR "FACTURA DE VENTA No. : F-003-00000060466" , I have to get the billing number which is F-003-00000060466 , do u know a regular expression for that ?
Also for instance a line like this
PLAN XXXXXXX                         11                                        9,215.00        101,365.00, where XXXXXXX might be any name
I need to get the values PLAN XXXXXX , *11* , *101,365.00* it would be perfect if i get them in an array, so i know that first position corresponds to X value, second corresponds to Y value, and so on
There are not tabs between values, but just certain amout of spaces , which might vary
Thanks in advance,
deibys

It may seem trivial, but if strings are fixed (FACTURA DE VENTA No. will always be the same and the same for PLAN), I would search for those strings (first by reading all document into a string variable) inside the document, and having the position of the end of that string, go on parsing ignoring white spaces and storing all "non-space" data found (if you are looking for a price, you know it won't have spaces, or if you're looking for a code you also know it would have no spaces or maybe it would have fixed length)...I know it's dirty but it would surely work.
I repeat, it's not smart but it will work with few code (I suppose :) ).
P.S. I hate regular expressions :)
Edited by: scuffia on Jan 31, 2008 9:27 PM

Similar Messages

  • Runtime parsing of policy.file - from source

    Hi All
    Decided to post here sinceI did not find any similar topic on forums and googling did not solve this.
    Is there any way to parse polic.file like input at runtime? PolicyTool. PolicyFile are classes that do that but:
    1. all methods are private so it does not give much place to have fun - cant make PolicyFile to read from StringReader for instance.
    2. they make immedaite changes to jvm wide Policy object ? without access to installed code sources.
    The question is is there a way to parse policy.file like data in a way that all goodies from PolicyFile are considered? - I mean keystore, principials, etc etc.
    Or is it perfectly legal to create CodeSource and permissions from what is passed and dont worry about location of keystore or verification of signature?

    You can work-around this by removing the language="java" altogether. The
              default is "java" and I don't expect anything else to be supported for a
              very long time to come!
              "kethidi" <[email protected]> wrote in message
              news:3d5bf557$[email protected]..
              > Parsing of JSP File '/jsp/default.jsp' failed:
              > /jsp/default.jsp(2): page directive language at /jsp/default.jsp:2
              previously defined at /jsp/CheckSession.jsp:1
              > probably occurred due to an error in /jsp/default.jsp line 2:
              > <%@ page language="java" import="com.pmi.mi.MIxmlbean"%>
              >
              >
              > I am getting this error, when I upgrade from weblogic5.1sp10 to
              weblogic7.0. The code is working fine when I use weblogic server 5.1 sp10.
              But it displayed the above error, when we convert to weblogc server 7.0.
              >
              > Thanks,
              > kethidi
              

  • "Error parsing MPEG Metadata file.

    I have been using Encore for about 4 years: 1.5 -> 2.
    Recently I have had problems with projects exported as an avi file from Premier 2 and used in a simple menu and timeline in Encore 2. Typically projects were about an hour long. Chapter points were added in Encore automatically every 3 mins for general navigation assistance. I checked the project was OK and pressed Build. After watching the video transcoding progress bar creep to 100%, the error message appears immediately the process appears to have completed - "Error parsing MPEG Metadata file. Deleting or renaming filename.m2v.xmpses" will allow you to import, but any markers will be lost". On the previous occasion I went back to the assets, highlighted the avi file and transcoded it manually (automatically). No error message. I then built and burned the DVD.
    I have sometimes cured problems by removing any info from the final chapter point - delete the visible info. This may have just solved this last problem despite the initial build being reported as being free of problems. Following the first problem I rechecked and was told there was a problem with the final chapter point. I deleted the chapter point info and it has built and burned satisfactorily.
    Two questions.
    What is causing this problem. I have burned lots of DVDs over the years with Encore. Is the use of chapter points the cause of the problem. There have been quite a lot of reports of this in other (Matrox) forums. I am using Matrox RTX100. How can I prevent this huge waste of time - a build may take me a couple of hours.
    Is it better to export the Premier Pro2 timeline as an avi and use Encore for the transcoding, or is it better to export a trancoded file from Premier directly and just include this in the Encore project. If yes, which format should I export it in. I have the Premier and Matrox transcoding options.
    Roger

    Not sure if this is causing the error, but since version 2 Encore automatically adds a chapter point on the last available GOP. It could be that the last of your 3 minute chapter markers is closer to this final chapter point than 0.4 seconds. The DVD-Video specification requires chapter points to be at least 0.4 seconds apart.

  • How to parse a HTML file using HTML parser in J2SE?

    I want to parse an HTML file using HTML parser. Can any body help me by providing a sample code to parse the HTML file?
    Thanks nad Cheers,
    Amaresh

    What HTML parser and what does "parsing" mean to you?

  • Time capsule won't allow long file names

    Hello,
    I've managed to solve every problem I've had through searching other people's forum posts - apart from this one.
    I've got a MacBook Pro and Dell PC (Windows 7) connected to a Time Capsule. Soon I'll happily bin the Dell but am moving gently to Macs while I learn about them.
    The Mac connects happily to TC and will allow creation/editing of long file names.
    The Dell allowed this for a week, but now doesn't like it. When I go to the Time Capsule/Data folder in Windows 7 Explorer, I can copy over files with long names, but I can't create them, nor can I change any existing file/folder names on TC to be longer than 8 characters.
    I've searched and searched online and can't find anything that would suggest why this is happening.
    Thanks in advance,
    Adrian

    Tried DHCP & NAT but had the double NAT issue.
    If you got the TC working and had double NAT .. sorry but the TP-Link is exactly the same.. you cannot distribute a single IP without double NAT.. the TC tells you it is a problem.. the TP-Link doesn't.. otherwise there is no difference.
    But it is important the double NAT is setup right.. ie you must use different ranges.. please tell us the IP you get from a directly connected computer..
    If it is 10.x.x.x then you should move the TC to 192.168. rather than default IP of 10.0.1.1 .. the TP-Link already will use 192.168.x.x. which might also explain why it works better.

  • I want to *use* very long file and path names!

    This is really a plea to Microsoft...
    There are several threads about copying or deleting files where the path and/or file name is too long.
    Most have explanations of why this problem occurs.  (depending on Windows version and application, the total length [fully qualified file name; i.e. C:\this-dir\that-dir\somefile.xyz] is limited to a maximum of 260 or fewer characters).  This limit
    But I *WANT* to be able to use very long file names and paths!
    I can understand Microsoft keeping this limit - even while allowing UNICODE paths and file names up to 32k characters - because many existing tools will be unable to handle the longer names.  This would probably yield a lot of questions/flames about
    them "breaking the software I've used for years."
    But it would be possible to have a system setting to optionally allow the long names.  Since I'd have to manually set it, I'd know I'm potentially breaking existing software.
    In my case, I'm backing up various file directories where some files are very long.  With the server-side additional paths (e.g., client-name\project-name\backup-date\...") I occasionally hit files that can't be copied.  Renaming is not suitable;
    sometimes names have to match other file names.
    I can zip them, create iso files, use a backup program that creates a blob, put them in a source-control system, etc - but I really don't *want* to do that; it's very convenient to have a direct copy of the directories.  Each of these 'solutions' either
    requires extra work (which could be scripted, so ok...) or doesn't work with the work-flow for some reason.
    Microsoft, *please* fix this in Windows 8!  (if not before...)   This limit has existed for far too long!
    And readers - please don't just repeat what's in the other threads (rename/use subst/map directory/etc) or flame without useful information.  Thanks!

    Hi,
    I would submit your opinion to our Product Team. If you have another feedback, please feel free and let me know. Or you could follow TekDozer’s advice to submit
    by yourself.
    Thank you for your understanding and cooperation.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

  • Parsing error in file C:\Program Files (x86)\HP\D​igital Imaging\bi​n\hpqscloc​\1033-xml

    Spoiler (Highlight to read)
    I have a HP Photosmart Premium C310a All-In-One I can not open solution center get the message I wrote as a subjekt.I´ve tried a lot of methods I´m 75 years old and I´m tired of this problem!    I´ve got 2 computers one HPdv5009 with W.XP Home Edition and it works free from problem The solution center opens up without any problem but on the other HP dv7 with W.7 Home Premium 64 Solution center did not like my order to open up! Parsing error in file etc. That is the answer I got!
     Please Help Me anybody!
    This question was solved.
    View Solution.

    Hello-
    I have included a link where the issue has been resolved. Look for the file that is in grreen_apple's post. (attachment)
    http://h30434.www3.hp.com/t5/Scanning-Faxing-and-C​opying/Parsing-error-in-file-c-Program-Files-HP-Di​...
    Also, remember a click on the Kudos star to the left is a quick "Thanks" for a helpful post.
    Please select the "Accept as Solution" button on the post that best answers your question.
    I appreciate your input !
    Thank You,
    Donald

  • Parsing error in file C:\Program Files (x86)\HP\Digital Imaging\bin\hpqscloc\1033.xml

    The HP Solution Centre has disappeared from my toolbar and we I attempt to open it with the program file I receive the above error

    Hi ... I have the same kind of error message:
    Parsing error in file C:\Program Files (x86)\HP\Digital Imaging\bin\hpqscloc\1033.xml
    Have been searching for a solution, using different sort of key words, no luck so far.
    Anyone here? Many thanks in advance.

  • Can someone help me with a problem of parsing an XML file?

    Hello,
    I'm having some problems parsing an xml file. I get a SAXNotSupportedException when setting a property value.
    Here is the piece of code where I have the problem:
    SAXParserFactory spf = SAXParserFactory.newInstance();
    spf.setNamespaceAware(true);
    SAXParser saxParser = spf.newSAXParser();
    XMLReader xmlReader = saxParser.getXMLReader();
    DefaultHandler defHandler = new DefaultHandler();
    xmlReader.setProperty("http://xml.org/sax/properties/lexical-handler", defHandler);
    and the log is:
    Problem with the parser org.xml.sax.SAXNotSupportedException: PAR012 For propertyID "http://xml.org/sax/properties/lexical-handler", the value "org.xml.sax.helpers.DefaultHandler@4ff4f74a" cannot be cast to LexicalHandler.
    http://xml.org/sax/properties/lexical-handler org.xml.sax.helpers.DefaultHandler@4ff4f74a LexicalHandler
    I've been working on this problem but I can't find the error.
    Does anyone have an idea of what to do to solve it?
    Thanx in advance,
    M@G

    before deciding which XML technology to use, you should see if your application fit in the category below:
    use SAX:
    1. The XML file is rather large (30 or 40+ MB)
    2. I don't need the xml document in memory. I will parse the document and store the data in my own object.
    use DOM or JDOM
    1. The XML file is relatively small (less than 30 MB) or I can increase the runtime memory for larger xml file.
    2. I will need to walk up and down the xml document tree severals time.
    3. My application is in Java and it's not going to be rewritten in C++, etc (use JDOM)
    NOTE:
    JDOM is rather easier to use (for Java developer), but it's not an www.org.com standardlized xml parser.
    personally, i like JDOM for traversing the DOM.

  • Parsing of xml file in oracle stored procedure on linux server

    We have an XML file in the "/database/stats/dev/xml1/" path and tried to parse the file using the below code :
    p := xmlparser.newParser;
    xmlparser.setValidationMode(p, FALSE);
    -- xmlparser.setErrorLog(p, errfile);
    xmlparser.setBaseDir(p, dir);
    xmlparser.parse(p, inpfile);
    doc := xmlparser.getDocument(p);
    xmlparser.freeParser(p);
    The above procedure is throwing below mentioned exception at "xmlparser.parse(p, inpfile);".
    SQLCODE: ORA-31001
    SQLERRM: ORA-31001: Invalid resource handle or path name "/xml1.dtd"
    The xml file contains the following line, which is giving an error, while parsing the xml file.
    <!DOCTYPE CCIOrder SYSTEM "xml1.dtd">
    Directory Structure:
    OWNER DIRECTORY_NAME DIRECTORY_PATH
    SYS XML1 /database/stats/dev/xml1

    you'll need to use server-side code to check the xml file names in that folder, return that list to flash and display the list to the user.
    or, if you can get by presenting a hard-coded list of xml files, you won't need any server-side coding.

  • How to Parse an XML file using SAXParser in java.

    Hi all
    Am a bit new to XML files and have no idea about SAXParsers ... Now my problem is to parse this XML file below
    <?xml version="1.0" encoding="UTF-8"?>
    <sc:memory_segmentation xmlns:sc="sc_memory_segmentation.xsd">
       <sc:architecture name="MPC55xx"></sc:architecture>
       <sc:derivative name=""></sc:derivative>
       <sc:configuration name=""></sc:configuration>
       <sc:memory name="Internal ROM" type="ROM">
          <sc:area-list>
             <sc:area name="Bootmanager" type="BOOTMANAGER">
                 <sc:segment-list>
                   <sc:segment name="ROM page 1">
                      <sc:start></sc:start>
                      <sc:end></sc:end>
                   </sc:segment>
                 </sc:segment-list>
             </sc:area>
             <sc:area name="Bootloader SWE" type="BOOTLOADER">
                 <sc:segment-list>
                   <sc:segment name="ROM page 2">
                      <sc:start></sc:start>
                      <sc:end></sc:end>
                   </sc:segment>
                   <sc:segment name="ROM page 3">
                      <sc:start></sc:start>
                      <sc:end></sc:end>
                   </sc:segment>
                </sc:segment-list>
             </sc:area>
             <sc:area name="Application SWE 1" type="APPLICATION">
                <sc:segment-list>
                   <sc:segment name="ROM page 4">
                      <sc:start></sc:start>
                      <sc:end></sc:end>
                   </sc:segment>
                   <sc:segment name="ROM page 5">
                      <sc:start></sc:start>
                      <sc:end></sc:end>
                   </sc:segment>
                   <sc:segment name="ROM page 6">
                      <sc:start></sc:start>
                      <sc:end></sc:end>
                   </sc:segment>
                   <sc:segment name="ROM page 7">
                      <sc:start></sc:start>
                      <sc:end></sc:end>
                   </sc:segment>
                </sc:segment-list>
             </sc:area>
             <sc:area name="Application SWE 2" type="APPLICATION">
                <sc:segment-list>
                   <sc:segment name="ROM page 8">
                      <sc:start></sc:start>
                      <sc:end></sc:end>
                   </sc:segment>
                </sc:segment-list>
             </sc:area>
             <sc:area name="Application SWE 3" type="APPLICATION">
                <sc:segment-list>
                   <sc:segment name="ROM page 9">
                      <sc:start></sc:start>
                      <sc:end></sc:end>
                   </sc:segment>
                </sc:segment-list>
             </sc:area>
             <sc:area name="Application SWE 4" type="APPLICATION">
                <sc:segment-list>
                   <sc:segment name="ROM page 10">
                      <sc:start></sc:start>
                      <sc:end></sc:end>
                   </sc:segment>
                </sc:segment-list>
             </sc:area>
          </sc:area-list>
       </sc:memory>
       <sc:memory name="Internal RAM" type="RAM">
          <sc:area-list>
             <sc:area name="RAM" type="RAM">
                <sc:segment-list>
                   <sc:segment name="RAM page 1">
                      <sc:start></sc:start>
                      <sc:end></sc:end>
                   </sc:segment>
                   <sc:segment name="RAM page 2">
                      <sc:start></sc:start>
                      <sc:end></sc:end>
                   </sc:segment>
                   <sc:segment name="RAM page 3">
                      <sc:start></sc:start>
                      <sc:end></sc:end>
                   </sc:segment>
                   <sc:segment name="RAM page 4">
                      <sc:start></sc:start>
                      <sc:end></sc:end>
                   </sc:segment>
                   <sc:segment name="RAM page 5">
                      <sc:start></sc:start>
                      <sc:end></sc:end>
                   </sc:segment>
                </sc:segment-list>
             </sc:area>
          </sc:area-list>
       </sc:memory>
       <sc:memory name="Internal EEPROM" type="EEPROM">
          <sc:area-list>
             <sc:area name="EEPROM" type="EEPROM">
                <sc:segment-list>
                   <sc:segment name="EEPROM page 1">
                      <sc:start></sc:start>
                      <sc:end></sc:end>
                   </sc:segment>
                   <sc:segment name="EEPROM page 2">
                      <sc:start></sc:start>
                      <sc:end></sc:end>
                   </sc:segment>
                   <sc:segment name="EEPROM page 3">
                      <sc:start></sc:start>
                      <sc:end></sc:end>
                   </sc:segment>
                   <sc:segment name="EEPROM page 4">
                      <sc:start></sc:start>
                      <sc:end></sc:end>
                   </sc:segment>
                   <sc:segment name="EEPROM page 5">
                      <sc:start></sc:start>
                      <sc:end></sc:end>
                   </sc:segment>
                </sc:segment-list>
             </sc:area>
          </sc:area-list>
       </sc:memory>
    </sc:memory_segmentation> And from this file I need to make 3 Hashtables out of it one for ROM , RAM and EEPROM containg Segment information i.e. Segment start and end addresses and Area type of the segment....
    If anyone could at least guide me with the basic commands and structure of the parser it would be really really great ...
    Thanks a lot
    Anisha

    Normally if you have no idea about X, the first thing you should do is google "X tutorial". You will find plenty of them out there. And the advantage is, they are better written than whatever we spend two minutes throwing together here. Not to mention that it saves us the two minutes.
    But if you have specific questions with your SAX parser when you get it going, then ask them here. Actually, ask them in the XML forum here, not this one.

  • Parsing an XML file

    I've written a program which is partly responsible for parsing an XML file that can be found on the web. I appear to be accessing the XML file correctly, but when I try to parse it I am running into a problem. I try to create a List object that contains all of the children of the root element. The code looks like this:
    Document doc = parser.build(xmlFile);
    Element root = doc.getRootElement();
    List rootChildren = root.getChildren();But I get an error that say that "the type List is ambiguous". I am importing java.util.*. I am trying to do this exactly like a few examples I found on the web, but I can't seem to get past this issue. What do I need to keep Eclipse from telling me that List is not an ambiguous type.

    Maybe you haveimport java.util.*;
    import java.awt.*;Both packages contains a List class.
    In that case, the compiler doesn't know which one you're talking about.
    If you don't need the java.awt.List class here, try not to import it.
    If you need it, use the fully qualified class name in your code.

  • Parsing an xml file using xerces DOM  parser

    Hi
    I want to parse a simple xml file using DOM parser.
    The file is
    <Item>
         <SubItem>
              <title>SubItem0</title>
              <attr1>0</attr1>
              <attr2>0</attr2>
              <attr3>0</attr3>
         </SubItem>
         <SubItem>
              <title>SubItem1</title>
              <attr1>1</attr1>
              <attr2>0</attr2>
              <attr3>0</attr3>
         </SubItem>
         <SubItem>
              <title>SubItem2</title>
              <attr1>1</attr1>
              <attr2>1</attr2>
              <attr3>0</attr3>
              <SubItem>
                   <title>SubItem20</title>
                   <attr1>2</attr1>
                   <attr2>1</attr2>
                   <attr3>0</attr3>
              </SubItem>
              <SubItem>
                   <title>SubItem21</title>
                   <attr1>1</attr1>
                   <attr2>1</attr2>
                   <attr3>0</attr3>
              </SubItem>
         </SubItem>
    </Item>
    I just want to parse this file and want to store the values in desired datastructures,
    I am trying using DOM parser, since it gives a tree structure, which is ok in this case.
    public void init()
              InputReader ir     =new InputReader("Habsys");
              Document      doc     =ir.read("Habitat");
              System.out.println(doc);
              traverse(doc);
    private void traverse(Document idoc)
              NodeList lchildren=idoc.getElementsByTagName("SubItem");
              for(int i=0;i<lchildren.getLength();i++)
                   String lgstr=lchildren.item(i).getNodeName();
                   if(lgstr.equals("SubItem"))
                        traverse(lchildren.item(i));
    private void traverse (Node node) {
    int type = node.getNodeType();
    if (type == Node.ELEMENT_NODE)
    System.out.println ("Name :"+node.getNodeName());
    if(!node.hasChildNodes())
    System.out.println ("Value :"+node.getNodeValue());
    NodeList children = node.getChildNodes();
    if (children != null) {
    for (int i=0; i< children.getLength(); i++)
    traverse (children.item(i));
    But I am not getting required results, a lot of values I am getting as null
    Could anybody tell me how to retrieve the data from the xml file, I simply want to read data and store it in data structures. For eg, for tag Subitem with title as ' SubItem1' has attr1 as '1', attr2 as'0' and attr3 as '0'.
    Thanks
    Gaurav

    Check This Sample Code....
    public void amethod(){
    DocumentBuilderFactory dbf = null;
    DocumentBuilder docBuilder = null;
    Document doc = null;
    try{
         dbf = DocumentBuilderFactory.newInstance();
         db = dbf.newDocumentBuilder();
         doc = db.parse(New File("path/to/your/file"));
         Node root = doc.getDocumentElement();
         System.out.println("Root Node = " + root.getNodeName());
         readNode(root);
    }catch(FactoryConfigurationError fce){ fce.printStackTrace();
    }catch(ParserConfigurationException pce){  pce.printStackTrace();
    }catch(IOException ioe){  ioe.printStackTrace();
    }catch(SAXException saxe){  saxe.printStackTrace();
    private void readNode(Node node) {
    System.out.println("Current Node = " + node.getNodeName());
    readAttributes(node);
    readChildren(node);
    private void readAttributes(Node node) {
    if (!node.hasAttributes())
         return;
    System.out.println("Attributes:");
    NamedNodeMap attrNodes = node.getAttributes();
    for (int i=0; i<attrNodes.getLength(); i++) {
    Attr attr = (Attr)attrNodes.item(i);
    System.out.println(attr.getNodeName() + " => " + attr.getNodeValue());
    private void readChildren(Node node) {
    if (!node.hasChildNodes())
         return;
    System.out.println("Value/s:");
    NodeList childNodes = node.getChildNodes();
    for (int i=0; i<childNodes.getLength(); i++) {
    Node child = (Node)childNodes.item(i);
    if (child.getNodeType() == Node.ELEMENT_NODE) {
    readNode(child);
    continue;
    if (child.getNodeType() == Node.TEXT_NODE) {
    if (child.getNodeValue()!=null)
    System.out.println(child.getNodeValue());

  • Premier Pro CC and Media Encoder crashing on long file export.

    Please forgive the length of this inquiry. But it is complicated and has a lot of variables.
    I have an hour long mixed format timeline both Red 3K footage and Black Magic ProRes 1080P footage that I want to make a DVD from and it takes forever and crashes half way through. I have tried doing it every way possible and the only way I was able to get even a partial export was using the "MPEG 2 DVD" export option in Premier CC. It goes fast at first telling me it will take about 2 hours but even though it starts quickly doing about 15 fps it slows down to less than 1 fps and finally just stops and crashes my Cuda Core enabled Macbook Pro Laptop.
    I really don't know who to ask about this since there are so many different variables. I never had a problem like this on my MBP with PP6 on a 4K timeline exporting to DVD or Blue Ray or to H-264 or Even Prores. But I wasn't mixing formats either. But on this project the first 20-30 minutes of footage goes through fine in a couple of hours but something seems to be bogging down the system on longer projects. My work around was to break the project up into multiple exports and combining them on the DVD timeline but I can't do this on every project. I thought maybe it was a corrupted clip somewhere in the timeline but when I broke the timeline up into several parts I had no problems.
    I did notice a dramatic variance in the time it took to export footage based on the sequence settings. A one minute timeline comprised Red 3K footage and ProRes 1080P footage Here are some sample export results:
    From a Red raw 3K timeline 2880x1620  with 1080P Prores footage upscaled 150%)
    to .m2v Mpeg 2 720x480 format    1:48 Minutes ***
    to .mov  Prores 422HQ  1080P                         22 Minutes
    to .mov H.264  1080P                    22 Minutes
    to .m2v Mpeg 2 1080P                                                22 Minutes
    From a 1080P timeline Prores footage at 100%  (Red footage downscaled to 67%)
    to .m2v Mpeg 2 720x480 format                         13 Minutes
    to .mov  Prores 422HQ 1080P                             13 Minutes
    to .mov H.264  1080P                                                             14 Minutes
    to .m2v Mpeg 2 1080P                                                            14 Minutes
    Since I am going to DVD,  I chose the fastest option  Red to m2v Mpeg 2 720x480 format which only took 1:48 per minute. Why? I have no idea. Maybe someone here knows the answer. But again these numbers are for a ONE MINUTE clip when I tried to convert the whole hour timeline to  the 720x480.m2v DVD File the Red timeline froze my computer after several hours even though I had set sleep mode to “Never” and turned the display off manually and I had to convert it in multiple chunks. In 20-30 minute chunks it did go fast about 1:48 per minute like the test indicated. But I would like to be able to convert the whole hour and not to have to try to stitch the clips together in my DVD authoring program.
    I don’t want to have to avoid using multiple formats on the same timeline or waste time transcoding everything to the same format.
    Can anyone give me any suggestions as to why the computer is crashing or bogging down in long exports and what timeline settings I should be using?
    I have plenty of room on my Scratch Disk and 8 Gig of RAM and according to my Activity Monitor during the export process  have about 800 Meg of System Memory during export but the CPU Usage is 98% and in my Activity Monitor I see under “Process Name” ImporterRedServer flashing up at the top of the list about every second during export.
    Why .720x480 mpeg DVD setting is so much faster than all the other export codecs?
    And if there are any other settings I can use to get higher speed exports in HD? 14x1 seems a little slow especially since every time it crashes I have to start over.

    Hi,
    Since a long time I did not encounter the crash of Media encoder with
    long file export.
    But I take care of a lot of details before the export :
    - clean up Media cache and Media Cache Files within PP CS6 and/or CC,
    - delete all render files with Preview Files,
    - rendering of sequences until the rendering is completed,
    - PP CS6 and/or Pp CC opened during export to AME and/or Encore CS6,
    I guessed to leave Adobe but this company remains the last with a
    serious authoring software (Encore CS 6).
    I tested :
    - Avid Media Composer, Final Cut Pro X, both are very good software but
    no really authoring software for these video editing softs.
    Th only way is to "flood" Adobe with "bug reports" and "wish forms"
    which are not very easy to use.
    And also to call the Adobe support day by day until they send they
    escalate the bug.
    Le 16/05/2014 16:51, alainmaiki a écrit :
    >
          Premier Pro CC and Media Encoder crashing on long file export.
    created by alainmaiki <https://forums.adobe.com/people/alainmaiki> in
    /Premiere Pro/ - View the full discussion
    <https://forums.adobe.com/message/6384665#6384665>

  • ITunes freezes briefly when un-pausing near the end of a long file

    On the 1.6GHz G5 pro, 10.5.7 and iTunes 8.2 (and the problem occurred in earlier versions as well).
    I wouldn't notice this issue with 3-5 minute songs, but it's getting to be a problem with e.g. podcasts of several hours' duration. When the elapsed time cursor is over, say 30 minutes into a file, and I un-pause the playback, it will take maybe 5 seconds to begin playing. During this time, the only functioning element of the computer is the mouse cursor, and that only in movement. Clicks are queued but do not apply until the playback starts. Keyboard input is likewise queued. Monitoring the system with top(1) in the terminal or using the system monitor doesn't reveal anything - the displays freeze until play restarts. The system even stops responding to pings. Here's the trick - if I un-pause the replay even further into the track, say, an hour and fifteen minutes, it can take up to fifteen seconds of freeze before everything starts working again. If I pause, drag the time cursor back to the beginning, and hit play, play starts immediately and I can drag the cursor back to where I was with no freeze or interruption. It's only when I un-pause into a long file that the system freezes.
    Any ideas?

    I did find a workaround - note the time, drag the slider back to the beginning, and un-pause. It will start immediately. Then, drag the slider back to where you were in the file. It works, but it's really annoying, especially since this problem never happened until recently.

Maybe you are looking for