I am running into two issues (one fixed).

I'm running Pianoteq and your server on a Raspberry Pi 400.

Before starting the server, I set up a the Raspberry Pi as a Wifi Hotspot (without internet), since that will allow for use even where there is no internet.

One probem I had (solved) was that npx checks for updates by default. 

However, if there is no internet, this (futile) check takes a good while before it fails. 

The fix I found is to use the "no update" flag to prevent they update check - e.g. (from the server directory):
NO_UPDATE_CHECK=1 npx serve -s build
(Reference: https://github.com/vercel/serve/pull/457)

The other problem: when I connect to the server using my Android phone or tablet, the webpage is devoid of all "style".  What am I missing?

PS my hunch (after looking at the page source) was that the Android device couldn't get the "bootstrap" CSS, because the Raspberry Pi had no internet connection - but that somehow the Raspberry Pi was able to get the CSS during installation of the application (when there was a internet connection).

Indeed this hunch was proven, because when I connected the Raspberry Pi to Ethernet, the Android device WAS able to get the style sheet (the application looked normal).  And (happily) when I disconnected the ethernet, the server page still looked normal despite lack of internet.

Your documentation is better now and the part "Option 2 - Deploy locally" in particular.
The diagram makes it clear what the heck i need to install.

Thanks for the feedback!

Well, this is my light dyslexia at full display! 

Some sliders in Pianoteq have pre-defined set of values and not an open range.  This difference accounts for that discrepancies.

Hi,

I just deployed 1.2.4, which now should include all instruments.  Pls let me know if you are still missing a few instruments.  Bear in mind that the Pianoteq API does not provide the same grouping as the UI interface of Pianoteq.

Also, I updated the documentation (got carried away).  If someone would be so kind to look at it and provide feedback.  I'd really appreciate.  Still not sure if the way I described option 2 is good enough.

Thanks

I count 64 instruments in my PTQ as well as in your client. Perfect!

Your documentation is better now and the part "Option 2 - Deploy locally" in particular.
The diagram makes it clear what the heck i need to install.

Not to be picky but there are a few typos/inconsistencies:
"Option 2 - Step 3 - Install PQT-Client-Webapp" (It's "PTQ"!)
"Option 2 - Step 5: Access the PQT-Client-Webapp from your mobile device" (Again!)
"Option 2 - Step 4: Run the HTTP server to serve Ptq-Client-Webapp" (Now "Ptq", not "PTQ"?)

All in all i'm in awe what "you guys" are able to do with PTQ, the JSONRPC and your coding wizardry.

Thank you sir!

[edit]
Why are the volume sliders in the client and PTQ not congruent?

I just deployed 1.2.4, which now should include all instruments.  Pls let me know if you are still missing a few instruments.  Bear in mind that the Pianoteq API does not provide the same grouping as the UI interface of Pianoteq.

Also, I updated the documentation (got carried away).  If someone would be so kind to look at it and provide feedback.  I'd really appreciate.  Still not sure if the way I described option 2 is good enough.

Thanks

Anyway, now i went the path of least resistance by installing Firefox for Android. Works right away!

Glad it worked out!

No worry.  As I said, the doc will need to do a better explanation on the local installation.  I have seen a few being confused by it so I definitely will need to rewrite some of the doc in the future.

Cheers.

I am assuming here that you are making use of the public website for the app right?

I actually did add the client to my homescreen but i failed to read the part about installing node. Mea culpa!

Anyway, now i went the path of least resistance by installing Firefox for Android. Works right away!

Hey,

This is really cool. I opened the forum with the intention of seeing if it was possible to build something like this so to make PT usable on a tiny touchscreen, so have just downloaded your repo.

When I run I'm getting a TypeError: Cannot read properties of undefined (reading 'split')

Looking in the code I guess this could possibly be coming from the metronome class or the FractionRangeParameterViewController function in inputs.js, but I'm not familiar enough with React to trace it back.

I am a programmer though so happy to help debugging if I can. I'm running Pianoteq v8.0.3/20221209

Cheers!

Hi MurkyFreddery,

I tried to replicate this but I am not seeing this on my end.   If you don't mind, pls open an issue on GitHub so we can discuss it there.

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

Cheers

@sordess

I'm not much of a coder. I wasn't aware you need to implement every single instrument by hand.
I thought your client somehow retrieves the information which instruments are present from PTQ.
So thank you for your work.

I successfully managed to connect to PTQ8 from a second Win10 laptop running Firefox without effort.

Question:
In order to run your client on android chrome, i need to install it on my device by adding it to the homescreen because of security reasons,
as you mention on your github.

Unfortunately i get a network error on both my android phone and my android tablet even though i carefully entered the correct line, in my case:
http://192.168.1.110:8081/jsonrpc

I know it's hard to tell but can you give me any suggestions about possible causes?

Hi Zaskar,

The new implementation won't require me to adapt the code every time there is a new instrument set.  As stated above, I forgot to change the initial implementation along the way as I am not using these other presets.

I am assuming here that you are making use of the public website for the app right?  If so, this is a restriction imposed by Google Chrome.  See a full explanation on the GitHub discussion thread here: https://github.com/robert-rc2i/ptq-clie...ussions/28

As for the install.  The documentation might be confusing.  For Chrome to work you need to have  web server installed locally.  Instruction to deploy the app locally can be found here: https://github.com/robert-rc2i/ptq-clie...loy-localy.   On my end, I deploy the app and web server on the same device that Pianoteq is installed.  Once installed, you can now point your Browser to the URL provided by the "serve -s build"

If it does not help.  Open a discussion on GitHub and I'll see what I can do.

Cheers

I'm not much of a coder. I wasn't aware you need to implement every single instrument by hand.
I thought your client somehow retrieves the information which instruments are present from PTQ.
So thank you for your work.

I successfully managed to connect to PTQ8 from a second Win10 laptop running Firefox without effort.

Question:
In order to run your client on android chrome, i need to install it on my device by adding it to the homescreen because of security reasons,
as you mention on your github.

Unfortunately i get a network error on both my android phone and my android tablet even though i carefully entered the correct line, in my case:
http://192.168.1.110:8081/jsonrpc

I know it's hard to tell but can you give me any suggestions about possible causes?

This is really cool. I opened the forum with the intention of seeing if it was possible to build something like this so to make PT usable on a tiny touchscreen, so have just downloaded your repo.

When I run I'm getting a TypeError: Cannot read properties of undefined (reading 'split')

Looking in the code I guess this could possibly be coming from the metronome class or the FractionRangeParameterViewController function in inputs.js, but I'm not familiar enough with React to trace it back.

I am a programmer though so happy to help debugging if I can. I'm running Pianoteq v8.0.3/20221209

Cheers!

@Zaskar & @davidizquierdo82 Thank you for the kind words

@Zaskar:  You'r right.  I must have forgotten to update the navigation at some point.  Since I am mainly using the Piano classes, I did not noticed the missing ones.  I'll be updating the software over the weekend with the additional instruments.

That being said.  Bear in mind that some controls do not apply to some instruments, especially the new Guitar.  That Guitar made me realize that some controls are not  visible for some instruments. This makes a lot of sense, but I was just not aware of it.  That's something I'll have to investigate more in the future.

Cheers.

But i am missing a whole bunch of instruments in the webclient.
For example: Classical guitar, the harps, Karsten collection, Ruckers, Blanchet, Grimaldi, Schantz, Dohnal, Broadwood etc. etc.
There are 20 instruments that are not under "Instrument selection" in the main menu!
Is there a way to access them anyway?

navindra wrote:

Well done!

Modartt should link these somewhere... it's really quite cool that you can run a custom Pianoteq interface right from your phone.

Hi and thanks for the kind words.

I'll be adding a new UI interface to support tablet in the near future.  So that I can maximize the screen size when appropriate.

Cheers,

That would be so cool, thanks for the great job done so far!

Well done!

Modartt should link these somewhere... it's really quite cool that you can run a custom Pianoteq interface right from your phone.

Hi and thanks for the kind words.

I'll be adding a new UI interface to support tablet in the near future.  So that I can maximize the screen size when appropriate.

Cheers,

Modartt should link these somewhere... it's really quite cool that you can run a custom Pianoteq interface right from your phone.