Lemondrop 1.2 Feedback

[Remuka]

Have been an issue with this firmware (machine stuck on rebooting forever), so for now downgraded to 1.1.2 and things are working fine.
Not sure if data might have been corrupted, will try again in the future.

[ukaeatech]

Ah no i didnt try that with the luminosity. Eventually after reading a bunch of other posts about this i freed up and formatted my most expensive sd card and copied everything across to that. No trouble since and yes gig was fine thanks ♡♡♡

[Callimero]

Hi
I did not look here a long time. Hey the new firmware is nice!

I stumbled on one thing: record with threshold. I need to keep record pressed now until a Signal with exceeds the threshold comes in? I thought one tap would arm and then wait? Or is it a preference somewhere?

Best,
Carsten

[Mindtraveller]

Have you reduced the screen luminosity in the menu to minimum? In my case that seemed to help along with a better power supply. Hope everything goes well with your gig. Fingers crossed

[ukaeatech]

Bit of a srs issue tho, i made loads of patches for my gig on saturday with the new firmware; today its only booting 15 times out of 20 and is regularly crashing back to the 'no sd card' screen during play. Stock sd; nothing changed apart from firmware; decent power supply; no errors on card. Errrr fuck haha

[ukaeatech]

Its a wonderful update, i'd hoped for trimming of recorded sample start n end same with the razz but rah what u've given us is absolutely class so hey ho

[Salioh]

It seems to me that in version 1.2.5 the representation of the first two waveforms of the LFO are reversed.

Using waveform 'Saw' (ascending form image) leads to a descending effect (with a suitable right-to-left animation for the LFO)
and vice versa waveform 'Rev Saw' (descending) leads to an ascending effect.

I suspect and hope that this is not meant to be and that I have not overlooked anything.

Test case with LFO1 modulating OSC pitch:

LFO 1:
Waveform: Saw -- the "ascending sawtooth"
Rate: 50%
Depth: 100%
Restart: ON

GR1 and GR2:
Level: 0%

OSC:
Pitch: 0%
+ Modulation 1: Source: LFO1; Amount: 100%
+ Modulation 2&3: Source: none
Level: 100%

Play a note, ascending pitch expected:
- Its sound has a descending pitch.
- On the HOME page the LFO animation shows a descending effect.

[Steve]

rockysmalls The bug, once confirmed, is that the playhead disappears at certain density/size settings. This has nothing to do with file size or length. The lemondrop only loads the first 30 seconds. This is not incidental; it is designed this way. As for trim, that should go on the wishlist. And I think you'll find a wish there to +1.

[rockysmalls]

@Rlorjsg62vha Make sure you are using 1.2.5.
I see @rockysmalls is using 1.2.5.

First, I can confirm that the granular oscillators are only loading the first 30 seconds of your file. I created and tested four files to confirm this.

I believe some of what you are seeing has to do with how the Density and grain Size parameters interact with one another. However, I can see a different behavior in 1.2.5 using rockysmalls steps. I need to do a bit more research into our granular engine to determine the next steps. I will log it for future consideration if it is considered a bug. Thanks for reporting.

FWIW, this is from the manual.

Density When Beat Sync is OFF, the density controls the number of grains played per second. You will get about 1 grain at the lowest end every few seconds. At 100%, you will get the maximum overlap of the grains. 0% - 100%

Grain Size The length of the small segments of the WAV file that will be played, ranging from about 20 ms to about 1 second. 0% - 100%

thanks for looking into it Steve, personally, on further pondering about it, apart from the visual aspect I think it’s definitely a bug for the simple reason that it means when using files longer than 30secs you will end up with reduced resolution in the position parameter, you know , maybe only getting 45% of the possible 100% resolution when LFOing SEQing or XYing position etc, ( i may be misunderstanding the parameters resolution here ) of course the workaround would be to NEVER use files longer than 30 secs .. which is ok if yr loading from computer but not when recording directly into LD as is my workflow. I guess this brings us around to the subject of “SAMPLE TRIM” capabilities , wink wink nudge nudge ... even an auto trim to first 30secs would be cool , especially if it saved the trim as a seperate file?

[Steve]

@Rlorjsg62vha Make sure you are using 1.2.5.
I see @rockysmalls is using 1.2.5.

First, I can confirm that the granular oscillators are only loading the first 30 seconds of your file. I created and tested four files to confirm this.

I believe some of what you are seeing has to do with how the Density and grain Size parameters interact with one another. However, I can see a different behavior in 1.2.5 using rockysmalls steps. I need to do a bit more research into our granular engine to determine the next steps. I will log it for future consideration if it is considered a bug. Thanks for reporting.

FWIW, this is from the manual.

Density When Beat Sync is OFF, the density controls the number of grains played per second. You will get about 1 grain at the lowest end every few seconds. At 100%, you will get the maximum overlap of the grains. 0% - 100%

Grain Size The length of the small segments of the WAV file that will be played, ranging from about 20 ms to about 1 second. 0% - 100%

[rockysmalls]

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.

yes, the good news is it’s not so much of an urgent ‘fun killer problem’ as it stands, but it will be a huge PITA if you like to use the first section of some 2 min or much longer recordings made on the machine. not audibly of course , just in terms of seeing what’s happening with the grains play indicators as you change 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.

[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.

[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

[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%