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: 1.3.4 beta discussion (Read 19268 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

1.3.4 beta discussion

Thanks Peter for the awesome update.

The only thing we talked about few months ago was the ReplayGain settings on Converter / Other, it's confusing because it's not called exactly like the one from the menu. I think you should add (by tags) after albums on Other as well.

1.3.4 beta discussion

Reply #1
In which way is it confusing? How else is it supposed to transfer existing ReplayGain data?

1.3.4 beta discussion

Reply #2
Confusing because the ReplayGain menu has "(by tags)" and the Converter doesn't and someone may assume that albums on converter means everything as a single album. That's it.

1.3.4 beta discussion

Reply #3
Hi,
May be it's intentional but I've notice in registry foobar2000 DefaultIcon for M4A pointed to MP4 icon.

1.3.4 beta discussion

Reply #4
Hi,
May be it's intentional but I've notice in registry foobar2000 DefaultIcon for M4A pointed to MP4 icon.

Good find.
Fixed, thanks for reporting.
Microsoft Windows: We can't script here, this is bat country.

1.3.4 beta discussion

Reply #5
Also, it's possible to add: Hold Shift + Minimize = Tray (like mIRC)? Thanks.

1.3.4 beta discussion

Reply #6
Anyone else having issues where the latest beta's stripping the Genre tag from M4A files during tag updates? This wasn't happening in 1.3.3, just 1.3.4b1. Reverted back to 1.3.3, issue went away.


1.3.4 beta discussion

Reply #8
Anyone else having issues where the latest beta's stripping the Genre tag from M4A files during tag updates? This wasn't happening in 1.3.3, just 1.3.4b1. Reverted back to 1.3.3, issue went away.

Found and fixed, thanks for reporting.

Regression caused by mangled "©gen" from shuffling source between different OSes for the upcoming iOS port
Microsoft Windows: We can't script here, this is bat country.

1.3.4 beta discussion

Reply #9
What parameter should I use on the command line to suppress the startup dialog about bad last shutdown?

Thanks for this feature!

1.3.4 beta discussion

Reply #10
File -> Preferences -> Advanced -> Tools -> Suppress bad shutdown dialog on startup


1.3.4 beta discussion

Reply #12
Nice to see RAR5 support is added. Thanks for that!
But it seems, that foobar crashes, if a RAR5 archive is created in solid mode.

Tested:
RAR4 > OK
RAR5 > OK
RAR4 Solid (4MB) >OK
RAR5 Solid (64M Dict) >Crashes after some tracks, while playing/seeking.

Sure, solid mode is uncommon in terms of music, because there is no real benefit,
but foobar should at least handle it. (even with an error message)

Note:
With RAR5, it is possible to use dictionary up to 1GB RAM.
Maybe there is a problem with the allocated memory...

Suggestion:
If this a bigger challenge to fix, maybe just post a error message in the console window like
"unsupported archive type (rar archive in solide mode)" or something like this, and skip solid archives.

Thanks.


*EDIT*
New Foobar has also a problem, reading older existing rar4 archives, from the music library.
(70% of them produce a error message in the console window "Location not parsable: archivename.rar ...")
Foobar 1.3.3 works correctly on this files.

1.3.4 beta discussion

Reply #13
Thanks for the feedback, I'm looking into it.

Unfortunately it looks like it's unrar.dll that is crashing, not my own code. My possibilities of debugging/fixing this are limited.

Regarding non working rar4 archives, I'm looking into it, probably some kind of a bug on my side.
Microsoft Windows: We can't script here, this is bat country.

1.3.4 beta discussion

Reply #14
Thanks for fixing:

http://www.hydrogenaud.io/forums/index.php?showtopic=106711


But the Information from "Information lookup" (freedb, MusicBrainz) isn't available anymore now (in 1.3.4 beta 1 & 2).

Before bug fixing this Information was in the cuesheet (in "Title", etc.); after bug fixing "Title" and other Metadate are not stored in the cuesheet. (The cuesheet is realy simple now  ).

Please store the Metadata from "Information lookup" in the tags of the generated flac-file.

1.3.4 beta discussion

Reply #15
I don't know where to say this so I'll just drop it here.
In 1.3.3, I think there's a glitch with the Spectogram visualization. If you start a song and play it and decide to pause it for a while, if you come back to it and unpause it, the spectogram will still to scroll but will show nothing. Re-clicking on the seekbar will fix it... until you pause it for a while again and unpause it...

My settings:
FFT: 2048
Channels: Unchanged
Style: Scrolling
Scale: Linear.

1.3.4 beta discussion

Reply #16
@Peter

I do some further testing of the current RAR problems.

RAR5 or RAR 4 without any compression > seems to work
RAR5 with compression > crashes sooner or later
RAR4 or RAR5, with files that has the "read-only" fileattribut "r", produced the "Location not parsable: archivename.rar ..." in the console window. (V1.3.3 can handle this)

hope that helps a bit to fix this.

Feature Request:
Please add support for rar archives with renamed extensions or by magicbytes.
For Example "Bandname.rar" or "Bandname.music" or "Bandname.xyz"
Thanks.

1.3.4 beta discussion

Reply #17
Meanwhile FFmpeg 2.4 "Fresnel" was released.

"The most important thing in this release is the major version bump of the libraries.  This means that this release is neither ABI-compatible nor fully API-compatible."

1.3.4 beta discussion

Reply #18
If you start a song and play it and decide to pause it for a while, if you come back to it and unpause it, the spectogram will still to scroll but will show nothing.

This is normal and has happened for all visualizations since forever. Unless it's been changed since 1.2.2 (my version), and has regressed in 1.3.3

1.3.4 beta discussion

Reply #19
If you start a song and play it and decide to pause it for a while, if you come back to it and unpause it, the spectogram will still to scroll but will show nothing.

This is normal and has happened for all visualizations since forever. Unless it's been changed since 1.2.2 (my version), and has regressed in 1.3.3

Actually, the normal behavior I always saw is that it starts empty for a second then picks up again automatically. Right now, it just doesn't pick up again until a new song comes in or I seek through the song once.

1.3.4 beta discussion

Reply #20
Ah, ok.

1.3.4 beta discussion

Reply #21
Bug with read-only files in the RAR achive, acknowledged and fixed for beta3.

Cannot reproduce the rar5 crash here, will keep trying. Any additional information about how to reproduce this is welcome.
Microsoft Windows: We can't script here, this is bat country.

1.3.4 beta discussion

Reply #22
@Peter

can't reproduce the crashes. currently i'm not sure, if the crashes was produced by the rar files i drag'n'dropped to the playlist,
or it was the background thread, that scanned the whole library (~ 1000) rar files, that contains files with a read only flag.

But, if foobar was crashed, than this seems to happend everytime, while seeking a song.



1.3.4 beta discussion

Reply #23
Bug with read-only files in the RAR achive, acknowledged and fixed for beta3.

Cannot reproduce the rar5 crash here, will keep trying. Any additional information about how to reproduce this is welcome.

Hey Peter can you look into my low-priority issue with the Spectogram visualization?

1.3.4 beta discussion

Reply #24
Hey Peter can you look into my low-priority issue with the Spectogram visualization?

Sorry, tried but it does not happen here, please specify additional details. How long do you have to pause in order to get it? If you have more than one visualization open at a time, does it affect all of them or just the spectrogram? What output method and DSPs are you using? [DSPs and outputs affect audio timing info which is critical for visualizations to work correctly]


Regarding RAR crashing, it's been fixed - it seems unrar.dll is complete **** - it's not even multi thread safe, I made sure we only call it from one thread at once. New beta soon.
Microsoft Windows: We can't script here, this is bat country.