JPR Support

I have noticed Palette Midi buttons share the same midi message (ControlChange)

For Example Palette one, button one has a midi message of BE 2E 00.
If I then assign a midi message to palette two, button one. I find it has already been assigned (shared with palette one's) BE 2E 00, and i can not assign th ebutton it's own unique message.

Is this intentional?

Hi Wildman

MIDI assignments are for buttons, not jingles themselves, through different palettes.
So for example, you assign MIDI (press/release) messages to Jingle button 0 (the first button, at top left), it will always have the same assignment regardless which palette is load, even if there is or not a jingle loaded). This is the normal behavior of MIDI usage with JP.
It is not planed to assign MIDI messages to jingles themselves, sorry

Thank you for your replay.

Can JP output midi feedback?
For example: When a jingle is finished JP to send feedback/output midi message BE F2 00 to the controller fo the LED will shut off.

I have seen this in some of your videos. Yet i can't find any insuructions. I have tried Bome's midi translater to no avail.

MIDI outputs (for buttons LEDs feedbacks, and also for triggering functions of a third party software, through a MIDI Virtual Cable) will be available for v5.7, so that explains why you find no info about this with 5.6

Thank you Couin. I'm a patient guy

That's a good point Because I have a problem without a feature on machines that have a Win .81 or below, that makes JP crashing
So release could be delayed or I will remove it (or lock this feature for non Win 10/11 machine).

I think with windows 7 unsupported this october, and windows 8 during 2026 it would be prudent to allow the feature to users of windows 10+ . And lockout 8.1 and below.
It could be detremental to the software not to have midi control fully implemented.

If we are following EOLs, we should put a lot of machiens to the trash
JP is a very light software that can run on poor machine with XP (like I use for my live shows), for example with ThinClients T5720, etc. That is a good project to re-use these machines instead of trashing them.
the feature that cause problems is not the MIDI but another, to define a Stop/Fadeout point (like the Start position for beginning), to finish a jingle playback before the end of its file, this is less significative (so that's why I will state on its becoming ASAP, because it is just a "plus").

Theres a piece of old (actually still current) software called OtsAV that packets audio into their ots format. This allows proper manipulation over the audio or video file.
This includes fadin and fadeout points as you mentioned.

The packaging software is called "ots studio", perhaps wrapping audio in similar fashion on older machines might be one solution?

I have often seen unsupported features grayed out on some computers.

Oula, no. The goal is not at all to require another software (by curiosity, I installed it, I understood nothing, the software is not intuitive at all, I even don't know what it is supposed to do.... I uninstalled it), but define directly in JP , a fadeout point. If a third party software is required to do this, users will go faster to edit the sound with audacity.

About grayed out features for non Win 10/11 is a possibility that I already thought, but I would prefer to resolve the problem instead.