AVS › AVS Forum › Blu-ray & HD DVD › Blu-ray Players › Official OPPO BDP-95 Owner's Thread
New Posts  All Forums:Forum Nav:

Official OPPO BDP-95 Owner's Thread - Page 298

post #8911 of 10430
Correct. What's happening over that cable is a file transfer. For the audio to go bad the file transfer would have to be corrupted. A broken cable could do that of course -- a cable that wouldn't even work to read or write files with that drive attached to a computer.

But if two cables are both transferring the file correctly, then the audible result can't be better on one cable vs the other. There's no difference between the two files as presented to the decoder.

Now, if the drive/cable combo is letting interference into the player that's going AROUND the digital processing and affecting the analog output stage directly that's a different issue. But I've got no reason, at this point, to suspect that is even possible.
--Bob
post #8912 of 10430
Quote:
Originally Posted by audiofan1 View Post

Be sure your Denon is in it's "direct mode" if it has one, with no additional processing And use Pandora,usb or disc for burn in, 12hrs on and shut it down for 30 min to drain the caps, then back on! 500hrs is the "Honey Pot"

Thanks!! Do I have to have the Denon running, or can I let the Oppo run on its own?

Chris
post #8913 of 10430
Quote:
Originally Posted by Bob Pariseau View Post

Sorry, no. This still makes no sense.


--Bob

