'P1 dub aborted' error

sezare56 · 2017-05-08T01:07:12.064Z

New project, to be sure there’s no lfos, pitch changes…

Open_Mike · 2017-05-08T02:35:28.228Z

It will clear the buffer and all associated attributes, if the tempo has been changed it will reset it, just a troubleshooter… I’ve had it resolve issues with recorder buffers here and there…

Analogic · 2017-05-08T02:54:51.914Z

Interesting, new project worked (good tip!), but I still can’t get my original project to work. No lfo’s, pitch changes etc ANYwhere… buffer cleared a bunch of times… anything not yet mentioned that causes this error? It’s a 48 step pattern, qrec and qpl both set to plen… no slave pickup… also tried really short patterns that couldn’t possibly hit the ram limit.

Open_Mike · 2017-05-08T04:03:32.240Z

Could you have a scene activated with plock on pitch or lfo?, you could try with scenes deactivated. If you have a part saved you could try a part reload, if not it’s a good idea to save one once it’s working for times like these…

Analogic · 2017-05-08T05:22:43.863Z

That just solved it! I cleared both active scenes and it seems to have eliminated the error. I might have had an old LFO assignment in there. Thank you all!

Open_Mike · 2017-05-08T06:07:42.361Z

Sweet, the lfo’s default to pitch so a lock on lfo dep can do it…

Open_Mike · 2017-05-08T16:40:48.599Z

I’m gonna keep this one in the back of my brain because it seems like it will happen if you have a scene set to lfo dep targeting some parameter, but then you clear the lfo page and it targets pitch again…
Or if for some reason you set the scene on lfo dep but then save your part before adjusting the lfo target and later do a part reload…

Analogic · 2017-05-08T16:52:46.563Z

Totally! I forsee bumping into this issue again for sure.

Open_Mike · 2017-05-08T17:01:59.644Z

I’d say feature request: have lfo page default to something other than pitch when using pickups, but it’s probably too late for that…

Gaia.Tree · 2018-03-19T00:29:55.852Z

Now I start running into this dub aborted shit all the time. Not the biggest killer for my beatbox looping workflow but surely annoying. Maybe Elektron could help us loopers out in a future update. Gathering my info’s on this but guessing my habit of pitch changing on my loops is the culprit for most of my aborted messages

sezare56 · 2018-03-19T00:40:16.613Z

Gaia.Tree:

Now I start running into this dub aborted shit all the time.

Even with OT only?
OT master ?

Edit : yes, avoid pitch with Pickups overdub.
You can use pitch with Flex machines, playing Pickups recordings.

sjvl · 2021-05-05T18:10:44.961Z

Ok following up on the experiences here: i was getting p1 dub aborted in a “save as new” project.

I still had the error even with no scenes on pitch or LFO’s.

I changed all three lfo destinations from ptch to something else not pitch related…all good.

Supercolor_T-120 · 2021-05-06T00:24:52.433Z

I have literally never gotten pickup machines to work reliably with external clock from anything, no matter how stable. But I’ve also never had this error happen wuth the OT as master in over 3 years

mpiecora · 2022-02-26T20:35:36.017Z

If you have MIDI clock receive and TRANSPORT receive turned on you will have the ABORT error.

Supercolor_T-120 · 2022-02-26T22:42:20.428Z

Transport recievedoesn’t cause any issues for me, I’ve been suing external transport control with pickup machines for years and never had a problem. External clock never works.

JWA · 2022-03-22T21:49:57.351Z

This was driving me nuts. Tried everything, midi clock, LFO pitches etc then just before giving up exasperated, spotted the slider was very slightly not against the stop at A. Found I’d set up a B scene for +1 tone, as soon as I pushed the slider fully towards A, everything worked fine, no dub abort messages.

mpiecora · 2022-04-01T17:28:05.608Z

I guess the transport part shouldn’t matter anyway, ha. Definitely does not work with external clock - sadly that kills it’s usefulness for most of my ambitions.

Cozyvandal · 2022-12-21T17:07:33.421Z

Just to add here as it is perhaps not explicitly clear from comments on this thread: changing the project/pattern tempo after recording to a pickup machine will give the ‘dub aborted’ message. Once that pickup machine audio is erased it will dub again (at the new tempo). Kind of a shame.

bgEN · 2023-02-04T15:34:53.993Z

spotted the slider was very slightly not against the stop at A.

Holy crow, sanity saved. Read your comment, walked over to Octa, sure enough, this was exactly my problem too.

JoyrexJ9 · 2024-10-27T16:26:16.854Z

'wise fwom your gwave etc

After seven years of OT ownership I thought I’d give pickup machines a try…
I’ve got the OT as a sort of sub mixer for four mono synths, and using the DT2 as the main brain; it’s the master clock + transport and sequencing these synths via MIDI

I thought it might be nice to capture 4 bar phrases and layer them into things, “hey maybe I should finally try pickup machines”
But I’m hitting the same dub aborted error

Is this all due to the OT being the slave for clock?

Are pickup machines even the right job for this? Being as everything is MIDI synced and I want loopable 64 step recordings, should I just stick to regular recording buffers, rec trigs, and flex machines for this?