Looper X Pre-roll and Recording Length don't work until Quantize parameter is toggled.

Quad Cortex Bug Reports
1

I think I’m among the few on here that depends heavily on a looper – this issue causes a lot of problems when I perform.

CorOS Version: 4.0.0

Describe your issue:
Any preset with Looper X where I’m trying to use Quantize, Pre-Roll, and Recording Length features, the Pre-Roll and Recording Length parameters have no effect until I change the Quantize value from the original value in the preset.

Steps to reproduce your issue:

  1. Create a preset with Looper X Quantize = 4, Preroll = 1 bar, Recording Length = 2 bars and save.
  2. Go to a different preset, then back to this preset.
  3. Hit record in Looper X - there will be no pre-roll, and the recording will not stop automatically after 2 bars.

I expected this to happen:
With those preset setting, I expect a pre-roll of 1 measure, then the Looper X will record 2 measures and start playback automatically. If I toggle the Quantize parameter (say, change it to 3 and then back to 4), things work as expected.

I have tried the following things:

  • Here is a video of the issue: https://youtu.be/T5CMKF5TE3E
  • If I toggle the Quantize parameter to a different value and then back, the Pre-roll and Recording Length functions work as intended.
2

This is ABSOLUTELY an issue. I’ve run into this live and can no longer use the looper at my shows until this is resolved.

Thanks for bringing this up.

1 Like
3

Are we the only two people experiencing this?

1 Like
4

I’m bothered by it too!

1 Like
5

Thanks for letting me know that you guys also experienced this (and that it’s hindering your performances). I sent an email to Neural a couple weeks ago, but no response.

6

Please check your spam folders etc., and please copy network@neuraldsp.com when emailing support to ensure they receive your email. If you haven’t heard anything back after 48hrs, please DM your contact details and I will forward directly to support. Everyone else, please do the same and email support about the issue so they can log it and get to providing a solution.

7

Thanks. Nothing in my spam folder, but followed up with support and the network email address you listed.

1 Like
8

It’s the same for me here! Thanks for sharing that workaround! I always thought I was too stupid for that looper to get it to work because I remembered it working correctly but later it didn’t work as expected. Drove me away from the Looper X several times now. At least now I know the workaround!

Please, NDSP, fix this bug!

1 Like
9

Can’t you just forward issues like these to NDSP if several people are experiencing a bug?

I mean, is it really company culture to have your customers report issues several times in different places?

Is it really necessary for everyone to send a separate mail about the same issue?

Sorry, but NDSP is already a little behind with their community after years and years of not delivering QC plugin compatibility for most of their catalogue, although it was promised before the unit was even released.

If a new issue is seen by someone from that company, it should be logged and added to the list of bugs to fix. Don’t you think it should be that way? Don’t you think NDSP should be happy that people even report these issues in their forum? Bug reports are worth a lot!

All the best for you! Maybe you can make an extra buck or two for handing over this advice to the company and taking care of that matter in the future.

10

This person doesn’t work for Neural lol

11

Minor update: Neural did get back to me a couple days ago and said they were unable to reproduce the issue. They asked me to update CorOS 4.0.1 and see if I still experienced the issue, which I still did. Now that several people are experiencing this, maybe it will be easier for them to fix.

ALSO: I started a separate thread to see if we can pull together users who uses the LooperX block for live performance and what improvements would be most beneficial, so please check in there: