Xion 1.0 build 87 Beta Release

[Cliff Cawley]

WARNING:
This is a Beta Build. That means it has fixes and features that are NEW. It is also possible it has bugs that are NEW! If you are looking for stability, please don't expect this build to be perfectly stable. It may have issues. If on the other hand you are happy to try this build out and post any bugs back in this thread, then please do!

Download Installer Version:
r2 Studios Server -> http://www.r2.com.au/downloads/files/beta/qa-xion_v1.0b87.exe
OR
Xion Server -> http://xion.r2.com.au/download/beta/qa-xion_v1.0b87.exe

Changelist:

• Optimize some rendering code in order to speed up Shimmer Interface drawing
  
• Add some minor list optimizations with vectors
  
• Add more optimizations to the rendering code in order to reduce the CPU usage
  
• Fix and optimize indicator states
  
• Fix indicators not displaying Tooltips
  
• Modify Library so that it shows the name of the CD in the drive

If you find bugs specifically related to this build, please post them here instead of the Bug reporting forum. Any feedback positive or negative should also go in here, no new threads. This way all feedback, etc related to this build will be in the one place.


ABOUT THIS BUILD:

I've done a bunch of optimizations to fix the CPU issues. It won't be completely gone on larger skins, however it should be much better on normal skins that aren't always updating large areas. There are also some other minor fixes.

Enjoy!

Cliff

[SLoB]

not experienced any high cpu usage at all in recent builds

cd name not showing on at least 2 of my latest cds in either cd or dvd drive

thers an issue with track layers not scrolling
if the track layers are not exactly the same size then only the smaller one will scroll

for example
you have 2 layers, 1 white, 1 black to represent a drop shadow
the black one is slightly smaller in size due to a gradient so it sort of looks more blurred shadow at the edges, this layer is smaller than the one above and so scrolls if the track name doesnt fit, yet the above layer does not scroll

this was working fine in 84, both layers would scroll

Cliff, are we going to have to go over these to make sure theyr the same size or will you fix it so it works the same?

I've always wanted it to have core settings for drop shadows rather than roll yer own type thing and there are a few skins using that sort of look to enhance track,time names/values

[Cliff Cawley]

thers an issue with track layers not scrolling
if the track layers are not exactly the same size then only the smaller one will scroll

for example
you have 2 layers, 1 white, 1 black to represent a drop shadow
the black one is slightly smaller in size due to a gradient so it sort of looks more blurred shadow at the edges, this layer is smaller than the one above and so scrolls if the track name doesnt fit, yet the above layer does not scroll

this was working fine in 84, both layers would scroll

Cliff, are we going to have to go over these to make sure theyr the same size or will you fix it so it works the same?

I've fixed a couple of sizing issues, so its most likely that its simply being exposed now as one is smaller than the other. just make sure they're the same size. There's no way to link them to each other, other than making them the same size with the same properties.

Cliff

[UnseenRage]

Not sure if this is a bug or if I am doing something wrong, but I can't seem to get my skin to snap to the upper edge of my screen when I use snaprectangle. I have a layer that is centered in the middle of a larger canvas. I can get the player to snap to the left, right and bottom, but never the top. Is this a bug or do layers have to be at the very top of the canvas at all times to snap correctly to the top?

[SLoB]

thers some sort of wierd stuff going on with snapping on dual monitors

it will snap to the main monitor all edges but only top and bottom edges on the 2nd monitor(which is to the left)
part and parcel of dual monitors or?

yep verified text layer width, so if anyone else gets that issue you gotta redo those layers to be same width

[Cliff Cawley]

Not sure if this is a bug or if I am doing something wrong, but I can't seem to get my skin to snap to the upper edge of my screen when I use snaprectangle. I have a layer that is centered in the middle of a larger canvas. I can get the player to snap to the left, right and bottom, but never the top. Is this a bug or do layers have to be at the very top of the canvas at all times to snap correctly to the top?

Are you using dual monitors? If not, could you send me a copy of your skin so I can reproduce here? Thanks!

Cliff

[Cliff Cawley]

yep verified text layer width, so if anyone else gets that issue you gotta redo those layers to be same width

