›

various persistent questions encountered (updated)

nagualnagual
edited May 2015 in Feature requests and bug reports
OSC > FIN (no apparent change in pitch, when compared to coarse steps)

LFO > FIN (treats fine as if it were coarse, no perceived difference between coarse and fine when LFO'd)

CL/OP > FM (even with gain of both FM osc's set to zero, FM seems to be still in effect




Comments

  • julianjulian
    OSC > FIN (no apparent change in pitch, when compared to coarse steps)

    I don't understand what's the problem here... coarse/fine works good here. It was broken in the latest firmware for voice 4,5,6 (fine not working) but on 1-3 I think it worked as expected.
    LFO > FIN (treats fine as if it were coarse, no perceived difference between coarse and fine when LFO'd)

    That's right. I have to take another look in the code, but I think it would have been quite a big effort to include the fine modulation target and it would not yield anything that can't be achieved with a smalled mod amount.
    CL/OP > FM (even with gain of both FM osc's set to zero, FM seems to be still in effect




    I cant confirm this. I just tried it with the CLP and OP/CL voice and with both gain parameters g1/g2 set to zero I get a pure sine and the f1/f2 parameters have no audioble effect.
  • nagualnagual
    gosh, i forgot about this post, i would have updated it since some of this weirdness vanished.  i plan to look at the code too when i get to the studio.

    btw, is the firmware link on the main site different than the latest at github? (i cant remember where the zip link is on the main site right now but i think it points to version .33)
  • julianjulian
    At the moment, yes they are different. I already commited some of the latest changes to github but have not officialy released the next version.

    Normally they should be the same. But I'm probably going to remove the link to my server and limit it to one file @ github
  • nagualnagual
    edited June 2015
    when I set the Midi note to an instrument to C-2, it is actually C-1 according to Reaper when I am sending Midi.  So there seems to be an octave difference in between.  LXR might be off by an octave or Reaper might be.
  • djversus01djversus01
    edited June 2015
    when I set the Midi note to an instrument to C-2, it is actually C-1 according to Reaper when I am sending Midi.  So there seems to be an octave difference in between.  LXR might be off by an octave or Reaper might be.
    For what its worth I've noticed that daw's and hardware seem to not agree on what is C-X, annoying but I've never seen consistency, ever.
  • nightworxxnightworxx
    Yep, unfortunately do some DAW manufacturers keep to the Yamaha definition of keys and some to the one of Roland.
  • lineofcontrollineofcontrol
    Yes unfortunately there are 2 different naming conventions. 1 that starts at c0 and one that starts at c1. Totally uselessly annoying.
Sign In or Register to comment.