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: foobar2000 v1.1.11 beta (Read 26169 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

foobar2000 v1.1.11 beta

Reply #25
Track advance fading doesn't work for me. When is it supposed to fade out/in?

edit: Oh I see, it's like crossfading between tracks. But is it supposed to work on a manual track change?
"I hear it when I see it."

foobar2000 v1.1.11 beta

Reply #26
>> is it supposed to work on a manual track change?

yes, but not work here

it was working in older version by "advanced features"
Music is my first love.

foobar2000 v1.1.11 beta

Reply #27
Fade on seek is applied on manual track changes now.
Microsoft Windows: We can't script here, this is bat country.

foobar2000 v1.1.11 beta

Reply #28
Fade on seek is applied on manual track changes now.

Thanks, yeah that works. Imho, that's a bit confusing though.
"I hear it when I see it."

foobar2000 v1.1.11 beta

Reply #29
Problematic WAV files - thanks for the report, looks like it's some kind of a FLAC-specific problem, we can convert these to WavPack etc just fine, investigating.


It is due to fb2k using --ignore-chunk-sizes (I see that --ignore-chunk-sizes is not 1.11 news), and as Case points out (quoted below), it is a flac issue. Doing flac.exe --ignore-chunk-sizes dawn_in_space.wav from command line, produces a file which is bit-identical to the fb2k-converted files (which are corrupt). 

Now since FLAC returns both an INFO and an ERROR string using --ignore-chunk-sizes , it is hardly adequate of fb2k to give no warning whatsoever?




Porcus, your issue seems to be a bug in FLAC encoder's wav handling. The fix for 2GB issue I posted here also fixes this problem.


Replicated here. This exe file of yours yields a copy bit-identical to input even when --ignore-chunk-size is used. And it returns an INFO string but not any ERROR string.

foobar2000 v1.1.11 beta

Reply #30
Thanks, yeah that works. Imho, that's a bit confusing though.

Technically it is correct (manually changing tracks is "seeking to another track"), but I can see how this is unclear in this context. I'll change the dialog to be more clear about what each setting does.
Microsoft Windows: We can't script here, this is bat country.

foobar2000 v1.1.11 beta

Reply #31
hey...
just installed this beta version and already noticed an issue...

in previous versions, when I dragged some tracks from foobar into a folder (on the same drive), the files were physically moved from their folder into the new one... well in this version they're just copied, so they remain in the old folder and have to be removed manually...
also it would be nice if the songs' paths would change automaticaly after the moving action, so they can play without the user having to import them again from the new folder into foobar...
oh... and if it's of any relevance, i'm using Windows 7

foobar2000 v1.1.11 beta

Reply #32
foobar's File Operations component (bundled with the installer) is the preferred tool for moving and copying files, and has very flexible/powerful capabilities.  It can do everything you described in your post quite efficiently (give it a try    )

foobar2000 v1.1.11 beta

Reply #33
when I dragged some tracks from foobar into a folder (on the same drive), the files were physically moved from their folder into the new one... well in this version they're just copied

The old behavior was a bug. New behavior is what the player intended to happen. That is also the reason the playlist entries didn't change.

foobar2000 v1.1.11 beta

Reply #34
too bad it was just a bug... it could have been helpful in some cases...
indeed the Move to... file operation does it, but it's not as simple as drag&drop

foobar2000 v1.1.11 beta

Reply #35
I'm just curious about why fade on seek and fade on pause/stop was removed in the new beta?
Is the new crossfader supposed replace the fade on seek and fade on pause/stop?
I tried the new crossfader, but it does not fade on manual track change.
Using 1.11.b2

foobar2000 v1.1.11 beta

Reply #36
If you would go back and read the topic and/or change log, all fade settings have moved to the output page.

foobar2000 v1.1.11 beta

Reply #37
If you would go back and read the topic and/or change log, all fade settings have moved to the output page.


I did read the change log, but I missed that part about fading, thank you for your reply kode54

foobar2000 v1.1.11 beta

Reply #38
What about fading when resume playback after restarting?

foobar2000 v1.1.11 beta

Reply #39
Thank you very much for developing this excellent player. Unfortunately there is one change in 1.1.11 which for me is a big step back. I often change to a new track while one is still playing. With the fading as it worked before, this felt smooth and pleasant to listen to.

Now, the new track fades in as well. Fading in works well when seeking within a track. But when listening from the beginning, it often sounds very wrong or even unpleasant not to hear it completely from the start. Also, I find the default fade-out much too short, and increasing the fade length worsens the problem of skipping the start.

Please allow setting the fading to how it worked before.

foobar2000 v1.1.11 beta

Reply #40
what is track advance option for in fading.....



foobar2000 v1.1.11 beta

Reply #43
Looks like I'm gaving problems with 1.1.11 beta 3, the player always crashes after several minutes, unlike previous builds.

Code: [Select]
Illegal operation:
Code: 63D81B66h, flags: 00000001h, address: 765DB9BCh
Additional parameters: 00000D08h

Crash location:
Module: KERNELBASE
Offset: B9BCh
Symbol: "RaiseException" (+58h)

Stack dump analysis:
Address: 63D81B66h (foo_dumb+41B66h), symbol: "foobar2000_get_interface" (+2B896h)
Address: 765DB9BCh (KERNELBASE+B9BCh), symbol: "RaiseException" (+58h)
Address: 765E0C48h (KERNELBASE+10C48h), symbol: "WaitForMultipleObjectsEx" (+16Bh)
Address: 74811A2Ch (kernel32+11A2Ch), symbol: "WaitForMultipleObjectsEx" (+8Eh)
Address: 748141F0h (kernel32+141F0h), symbol: "WaitForMultipleObjects" (+0h)
Address: 74811136h (kernel32+11136h), symbol: "WaitForSingleObject" (+0h)
Address: 01242A70h (foobar2000+B2A70h)
Address: 63D81B66h (foo_dumb+41B66h), symbol: "foobar2000_get_interface" (+2B896h)
Address: 748141F0h (kernel32+141F0h), symbol: "WaitForMultipleObjects" (+0h)
Address: 74811136h (kernel32+11136h), symbol: "WaitForSingleObject" (+0h)
Address: 012A1E08h (foobar2000+111E08h)
Address: 012D7ED0h (foobar2000+147ED0h)
Address: 011C5A23h (foobar2000+35A23h)
Address: 7481339Ah (kernel32+1339Ah), symbol: "BaseThreadInitThunk" (+12h)
Address: 770F9EF2h (ntdll+39EF2h), symbol: "RtlInitializeExceptionChain" (+63h)
Address: 771371D5h (ntdll+771D5h), symbol: "WinSqmSetIfMaxDWORD" (+31h)
Address: 770F9EC5h (ntdll+39EC5h), symbol: "RtlInitializeExceptionChain" (+36h)
Address: 011C5950h (foobar2000+35950h)
Address: 011C5950h (foobar2000+35950h)

Environment:
App: foobar2000 v1.1.11 beta 3
UI: Default User Interface 0.9.5

foobar2000 v1.1.11 beta

Reply #44
Anakunda, the crashing you noticed should be fixed in the recently released beta 4 version.

foobar2000 v1.1.11 beta

Reply #45
i'm liking the update button on the new installer. 

foobar2000 v1.1.11 beta

Reply #46
Please allow setting the fading to how it worked before.


I want the same behavior as it was in 1.1.10 too.
I don't understand why the fading was changed in 1.1.11b, previous fading behavior has worked very well for so many years, why change it now?

foobar2000 v1.1.11 beta

Reply #47
Since the last formal announcement of beta 1, foobar2000 has been updated all the way to beta 4, which was released today (the 22nd). Here are the changelogs:

Quote
2012-01-19
foobar2000 v1.1.11 beta 2 released.
• Various beta 1 quirks have been sanitized.
• This version introduces an experimental deadlock detection feature - the application will automatically terminate and produce a crash report after long periods of apparent UI unresponsiveness.
• Please always send reports of any crashes that you encounter, chances are that they can be worked-around in the next version or forwarded to the developer of the problematic component.
• Cleaned up advanced preferences for MP3 tagging
↳ • “Force preferred tagging scheme” option gone - use the “MP3 tag types” dialog to convert between different tag types.

Quote
2012-01-22
foobar2000 v1.1.11 beta 3 and beta 4 released.
Various UI responsivity bugs have been fixed using the telemetry data from beta 2 - thanks to everyone who submitted crash reports.
Update: Now at beta 4. The short-lived beta 3 had a major stability problem that should be fixed now - special thanks to the 15 people who submitted crash reports so quickly.


foobar2000 v1.1.11 beta

Reply #48
in previous versions, when I dragged some tracks from foobar into a folder (on the same drive), the files were physically moved from their folder into the new one... well in this version they're just copied, so they remain in the old folder and have to be removed manually...


Hm... in beta 4 it still works like that for me - drag a song to another folder on same drive moves it, on different drive do a copy (same as in explorer, highly convenient).

Anyhoo - I've recently bought an android phone and when I connect it I can access the storage from the explorer, but I'm unable to copy files from foobar directly to the device, only via explorer copy-paste. Would it be possible to add such option?

foobar2000 v1.1.11 beta

Reply #49
For the crossfader, is it possible to split up the Seek & track change setting?


PS: sorry if this is a dumb question, but how/where do I submit crash reports?  Is it automatic?