![]() |
|
Keyrite 2 Help Post Keyrite 2 questions, tips and suggestions here. |
![]() |
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
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 Last edited by George; June 22nd, 2005 at 09:38 AM. |
#2
|
|||
|
|||
Thanks
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 ![]() |
#3
|
|||
|
|||
We've established a problem; now what?
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. |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Display Modes | |
|
|