Lemondrop 1.2 Feedback

[rockysmalls]

URGENT! with firmware 1.2.1 and 1.2.2
SEQ : there seems to be NO recall of a sequence (lfo) from a saved preset . this is a big one!! whatever settings you make it just reverts back to 16 blank steps with one anamolous step containing data!? this happens as soon as you do a ‘save as’! as well as when recalling a saved preset using SEQ steps as an LFO etc.
thanks for your attention.

p.s. i’ve sent a mail to support noting this and a few wav preview glitches, just to clarify: this is a great great update and much appreciated, shame i chose this moment in time to start getting into modulating with the SEQ lfo bit! whoops! sorry if i’m sounding a bit impatient.

[Lucas]

You can revert firmware in the meantime while we look into this bug.

[Steve]

URGENT! with firmware 1.2.1 and 1.2.2
SEQ : there seems to be NO recall of a sequence (lfo) from a saved preset . this is a big one!! whatever settings you make it just reverts back to 16 blank steps with one anamolous step containing data!? this happens as soon as you do a ‘save as’! as well as when recalling a saved preset using SEQ steps as an LFO etc.
thanks for your attention.

p.s. i’ve sent a mail to support noting this and a few wav preview glitches, just to clarify: this is a great great update and much appreciated, shame i chose this moment in time to start getting into modulating with the SEQ lfo bit! whoops! sorry if i’m sounding a bit impatient.

I received your email and have responded. Thanks for your patience while we address this.

[Rlorjsg62vha]

Hi,

I'm wondering if this is a bug with the 1.2.2 firmware or expected behavior.

1. Load a factory sample in GR1 (I used Oboe).
2. Verify sample loaded in GR1 is heard. I pressed key C3.
3. Make sure volume of GR2 is set to 0% and load a different factory sample.
4. Press C3 key again. This time the pitch of the sample in GR1 will be different.

When a sample is loaded in GR2 (even if GR2 volume is 0%) it seems to affect the pitch of the sample in GR1.

The behavior does not occur if a sample is loaded in GR2 first.

Is this expected behavior?

[Rlorjsg62vha]

I believe this issue predates the version 1.2.2 firmware.

If filters 1 & 2 are set to off should changing the mode of filter 2 (serial, parallel, per osc) have any impact on the sound?

In my case I have noticed that even when both filters are set to off if I set the mode of filter 2 to parallel the overall sound is significantly louder.

Is this expected behavior?

[pgnnwy]

I'm not sure this can be right, because I would have thought someone would have noticed it by now, but I was just playing around with v1.2.1 and noticed the LFO shape setting isn't doing anything (both LFO 1 & 2), even though you can select different shapes it seems to only ever use a triangle or possibly sine shape. I just installed 1.2.2. and the issue is happening there too.

[Steve]

Are you retriggering notes after you change the LFO waveform? I'm not seeing this. If you set RESTART to ON, set a slow rate and 100% depth. Trigger notes and watch the gauge on the dashboard. It and the resultant audio should match.

[pgnnwy]

Are you retriggering notes after you change the LFO waveform? I'm not seeing this. If you set RESTART to ON, set a slow rate and 100% depth. Trigger notes and watch the gauge on the dashboard. It and the resultant audio should match.

I knew this was going to be user error So on re-triggering notes the new shape is applied. Can't believe I didn't try that last night whilst I was trying to work out if this was a defect or just me.

This has made me realise that you can have an LFO per note/voice tho, which is brilliant.

[philxbx]

Is anyone else having a problem saving patches with sequenced notes? Mine saves the patch, but not the sequenced part?

[Steve]

There is a fix coming that addresses this issue.

[Thisistheway]

In v1.2.5 on the FX1 screen, the name of the "Flanger+Dist" effect is still shown as "(null)" in the title bar.

[Steve]

This has been reported and will be fixed.

[rockysmalls]

Unless I’m mistaken I think there is a significant bug in this Beta v 1.2.5 , i’m using a fixed play head with small grains ( high density ) and when I am scrolling/dialing through most sound files from the presets folder ( which i’m presuming are all kept under the 30 second limit ) the play head disappears at say 30% or some other point along the waveform view , all except the very smallest sound files don’t seem to be complete in the buffer , making me think this version isn’t using the full 30 seconds for some reason?

[Steve]

At a quick glance, I don't see it.

Please provide one of the following:
1. more detailed parameter settings for the granular oscillator in question
2. a preset that produces this result
3. a short video that shows the issue and addresses #1

