System Program 1.20 Bugs reported to Roland

6 May 2020, 13:34

Thread for reported or confirmed bugs in System Program 1.20, reported to Roland.

=====
Scene Banks do not correspond to assigned startup scene

System Program 1.20 added the ability to assign a startup SCENE other than 1-1. However, the bank selected at startup remains BANK 1, regardless of the startup SCENE selection. Say you choose 16-1 as startup. Press 2, and you now go to 1-2 instead of the expected 16-2. You expect the current BANK would match the selected SCENE.

Reported April 29, confirmed by Roland on May 1

=====
Tap Tempo does not work properly with iArp

There is a problem using Tap Tempo and iArp together.

Tap tempo appears to properly capture and display the tempo. But once Tap Tempo changes the tempo setting, the iArp now seems to start using the keypresses to also detect tempo. While the displayed tempo does not change, the iArp temp will jump all over the place, somewhat following key tempo as opposed to the scene tempo set by tapping.

Best demo: enable only part 5 to iArp. In this case you usually get a clean drum part as good backing. Set tempo via tap. Now watch the drum tempo jump all over the place in response to key presses - very psychedelic, but little music usefulness. Even with the part 5 receive switch off, it will change. If you adjust tempo via scene control, it will resume proper tempo, until you use the keys again.

This means you cannot use Tap Tempo in a live setting to follow a drummer while using iArp, for example.

Reported to Roland May 6.

Re: System Program 1.20 Bugs reported to Roland

12 Jun 2020, 11:21

Reported on 12th June 2020

1) The LFO Rate knob doesn't switch to Notes when the LFO is synced, it still controls the rate

2) Switching between LFO 1 and 2 doesn't reflect on the Pitch/Filter/Amp Leds, so when LFO1 controls Pitch and LFO2 controls Filter, the Leds don't jump to reflect that when switching LFOs.

3) MFX Matrix has Assign 0-3 instead of 1-4

Re: System Program 1.20 Bugs reported to Roland

19 Aug 2020, 19:36

Step Edit Data does not Export / Import Properly via Sysex

Cannot export and import step edit portions of scenes using sysex. The memory locations are shown in the Midi Implementation Guide. However,
Lines 1-3, 5-7, 9-11, 13-16 appear to export properly. When analyzed in a spreadsheet, they match the notes in the step edit grid.
Lines 4, 8, 12, 16 do not respond to the data request. (By shortening the data length from 01 02 you can get a partial dump, but by about offset 00 60 the data stops)

But, writing a good Line 1 back to the same memory location does not produce the same data - it is garbled, data appears on other lines, etc., even slowing the sysex playback down greatly.

This means that step edit data cannot be exported or shared.

Import does not show selected user locations

3 Sep 2020, 20:53

I have had several occurrences where importing tones did not show the selected locations.

In a normal tone import, sequence is:
1. select the sdz pack
2. select the desired tones from the sdz pack (checkmark)
3. Normally, the next screen will show the beginning of the blank locations selected by the X(m) for import, with the locations shown with checkmark.

On several occasions, step 3 instead shows U001-U004, already occupied, with no checkmarks. If I scroll down, I can eventually find the auto-selected locations, with checkmarks.

I suspect this occurs when the X(m) has to select non-contiguous locations for import. I have been keeping sound pack tones in low memory, but tones I am working on starting at 200, and experimental & test tones down from 256.

This was very confusing on 1.21 day, I kept thinking the tone import had failed. Once you know what is happening, is not hard to scroll down and find the checkmarks.

Reported to Roland on 5/27/20