Skip to main content

Recent Posts

1
General Audio / Re: Advice on transformer hum
Last post by Arnold B. Krueger -
Well, as mentioned above this is a very highly regarded DAC and I do like the way it sounds - hence my efforts to address this problem rather than simply swap the DAC. But you are right, changing it for another DAC is always an option.

The statement that the "Limpizator" DACs are "...highly regarded..."  is strictly a matter of a tiny noisy pocket of personal opinon, and requires considerable Cherry Picking to arrive at.

From a technical standpoint, it is a DAC that is intentionally mis-designed and from the pictures, mis-constructed.  It is a blatant example of anti-technology, anti-craftsmanship and anti-engineering.

The most obvious example of mis-design is the the reliance on throwback anti-engineering, one major aspect  of which is the use of an obsolete DAC chip with far less than SOTA performance and elimination of the digital filter and aperture correction that was origionally part of its design. This issue is so strong that it leads to easily measurable frequency response errors that might even be audible.

I could point out that the DAC has tubes, that may look great to some but add expense, complexity, reduce reliability, and possibly hinder sonic accuracy. But this is a level of rationality that I expect to get no traction at all with rabid subjectivists. :-)

Another mis-design element is the avoidance of modern technology for building audio gear that is inherently free of hums and buzzes due to the power line.

The most obvious example of mis-construction is the choice of an inappropriate but inexpensive style of the power transformer, and its location.

If I were to be such a Luddite that any of this weirdness appealed to me, I'd obtain an inexpensive solid state DAC and an equalizer for a fraction of the trouble, size, energy consumption and expense, that had vastly greater flexibility, and the ready ability to remove the equalizer or at least zero out its controls should a burst of sanity ever enter my brain. :-)



2
General Audio / Re: Advice on transformer hum
Last post by pdq -
That you "like the way it sounds" is very suspicious. A DAC should not "sound" like anything. It should be simply the equivalent of a straight wire, and if you are attributing anything more to it then you are deluding yourself.

Please accept the advice that you have been given and replace this troublesome device with one that works just as well but does not cause the problems.
3
@kgena_ua

hi

version 171215 crashes on both panels (jscript + wsh)
[/img]
4
General Audio / Re: Advice on transformer hum
Last post by extracampine -
OK- if you are alright working with the unit while the case is off, if it were me I would be using a plastic straw and probably also a light metal rod, each pressed against the power transformers in the unit, with the other end at my ear. IOW, using them as a stethoscope to see which transformer is making the noise.

I think that it is the smaller transformer which I had identified above that is making the noise. I tried prodding it with a rod and also unscrewing it altogether and placing a bit of rubber underneath it though that didn't really seem to help.

Have you contacted the manufacturer regarding this issue?

Yes, I actually sent the unit back to the manufacturer for testing, and there was no hum evident there. I am going to take the DAC to a music shop or 2 this coming weekend to see if it hums there.

My advice is to get rid of that DAC, it's poorly made garbage.  It seems to be far more trouble than it's worth.  I can understand if it was antique or a collectable that is worth something then it maybe worth fixing but this doesn't appear to be the case here.

Well, as mentioned above this is a very highly regarded DAC and I do like the way it sounds - hence my efforts to address this problem rather than simply swap the DAC. But you are right, changing it for another DAC is always an option.

