Snakeoil 1.2.2 Beta 1

[agent_kith]

OK..

A new found respect for web developers. Designing a UI that fit the various resolutions (both landscape & portrait), and themes are actually very difficult. It's not these tasks are time consuming, it is but there's something more to this - artistic flair. Of which I have none.

You really need to have that X-factor when it comes to colour combinations.



No prizes for guessing which themes are stock, and which themes are created by me.

Didn't get to do everything I planned with this 2 week break, the Perth heatwave is a huge curve ball. That basically fried my brains. It is what it is I guess, nothing ever goes to plans these past couple of years.

This beta hopefully addresses all the visual problems reported. I'll probably need to update the Wiki also. And the official release will be out once the Wiki more or less is updated.


  snakeoil-armv7l-1.2.2.2.fw (Size: 39.32 MB / Downloads: 1)
(SHA1: a5fff1b2c5ac7e0990ce52433b5460209a57b518)
  snakeoil-x86_64-1.2.2.2.fw (Size: 41.4 MB / Downloads: 10)
(SHA1:faba07c8c8e051467f40747c11871d620e2d549c)

Edit: BTW, https://demo.snakeoil-os.net has been updated to this latest UI.

[Bromf]

This beta hopefully addresses all the visual problems reported.

That fixed the 'invisible green' on player status !

Everything else is good too...(X86-64 version on HP t620 Thinclient Dual-core 4GB ram 16GB Flash )

[Snoopy8]

In Intel laptop (1920 x 1080) running Firefox, have the following issues:

• When Firefox set to "not maximised", sidebar is set to icons only. On maximising, sidebar set to icons + description.  However, when selecting networking, disk/NAS etc, the sidebar is reduced to icons only, when it should have icon + description.  A refresh clears it up, but this refresh should not be required.
  
• Snakeoil/Hardware,  "Delete" button spills over
  

Maybe it is me, but I am having issues with Music Player/ Expert.  The enabling/disabling of a music player is confusing.

• When I click on a disabled player, I have to  click box on right to enable it.  Why not just click to enable, click to disable?
  
• And some players require additional information which further adds to my confusion?  
  
• Initially, I thought I had to restart players to enable new players.  Perhaps use "restart players" to have a consistent way to enable players ????
  

Will post further comments after more testing...

[Bromf]

New oddness.. I start Snakeoil and my OMV NAS server but Snakeoil refuses to recognise the NAS unless I restart Snakeoil whilst the NAS is running.

In previous versions I could select 'Remount partitions' and the share would be added..... now I have to reboot...

Can this be rolled back ?

[agent_kith]

In Intel laptop (1920 x 1080) running Firefox, have the following issues:

• When Firefox set to "not maximised", sidebar is set to icons only. On maximising, sidebar set to icons + description.  However, when selecting networking, disk/NAS etc, the sidebar is reduced to icons only, when it should have icon + description.  A refresh clears it up, but this refresh should not be required.

There's some issues with that side menu bar, that's why it was removed initially. I'll see if I can find a way to fix that from code on my side (without hacking that menu side bar code, which is from a 3rd party).

Snakeoil/Hardware,  "Delete" button spills over
[/qote]
Will look into this. thanks.

[quote="Snoopy8" pid='5203' dateline='1641875405']
Maybe it is me, but I am having issues with Music Player/ Expert.  The enabling/disabling of a music player is confusing.

• When I click on a disabled player, I have to  click box on right to enable it.  Why not just click to enable, click to disable?

When you click on the player, can you click the icon before the name to turn it on? And off? Does that make it better? Ignore the checkbox for now, I'm adding two ways to enable/disable player to see what is the better option.

As for the click to toggle enable/disable. I tried that initially, it's actually worse. Because when you want to change a setting, you clicked on the player, it'll be disabled again. And you have to click it twice to enable.

So the idea is:
1. Click on the player.
2. If it's enabled, you can start to configure the player options straight away. Or click the power button to stop it.
3. If it's disabled, you can click the "STOP" button and it will be turned on, and you can configure it straight away
4. You can also click the stop/power button immediately to turn things on/off.

This works really well across computer, tablet and phone.

And some players require additional information which further adds to my confusion?  

Initially, I thought I had to restart players to enable new players.  Perhaps use "restart players" to have a consistent way to enable players ????

Will post further comments after more testing...

You are right. You have to click the "Restarting Player(s)" to save everything. Clicking start/stop for each player tile doesn't start/stop the players immediately. You have to click the button to save it.. I'll rename "Restart PLayers" button to "Save" to make it clearer.

 

New oddness.. I start Snakeoil and my OMV NAS server but Snakeoil refuses to recognise the NAS unless I restart Snakeoil whilst the NAS is running.

