Thanks for the kind words about the app.   As for setting the audio device it is not possible, as far as I know, form the JsonRPC API.  As you pointed out, you can see the current one and the list of audio devices available, but that's it. 

What we can set with the API is what ever is returned by the getParameters API.  Unfortunately, the audio & midi device are not returned by the getParameters API.

Cheers,

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.

Cheers

Hi @alfatreze,

Sure thing.  I wouldn't mind a UI upgrade especially if we can add tablet support!

I can help integrate it with the current project.  We can discuss it over at GitHub on the project page if you'd like.

Do you know BootStrap by any chance?

Regards,

alfatreze wrote:

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

Sure thing.  I wouldn't mind a UI upgrade especially if we can add tablet support!

I can help integrate it with the current project.  We can discuss it over at GitHub on the project page if you'd like.

Do you know BootStrap by any chance?

Regards,

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.

Here is a latest revision of this project.  The app is now back online at the same url:

http://ptq-web-client.s3-website-us-eas...onaws.com/

Once in the app, remember to set the URL of Pianoteq for the app to work.  Also, you can install the app on your device (iOS or Android) using the "Add to Home Screen" from Safari, Chrome or Firefox.  This will make the web app behave like a native app.

Here is the current feature of the app (1.1.4)

• Piano controls
  

  • Volume and dynamics controls

  • Sound modes (Recording, binaural, stereo & mono)

  • Piano condition

  • Piano lid

• Voicing controls
  

  • Hammer settings

  • Pedal settings

• Effects controls
  

  • EQ 1 & 2

  • Delay and reverb

• Design controls
  

  • Soundboard settings

  • String settings

  • Blooming settings

• Instruments
  

  • Loading an instrument

  • Previous and next preset

  • Reload a preset (Useful, when you make changes to Pianoteq directly)

  • Saving a modified preset

  • A/B Switching

• Metronome (Limited for now)

• Media player (Midi)

Screenshots are available on the README file in the Github project repo here:

https://github.com/robert-rc2i/ptq-client-webapp

Cheers

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. 

@Modartt,

There seems to be a parameter mismatch on the setMetronome API.

oops you're right -- the volume setting is broken, we will fix that.

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

• Metronome

• State of the midi sequencer

• And a few other enhancements

Thanks Modartt.  That's great!

I'll be implementing the metronome shortly! 

I do not know if this fixes the headless issue.  Can someone confirm?

Cheers,

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

--serve 192.168.2.87:8081

Now this SPA can be deployed anywhere as long as it is being served through HTTP and NOT HTTPS.

At first the app tries to initialized itself by calling Pianoteq on the same server that it is deployed to.  If that fails, you get an error message.  In that case, click on the menu button and set the url (like: http://192.168.1.10:8081/jsonrpc) to Pianoteq.

Oh and by the way, the URL is saved in the local storage of the browser.  So if you change device or browser agent, you'll need to provide the URL again.

Cheers

Edited:  Well, I might have found the culprit.  I am now able to communicate with Pianoteq directly without the need of a proxy other than a web server to serve the page.  I need to test it further but I think the proxy will no longer be required.   More to come....

Woohoo! Can't wait to learn more!

As for the CORS, I just verified and Pianoteq does provide the proper header response to allow any site to connect to it.  So, if you run the app from a desktop environment like your MAC, it will work without the proxy.  I just realized that iOS is imposing secured connection when making fetch calls to other site, but not on the same site (And yes, same site has to include same port)

So, the connection is not refused by Pianoteq but by Safari on iOS.  In theory, the the app would work on Android, without any proxy as there is no limitation for that type of connections on that platform.  But I do not have an Android device to test it.

Cheers

----

Edited:  Well, I might have found the culprit.  I am now able to communicate with Pianoteq directly without the need of a proxy other than a web server to serve the page.  I need to test it further but I think the proxy will no longer be required.   More to come....