Sorry, It makes sense... If one may know a little bit more about how it works the data transfer, and the data processing inside the machine.
Data transfers are very sensitive to errors, specially when this is happen over long wires, long distances. Few meters of wires are such long distances when is about high frequency transfer. Errors occur a lot in a data transfer, specially when is about big files (as music ones f. ex). The same is about wireless data transfer. The bits inside those files are often missing in their places. Those missing bits have to be reconstructed and placed where is detected an error (a missing one). The controller which supervise the transfer in every interface (and are a lot of such controllers both in the processors and in the every involved sender/receiver data circuit in this player main board), have to predict or calculate the value of that bit of information which is missing in the chain. Here is about an internal algorithm which the producer of that transfer chip or processor have decides that will (best) minimise the errors in missing informations. This is an approximation process. Statistic, this process correct the errors in a manner which may also be not 100% some time... The errors correction it may happen many times until the error is appreciated as corrected (by the algorithm involved din this job). At last it works and the CRC of the file is kept, and the errors are in a "legal" standard of specifications for that producer of a chip. The many the ways that such processes and corrections occur, the bigger the possibility to alter the original information.
In such cases of errors correction may also be the firmware involved, the firmware which is burned in the USB processing chip, in the hard disks internal controller, in a video processor chip, in DAC processor, and so on. In lot of places where the data are processed or transferred inside a quite (view from outside) simple machine like this player.
In a transfer of a file with hundreds of Mb or more may occur enormous data errors which are (have to be) corrected, approximated so to be minimised at a maximum level. All this processes which is happen enormous fast, are not all the time 100% sure. The informations in a digital sound file (music f. ex) are also very large and refer to a lot of parameters that sound is/was recorded, post processed, encoded, and so on. Let`s say that in a transfer process, the informations which represent the phase of the sounds of instruments in a music file are approximated in an error correction process. That original phase of the sounds is altered, and is not decoded by the DAC as it was when recorded/encoded. The information of the phase of the sounds in between a band (f.ex) are crucial for the listener to detect the same placement of the instruments (sound stage) as it were when that music were recorded. The listener may miss that information or that may be poor enough, and the resulting sound (which is digitally intact after a transfer from a processor/decoder point of view) will be perceptive as flat or something. I suppose about this kind of difference in quality is about here in the few posts above. About this kind of altering of the resulting sound I referred my self in the USB - eSATA case. This can very well explain why is registered a change in sound quality when one change the USB cables. Bad quality USB cables increase the errors in a data transfer, increase the processing time for correct those errors, the need for large buffers, and so on. This is not something positive or unimportant at all!
The less transfer errors, the less need for processing time for that involved chip/processor/controller, the higher the chance that the original (digitalised) information is transferred less altered or more accurate.
The digital transfer and processing is not perfect at all. It is about a kind of approximations to obtain an result which is in between some specifications of a product, player, chip processor and so on.
Is all this definitively not as black and white as Bob will want to see...
post #8914 of 10430
I realize my message is a bit off the "beaten path," but going to ask anyway since there are so many Oppo owners here.

Anybody running a Meridian 861V4, with the 621HDMI switcher + the Oppo player for doing the HD audio processing?

If so, just curious how this sounds as a setup.

Thx,

Stieger
post #8915 of 10430
Quote:
Originally Posted by Coris View Post

Sorry, It makes sense... If one may know a little bit
more about how it works the data transfer, and the data processing inside the
machine.

This is getting off-topic for a BDP-95 thread. We do have an Audio Theory,
Setup and Chat forum and this type of discussion would be more appropriate
there.

-Bill
post #8916 of 10430
Quote:
Originally Posted by Coris View Post

Sorry, It makes sense... If one may know a little bit more about how it works the data transfer, and the data processing inside the machine.

Reading your post has convinced me that you don't know "a little bit more about how it works the data transfer, and the data processing inside the machine."
post #8917 of 10430
Quote:
Originally Posted by mumps View Post

Thanks!! Do I have to have the Denon running, or can I let the Oppo run on its own?

Chris

Nope just the Oppo!
post #8918 of 10430
Quote:
Originally Posted by wmcclain View Post

This is getting off-topic for a BDP-95 thread. We do have an Audio Theory,
Setup and Chat forum and this type of discussion would be more appropriate
there.

-Bill

It really doesn't even belong in the Audio Theory thread as this is just a simple file transfer that I'm pretty sure was perfected a few decades ago... USB has been around since ~1996 and file transfers via USB have just gotten faster over time - the basic operation of moving bits from location A to location B hasn't changed . If we were talking about USB audio interfaces, the theory forum would definitely be a good place to discuss it.

But you're definitely right that the line of discussion is getting way off topic for this thread.
post #8919 of 10430
Quote:
Originally Posted by Coris View Post

Sorry, It makes sense... If one may know a little bit more about how it works the data transfer, and the data processing inside the machine.
Data transfers are very sensitive to errors, specially when this is happen over long wires, long distances. Few meters of wires are such long distances when is about high frequency transfer. Errors occur a lot in a data transfer, specially when is about big files (as music ones f. ex). The same is about wireless data transfer. The bits inside those files are often missing in their places. Those missing bits have to be reconstructed and placed where is detected an error (a missing one). The controller which supervise the transfer in every interface (and are a lot of such controllers both in the processors and in the every involved sender/receiver data circuit in this player main board), have to predict or calculate the value of that bit of information which is missing in the chain. Here is about an internal algorithm which the producer of that transfer chip or processor have decides that will (best) minimise the errors in missing informations. This is an approximation process. Statistic, this process correct the errors in a manner which may also be not 100% some time... The errors correction it may happen many times until the error is appreciated as corrected (by the algorithm involved din this job). At last it works and the CRC of the file is kept, and the errors are in a "legal" standard of specifications for that producer of a chip. The many the ways that such processes and corrections occur, the bigger the possibility to alter the original information.
In such cases of errors correction may also be the firmware involved, the firmware which is burned in the USB processing chip, in the hard disks internal controller, in a video processor chip, in DAC processor, and so on. In lot of places where the data are processed or transferred inside a quite (view from outside) simple machine like this player.
In a transfer of a file with hundreds of Mb or more may occur enormous data errors which are (have to be) corrected, approximated so to be minimised at a maximum level. All this processes which is happen enormous fast, are not all the time 100% sure. The informations in a digital sound file (music f. ex) are also very large and refer to a lot of parameters that sound is/was recorded, post processed, encoded, and so on. Let`s say that in a transfer process, the informations which represent the phase of the sounds of instruments in a music file are approximated in an error correction process. That original phase of the sounds is altered, and is not decoded by the DAC as it was when recorded/encoded. The information of the phase of the sounds in between a band (f.ex) are crucial for the listener to detect the same placement of the instruments (sound stage) as it were when that music were recorded. The listener may miss that information or that may be poor enough, and the resulting sound (which is digitally intact after a transfer from a processor/decoder point of view) will be perceptive as flat or something. I suppose about this kind of difference in quality is about here in the few posts above. About this kind of altering of the resulting sound I referred my self in the USB - eSATA case. This can very well explain why is registered a change in sound quality when one change the USB cables. Bad quality USB cables increase the errors in a data transfer, increase the processing time for correct those errors, the need for large buffers, and so on. This is not something positive or unimportant at all!
The less transfer errors, the less need for processing time for that involved chip/processor/controller, the higher the chance that the original (digitalised) information is transferred less altered or more accurate.
The digital transfer and processing is not perfect at all. It is about a kind of approximations to obtain an result which is in between some specifications of a product, player, chip processor and so on.
Is all this definitively not as black and white as Bob will want to see...

