Percussa Home / Shop / Contact /

After playing with sampler, no sound output modules work

SSP Bugs
#1

Bug description (state clearly and simply): after playing with sampler module in a chain totally unrelated to my other patches, the sampler not only doesn’t respond to various patches that should logically work it, I then get zero sound from my other output modules that are in totally unrealated chains. I reset the SSP, and didn’t save the sampler chains, and the original chains work perfectly fine once again.

Steps to reproduce (use numbered list):

  1. make a working chain of sound unrelated to a sampler
  2. make an unrelated sampler, and plug it in various ways (patch it various ways I mean)
  3. keep testing the outputs until it cuts them out.

Software version (blank if unknown): original

Type (major or minor): major, audio stops working, but you can see the audio coming in and going out in the oscilloscopes.

#2

Can you provide more details about what you loaded in the sampler and how you patched everything together? I am not able to reproduce it the way you describe it.

#3

no I can’t. I haven’t messed with the sampler. It’s just kinda annoying to use honestly. It needs help. <3 you @bert no offense meant.

#4

I am now seemingly getting this exact bug. I had various unrelated chains working fine, then trying to set up a sampler being externally triggered seemed to be working on screen but no audio going to pmix and on to output. Then channel 1 and 2 of the output started not working with anything i switched to 3/4 it worked temporarily but now it seems that also isn’t working even though there is a signal going to it. Very similar to what is being described in the original post.
Not sure what to do I’m in the middle of an important patch tried reloading the preset didn’t do much other than the problem varies slightly. On the output p screen the line that is normally in the middle or is a waveform disappears. I tried a separate output module for this sampler chain same problem but now its happening on the original output module too that was working fine. So it’s effecting output and I think also pmix as sometimes signals either aren’t reaching pmix or aren’t going out the main output for no reason.
Any ideas I’m kind of stuck?
Thanks

#5

yeah, Ive had this once or twice… (though its been a while since Ive had it)
and indeed its always been with SAM, and often when I change samples.

unfortunately, its very difficult to understand whats going on , so to raise a bug that would actually be ‘fixable’

I’d need to dig up my notes about the issue, but from what I remember it kills a particular ‘chain’ of modules, and to get around you have to remove all of the modules in that chain - then suddenly it will spring back into action.

… or something like that, honestly, it was about 6+ months, since I last looked at this.

but as I say the ‘issue’ is, whilst (for me) it always starts in SAM, as mentioned it spreads to other modules. so even if you remove SAM, the affected modules still go silent.
my assumption is, somehow, SAM does something that kills the DSP core it is on… or its passing invalid audio data, that causes issues downstream.

however, honestly, that is not enough info to actually debug the issue with…and I wasn’t able to reproduce it (in a simple enough patch) to get enough info to help debug the problem.
so, whilst a simple bug to describe, its going to be very hard (at this stage) to attempt to find a fix, since we dont know where to even start looking.

btw: I assume you are using the latest factory firmware version on the SSP.

#6

Thanks for that. Yes i have the latest firmware. I think I had tried deleting that sampler and trying another one but im not sure it worked. So you reckon if I delete that subchain of sampler (which was going into a new pmix) it should rectify everything else? I’ll give it a go and see where we are. Thanks a lot. Good to know you’re aware of it at least and it’s not a completely random problem

1 Like
#7

any news on this bug? I also encounter it a lot. maybe i missed a firmware update where this bug had previously been fixed?