Line Feed in Audio Device Name
A system-wide equalizer for Windows 7 / 8 / 8.1 / 10 / 11
Brought to you by:
jthedering
Menu
▾
▴
1 Attachments
#63 Line Feed in Audio Device Name
Here's a weird one. One of my audio devices has a \r\n in the middle of the device name. So when Equalizer APO attempts to pull the backup reg, it isn't able to and gives the error below:
"Error while opening file backup_Xpecial Audio
Stereo_Headphones.reg for writing"
I'm guessing that sanitizing the file path to exclude line feeds would solve this.
Yes, this is really a special case. The Configurator is already replacing many characters not allowed in filenames but I did not expect something like this.
@Jonas
A year ago or more I had an user who had a device name with an added space. This created also a problem but I'm sure that you have already thought of this.
Hi Peter, I don't see why an added space would be a problem when creating the backup file. Do you remember the forum thread maybe so that I can have a look?
Yep a very funny special case. It's a chinese bluetooth device and normally I would reprogram it to change the name ... but it's an unknown chip so that method is a no go.
Hi Jonas, after some extensive digging into the Peace forum I've found a ticket with the issue I referred too. It could have been an issue to Peace only. If so, I'm sorry.
Nonetheless, to summarize: A device called "Polk Hampden Speakers USB Audio DAC" had one or more trailing spaces. These added spaces can't be seen in the Windows audio device list nor in the E-APO configurator. When a user enters this device in a config file without these added spaces, what will happen then? Will it still be selected?
Thank you for searching. As I can see, the problem seems to have been Peace-only, as the user did not report any problems using the Configurator.
The string you give to the Device command only needs to be a substring of the device name, so added spaces do not do any harm. Spaces only serve as separators, so if you have
it will actually just search for those six words (the trailing spaces separate empty words, which are ignored) in the string <connection name> <device name > <GUID> and it should find the device. In this case, it would be sufficient to write just Polk for example to select the device. You only need to make sure that you do not accidentally also match other devices. That's why the Configuration Editor even includes the GUID.
Thanks, Jonas, for the detailed explanation. So there's no issue. Great.
I always add the GUID. Better to be sure to set the right device as you're saying.