A little "Pop" at the beginning of a track?

[jahern]

I reinstalled but still get a little "click" or "pop" before play preview, and, I will test this again later, suppose that the new file and resultant disc will also include the noise, just as before. This is on raised files. I have windows XP and I imagine that the solution has something to do with hardware accelaration.

I will do further testing when I am home at my own computer. Until then, assume that I have the same problem as before, a nasty little "pop" at the beginning of raised files.

[jahern]

Dabbled with hardware accelaration and it doesn't seem to improve anything. Am I the only one with this problem? Is there noone who has a solution?

[George]

Hi Jahern,

Been watching this with interest. I haven't a clue as to what's happening, but wonder if you'd do something.

Save one of the files with the pop in it. Use a slightly different name so's not to mess up the original.

I believe I remember you having an audio editing program.

Open the track into your audio editing program and see it the pop is visible. One would think it should be.

If so, then you should be able to edit it out, as you well know.

The only reason for this exercise is to give you a "workaround" so you can use tracks in the key you wish until an answer can be found.

At his point I haven't been able to duplicate it, but will keep messing around with it.

Take care,

George

[jahern]

George, Thanks for your good wishes.

I actually had to use a file with the key changed up at an affair in which I was to sing "Top of the World". I was noticing the little "Pop" but was going to live with it. That morning I decided to take some time and make an MP3-G of the file, convert the mp3 part to wave, use Nero to change the key, change it back to mp3, convert the mp3-g to Bin then back to normal cdg (Whew-I'm out of breath) No "pop" in an original cdg, but obviously a lot of extra work.

So I do have the workaround. Obviously the workaround is less if I am creating the files with KHPRO. I haven't tried wave files on Keyrite recently. But if Keyrite can't do the cdg files, then it's not very useful.

But like I have said already. The downward keychanges don't seem to have this problem.

[George]

Jahern,

Somehow or another I didn't pick up on the fact you were having the difficulty with CDG files...that should have been obvious, but I missed it, and became focused on WAV

I imported 10 cdg tracks to the hard drive and opened each one into Keyrite.

There is a very distinct pop as a track opens with a upward key change. This happened on all ten tracks. All ten were KHP produced.

I then grabbed a Sound Choice disc at random and imported a track into the hard drive. A definate click when selecting a upwards key change.

You're not alone, old buddy

It sounds to me like the pop happens just as the graphic title page starts to load because the popping is almost instant as one clicks the upward key number and is followed by a few seconds of silence before the audio kicks in.

George

[jahern]

I read the e-mail that your entry generated and did a little experimenting. As I went on-line again I came to find out that you did some more investigating yourself and edited your post. Thanks for your efforts and thanks for setting my mind at ease that my computer isn't malfunctioning. My new results were, of course, similar to yours.

Oh yeah, and the waves worked fine, but not when made into cdg files by KHP, with the already stipulated exceptions

[jahern]

So far, it looks like the problem that I brought up in this thread is "reproducible", so it seems that my own computer is not necessarily very flawed. I'm wondering why noone has chimed in with a solution, or at least pointing me in the direction of another thread where this issue is discussed, and a solution is given. This version of keyrite has been out for a long time and even though I haven't usually used the raise-the-key buttons, someone else has, either with similar results, or with different results-which somehow points at my equipment. I'm all ears about what to do.

Even a "We are aware of the problem, and there will be corrections in the next version" from MTU would be nice.

PS. Once again, thanks everybody for the input already received.