Drained Buffer?

Have an internal Pioneer DVR-103 that I have never used other than to burn audio CD's which have worked fine. And still do. Now trying to save photos on a DVD through IPhoto program. When I hit "Burn" after a bit the disk ejects & I pop it back in then this message comes up about "... the drive failed. The device drained its buffer without underrun protection". Tried to change speed but that option is greyed out. Not even sure if this is the correct way to save photos but it has worked on a CD...You can save just photos on a DVD right or should I stick to a CD? DVD's hold more, so I've got alot photos! I have tried all sorts of ways to save on the DVD & it still comes up with the same message. Can anyone help?? Attached device info. if needed. Thanks I hope!!
PIONEER DVD-RW DVR-103:
Manufacturer: PIONEER
Model: PIONEER DVD-RW DVR-103
Revision: 1.90
Serial Number:
Drive Type: CD-RW/DVD-RW
Disc Burning: Apple Supported/Shipped
Removable Media: Yes
Detachable Drive: No
Protocol: ATAPI
Unit Number: 0
Socket Type: Internal

Sounds like your discs are about the same age as my old ones and are probably 2x discs. Newer discs may be a problem if you cannot select the burn speed (Toast Titanium allows you to set the speed.)
Drained buffer means that the drives' read ahead buffer was depleted and the burn failed because there was a break in the data transfer (the disc is made in one burn attempt, anything that interrupts the process will cause problems.)
Another thing to try is to defragment your hard drive (how full is the hard drive?) If the drive has to look too long for the data then the buffer could get depleted.
Optical drives are notorious "dust filters" so a cleaning attempt may be a thing to try. Replacement drives are ~$30-40 US on-line.
Regards,

