Long samples get faded away!? Help!

[Satanoid]

I have a gig tomorrow and I have no idea how to have longer samples stay playing when I press the pads. ATM they play for like 5-10 seconds and then fade away. I tried to wiggle the decay and attack, but it didn't go long enough.

[Seiishu]

Have you ever solved this? I am running into similar problem. Whenever I try to load new sample into a spot where some previous sample was before, it does not reset filters/effect settings to default, but keeping old settings from the old sample instead. Really annoying, especially I can't find any option where to reset everything to default and start clean. Is there a preset to wipe out all samples and reset effects to factory settings, so we can start adding instruments from scratch?

I know there is D.I.Y Sample Templates Vol.1, but they already have samples in and almost every sample has filters applied. For example, I am trying to load 4 seconds long synthesizer pad loop into one of the instrument spots, and just like in your case, it starts playing but after just one second it starts fading out. It also has some effects applied and it doesn't sound anything like the original WAV sample I wanted to hear. I tried playing with knobs resetting them all to default position, but I never managed to get exactly the same sound like original WAV.

Can someone from Arturia team help with this please? How to draw their attention to this thread? This is really slowing down our productivity.

Thanks in advance!

[ben arturia]

Max sample length is 13s.
But the fact that your imported sample has not the right length is a bug.
Have you tried to load the basic 80's Studio Drums BD then load your own sample on it. This could be a workaround
Anyway thanks for your bug report !

[Seiishu]

Thanks for your reply. I also asked about this in the following thread: http://www.arturia.com/evolution/smf/index.php?topic=82080.0

Creating new project from scratch helped in my case.

[ben arturia]

No problem. But if you want to begin with a factory project and only change one instrument in the set you should follow the workaround in order to have a reseted inst.
Cheers

[Seiishu]

Thank you Ben! Message taken, and sure it's super useful until there is a permanent fix in upcoming software update.

While we're at reporting programs bugs... I know I should start a separate thread, but if I post it here, it will probably catch your attention easier and a lot faster faster. I hope forum moderator can move this message into new thread later (for easier search purposes in case it could help someone  else in future).

It happened once and I didn't want to report it since I though it wasn't really a bug, but maybe rather something I did on my end. So, it happened for the second time last night... I can't recreate this problem since I don't really remember what exactly I did to cause this, but I remember I was trying to record my pattern by live playing using bottom pads, not using sequencer mode. First big pad (number 1), locked itself and it was completely non-responsive to touch (on my SparkLE hardware controller). It wouldn't produce sound, it wouldn't even light up when touched. All other pads would work perfectly fine. I tried touching same pad in my software and it worked perfectly fine, producing sound and lighting up as it should, on both, software and on my hardware controller. Every time I touch pad number 1 on my computer, it produced sound and lit up the LEDs on both, software screen and SparkLE. I tried loading completely different project - no help. Pad number 1 still non-responsive. I tried pressing INT key on software to disconnect and then reconnect my SparkLE - still same. No matter how many times I repeat that, it wouldn't help at all.

The only thing that would help is physically disconnecting SparkLE by removing USB cable, let it alone 1-2 seconds, and then reconnect everything. I am using direct USB connection to my i5 machine with 16 Gb of RAM and very good dedicated sound card, with plenty of empty space on my hard drive.

Again, unfortunately I can't recall what exactly I did to cause this behaviour, but I remember I tried recording live and pad number 1 "locked" itself while I was using it... hitting it couple of times pretty fast to record kick drum sequence (but not too hard definitely, I love my SparkLE).

Regards.

[Kevin]

Hi Seiishu,
the best thing to do is to report these issues in the beta test email so Ben will enter it in our bug tracking system.

thx
Kevin

[Seiishu]

Hi Kevin, and thanks for your respond.

But this has nothing to dowith Spark 2 Beta. It was happening on my machine with 1.7.2 as well. Guys at the store said it's clearly a hardware issue. I tried it on my Mac OS X, latest version as well.

Something is bugging my pad #1.

Thanks in advance

[Kevin]

Do you have a support ticket number?

[Seiishu]

I have two tickets. Just sent you personal message.
Did you get it in your inbox?

The second one is regarding the replacement SparkLE controller and the licensing question. Store will get a replacement this week, and I was just wondering can I keep using same software licence if I just receive new hardware unit?

They might not give me new software since I already registered this current one.

Thanks.

[Kevin]

I am not very sure about these license issues.
I will let the support answer you.
As I wrote in my PM they will answer you soon.

[Seiishu]

Also I'd appreciate if someone could try doing what I was doing in my video (vimeo link is posted two replies before this one) to replicate pad#1 locking itself. If someone else could do it, then it might be trouble in Spark software too... Since I never tried using controller in any external DAW to see if this pad#1 would lock itself there too.
If anyone is willing to help me by testing, they need to use either Spark 1.7.2 or Spark 2 beta. It happens in both on my end here.

Thanks in advance.

EDIT: OK, I just tested my controller in Ableton Live 9, although demo version. Same thing is happening, pad #1 lock itself after just couple of taps on it. So it's definitely a hardware issue, not the Spark software issue.

[Terrym]

Hi this is a hardware issue i cannot repeat this issue with my equipment.

terrym

[Seiishu]

Thank you Terry. Yes, I also confirmed it trying it in Ableton. Pad #1 behaves completely crazy. When I switch my controller to MIDI mode, you need to press all pads just once to make LED light go on, and only once to make it off. Pad #1 starts flickering like crazy, and after couple of seconds it turns itself on, but it stays on even if I press it again to turn it off. It locks itself for some reason.

I am getting new controller and hopefully it will arrive to the store soon.

Thank you so much for taking your time to test it and help me with this. Greatly appreciated Terry.