how to give the sampleplayer prev/next buttons?

[AngularMomentum]

Thanks! For the end user I got it solved, but creating new presets in SM in a new created slot gives problems, then the selector needs to be "touched".

[aliasant]

Thanks! For the end user I got it solved, but creating new presets in SM in a new created slot gives problems, then the selector needs to be "touched".

Isnt it so that it just needs a trigger somewere?
Use a 1ms delay with a timer to delay a single trigger from some were and send it in to the selector?

[AngularMomentum]

Just trigger it into the green Int input in the selector?

[aliasant]

Just trigger it into the green Int input in the selector?

O I dunno. Possibly the output from the selector. I could help better if i had the osm but you should be able to find the place. Just set the osm in the state were it needs that "touch" then send 1 trigger do different places were you think it should go. Test 1 place and if it doesnt work set the selector in that state again and test somwere else till you find it.

[AngularMomentum]

OSM is posted...just a page back.

[aliasant]

Im looking at it and as usual in SM its trigger hell.

I placed trigger counters everywere. Then I loaded 1 new wave file and went back in to see what triggers were sent and were... Its just to many of them
string splits usually creates an additional trigger and if you use two stringsplits 1 trigg will quickly become 4 and so on..

Ideal would be to have all trigger counters report only 1 trigger. That would mean its a fast schematic with no unneccessary computations going on.
My suggestion is to build this from scratch and make sure theres only 1 trigger being sent out from each module.

Or you could try to optimize this one. I started and got most down to 1 trigger but I havnt found the smartest way to save the current wavefile for that preset.
Looked some more and I still say build a new one.
I think it will be quicker, smarter and more effective in the long run.

I did have something similar in my drummachine. I have 12 pads that all shared the same wavefile loader so I used arrays to save all the locations and wavefiles. Never got it to work 100% though but I didnt bother. I am gonna use the file list thing we made instead. Faster and simpler and very reliable.

Sorry for not helping much.

[aliasant]

I think I solved it.

I realised you were working on the selector from the tapeplayer or?

Anyways. i had a newer version of that that I optimized and it worked. almost. There was a problem with a trigger of course.
After the "Find the wavefile" thing there is an integer s&h that received the wrong trigger. It actually received the trigger before it had even found the file so it would always output the wrong integer. I fixed that.
Seems to work good now and uses less triggers.


Update: Ooops.
it still doesnt quite work. It remembers if you have loaded a file from scratch but not if you change that slot with the selector.
This selector doesnt have its own presets. Maybe it needs to. Ill have another look at it.

[aliasant]

Ok. This one actually works.


Pfeew.....

[AngularMomentum]

Yeah I think it needs that some sort of...I am now trying to read everything you did in the schematic and compare that with what I have in KickLab...If it uses less triggers, then it is all good!

[AngularMomentum]

Looks very neat...I noticed indeed the same behaviour when the selector selects a sample, but the rest looks very solid.

In your example, the string array also ouputs an empty string on the end of the list, you can see this when using the drop down menu...one empty slot.

[aliasant]

Looks very neat...I noticed indeed the same behaviour when the selector selects a sample, but the rest looks very solid.

Hmm. Maybe I missed something what exactly is happening that shouldnt?

In your example, the string array also ouputs an empty string on the end of the list, you can see this when using the drop down menu...one empty slot.

Yes. Right. Forgot that one. I guess the list needs a split to get rid of 2 extra invisible characters. Something I think came in one of the beta 1.3's?
I also think you can get rid of moore triggers but thats a chase I dont like to do right now ;9 but it could probably save some un neccessary computations and speed things up.

[AngularMomentum]

It still has the error when hitting the back preset button...load a sample, preset up, then down, and it loads the wrong one. This is a real bugger

[aliasant]

It still has the error when hitting the back preset button...load a sample, preset up, then down, and it loads the wrong one. This is a real bugger

I cant reproduce that here. Works like it should....
These are the steps I took.

I was currently on preset 5 so first thing was to step down to preset 4 using the down/back arrow.
Then I hit load and loaded a new sample.
Then hit preset arrow up to preset 5 again and finally back to preset 4.
It loaded just fine.

I think I did it the wrong way. Started over like this.
Went to preset 16 (empty)
loaded a sample.
stepped down to preset 15 (also empty) and loaded a new sample from a different folder.
Stepped back up to 16 and yes. It loads the first file but from the correct folder.
It loads index 0 instead of, in this case, 8.

I repeated this several times and the same thing. Bugger!.
Tried exchanging the VST string preset to a VST Parameter but that didnt help.

There must be a bug here somewere?

[aliasant]

Lol. Just realized that this is exactly the problem I was having with my loader in my drummachine.

Pretty convinced that it is a bug. Probasbly in the droplsit primitive.
Didnt someone else report a bug in it?

[AngularMomentum]

I am not sure if it has been brought to the attention of Malc...I think I have some of these problems as well in Wave Manager, when trying to use key codes.

Also I built in, when a sample is not found it will automatically look in the install dir...just to make it all even a bit more fun and confusing...heheh.