The functionality hasn't changed here. If you make one track box larger than the other and the title text goes 1 pixel over the smaller track rectangle, then its going to scroll the smaller track box and not the larger one, as the larger one can still fit the text.

This is how its always been. The layers were never linked, you were just lucky to have had the text always flow over by enough pixels so that both the larger and smaller boxes were required to scroll at the same time.

Also remember that at one point text was always scrolling and then changed to only scroll when the text couldn't fit into the box.

Cliff

[ForceField]

Hey Guys!

I am still experiencing high CPU usage when I am using the visualisation window with Build 87

Here is a screenshot with gPod:


I am on a P4(single core) 3.4 Mhz with 2Gb Rams and the load is always above the 60%.This concerns me because I am currently designing a skin with a surface area for the visualisation bigger than this one.With an old CPU like mine,when the load is above the 60%,the fan becomes very noisy.My Vista is very light as I disabled all the useless and heavy services(like the indexing one) and barely goes above 1% when idle.

[Cliff Cawley]

Hey Guys!

I am still experiencing high CPU usage when I am using the visualisation window with Build 87

Here is a screenshot with gPod:


I am on a P4(single core) 3.4 Mhz with 2Gb Rams and the load is always above the 60%.This concerns me because I am currently designing a skin with a surface area for the visualisation bigger than this one.With an old CPU like mine,when the load is above the 60%,the fan becomes very noisy.My Vista is very light as I disabled all the useless and heavy services(like the indexing one) and barely goes above 1% when idle.

The Visualisation code has had no optimizations. Its all software rendered and needs to get changed.

Anyone can make a new Visualisation that will use less cpu, i just haven't had the time.

Cliff

[ForceField]

The Visualisation code has had no optimizations. Its all software rendered and needs to get changed.

Anyone can make a new Visualisation that will use less cpu, i just haven't had the time.

Cliff

I think that the currently used libraries must be changed to libraries that uses the CPU of the graphic card.

Cliff,if you can explain how to make a visual for Xion maybe I can help. I mean,do we need any special software(like editors) or wich language to use (C++)......

[Cliff Cawley]

The Visualisation code has had no optimizations. Its all software rendered and needs to get changed.

Anyone can make a new Visualisation that will use less cpu, i just haven't had the time.

Cliff

I think that the currently used libraries must be changed to libraries that uses the CPU of the graphic card.

Cliff,if you can explain how to make a visual for Xion maybe I can help. I mean,do we need any special software(like editors) or wich language to use (C++)......

Yes, I agree. Realistically the Vis should be done in DirectX instead of Software. I've released a Beta SDK. This is what you can use, but you'll have to know Win32 and C++. The next release will contain source for MFC support. You can find it in the Beta [url="http://xion.r2.com.au/community/vwfrm.php?f=12"]Component SDK Builds[/url] Forum.

This SDK is now out of date, however it contains the full source code for the Visualisation component.

Cliff

[pickle]

If I'm playing a radio station, then either click the 'Next' button, or double-click on a song in the playlist, it doesn't play. If I go to another station, it just stays on 'Connecting...' forever. If I go to an MP3, it loads up the song name, but doesn't play (though the buttons are the same as if it were playing).

I have to quit Xion & re-open it in order to play another song. When Xion starts again, the song I wanted to play (but wasn't) is loaded & plays fine.

This only happens if I'm playing a radio station - not if I'm playing MP3s (don't play CDs).

[SLoB]

y i get that too, its as if radio streams are borked, normal mp3 streams work ok

[ForceField]

I have also a problem with the radio.It won't start.It displays connecting and stays like that.We must also have an indicator for the radio-mp3 so that we can display it in the inteface when using the radio.

Thanks Cliff for the link of the SDK. I know C++ and I think that I can help.

[Cliff Cawley]

I have also a problem with the radio.It won't start.It displays connecting and stays like that.We must also have an indicator for the radio-mp3 so that we can display it in the inteface when using the radio.

Ok, I've reproduced this and have fixed it for build 88

Thanks Cliff for the link of the SDK. I know C++ and I think that I can help.

Ah sweet. Just keep in mind that that version is a little out of date. I'll update it with the next version when I release the next Beta build of Xion

Cliff