5
3rd Party Plugins - (fb2k) / Re: OpenMPT Module Decoder
Last post by deus-ex -
Enjoy the real configuration dialog (you'll need to change your settings from defaults again) [...]
I did not had to update the settings, those were transferred from v0.4.0-pre.3+1 to v0.4.0-pre.3+2. It might be noteworthy that I update foobar2000 and user components manually only, except for the initial installation of foobar2000 which probably makes a difference regarding the preservation of the settings.

[...] enjoy the new pattern visualization [...]
Awesome! After all these years we get to have a live pattern viewer. That's a neat surprise. Thank you very much!
Unfortunately I have to report a bug regarding the pattern visualization right away:

  • foobar2000 crashes upon attempt to advance the playlist when reaching the end of any module AND if the next playlist item is a module OR if the current module is going to be repeated
  • The crash does NOT occur if the next playlist item is not a module OR if the user forces to advance to the next/previous playlist item OR if the user creates/loads a new playlist before the currently played module reaches its natural end.


I'd like to suggest a couple items regarding the pattern visualization. I leave it to your expertise and motivation whether these are feasible, of course:

  • Color customization for the highlight bar
  • Font, style and size customization (foobar2000 default UI settings seem not to apply)
  • Option for continuous pattern display
  • Display presets for 4/8/16/32/64 channels with varying detail (similar to Impulse Tracker UI)
  • Context menu allowing for quick change of continuous pattern display and channel presets
6
3rd Party Plugins - (fb2k) / Re: OpenMPT Module Decoder
Last post by kode54 -
Try reducing or turning off volume ramping, but note that many XMs will sound bad without it, since the tracker implemented it and many composers assume it will be featured in the player.
7
3rd Party Plugins - (fb2k) / Re: foo_wave_seekbar
Last post by Zao -
I've also observed this GPU drain and have not really found any way to mitigate it if you still want smooth painting.
The choices available as a child window is very limited and the only way to reduce it is indeed to draw less often.

The GDI mode in foo_wave_seekbar has a much lower update rate than the other two frontends. foo_wave_minibar doesn't have any control at all, as it was made to not be complicated. The difference between GDI and minibar is strange, as they're pretty much the same kind of painting logic.

It wouldn't surprise me if this is something that newer Windows 10 builds introduced too, considering that I've never had any trouble in the past with either component.

As for resolving this, I've got no clue. Drawing rapidly as a child window in foobar2000 is a right mess and you have to either be wasteful or careful to not starve the message pump. It's one of the reasons why I never bothered to make any dockable visualisations as the perf just isn't there.

Edit: I wonder how to benchmark this... run a stable game on the side and see how much mud it sucks?
8
edit: I just tested it out:

- install wine (any version really, it's been working for me for several years, I'm currently using 3.0rc6)
- install wine-mono (or whatever it is called on your distribution)
- create a new win32 prefix (WINEARCH=win32)
- install dotnet20sp2 using winetricks. It shows a couple of errors (i.e. "mono not installed", even though it is), but the process finishes fine
- install vcrun2008
- copy the CUETools folder to your prefix/drive_c/Program Files/
- launch CUETools.exe with WINEPREFIX set to your prefix

It takes a while to launch, but it does launch fine. The only problem I had was that configuring it as I wanted crashed on some steps.
What I did was configure it as I want on a windows machine, then copy the settings.txt to my linux one.
is there any benefit to install wine-mono in first place when dotnet20sp2 gets installed right afterwards? afaik, mono is a replacement for dotnet and gets uninstalled by winetricks when you attempt to install dotnet anyways.
9
3rd Party Plugins - (fb2k) / Re: OpenMPT Module Decoder
Last post by Slender -
More a general OpenMPt question than anything, but I've noticed that modules that have short, chippy samples, such as dunderklumpen.xm by Loonie, have a bit of an attack added on to their samples, which can sound yucky with some modules, something that DUMB didn't do before. I'm curious why? Is it something the original tracker did? Additionally, the attack seems to be module dependent, chip 7.xm by Saxxonpike doesn't do it.
10
It's quite easy to do.

In foobar2000:
1. Right click on the range of songs you want to remove the tag from and click on properties.
2. Scroll down to the desired tag and right click on the name of the field and choose remove.
3. Click apply.

In MP3tag
1. Right click on range of files you wish to remove this tag from and choose "Extended Tags..."
2. Find the desired tag and highlight it.
3. Click the red X to the left of the album art.
4. Click OK.

Values to play with if you want to troll your friends:
0 = Off (no warning) (same as the tag not existing)
1 = Explicit Warning
2 = Clean Version