i do not target anyone in particular here. I know there’s people who actually make real music out there. But i know there’s people like i describe, because i discuss with… i mean a lot IRL and i try to make them less angry and to understand why they make less music and spend they’re money in a constant flow… it doesn’t mean nothing at some point, gear, system take a huge amount OF TIME to learn, handle… But in a normal way you buy gear to make music at first. So yes i can said what i said. That’s just people we’ll read that, think about it and maybe some of those will have a personal reflection and take actions there (and if it’s help us i mean…). and i really think market keep that for a very excellent reason. Play to our frustrations and our demons is profitable in some way
NB: i perfectly understood too that i know nothing about the people’s life and people’s problems here and all is mixed… we all have our good days and our bad and I think it play a role on our content posts
This is something I was determined to do methodically too, it was going to be an appendix of a ‘how to get the best of PUM’ thread so that they didn’t just have this generally bad press … I agree there are certainly glitches and they are not just about usage constraints
Perhaps collate these observations here too (for example, there may be other threads) so the general community can see and discuss what we have all found and reported and perhaps discuss workarounds or steps to avoid
@sezare56: The workflow you describe is a valid one, for sure. But to me it sounds more like something possible in the studio, when one has time.
When I am performing live with the OT, I improvise with my modular and layer things in the pickup machines. In that context, I don’t have the time to save the sample, remember the name I gave it, change the machine from Pickup to Flex, and load that sample into the Flex. And what if I decide that I want to put another layer on top that sample again?
Hi, please, would you mind providing detailed steps on what exactly is not working there? On my OT 1.25H, at least having different scenes on a pickup track and switching & crossfading between them seems to work, also when storing & recalling projects.
AFAIK A+B is designed to sum to mono, what’s the observation ? are you using the midi note to start the machine, in which case this seems normal, perhaps your mixer setting are allowing you to hear a and b un-summed
Hi. I’m sure you’re woorklow is valid too.
I was thinking if there would be only one update point, I would choose AUTO SAVING RECORDS !
As you noticed, the fades implementation is bad.
They are exponential instead of logarithmic.
The advantage of Flex is that you can apply real-time plocks on Pitch, Rate,(the too first page parameters), while you’re playing. You cannot do it with other machines. Of course you can play it faster than the recording, if you disable time stretch, or reverse it. You can do it if you delay the playing.
You can overdub with Flex, recording Cue or a Track.
You can choose a specific recording time with Max and Recorder Trigs, with for exemple an 1/8 Scale, you can record up to 32 bars!
For me, the main advantages of Pickups are the ability to choose the first record length and tempo, and the working fades on overdub, to layer sound like pads.
With Pickups, as MonstreJumo said you cannot plock anything, and you loose you’re recording if you stop the Octatrack. Edit : so MJ, I didn’t understand you’re “problème”.
I don’t really remember but problem occurs to me when switching from one part to another, both having a pickup machine on same track. switching parts seem to disable the fader impact to scenes activation… I have made a thread some times ago about it, gotta find a link to it
It has to do with switching parts, and I guess my issue is not that the pu scenes don’t hold, it’s that they take over scene parameters assigned to same track on another part, but I think this is somehow related(in reverse) to the pu scenes not holding that others have noticed. There is more to it as well.
Here is part of a bug report confirmed by elektron:
“While switching from a pattern linked with a part with a pickup machine on a track, then switching to another pattern linked to a different part with something other than pickup machine on the same track(flex lets say), if the pickup machine isn’t running before switching, the new part/pattern will trigger the pickup machine loop from the old part instead of the assigned sample of the new part, even if sample locked and starts silent is selected. Also scene behavior of new part might still respond to the old pattern/parts scene. Workaround has been to make sure pickup loop is running before switching, muted if necessary.”
I have to say, since being involved in the development of a product that streams audio off an external memory source and involves realtime timestretching, I’m much more generously disposed to the OT’s developers.
Hi avantronica, you are of course right, “A+B” is the mono sum. I just copied the title of the support ticket, in which I made the same mistake. So it should read:
• If a Thru machine set to “A B” receives a MIDI note, it collapses from stereo to mono (#13615)
The bug does not happen with inputs “C D”.
Man i really think i am not the only one who would love to hack the firmware of the Octatrack.
The potential of getting Elektron to open source the firmware would be magnitudes compared to the neat and imo almost a little bit pathetic hype of the conditional trigs.
if you think it would be great to be able customize your OT to the fullest extend possible:
Any known efforts in this direction worth sharing?
Any suggestions how to approach this undertaking generally?
What you guys think about crowdfunder where we pay off Elektron to collaborate?
For now, please let us not talk about the worst case scenarios where we go reverse engineer/disassemble/rewrite OS from scratch etc… different topic?
Sure, with the right amount of resources it is possible to reverse engineer the OS, set up your own build infrastructure, replicate whatever proprietary tools Elektron might be using, add your own features, get the code to build and the OT to eat the binary. I just think that the amount of resources you would need to throw at this problem is huge and I very much doubt Elektron would just stand by and watch if their IP is violated, let alone endorse or even support such an endeavor. Exchanging a few graphics here and there yes, rerouting some calls to functionality not intended to be used, ok. Rewriting the OS without the infrastructure the original author uses - no way.
Well my thread got killed by the admins and merged into this one.
Therefore i assume partial ownership of this thread right here as a result.
Just to be clear, I dont hijack this thread, my thread got hijacked into this one.
So, lets continue:
Please contribute to this thread if you also embrace the idea of “freedom of use” and if you love the idea of open source firmware for e.g. your OT.
If you dont like the idea or you only about to discourage the undertaking, stay away from the thread, you are not helping. Thanks to everyone supporting the idea of an Open Sourced firmware for your Elektron hardware.