No, I disagree.

How on earth do you expect an audio phase error to crop up in a file transfer when the phase is not even relevant until the data is decoded? It's NOT AUDIO YET!

And a large buffer is no different than having the file entirely in memory before the decoding starts.

Let me try expressing it another way. The USB in this case is not being used as a data path between a computer audio driver and a DAC -- the sort of thing that would happen with an external USB DAC. The USB is being used to do a file transfer.

All of the audio errors you are worried about can only happen between the decoder and the DAC, which are both inside the player -- no USB involved.

-------------------------------------------

Ah well, Bill is right. I'll make this my last response on this.
--Bob
post #8920 of 10430
Quote:
Originally Posted by wmcclain View Post

This is getting off-topic for a BDP-95 thread. We do have an Audio Theory,
Setup and Chat forum and this type of discussion would be more appropriate
there.

-Bill

Agree!
post #8921 of 10430
Quote:
Originally Posted by Bob Pariseau View Post

No, I disagree.

How on earth do you expect an audio phase error to crop up in a file transfer when the phase is not even relevant until the data is decoded? It's NOT AUDIO YET!

And a large buffer is no different than having the file entirely in memory before the decoding starts.

Let me try expressing it another way. The USB in this case is not being used as a data path between a computer audio driver and a DAC -- the sort of thing that would happen with an external USB DAC. The USB is being used to do a file transfer.

All of the audio errors you are worried about can only happen between the decoder and the DAC, which are both inside the player -- no USB involved.

-------------------------------------------

Ah well, Bill is right. I'll make this my last response on this.
--Bob

