Yes. The update installer asks which directory you wish to install software into, and doesn't touch anything else.
ProScan: Official Software Thread
Yes. The update installer asks which directory you wish to install software into, and doesn't touch anything else.
Hi, does anyone have thoughts on how to independently stream the audio from the ProScan's web server? As it is, the presumption in all the tutorials and information I find, only mentor on using the dedicated ProScan web server's page. However, I want to embed the audio stream (and for that matter only the audio stream) into my own website's presentation.
I can independently load the audio stream and controller outside the Proscan's iteration of the web page just fine, but doing the same trick, which I would take as being just as easy, seems astonishingly difficult when embedding into a PHP website.
As a starting point for any possible discussion, I start by copy/pasting the basic audio tags from the HTML source of the Proscan web's page, then am sure to change the "src" so that it points to the local host and the Proscan webserver at port 5006.
Anyone is free to see what I am trying to do by looking at my target page directly.
I can independently load the audio stream and controller outside the Proscan's iteration of the web page just fine, but doing the same trick, which I would take as being just as easy, seems astonishingly difficult when embedding into a PHP website.
As a starting point for any possible discussion, I start by copy/pasting the basic audio tags from the HTML source of the Proscan web's page, then am sure to change the "src" so that it points to the local host and the Proscan webserver at port 5006.
Anyone is free to see what I am trying to do by looking at my target page directly.
Thanks !!!!
If you're able to make a html page with the audio tag then you should be able to make a php script outputting a html page. There's are zillions of tutorials on php. I don't think this is the place to discuss php and html which sounds like you're suggesting. Perhaps someone willing to share may want to contact you offline.
Last edited:
I would have thought so too, and you are probably correct then. I may just not have the skillset.
Anyway yes, if anyone has done this without the machinations of additional scripting beyond simple HTML5 please do contact me. I have other approaches in mind in any event.
Last edited:
Ok so this may be more of a issue with my phone..not sure, but it started with the latest update-could be coincidence. When I start webserver and go to my site to listen on my phone, I see the SDS-200 virtual scanner, but it won't let me hear the audio on that page like I usually do. It just says "loading". When i click the actual link to "listen live" it works, but then I can't see the virtual scanner and make inputs. It works fine like usual on my ipad on safari. I tried clearing the history and cache, tried chrome, and made sure java was enabled. Any other ideas? I like listening on my phone
I received a few reports on this issue with iPhones . I'll release an update 1st thing Sunday morning.
awesome thanks!
ProScan Version 20.3 Just Released!
ProScan is the most powerful and feature rich scanner software in the world !!!
- Fixed - Low latency audio player wasn't working on iPhone web browsers.
ProScan is the most powerful and feature rich scanner software in the world !!!
it works now thanks
ProScan Version 20.4 Just Released!
ProScan is the most powerful and feature rich scanner software in the world !!!
- Fixed - Memory leak when using the Web Server and Source Client when the mp3 Bitrate is set to 64 kbps or higher.
- Changed - Reduced the latency even more on the low latency audio player on the Web Server web page. It's now less than 0.8 second.
- Removed - 'Display & Metadata Delay' option on the Web Server web page as it's no longer needed.
ProScan is the most powerful and feature rich scanner software in the world !!!
- Joined
- Jan 15, 2007
- Messages
- 7,466
-
Awesome!
I'm so glad that I wrote a script to automatically update the 10 copies I have on my PC, especially when you push a few releases out within a few day's time!
Thanks as always, Bob!Would you consider sharing the script?I'm so glad that I wrote a script to automatically update the 10 copies I have on my PC, especially when you push a few releases out within a few day's time!
Thanks
Robert
- Joined
- Mar 6, 2009
- Messages
- 217
Hi Bob,
Is there an option to bring back the display latency offset? Have upgraded to 20.4 however am still getting around 3-4 second delay, most likely related to work network (out of my control)
Also, it seems that audio on Firefox may not be working (however this may be blocked - need to investigate this on another machine.)
Is there an option to bring back the display latency offset? Have upgraded to 20.4 however am still getting around 3-4 second delay, most likely related to work network (out of my control)
Also, it seems that audio on Firefox may not be working (however this may be blocked - need to investigate this on another machine.)
So you want to use the HTML5 player with about 24 seconds latency??? No there's not. Perhaps try an external player.
Last edited:
- Joined
- Jan 15, 2007
- Messages
- 7,466
-
Really liking the low latency audio player. Might just be my imagination, but the .08 second delay seems to decrease even a little more after the web page has been connected to the ProScan server for a short while.
Very well could be. I did a couple of tests in JavaScript to try to get an accurate latency figure. Both tests had similar results. The latency started at 1.2 seconds and gradually decreased to about 450 ms. I wasn't sure if my testing was valid so I'm glad you brought it up
Test 1. Compared the metadata text change in the panel (directly below the List of Parameters label) with the metadata next to the audio player. The metadata in the panel uses a websocket method to get the metadata and the metadata near the audio player gets the metadata from the mp3 stream.
Test 2. On the server side, I used the computer clock to put a timestamp in the metadata in lieu of the normal text tags. On the browser side, I compared the timestamp in the metadata with the computer clock.
