Rein,
I really like the fact of having only one application to launch and manage.
Results of my tests:
Environment: Client 2.0.9 on Ubuntu then Windows XP. Server 1.6.0 on Ubuntu.
1. Audio devices: when changing from one device to another only a stop and restart of the application will apply the changes. The result is that is seems that none of the options work when it fact they were not activated.
2. The audio volume sliders do not seem to work or if they work they may be working on mixers not related to the selected audio device.
3. RSIDs are TXed with most modes all the time. Is there a logic for that? Was it for narrow modes only, if yes shouldn't they be applied only when the server sends one (which the 1.6.0 server does almost all the time). So it could be a server issue instead.
4. Doing a configuration change in the middle of a session breaks the ARQ. The client sends inconsistent missing packet numbers. This is a real issue as the session password can't be changed without connecting with the old one first, then changing it and re-updating the server while connected.
5. New session password update is logical and much better than the :SETPASSWORD exercise.
6. Error messages related to the session password are really confusing. I propose the server clearly states "Wrong Session password" instead of "Wrong Password" only as I was wondering for a while which password it related to.
7. The QUIT button separate from the connect button is a good thing. Can we take that opportunity to rename it "Disconnect" since it does the opposite of "Connect"?
8. When performing an "Update server" when the session password is incorrect can we make the error message consistent with the other commands (i.e. "Wrong Session Password")?
9. Can I propose that mode changes be disabled during a connected session. It is possible to force the client to another mode in a middle of a session at present.
10. Windows audio devices: I tried on 3 different machines running Windows (2 x XP and 1 x Windows 7) and got the same result (see log below). It seems there is an incompatibility with the parameters of the audioFormat variable in SoundInput.java.
As I remember it working under Windows before, did we change anything there?
D:\Program Files\jPSKmail>java -jar jPSKmail-2.0.9.jar
Exception in thread "Thread-5" java.lang.IllegalArgumentException: Line unsuppor
ted: interface SourceDataLine supporting format PCM_SIGNED 8000.0 Hz, 16 bit, mo
no, 2 bytes/frame, little-endian
at com.sun.media.sound.PortMixer.getLine(Unknown Source)
at javapskmail.SoundOutput.run(SoundOutput.java:46)
Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
at javapskmail.DSPModem.ChangeRxModem(DSPModem.java:365)
at javapskmail.arq.send_mode_command(arq.java:694)
at javapskmail.mainpskmailui$2.actionPerformed(mainpskmailui.java:763)
at javax.swing.Timer.fireActionPerformed(Unknown Source)
at javax.swing.Timer$DoPostEvent.run(Unknown Source)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
at javapskmail.DSPModem.ChangeRxModem(DSPModem.java:365)
at javapskmail.DSPModem$1.actionPerformed(DSPModem.java:199)
at javax.swing.Timer.fireActionPerformed(Unknown Source)
at javax.swing.Timer$DoPostEvent.run(Unknown Source)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
11. Overall I feel there are too many concurrent threads and maybe we can apply the same logic as the Android version with only a modem thread and a GUI one so that we have better control of the execution, especially when changing modes.
12. A question: do you still have the problem with THOR8 decoding?
Hope this helps,
73, John
On Wed, Mar 28, 2012 at 5:28 PM, John Douyere
<vk2eta@xxxxxxxxx> wrote:
Rein,
I have done a good amount of testing today on 2.0.9 and I have quite a few points for us to work on. I will send you the list tomorrow.
But overall it works quite well on my laptop and desktop under Linux. I am having issues with sound under Windows though...more checking needed.
I find it much easier to have everything in one place.
We will also then be able to look at the user friendliness of the system. I really think we can make it much easier for newcomers.
Great stuff.
Regards,
John
On Tue, Mar 27, 2012 at 9:24 PM, Rein Couperus
<rein@xxxxxxxxxxxx> wrote:
It is time to test the V2 client before it is officially released.
Features:
* Modems included, start only 1 program
* Easier authentication with server 1.6 (only 'Update server' necessary)
* Keyboard chat and client-to-client file up/download works again
Software download via http://pskmail.org
Please send test reports to the mailing list...
Tnx & 73,
Rein PA0R
--
http://pa0r.blogspirit.com
