1.1 update issues thread

Hi folks - just starting this in case there is anything pressing. Thanks.

Comments

  • edited February 2020
    1. The patches use more than twice the RAM as the v1.0.1 patches according to the Kontakt RAM info. Oopsie, why that?
    2. The CPU print is slightly heavier. What a bummer. Would be great to have some performance boost with updates and not vice versa. )=
    3. I cannot load old patches without renaming new and old WHOLE folder and reloading the project. So basically I cannot even compare the two versions side by side easily ...
    4. In a way the new patches sound weirder to me. Here I did some violin and cello ensemble (dry) comparison. Motifs are first the old ones and directly after that the new ones. Especiall the trill in the new violins is not even usable: (MP3 attached here... hopefully?)

    And I could not hear CC38 or CC27 make any difference (according to the mail the first one should make the attack more aggressive).

    I am looking forward to the next update, I guess, while sticking to v1.0.1 - what a bummer. Luckily I did not delete the old folder and I would suggest other users to do so as well, before trying the update on their own!

    Oh: and due to point 3. I cannot even load older projects, when updating. This totally should not happen - or at least the old patches should still be usable (tried in Reaper v6.03).

  • Tagirijus,

    I'll reply for the time being to your observation: "Especiall the trill in the new violins is not even usable". You are right, the ensemble trills are faulty. We found a coding error which under certain circumstances provokes this issue. A fix will be available soon.

    Sorry for the inconvenience.

    As to the other observations, please be patient. We'll reply ASAP.

    Giorgio

  • Hi Giorgio, thank you for the quick reply. I'll stay patient, no problem. (=

  • Thanks for your hard work. I noticed also that specifically the viola ensemble (dry) has a tapping noise with trills as well around middle c.

  • Dear friends,

    we found the coding bug, and could prepare a new set of ensemble patches perfectly working. They are now at NI for locking. We hope to have them available by the beginning of the next week.

    Best,

    Giorgio & Peter

  • Looking forward to the new patches. Thank you! (=

  • Hi all,

    I did a little test with short notes and I must say two things:


    1. I like the sound of the update the most;

    2. The short notes are more distinct in the old version. I the new one seems a little messy (maybe I'm doing something wrong with settings).


    I recorded the little test and in the second repetition I brought the velocity almost at the maximum level, by doing this I felt the notes became more distinct that in the first repetition. You will hear v 1.0.1 before and 1.1 after.


    In the 002 MP3 the attack knob is at 0 and the other settings are the same for 1.0.1 and 1.1.


    In the spiccatos MP3 I shortened the notes a bit more and I slowed down tempo to 80 bpm and then 60 bpm (the first is at 120 bpm) and the effect is more present, am I doing something wrong?

    Will this be addressed with this quick fix?


    Thank you.

  • Hi. First of all, this Set of strings is the best I have never used and heard. Thanks for your Wonderfull work.

    I want to show another issue that I have detected. Viola Solo patch with sustain pedal for change to detache doesn't work properly. Every note keep sounding and became detuned.

    Thank you.

  • I noticed that too, but this problem is also present in 1.0.1 it is not a 1.1 fault. The sustain pedal doesn't work as expected with viola solo patch.

  • Update in my issue:


    1. The "I cannot hear"-thing was due to the missing re-mapping of the "Volume" CC, which I overlooked on the remapping page 4. This might be a GUI bug: the volume remapping is on the upper left, instead of the lower right!


    2. Old projects have to be loaded and the patches have to be re-loaded by the user to make the old project "work again".

  • edited April 2020

    Hi, I hope this is the right place to ask this, apologies if not, I'm new here. :)

    CC19 by default controls both vibrato rate and (when tremolo is activated) tremolo rate. When I remap CC19 to CC1 (with nothing else mapped fo CC1), this successfully remaps vibrato rate, but tremolo rate is still only controlled by CC19. Am I missing something to remap tremolo rate?

    Also when I remap vibrato intensity to CC11, this works fine, and the label "CC11" appears correctly next to the vibrato intensify knob, and turning the knob on the GUI works, and inputting CC11 also works, *but* inputting CC11 is not reflected in the knob's position being updated in the GUI. (Unlike all other knobs, which do update when CC is inputted).

    I am loving these instruments, by the way, and have much to learn, but these two interface issues seem to have cropped up for me. Thank you.

  • edited April 2020

    You can remap it on the CC remapping 1 page:



  • Hi, thanks for reply, that's where I remapped it; and it works to remap vibrato rate from CC19 to my CC of choice, but tremolo rate stays on CC19?

  • Woops, sorry, this was a misunderstanding. Hm. I am not sure if or how it could be possible to set another CC to the tremolo rate. Maybe a SM team member will answer this. :)

Leave a Comment

Rich Text Editor. To edit a paragraph's style, hit tab to get to the paragraph menu. From there you will be able to pick one style. Nothing defaults to paragraph. An inline formatting menu will show up when you select text. Hit tab to get into that menu. Some elements, such as rich link embeds, images, loading indicators, and error messages may get inserted into the editor. You may navigate to these using the arrow keys inside of the editor and delete them with the delete or backspace key.