Dennis Han

For DSD or DSD+PCM, I use "ASIO+DSD: ASIO for USB Device." I've also used "WASAPI (event), (push), and (shared)" for PCM DACs, and, for those, the elapsed time indicators work; the indicators also work for "Default: Primary Sound Driver"; my Windows default driver is a PCM DAC. All of this is for playing SACD ISO files, DSF files, and PCM files converted by the DSD Processor; none show elapsed time while using the driver for my DSD64 DAC.

For DSD or DSD+PCM, I use "ASIO+DSD: ASIO for USB Device." I've also used "WASAPI (event), (push), and (shared)" for PCM DACs, and, for those, the elapsed time indicators work; the indicators also work for "Default: Primary Sound Driver"; my Windows default driver is a PCM DAC.

For DSD or DSD+PCM, I use "ASIO+DSD: ASIO for USB Device." I've also used "WASAPI (event), (push), and (shared)" for PCM DACs, and, for those, the elapsed time indicators work; the indicators also work for "Default: Primary Sound Driver."; my Windows default driver is a PCM DAC.

Elapsed Time Not Working

In my case, I always have a number followed by an alpha character, so I never noticed that print inserts spaces differently depending on the situation. Using a configuration setting would be helpful to have. I've found ways to make the changes faster with Notepad++, fortunately. I'm using version 5.4.4, which I thought was the preferred version once it was released yesterday. I'm using the Windows binary.

I have figured out how to make sprintf work for me, but the problem is I have probably 10,000 instances to fix that are not a simple search and replace. Making a command that operates the same as print had operated would be more helpful. Am I the only one to have a problem with the new print?

The text reports and configuration files have many hundreds of lines of unique text that can't be created with an array. Some of the text is numbers determined from equations. I probably should be using Perl instead, but gnuplot used to make this so easy to do.

Thanks for the reply, but I use gnuplot to create graphs and also to write text reports and configuration files for other software all with one large program. There's got to be another way. How about creating a new command called oldprint?