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.
Topic: Spider Monkey Panel (foo_spider_monkey_panel) (Read 370801 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Re: Spider Monkey Panel (foo_spider_monkey_panel)

Reply #1400
Uhm... disclaimer, have not really much experience with all this.

First, your scripts don't seem to work on win. Since it looks for py instead of python.
https://stackoverflow.com/questions/64697211/how-to-fix-py-is-not-recognized-as-an-internal-or-external-command-operable-p
Using doskey doesn't work for the lines using "subprocess.check_call()", so I had to edit the *.py files to use 'python' instead of 'py'.

Then V2 has different submodules than V1, it is not just a matter of using the scripts from V2 on V1. i.e. it now complains that there is no lexilla submodule too.

EDIT: as far as I understand, do you mean not only the scripts must be ported to V1, but also submodules and then all this?
https://github.com/TheQwertiest/foo_spider_monkey_panel/commit/c9d8d83d577516153070047572fa78d69e976906

There is now way to simply build v1 as is?

Re: Spider Monkey Panel (foo_spider_monkey_panel)

Reply #1401
First, your scripts don't seem to work on win. Since it looks for py instead of python.
I develop SMP (and all other fb2k components) exclusively on windows =)
"py" is an utility that comes with default windows Python installation (https://stackoverflow.com/a/50896577)

Then V2 has different submodules than V1, it is not just a matter of using the scripts from V2 on V1
But I've never said that only scripts changes are needed, on the contrary, I've mentioned scintilla submodule (which lexilla was part of at some point).

Anyway, my previous reply was not intended as a guide, but rather a pointer on where one can look for the changes required to make v1 buildable.

Re: Spider Monkey Panel (foo_spider_monkey_panel)

Reply #1402
First, your scripts don't seem to work on win. Since it looks for py instead of python.
I develop SMP (and all other fb2k components) exclusively on windows =)
"py" is an utility that comes with default windows Python installation (https://stackoverflow.com/a/50896577)

Then V2 has different submodules than V1, it is not just a matter of using the scripts from V2 on V1
But I've never said that only scripts changes are needed, on the contrary, I've mentioned scintilla submodule (which lexilla was part of at some point).

Anyway, my previous reply was not a guide, but rather a pointer on where one can look for the changes required to make v1 buildable.
Well all my installations of python only had "python.exe" not py. And all references of py I found were related to unix systems, my bad anyway.

Quote
Anyway, my previous reply was not a guide, but rather a pointer on where one can look for the changes required to make v1 buildable.
Understood. I thought v1 was buildable without further changes at some point of the commit history. Thanks anyway

Re: Spider Monkey Panel (foo_spider_monkey_panel)

Reply #1403
Understood. I thought v1 was buildable without further changes at some point of the commit history. Thanks anyway
IIRC, the problem is with environment and not SMP code per se: older scintilla is not buildable with newer Python version, so either the newer scintilla version or older python version is required.
There are also might be some compilation errors caused by newer VS, but I don't remember any specifics.

Re: Spider Monkey Panel (foo_spider_monkey_panel)

Reply #1404
Could someone help me create a "mood" button akin to what's present in Br3tt's smooth playlist browser? On click to write anything to specific tag and on second click if this tag is present - remove it.

Re: Spider Monkey Panel (foo_spider_monkey_panel)

Reply #1405
Does pseudo transparency work in SMP? It never seems to work for me. For example, I can make ESLyrics display the lyrics over top of DarkOne's artwork script, but it doesn't refresh properly and the lyrics are showing a strange 'double image' effect. There's no difference when having SMP's pseudo transparency checked or not.

Now if I do the same thing using a Panel Stack Splitter, ESLyrics and the DarkOne artwork script combo works fine.


Re: Spider Monkey Panel (foo_spider_monkey_panel)

Reply #1407
The problem is ESLyrics needs constant refreshing and I don't know how to do that in SMP. (I can do a one time refresh no problem)

I can do constant refreshing in PSS, however the coordinates have to be in per second and I get a slight flicker every second.

Re: Spider Monkey Panel (foo_spider_monkey_panel)

Reply #1408
This refreshes once per second but only if fb2k is playing.

Code: [Select]
function on_playback_time() }
    window.Repaint();
}

Use setInterval if you need it all the time even when playback is stopped.

https://theqwertiest.github.io/foo_spider_monkey_panel/assets/generated_files/docs/html/global.html#setInterval

Re: Spider Monkey Panel (foo_spider_monkey_panel)

Reply #1409
For anyone considering this component - don't.
This component should be flagged as crashware.

Today: open FB and wait... NOT playing, NOT browsing, NOT selecting, just letting it run in the background.

mem usage at launch: see image.

Console in this instance after some hours:

