I just tried the new v4 demo, which felt much better, to find out that midi out is disabled, and so (against my better judgement) upgraded to Playbeat 4.
All I want to do is trigger other samplers, that have full feature sets.
I set the remix octaves, I set the fixed note triggers. Do all the necessary midi routing.
I get midi communication going between tracks. Each separate receiving track contains a sampler. Testing on one track for now. (A kick on track 8, which should be track 1, imo!)
Every time I change or retrigger a remix pattern from midi note, the fixed note somehow changes, resulting in silence.
However, the fixed note readout still states that it is c2 or whatever.
I move the fixed note value up and down and it starts triggering the assigned note.
Then it changes again when the remix note is retriggered, and thus silence again.
Can you please check the latest 4.0.3? The new version is up on our site and will be available on our resellers and the App Store today. We will probably have a series of updates this week addressing some issues on various setups so a change-log thread is coming up.
Opening a saved VST3 preset with locked MIDI outputs will reset all tracks to C3, no matter what notes were there before saving. Maybe you can just make separate processes for locked MIDI outputs and internal notes triggering internal PB sounds? If Track 1 in a sequencer has any note and is set to output C1 in the settings, then no matter what pitch is set in the sequencer, it will always trigger that note as MIDI output? I don’t understand the point of repitching the internal sequencer when setting the MIDI outputs (why, when Track 1 MIDI output is set to C1, the sample playback in PB is also C1?)
Nothing plays until I shift the assigned note up/down, and then back to the necessary note being sent to the sampler.
When the loop comes round, the assigned note is no longer triggered.
I am always happy to be wrong and concede user error, if that’s the case. This is always the best outcome.
However, the fact that I bought this specifically to use the midi out facility, that was absent in the demo, only to find that it does not work, has left a bad taste.
Unfortunately, only compounded by being advised to try a new version, a questionable shot in the dark, which I personally and correctly predicted was not going to address the issue.
I was already giving the benefit of the doubt to this software house, when I made this purchase.
I feel it would not be out of the question to request a refund at this stage.
I would rather it actually worked, of course.
Thanks Ch1mpact, but I don’t have the standalone installed, and I have wasted enough time trying to get this software to work as advertised.
I’ll wait and see if this gets fixed before I request a refund over the next week.
Ahh sorry to hear mate. May be a positive to take at the moment is AM are quick with updates and responsive in the forums. Hopefully a solution is found soon
If the problem was acknowledged, and fixed, I am sure we wouldn’t have received another vague, general update notification. Perhaps a specific response pertaining to the issue?
Suffice to say, the issue remains.
Edit: I said i would be happy to be wrong. Looks like the lock midi outputs thing is working.