Similar Messages

  • SuperDrive Media Disc(s) .. Assist ...

    07.11.2005
    Dear Apple Mac Mini User forum participants
    b Macmini SuperDrive : Matsushita DVD-R UJ-845C
    How do we confirm the correct read/writable disc(s) media for our Mac mini ?
    We have searched widely .. specifically .. and generally .. online.
    And we come away with no new definitive knowledge. Others
    have trialled and erred .. and learned .. and reported. But still
    we are ill-informed about which particular media we should
    be restricting ourselves to use in our Mac mini.
    Are you able to assist by sharing your garnered information(s)
    about the correct media(s) for the Mac Mini Superdrive.
    We seek your illumination by kind response, if you will.
    Point us to the worthy online repositories or share your personally
    accrued gems of optical SuperDrive media disc management.
    And finally, for now, we would like to hear your formula for establishing
    the minimum specification to share your media disc(s) among your Mac
    computers in use and even with an XP machine, from time to time.
    Establishing the upper performances and the lower compatibilities would
    provide a practicable strategy to managing machine restricted and machine
    to machine informations sharing by optical drive media disc(s).
    Positively thanked will you be.
    very much obliged,
    Stuart .

    09.12.2005
    Dear Apple Mac mini user discussions participants
    Thank you to everyone who has constructively added to
    the body of useful knowledge now available in this
    humble thread. Your contributions are genuinely prized.
    Gems.
    We have read and re-read your entries, acting where
    able, to discover more about the true capabilities of
    the Mac mini SuperDrive mentioned. Along the way, we
    have discovered a few many other related and relevant
    aspects to the personal industry of media disc burning.
    Here is the Apple Mac mini ..
    About This Mac ..
    More Info ..
    Disc Burning ..
    MATSHITA DVD-R UJ-845C:
    Firmware Revision: DPP9
    Interconnect: ATAPI
    Burn Support: Yes (Apple Shipped/Supported)
    Cache: 2048 KB
    Reads DVD: Yes
    CD-Write: -R, -RW
    DVD-Write: -R, -RW, +R, +RW
    Burn Underrun Protection CD: Yes
    Burn Underrun Protection DVD: Yes
    Write Strategies: CD-TAO, CD-SAO, DVD-DAO
    Media: No
    One of the informations we seek is the speeds capacities
    of the SuperDrive mentioned. More frequently now .. in
    the stores .. you find speed rated disc media for
    burning. What are the rated speeds of the Mac mini
    SuperDrive and media ?
    What does CD-TAO mean ? TAO : TrackAtOnce
    What does CD-SAO mean ? SAO : SessionAtOnce
    What does DVD-DAO mean ? DAO : DiscAtOnce
    What does .. Media: No .. mean ?
    From here we begin to discover compatible media ..
    the original mission.
    Online .. here and elsewhere .. we are educated by the
    many who have trialed and erred before us. Most demanded
    manufacturer of disc burning media is 'Taiyo Yuden(s)'.
    Made in Japan. Taiyo Yuden Company Limited is mentioned
    by www.cdfeaks.com WIKI as the most preferred media too.
    Most recommended brand name of disc burning media is
    Verbatim.
    We searched for Taiyo Yuden(s) media in our geographical
    locale. Rare as hens teeth. Sold out before arrival.
    Premium price no deterrent to those in the business of
    quality disc burning. We settled for a couple of
    Verbatim DVD+RW media discs. Made in Taiwan. Every disc
    we could locate in retail was either made in Taiwan or
    made in Singapore.
    We began our media disc burning adventure by applying
    the native OS X Tiger 10.4.2 disc burning applications.
    Finder and Disk Utility. We bothered not with itunes,
    iphoto, since our mission is data. Problems emerged
    early. From the log file automatically kept by Disk
    Utility (top right hand corner of the DU window) you are
    able to read for yourselves the two error messages
    reported as operations failed. Error messages ...
    Finishing burn
    Verifying burn...
    Verifying
    Burn failed
    Verification of the burn failed.
    Unable to burn “backup xxxxxxxxxxxxxx xx.xx.xxx.dmg” -
    Verification of the burn failed..
    Burning Image “backup xxxxxxxxxxxxxx xx.xx.xxx.dmg”
    Preparing data for burn
    Opening session
    Finishing burn
    Burn failed
    The device failed to calibrate the laser power level
    for this media. Unable to burn “backup xxxxxxxxxxxxxx
    xx.xx.xxx.dmg” - The device failed to calibrate the
    laser power level for this media..
    Finder media disc burn error message ...
    This disc did not verify correctly and is unreliable.
    Because the disc is unreliable, discard it and try again
    using a new, blank disc. (Error code: 0x80020063)
    Success message - without verification ...
    Burn completed successfully
    Image “backup xxxxxxxxxxxxxx xx.xx.xxx.dmg” burned
    successfully.
    Operations failure .. we quickly discovered .. does not
    mean media disc burn total failure.
    All media disc burn operations were 'successful'. And,
    as soon as we unticked Verify data at end of disc burn
    (DU), we were regularly greeted with successful media
    disc burn dialogue affirmation. Encouraging .. and
    further confirmed as we examined the data burned and
    satisfied ourselves of the totality of the writing
    event. Otherwise .. DU had zero challenges media disc
    burning and reading burned media and copying data files
    back onto the originating apple mac mini hard disk
    drive. Remember that DU is limited to media disc burning
    in apple format only and multi-sessioning where on
    screen you will be greeted with individual icons
    representing each session burned on the same media disc
    burned.
    However, things went south far to soon and without very
    apparent reason. The DVD+RW was suddenly and perpetually
    rejected by the SuperDrive. No doubt .. the more
    informed among you are smiling and nodding knowingly ..
    at our novice and amateur opening efforts. Useless disc.
    You may be able to pinpoint the moment of coaster
    creation from the supplied error messages logged.
    We imagine that the lack of verification availability ..
    always displayed with an unsuccessful burn message,
    every time .. points directly to media disc quality.
    Unusable disc an eventual certainty. Perhaps.
    Every disc burned delivered an unsuccessful burn message
    whenever Verify data burned was ticked. Finder media
    disc burning does not provide apparent opportunity to
    switch off verification. Read-on .. if you are
    interested to discover our further media disc burning
    experiences and experimentations.
    We re-examined the apple computer help system from DU
    and learned that DVD+RW is the favoured alternate re-
    writeable format disc for DVD re-writing intended to
    replace the capabilities of DVD-RW and DVD-RAM and
    provide higher compatibility with set-top players ..
    though some DVD drives or applications may not support
    recording to this disc format. At the store .. we re-
    read the retail store chart by Verbatim on DVD options
    and learned of media designation purpose distinctions.
    Still .. we appear to have chosen within the SuperDrive
    capabilities. Another disc we should like to sample is
    the DVD-RAM disc .. which is not specifically mentioned
    as compatible media .. are you able to clarify whether
    Mac mini users with the mentioned SuperDrive
    MATSHITA DVD-R UJ-845C are able to use this designation
    ? And the reason for the question is that we have
    discovered a DVD-RAM disc available from a Japanese
    manufacturer. Premium price at the retailer .. assuming
    premium quality too. Appears, however that we are unable
    to use DVD-RAM media burn disc(s).
    After media disc burning the DVD+RW disc we then fed the
    written disc (and at that time, readable - by the
    originating Mac mini machine) to the iMac DV SE
    (graphite) running OS X 10.4.3 Tiger to confirm
    compatibility. Nightmare on Apple street. Barely able to
    read the media disc burned .. we eventually had to force
    the iMac cough the DVD+RW disc back out by manually
    restarting the iMac machine (side button) and holding
    the mouse button down on start-up. Disc retrieved ..
    safely. First time ever in five years of ownership ..
    since new. Bummer. To eliminate speculation of poor iMac
    DV SE drive performance we set about throwing other CD
    and DVD discs at the machine. Perfect. From the iMac ATA
    Device Tree - ATA Bus ... (no media disc burning capability)
    MATSHITADVD-ROM SR-8184:
    Model: MATSHITADVD-ROM SR-8184
    Revision: AA32
    Serial Number:
    Detachable Drive: No
    Protocol: ATAPI
    Unit Number: 1
    Socket Type: Internal
    Disk Utility and Finder are limited media disc burning
    applications. DU creates multi-session disc by burning
    separate instances that manifest as separate disc icons
    on the desktop. Operationally limiting and eventually
    problematical. iMac DV SE showed only the first media
    disc burn of a multi-session disc burned. DU is limited
    to media disc burning in Mac OS format only too.
    We returned the DVD+RW discs to the retailer .. one
    opened and used and fully rejected and the other
    unopened. Instead we chose to step down to Verbatim
    CD-RW discs .. made in Taiwan. We continue with our
    experimentations. Finder help reveals more about disc
    burning and under; "I got an 'unknown error' message
    while burning a CD or DVD disc" we find two links ..
    Apple Service & Support article: Problems burning discs
    [http://www.info.apple.com/kbnum/n25480] reads ...
    Mac OS X: "Unknown Error -2147352480" when burning CD-R,
    CD-RW, or DVD-R media Learn how to troubleshoot burn
    underrun protection issues ("Unknown Error -2147352480"
    alert) when burning a disc. This document applies to Mac
    OS X 10.2 or later.
    Try these tips:
    * Specify a burn speed that is less than the maximum
    speed rating for the optical drive.
    * Quit open applications you are not using. Open
    applications are marked with a triangle in the Dock.
    * Once a burn session has started, do not move, bump,
    or vibrate the computer.
    * Do not put labels on blank discs before burning them.
    * Use blank discs that are rated for the burn speeds of
    your drive, or consider using a different brand of media.
    * See "Macintosh: Factors That Affect Writing to or
    Reading From Optical Media".
    Your computer may also benefit from installing additional
    memory (RAM) or a higher-bandwidth system interface for a
    burning device (such as SCSI).
    You might also consider having the optical media device
    tested by an Apple Authorized Service Provider.
    Additional information
    The Console utility or log may report:
    "-2147352480 = 0x80020060 = kDRBurnUnderrunErr = Device
    drained buffer without burn underrun protection"
    Low disk space or RAM availability issues can lead to this.
    These are some clues that this might be the case:<
    * The issue more often occurs during the burn process.
    * The failed burn more often leaves data partially
    written to the disc, and he disc can't be reused.
    Physical source of these issues can lead to burn failures
    and can sometimes be identified when:
    * The issue more often occurs at the start of the burn
    process.
    * The failed burn session more often leaves the media
    untouched and ready to be burned. (It is still blank.)
    * The burn starts, but an external incident interrupts
    the session.
    ... and the one link on that page ...
    "Macintosh: Factors That Affect Writing to or Reading From Optical Media" ...
    Factors that affect writing to or reading from optical media
    This document discusses things can affect your computer's
    ability to write CD and DVD discs, and what can potentially
    affect their being read by other computers and consumer
    electronics equipment.
    Several things can affect the mastering of recordable media
    and the ability to read them by other devices. These factors
    equally apply to CD-R, CD-RW, DVD-R, and DVD-RW media.
    To consistently achieve successful burns, be aware of these
    factors
    The source for the media
    Third-party discs that conform to the specifications of the
    drive should operate as expected. However, since Apple has
    not physically tested these discs, you should contact the
    manufacturer if full compatibility cannot be achieved.
    Apple-brand discs are tested and qualified for use with
    Apple-installed optical drives and are fully compatible.
    The optical drive used to master the media
    Earlier drives may not work with some later, high speed
    media. Use discs recommended by your drive's manufacturer.
    Make sure you have installed any firmware updates available
    for the drive. Some updates may address media compatibility
    issues, or update the function of the drive in other ways.
    The software used to master the media
    Make sure the application software you use to master the
    discs is up to date. Make sure the options you choose in
    the application, such as the burn speed, work with the
    drive and the media you are using. Varying the burn speed
    may affect the compatibility of the media in the playback
    device. This may make a difference in the accuracy of the
    mastering of an audio CD or DVD. Burning applications often
    perform a verification after the burning process is complete.
    This ensures that the final disc is ready for playback.
    If the verification fails, try choosing a slower burn speed.
    The connection method for your optical drive
    If your burner is connected via USB, you may not be able to
    burn at the highest speed the drive is capable of using.
    Trying to burn at too high of a speed may lead to a failed
    burn because there is not enough bandwidth on the bus.
    If you have a SCSI burner, make sure the SCSI cabling is
    configured correctly, and that the SCSI chain is properly
    terminated. Issues may result from improper termination.
    Also, make sure you use properly-shielded cables to connect
    the burner to the computer.
    To successfully use your burned media, be aware of these factors
    The source of the media
    In general, if you are able to successfully burn discs in a
    drive, that drive should be able to read the same discs without
    an issue.
    Note: Apple optical drives work with standard 650 MB-capacity
    discs, but not all drives work with 700 MB-capacity (80 or 90
    minute) discs.
    The optical drive used to read the media
    Earlier optical drives may have issues reading modern media.
    Early DVD-ROM drives, for example, may not read burned DVD-R
    or DVD-RW discs. Some may read DVD-R, but not DVD-RW. This is
    true for consumer audio CD players, car audio players, and
    DVD-Video players, too. Depending on when the drive was
    manufactured, it may or may not be compatible with certain
    burned media. Check the documentation that came with the player,
    or check with the manufacturer for more information. A firmware
    update may be available that improves compatibility. Even if it
    is considered "compatible" with certain media, you may encounter
    issues with some brands of media, or issues with media burned at
    certain speeds.
    The software used to read the media
    You may find that software designed to copy data to discs cannot
    successfully copy video or audio to discs. Make sure you are
    using a current version of the application, and that the software
    can copy the kind of data you are working with.
    For best success in reading media, use the latest version of
    the Mac OS. Also, make sure that you burn the disc in a format
    that can be used by the operating system that will read the disc.
    For example, a CD burned in Mac OS Extended (HFS Plus) format
    may not work with a Microsoft Windows-based computer.
    If a disc's format is not normally recognized by the computer's
    operating system, you may need to install software that allows
    the computer to recognize it.
    Additional information
    60849: "Mac OS: How to Determine a CD or DVD Drive's Mechanism
    and Firmware Version"
    120029: "Power Macintosh G4 CD-RW Firmware Update: Information
    and Download"
    86130: "SuperDrive: Important Information About Using With
    High-Speed Media"
    ... 60849: "Mac OS: How to Determine a CD or DVD Drive's Mechanism
    and Firmware Version" ...
    ... blah about Apple system profiler .. where we started .. just
    one possibly useful link ...
    For the latest information about compatible CD-RW drives, visit
    the iTunes website.
    So .. we did .. and found nothing of specific use ..
    86130: "SuperDrive: Important Information About Using With
    High-Speed Media" ...
    ... blah about older mac computers and SuperDrive .. inapplicable.
    Apple Service & Support article: Hardware specifications
    [ http://www.info.apple.com/support/applespec.html ]
    ... interesting .. and could have been useful .. maybe
    .. if the mac mini were itemised at all .. not to be ..
    yet the hypertext link is in the mac mini help .. anyone
    see the mac mini here ? ...
    ... Moving along ..
    Finder help also explains about burning blank CD or DVD
    disc(s) and states that it will create burned disc(s)in
    'hybrid' format that can be read by most computers,
    including Windows computers. The (burned) disc contains
    these filesystem: HFS+, ISO-9660 with Rock Ridge, and
    Joliet with Rock Ridge. However .. "The names of files,
    folders, and the disc can't be changed after the CD is
    burned." So, a CD-R or DVD-R would seem the appropriate
    media disc(s) to use as they cannot be (erased and) re-
    written .. on any machine. [ but they can be written
    until full with other softwares and on other operating
    systems .. e.g. XP ]
    We used CD-RW to experiment with this capability .. by
    media disc burning data files to find out what we could
    do after the first Finder burn. Initially recognized as
    a CDR media disc. As you, dear reader, are by now, well
    aware, media burn automatic verification failed.
    Automatic ejection occurred after the burn and at the
    (usual) verification failure message from Finder.
    Re-insertion (after a delayed period) showed the CD-RW
    disc to be CD-RW Untitled CD .. even though we had
    titled the disc at dialogue box burn time. One folder
    and zero nested folder or data files content were shown
    as recorded in the Finder window. We know something is
    on the disc because the usage amount is shown as 353.6MB
    on the desktop icon. Second attempt to burn gave
    message: Insert a blank disc to begin. So CD-R is better
    value (read: cheaper) media than CD-RW for Finder burns.
    You can use use DU to erase the CD-RW. DU agrees with
    the media burned disc volume usage.
    Finder is doubly confusing because of two apparently
    colliding help entry explanations.
    Under: Disc burning options are dimmed or unavailable ..
    is the explanation: If the entry contains "-R", your
    computer can write to a CD-R or DVD-R disc only once. If
    the entry contains "-RW", your computer can erase a CD-R
    or DV-R disc and write to it again.
    However ..
    Under : I can't burn files on my recordable CD or DVD
    disc .. is the explanation: If the entry contains "-R",
    your computer can write to a CD-R or DVD-R disc only
    once. If the entry contains "-RW", your computer can
    erase a CD-RW or DVD-RW disc and write to it again.
    Personal experience proves the latter explanation to be
    the more correct one. We are unable to erase a CD-R or
    DVD-R disc on either Mac or XP machines. Whew.
    Are we missing something here ?
    Or is that the correct facts of the designations ?
    Finder also provides a run-down of Types of recordable
    CD and DVD media.
    Types of recordable CD and DVD media
    If your computer has an internal or external recordable
    optical drive supported by Apple, you can "burn" or
    record your favorite music, applications, documents,
    digital photos and video, and other digital files to
    recordable CD and DVD discs. You can create your own
    music CDs and play them on a standard audio player, or
    create DVDs with movies and slideshows and play them on
    a DVD player.
    There are several types of recordable CD and DVD media:
    • DVD-R discs hold about 4.7 GB of information.
    You can burn files on a DVD-R disc using the Apple
    SuperDrive. DVD-R discs are not reusable; you can burn
    files on them only once.
    • DVD+R is an alternate DVD Recordable write-once
    format. Some DVD drives or applications may not support
    recording to this disc format.
    • DVD-RW discs hold about 4.7 GB of information on
    each side. If you have an Apple SuperDrive, you can read
    information on these discs, but you can't burn files on
    them using Mac OS X. DVD-RW discs are reusable: you can
    burn files on them, erase them, and then burn again (if
    you have an application that is compatible).
    • DVD+RW is an alternate DVD ReWritable format
    intended to replace the capabilities of DVD-RW and DVD-
    RAM and provide higher compatibility with set-top
    players. Some DVD drives or applications may not support
    recording to this disc format.
    • CD-RW discs come in normal and high-speed
    formats. You can burn files on CD-RW discs using the
    Combo drive (or another supported CD burner). CD-RW
    discs are reusable: you can burn files on them, erase
    them, and then burn again.
    • CD-R discs come in two types. One holds 74
    minutes of audio, or about 650 MB of information. The
    other holds 80 minutes of audio, or about 700 MB of
    information. You can burn CD-R discs using the Combo
    drive (or another supported CD burner).
    For recording audio CDs, it is best to use CD-R discs
    because most standard audio CD players cannot read CD-RW
    discs. For longer-term storage and reliability, use CD-R
    discs.
    You can't burn anything on a CD-ROM or DVD-ROM disc.
    Enter Microsoft Windows XP Professional
    We are .. for once .. fortunate enough to have Microsoft
    Windows XP machine available to us with media disc
    burning hardware installed. Just like the Mac mini .. we
    do not have any other software installed for media disc
    operations, only from the native XP OS supplied tools.
    However .. we quickly discover that the XP machine has
    an edge .. licensed Roxio software integrated into the
    XP OS. And it works well. We discover that the Apple OS
    X media disc burning software Disk Utility .. chooses
    only to format in Apple OS. Meaning .. DU media disc
    burned with Mac mini are only able to be read by Apple
    OS machines. Confirmed by attempting to have the XP
    machine(s) read the disc burned. Unable. But .. media
    discs burned by XP machines are able to be read by the
    Apple machines. Because XP machines native OS media
    disc burning format appears to be an industry standard
    OS independent. Couldn't tell from the available
    information from the XP OS but suspect it is an ISO 9660
    format variation. To be exactly confirmed .. and it will
    be .. because the entire outcome of this mission is to
    arrive at a total media disc burning and sharing
    strategy among Apple and as a matter of operating
    contingency .. XP machines too. Open source
    applications in use by us are deliberately cross
    platform between XP and Apple machines. Data generated
    is able to be swapped or even shared among the machines
    with little or mostly no user operating challenges.
    Focus on productivity. The media disc(s) burned in the
    XP machine reads well in the Apple machines.
    The Finder media burned disc .. mentioned above earlier
    .. CD-RW .. read immediately on the XP machine .. folder
    and data files burned .. all there .. all on display.
    99% able to be copied to the XP machine hard disk .. and
    confirmed as a CD-R formatted disc since only option is
    to erase the disc and not add to the existing content ..
    thanks to the Apple Finder format for the re-use sharing
    limitations. So Apple SuperDrive cannot read it's own
    disc but XP machine can and is able to verify burn by
    way of 99% trouble free copy to XP machine hard disk.
    Here .. we begin to struggle with what is happening in
    our limited media disc burning experience(s).
    Enter Media Disc Burning Software
    Additional software has become necessary to accomplish
    our media compatibility and resource management
    requirement(s) .. and we are surely open to your welcome
    suggestions for software applications that enhance the
    available Tiger OS X applications for dependable
    outcomes.
    Remembering for a moment that we have arrived at almost
    total incompatibility between the two Apple disc media
    drives mentioned after burning disc(s) in the Mac mini
    using DU and Finder and attempting reading in the iMac
    DV SE. We are searching for ways to achieve worthwhile
    compatibility.
    And one way is to use the XP machine to create data
    burned media disc(s) that are instantly able to be
    easily read by both Apples in our humble possession.
    This fact is an earlier discovery .. when migrating
    (again) from the XP realm to Apple heaven. Moving open
    source application data files form the XP realm to
    the Apple iMac DV SE machine was unencumbered. Easy.
    How unprepared we are for the encounter with OS X media
    disc burning tools limitations.
    We go on-line to seek any worthwhile open source media
    burning software for OS X. www.pure-mac.com lists
    several possibilities. We need to burn media disc(s)
    that are able to be read by a wider population of
    computer systems including Apple (OS X) and PC (XP) and
    be fully (re-)used to their manufactured storage
    capacities. A combination of Finder and Disk Utility,
    if you will.
    We quickly learn that Roxio is evidently the developer
    of the supreme media burning software available to Apple
    users. And garner from on-line sources that Roxio is
    favoured by the serious and casual user who demands
    quality.
    For the moment we choose to learn more by trialing less
    expensive media disc burning software(s) to find out
    whether our simple needs (and open source patronages)
    can be met by available applications without unnecessary
    bells and whistles. We may be wasting our time here ..
    if Roxio or similar is favoured by so many and not
    because of the bells and whistles but rather
    because of media disc burning performance quality and
    standards then we are likely to arrive at that same
    destination too. As satisfied Roxio user.
    www.pure-mac.com displayed the media disc burning software list below .. in alphabetical order ...
    CD Session Burner
    BurnAgain
    BurnX Free
    Burnz
    DiscBlaze
    Disc-o
    Dragon Burn
    FireStarter FX
    ImageBurner
    Jam
    PatchBurn
    Popcorn
    Toast
    YuBurner
    BurnAgain is one of the programs we chose to experiment
    with to create more standards compatible media disc(s)
    burned. BurnAgain is developed only for the OS X.
    BurnAgain automatically and only formats in ISO 9660
    (Rock Ridge) .. guaranteeing Windows machine
    compatibility. And it does .. so far .. we have used up
    about 5 of the available 10 burns before registration
    should be made with the author. We learn from the
    BurnAgain help system that iTunes burns the same as
    Finder.
    However, BurnAgain focuses only on CD-R and CD-RW media
    .. SuperDrive is capable of more. And you are
    discouraged from mixing media disc burning applications
    to burn the same media disc. BurnAgain prefers you to
    stay the course. DU is the OS X solution to alternate
    media burning (DVD) .. but apple OS format only.
    However, still our iMac is troubled and challenged to
    fully and properly read the BurnAgain media disc(s)
    burned (CD-RW) by the Mac mini .. it couldn't .. but
    eject was a formality and not a crises recovery
    management procedure as before with the DVD+RW disc
    burned by DU on the Mac mini.
    XP machine could read the BurnAgain CD-RW Verbatim
    disc(s) easily and fully .. but copying was about 99%
    accurate (same as Finder). We are writing about 350
    Mbytes of data files recorded on the CD-RW media disc
    with nested folders up to several deep. However,
    subsequent burns to disc(s) wouldn't repeat the same
    data file errors .. meaning if you noted the delinquent
    files then you could just BurnAgain those files and
    expect eventual full disc to hard drive copy success on
    the target machine (XP in our situation) of those
    deliquent datafiles.
    Originating Apple Mac mini machine could read the
    BurnAgain CD-RW verbatim disc(s) easily and fully .. and
    copying was 100% accurate back onto the originating
    Apple Mac mini machine hard disk .. all 350 Mbytes of
    data files .. no error messages reported. Meaning the
    originating machine is performing as expected .. with
    BurnAgain .. but sharing remains a challenge with other
    machines. Particularly iMac DV SE. Remember that Finder
    media disk burned couldn't read again on the Mac mini.
    BurnAgain is clearly an improvement of standards based
    media disc burning .. since originating Mac mini could
    read it's own burn and XP machine 99% accurate too. DU
    is OK if you are confining yourself to Apple machines
    and they can actually read the media disk burned .. only
    originating Mac Mini was able to read it's own burn 100%
    MATSHITA DVD-R UJ-845C is the most modern and capable
    (Super)drive among the five disc media equipped machines
    available here. For now we are confused whether that is
    any advantage or disadvantage.
    We are going to run through the remaining media disc
    burning softwares available from the www.pure-mac.com
    website to determine if our simple needs can be met
    or whether we are required to plumb for the creme deluxe
    (Roxio) and have greatest confidence that our media disc
    burning needs are fully met. We may report back our
    findings to anyone so interested at this forum. Are you?
    We also chose to sample a Verbatim CD-R media disc for
    burning and copying of data files among machines.
    However .. the BurnAgain burn went well .. but the
    copying was problematical to the XP machine hard disk ..
    file copy errors .. and back on to the originating Apple
    Mac mini machine hard disk too .. Error code - 36 (same
    file errors as XP machine). We tried again and met error
    messages from the BurnAgain application .. to the effect
    that BurnAgain would not permit a further media disc
    burn .. even though few hundred megabytes available on
    target media CD-R disc. This outcome .. according to
    Disk Utility help is because: "Mac OS Extended allows
    burning the disc more than once. Formats such as ISO
    allow burning the disc only once." Off to the XP machine
    and burn an additional small file to the disc. Perfect.
    Back to the Apple originating machine .. copy file to
    the Mac mini HD. Perfect. Kept the disc for any future
    file transfers between the XP to the Mac(s) until fully
    used. How confusing .. and .. yes .. frustrating too.
    Burnz is the only other program we choose to sample
    after studying the homepages and value propositions
    and our needs assessment. Thank you to www.pure-mac.com
    for the compilation(s) and accessibilities. Appreciated.
    Burnz developer www.thinkertons.com have other software
    available too. While downloading Burnz media disc burn-
    ing software for trial evaluation .. we browsed Burnerz
    .. another application from thinkertons that is 100%
    free. Burnerz is an informational tool .. and retrieves
    whatever informations available on your system about
    optical media drives fitted and attached and your
    computer systems' optical media drive compatibilities.
    Burnerz is a welcome assist for the knowledge starved
    and delivered up useful confirmations of the MatShita
    DVD-R UJ-845C optical superdrive fitted by Apple. Nice
    one thinkertons.
    Here is the information display from Burnerz ..
    106 Supported Drives in this Version of OS-X
    ( that would be Tiger 10.4.3 fully updated mac mini )
    AppleShipping MATSHITA DVD-R UJ-845C, Internal via ATAPI
    Device Information
    2005-12-06 15:39:56 +1300
    ProfilePath: built-in
    IORegistryEntryPath: IOService:/MacRISC2PE/pci@f4000000/
    AppleMacRiscPCI/ata-6@D/AppleKauaiATA/ATADeviceNub@1/
    IOATAPIProtocolTransport/IOSCSIPeripheralDeviceNub/
    IOSCSIPeripheralDeviceType05/IODVDServices
    CanWriteCDText: YES
    CanWriteDVDPlusRDoubleLayer: NO
    CanUnderrunProtectDVD: YES
    CanWriteDVDR: YES
    CanWriteDVDRAM: NO
    CanWriteDVDDAO: YES
    CanWriteIndexPoints: YES
    CanWriteDVDRW: YES
    CanWriteCDTAO: YES
    CanTestWriteCD: YES
    CanUnderrunProtectCD: YES
    CanWriteCDSAO: YES
    CanWriteCDRaw: NO
    CanWriteCDRW: YES
    CanWrite: YES
    CanWriteCDR: YES
    CanWriteCD: YES
    CanWriteDVD: YES
    CanWriteDVDRDualLayer: NO
    CanTestWriteDVD: YES
    CanWriteDVDPlusRW: YES
    CanWriteDVDPlusR: YES
    CanWriteISRC: YES
    PhysicalInterconnect: ATAPI
    FirmwareRevision: PP9
    LoadingMechanismCanEject: YES
    ProductName: VD-R UJ-845C
    SerialNumber: MATSHITADVD-R UJ-845C 5D0A25C7
    VendorName: MATSHITA
    LoadingMechanismCanInject: NO
    WriteBufferSize: 2048
    PhysicalInterconnectLocation: Internal
    SupportLevel: AppleShipping
    LoadingMechanismCanOpen: NO
    Device Status
    2005-12-06 15:39:56 +1300
    MaximumWriteSpeed: 2822.4
    MediaState: MediaPresent
    CurrentWriteSpeed: 2822.4
    MediaIsBlank: NO
    MediaBlocksUsed: 173914
    BurnSpeeds: Object of Class: NSCFArray, description: ()
    MediaBlocksFree: 0
    MediaIsReserved: NO
    MediaIsAppendable: NO
    MediaIsErasable: NO
    MediaFreeSpace: 0
    MediaClass: CD
    MediaIsOverwritable: NO
    MediaSessionCount: 1
    TrackNumber: 1
    FreeBlocks: 0
    SessionNumber: 1
    TrackLength: 173914
    BlockSize: 2048
    TrackIsEmpty: NO
    SessionFormat: 0
    TrackType: Closed
    TrackStartAddress: 0
    BlockType: 8
    MediaType: CDROM
    MediaBlocksOverwritable: 0
    MediaUsedSpace: 173914
    TrackRefs: Object of Class: NSCFArray, description: (<DRTrack: 0x003B4950>)
    MediaBSDName: disk1
    MediaOverwritableSpace: 0
    MediaTrackCount: 1
    IsBusy: NO
    IsTrayOpen: NO
    And here is the Media information from Mactracker ..
    www.mactracker.ca .. a free informational tool on
    everything Apple hardware ...
    Media: 4x8x16x8x24x SuperDrive
    .. Dunno exactly what those numbers mean ..
    And here is the Media information from Mactracker on the
    iMac MATSHITADVD-ROM SR-8184 ...
    Media: 24x CD-ROM or 4x DVD-ROM
    Imagine that means read at 24x CD-ROMs and 4x DVD-ROMs
    Back to BURNZ
    Burnz has a particular feature that meets our
    requirements and added weight to the application's value
    proposition. You are able to choose the specific optical
    media disc burn format. Five graduations exist.
    Each graduation includes (all) of the lower ranked media
    burn format qualities. Top to bottom sliding scale.
    HFS+
    ISO 9660 Joliet extensions
    ISO 9660 RockRidge extensions
    ISO 9660 level 2
    ISO 9660 level 1
    Visually affirmative .. this feature gives user
    confidence about media disc burned format
    compatibilities. And the website and written materials
    from thinkertons make clear that compatibility is well
    covered for all optical media drives. Exactly what we
    seek. Default is HFS+ which thinkertons encourages you
    to maintain unless you do reason to otherwise change.
    Finally, for now, Burnz writes DVD media disc(s) too.
    Wethinks .. could we go wrong now .. as we progressed to
    practical evaluation. 10 free burns before registration
    is required by thinkertons. Here we go ..
    We chose 407.29mb data files .. application downloads
    and Tiger updates (.dmg, .zip, .bin) .. in one folder
    to brand new Verbatim CD-R (702.82mb available according
    to Burnz) .. and settings to maximum possible speed
    (automatically selected at 16x) .. other selectable
    speed setting is 8x .. and leave disc appendable ..
    verify burned data ON ...
    Burn failed...
    StatusError: -2147352477
    ErrorString: Verification of the burn failed
    RE-inserting the media burned disc gave desktop CDR
    icon with the burn folder named and 406.9 MB usage ..
    Finder (double click on the desktop disc icon) shows
    all 18 items burned .. copy from CDR back to new desktop
    folder showed the appropriate copy dialogue box and
    progress bar without color .. left awhile to see what
    happens ...
    The Finder cannot complete the operation because some
    data in "Gimp-2.2.8.dmg" could not be read or written.
    (Error code -36).
    Error code -36 is becoming an old friend ..
    Repeating the operation minus "Gimp-2.2.8.dmg" ..
    same drill .. offending file "MacOSXUpdate10.4.3.dmg" ..
    repeating minus "MacOSXUpdate10.4.3.dmg" .. same
    drill .. repeating minus "PDFLab.dmg" .. that's three
    out of total 18 so far .. and not one copied from disc
    to desktop .. last chance before coaster designation
    is applied as we get the pattern and the picture ..
    down to 245.9 MB to copy and still no satisfaction ..
    and now number 4 "Firefox 1.0.7.dmg" ..
    Houston .. we have a coaster .. trajectory .. garbage.
    Won't bother trying this disc insert into the iMac.
    However, we troubled ourselves to find out what would
    happen in the XP machine .. same outcome .. yes,
    readable by XP but copy failure to hard disk on the
    larger .dmg files. Not unexpected. Media format
    compatibility confirmed .. just as Burnz promised.
    Repeating the entire exercise with brand new Verbatim
    CD-RW (just to reduce CDR coaster count) .. this time
    at 4x write (automatically determined with no other
    speeds selectable - maximum possible) .. all other
    settings unchanged ... samo .. samo ..
    Burn failed...
    StatusError: -2147352477
    ErrorString: Verification of the burn failed
    RE-inserting the media burned disc gave desktop CDRW
    icon with the burn folder named and 406.9 MB usage ..
    Finder (double click on the desktop disc icon) shows
    all 18 items burned .. copy from CDRW back to a new
    desktop folder showed the appropriate copy dialogue box
    and progress bar color .. copy began immediately and
    reached the end .. Bingo .. we have a winner ! .. or
    do we ? .. Opening 50% of the now copied to desktop .dmg
    files produced an error message: The following disk
    images failed to mount. And for each delinquent .dmg ..
    the same Reason: codec overrun .. quite whatever that is
    meaning .. we appreciate the .dmg is damaged and now
    useless. Always the larger .dmg files .. up to 125 MB.
    On the Apple .. we are down two for two .. let's go
    again with burn verification off .. but first erase the
    disk with DU quick erase .. done .. now regarded again
    as an empty CDR by Finder .. (note that 'Erase disc
    before burning' is an available option in Burnz and on
    the Burn Disc dialogue box .. but it wasn't available
    as soon as the previously burned media disc was
    re-inserted for deleting and re-burning) ..
    No burn failure message .. as expected .. 406.9 MB
    usage on CDRW .. as expected .. Finder shows all
    18 items burned .. copy to desktop .. seemingly
    good .. as before and usual .. opening .. again
    a 50% failure rate .. same message .. same result.
    And in the XP machine .. same for read and copy to HD.
    OK .. let's give it one last go with the .dmg's, .bin's,
    and the .zip files .. by erasing again (with DU again)
    and media disc burning the CD-RW with just one file at
    a time and then copying back to confirm burned file
    integrity .. that's totally 18 burns .. but we shall
    only go as far as 9 file burns and copy back to the
    desktop from the burned media disc .. if all 9 are
    good then we shall assume it would all be good. We
    trial the big .dmg's to begin .. interestingly, erase
    disk before burning is available now and so we use
    that feature rather then DU (perhaps because the
    burn is less than the remaining disc storage available)
    .. is that a bug ? we wonder .. we turn Verify burned
    data ON .. just curious .. we are asked about our erase
    certainty before proceeding .. we click yes ..
    burning .. 97 MB .dmg .. burned (no negative
    verification error message) .. now copying back to
    desktop .. opening .. and .. codec overrun message.
    Finally, for now, we return to our original evaluation
    folders and files trialled with BurnAgain .. and perform
    the same media disc burn and onto the same (new) media
    disc (i.e. CD-RW) from the same batch too .. using Burnz
    .. Verify ON ...
    Burn Failed ... blah
    Copying back to desktop .. copy back is good .. just
    like BurnAgain .. encouraging.
    What that says about the larger .dmg files or perhaps
    any larger (50mb+) files to burn is unclear .. do you
    need even better hardware (media and burner) and
    software ? .. or are you out there in expert land able
    to advise readers how you do exact maximum confidence
    on the larger files media disc burn(s)?
    No DVD media burn disc(s) lying around here, for now,
    so we shall reserve any outcomes for another day of
    evaluations and experimentations.
    BurnAgain and Burnz go head to head .. From the tests
    performed to date we are able to comment from personal
    experimentation and practical experience .. they are
    very much similar quality .. Burnz does DVD's too.
    However, neither managed to accomplish entirely reliable
    media disc burn(s), of use, beyond the originating Mac
    mini SuperDrive .. nor accomplish verification .. is
    that normal ? Or do we have a particular problem ?
    We are back to square one for verifiable media disc
    burning.
    Interestingly .. those 10 free media disc burns
    available .. have only reduced by the number of burns
    without verification .. since negative verification
    appears to not count .. 8 free burns still available ..
    Recap On Applications, Capabilities and Limitations as
    encountered To Date ..
    SuperDrive MATSHITA DVD-R UJ-845C : Mac mini (Apple)
    Apple OS X Disk Utility : apple OS format only
    : multi-session burn(s)
    Apple OS X Finder : apple OS format,
    : ISO 9660 Rock Ridge..
    :..Joliet with Rock Ridge
    : one burn only each media disc
    OS X BurnAgain : ISO 9660 Rock Ridge
    : do not mix burn applications
    : CD-R & CD-RW media disc(s)only
    : no DVD media disc burn feature
    OS X Burnz : ISO 9660 level 1
    : ISO 9660 level 2
    : ISO 9660 RockRidge extensions
    : ISO 9660 Joliet extensions
    : HFS+
    : CD-R & CD-RW media disc burn
    : DVD-R & DVD-RW media disc burn
    [1]Sony cd-rw crx230e (CD 207x rd, 52x Wr):XPmachine(PC)
    XP integrated tools .. : ISO 9660 ?*
    .. Windows Explorer :read SuperDrive Finder CD media
    :..disc(s) burned and copy to HD
    :..and write to CD media disc(s)
    :..burned with Finder
    :read SuperDrive BurnAgain
    :..CD media disc(s) burned and
    :..copy to HD and write to CD
    :..media disc(s) burned with
    :..BurnAgain application but
    :..preferred that you do not
    : limited to and tested only CD
    ?* .. opening resource: http://aumha.org/win5/a/xpcd.php
    Explains more about XP native CD media disc burning and
    further links to more well informed research webpages
    that show XP appears to apply ISO 9660 Joliet .. to
    manage long file names, primarily. The entire area is
    wide-scope with technicalities .. access
    www.cdrfaq.org and see for yourself how deep the rabbit
    hole goes. Software is performing an important aspect
    of your optical drive media disc burning capability ..
    as hardware specs improve and softwares fully use the
    available service offered by the developing hw/sw
    standards .. as evidenced by browsing the cdrfaq.org
    .. you can see how things have moved along for the
    user's benefit and advantage.
    MATSHITA DVD-R UJ-845C : iMac DV SE (Apple)
    : read only media disc(s) burned
    from Mac mini.. : cannot read SuperDrive media
    from mac mini.. :..disc(s) burned on DVD or CD
    from XP machine.. :can read media disc(s) burned..
    from XP machine.. :..on XP machine (test only CD)
    : if SuperDrive media disc burn first and then further
    written and so added to by XP machine..unable to read.
    (applied to Os X Finder, BurnAgain and Burnz
    applications)
    We are safely at the point where we can assert that we
    have a potential operating solution for the Mac mini
    media disc burning. However, we remain reliant on our
    XP machine to create media disc burned that can be read
    fully by the iMac DV SE. And we have no confidence to
    date in the ability to share information burned by the
    Mac mini with any other party .. except where we can
    repeat ourselves over several iterations to accomplish
    100% data transfer .. and that means we are confined to
    our home operating computer systems. For now, XP machine
    is required to write a media disc that can then be read
    by the iMac DV SE. (Yes, we do have a Mac to Mac network
    .. but if data is unavailable on either of the Mac
    machine drives then we are required to resort to hard
    media backup) Media disc(s) sampled to date .. Verbatim
    CD-R, CD-RW, DVD+RW .
    Apple quality media pack (8x DVD-R only)*• is available
    at www.apple.com and in our locale. We shall sample the,
    not inexpensive, apple media disc(s) in the near future
    .. and report back. Still the DVD-R is write once. And
    no mention of any CD-RW apple quality media
    availability. Remember ...
    *• DVD-R discs hold about 4.7 GB of information.
    You can burn files on a DVD-R disc using the Apple
    SuperDrive. DVD-R discs are not reusable; you can burn
    files on them only once.
    [1] Action item one is to acquire genuine quality media
    disc(s). [ to, ideally, accomplish burn verification ]
    If 100% media disc burn and verification were able to be
    accomplished by the OS X supplied applications Finder
    and Disk Utility then only limitations to overcome are:
    Finder's (improved standards adhering) write once only
    to media disc feature and Disk Utility's apple OS only
    media disc burned format limitation and maybe multi-
    session disc burning feature.
    [2] Action item two is to acquire genuine quality media
    disc burning software(s). [to accomplish burn media
    capacities and maximum standards adherences ]
    If fuller standards compatibility and media disc burn
    usage features are available then items one and two
    requirements seem to be met. And actions items three
    and four are no longer options of any material
    significance. That would be welcome.
    [3] Action item three is to optionally acquire an
    alternative media disc burning solution. [ to accomplish
    100% or nearest possible media burn quality and
    consistency ]
    [4] Action item four is to forego media disc burning
    (item three) in favour of external hard disk solution
    (which could be partitioned) to share datafiles among
    differing machines and operating systems. [ to resolve
    the media sharing challenge in the absence of
    satisfactory value media burning solution that meets
    quality, consistency and compatibility needs ]
    Hopefully .. this tale of media burning discovery does
    ignite some passion and interest among certain others of
    you who may be willing to share a little of your own
    enlightening discoveries in the industry of media disc
    burning and any Apple SuperDrive MATSHITA guidelines or
    guidance(s) that you have established .. in particular.
    For now .. and until any further future update .. thank
    you again everyone .. we look forward to any remedial
    solutions that you may have developed to your media disc
    burning operating satisfaction. Much have we to learn ..
    search for answers continues ...
    Well .. it's been fun .. in an adventurous and discovery
    kinda way .. but back to our chosen path must we return.
    Stuart.
    Additional Informations ...
    We only ever used the software system default media disc
    burning speed settings where no choice permitted, or
    where choice permitted .. we used half (the
    automatically selected ) speed setting or lowest
    possible speed setting.
    Xp machine OS: Windows XP (5.1.2600 Service Pack 2)
    XP machine media disc burner: Sony cd-rw crx230e
    [+]Sony cd-rw crx230e (CD 207x rd, 52x Wr)
    This is what we want(ed) to know about the Apple
    MatShita SuperDrive too ! (opensourceuser note: crx230ae
    is the closest we could find to XP revealed Sony optical
    drive)
    [+]SPECIFICATIONS
    PART NUMBER CRX230A/U
    DRIVE TYPE Internal
    MEDIA & MODES SUPPORTED CD-R, CD-RW, CD-ROM (Mode 1 & Mode 2),
    CD-ROM XA (form 1 & form 2), CD Audio, Video CD,
    CD Extra, Multi-Session, Packet Writing
    READ/WRITE SPEED CD-R Write: 4X, 8X, 12X, 16X CLV, 24 ~ 40X P-CAV,
    52X CAV (turbo mode) max.
    CD-RW Write: 4X, 8X, 10X, 12X CLV, 16 ~ 32X CAV max.
    CD Read: 52X max.**
    SUSTAINED DATA TRANSFER RATE 600 kB/s (4X CD-R/RW read/write)
    (CD-R/RW DISCS): 1,200 kB/s (8X CD-R/RW read/write)
    1,800 kB/s (12X CD-R/RW read/write)
    4,800 kB/s (32X CD-R/RW read/write max.)
    7,800 kB/s (52X CD-R read/write max.)
    RANDOM ACCESS TIME 100 ms
    INTERFACE ATAPI/EIDE
    LOADING MECHANISM Motorized tray
    MOUNTING Vertical or Horizontal
    BURST TRANSFER RATE PIO Mode 4: 16.7 MB/s, Ultra DMA Mode 2: 33.3 MB/s
    BUFFER MEMORY 2 MB
    POWER REQUIREMENTS +5V / +12V V DC
    POWER CONSUMPTION +5V: 1.5A / +12V 1.5A
    DIMENSION (W x H x D) 5.75 x 1.63 x 7.49 inches
    WEIGHT Approx. 2.2 lbs.
    PACKAGE CONTENTS CRX230A/U Drive
    ATAPI Cable
    Software installation CD-ROM: B’s Clip and B’s Recorder Gold
    Mounting Screws
    Quick Start Guide
    Limited Warranty Card
    SYSTEM REQUIREMENTS Intel®Pentium®II processor 400 Mhz or faster (or equivalent)
    CPU, 64 MB RAM, 1 GB available hard disk space
    recommended. Microsoft®Windows®98SE, Windows®
    Millennium Edition, Windows®2000 Professional, or
    Windows®XP Home/Professional operating systems
    WARRANTY One Year Limited
    *Buffer underrun protection technology is conformed to Sony’s Power-BurnTM drive specifications.
    **Requires Ultra High Speed Plus CD-RW Media
    (opensourceuser note: datasheet(s) supplied with images
    of the recommended Sony media disc(s) - however on
    closer inspection at the local store - Made in Taiwan)
    Still we did find TDK media disk - Made in Japan - at
    the same store and apart from the DVD-RAM media discs,
    the only one type CD-R, everything else from China to
    Singapore.

  • Removed some files from library folder

    moved files from library folder and attempted to put them back after experiencing major changes and problem. This is not correcting the situation what can be done to restore it back to what it was before I started?

    Hi Ali,
    Update, I did a verify permissions with disk utility and some stuff is where it should be now, (recovered iphoto yeah) but still a problem with other things as before.
    So to answer your questions,
    What is the exact path to this folder? And please post the contents of the folder.
    I get to her old itunes by the following path;
    home>music>itunes>itunes music - this folder contains folder icons of all her old itunes library, each artist has a folder, such as amy cook>list of albums>list of songs - if selected will than open itunes and will import to new itunes library.
    I don't quite understand the heirarchy you are describing. Please post the contents of her Home folder.
    Her home folder contains
    Desktop
    Documents
    Library
    Movies
    Music
    Pictures
    plus 9 folders she had created over the past four years these are intact and accessible to proper application programs (ie documents open in appleworks, pictures are from the pictures library not iphoto, 3rd party software such as genealogy programs are intact and up to date)
    "I find some old unchanged items such as itunes, imovie, email mailbox items, in a folder that she created before the change took place in her user
    account."
    What is the exact path to this folder?
    As for this folder some things were moved back to proper places with the above mentioned verify permissions, some like, mailbox items, I was able to import to current settings to restore to how it use to be. From what I gather she created this file when things were going wrong and she feared messing the whole thing up. I access this by the following path;
    home>library>(then the folder she created) Library do not touch.
    When I compare the main library file to my account main library file they do not contain the same items in fact many of the missing items seem to be in this folder that she created. I assume the ones I need are in this file she created but I am really hesitant to just start moving things around out of fear of creating more problems on her side or messing up my side.
    If you have sufficient available disk space, you shouldn't have any problem, but you need a reliable backup, just in case.
    In regards to archive/install - sufficient available disk space meaning as much or more than what I am currently using? How do I check this to be sure?
    Which brings me to a whole new question if you have time?
    We do have an external back up system, which we used before a semi-recent move, (I plan on finding the box it is packed in believe me), however we attempted to use imacs backup program to do a quicker backup, were able to back up her side onto disks, but when I attempted to do the same on my side I received an failure error screen something about a drained buffer and being unable to perform a backup. Please tell me I have not fried my dvd drive!!!
    Thanks again, hope I answered in a way that is helpful to you.
    need to know

  • Device drained its buffer w/out burn underrun protection

    I've been trying to burn one of my playlists from itunes, but after a minute or so, the message "The device drained it's buffer w/out burn underrun protection" appears, and the blank CD is ejected, with no tunes burned.
    I've never had a problem burning playlists before, and I have no idea what this message means, nor how to correct the problem. Help! please.

    Cyd,
    To even get started on resolving this issue, you and the others having the problem should all report (by posting here) the version of iTunes you are using and which built in external media drive your Mac has. I for example have an eMac with Combo drive and iTunes 4.7.1.
    I just ran across your post and "looked in" - so I promptly composed a new playlist and burned it to Maxell CD-R, 700 MB disk. It worked flawlessly.
    I've checked (as you probably have) every item on the iTunes Preference Panel and can't find anything about buffer size EXCEPT in "Advanced" under the streaming internet radio panel (or "window"). There is a buffer size selection of "small, medium, large."
    I see no indication that there's a connection between that and the "other" buffer which is for under-run protection. (Using Toast Titanium, there's a very clear arrangement of menus, including one for setting {disk burning} buffer size.)
    So I'm stumped too - except to suggest you try setting the streaming buffer to "large" just in case it's a "dual control" for the burning buffer also. Mine's set at Medium, by the way.
    Can't resist mentioning - I think your screen name is fantastic, I'm old enough to remember the lovely dancer / actress, Cyd Charisse.
    Regards,
    macnoel

  • "The device drained its buffer without burn underrun protection"

    I see so many postings about this but no answers?!?!
    I am trying to burn a movie made with iMovie HD to a dvd with my superdrive (details on the drive below). The DVD is Office Depot generic (not the best I know) DVD-R media. I have tried burning it with Dragon Burn and the mac disk utility, and keep getting the same error:
    "The device drained its buffer without burn underrun protection"
    How do I fix this? The movie is a 1.7 gig .img file . I have also tried burning it straight from iDVD and to know avail, same error. Suggestions?
    Here is my drive info.
    SONY DVD RW DW-U10A:
    Manufacturer: SONY
    Model: SONY DVD RW DW-U10A
    Revision: A43h
    Serial Number: EAB86043
    Drive Type: CD-RW/DVD-RW
    Disc Burning: Apple Supported/Shipped
    Removable Media: Yes
    Detachable Drive: No
    Protocol: ATAPI
    Unit Number: 0
    Socket Type: Internal

    Welcome to iDVD Discussions.
    How do I fix this?
    Suggest you create a disc image and then burn the DVD. File/Save as Disc Image...
    http://docs.info.apple.com/article.html?path=iDVD/6.0/en/18.html
    http://www.kenstone.net/fcphomepage/image_to_diskstone.html
    This will isolate any encoding/burning issues you may encounter. Once the disc image is created, double-click the .img and burn the virtual disc that should appear on your desktop, using Toast to burn the DVD. Disk Utility to burn the .img file. Usually, you can select a burning speed in Disk Utility.
    There are variations to this process based on which OS X you are using...
    Open Disk Utility (in Utilities folder in Applications folder), click on the virtual disc (maybe the .img) in the left-hand window. Click the Burn icon. A new window should drop down and your SuperDrive tray will open after clicking the Burn icon. Insert a recordable DVD. (Verbatim DVD-R preferred by me.) Click the Close button. Wait. Select a burn speed. If you hold your mouse cursor over the pop-up it says: "Select a slower speed to work around burn failures," so select 4x or slower for best results. Then click the Burn button.
    -->If the virtual disk selection won't allow you to click the Burn icon, use the .img file instead. This may have changed in 10.3.9 and did change in Tiger.
    Also, you can use DVD Player to play the virtual disk to check your iDVD project before burning to DVD. Launch DVD Player. File/Open VIDEO_TS (Open DVD Media... in Player 4.6). Find the VIDEO_TS folder and open that. (The audio folder is for DVD-Audio disks.)
    http://docs.info.apple.com/article.html?artnum=93006

  • 4s with ios8 - battery drain issue - possible clue?

    I am one of the 4s users who is experiencing significantly accelerated battery drain since upgrading to ios 8.0 the first day it was released.  My battery will drain from %100 to less than %50 in less than two hours with typical light use.  Previously on ios 7.x I could go all day and be only down to %70 or so.  The way it's working now I won't make it through a day at work without having to recharge.
    I have tried optimizing in all the ways suggested in other threads (like turning off background apps etc.) and as far as I can tell my battery usage should be no worse (and presumably better since attention was given in ios 8.0 to making battery use better) than it was in ios 7.x.
    However, I'm wondering if this is causing my battery drain:
    In Settings->Privacy->Diagnostics & Usage->Diagnostic & Usage Data:
    There is a long list of "stacks+backboardd-2014-09-22-1..." files.  Yesterday (22nd) there were eight (8) of these rather large files created.  Today, on the 23rd, I'm up to three, when I looked this morning, there was just one.  Each file is rather massive, so something is burning a fair bit of energy triggering the debugging diagnostics tool to create and store these files.  (I'm guessing).
    Here's an example of the contents of one of them (just the head of the file, as I say, they are massive):
    {"os_version":"iPhone OS 8.0 (12A365)","bug_type":"188"}
      Incident Identifier: BDD2D474-CDCF-4409-8A16-732C2D22EF06
      CrashReporter Key:   f14750a09f7499f2bd4c6b15297406f27dc09a69
      Hardware Model:      iPhone4,1
      OS Version:          iPhone OS 8.0 (12A365)
      Kernel version:      Darwin Kernel Version 14.0.0: Tue Aug 19 15:08:02 PDT 2014; root:xnu-2783.1.72~8/RELEASE_ARM_S5L8940X
      Date:                2014-09-23 13:08:17 -0500
      Exception Code:      0xfaded322
      Reason:              Watchdog: Thermal not updating, backboardd 20.002234s last successful ping: 270b50 269f9fd0ce63 269r1d77000 200m0/1 200nffffffff 0m10004003/1 0u0 0n1
      Thermal data unavailable
      Frontmost process PID:    43
      Stackshot trace buffer size too small, trying again with 524288 bytes.
      Jetsam Level:              0
      Free Pages:              797
      Active Pages:          41652
      Inactive Pages:        18292
      Purgeable Pages:          71
      Wired Pages:           23313
      Speculative Pages:     20591
      Throttled Pages:       24377
      File-backed Pages:     67840
      Compressions:              0
      Decompressions:            0
      Compressor Size:           0
      Busy Buffer Count:         0
      Pages Wanted:            533
      Pages Reclaimed:           0
      Process 0 info:
              resident memory bytes:  64299008
              page faults:                3789
              page-ins:                      0
              copy-on-write faults:          0
              times throttled:               0
              times did throttle:            0
              user   time in task:          25.616464 seconds
              system time in task:           0.000000 seconds
      Process 0 kernel_task threads:
      thread 0x65 TH_WAIT|TH_UNINT 0x803e35a8
              thread priority:               92
              Base thread priority:          92
              thread sched flags:     none
              kernel cont: 0x8007ea05
              user   time in thread:     1.234561 seconds
              system time in thread:     0.000000 seconds
      thread 0x66 TH_RUN|TH_IDLE 0
              thread priority:                0
              Base thread priority:           0
              thread sched flags:     none
              kernel cont: 0x800294e5
              user   time in thread:     6.564943 seconds
              system time in thread:     0.000000 seconds
      thread 0x67 TH_WAIT|TH_UNINT 0x8002574d
              thread priority:               95
              Base thread priority:          95
              thread sched flags:     none
              kernel cont: 0x8002574d
              user   time in thread:     0.027250 seconds
              system time in thread:     0.000000 seconds
    ...etc...
    Anyway, just wondering if this might be related to why my phone's batter life has plummeted.  Also, does anyone have any insight as to what this file is actually telling us?  I'm happy to send diagnostics to Apple if it will help them get to the bottom of this issue that seems to be plaguing other 4s users.
    Thanks!
    James Rowell.

    I just wanted to post a small follow up. During my recent attempts to debug my battery issues, I rebooted the iPhone.  I don't think my phone had been rebooted since I did the upgrade and started experiencing these battery issues.  At any rate, since rebooting I have seen my battery use return to much more acceptable and expected rates of idle/usage times.
    Try rebooting your phone to see if it helps!  I wonder if it's just this simple for the folks who have been experiencing similar problems?!
    Good luck all.

  • Battery draining/o​verheating​?

    Situations just like today have been happening to me every day for the last two weeks, and I just want to know if other people are having "phone gets really warm" issues or if it's just me.  I ran an experiment of sorts this morning, not using my phone for a single thing, and the results of that experiment are below.
    I took my Pre [Sprint version] off the charger at 10:30AM.
    Got ready and drove to a friend's place in Atlanta.  Arrived just before noon.
    Had lunch and went to friend's house.  Arrived at about 1:30.  At this time, I looked at my phone for notifications and a battery check.  No notifications and battery icon was green and stated 100% still.  I was very pleased.
    Went into friend's house.  I could feel the phone getting warm in my pocket.  About where the microphone hole is, only on the back side.  Pulled out my phone and it was at 94% and falling.  Tried Airplane Mode.  Tried disabling roaming.  Tried disabling data.
    By the time I left at about 2:30-2:45, the battery was at 80% and continuing to fall.
    On my way back through Atlanta, the phone felt its normal temperature and battery was declining, but more slowly.
    Returned home around 4:30PM.  Battery was right around 60-65%.
    Things of note:
    During this time, I received and made no phone calls.
    During this time, I received and sent no text messages or e-mails.
    During this time, I used no applications and had no notifications.
    The screen was on for approximately five minutes total, just while I was checking the battery and applying my emergency settings.
    Don't know what's going on.  It's now 9PM and the phone is at 50% without having been used for a single thing all day.  The overheating issue can kill 20-25% of my battery and I am not always aware of when it happens as I keep the phone in the pouch.  I believe this started happening with the most recent update to 1.4.  I have tried all the common sense solutions such as:  set Bluetooth and Wi-Fi to off, set screen brightness to minimum, update software and roaming and PRL in the phone app.  I've done everything I reasonably can to make the battery last.  I really think it's the heating up--like it's stuck on something or busy or I don't know.
    Has anyone else had this same specific problem, and if so, what have you done about it?  Curious to know how I can get my phone functional again--right now, I'm afraid to use it for anything as it will kill the battery even more.
    Thanks for any help you can give me.

    I've posted about this on several boards and have yet to find an explanation. My experiences sound almost identical to what possiblybored is going through. You don't use the phone and it dies at an insane rate. Mine's been doing it for about four months now. I've been through four Palm Profiles and easily 20 WebOS Doctor "formats" and three different WebOS update patches. Nothing has fixed it.
    With the help of a few people on Precentral.net, I've found that the constant drain is due to the phone constantly waking up and sleeping, even when the screen is off. This is through constant monitoring of the /var/log/messages file while running Terminus. I eventually setup an SSH connection on my phone so I can connect to it using my desktop for easier reading. Here's what I receive while the phone's screen is off:
    Broadcast message from root (Mon Apr 5 18:32:49 2010):
    powerd: System going to sleep now
    Broadcast message from root (Mon Apr 5 18:32:51 2010):
    powerd: System woke up.
    Broadcast message from root (Mon Apr 5 18:32:52 2010):
    powerd: System going to sleep now
    Broadcast message from root (Mon Apr 5 18:32:53 2010):
    powerd: System woke up.
    Broadcast message from root (Mon Apr 5 18:32:54 2010):
    powerd: System going to sleep now
    Broadcast message from root (Mon Apr 5 18:32:55 2010):
    powerd: System woke up.
    If you look at the timestamps, you can see this happens once every couple seconds. ALL DAY LONG. When I view the /var/log/messages file while this is going on, this is what I come up with:
    Broadcast message from root (Mon Apr 5 18:34:41 2010):
    powerd: System woke up.
    2010-04-06T01:34:41.450042Z [585] palm-webos-device kern.info kernel: [ 585.620000] 00002732.980: enter suspend
    2010-04-06T01:34:41.450622Z [585] palm-webos-device kern.info kernel: [ 585.620000] 00002733.401: leave suspend
    2010-04-06T01:34:41.450927Z [585] palm-webos-device kern.info kernel: [ 585.620000] WAKEUP STATE/REASON
    2010-04-06T01:34:41.451202Z [585] palm-webos-device kern.info kernel: [ 585.620000] PM_WKST_WKUP 00000100
    2010-04-06T01:34:41.451629Z [585] palm-webos-device kern.info kernel: [ 585.620000] fastpath_fastsleep: Non RTC Wakeup
    2010-04-06T01:34:41.451934Z [585] palm-webos-device kern.info kernel: [ 585.620000] twl4030_phy_resume: mode=1
    2010-04-06T01:34:41.452301Z [585] palm-webos-device kern.info kernel: [ 585.630000] musb_softconn: on
    2010-04-06T01:34:41.452575Z [585] palm-webos-device kern.info kernel: [ 585.630000] twl4030_phy_suspend: irq_disable=0
    2010-04-06T01:34:41.452850Z [585] palm-webos-device kern.info kernel: [ 585.630000] phy_suspend: enter
    2010-04-06T01:34:41.453124Z [585] palm-webos-device kern.info kernel: [ 585.630000] musb_softconn: off
    2010-04-06T01:34:41.453369Z [585] palm-webos-device kern.warning kernel: [ 585.680000] Restarting tasks ... <6>timechange: time was changed.
    2010-04-06T01:34:41.459472Z [585] palm-webos-device kern.warning kernel: [ 585.740000] done.
    2010-04-06T01:34:41.476074Z [585] palm-webos-device user.info wall[2579]: wall: user root broadcasted 2 lines (27 chars)
    2010-04-06T01:34:41.492156Z [585] palm-webos-device user.info powerd: {powerd}: POWERD-SUSPEND: POWERD-WOKE after 1s : 0 days, 0h-0m-1s
    2010-04-06T01:34:41.492614Z [585] palm-webos-device user.info powerd: {powerd}: POWERD-SUSPEND: Wakeup Source: [ 585.620000] MODEM (MODEM_WAKE_USB) omap3_wakeup_sources_save+0x114/0x144 (a004962c)
    2010-04-06T01:34:41.492889Z [585] palm-webos-device user.info powerd: {powerd}: POWERD-SUSPEND: Wakeup Source: [ 585.620000] GPIO (RINGER_SWITCH) omap3_wakeup_sources_save+0x114/0x144 (a004962c)
    2010-04-06T01:34:41.493103Z [585] palm-webos-device user.info powerd: {powerd}: POWERD-SUSPEND: Wakeup Source: [ 585.620000] BUTTON (POWER_BUTTON) omap3_wakeup_sources_save+0x114/0x144 (a004962c)
    2010-04-06T01:34:41.587768Z [585] palm-webos-device user.info powerd: {powerd}: BATTERY_IPC: (1091.199951mAh, 94%, 98%_ui, 34C, -328mA, 4011mV, authentic)
    Broadcast message from root (Mon Apr 5 18:34:42 2010):
    powerd: System going to sleep now
    Repeating over and over, about once a second. This happens when connected via EVDO or WiFi. It happens when I'm not connected to the phone via SSH (spams my Terminus buffer). The results you're seeing above is from a phone that was Doctored with 1.4.1.1 (sprint) about 20 minutes ago. No profiles were restored (created a new one), no accounts were loaded (Google, Yahoo, Facebook, etc). One thing I noticed when my battery issues started was my data usage shot through the rough (to almost 2 GB a couple months ago). I'm averaging around 1.8 GB per month of data on my phone, and I don't tether. I ran the following command to check for open connections on the phone:
    netstat -a | grep "^tcp.*ESTAB"
    The results:
    tcp 0 0 72-62-209-65.pools.sp:59313 205.140.203.50:xmpp-client ESTABLISHED
    tcp 0 0 72-62-209-65.pools.spcs:222 ip68-226-115-44.ph.ph:52237 ESTABLISHED
    tcp 0 0 localhost.localdomain:4445 localhost.localdomain:56637 ESTABLISHED
    tcp 0 0 localhost.localdomain:56637 localhost.localdomain:4445 ESTABLISHED
    All of these make sense, except the 205.140.203.50, which is the only unrecognized remote connection. I was told that xmpp is a generic protocol for exchanging data, but we don't know what type of data. I used an app called JsTop to shut down all running applications on the phone, which should kill all connections not used by the OS itself. That remote connection did not go away.
    I've posted these results here already: http://forums.palm.com/t5/webOS-Software/1-4-is-ki​lling-my-battery/td-p/260368/page/7 but it has yet to receive the attention of a Palm Tech Support person. It's been buried to page two, so hopefully it will have some luck in this thread.
    I've also been in and out of the Sprint store half a dozen times with this issue over the last few months. They're unable to "replicate" it, but I doubt they're going to the lengths I am to find it. What does Palm say about this?

  • Requested buffer too large - but data is already in memory

    Hello all,
    I am writing a program that generates sound and then uses the Java Sound API to play it back over the speakers. Until recently, using clips have not led to any problems. On two computers I can play the sound without a hitch. However, on the newest computer (and also with the largest specs and especially more RAM), I am getting an error while trying to play back the sound. The exception that is thrown is:
    javax.sound.sampled.LineUnavailableException: Failed to allocate clip data: Requested buffer too large.
    I find this odd because the buffer already exists in memory: I don't have to read in a .wav file or anything because I am creating the audio during the course of my program's execution (this is also why I use Clips instead of streaming - the values are saved as doubles during the calculations and then converted into a byte array, which is the buffer that is used in the clip.open() method call). It has no problems allocating the double array, the byte array, or populating the byte array. It is only thrown during clip.open() call. I also find it strange that it would work on two other computers, both of which have less RAM (it runs fine on a machine with 512MB and 2GB of RAM, both XP 32-bit). The only difference is that the computer with the issue is running Windows 7 (the RTM build), 64-bit with 6GB of RAM. I am running it through Netbeans 6.7.1 with memory options set to use up to 512MB - but it's never gone up that far before. And I've checked the size of the buffer on all three computers and they are all the same.
    Does anyone know what the issue could be or how to resolve it? I am using JDK6 if that matters. Thank you for your time.
    Edited by: Sengin on Sep 18, 2009 9:40 PM

    Thanks for your answer. I'll try that.
    I figured it had something to do with Windows 7 since it technically hasn't been released yet (however I have the RTM version thanks to a group at my univeristy in cahoots with Microsoft which allows some students to get various Microsoft products for $12).
    Edit: I just changed the Clip to a SourceDataLine (and the few other necessary changes like changing the way the DataLine.Info object was created) and wrote the whole buffer into it, drained the line and then closed it. It works fine. I'll mark the question as answered, however that may not be the "correct" answer (perhaps it does have something to do with Windows 7 and not being completely tested yet). Thanks.
    Edited by: Sengin on Sep 21, 2009 8:44 PM
    Edited by: Sengin on Sep 21, 2009 8:46 PM

  • InsufficientBufferRule reporting bogus buffer lengths with live dynamic MBR streams

    Can someone tell me why InsufficientBufferRule.as uses the "rtmpMetrics.netStream.bufferLength" as opposed to "rtmpMetrics.netStream.info.videoBufferLength"?
    The reason I ask is because the "rtmpMetrics.netStream.bufferLength" returns 10 times(can grow to even more during transitions in quick succesion) what the actuall buffer length is when it switchs to a differnt stream. It will then continually drop until it starts returning the real buffer length(with my current bitrate(100, 300, 500) and bufferTime(10 seconds) setup, its takes about 20 seconds to get back to real buffer length). Durring this time the player is vulnerable to a buffer empty event because of the extremly high(and obviously wrong) buffer length being returned by "rtmpMetrics.netStream.bufferLength". Because of the incorrect buffer length being returned, the "if (_panic || (rtmpMetrics.netStream.bufferLength < minBufferLength && rtmpMetrics.netStream.bufferLength > rtmpMetrics.netStream.bufferTime))" statement never fires and hence the buffer drains completely without any warning.
    I hate the stuttering buffer empty, buffer full, buffer empty, buffer full... crap that happens when this occurs so I've been debugging(more like hacking:)) this issue for quite some time. I tried many different things to try and avoid the buffering empty state. Most of my hacks have been done in the NetStreamSwitchManager file and I have had some limited success in avoiding the buffer empty state but ultimatly it would shows it ugly head no matter what I did.
    Last night I found the "rtmpMetrics.netStream.info.videoBufferLength" property and noticed it returns the correct buffer length all the time even during a transition. So I changed "if (_panic || (rtmpMetrics.netStream.bufferLength < minBufferLength && rtmpMetrics.netStream.bufferLength > rtmpMetrics.netStream.bufferTime))" to "if (_panic || (rtmpMetrics.netStream.info.videoBufferLength < minBufferLength && rtmpMetrics.netStream.bufferLength > rtmpMetrics.netStream.bufferTime))" and tada!!!! It works like a dream. No matter what I do with my Netlimiter program(simulates bad connections), short of going below the 100kbs setting, the player never reaches the buffer empty state. Yaaaayyyyyyyyy:). I was even able to remove some of my hacks and still get good results. I plan on setting up a totaly new and clean enviroment and try this without any of my previous hacks and see how it works. In the meantime I was hoping someone could enlighten me as to why bufferLength is being used as opposed to videoBufferLength.
    I included some browser logs that show what I am describing below. Any insight into this would be greatly appreciated.
    100kbs to 300kbs
    [LOG] time 10:44:15.967 :: org.osmf.net.rtmpstreaming::InsufficientBufferRule : bufferLength reporting Buffer of 10.102
    [LOG] time 10:44:15.969 :: org.osmf.net.rtmpstreaming::InsufficientBufferRule : videoBufferLength reporting Buffer of 10.1
    [LOG] time 10:44:16.517 :: org.osmf.net.rtmpstreaming::InsufficientBufferRule : bufferLength reporting Buffer of 9.901
    [LOG] time 10:44:16.519 :: org.osmf.net.rtmpstreaming::InsufficientBufferRule : videoBufferLength reporting Buffer of 9.9
    [LOG] time 10:44:17.49 :: org.osmf.net.rtmpstreaming::InsufficientBandwidthRule : -------Average bandwidth of 68955.72916666667
    [LOG] time 10:44:17.50 :: org.osmf.net.rtmpstreaming::InsufficientBufferRule : bufferLength reporting Buffer of 9.981
    [LOG] time 10:44:17.57 :: org.osmf.net.rtmpstreaming::InsufficientBufferRule : videoBufferLength reporting Buffer of 9.95
    [LOG] time 10:44:17.549 :: org.osmf.net.rtmpstreaming::SufficientBandwidthRule : Move up since avg dropped FPS 0 < 2 and bufferLength > 10
    [LOG] time 10:44:17.551 :: org.osmf.net.rtmpstreaming::SufficientBandwidthRule : getNewIndex() - about to return: 2, detail=null
    [LOG] time 10:44:17.554 :: org.osmf.net.rtmpstreaming::InsufficientBandwidthRule : -------Average bandwidth of 68955.72916666667
    [LOG] time 10:44:17.557 :: org.osmf.net.rtmpstreaming::InsufficientBufferRule : bufferLength reporting Buffer of 10.085
    [LOG] time 10:44:17.560 :: org.osmf.net.rtmpstreaming::InsufficientBufferRule : videoBufferLength reporting Buffer of 10.05
    [LOG] time 10:44:17.564 :: org.osmf.net::NetStreamSwitchManager : 10:44:17 GMT-0400>>> NetStreamSwitchManager.----------0
    [LOG] time 10:44:17.567 :: org.osmf.net::NetStreamSwitchManager : 10:44:17 GMT-0400>>> NetStreamSwitchManager.checkRules() - Calling for switch to 1 at 300 kbps
    [LOG] time 10:44:17.570 :: org.osmf.net::NetStreamSwitchManager : 10:44:17 GMT-0400>>> NetStreamSwitchManager.executeSwitch() - Switching to index 1 at 300 kbps
    [LOG] time 10:44:18.165 :: org.osmf.net::NetStreamMetricsBase : onNetStatus() - event.info.code=NetStream.Play.Transition
    [LOG] time 10:44:18.167 :: org.osmf.net::NetStreamSwitchManager : 10:44:18 GMT-0400>>> NetStreamSwitchManager.onNetStatus() - event.info.code=NetStream.Play.Transition
    [LOG] time 10:44:18.599 :: org.osmf.net.rtmpstreaming::SufficientBandwidthRule : Move up since avg dropped FPS 0 < 2 and bufferLength > 10
    [LOG] time 10:44:18.603 :: org.osmf.net.rtmpstreaming::SufficientBandwidthRule : getNewIndex() - about to return: 2, detail=null
    [LOG] time 10:44:18.607 :: org.osmf.net.rtmpstreaming::InsufficientBandwidthRule : -------Average bandwidth of 68955.72916666667
    [LOG] time 10:44:18.610 :: org.osmf.net.rtmpstreaming::InsufficientBufferRule : bufferLength reporting Buffer of 27.508
    [LOG] time 10:44:18.612 :: org.osmf.net.rtmpstreaming::InsufficientBufferRule : videoBufferLength reporting Buffer of 10.1
    [LOG] time 10:44:19.99 :: org.osmf.net.rtmpstreaming::SufficientBandwidthRule : Move up since avg dropped FPS 0 < 2 and bufferLength > 10
    [LOG] time 10:44:19.101 :: org.osmf.net.rtmpstreaming::SufficientBandwidthRule : getNewIndex() - about to return: 2, detail=null
    [LOG] time 10:44:19.105 :: org.osmf.net.rtmpstreaming::InsufficientBandwidthRule : -------Average bandwidth of 68955.72916666667
    [LOG] time 10:44:19.108 :: org.osmf.net.rtmpstreaming::InsufficientBufferRule : bufferLength reporting Buffer of 27.008
    [LOG] time 10:44:19.110 :: org.osmf.net.rtmpstreaming::InsufficientBufferRule : videoBufferLength reporting Buffer of 10
    300kbs to 500kbs
    [LOG] time 10:44:47.472 :: org.osmf.net.rtmpstreaming::InsufficientBufferRule : bufferLength reporting Buffer of 10.035
    [LOG] time 10:44:47.480 :: org.osmf.net.rtmpstreaming::InsufficientBufferRule : videoBufferLength reporting Buffer of 10
    [LOG] time 10:44:47.966 :: org.osmf.net.rtmpstreaming::SufficientBandwidthRule : Move up since avg dropped FPS 0 < 2 and bufferLength > 10
    [LOG] time 10:44:47.968 :: org.osmf.net.rtmpstreaming::SufficientBandwidthRule : getNewIndex() - about to return: 2, detail=null
    [LOG] time 10:44:47.970 :: org.osmf.net.rtmpstreaming::InsufficientBandwidthRule : -------Average bandwidth of 31764.322916666668
    [LOG] time 10:44:47.972 :: org.osmf.net.rtmpstreaming::InsufficientBufferRule : bufferLength reporting Buffer of 10.135
    [LOG] time 10:44:47.976 :: org.osmf.net.rtmpstreaming::InsufficientBufferRule : videoBufferLength reporting Buffer of 10.1
    [LOG] time 10:44:47.981 :: org.osmf.net::NetStreamSwitchManager : 10:44:47 GMT-0400>>> NetStreamSwitchManager.----------1
    [LOG] time 10:44:47.986 :: org.osmf.net::NetStreamSwitchManager : 10:44:47 GMT-0400>>> NetStreamSwitchManager.checkRules() - Calling for switch to 2 at 500 kbps
    [LOG] time 10:44:47.989 :: org.osmf.net::NetStreamSwitchManager : 10:44:47 GMT-0400>>> NetStreamSwitchManager.executeSwitch() - Switching to index 2 at 500 kbps
    [LOG] time 10:44:48.308 :: org.osmf.net::NetStreamMetricsBase : onNetStatus() - event.info.code=NetStream.Play.Transition
    [LOG] time 10:44:48.309 :: org.osmf.net::NetStreamSwitchManager : 10:44:48 GMT-0400>>> NetStreamSwitchManager.onNetStatus() - event.info.code=NetStream.Play.Transition
    [LOG] time 10:44:48.465 :: org.osmf.net.rtmpstreaming::InsufficientBandwidthRule : -------Average bandwidth of 23247.514204545456
    [LOG] time 10:44:48.467 :: org.osmf.net.rtmpstreaming::InsufficientBufferRule : bufferLength reporting Buffer of 40
    [LOG] time 10:44:48.469 :: org.osmf.net.rtmpstreaming::InsufficientBufferRule : videoBufferLength reporting Buffer of 10
    [LOG] time 10:44:48.966 :: org.osmf.net.rtmpstreaming::InsufficientBandwidthRule : -------Average bandwidth of 17793.34677419355
    [LOG] time 10:44:48.967 :: org.osmf.net.rtmpstreaming::InsufficientBufferRule : bufferLength reporting Buffer of 39.5
    [LOG] time 10:44:48.970 :: org.osmf.net.rtmpstreaming::InsufficientBufferRule : videoBufferLength reporting Buffer of 9.9
    Thanks,
    Wayne
    P.S.    While wrighting this I realized I need to replace the second part of that if statement to the videoBufferLength as well, so I will do that and make sure it still works. If I don't reply to this you can assume that it works as well.

    Wow I'm starting to get a little confused here. I need to mention that in my first post I said that I changed/used 
    "if (_panic || (rtmpMetrics.netStream.bufferLength < minBufferLength && rtmpMetrics.netStream.bufferLength > rtmpMetrics.netStream.bufferTime))".
    That was not the truth, I had actually shortened that statement in one of my earlier hack attempts, not really giving it to much thought at the time. The statement that I ended up changing/using was more like
    "if (_panic || rtmpMetrics.netStream.bufferLength < minBufferLength)" changed to "if (_panic || rtmpMetrics.netStream.info.videoBufferLength < minBufferLength)".
    So now that I go back and try using the original code which I had commented out earlier I realize there is somthing very wrong here, I think:) The second part of the statement
    "if (_panic || (rtmpMetrics.netStream.bufferLength < minBufferLength && rtmpMetrics.netStream.bufferLength > rtmpMetrics.netStream.bufferTime))"
    is checking if the buffer length is greater than the buffer time, but the first part is checking if the buffer length is less than min buffer length. How would that ever be possible?
    bufferTime = 10
    minBufferLength = 9
    if the bufferLength(no matter which one you use) is less than minBufferLength(9) how is ever going to be greater than bufferTime(10)?
    fyi:
    if  I change the statement
    "if (_panic || (rtmpMetrics.netStream.bufferLength < minBufferLength && rtmpMetrics.netStream.bufferLength > rtmpMetrics.netStream.bufferTime))"
    to
    "if (_panic || (rtmpMetrics.netStream.info.videoBufferLength < minBufferLength && rtmpMetrics.netStream.info.videoBufferLength < rtmpMetrics.netStream.bufferTime))"
    it works like a dream again.
    Thanks again,
    Wayne
    P.S.   I noticed that there are other places such as SufficientBandwidthRule.as that are referencing rtmpMetrics.netStream.bufferLength. I plan on going through the code and changing these and see how it works. I'm starting to wonder what else could be written like this or am I crazy? 

  • Buffer Management and Threads

    Hi,
    I'm trying to program an audio editor for wav files. At the moment I am struggling to handle playing the large files. I want to implement some sort of buffer management, possibly LRU.
    As one buffer is playing, I need another buffer to read in the next block of the sound file and get ready to play it. I then need the blocks to play seamlessly I.e. no gap in sound output when the SourceDataLine is changing from one buffer to another.
    Eventually I need a set number of fixed size buffers to play without the user being able to hear the transitions.
    Does anybody have any ideas about where to start?
    Any help would be greatly appreciated, I'm really stuck!
    Jimbo

    I don't mean I'm experiencing any gaps in playback, i mean I need to code a system that manages a certain number of buffers, and manages to play transitions between buffers seamlessy - i.e. without noticing.
    The following is my code for the Thread that writes the data to the SourceDataLine.
    class PlayThread extends Thread {
            int bufLen = frameSize*bufferFrames/2;
            byte[] aBuffer = new byte[bufLen];
            public void run() {
                int counter;
                playButton.setEnabled(false);
                try {
                    sDL.open(format);
                    sDL.start();
                    while((counter = theStream.read(
                            aBuffer,0,aBuffer.length)) != -1 && currentlyPlaying == false){
                        if(counter > 0){
                             CurrentTime = currentFrame / frameRate;
                             System.out.println("Timer : "+currentTime+" "+counter+" Bytes");
                            sDL.write(aBuffer, 0, counter);
                            currentFrame = currentFrame + framesReadSoFar;
                    sDL.drain();
                    sDL.close();
                    playButton.setEnabled(true);
                } catch (Exception e) {
                    System.out.println(e);
        }

  • RTP jitter buffer growing too large?

    Hi all I am experiencing a rather annoying problem when receiving RTP audio data and rendering it: It takes some time for the player to get created and realized, in the mean time RTP packets continued to arrive, causing them to be buffered. It appeared that the buffer grew until data is drained from it (by the player), so the longer it took the player to get created and realized the larger the buffer became, causing a massive delay which is annoying when a conversation is being carried out. I did set the buffer length (via the RTPManager's BufferControl) to 200ms but this does not seem to make any difference. I don't have direct proof that this is what actually happened under the hood but all evidence seemed to point to this unchecked growth of the jitter buffer. The faster the computer, the faster the player get realized and the smaller the delay.
    Does anyone else experience this phenomenon? Is there a fix?

    I don't know if your diagnosis is correct, for shure I have a lot of jitter between two PC using the same java app and playing a RTP broadcast audio.
    But I could not relate it with the speed of the computer, sometimes A plays before B, sometimes after. Problably it is the time to create objects that varies.
    Still looking for a solution....

  • How to empty Serial port buffer ???

    Hi!
    I am having problems with serial port. I want to clear i
    serial ports buffer, but i dont know how to do this. I am receiving NMEA data through that port and every now and then i need to clear it because there are too much data and i dont need them all. Could someone please help me?

    Hi,
    Take a look at this link.
    http://www.sc-systems.com/JavaDoc/Serialio.SerOutputStream.html
    flush
    public void flush() throws IOException
    Causes any buffered data on the output stream to be written. Note: when using txDrain be advised that some OS's (like WinNT) do not provide a timeout on the OS level drain/flush call. In this case if handshake (flow control) is disabled from the far end your txDrain call will block until drain can complete. (i.e. until the handshake state changes). Because of this the default mechanism for flush is to watch the txBuffer. This will allow you to abort a stalled OutputStream since your code will not be locked up at the native level.
    Throws: IOException
    if an error occurs. Overrides:
    flush in class OutputStream
    However the above function and the class defining this is not provided by SUN.
    I hope this helped.
    Roopasri Vittal
    Developer Technical Support
    Sun Microsystems
    http://sun.com/developers/support

  • Recording fails when reading from a buffer

    Hello together,
    I'm new to the java sound api so I decided to get some example code working that I found on the internet. But I Fail.
    Here's the code snippet that does the recording and runs in a thread:
    ByteArrayOutputStream byteOutStream = new ByteArrayOutputStream();
    DataLine.Info info = new DataLine.Info(TargetDataLine.class, m_format);  // m_format is initialised somewhere in the c'tor
    TargetDataLine inputLine = (TargetDataLine)AudioSystem.getLine(info);
    inputLine.open();
    inputLine.start();
    AudioInputStream inStream = new AudioInputStream(inputLine);
    int iCount = 0;
    byte[] buffer = new byte[1024];
    while(m_bRecording && ((iCount = inStream.read(buffer)) != -1))
    {   // m_bRecording will be set false when invoking stop() method
         if(!m_bPause)
             byteOutStream.write(buffer, 0, iCount);
    inStream.close();
    byteOutStream.flush();
    byteOutStream.close();
    byte[] inBuffer = byteOutStream.toByteArray();
    AudioInputStream inRecorded = new AudioInputStream(new ByteArrayInputStream(inBuffer),
                                            m_format,
                                            inBuffer.length / m_format.getFrameSize());
    Clip clip = (Clip)AudioSystem.getLine(info);
    clip.open(inRecorded);I've read the documentations about the classes and their methods so everything seems to make sense about this approach. But when I invoke clip.start() then all I get to hear is only a second or less of the sound I recorded. I found a link (http://www.jsresources.org/faq_audio.html#recordings_cutoff) that may (I'm not sure) be the solution I am looking for. But I still don't know how to apply this suggestion on my example code. Maybe you can help.
    By the way: I've already tried the examples from www.jsresources.org and they work fine. But now I find it important to have my recorded data in a byte array so I will be able to apply effects and play around with the data and see what happens.
    I am looking forward to reading your answers. Tanks!
    Edited by: schmetterfly on Dec 22, 2009 10:22 AM

    captfoss wrote:First, there's absolutely no need for "inStream" because you can read directly from inputLine...so get rid of inStream.You're totally right about this so I got rid of the inStream.
    captfoss wrote:Second, redo the loop so it doesn't exit until you run out of data on the line...rather than when the boolean changes. Close the line in response to the boolean changing (don't flush it or anything, just close it) and continue to read until you get a -1 from reading from it...My code looks like this now.
       inputLine.open();
                inputLine.start();
                byte[] buffer = new byte[1024];
                int iCount = 0;
                do
                    iCount = inputLine.read(buffer, 0, buffer.length);
                    if(!m_bPause)
                        byteOutStream.write(buffer, 0, iCount);
                    if(!m_bRecording && inputLine.isActive())
                        inputLine.stop();
                        //inputLine.drain();
                }while(iCount > 0);
                inputLine.close();It is important to stop() the line, then go on reading until there is no more data to read and then close() the line. It is neccesary to just stop() the line first because it muste be open for reading. So I close() the line when all the job is done.
    I added inputLine.isActive() as an additional condition for the line to stop so it will not be stopped several times although nothing bad happens when closing the line several times.
    After stepping into the if-block the loop continues few more times. When looping for the next to last time iCount has a value smaller than 1024. I suppose this way I can see that the line in fact does run out of data. When looping the last time iCount equals 0 and the loop is left.
    Everything looks just fine but it still doesn't work properly.
    Im starting to wonder if there's something wrong with the version of my JRE installed or the OS or the input device... Is there a way to figure that out?

  • Toast--Buffer under run protection--does it work?

    Lately I have been having trouble with the "device has drained its buffer without under run protection" error. I usually can deal with it with several things I try, but for the last couple of projects I can burn only one or two disks before I start getting this problem. Then I can't burn until I let the computer rest overnight, no matter what I try.
    I have heard that Toast has a buffer under run protection option. Does it work? If it does, I'll down load it.

    Hi R
    Even Toast™ are dependant on the free space on internal hard disk. Even more so
    if You use it for capturing material from DVD discs - then to add to the strain
    say that it should be changed to fit a new DVD.
    Say from a DL-disc to a SL-dito.
    Don't be amazed if the need exceeds a 60Gb need.
    Yours Bengt W

  • IDVD6 Buffer under-run through View Image

    Higtherto a fair run with iDVD6 but suddenly, no matter what I've tried, when I eventually have run through the creation in iDVD then saved to Image View the complete disc build carries right through to the end then closes with the box message tellingme it has failed through buffer under-run. A waste of approximately 11 hours.
    I'm employing OSX.3.9 for the job with my undermentioned spec. The film is a holiiday one of 58 mins 30 secs, and I'm working in PAL with a Pioneer 109 and -R disc.
    Maybe I should know what is buffer under-run and maybe it's something I'm doing along the line but I haven't a clue.....
    Help required here, people - with thanks.

    Apologies - read it as 'when burning from' and confirm that I get as far as having already saved as Disk Image.
    I've a number of times gone over the lengthy process of saving from FCP through FCP Movie then iDVD to Disk Image followed by spasmodic print results to disks during this present difficulty. Last night I had one result from Toast 6 and another result from Disk Utility followed by a string of complete failures in the way I have already reported - that fatal "The drive drained its buffer without underrun protection."
    I've used Disk Warrior's Optimiser to optimise both my HDs which showed a noticeable difference to the storage graphs. Turned the computer off and on again. Resaved the film in the way described. Gone through the process with Toast and Disk Utillity, and produced one good disk from each. All followiing attempts have ended in failures as described and those attempts have included switching off and on again, not just restarting. My startup disk has 42gb free space and the storage disk containing the edited material has 47gb free space.
    So yes - the problem shows from the Disk Image starting point. When I got a result from Toast 6 followed by another one from Disk Utility I thought I'd cracked it. Maybe there's a clue in noting that the failures occurred again after once more using Disk Utility.
    Thanks again for your interest.

Maybe you are looking for

  • How do i change the phone number associated with my apple ID?

    how do i change the phone number associated with my apple id and attach it to my ipad?

  • Fed Up with BT's Complaint Department

    At the end of augest i split from my ex-wife and as the broadband was in my name she had to take out a new contract for the bt infinty, i was told at the time that i would not have to pay the £30 cancelation fee by the advisor "as its not really a ca

  • Force new window to open in new tab

    Now my safari open pages from the original pages to the new pages, I tried to set Safari to open pages in new tabs. I tried Safari ▹ Preferences ▹ Tabs ▹ Open pages in tabs instead of windows: Automatically or Never or Always, but it still opened the

  • Iphone 5 pila

    Tengo una duda es que ultimamente he notado q la pila del iphone se termina muy rapido aun sin utilizarlo, lo deje bloqueado y no lo utilize en 7 horas (la pila estaba al 100%) y cuando lo desbloequie, sorpresa la pila estaba en 52% alguien me podria

  • Reading SNMP OID for used storage on px12-400r

    Hi, does anyone know how get the correct value for used disk space via snmp on the px12-400r nas? All capacity is configured as one big cifs share. I want to monitor the usage of space with snmp. If I do a snmpwalk (v3) I can pinout the filesystem /m