Code: [Select]
Components loaded in: 0:02.685906
Configuration read in: 0:01.462188
foobar2000 v1.6.18 [portable]
myInitStageCallback init
Querying last.fm: http://ws.audioscrobbler.com/2.0/?method=user.getRecentTracks&api_key=a1685abe5265b93cf2be4a70d181bf6b&user=mjm716&limit=200&format=json&from=1717374789&page=1
Minibar scanning S:\Jukebox Hero\Audio\B\Big Star\1972 #1 Record [R09]\01 Feel (1972).mp3
Track scanned in 2301.476 ms
Spider Monkey Panel v1.6.1 (Now Playing Bio: Biography v1.4.2 by WilB): initialized in 3605 ms
Spider Monkey Panel v1.6.1 ({AE0FC962-585E-4D7B-9F37-3732922F0080}: Biography v1.4.2 by WilB): initialized in 158 ms
Spider Monkey Panel v1.6.1 (Now Playing Discog: Find & Play v1.3.0 by WilB): initialized in 274 ms
Spider Monkey Panel v1.6.1 (now playing art: Biography v1.4.2 by WilB): initialized in 139 ms
Spider Monkey Panel v1.6.1 (Now Playing Review: Biography v1.4.2 by WilB): initialized in 123 ms
Spider Monkey Panel v1.6.1 (now playing other albums: Library Tree v2.4.0 by WilB): initialized in 428 ms
Spider Monkey Panel v1.6.1 (Selection bio: Biography v1.4.2 by WilB): initialized in 89 ms
Spider Monkey Panel v1.6.1 (selection Discog: Find & Play v1.3.0 by WilB): initialized in 15 ms
Spider Monkey Panel v1.6.1 (selection art: Biography v1.4.2 by WilB): initialized in 114 ms
Spider Monkey Panel v1.6.1 (selection review: Biography v1.4.2 by WilB): initialized in 124 ms
Spider Monkey Panel v1.6.1 (selection other albums: Library Tree v2.4.0 by WilB): initialized in 33 ms
Spider Monkey Panel v1.6.1 (Album Art: Find & Play v1.3.0 by WilB): initialized in 17 ms
WSH Panel Mod (Now Playing by marc2003): Parsing file "S:\Jukebox Hero\foobar2000\profile\js_marc2003\common7.js"
WSH Panel Mod (Now Playing by marc2003): initialized in 2866 ms
Spider Monkey Panel v1.6.1 ({3619C357-4FEF-4C7B-98E0-53FEE781BE3A}: Last.fm Similar Artists + User Charts + Recent Tracks by marc2003): initialized in 1384 ms
Spider Monkey Panel v1.6.1 ({E8C329D3-03E9-4ABF-A58B-871009A023E5}: Biography v1.4.2 by WilB): initialized in 58 ms
User Interface initialized in: 0:19.453834
foo_enhanced_playcount: loaded
FFmpeg version: 4.4.1
Autoplaylists initialized in: 0:02.028402
"Rating 3+" : 0:01.729934
"bitrate < 192" : 0:00.283116
Loading
Startup time : 0:47.951863
foo_spider_monkey_panel:
out of memory

Playing or selecting anything beyond this point results in FB crash with no report.

If I actually use FB, it will generally crash consistently somewhere between 15-25 plays (using shuffle tracks, and if SMP panels are visible in theme; if not visible, crash will take much longer).
Occasionally reports are generated by crashes also implicating SMP.

This has been my ongoing experience for more than 1 YEAR...  :'(
Wilb's panels are what makes using FB worthwhile to me, however SMP foundation is cursed   >:(

Components:
Core (2024-05-21 12:03:36 UTC)
    foobar2000 core 1.6.18
foo_bpm.dll (2015-03-01 03:39:58 UTC)
    BPM Analyser 0.2.4.6
foo_converter.dll (2024-05-21 12:03:12 UTC)
    Converter 1.6.18
foo_discogs.dll (2020-04-11 05:21:32 UTC)
    Discogs Tagger 2.23
foo_dsp_eq.dll (2024-05-21 12:03:10 UTC)
    Equalizer 1.2.2
foo_dsp_std.dll (2024-05-21 12:03:10 UTC)
    Standard DSP Array 1.6.18
foo_enhanced_playcount.dll (2023-03-23 02:56:32 UTC)
    Enhanced Playback Statistics 5.0.0
foo_facets.dll (2011-08-27 18:05:16 UTC)
    Facets 1.0
foo_fileops.dll (2024-05-21 12:03:10 UTC)
    File Operations 1.6.18
foo_flowin.dll (2022-03-27 03:50:52 UTC)
    Flowin 0.1.7 beta
foo_freedb2.dll (2024-05-21 12:03:10 UTC)
    Online Tagger 0.8
foo_input_std.dll (2024-05-21 12:03:20 UTC)
    FFmpeg Decoders 4.4.1
    Standard Input Array 1.6.18
foo_onewaysync.dll (2020-04-21 04:19:28 UTC)
    One Way Sync 0.7.0
foo_playcount.dll (2023-03-14 18:03:58 UTC)
    Playback Statistics 3.1.5
foo_preview.dll (2023-05-27 15:44:26 UTC)
    Preview 1.24
foo_rgscan.dll (2024-05-21 12:03:12 UTC)
    ReplayGain Scanner 1.6.18
