Jump to content


Steve in VA

Member
  • Posts

    93
  • Joined

  • Last visited

Posts posted by Steve in VA

  1. UPDATE: 72 hours later, my Kronos is healed! I found an authorized Korg tech a couple hours drive away who was able to take it in the same day. It seems to have been a spring that was not properly seated under the one key. He reassembled it and tightened everything up.

     

    So for the price of a few hours of my life driving and a couple tanks of gas, all is good once again. Thanks again for the responses.

  2. Question for anyone with experience getting warranty service. I got a Korg Kronos 2-61 back in November. One of the keys started making a rattle/clicking sound when pressed or released. It still functions fine, but is annoying. Other than the one key, the keybed is dead quiet. I am in the middle of my 1-year warranty period.

     

    Is this a reasonable thing to have fixed under warranty or am I being too nit-picky? Also, how does warranty service work. Do you just directly call one of the nearby service centers and coordinate with them?

     

    Thanks!

  3. Sad to say, 'Jump' is the very first one.....

     

    And it's great! There is an "I'll Wait" patch too. Now, does anyone know where I can find good tabs for those songs?

     

    Seriously, this VST seems well worth the $49 to me. Lots of fun.

  4. I thought I would chime in since I was in about the same spot as you 3-4 years ago. I tackled Linus and Lucy as one of my first songs because no one ever told me it was considered hard! I eventually learned the entire song, one bar at a time, by slowing down the recording with MusicSpeedChanger on my phone. I also found that playing to a metronome or drum beat helped. There is a pretty good (but not quite perfect) transcription that is free on MuseScore.

     

    It's only been within the past year or so that I can finally play the song with nuance and "feel". It always seemed to be lacking something I could not quite put my finger on.

     

    Just remember to "slow it down and break it down" and you'll get it!

     

    Also, I found it helpful to work on BOTH hands at the same time, but only a few notes at a time.

  5. Furthermore, it has coilwhine, which is a constant, high-pitched "whining" noise coming from capacitors/inducers/electric coils inside the machine. This is highly irritating, but doesn't affect your music.

     

    I have not had this problem with my XPS 15. Unless the fan cuts on, it is dead silent.

     

  6. I have a 2017 XPS 15 (9560 model) that I use for similar purposes. I have optimized it to its limits: 32 GB RAM and 2TB Samsung EVO NVME SSD.

     

    On RAM, 32 GB should be more than enough unless you create enormous projects with huge amounts of sample-based instruments. You can always upgrade the RAM later if you need to. RAM usually only gets cheaper over time.

     

    Regarding SSD storage, if you get a fast NVME SSD such as the Samsung EVO 970, they provide more than enough throughput for everything. No need for separate drives or partitions.

     

    One common issue with Dell laptops (and many others) is DPC latency, which means system drivers may consume more CPU time than they are supposed to and can cause audio drop-outs despite all your optimization efforts. I was able to tame these problems by keeping WI-FI disabled when doing audio, turning off bluetooth, and disabling all unnecessary Windows services. I also have a totally separate boot partition for audio, since applications such as MS Office tend to wake up and do things at random times and wreak havok on audio.

     

    Despite the challenges, I do like the laptop and the fact that it cost about half of a MacBook with similar specs.I also use it for work.

  7. To put the prices in perspective, I just built a PC with Intel i9 9900k (8 core), 64GB of RAM, 2TB Samsung SSD (NVME - fast!), dead-silent case, and a motherboard with Thunderbolt support for about $2,000 and change. And it rocks!
  8. Just a quick update on my problem a while back of lower VST volumes in GP3 vs. Studio One:

     

    It turns out my controller was sending all MIDI messages on two channels simultaneously. GP and Studio One apparently handle this situation differently, resulting in volume differences. Once I eliminated the duplicate MIDI, the problem went away. So yes, it was user error.

     

    (Provided the update on the off chance anyone ever encounters something similar.)

  9. 1. Ringo Starr and Friends (Colin Hay, Steve Lukather, etc.)

    2. FloydFest, featuring Brandi Carlisle, Kasey Musgraves, String Cheese Incident, Lukas Nelson, and many others

    3. Pat Metheny (front row!)

    4. Steve Vai, Yngwee Malmsteen, Nuno Bettencourt, Zakk Wilde, and friends

    5. Some dude from Long Island who calls himself a piano man and gripes about having to cut his songs down to 3:05 :)

  10. In my case, I have found Windows TB performance to be half-baked even on a laptop that has it integrated into the motherboard: Dell XPS 15 9560.

     

    I have used two TB interfaces, Apollo Twin - which performed on par with a cheap USB interface latency-wise, and the Presonus Quantum 2, which was worse. In both cases, I was using a well-optimized machine with updated drivers.

     

    After switching to the Babyface PRO USB 2.0, latency and stability performance is stellar. Sometimes proven technology is just a better choice.

  11. Thanks for the suggestions. As best I can tell, all Keyscape settings are the same in both GP3 and Studio One, but I will keep looking.

     

    I get lower volumes using other VSTs also, but Keyscape sounds the most dramatically different.

     

    This problem seems to have developed recently, possibly when I did a software update of GP3 a while back. I will check their forums also for any hints.

  12. This is a question for any users of GigPerformer 3.

     

    I have noticed than when I create a new .gig file and add a VST (Keyscape in particular), the sound levels are significantly lower and the timbre sounds not quite the same as when I load the same plug in into Studio One.

     

    In both cases, I am not altering any volume levels on input or output. Sample rate is set to 44.1k and my interface (Babyface Pro) is set to 64 samples. So no differences in configuration that I can tell.

     

    Any ideas why I would get different results in GP3 vs Studio One?

     

  13. It looks good, but causes the vertical scroll bars to be invisible (blacked out) on my Chrome/Windows 10. The other dark mode, "UBBT70 - Dark" does not have this problem and has better contrast, to my eyes.
×
×
  • Create New...