New Web/SPA front-end for Pianoteq (Using JsonRPC)

Good job! I can report that it works.

I had to do "npm install react-scripts" first.

I had to relaunch it once, perhaps because the JSON-RPC interface was not ready the first time. Maybe a self-refresh would be nice.

Thanks!

Hi,

I have updated the project with the addition of a few controls

• Volume & Dynamics

• Effects - Mainly toggling on/off Delay, EQ1 & 2 and Reverb

• I also updated the readme for a better explanation on how to install and run it.

• New menu

• Reload preset button

Next I'll be adding some voicing controls.

Cheers

This is awesome, I can't wait to try this!

We should get a request to Julien so that CORS headers are returned (if configured), and that way, no proxying is needed.

For me, an external client app should be able to connect to JSON-RPC API directly without any need of proxying or using any server resources at all.

I tried it on my Mac and it works great! In fact, I think it is doing everything I would need such an interface to do.

I'm going to wait until the MIDI sequencer works in headless mode before I use your interface on my Raspberry Pi 400. My other hope is that we can eliminate the need for the proxy.

In time, there should be some kind of showcase corner like the FXP Corner for these new interfaces. You might want to post about your new interface on Piano World (and maybe PianoClack) as well.

Woohoo! Can't wait to learn more!

Hi,

Just to let everyone know that I moved the repo from bitbucket to GitHub.  The old repo has been updated with a link to the new repo, but it might get deleted at some point.

So the new link is: https://github.com/robert-rc2i/ptq-client-webapp

Sorry, but I cannot change my original post for some reason. 

Cheers

@Modartt,

There seems to be a parameter mismatch on the setMetronome API.  When posting the following command, the BPM gets updated by the volumde_db param

{
    "method": "setMetronome",
    "params": {
        "accentuate": true,
        "bpm": 104.0,
        "enabled": true,
        "timesig": "4/4",
        "volume_db": 72.0
    },
    "jsonrpc": "2.0",
    "id": 1642889493614
}

With the above post, I get a response that my command was successful, but when I looked at the UI interface, I see that the BPM is now 72 and not 104.

Cheers

Hello,

Here is the latest version deployed to AWS here:

    *** Removed for now ***

So it means you can use it without installing it locally.

As always, the first time you access the web page, you'll get an error message.  Simply click on the menu button and fill in the full URL of your Pianoteq instance like

    http://ip.address.here:8081/jsonrpc

This new version supports
    * The new metronome API (Only partially for now)
    * Midi sequencer state - Now know when a recording/play is enabled

Enjoy!

---

Edited: Had to shutdown the site as some bots were trying to poke security holes at the site. 

Hi @sordess,

I-m having a really weird issue with this. Both with the web version (safari) or running a local build whenever I configure the ip correctly the web app loads completely blank.

I'm loading pianoteq with the proper arguments from terminal, and atm I'm quite unsure what I'm doing wrong.

My goal is to fork the project and build a custom ui that's both a bit more elegant and customized.

I'm a Product Designer with a fair bit of css / html knowledge. Though not so great with js/react, which is the core of this.

I'm doing this to have a customized full screen ui for the piano i built for my daughter around a pi and a vpc1. I plan for it to be fully responsive to acommodate a fair amount of screen sizes.

I haven't really started with the design phase, As I'd like to hack away a bit at how the app is built and how far I'm able to change some of the stuff .

Anyway I'f you or anyone more versed in react and js than me is interested I'm more than willing to collaborate. It should also be interesting to make this an open design project for people ot pitch in ideas an needs on a a custom touchscreen ui would be useful.

BTW: Here´s a very quick first draft with some ideas jooted down. I want to be able to support both vertical and horizontal layouts, with either typical proportions as well as really wide sreens, like a waveshare 1480x320 as well as epaper, so high contrast and avoiding scrolling for conting is an important feature.

Not too many changes atm from current layout.

Sure, I'd love to.

Yeah, even tough I know my way pretty well around bootstrap, I haven't used it for quite a while. Not a biggie to pick it up again.

I'd like to do the design part as an open design project and pick up quite a bit of feedback, needs and wants from the community to inform direction and ideas, though, even if these may come up quite later on never at all

Hi Sordess,

Really nice work here - congrats!

Since you obviously know your way round the RPC API by now can I ask you to confirm that there is no way of changing the selected audio and midi devices via RPC? I can't find any. Am I missing something?

There's the 'getAudioDeviceInfo' call which shows you the currently selected audio device, although, strangely, no equivalent for MIDI devices, as far as I can see.

The trouble is that if you're running PT headless on a machine without a desktop it's rather difficult to set the devices up in the first place, and then to change them if that becomes necessary. PT has a command line argument to start without any audio/midi preferences, but not to set them. So, as far as I can see, you're reduced to having to edit the Pianoteq81.prefs file manually, using 'aplay' and 'amidi' on the system to get the correct device strings (although there's also the RPC 'getListOfAudioDevices' which I suppose you could use instead of aplay).

Have you found any other workarounds?

Thanks, Ian.