Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Recent Posts
2
3rd Party Plugins - (fb2k) / Re: foo_vis_vumeter
Last post by Defender -
Quote from: Defender on
Quote from: oops on
0.9.5 released!

  • Fix Columns UI fullscreen within Panel Stack Splitter (PSS) crash and skip GDI drawing when fullscreen. GDI drawing the (transparent) background is pointless because the parent PSS window is not fullscreen'd. So, the fullscreen entry methods are disabled in this context. In addition, even if not prevented, going fullscreen and returning loses the transparent background. I think this is a bug in PSS (or Columns UI) [windows hosting other windows not dealing with the fullscreen gracefully]. Only closing and reopening the player would bring back the transparency.
Are you sure you are not disabling transparency in your code returning from fullcreen regardless of the nature of the splitter type of the parent?
Did an extra test. This time CUI 3.0.0 alpha-2 with just a single JSplitter which holds a VU 2024. No PSS around whatsoever.
Green background is lost after returning from fullscreen.

So PSS has nothing to do with this issue.

What I also noticed is when you switch quickly between fullscreen and no fullscreen, the green background that is painted in the JSplitter is displayed but replaced quickly by a dark background. So what's up?
4
3rd Party Plugins - (fb2k) / Re: foo_vis_vumeter
Last post by Defender -
Quote from: oops on
0.9.5 released!

  • Fix Columns UI fullscreen within Panel Stack Splitter (PSS) crash and skip GDI drawing when fullscreen. GDI drawing the (transparent) background is pointless because the parent PSS window is not fullscreen'd. So, the fullscreen entry methods are disabled in this context. In addition, even if not prevented, going fullscreen and returning loses the transparent background. I think this is a bug in PSS (or Columns UI) [windows hosting other windows not dealing with the fullscreen gracefully]. Only closing and reopening the player would bring back the transparency.
Thx!

Just a quick reaction. In the attached screenshot I'm running 5x VU 2024 instances from CUI/PSS/JSplitter parent.
All instances are set to "Lock ratio on" and therefore don't stretch fill the parent panel they live in and therefore can show transparency of this parent panel. They all run fine and no issues with flickering needles or the like.

Of course I noticed transparency being lost when returning from fullscreen.
I paint background/art from the grandparent PSS panel (all the reddish backgrounds).
For testing purposes I changed one of the direct JSplitter parents to display a bright green background and thus overwriting the PSS painted reddish background/art.
Returning from fullscreen also the green background is lost.
PSS has nothing to do with this since the parent is a JSplitter.

Are you sure you are not disabling transparency in your code returning from fullcreen regardless of the nature of the splitter type of the parent?
5
3rd Party Plugins - (fb2k) / Re: Columns UI
Last post by dix-hill -
Is there a way to make a Style Script conditionally dependent on the active playlist?  By active playlist, I simply mean the playlist I'm looking at regardless of whether a track is playing or not.

I'm using a playlist to edit the genre fields of my tracks and I want the Genre column to have a green background, but only on the "Genres Playlist".

Thanks for any help!
6
3rd Party Plugins - (fb2k) / Re: [fb2k 2.0] Queue Viewer
Last post by Defender -
Quote from: marc2k3 on
I wouldn't know how even if I wanted to.

Peter's excellent list controls in the SDK do all the heavy lifting. All my code does is fill values/update on queue changes, re-ordering etc. I don't need to know or care about any display related code. It's invisible to me. This is very different from JSP3 where every single aspect of display handling is entirely my own code.
Bummer.

Thanks for the answer.
7
3rd Party Plugins - (fb2k) / Re: [fb2k 2.0] Queue Viewer
Last post by marc2k3 -
I wouldn't know how even if I wanted to.

Peter's excellent list controls in the SDK do all the heavy lifting. All my code does is fill values/update on queue changes, re-ordering etc. I don't need to know or care about any display related code. It's invisible to me. This is very different from JSP3 where every single aspect of display handling is entirely my own code.
8
Other Lossy Codecs / Re: TOY, a lossy and experimental "do not use" codec
Last post by maikmerten -
@a.ok.in Well, thanks for testing - personally I guess the performance is more like MPEG-1 Layer II, not MP3 - simply because the encoder has no psychoacoustic model. Also, I guess the entropy coding is plain stupid. I completely expect MP3 to outperform TOY and don't trust TOY with bitrates below 200 kbps.

@Klymins The current encoder determines bands according to frequencies. Basically, for anything lower than 44.1 kHz, some bands would go unused. The current frequency layout is a vague approximation of the Opus band layout.

The band layout is transmitted in the TOY file and encoders can choose their own band layout. A proper, non-experimental codec would just go for a predetermined, fixed layout.
10
3rd Party Plugins - (fb2k) / Re: foo_vis_vumeter
Last post by Majestyk -
Quote from: oops on
0.9.5 released!

I'm very happy with how development has been going. Lots is (small but) interesting problems solved, much documentation read and unfamiliar concepts learned, several moments of frustration turned to happiness when that "eureka" insight hit. Let's also keep up the good back-and-forth we're having in this thread. Thank you to for the trust and contributing through ideas, help, discussion, and, above all, testing.

This version is completely broken on my DarkOne tweak theme.

For previous versions I'm using these commands for the skin loading...

Code: [Select]
	this.DarkOne4PEAK = function() {
		fb.RunMainMenuCommand("View/Visualizations/Analog VU Meter skins/Peak Meter (Color Switch)/" + 0 + " " + display_system.display_arr[display_system.display_combi_colour]);
		setTimeout(this.DarkOne4PEAK.bind(this), 150);
	}
	
	this.DarkOne4VU = function() {
		fb.RunMainMenuCommand("View/Visualizations/Analog VU Meter skins/VU Meter (Color Switch)/" + 0 + " " + display_system.display_arr[display_system.display_combi_colour]);
		setTimeout(this.DarkOne4VU.bind(this), 200);
	}

In 0.9.5, all my meters are flickering back and forth between the two folders above. The only way to get it to stop doing that is to have one VU Meter only, which means things have reverted back to versions before 0.8.0.