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: foo_wave_seekbar (Read 799084 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

foo_wave_seekbar

Reply #350
That is impossible for now, as there exists no published interface to augment the toolbar.
Stay sane, exile.

foo_wave_seekbar

Reply #351
Looks great Zao.

Probably wanna move those tick boxes to the right a bit, they look too close to the edge of the group box at the moment.

foo_wave_seekbar

Reply #352
That's how a list view with checkboxes looks natively. I will not muck around with owner drawing or other ill stuff. I value my sanity.
Stay sane, exile.

foo_wave_seekbar

Reply #353
0.2.0 released, see OP for a glorious changelog.
Highlights include multichannel display, fancy configuration for said display, multichannel analysis, storage compression.
Stay sane, exile.

foo_wave_seekbar

Reply #354
Thanks Zao, looking good
Roughly I can't notice any difference in scanning speed which is great I guess

foo_wave_seekbar

Reply #355
Thank you! My Foobar looks so cool now with multichannel waveforms. 

This is a truly magnificent add on, keep up the good work Zao.

foo_wave_seekbar

Reply #356
Thanks for the update, Zao, works great.

foo_wave_seekbar

Reply #357
Thanks Zao.

Excellent addon.

foo_wave_seekbar

Reply #358
Very nice indeed.

foo_wave_seekbar

Reply #359
Thanks for the latest version Zao, and thanks for blocking scanning of last.fm radio tracks. It doesn't interrupt playback anymore, but unfortunately it seems to try and scan them when they are the next thing in the playlist, so some tracks get skipped when foobar tries to play them.

foo_wave_seekbar

Reply #360
Hrm, odd. There should be no difference whatsoever between how the current and next tracks are auto-scanned.
Can you PM me your console contents when this happens?
Also, what is the URL/location of the entries it occurs on? Are they lastfm://, http://, or other?
Stay sane, exile.

foo_wave_seekbar

Reply #361
thanks for blocking scanning of last.fm radio tracks.

Mine doesn't do that.  I'm using the latest 0.2.0 release, and I still get errors on Last.fm radio streams.  Any track that I select plays for a few seconds, then I get an error and it skips to the next track.  I'm using the Last.fm radio component, and the stream URLs begin with FOO_LASTFM_RADIO://.  If this protocol isn't automatically skipped, can it be?  Additionally, my http:// streams are also being scanned, but it's not causing problems (yet).

foo_wave_seekbar

Reply #362
I'll add those silly foo_lastfm_radio: and lastfm: protocols to the next version, but your HTTP claim bothers me.
Can you show a complete URL that it tries to scan together with the console output for it? If it contains sensitive fields like user/pass, censor those.
Note that messages like "Wave cache: skipping location ..." are from when the exclusion filter works. Any file that that message appears for will not be scanned.
Stay sane, exile.

foo_wave_seekbar

Reply #363
Hmm it's started skipping tracks again. But the seekbar doesn't say it's scanning them, here's the console log:

Code: [Select]
Last.fm Radio: Handshake successful.
Last.fm Radio: Retrieved track "Fushitsusha [Pathetique] - Pathetique Pt. 2"
Last.fm Radio: Retrieved track "The Gerogerigegege [Tokyo Anal Dynamite] - Track 73"
Last.fm Radio: Retrieved track "Ruins [1986 - 1992] - Praha In Spring"
Last.fm Radio: Retrieved track "High Rise [Live] - Mainliner"
Last.fm Radio: Retrieved track "Keiji Haino with Boris [Black, Implication Flooding] - a rise, a moment before something unexpected is on the verge of starting"
Opening track for playback: "FOO_LASTFM_RADIO://play.last.fm/user/edbbe0bdade3d7d9d26c5c07e6e8d6c4.mp3LASTFM"
Last.fm Radio: Problem opening track "FOO_LASTFM_RADIO://play.last.fm/user/edbbe0bdade3d7d9d26c5c07e6e8d6c4.mp3LASTFM" : Forbidden (403)
Opening track for playback: "FOO_LASTFM_RADIO://play.last.fm/user/67467814a3f56101b38f7b014791fe6d.mp3LASTFM"
Last.fm Radio: Problem opening track "FOO_LASTFM_RADIO://play.last.fm/user/67467814a3f56101b38f7b014791fe6d.mp3LASTFM" : Forbidden (403)
Decoding failure at 0:00.000 (Unsupported format or corrupted file):
"FOO_LASTFM_RADIO://play.last.fm/user/67467814a3f56101b38f7b014791fe6d.mp3LASTFM"
Opening track for playback: "FOO_LASTFM_RADIO://play.last.fm/user/a7890215f52583f3731a1c99d365026f.mp3LASTFM"
Last.fm Radio: Problem opening track "FOO_LASTFM_RADIO://play.last.fm/user/67467814a3f56101b38f7b014791fe6d.mp3LASTFM" : Forbidden (403)
Last.fm Radio: Updating playlist "lastfm://artist/灰野敬二"
Last.fm Radio: Problem opening track "FOO_LASTFM_RADIO://play.last.fm/user/a7890215f52583f3731a1c99d365026f.mp3LASTFM" : Forbidden (403)
Last.fm Radio: Retrieved track "Masonna [Release Your Mind Volume 2 (Disc 3)] - Spark"
Last.fm Radio: Retrieved track "Merzbow [1930] - Intro"
Last.fm Radio: Retrieved track "John Wiese [Soft Punk] - PS2"
Last.fm Radio: Retrieved track "灰野敬二 [A Challenge To Fate] - My Only Friend"
Last.fm Radio: Retrieved track "Sutcliffe Jügend [We Spit on Their Graves (tape 1)] - Kill, Kill, Kill!"

It has managed to play a couple of tracks OK now though...

They all seem to be FOO_LASTFM_RADIO://

foo_wave_seekbar

Reply #364
0.2.1 (see OP) now ignores stuff. Try it.
Stay sane, exile.

foo_wave_seekbar

Reply #365
Thanks for the update(s)!

foo_wave_seekbar

Reply #366
Since .2, it seems to randomly decide whether or not to draw the seekbar in the window. Sometimes it returns if I switch between dx9/d2d/gdi, but most of the times it's just gone now.
(Playing .ape files from within my library)

foo_wave_seekbar

Reply #367
Thanks very much Zao


foo_wave_seekbar

Reply #369
boombaard: Oh joy. There's always someone that fails horribly. What OS and machine are you on, and does it occur with older versions (preferably including 0.1.12, 0.1.13; back up your DB and configuration beforehand)?

Dandruff: There goes my assumption that "surely no-one will have really really short tracks".
The thought struck me when rewriting the analysis code, but I focused effort on things that mattered more. I might look into it if free time magically appears.
Stay sane, exile.

foo_wave_seekbar

Reply #370
boombaard: Oh joy. There's always someone that fails horribly. What OS and machine are you on, and does it occur with older versions (preferably including 0.1.12, 0.1.13; back up your DB and configuration beforehand)?

All previous versions worked fine (.12, .13, .14) running win7 x64 (ATI HD3300 chipset, recent drivers). Stopped working with .2, .21 not working also.
After some finnicking with the new options, however, I noticed that it was due to the files I was using.
Apparently files that are mono (that is, with identical l/r channels) but encoded as stereo are displayed in the Center channel rather than frontleft/right. I'd disabled all other channels yesterday, hence it didn't do anything.

foo_wave_seekbar

Reply #371
Dandruff: There goes my assumption that "surely no-one will have really really short tracks".


Yeah. I actually have quite a lot of such samples. So it would be nice to be able to browse them with waveform display too ...


I might look into it if free time magically appears.


Thanks! Much appreciated!



Another suggestion: What about a "Normalize waveform display" option to get quiet tracks displayed in full height too? Would help the visibility quite a lot I think ...

foo_wave_seekbar

Reply #372
I thought that the (mono) annotation on the center channel should be enough, but you've shown me wrong.
Yes, tracks with "legacy" single-channel waveforms will display in the center (mono) channel. Note that if a channel is not present, it will not take any place in the display, so there's no harm in having them all enabled.

I'd recommend rescanning your whole library if you want proper multichannel. There's a command in the menu under Library to do just that.
Stay sane, exile.

foo_wave_seekbar

Reply #373
Ahh, this was the problem with my short samples too. Now they show a waveform but in a very ugly way.



For http://www.freesound.org/download/60719/60...ct_Goa_Kick.wav I'm getting this display:

waveform-seekbar-goa-kick.png


Almost invisible/unreadable. Guess the line should be thicker ...

 

foo_wave_seekbar

Reply #374
In D3D/GDI, the line thickness is determined by the difference between the maximum and minimum amplitude within a 1/2048th of the waveform. As your waveforms are very short, 16000-30000 samples, it's working with segments 7-14 samples wide. There's not much variation there really.

You could use the Direct2D mode, as that draws a line at the upper and lower bound of the waveform, or edit the shader for Direct3D, artificially adding a constant factor to the waveform.
Stay sane, exile.