Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
55
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
55
CC-HDe Encoder Plus DoStudio Authoring Deliver Pristine Picture Quality, Professional BD Features
Alexandria, VA and Newport Beach, CA (PRWEB) December 15, 2009 — NetBlender and CINEMA CRAFT USA announced today the immediate availability of a new high-end Blu-ray solution that combines the award-winning CC-HDe Encoder with NetBlender’s proven, professional DoStudio Authoring system. The new solution, called CC-HDe/a, satisfies the high-end Compression and Authoring (C&A) market’s need for pristine, highly-configurable Blu-ray compression and full spec, cost-effective and user-friendly Blu-ray authoring. CC-HDe/a is available exclusively through CINEMA CRAFT USA.
“A comparable solution from other vendors would have cost more than $100,000 in license fees, required weeks in dedicated authoring training and would have meant lengthy production cycles. The CC-HDe/a solution from CINEMA CRAFT USA saves me more than 50% in upfront cost, delivers the fastest and most importantly, the highest quality AVC encoding for Blu-ray. And now, combined with the professional authoring features and ease-of-use DoStudio, this bundle really delivers the end-to-end package,” said Tony Laughton, CEO, PROMO SCAPE-Melbourne, Australia.
“This customer-driven solution changes the economics of Blu-ray, and not a moment too soon. Unlike DVD, Blu-ray faces several home video competitors. If Blu-ray is to take its rightful place as the dominant home entertainment format, Blu-ray disc prices have to come down. The only way that will happen is if content creators and the post-production community that serves them have access to cost-effective solutions that reduce production cost and time, and most importantly without compromising high quality. That’s what CC-HDe/a is all about,” said, Ray Wallick, President, CINEMA CRAFT USA.
“Our partnership with CINEMA CRAFT represents the next step in NetBlender’s mission to cut the drama out of Blu-ray production. Since the launch of DoStudio Authoring in 2008, it has been used to author hundreds of mass-replicated titles worldwide, increasing the supply of BDs and bringing their shelf-price closer to DVD. With DoStudio Workflow Suite, announced at NAB 2009, we eliminated the Blu-ray-compliant encoding bottleneck for the independent post production and corporate markets. This partnership with CINEMA CRAFT offers high-end and mid-level C&A facilities a “right-priced,” fast and easy-to-use Blu-ray solution,” said John Harrington, CEO of NetBlender.
About CINEMA CRAFT USA For over 10 years CINEMA CRAFT has developed innovative high-end software toolsets for DVD and Blu-ray studio professionals who demand pristine picture quality. CINEMA CRAFT Software and Turnkey Systems include solutions for Film Restoration with–Reneat; Standard-Definition MPEG-2 Encoding with–CCE-SP2, CC Xtream, and CCE-MP); and High-Definition AVC/H. 264 Encoding with–CC-HDe. A vast majority of the Hollywood “A list” DVD and Blu-ray Titles have been encoded using CINEMA CRAFT. For more information, please visit: www.cinemacraftusa.com
About NetBlender NetBlender was founded in 2005 by a team of veteran interactive media producers. The company designs and develops practical and professional Blu-ray technology solutions for the global BD production community. NetBlender’s Blu-ray solutions include DoStudio BD Authoring Edition (DSA), a complete Blu-ray authoring tool designed for DVD authors moving to Blu-ray Disc, DoStudio BD Workflow Edition (DSW) which integrates with DSA Blu-ray encoding, subtitling, playback, burning and formatting, and BD Touch, an acclaimed solution that lets end-users interact with BD content through their iPhone and iPod Touch. For more information, please visit: www.netblender.com
###
Source : PRWeb
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
55
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
55
Simplicity Comes to Blu-ray Audio Disc Navigation with “Pure Audio” Standard from msm-studios
Posted December 18th, 2009 by Brandon DuHamel on Blu-ray Definition.com
With Blu-ray Disc adoption now making up a total of 15% of the packaged media home video market according to the latest numbers from Home Media Research and the strong showing for Blu-ray player sales, with the latest NPD numbers showing sales for players up 53% this holiday season, all evidence points to Blu-ray being very much here to say and finally establishing itself as a formidable next-generation format.
Ask the average person what the advantage of Blu-ray is over DVD and they will most likely tell you about its high definition picture quality, but Blu-ray also holds another advantage — high-resolution audio. For audiophiles seeking the Holy Grail of aural bliss, the advanced fidelity that Blu-ray offers with its expanded storage capacity and bandwidth may be a dream come true. Finally, there is a format capable of high-resolution (up to 192kHz/24-bit in 2.0 and 7.1 in comparison to CD’s 44.1kHz/16-bit in 2.0 only) audio reproduction that can and has penetrated the market beyond a mere niche.
Previous efforts to market a high-res format to replace the compact disc have only ended in disappointment for most audiophiles. Super Audio CD (SACD or SA-CD), has only managed to eek out a small market for itself in the classical and jazz arenas, and the format that was meant to ride the coattails of DVD, DVD-Audio, or DVD-A, is pretty much non-existent outside of the very rare pop-rock title.
The two formats battled it out a few years back to be the successor to the Compact Disc, but it was like watching two pieces of lint battle over a portion of a pinhead. Neither format ever caught on with the masses and it is debatable whether that had more to do with the format war or people wanting downloads over another optical format.
Perhaps Blu-ray Audio releases have a better chance of succeeding since there is no format war, especially since HD DVD has been long dead now, and the format has been steadily penetrating the market at a pace that has matched or exceeded DVD at the same point in its lifespan, with over 12 million players in U.S. homes to date. But actual audio-only releases have been slow to come to market. Outside of an Internet-only release from Nine Inch Nails, Ghosts Vol. I – IV, a few releases from classical label Surround Records, the BD + SACD combo releases from Norwegian label 2L, and two of the major audio-only releases to hit the format, Neil Young’s sprawling Archive’s Vol. 1 and Tom Petty’s Live Anthology — a Best Buy Exclusive, there hasn’t been much activity in this area for Blu-ray.
Another problem with Blu-ray Audio Discs has been the complicated manner in which users must navigate the discs to access the different audio programs, as anyone who has used the Neil Young set can attest to. They are lacking the same “insert and play” ease of use that the CD has had since its launch and that even SACDs have — until now, that is.
German audio production facility msm-studios in conjunction with Norwegian classical label 2L has created what they have named the “Pure Audio” standard. As Stefan Bock, Managing Director of msm-studios, describes it:
“We have agreed on a feature set that distinguishes “Pure Audio” Blu-rays. The most important part of the concept is to navigate the discs without a screen (i.e. numeric track access, selection of the audio stream etc.) as well as to provide the customers playback information if the screen is left on.”
Stefan Bock was kind enough to take a little time to talk with Blu-rayDefinition about msm-studios’ Pure Audio standard. What follows is that interview:
Blu-rayDefinition: Is the “Pure Audio” format specifically created in BD-Java?
Stefan Bock: Yes, most of the features are only available if Java code is involved (i.e. color buttons to select the audio stream, etc.)
BD: How active does msm-studios plan to be in the authoring process to ensure the propagation of the “Pure Audio” specification on Blu-ray Audio releases?
SB: Until now, all activities regarding “Pure Audio” have been driven by 2L and us.
We have developed a feature set that 2L and msm-studios regarded as very important for a new audio media. We all have payed our dues with DVD-Audio and SA-CD, so we were quite aware of all the draw-backs in these standards. We both had agreed on a functionality that combines the best of both worlds. Although we had to develop all this by ourselves without any support of the BDA , we were quite happy to see some hardware manufacturers supporting us. Now as we have set a kind of standard, we are very happy to see other companies follow our ideas. We are heavily concerned that releases are according to our spec and we have made a proposal to the AES (Audio Engineering Society) to define “pure audio”. This will hopefully be an AES standard in May 2010.
BD: Does it require licensing from msm, or is it an open platform that anyone who wants to release an audio-only Blu-ray disc can use?
SB: As we have spent a lot of money into the project, we’ll have to find a way to recoup.We own a patent for switching between audio streams by using the color buttons (witch is essential for screenless navigation), but we don’t follow a license model based on this. We would like to have as many people making use of the concept. That was the reason to make the AES proposal that defines the essentials of a Pure Audio Blu-ray.
Today’s business model is based on our services. As most of the audio studios are not involved in Java programming at all, the biggest problem for them seems to be in the authoring itself. This is where we can help.
I know exactly how much effort we had to spend to make it work – I doubt whether it is worth to re-invent the wheel.
Of course, in the long run, it is not realistic to create all Pure Audio discs in the world. Actually, we are working on a web-based authoring solution so people can log in online to a server and will get an “Authoring assistant” that will automatically create the menus and a disc image that can be downloaded and burnt for reference. I’m sure that there are lot of people interested in this service as they don’t have to deal with Java code at all. Our aim is to make it simple and affordable. It’s easier to handle as supplying studios a piece of Java code or a piece of software. On the long run [sic], there might be a demand for an authoring solution, but this will be a long way to go.
BD: Are onscreen menus required at all, or can a disc be authored without any video content?
SB: Technically, we don’t need menus. But we strongly recommend to make use of them as I would expect end users to feel that the disc is broken if nothing appears on the screen. This is one of the reasons we are working on the web-tool. People will have an easy way to create menus on a template base.
BD: So, in your opinion, does this open the door for the mythical, “Profile 3.0″ audio-only Blu-ray players to come to market? Is that something that you would like to see take off in the future?
SB: here’s no need for “Profile 3.0″ players and there won’t be any on the market.
—–
Currently there are three labels using the Pure Audio format on Blu-ray: 2L, Naxos, and the German label Stockfish. Stefan Bock has said there is another Norwegian label set to begin using the Pure Audio format on Blu-ray Audio Disc releases, but there is nothing officially announced yet.
We’d like to thank Stefan Bock for taking the time to speak with us. We’d also like to take the time to thank everyone at msm-studios as well as Morten Lindberg at 2L for his assistance.
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
55
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
55
An interesting post from High-Def Digest today…. Apparently a new Hollywood Blu Ray release wasn’t authored correct. Oops! Just goes to show that you should hire a company who know what their doing with BD authoring.
Q: I recently purchased the ‘Starship Troopers’ Blu-ray disc. When I brought it home, I discovered that when I placed it in my Blu-ray player (Sony BDP-350), it would only load as far as the loading screen. The “Loading” bar plays, followed by nothing but a black screen. I left it on for ten minutes and nothing happened. I upgraded my firmware to no effect before finally assuming the disc was in some way defective. I exchanged it for another copy, only to discover the same issue when I got home. When I took the second disc back, the store tested it on their own Blu-ray player - also a BDP-350 - and the same disc that gave me trouble played perfectly! As a result, they wouldn’t give me another replacement disc. I don’t entirely blame them, but now I’m stuck with a disc that I really want but can’t seem to play. What could possibly be wrong?
A: It turns out that the ‘Starship Troopers’ Blu-ray has an authoring glitch. When inserted into a BD-Live capable Blu-ray player, the disc attempts to confirm the player’s BD-Live status, regardless of whether you plan to use the BD-Live features or not. What this means is that your player must have internal memory installed for BD-Live, or the disc won’t play.
The Sony BDP-S350 doesn’t come with any internal memory out-of-the-box. You must install that yourself via a USB stick. (Some brands may take an SD card instead.) 1 GB should do. Once you do that, ‘Starship Troopers’ will play.
Fortunately, this should be an inexpensive fix. However, I agree that this is a tremendous nuisance. Frankly, it astounds me that major hardware manufacturers like Sony (Panasonic, Samsung, and other brands have also had the same problem) would ever build BD-Live Blu-ray players that don’t have the required memory built-in. 1 GB of memory certainly wouldn’t have added much to their manufacturing costs. Thankfully, this seems to be less of a problem in current models, but was very much an issue at the time yours was released.
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
55
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
55
PacificDisc announced today that the fees being collected from Blu-ray publishers for AACS Title Keys, per-disc royalty fees and AACS processing costs would be reduced by approx. 60%. The AACS Licensing Agency (AACS LA) released a new fee structure in their long-awaited “final” agreement which makes entry into this exciting market more cost-effective. In fact, the cost for 2,500 retail-ready Blu-ray discs has now dropped to $6325 + a Content Providers License of $500/annum.
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
55
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
55
PacificDisc Announces Lower Blu-ray Replication Pricing
Posted May 20, 2009 02:26 PM by Juan Calonge
Replication company PacificDisc has increased its Blu-ray capabilities by bringing the mastering in-house and announcing aggressive new pricing. According to Bob Novelli, VP of Marketing, “this makes entry into the BD space much more affordable for the independent producer, which is our target market.”
As a reference, current pricing for an order of 5,000 bulk BD25 discs would be $9,350, including replication, AACS and mastering (but excluding shipping and taxes). That is to say, overall unit price would be $1.87 per disc.
As is always the case in replication, the per-disc cost varies depending on order size. A larger order of 10,000 units would cost $16,600 ($1.66 per disc), whereas a small order of 1,000 units would run a bill of $3,580 ($3.58 per disc), again including mastering, AACS and replication.
These prices are noticeably better than those that were applied in the recent past. For example, the pricing for replicating 5,000 bulk BD25s (not counting AACS and mastering) has decreased from $3.15 per disc in August 2007 to $1.47 per disc now, or a drop of over 50 percent.
AACS fees have also dropped by around 20 percent (from $1,585 + $0.05/disc to $1,300 + $0.04/disc). However, they continue to be steep for smaller runs. For example, an independent producer ordering 5,000 discs must pay $1,500 in AACS fees alone - in other words, compulsory AACS costs him 30 cents per disc.
PacificDisc agrees that AACS fees, while insignificant for major studios, remain a huge obstacle for the smaller agents and put off many a potential producer wishing to take the plunge. This issue has been repeatedly raised in industry fairs by independent replication houses and producers, who demand a tiered license pricing scheme.
Most of PacificDisc’s recent BD projects have come from smaller independent producers, or corporate clients. These include: product demos, yoga and meditation videos, an HD eye candy series (fireplace video, aquariums, etc.) and some indie films. “We’ve not broken into the mass-market titles outside a handful of PBS stuff,” said a PacificDisc representative, “as this is not our niche.”
The typical BD orders the company receives range from 1,000 to 10,000 discs, though they have also had some orders for as many as 100,000 units.
As regards disc size, the vast majority of orders are for BD25s. PacificDisc doesn’t do BD50 in-house, and contracts out those few dual-layer jobs instead.
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
55
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
55
At PacificDisc, we are always looking for new customers, as we are confident that we’ll impress them so much, they’ll keep coming back with project after project. Over the years we’ve handed out hundreds of iPods, offered countless discounts and are always looking for better “carrots” to entice new customers.
This summer’s promo is different for us, as we’ve looked long and hard at our competition and come up with offerings that not only beat out their pricing, but does so without compromise. We’ll simply giving our customers a break on price, without cutting corners, or dragging out production times. Many of our competitors offer entry-level pricing, but to get the good stuff, you have to pay extra. PacificDisc has always prided itself on producing best quality product available on the market today. This promo is the best of both worlds. Best discs money can buy, for less!
Checkout our prices on the site and feel free to comment here.
Thanks
Morris Anderson
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
55
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
55
We just received an email from our partner Carbonfund.org, where they have announced some major contributions to carbon offsetting projects. While we can only claim a small fraction of these pounds - every little bit helps and donating $0.01/disc on your next CD or DVD replication run will help with their efforts.
______________________________________________________________
Dear Supporter,
We announced today that we have reached a milestone thanks to your support! Carbonfund.org is now offsetting over 4 billion pounds of CO2 emissions. Please read about this exciting news, and more, in this edition.
|
Carbonfund.org Offsetting Over 4 Billion Pounds of CO2
|
|
 We’re very pleased to announce that through your support, we’re now offsetting over 4 billion pounds of carbon dioxide emissions. That’s equivalent to the carbon dioxide emissions of over 205 million gallons of gas consumed or the electricity use of 240,000 homes for a year. We reached this important milestone through individual support (we’re now over 400,000 supporters strong) and new partnerships. Fighting global warming is a large challenge, and we’re continuing to build our support through holiday giving and donations. [More] |
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
55
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
55
Another way PacificDisc helps the Independent Producer
We have added a dozen new DVD titles for sale on the FulfillDisc website this month. These are titles that PacificDisc had replicated and then setup for online sales for the clients. By having the fulfillment warehouse next door to the replication plant, we can save the customer on shipping costs and immediately open an eStore for business as soon as the discs roll off the production line.
A one-stop-shop indeed
Many replicators offer fulfillment services, but they normally want huge volume commitments upfront and probably won’t talk to someone who is “unsure how many copies they will sell to start with”. Let’s face it, how many among us know if our latest special-interest doc, or instructional video is going to sell like a Hollywood blockbuster straight out of the gate? And while other companies look to fulfillment as another revenue stream, PacificDisc formed our FulfillDisc division as a value-added service for our customers first - not necessarily a money-maker. We offer these services to assist our customers get exposure and perhaps zero in on that distribution deal we all want for our projects.
Hands off
So while others are setting up an eStore themselves, deal with merchant accounts, PayPal & web develops - FulfillDisc customers are setup within 24 hours of completing the paperwork and have professionals handling those pesky customer support calls. We lick the stamps and trudge down to the Post Office, so you don’t have to.
For more information about pricing and how to signup, click here for more details.
Take a look at our FulfillDisc online catalog and read the following article - which should get you started.
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
55
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
55
After several weeks of planning and making changes to our internal processes, we have finally been able to publish our eco-packaging pricing. Check it out here: www.pacificdisc.com/PricingEco.html
Chose between 5″ Eco-Sleeves made from 60% recycled board stock and printed with veggie inks, or 4-panel wallets sealed with mylar seals to save on plastic use.
We’ve tried to keep the costs down too, so please let us know what you think
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
55
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/34/d129196689/htdocs/0408/blog/wp-includes/functions.php on line
55
We came across this useful Buyer’s Guide by DigitalFAQ that lists all the various blank media brands (DVD-R, DVD+R, DVD-RW, DVD+RW, DVD+R DL) and all the manufacturers out there. It goes into great detail on which discs work best for various applications, as well as specifying which discs to avoid all together.
http://www.digitalfaq.com/media/dvdmedia.htm
