Jump to content
SAU Community

Recommended Posts

Any ideas on how to get around them?

Even on perfect CDs I get them.

 

Tried ripping at every available speed from 1.00X to 32.00X.

Tried EAC, Audiocatalyst, iTunes, even copying the WAV files with random programs then using Audiocatalyst to convert to mp3.

Tried several different encoders (including all bitrates between 128 and 320k)

 

Sorta running out of ideas... maybe the cdrom is just sh1t? Aopen 52x32x52...

where r u getting the tracks from because it will most likely be from the sorce & if so u are not going to get rid of em :Bang:

  • Replies 62.7k
  • Created
  • Last Reply

Top Posters In This Topic

  • chaos

    7164

  • Ska

    5791

  • BelGarion

    3645

  • Nexus9

    3590

Top Posters In This Topic

hey mike.. waz up?

well now i sold my r33 i might do some stuff on the r31..

might come this weekend to see what i might buy off your wreck. at the moment the only thing that is really bothering me is the odometer stopping about a month ago.. but i just need the little bit inside the cluster. its hard to explain.

rest not sure. one minute some of the worn stuff bothers me, at others its just extra character :D

Any ideas on how to get around them?

Even on perfect CDs I get them.

Tried ripping at every available speed from 1.00X to 32.00X.

Tried EAC, Audiocatalyst, iTunes, even copying the WAV files with random programs then using Audiocatalyst to convert to mp3.

Tried several different encoders (including all bitrates between 128 and 320k)

Sorta running out of ideas... maybe the cdrom is just sh1t? Aopen 52x32x52...

I got around them by creating an iso image of the cd using alcohol 120%, using isobuster to correct any "errors" Using Daemon tools to run the corrected iso image then using Musicmatch Jukebox to rip them.

Pain in the arse but it worked for me

Sorta running out of ideas... maybe the cdrom is just sh1t? Aopen 52x32x52...

probably :D is the pops playing on every device u try and play it back on?

i never have had probs? i was using a pioneer drive to rip them though?

oh them..

from what i remember i think i just used nero to extract each track as WAV's.. then fed thru musicmatch to generate the mp3 ... worked fine using the pioneer. I think some drives must just be more sensitive to the protection than others?

i think it was how i did it on a couple of cds anyhow.. but i forget. they could have brought out even newer protection.

Guest
This topic is now closed to further replies.



  • Similar Content

  • Latest Posts

    • Input shaft bearing. They all do it. There is always rollover noise in Nissan boxes - particularly the big box. Don't worry about it unless it gets really growly.
    • For once a good news  It needed to be adjusted by that one nut and it is ok  At least something was easy But thank you very much for help. But a small issue is now(gearbox) that when the car is stationary you can hear "clinking" from gearbox so some of the bearing is 100% not that happy... It goes away once you push clutch so it is 100% gearbox. Just if you know...what that bearing could be? It sounding like "spun bearing" but it is louder.
    • Yeah, that's fine**. But the numbers you came up with are just wrong. Try it for yourself. Put in any voltage from the possible range and see what result you get. You get nonsense. ** When I say "fine", I mean, it's still shit. The very simple linear formula (slope & intercept) is shit for a sensor with a non-linear response. This is the curve, from your data above. Look at the CURVE! It's only really linear between about 30 and 90 °C. And if you used only that range to define a curve, it would be great. But you would go more and more wrong as you went to higher temps. And that is why the slope & intercept found when you use 50 and 150 as the end points is so bad halfway between those points. The real curve is a long way below the linear curve which just zips straight between the end points, like this one. You could probably use the same slope and a lower intercept, to move that straight line down, and spread the error out. But you would 5-10°C off in a lot of places. You'd need to say what temperature range you really wanted to be most right - say, 100 to 130, and plop the line closest to teh real curve in that region, which would make it quite wrong down at the lower temperatures. Let me just say that HPTuners are not being realistic in only allowing for a simple linear curve. 
    • I feel I should re-iterate. The above picture is the only option available in the software and the blurb from HP Tuners I quoted earlier is the only way to add data to it and that's the description they offer as to how to figure it out. The only fields available is the blank box after (Input/ ) and the box right before = Output. Those are the only numbers that can be entered.
    • No, your formula is arse backwards. Mine is totally different to yours, and is the one I said was bang on at 50 and 150. I'll put your data into Excel (actually it already is, chart it and fit a linear fit to it, aiming to make it evenly wrong across the whole span. But not now. Other things to do first.
×
×
  • Create New...