Octatrack OS 1.30B is here

News
#57

Epic win. New data point: when items come down from the website, it means the metamorphasis has begun and gifts will drop the next day!

Thanks again Elektron for you guys supporting Octatrack as an ongoing evolving instrument.

3 Likes
#58

its a good day. happy Octatrack

#59

I don’t know, I think I was on 1.25e and I didn’t have this bug before.
“Reconfiguring the flex memory would make it impossible to trigger flex samples, unless a manual reload of the samples was invoked.”
so did they fix it for flex samples, but not static samples? Or is it a new bug? :slight_smile:

2 Likes
#60

Yes.

Have to say / when I read the changelog entry “Reconfiguring the flex memory…” I thought they had fixed it at last! But they’re talking about flex slots.

Pretty sure the problem was always with static slots !?!

#61

I also made this observation :joy:

1 Like
#62

My party mood’s already over with this update, grrr, no real pickup love, still this :zonked:


3.5 years after this

takes the buzz right off, ah well, next stop TRCs

5 Likes
#63

Great update! Thanks Elektron, my Octatrack is happy after being fed this update :slight_smile:

#64

ThanksEgods
ThanksEgods.jpg1256×708 79.8 KB

But you ruined my social and work life !

IhaveTRC
IhaveTRC.jpg1256×708 173 KB

13 Likes
#65

Annoying, I tried playing around with PUM again last night and gave up, that and don’t get me started on the clicks… unbearable. Really hope the guys at Eleccy sort this mess out

1 Like
#66

Just thought i’d check before upgrading.

So on OS 1.25H if you make changes via CONTROL>MEMORY, like switching dynamic recorders off/on it mutes all tracks whether static or flex. Or to be more accurate it mutes all SLOTS, static or flex.

Every single slot needs to be opened in the editor to bring it back to life.

It’s totally painful so was really hoping this would be fixed. Let’s see…

Just double checked the suggested workaround “reload the project” which alone isn’t very helpful. However - save and then reload seems to work…

Anyway I’m now caught up in the conditional mania - so looking forward to trying it out for that right now. Bugs another day :slight_smile:

1 Like
#67

No I want to find a bug !
Of course not, TRCs ! :thup:

1 Like
#68

The second born of my OT

1 Like
#69

sadface.jpg

#70

You and @dustmotes thought like me that recordings where still there after reboot ?

2 Likes
#71

Yes sir

1 Like
#72

same :slight_smile:

#73

I had noticed with great regret that the recording was no longer there, after restarting :confused:

#74

I did, too.

#75

Being a sliced buffer devotee I thought it meant what it does, and I’m quite happy about it…:boom:
I’m oddly glad it didn’t work for awhile because it got me to use start points which I now prefer, they work much better with bpm changes and timestretch…
Looking forward to checking out slices again…

For anybody wondering, you can slice up a recorder buffer sample that you made, clear the recording, and the slices are still there. You can target these slices on one or several flex tracks. Now when you record to the buffer it is sliced already and the sliced track is played back in real time(as long as your not trying to play a slice that hasn’t been recorded yet :open_mouth:).

After powering off the OT and turning it back on, the emtpy recording buffers should still be sliced.
This broke in os 1.25H, now it should work again…

10 Likes
#76

Thank you Elektron :slight_smile: OS 1.30B :slight_smile:
for your continued updates and maintenance of Octatrack.

2 Likes