Yes... This can be (become) a long discussion...and I agree with that opinion (above) that is out of the topic here... Else is also too much to be written on this subject... Let`s forget this for moment.
post #8922 of 10430
Quote:
Originally Posted by audiofan1 View Post

Nope just the Oppo!

Sweet. Your assistance is greatly appreciated.

On a side note, The picture on my new Panasonic TC-P65VT50 provided by the Oppo is absolutely stunning!

Chris
post #8923 of 10430
Quote:
Originally Posted by mumps View Post

Sweet. Your assistance is greatly appreciated.

On a side note, The picture on my new Panasonic TC-P65VT50 provided by the Oppo is absolutely stunning!

Chris

I know you gotta be lovin that setup

Happy viewing and listening
post #8924 of 10430
Quote:
Originally Posted by stieger View Post

Anybody running a Meridian 861V4, with the 621HDMI switcher + the Oppo player for doing the HD audio processing?

I run the Oppo 95 into the 621 with my 861v6 and am very happy with the setup. Prior to this, I had the v4 and prefer the v6. OTOH, that applies to every input source so it is not a direct reflection on the v4 combination which worked well.
post #8925 of 10430
Quote:
Originally Posted by ttsakai View Post

Hi Bob,

I just would like to jump in here regarding my original post regarding the sound reproduction quality of a USB interfaced disk drive using a the "stock" cheap USB data cable versus using an upgraded Furutech ST2 USB cable.

I realize that this flies against all logic with regards to the discussion of 0s and 1s and either the data accurately gets to its destination or not. And how can the sound be affected purely based on the quality of USB cable. I can't explain it myself but all I can say is try it for yourself and you'll definitely hear a difference in the quality of the sound reproduction. We're not talking about a subtle difference. The frequency response is extended especially in the lower frequencies and the sound overall is fuller and has more detail. Go figure.

By the way my Oppo 95 has the Modwright upgrade including the upgraded umbilical cord between the power supply and the analog section in addition to an installed Bybee rail and also an Audio Magic Pulse Gen unit.

How would you compare the stock 95 versus the Modwright's 95? I've been mulling his mod for a while. I met him over the weekend at the Show in Newport and was a great guy indeed! Does he mod the MCH on the tube mods version of the 95?
post #8926 of 10430
I am going to buy a Oppo BDP 95 from a retailer in Canada that has a full replacement warranty for one or two years available for purchase at $69 and $99. Is it worth getting the extra warranty? What is the build quality of the player?
Also, I am going to be using a NAD T787 receiver and Panasonic VT 30 TV with it. Has anyone had any compatibility problems with any of these devices?
Thanks,
Jim
post #8927 of 10430
Quote:
Originally Posted by LSL#1 View Post

I am going to buy a Oppo BDP 95 from a retailer in Canada that has a full replacement warranty for one or two years available for purchase at $69 and $99. Is it worth getting the extra warranty? What is the build quality of the player?
Also, I am going to be using a NAD T787 receiver and Panasonic VT 30 TV with it. Has anyone had any compatibility problems with any of these devices?
Thanks,
Jim

The odds of you collecting are far greater than 90 to 1. Throw in the fact that OPPO does repairs on players out of warranty for very low fees and I would take a pass.

Quote:
Also, I am going to be using a NAD T787 receiver and Panasonic VT 30 TV with it. Has anyone had any compatibility problems with any of these devices?

Why are you buying the 95 instead of the 93? I ask only because they are identical for video, and you don't mention critical listening for music.
post #8928 of 10430
Thanks for your reply htwaits. I will pass on the extra warranty. I just had to ask to make sure.
I currently have an Oppo 83 and have been happy with its audio performance, but I have also been very curious to find out how much better the Oppo 95's is ever since I found out about it. Just recently, I have become interested in getting a 3D capable player, so that has given me the reason to buy now.
post #8929 of 10430
Quote:
Originally Posted by LSL#1 View Post

I currently have an Oppo 83 and have been happy with its audio performance, but I have also been very curious to find out how much better the Oppo 95's is ever since I found out about it. Just recently, I have become interested in getting a 3D capable player, so that has given me the reason to buy now.

I don't have the 95, but I understand that it takes first class analog electronics, very good room acoustics, very good speakers, as well as discriminating ears to get the full benefit from the difference between the 95 and the 93. Enjoy.
post #8930 of 10430
Quote:
Originally Posted by Coris View Post

Agree!

Was googling on the subject Coris and while o/t so will say no more you may be interested in this vvv ;of course the oppo has jitter reduction dacs so its more horses for courses Interesting that the ayre dx5 [based on the oppo 83] has asynchronous usb input as well .

http://www.audiophilleo.com/audiophilleo1.aspx

Quote:
Data transfers are very sensitive to errors

If by that do you mean ''jitter'' ? as in timing errors ? I assume not Oppo certainly addresses's this problem with its ess dacs
post #8931 of 10430
Quote:
Originally Posted by cwt View Post

Was googling on the subject Coris and while o/t so will say no more you may be interested in this vvv ;of course the oppo has jitter reduction dacs so its more horses for courses Interesting that the ayre dx5 [based on the oppo 83] has asynchronous usb input as well .

http://www.audiophilleo.com/audiophilleo1.aspx

That product is a USB audio interface - so the device would appear essentially as a sound card when connected to a PC. The Oppo BDP-93/95 just use USB for transferring files from an external storage device. That's a VERY big difference.

Quote:
If by that do you mean ''jitter'' ? as in timing errors ? I assume not Oppo certainly addresses's this problem with its ess dacs

Things like jitter don't come into play for file transfers.
post #8932 of 10430
Quote:
Originally Posted by gsr View Post




Things like jitter don't come into play for file transfers.

Sorry, you are very wrong here. Jitter exist everywhere where is about a frequency signal. A file transfer is in fact (electrical point of view and said in a very simple way) a multitude of frequencies of switching digital levels over a line (wire or wireless). Jitter in such cases are eliminated with special digital techniques inside the chip involved. Too much jitter in the case of a digital transfer lead to errors, and at least can corrupt the file to be transferred (is a particular case where transfer errors occur).
post #8933 of 10430
Quote:
Originally Posted by Coris View Post

Sorry, you are very wrong here. Jitter exist everywhere where is about a frequency signal. A file transfer is in fact (electrical point of view and said in a very simple way) a multitude of frequencies of switching digital levels over a line (wire or wireless). Jitter in such cases are eliminated with special digital techniques inside the chip involved. Too much jitter in the case of a digital transfer lead to errors, and at least can corrupt the file to be transferred (is a particular case where transfer errors occur).

I doubt that there will be errors in the USB file transfer. USB uses a CRC check on each packet sent to verify data transfer integrity. Cosequently, jitter is not a issue in the file transfer. It should be bit perfect and the bit timings in the transfer have no effect on the data stream sent to the DACs,
post #8934 of 10430
Quote:
Originally Posted by Coris View Post

Sorry, you are very wrong here. Jitter exist everywhere where is about a frequency signal. A file transfer is in fact (electrical point of view and said in a very simple way) a multitude of frequencies of switching digital levels over a line (wire or wireless). Jitter in such cases are eliminated with special digital techniques inside the chip involved. Too much jitter in the case of a digital transfer lead to errors, and at least can corrupt the file to be transferred (is a particular case where transfer errors occur).

This is right in a simple way and very wrong. The electrical signals being used are transmitted on one or several frequencies, but the data being carried is not affected by the frequencies chosen.

The data is expressed as 1's or 0's electrically. In all cases, the 1 or 0 is done as a plateau voltage value; for example, a 1 could be 5 volts, a 0 could be 0 volts. This is also time based, so that you avoid false values, so a value (5 or 0) is held for a certain time cycle to make sure you have an actual value. These 1's and 0's are gathered into bytes (8 bits) to make them useful as a way to transfer data. These bytes are then grouped into blocks, those blocks into data blocks.

The data blocks hold the raw information that makes up, for example a song. In the case of USB or eSATA, the data is not just pushed across a wire. There are several levels of error checking that happen at the time of transfer of bytes, blocks, data blocks and transactions as a whole. In the case of ethernet or radio transfers, there are many levels of checking for errors to avoid exactly the type of issue where you would lose data.

Errors are often found during the transfer, but the safeguards put in place at every level ensure that, even if a corrupted chunk of data is found, it is just re-transmitted until the transfer is done correctly or fails completely. In which case the interface throws up its hands and says "I'm done".

Jitter due to electrical interference at the most basic level plays a role only in the formation of 1's or 0's. That has been handled already by algorithms that deal with appropriate approximations of what 1 or 0 should be. Something serious enough (in the wireless area or wired) to break down the recognition of 1's or 0's will shut down the whole shebang, not selectively corrupt data. Which is what would cause some things to sound bad and others good.

The USB 2.0 (60 mBytes/s , more like ~25 mBytes / sec in real life), USB 3.0 (625 mBytes/s) and eSATA (300 mBytes/s) protocols are sufficiently fast enough to maintain the required Bluray top speed (54 mbit/s of 6.75 mBytes/s) without much issue. Even if you assume a 100% failure rate - every byte has to be resent due to corruption, that demands a 13.5 mByte transfer speed, which even USB 2.0 would have no problem holding.

So assuming that you have 100% errors, if an interface or a cable meets the USB 2.0 requirements and so can call itself such (which is the only way it can say so), then it should have no problems. Jitter is not an issue in a digital transmission unless it is so severe that it shuts everything down.
post #8935 of 10430
Quote:
Originally Posted by hernanu View Post

This is right in a simple way and very wrong. The electrical signals being used are transmitted on one or several frequencies, but the data being carried is not affected by the frequencies chosen.
The data is expressed as 1's or 0's electrically. In all cases, the 1 or 0 is done as a plateau voltage value; for example, a 1 could be 5 volts, a 0 could be 0 volts. This is also time based, so that you avoid false values, so a value (5 or 0) is held for a certain time cycle to make sure you have an actual value. These 1's and 0's are gathered into bytes (8 bits) to make them useful as a way to transfer data. These bytes are then grouped into blocks, those blocks into data blocks.
The data blocks hold the raw information that makes up, for example a song. In the case of USB or eSATA, the data is not just pushed across a wire. There are several levels of error checking that happen at the time of transfer of bytes, blocks, data blocks and transactions as a whole. In the case of ethernet or radio transfers, there are many levels of checking for errors to avoid exactly the type of issue where you would lose data.
Errors are often found during the transfer, but the safeguards put in place at every level ensure that, even if a corrupted chunk of data is found, it is just re-transmitted until the transfer is done correctly or fails completely. In which case the interface throws up its hands and says "I'm done".
Jitter due to electrical interference at the most basic level plays a role only in the formation of 1's or 0's. That has been handled already by algorithms that deal with appropriate approximations of what 1 or 0 should be. Something serious enough (in the wireless area or wired) to break down the recognition of 1's or 0's will shut down the whole shebang, not selectively corrupt data. Which is what would cause some things to sound bad and others good.
The USB 2.0 (60 mBytes/s , more like ~25 mBytes / sec in real life), USB 3.0 (625 mBytes/s) and eSATA (300 mBytes/s) protocols are sufficiently fast enough to maintain the required Bluray top speed (54 mbit/s of 6.75 mBytes/s) without much issue. Even if you assume a 100% failure rate - every byte has to be resent due to corruption, that demands a 13.5 mByte transfer speed, which even USB 2.0 would have no problem holding.
So assuming that you have 100% errors, if an interface or a cable meets the USB 2.0 requirements and so can call itself such (which is the only way it can say so), then it should have no problems. Jitter is not an issue in a digital transmission unless it is so severe that it shuts everything down.

Exactly. When I mentioned jitter, I thought it was obvious I was talking about the type of jitter that people get so worried about in audio circles - THAT type of jitter doesn't apply when using either the USB or eSATA ports on the Oppo players.
post #8936 of 10430
Quote:
Originally Posted by gsr View Post

Exactly. When I mentioned jitter, I thought it was obvious I was talking about the type of jitter that people get so worried about in audio circles - THAT type of jitter doesn't apply when using either the USB or eSATA ports on the Oppo players.

Yup. Agree completely.
post #8937 of 10430
I recently replaced my BDP-83SE with a BDP-95, and given some of the comments I've read from others concerning fan noise, a problem that has very much bothered me too (and with both of the players), I thought it might be helpful if I described some of my recent experiences, and the best solution that I have found. When I first installed the BDP-95 in my wooden stereo cabinet, which has two shelves that are open on the front but closed on the sides and back, except for a few 4 inch ventilation holes in the back, the fan came on frequently, and often caused a very loud noise. By removing the back panel from the cabinet and moving my BDP-95 to the bottom shelf and my integrated amplifier to the top shelf, I was able to keep the fan from coming on as often, and to reduce the amount of noise that it made. But the fan still came on after about 50 minutes, and during a total test period of 3 hours, it came on 9 more times, each time for roughly 4-6 minutes (and each time at low speed, except for once toward the end of the 3 hours when it came on at a higher speed).

Because my listening room is very quiet, and I'm very sensitive to noise and the nuances of musical performance, and mostly listen to classical music at low to moderate volume levels, this remaining fan noise still really bothered me. In trying to brainstorm a solution, I considered both thermoelectric and exothermic approaches, but quickly gave up on a thermoelectric solution due to both practical and cost related concerns. In the end, what seemed most promising was an exothermic approach using cold packs, so I checked the web and finally came across some "Moisture-Resistant Cold Packs" that are used to keep pharmaceutical products cool and dry during shipment. Before placing an order, I contacted Oppo, described the cold packs and how I planned to try using them, and asked if there would be any warranty problems if I proceeded. Oppo said there would not be, so I ordered one dozen 24 ounce "Moisture-Resistant Cold Packs" from ULINE for $21, plus S/H (Model S-18251, www.uline.com).

The cold packs contain non-toxic gel, feature a non-woven 1.5 ounce leakproof outer poly cloth that "absorbs all moisture," are reusable, and when placed in a normal freezer overnight are said to reach a temperature of 30 F. After some experimenting, I found that placing 3 of these cold packs side by side on top of the BDP-95 seems to work best (which leaves an inch or so of the player uncovered at the front and back), and that by using the cold packs in this fashion, I can keep the fan from coming on at all for about three and a half hours (with room temperature in the 60's), at which point the cold packs have warmed up enough to need to be changed. Although the cold packs did seem to absorb almost all moisture when I first tried them out, leaving the top of the Oppo only slightly damp, I have found that in everyday use, when I do not give them the time to completely dry on the outside before refreezing, they do gather some frost in the freezer and leave a bit of water under them on top of the player, but since my player is level, this has not seemed to pose any problem, and has been easy to simply sponge off. I towel each cold pack pretty much dry after use and place it in a zip-lock freezer bag for refreezing.

Since this is my first post on this site since purchasing a BDP-95, I might also mention that I have been surprised and pleased at how much of an improvement in sound quality I note with the BDP-95 over the BDP-83SE, in terms of spaciousness, detail, bass definition, and sheer musicality, even in my rather simple stereo system (BDP-95 via Audience 24e's to NAD C325BEE via Kimber 8TC's to NHT Classic Threes, with the NAD plugged into an Audience aR1p). I can't say I enjoy the cold pack routine (and I certainly hope that Oppo or someone will come up with a better solution soon), but at least for three and a half hours I'm in musical heaven. Bravo to Oppo for a great design, and thanks to those on this forum for the many comments I've learned from.
post #8938 of 10430
Quote:
Originally Posted by hernanu View Post

Jitter is not an issue in a digital transmission unless it is so severe that it shuts everything down.

Yes, you express yourself and explain better than I can in my English....
I intended to say the same about jitter. This exist anyway in digital "world" too, but is not an issue in digital transmissions, just because everything is corrected in many levels and techniques in the internal circuits of a transmission device or processors, and so on.
This subject is quite vast and maybe a little bit out of topic here, but if come some good explanations as above, one can get a better view of the "case"...
Anyway, I still mean that less errors to be corrected in a transmission process, the better the finally result. Everything which is to improve the errors levels in a digital process is benefit for the final quality of the result of that process.
post #8939 of 10430
Quote:
Originally Posted by gsr View Post

Exactly. When I mentioned jitter, I thought it was obvious I was talking about the type of jitter that people get so worried about in audio circles - THAT type of jitter doesn't apply when using either the USB or eSATA ports on the Oppo players.

I fully agree with your extended now explanation. But in your original above post did not came out clearly this idea you have precise last...
If do not come another interventions on this quite theoretical subject, maybe we can consider this closed, for not to come completely out of the thread`s topic...
post #8940 of 10430
Quote:
Originally Posted by gsr View Post


That product is a USB audio interface - so the device would appear essentially as a sound card when connected to a PC. The Oppo BDP-93/95 just use USB for transferring files from an external storage device. That's a VERY big difference.

Things like jitter don't come into play for file transfers.
Primarily suggested it to Coris as an alternative as it just has a sp/dif output for avr/pre pro input cool.gif No secret an asynchronous usb input would be preferable jitter wise compared to the standard one the 95 has . Its been mentioned in the '' wishlist '' thread a few times [not just by me biggrin.gif ] . May be out of oppo's target demographic but I can hope smile.gif
Quote:
Things like jitter don't come into play for file transfers

As Bob has explained ; of course .Without going into audio theory [not the place for this of course] this link will hopefully show where Ime coming from; if Its good enough for Ayre to make the usb on the dx5 asynchronous to help eradicate noise and jitter ...

http://www.audioasylum.com/forums/pcaudio/messages/7719.html
Edited by cwt - 6/6/12 at 11:43am
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Blu-ray Players
AVS › AVS Forum › Blu-ray & HD DVD › Blu-ray Players › Official OPPO BDP-95 Owner's Thread