I'm happy to look deeper with more info.

Thanks

[Rlorjsg62vha]

I am seeing the same behavior that Rockysmalls is seeing. For example when I load the sample AmajorAscent the play head disappear and the sound stops when the position is >85%. When using the sample CS80Ringmod the play head disappears and the sound stops when the play position is >45.3%. When using the sample EbowKotoBFW the sounds stops at >67.4%

In the above cases Density=35.4% and Grain Size=41.0%

[rockysmalls]

At a quick glance, I don't see it.

Please provide one of the following:
1. more detailed parameter settings for the granular oscillator in question
2. a preset that produces this result
3. a short video that shows the issue and addresses #1

I'm happy to look deeper with more info.

Thanks

further investigation: I don’t think, as i previously stated that the full 30 seconds isn’t being used, it’s actually just that the waveform drawing is showing the whole of the file and the cursor disappears when it reaches the 30 sec point , eg: with a 40 sec file the ‘fixed’ play head cursor will disappear at the 75% mark.
re: buffer/ waveform view , i can see from using my own recordings which i tend to halt at around 30 seconds BUT are usually a second or two over .. that the buffer is using all 30 secs of the file BUT the wav drawing is of the whole wave length including the few seconds overhang , has this changed in recent betas? , i feel sure i remember it only showing the first 30 secs previously? more useful/ detailed if it does , long files would lose a lot of ui room to adjust accurately.
i don’t think a specific preset is needed , just set density to Zero , grain any size, no jitter, window etc etc , and play to FIXED , then scroll the single play head position using the lower dial,, OH , but you will need a file that is a bit longer than 30 seconds to see it , so either record a dummy one in the machine or I guess i can go back and try and identify a preset wav that is over 30 secs.
My confusion was because I didn’t think you would include any preset wavs that were over the 30 sec limit ?
the question is : is the drawing of ALL of a longer file deliberate, is it legacy behaviour and i’ve just not noticed it, or is it a small bug introduced in recent betas?.
if it’s deliberate , I’m not sure i’m in favour of it. only the used section of the wav should really be visible in the edit window ... of course IT WOULD be great to see the lengths of ( specifically recorded ) wav files when scrolling through them in the folders view.


oh, and https://forum.1010music.com/member/18117-rlorjsg62vha has helpfully mentioned several preset wavs that fit the bill above

[Steve]

I am seeing the same behavior that Rockysmalls is seeing. For example when I load the sample AmajorAscent the play head disappear and the sound stops when the position is >85%. When using the sample CS80Ringmod the play head disappears and the sound stops when the play position is >45.3%. When using the sample EbowKotoBFW the sounds stops at >67.4%

In the above cases Density=35.4% and Grain Size=41.0%

Thank you. Generally, I need more details than a few parameters.

[Steve]

further investigation: I don’t think, as i previously stated that the full 30 seconds isn’t being used, it’s actually just that the waveform drawing is showing the whole of the file and the cursor disappears when it reaches the 30 sec point , eg: with a 40 sec file the ‘fixed’ play head cursor will disappear at the 75% mark.
re: buffer/ waveform view , i can see from using my own recordings which i tend to halt at around 30 seconds BUT are usually a second or two over .. that the buffer is using all 30 secs of the file BUT the wav drawing is of the whole wave length including the few seconds overhang , has this changed in recent betas? , i feel sure i remember it only showing the first 30 secs previously? more useful/ detailed if it does , long files would lose a lot of ui room to adjust accurately.
i don’t think a specific preset is needed , just set density to Zero , grain any size, no jitter, window etc etc , and play to FIXED , then scroll the single play head position using the lower dial,, OH , but you will need a file that is a bit longer than 30 seconds to see it , so either record a dummy one in the machine or I guess i can go back and try and identify a preset wav that is over 30 secs.
My confusion was because I didn’t think you would include any preset wavs that were over the 30 sec limit ?
the question is : is the drawing of ALL of a longer file deliberate, is it legacy behaviour and i’ve just not noticed it, or is it a small bug introduced in recent betas?.
if it’s deliberate , I’m not sure i’m in favour of it. only the used section of the wav should really be visible in the edit window ... of course IT WOULD be great to see the lengths of ( specifically recorded ) wav files when scrolling through them in the folders view.

Thank you. This is a slightly different issue. I will look into this based on your new info. I ask for a preset because there are a lot of parameters for the granular oscillators. I like to see everything when looking for issues like this one. It is sometimes easy to overlook a parameter that may be the culprit, or lead to thee cause of the problem.