1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

1.6.0.6767 Release candidate - Fixed bugs & need info

Discussion in 'Public Beta Discussion' started by Mads L, Mar 9, 2011.

Thread Status:
Not open for further replies.
  1. Mr36

    Mr36 NI Product Owner

    Messages:
    8,454
    Not sure why the link doesn't show, but I'll try again...

    http://www.native-instruments.com/forum/showthread.php?t=132761

    This thread shows a 6775 build. Though Thomas A. has trumped me with 6779. :p
     
  2. kraster

    kraster Forum Member

    Messages:
    275

    This still works for me in the new release, Mr. 36.
    Just hold select while adjusting the master volume knob after selecting events and it does adjust velocities. Phew. I love that feature.
     
  3. Mr36

    Mr36 NI Product Owner

    Messages:
    8,454
    In the previous beta I was doing this but holding the pad down too and it was adjusting the velocities of that pad and not the volume as it does now. I remember thinking how awkward it was, so if just holding SELECT and not the pad as well now does that trick, that's even better anyway. Thanks.
     
  4. stug111

    stug111 NI Product Owner

    Messages:
    23
    My Arturia keyboard bug is still not fixed in this Beta, but is flagged as resolved in bug tracker. My email said : "Remember that you will need to wait for the build with the version equal to or greater than * 1.6.0.6784 * in order to verify this fix!"

    Does this mean my fix will appear in the final release?
     
  5. sowari

    sowari Moderator Moderator

    Messages:
    27,759
    it means that the bug has been fixed with * 1.6.0.6784 * ;)

    sowari
     
  6. Mads L

    Mads L NI Product Owner

    Messages:
    437
    Just to make versioning clear - Our tracking system is tied to our buildserver so for each fix a fix version will be set for the user/tester to know in which version this can be checked and either verified or reopened.

    Bugs in the build family 67** will definitely make the final release
    Bugs that are already flagged as resolved will also make the final release.
     
  7. hank44

    hank44 Account Suspended

    Messages:
    101
    Great work Mads!
     
  8. dath0tsauc3

    dath0tsauc3 New Member

    Messages:
    8
    im trying to get this 1.6.0.6767 Release but its not letting me log in !
     
  9. continuous

    continuous NI Product Owner

    Messages:
    198
    I'm still a bit confused on how this process works. I reported a bug and have received an email saying the issue has been closed yet the bug is still there in the latest build. Does this mean it will be addressed in the next update?

    The bug was: The software shortcut to browse stock effects presets (magnifying glass symbol) is broken.
     
  10. Mr36

    Mr36 NI Product Owner

    Messages:
    8,454
    I used this last night and it's not broken in the build I'm using, which is the latest one. You mean the button that opens the browser, don't you?


    And Mads, I hope you don't mean this literally... I hope this means that bugs found or still present in the build family 67** will be fixed for the final release. Or does this actually mean that the bugs that aren't already resolved will be present in the official release? Doesn't seem right to me. :(
     
  11. continuous

    continuous NI Product Owner

    Messages:
    198
    Is the latest version 6767? That is the version I have that still has the bug.

    I hate to throw the thread off but I'll paste my description.

    Problem Description:
    The presets shortcut (magnifying glass) is grayed out and unresponsive when clicked.

    Reproduction Steps:
    Load stock effect such as METAVERB. In the software, click on the the presets shortcut which is a magnifying class symbol and it will be gray and unresponsive when normally it is orange and when clicked opens the browser showing the presets.
     
  12. Mr36

    Mr36 NI Product Owner

    Messages:
    8,454
    Oh, right, I think we might be talking about different things then. Not sure though. I'll have a look when I get home.
     
  13. Dalski

    Dalski NI Product Owner

    Messages:
    41
    Yep, that is the case here.
     
  14. timmymac13

    timmymac13 New Member

    Messages:
    3
    i'm having the same problem. Does anyone have any insight on this?
     
  15. Eiuro

    Eiuro New Member

    Messages:
    4
    Maschine 1.6 (R6767) does not recognize my virtual instruments but does recognize all waves plugins. How do I have maschine reinstall my virtual instrument plugins?
     
  16. Mr36

    Mr36 NI Product Owner

    Messages:
    8,454
    Have you tried rescanning the plugin directory? Assuming your plugins are all in there...
    ---
    This works as it should do. Loading just an effect is not loading a PRESET i.e. something you can load from the browser, which is what that Quick Browse thing is used for. When you load a preset (FX, instrument, whatever), you can click that magnifying glass and it will automatically load all of the tags of that preset into the browser.
     
  17. continuous

    continuous NI Product Owner

    Messages:
    198
    Mr36 - Thanks for your feedback. I still think this is not working correctly as I used this quite a bit pre-beta.

    So you're working with the software.... you insert a Metaverb plug in one of the modules... then you decide you'd like to run through the presets and to see how they sound so you click the little magnifying glass which should open the browser window and bring up the presets for your plug. From there you should be able to click in the browser and that preset loads into the Metaverb plug which you've inserted. On my setup the magnifying glass is greyed out and null.

    No biggie as it's all doable from the hardware but basically one of the interface elements (the little magnifying glass) is not working correctly - similar to a null link.
     
  18. Mr36

    Mr36 NI Product Owner

    Messages:
    8,454
    It depends how it's supposed to work. What it does at the moment is directs the browser to the loaded preset and highlights it. But this of course requires you to have a preset in their in the first place and so is pretty pointless in a way because if you've loaded a preset you're already at that position in the Browser (be it on the hardware or in the software). If you say that this worked differently pre-beta then this is definitely an issue. It's not something I'd ever used until I tried it last night. The way you describe it to work (or how it should work) certainly sounds more useful.
     
  19. b-righteous

    b-righteous Moderator Moderator

    Messages:
    9,673
    Right. It's for presets.
     
  20. continuous

    continuous NI Product Owner

    Messages:
    198
    Very interesting - I see exactly what you mean now. Hmmm maybe I am confused about how I was using it pre-beta.

    Kinda seems like it should work both ways - whether the plug has been inserted from the module drop-down or was inserted originally by choosing a preset but no biggie either way it's all very do-able from the hardware.

    Sorry for any confusion!
     
    Last edited: Mar 15, 2011
Thread Status:
Not open for further replies.