Request: can you replicate this bug?

Elektron Gear Octatrack
#9

Changing any of the settings on the memory page causes this bug for me!! This could have bad implications…

#10

i think if we all report this bug on elektron website,they might consider to fix it.

#11

I contacted support last night, this definitely needs fixing :thinking:

1 Like
#12

:+1:
me too

#13

Thanks all. In some ways it’s kind of better to know it’s a general bug and not my OT going rogue on me.

Elektron must surely want to fix this asap.

#14

Support got back to me saying the bug will be reported. Also, as a workaround, it would seem its faster to do Project>>Reload than to bring the samples back online individually.

1 Like
Running out of memory in project too fast :-( resolved thanks :-)
#15

Good tip. Thanks for sharing

#16

You still want me to test this sometime?

#17

You still want me to test this sometime?
[/quote]
Yes I’d appreciate it. I think I would have run into it on 1.25 E but I’m not sure. I haven’t yet rolled back and this would be a deciding factor. Thanks

#18

You still want me to test this sometime?
[/quote]
Yes I’d appreciate it. I think I would have run into it on 1.25 E but I’m not sure. I haven’t yet rolled back and this would be a deciding factor. Thanks [/quote]
I just did a quick test, was unable to replicate…

  • OS v1.25E

  • Flex slots 001, 002 and 003 using some random samples / loops.

  • Static slots 001, 002 and 003 using some random samples / loops.

  • Track01 - Flex : some parameter lock action, one sample lock

  • Track02 - Static : some parameter lock action, one sample lock, one trigless lock

My advice?

Replicatable bug. So do this…

  • Create a Project with 3 Flex, and 3 Static samples
  • Track 01 Flex
  • Track 02 Static
  • Throw down some trigs, plocks etc.
  • Save the project and archive it. (#1)
  • Replicate the bug.
  • Save the project and archive it. (#2)
  • Fix the issue manually.
  • Save the project and archive it. (#3)
  • Create an archive of the archives (#1, #2 and #3)
  • Send me the archive of the archives
  • ???
  • Profit
1 Like
#19

PS: I think I already know why this occurs, how it is caused, the reasoning for it, and how to fix it… but educated guesswork at the moment, send me the files and I can confirm or deny… :astonished:

1 Like
#20

Nice one Rusty. Worth investigating. Might take a little while - I borrow a computer for transfers etc. (hence not yet an
Octaedit customer!)

#21

No stress at my end… but if what I think is happening, is happening… then I know exactly what, why, how and how to fix it…

Boo… Hiss… You’re blacklisted.

#22

Seeing as Clancy is blacklisted, anyone else what to do the steps and send to me?

1 Like
#23

I can have a go if you like, shouldn’t take long. When you say ‘archive’ the projects, do you mean compress them to .zip files?

#24

Okay I went ahead and did it anyway…

https://www.sendspace.com/file/pq6rny

Every time the CF card is ejected, the bug is corrected so I had to recreate it a couple of times. I hope it reveals something…

#25

01 : First
02 : Enabled
03 : Corrected

?

#26

Yeah its a bit confusing, can you tell I did it in a hurry?
First - Samples loaded, couple of trigs placed, then saved.
Enabled - Triggered the bug, then saved.
Corrected - Corrected the bug, then saved.

#27

Yeah its a bit confusing, can you tell I did it in a hurry?
First - Samples loaded, couple of trigs placed, then saved.
Enabled - Triggered the bug, then saved.
Corrected - Corrected the bug, then saved.[/quote]
Not at all, makes perfect sense. Just me double checking before I run off and look in the wrong place… wouldn’t want a false positive.

#28

What I actually meant is using the USB disk mode corrects the bug, basically because it unloads the project then reloads when the CF card is unmounted from the computer.

1 Like