In previous versions I could select 'Remount partitions' and the share would be added..... now I have to reboot...

Can this be rolled back ?

You can roll back to a previous firmware without issue. But clicking the "Save" button should remount them automatically (as long as the NAS has finished loading). What kind of network share are you using? CIFS or NFS?

[Snoopy8]

Further thoughts on Expert Player setup.  I revisited the CamiilaDSP setup and I am not sure I could have set it up with the new GUI.  In the old GUI, things were more logically laid out, no need to click on anything to see how to set things up.  There was a top to bottom, left to right flow.
https://www.snakeoil-os.net/forums/Threa...34#pid4634]
As a refresher, CamillaDSP uses a loopback to intercept the audio signal and apply the filters.

In the new GUI, have to click on custom audio output to bring up config (click on left of screen), then have to switch software status to output devices to see loopback (click on top of screen).  The new GUI was meant to make things easier?  I have my doubts that I could have set things up without needing to read the Wiki.
--------------

Having said all that, I do not want the Expert Player setup to hold up release of new GUI.  Not sure how many people will use Expert Player setup nor go into the complexity that I have.  So suggest releasing the new GUI with Basic player setup, while we discuss improvements to the Expert Player setup.

[agent_kith]

Further thoughts on Expert Player setup.  I revisited the CamiilaDSP setup and I am not sure I could have set it up with the new GUI.  In the old GUI, things were more logically laid out, no need to click on anything to see how to set things up.  There was a top to bottom, left to right flow.
https://www.snakeoil-os.net/forums/Threa...34#pid4634]
As a refresher, CamillaDSP uses a loopback to intercept the audio signal and apply the filters.

In the new GUI, have to click on custom audio output to bring up config (click on left of screen), then have to switch software status to output devices to see loopback (click on top of screen). 

I'll try and setup CamillaDSP and see how it goes. Will get back to you soonish. Are you saying the Loopdevice device didn't show up in the DAC Output drop down box?



Output devices in this dropdown box should mirror the old UI.

The new GUI was meant to make things easier?  I have my doubts that I could have set things up without needing to read the Wiki.

It makes it easier for me, not really the user per se . As in this new architecture makes it a lot easier to chain different player combinations. In the old instance everything is kind of hard coded. E.g. folks cannot use upmpdcli with different versions of MPD, they can only use the latest. Folks also have to pre-configure MPD first.

So this new one scales better.

Having said all that, I do not want the Expert Player setup to hold up release of new GUI.  Not sure how many people will use Expert Player setup nor go into the complexity that I have.  So suggest releasing the new GUI with Basic player setup, while we discuss improvements to the Expert Player setup.

Eventually I will add more stuffs to the basic setup (e.g. if you install HQPLayer or Roon, that will be shown in the list). That should cover +90% of the use case, and will kind of make documentation easier too.

[Snoopy8]

I'll try and setup CamillaDSP and see how it goes. Will get back to you soonish. Are you saying the Loopdevice device didn't show up in the DAC Output drop down box?

Not sure if you should spend your valuable time to install CamillaDSP? Sorry, I was not clear enough. All in the info is there, including the loopback. To me, the old GUI is more logically laid out and available. In contrast the New GUI, some info is hidden and requires clicking on expose it. And info is in several locations, not logically laid out.

Eventually I will add more stuffs to the basic setup (e.g. if you install HQPLayer or Roon, that will be shown in the list). That should cover +90% of the use case, and will kind of make documentation easier too.

Good to hear the basic player will be improved further.

[agent_kith]

Not sure if you should spend your valuable time to install CamillaDSP? Sorry, I was not clear enough. All in the info is there, including the loopback. To me, the old GUI is more logically laid out and available. In contrast the New GUI, some info is hidden and requires clicking on expose it. And info is in several locations, not logically laid out.

I'll see if I can tweak this more.

[agent_kith]

I'll see if I can tweak this more.

Here's the new revised layout. Information is no longer always shown now, user will have to click on the (?) icon to display this as a pop up dialog. That's the idea, the code isn't done yet as I spent most of my time this morning on responding to emails.
 

So this new re-design somewhat better reflect the top->down, left->right UX. I have been experimenting with moving the (?) and the (on/off) from the bottom left widget to the right, and it does feel more logical to have these two controls over on the right. that's something I might try to do. Might as well get this right so I only need to modify the wiki once.

Once this is done, beta 2 will be released, and very likely a official release will be pushed out in a couple of days (prob no more than a week).

The top two panels don't really look good on mobile devices in portrait mode. But I'll defer and fix that in the next update I think. It's really time to move on to the kernel stuffs now for 1.2.x