foo_run.dll (2022-09-19 16:12:20 UTC)
    Run services 0.4.5
foo_scrobble.dll (2022-09-06 05:43:00 UTC)
    Scrobble 1.6.0.22456
foo_simplaylist.dll (2018-09-05 06:56:25 UTC)
    SimPlaylist 1.0
foo_spider_monkey_panel.dll (2022-01-13 15:29:00 UTC)
    Spider Monkey Panel 1.6.1
foo_textdisplay.dll (2011-08-18 21:01:03 UTC)
    Text Display UI Element 1.1 beta 1
foo_ui_std.dll (2024-05-21 12:03:18 UTC)
    Default User Interface 1.6.18
foo_uie_wsh_panel_mod.dll (2015-09-27 18:40:19 UTC)
    WSH Panel Mod 1.5.10
foo_unpack.dll (2024-05-21 12:03:14 UTC)
    ZIP/GZIP/RAR/7-Zip Reader 1.6.18
foo_verifier.dll (2023-04-17 18:43:48 UTC)
    File Integrity Verifier 1.4.3
foo_vis_vumeter.dll (2013-02-16 09:44:26 UTC)
    VU Meter 2013-02-16


Re: Spider Monkey Panel (foo_spider_monkey_panel)

Reply #1410
ehm... or Wilb's scripts need fixing xd just saying.

EDIT: I mean, SMP could handle a lot of situations a bit better to only crash the panel and not foobar2000. But Wilb's scripts are known to have some crashes lately, and no updates since months. Also out of memory logging clearly points to a script problem doing something which should not be done (or something in your theme ;)) or just a 32 bit limit and you using tons of panel or wrong settings... and there are other questionable design decisions here and there on those scripts anyway.

BTW ton of people are using bio scripts without such problems anyway. And for sure I can use foobar for an entire week with bio and no crashes (with fixes applied).

Re: Spider Monkey Panel (foo_spider_monkey_panel)

Reply #1411

BTW ton of people are using bio scripts without such problems anyway. And for sure I can use foobar for an entire week with bio and no crashes (with fixes applied).

Yes, I appreciate your feedback. But over the year I have certainly removed all of Wilb's panels independently and still end up with crashes. I have ~400K tracks so that certainly has something to do with it and exacerbates trouble shooting.

There are 2 sorts here, those that really enjoy the coding of FB, and those that care more about the music than tweaking. I'm much more the latter and frankly well beyond sick of debugging a f#$%ing music player.
Don't even get me started about Refacets.

Re: Spider Monkey Panel (foo_spider_monkey_panel)

Reply #1412
Well foobar is clearly not suited for 400K tracks in its 32 bits version, which is what we have to use for SMP. I have already reported multiple times there should be settings to tweak which tags are cached on v2 (instead of all), but they have been ignored for the moment by devs. It's also a waste of processing time and ram on 64 bits.

About your crashes without panels, that doesn't make sense. Are you saying SMP crashes the entire program when there are no panels being used? That would be new. Or just that foobar crashes for unknown reasons?

Also giving more info about the exact panels and layout used may help. i.e. Bio should crash with network request without the latest fixes, but it should not crash randomly. The library panel one may have problems with a 400k library (?)

Re: Spider Monkey Panel (foo_spider_monkey_panel)

Reply #1413
How much memory does fb2k/zero components/400K tracks use? I'm guessing with a collection that large, you probably have a lot less wiggle room than the average user.
How much more memory does adding a single SMP instance/library tree add on top?

Only then you can think about adding silly amounts of other instances. I counted 8 bios in that console output. There can be no good reason for that.

 

Re: Spider Monkey Panel (foo_spider_monkey_panel)

Reply #1414
I bet on the wrong horse - who ever imagined you keeping up JSP so well after all your Houdini routines!  :o (props btw!)
Memory at startup is displayed above, about 2,6GB - ridiculous, but to FB credit, it is very responsive when it doesn't crash. With only facets, mem at startup = 1,950

per image: 1-2-3-4 (x2 for now playing & selection tabs) I figured better to keep the same when possible rather than adding new variables to the mix.
If a tab is not displayed, is it still processing?

#4 which displays the Library items by (multiple) album artist is probably the culprit, or at least is the worst performer, but it is arguably my favorite.
I could prob use your image display for #2, but it's nice to click to switch between album/artist artwork.

Wilb's UX is simply superior to other options. @Regor, if you fixed bio code, I'd be happy to test it.

I've actually tried 64 v2 twice now, but Refacets is still a ***POOR*** copy of Facets and remains a dev blackbox and PITA to set up each time (how about at least attempting to port filters and settings Peter?!?!)

I believe last I tried, Refacets couldn't even handle this column properly:
$cut($if2(%releaseyear%,%date%),3)0s|[$year($if2(%releaseyear%,%date%))]
much less this one:
$if($greater($left($stripprefix(%album artist%),1),$char(65)),#,$caps($cut($stripprefix(%album artist%),1)))|$meta_branch_remap(album artist)