Tutorial for Setting up XXhighend

[manueljenkin]

This is a set up tutorial for XXhighend. It is a high fidelity music player with optimizations for low system noise and comes with a custom interpolator called Arc Predict.

http://www.xxhighend.nl/

 

WARNING: This tool will require changes to the windows registry (automated) and can sometimes cause instability issues. Use it at your own risk. I don't recommend trying it on your primary PC, especially if you have any critical work or personal files without a backup. I recommend first trying on a spare PC to get used to the quirks.

 

Requirements
1. PC/Laptop running Windows
2. Dotnet 3.5
3. A Dac with drivers installed (preferrably with high sample rate support)

 

Setting up your PC for XXhighend
1. For the first run, preferrably load some music into the Music folder in your PC for ease of access.
2. Download for the XXhighend (latest version 2.11) is available in the above link. Download and Extract the zip file to a folder in your PC (preferrably desktop) as shown.
3. If running Windows 10 or 8, download and install Dotnet 3.5. This is a pre requisite for the tool to work.

 

Setting up your DAC: Connect your DAC to the PC and make sure you have your DAC drivers installed. After this a couple of settings shall be tweaked for optimal performance.

 

A. Setting up buffer and volume: The Control Panel for the DAC will have options to set the buffer size and priority. For initial trials, it is recommended to set the Buffer Size to the maximum permissible limit and set mode to "safe" as shown in image below.

 

 

XXhighend comes with a digital volume controller that is integrated to the Arc Predict and other features for less truncation/quantization error after interpolation. Using Windows or DAC volume controller on top of XXhighend volume control can produce unoptimal results due to increased truncation errors. Recommended to set the Windows Volume and DAC volume to 100% for best experience.
 

Some DAC may integrate their volume control settings to windows volume control (especially if running in ASIO) and in that case setting Windows volume to 100% will also set DAC volume to 100% which is the recommended option.

 

 

B. Setting up DAC filter: XXhighend comes with an interpolation filter called Arc Predict. Arc Predict is optimized to minimize pre-ring artefacts and is optimized for better temporal signal structure. When enabled, Arc predict will provide higher sample rate input to the DAC and bypass or reduce reliance on the internal filters in DAC. Arc predict is different from common filters used in most DACs and hence there will be noticeable change from the stock configuration of the dac (for the better imo). Proper matching with the oversampling/interpolation filters present in the DAC is necessary for best experience.

 

B1. If your DAC is based on R2R architecture (or similar), chances are it has an option to fully bypass its internal interpolation filters. This is generally provided as an option called NOS (Non Oversampling). It is the optimal choice to pair with XXhighend.

 

B2. In case your DAC is based on Delta Sigma architecture (or an R2R but without NOS option), it might come with a choice of different filters. The optimal choice for XXhighend Arc Predict will be filters that are concentrated to compact time. These filters would have no pre-ring (or very minimal), little or no post ring, and slow roll off in frequency response (filters concentrated in time will inevitably be spread in frequency and vice versa). The diagram below explains the optimal and less optimal filter choices to pair up with xxhighend, in case NOS is not an option.

 

 

Optimal filter choices for modern ESS dacs would be "minimum phase slow roll off", as it is compact in time domain. For modern AKM dacs, the optimal choice would be "slow" filter.

 

Less ideal are filters with pre-ring (sinc, brickwall, linear phase, etc) and filters with sharp band transition (and hence spread out time domain response) as they will affect the temporal benefits offered by Arc Predict.

 

Some Delta Sigma dacs come with a "NOS EMULATION" mode, I don't recommend this for initial setup since the actual implementation for random signals is not very clear in these DACs.

 

Setting up XXhighend:

 

1. Double clicking on XXHighEnd.exe as shown below will open XXhighend Player. During the first run it will seek permission for access to windows registry. As mentioned earlier this is necessary for the tool to perform its functionality. Sometimes windows might throw a diagnostic warning message during the first run, this is normal and pressing continue will take you to the XXhighend program.

 

 

The player might take a while to open. Patience is key to ensure proper functionality. It should open in a couple of minutes. If it doesn't open after a while, try double clicking XXhighend.exe again to open a new instance.

 

2. Once XXhighend is open, it is time to do some basic initial set up. The region marked in GREEN (top-center) in the figure below holds 4 tabs. P - Current Playlist, L- List of Playlists, S- Settings (and H, the utility unknown to me). Clicking P will open playlists tab, clicking L will open List of playlists tab and clicking S will open settings tab. Settings tab will occupy the lower portion of the screen, and to come out of settings, click the P or L tab.

 

 

3. Configuring Settings:

a. Add the music folder to the Music root entry

 

b. Scroll down in settings to find the configuration options for the DAC. As shown in figure,

i. In the Output Field, Choose the DAC to use. It is preferable to use the KS mode if the DAC entry shows up in KS option. Else general should be fine.

ii. In Device buffer size, select the buffer size you have configured on your DAC's control panel and press Refresh.

The maximum limit in the XXhighend Settings panel is 4096. In case your DAC buffer is set to more than 4096, there is a separate method (Q settings) to multiply on this setting which will be described in the next paragraph. In this case, keep your DAC's Control Panel settings at full level (in my case 32768) and keep the XXhighend Device Buffer Size field at 4096.

iii. In DAC settings Field, choose the maximum sample rate supported by your DAC. For first trial, I recommend 384kHz 32 bit for modern dacs even if it supports 768khz sample rate. After confirming that the tool works at 384kHz, you can experiment with 768kHz sample rate.

For "at >16 bits" field, recommended option is to choose 32 bits for modern dacs.

 

 

4. Exit settings by selecting the P (current Playlists) tab. If your DAC buffer was below 4096, skip this step. If your DAC buffer was above 4096, Press Q at the bottom (below play/stop commands), as shown in the figure to open Buffer Multiplier settings.

 

 

xQ1 acts as multiplier on top of the (Device buffer size) Field set in the Settings. Choose xQ1 such that "Device Buffer Size" x "xQ1" = DAC's Control Panel Buffer Size. In this example, the DAC's control panel buffer Size was 32768, and Device Buffer Size in XXhighend Settings was 4096. Since,4096*(8) = 32768, xQ1 was set to 8.

 

 

X1 is another multiplier to set the total SFS size. The default is 14 and I recommend keeping it the same for initial trials (here I have set it at 21). Press X (marked in Blue) to exit the Q menu.

 

5. In the Top Left (Purple) is menus for accessing Volume Control, Volume Normalization, Interpolation Ratio, Interpolation Algorithm, etc. If an option is marked Red, it is ON. and if it is marked Blue, it is OFF.

 

For first run I recommend to keep "Arc Predict" and "fx" ON and the rest off (this is the default configuration of the player).

 

The Scroll wheel at the left is for Volume and the level is indicated at top (in dB, with 0dB being full scale). Initial setting is at -36dB, slowly raise the value to comfortable listening level. During playback the volume control works in increments, and sudden jumps/dragging the slider will not work. Each click will give an incremental increase in volume. There is a small latency associated between request to increase volume and it being reflected in playback (depending upon the overall buffer).

 

The slider below fx sets the interpolation multiplier ratio. The default value of slider is at 4 (middle) and with fx ON, this will give an output with a sample rate of 44100 x 4 = 176400 (or 192000 if input music is 48000khz sample rate). The slider can take values 1 (left end), 2, 4, 8, 16 (right End).
 

In the example, the dac settings are chosen at 384000Khz so the slider is set to 8, as 48000 x 8 = 384000.

 

 

6. Time to play some music. Press Explore, marked in Blue in the Figure (present at the bottom right) to bring up the file/folder explorer.

 

 

If the test songs were stored in music folder, select the Music folder in the explorer. The music files will be imported to the left bottom side of the player (below the volume control and interpolation options).

 

 

After the music files are imported, dragging and dropping into the middle window will add it to the current playlists for playback.

 

 

Press the Play button to play the music. Make sure to keep control of Volume in safe listening levels! The image above shows a setting with Unattended Playback ON (Red). During the first run it is recommended to keep Unattended Playback off (Blue) to check if all settings are proper.

 

After confirming proper playback in normal mode, try Turning ON Unattended Playback (Red) for even lower noise playback. Make note of the shortcuts.

 

Alt + u = Volume up, Alt + d = Volume Down, Alt + s = Stop, Alt + x = close unattended mode. (u = up, d = down, s = Stop, x = close).

 

It is preferrable to first stop the playback using (Alt + s) before exitting using (Alt + x) to ensure system stability during the transition.

 

 

 

Some guidances for Further Tweaking if interested.

 

1. XXhighend 2.11 is optimized with unattended playback enabled as the target, and attended playback is there for functional testing. In attended playback version 2.11 can sound a tad bright. If unattended playback feels uncomfortable, I recommend trying out version 2.10 instead. It doesn't seem to have much brightness in attended playback, but imo version 2.11 with unattended playback sounds better than 2.10 with or without unattended playback.

 

Note: In case you experience glitches like removal of background wallpaper it is likely because of compatibility issues with windows 10 build version. XXhighend will likely be functional on most windows installations but there is possibility of encountering some gliches as described above in certain configurations. Xxhighend 2.10 and 2.11 is best used with Windows 10 build 14393.0 for better stability.

 

Also, if any other software audio tweaks had been set up in your windows installation (especially ones involving re-configuration of windows registry and/or disabling specific background system tasks) it is recommended to revert those changes before using XXhighend as it can clash with XXhighend procedure and cause stability and compatibility issues.

 

2. The buffer settings chosen in both DAC and XXhighend for this demo is a mere guideline. For best performance, it is suggested to start from highest buffer in both and tweak from there to find an optimal configuration. Higher Buffers cause less of total data fetch, but each data fetch contains larger data which will imply lower periodicity of access noise, but each noise spike can be higher. On the other hand lower buffers, will have higher periodicity of access noise but each noise spike can be of lower level. Note that these effects may not scale linearly due to intrinsic lack of determinism in modern systems due to use of differing paging algorithms and inter-processor scheduling. The optimal position would be to find the sweetspot that minimize the overall impact of this noise in the analog circuits, by either globally minimizing noise, or by detuning the noise to become uncorrelated. As can be seen, this will vary from system to system, depending upon the choice of CPU, RAM, motherboard, cables, connected accessories and even the electromagnetic spectrum in the ambient environment.

 

3. The choice of optimal filters for DAC is a mere guideline as well. The overall end result will depend also on how stable the system is with each of these filters, and also about the precision of implementation of these filters and how they interact with the noise shaping profile of the DAC. All other indexes matched, NOS > temporally concentrated (hence spectrally distributed) filter > temporally distributed filter in terms of compatibility with XXhighend. But it cannot be guaranteed, "all other indexes matched" happens in reality, as either system stability may change, or even the DAC manufacturer may choose to pay higher attention to detail on specific filters (say linear phase, which is less optimal for XXhighend) leaving out the others (say minimum phase apodized, which is more optimal for XXhighend) to merely exist as a choice and this could affect the overall analysis and comparisons. Hence it may be worthwhile to experiment with other filters in case the filters suggested in the beginning of the thread don't give good results.

 

4. Arc Predict Interpolator is optimized for real world sounds and analog synths. For EDM, Generic digital synths, or brickwall or compressed music, it would be optimal to disable Arc Predict Interpolator and use Anti-Image Instead (or bypass oversampling if you didn't prefer anti-image either). There are other configuration options in XXhighend that has not been described in this post (example : Peak Extend, iPhase, Anti Image, Minimize OS). There are also options in settings to disable different windows system tasks, etc. These may be explored on personal interest. @PeterSt may explain these better.

 

Happy Listening!

[manueljenkin]

Note: Keep this thread only for discussing different settings and computer hardware and DAC buffer/filter configurations, and preferably avoid any technical/performance discussion. Opinions/impressions of filter choices may be fine.

 

The choice of filters recommended above are in relation to usage with XXhighend and not related to any global preference for all scenarios.

[Norton]

Thanks for this @manueljenkin.  One thing I’m not clear on is that you are setting buffer size using the ASIO control panel for  your DAC, but AFAIK XXHE doesn’t use ASIO (On the other hand I’ve always wondered how you are supposed to know buffer size so it would be good to learn)

[PeterSt]

Manuel, thank you for this enormous effort.

 

I will try to jump in where it deems needed, and I will already do so because you asked me to. I will be happy to do so.

Peter

[manueljenkin]

45 minutes ago, Norton said:

Thanks for this @manueljenkin.  One thing I’m not clear on is that you are setting buffer size using the ASIO control panel for  your DAC, but AFAIK XXHE doesn’t use ASIO (On the other hand I’ve always wondered how you are supposed to know buffer size so it would be good to learn)

I don't think the control panel settings for the DAC works exclusive to asio. A buffer will be needed for asynchronous mode audio, be it asio, wasapi, kernel streaming or ALSA. So I think that should be fine.

 

I am unsure fully how USB audio protocol works but I believe there will be specific frames sent during enumeration (or before song playback) that can configure the settings for buffer, digital volume control, filter selection, clock select (if any, to match with sampling frequency multiple) etc. Buffer settings made in the dac control panel likely refers to the buffer size to be used in the dac (of course it'll be finite, some dacs will have only 1024, some dacs lesser, some 32768, etc). I am not sure if there are ways to bypass this and set the buffer size through specific playback software in windows. In Linux you can configure these buffer settings in ALSA and if you can handle alsa directly through software then you should be able to configure it on the fly. Maybe that's what kernel streaming does too, and if that's the case then the settings in the Dac control panel will not affect how xxhighend handles the data. However, it will be worthy to check settings to ensure that you don't insert a setting in xxhighend more than what the dac can take (Otherwise it cause buffer overrun I think). @PeterSt Does Kernel Streaming Buffer size set in xxhighend directly control the buffer size to be set in the DAC?

 

The settings for XXhighend refer to the size of the SFS that will be made in the RAM for playback. It will make a chunk that's of (Q1) x (xQ1) x (Device_buffer_size). The internal structure of this single SFS, I think it is a series of Q1 blocks each of size (xQ1) x (Device_buffer_size). @PeterSt can confirm and correct if there is any mistake.

 

The sequence I think follows this way: system storage (SSD/hdd/RAMdisk) -> RAM buffer (set in xxhighend settings) -> Dac buffer (set in dac control panel). 

[PeterSt]

7 minutes ago, Norton said:

you are setting buffer size using the ASIO control panel for  your DAC,

 

Norton, what you there literally say is correct: "An ASIO Control Panel". So what Manuel refers to is the "Control Panel" a Pro DAC comes along with, because in there you can change buffer sizes. The ones specifically for ASIO are useless for XXHighEnd, as indeed XXHE does not make use of ASIO.

 

Also:

 

17 hours ago, manueljenkin said:

X1 is another multiplier to set the total SFS size.

 

This is not correct because the SFS (Split File Size) is not related to the buffer size Manuel talks about regarding the "Control Panel".

BUT:

The buffer size as settable in the Control Panel is also not the same as the buffer size as settable in XXHE like 

 

This summarized, we have three "buffer sizes" by Manuel addressed as one:

- The SFS (Split File Size);

- The one in the (Driver) Control Panel (not ASIO);

- The one from the screenshot above, which relates to Q1 and xQ1.

Each have totally different effects, hence will change the sound in a very different way and in an interacting way (one could attest "sadly" but this is really how I myself already am tweaking the sound for more than a year in the same XXHE version).

[PeterSt]

5 minutes ago, manueljenkin said:

RAM buffer (set in xxhighend settings)

 

FYI: It is not a good idea to make up your own phenomena, like you do there. All these "buffers" (etc. etc.) already have been given names, and if you'd be able to scroll through ALL the Release Notes, you will see how it works and that the naming is correct and consistent.

 

Device Buffer Size indeed relates to USB *if* you would be using a USB interface. So for example, the USB Buffer Size can be 60MB (yea, you read right) or so. Notice though, that such buffers always resize on the side of the PC (never in the DAC - or they are not addressed by XXHighEnd anyway). This is more tricky when you use WASAPI, because that surely implies a buffer wich cooperates with the DAC (and Yes, Q1 works totally different for WASAPI opposed to for Kernel Streaming). The Device Buffer Size sits in the middle as a "shared" buffer. Anyway, it indeed always is part of the calculation of DevBufSize x Q1 x xQ1. Still Q1 on its own is special and its usage is not linear in WASAPI (it is for KS).

 

You don't need to know which is which, as you can't control sound with that. You can learn, however, which controls sound in which fashion. It is also good to know that whatever buffer involved, they oscillate with each other. Oscillation can imply a fixed resonance, or a slowly shifting one (program a synthesizer and you know what I'm talking about - tune two oscillators against each other).

[manueljenkin]

9 minutes ago, PeterSt said:

 

FYI: It is not a good idea to make up your own phenomena, like you do there. All these "buffers" (etc. etc.) already have been given names, and if you'd be able to scroll through ALL the Release Notes, you will see how it works and that the naming is correct and consistent.

 

Device Buffer Size indeed relates to USB *if* you would be using a USB interface. So for example, the USB Buffer Size can be 60MB (yea, you read right) or so. Notice though, that such buffers always resize on the side of the PC (never in the DAC - or they are not addressed by XXHighEnd anyway). This is more tricky when you use WASAPI, because that surely implies a buffer wich cooperates with the DAC (and Yes, Q1 works totally different for WASAPI opposed to for Kernel Streaming). The Device Buffer Size sits in the middle as a "shared" buffer. Anyway, it indeed always is part of the calculation of DevBufSize x Q1 x xQ1. Still Q1 on its own is special and its usage is not linear in WASAPI (it is for KS).

 

You don't need to know which is which, as you can't control sound with that. You can learn, however, which controls sound in which fashion. It is also good to know that whatever buffer involved, they oscillate with each other. Oscillation can imply a fixed resonance, or a slowly shifting one (program a synthesizer and you know what I'm talking about - tune two oscillators against each other).

Thank you Peter. I'll correct it in subsequent posts. I'm still learning the intrinsics with respect to buffer management choices.

[PeterSt]

18 hours ago, manueljenkin said:

WARNING: This tool will require changes to the windows registry (automated) and can sometimes cause instability issues. Use it at your own risk.

 

Although I an sure that this may happen, I never had a single report from anyone *that* this happens. However, there is a crucial prerequisite: Use the Windows version which XXHighEnd anticipates. This is never beyond W10 version 14393.0. Versions prior to that are always named an anticipated (for W10) but it is useless to name them now because they sound worse anyway.

Moral: Don't attempt any newer version than 14393.0 (and also not an other 14393.x).

 

The Minimized OS which XXHighEnd is capable to make in real time, explicitly anticipates prior Registry hacks or Changes and it will always revert back to those when you go back from Minimized OS to Normal OS. However, because the self-changes in the Registry are not anticipated on, you may be ensured that the consistent result of what XXHE creates, is not by any standard form. What I am saying is that all XXHE users can communicate with each other over settings, which will not be possible if one has some special hack applied which obviously the others don't know of. And really, nothing is needed because all what's in XXHE is all what can be done (OK, as far as I can tell). An extreme example: Using a "core" Server version is also not needed because in MinOS and Unattended playback, all what is there "is" a Server version (without OS UI etc.). But when Playback stops all reverts to normal (within MinOS which is still that and nothing like Normal OS).

 

14393.0 can be obtained though me, if needed (sales phasure com).

 

None of the versions officially supported show stability issues of any kind and you can even do normal office work. However, always *know* that Driver Installation of whatever kind, can only happen in Normal OS mode.

Might one work in MinOS for office work, you will see that your laptop is 10 times faster.

As Manuel advises, it is NOT a good idea to do office work on the Audio PC as such, because it will interfere with stable sound. But that is another matter ... (you will be making your OS thicker again by unnecessary (for audio) installs.

[manueljenkin]

6 minutes ago, PeterSt said:

 

Although I an sure that this may happen, I never had a single report from anyone *that* this happens. However, there is a crucial prerequisite: Use the Windows version which XXHighEnd anticipates. This is never beyond W10 version 14393.0. Versions prior to that are always named an anticipated (for W10) but it is useless to name them now because they sound worse anyway.

Moral: Don't attempt any newer version than 14393.0 (and also not an other 14393.x).

 

The Minimized OS which XXHighEnd is capable to make in real time, explicitly anticipates prior Registry hacks or Changes and it will always revert back to those when you go back from Minimized OS to Normal OS. However, because the self-changes in the Registry are not anticipated on, you may be ensured that the consistent result of what XXHE creates, is not by any standard form. What I am saying is that all XXHE users can communicate with each other over settings, which will not be possible if one has some special hack applied which obviously the others don't know of. And really, nothing is needed because all what's in XXHE is all what can be done (OK, as far as I can tell). An extreme example: Using a "core" Server version is also not needed because in MinOS and Unattended playback, all what is there "is" a Server version (without OS UI etc.). But when Playback stops all reverts to normal (within MinOS which is still that and nothing like Normal OS).

 

14393.0 can be obtained though me, if needed (sales phasure com).

Thank you Peter. I made this thread to help first time users who are trying out the demo. Asking to change OS build will be a little too much to give a try for the tool. If they are convinced (which I feel they will), then they can look further into the posts to see which build is most optimal for which xxhighend version.

[PeterSt]

18 hours ago, manueljenkin said:

After confirming proper playback in normal mode, try Turning ON Unattended Playback (Red) for even lower noise playback.

 

This is correct. Notice, however, that Unattended Playback shuts off all the Services and processes it can, according to your own settings (in the [S] tab). Now, in Normal OS this takes a relative ages to do because so many Services etc. still run there and they all need to be shut down and be confirmed that they have been shut down indeed before playback commences.

In MinOS most of these services have been shut down natively at boot, and thus now don't take time to shut down. Except for a first time per listening session, it now takes 1-2 seconds only (depending on your settings of what to shut down).

 

 

Warning : MinOS is only available with a licensed version (72 euros).

 

And yes, only yesterday I learned that Manuel's observations of XXHighEnd sounding "a best" came from an unlicensed version. Hence most of the SQ improvements can't even be done there.

[manueljenkin]

2 minutes ago, PeterSt said:

 

This is correct. Notice, however, that Unattended Playback shuts off all the Services and processes it can, according to your own settings (in the [S] tab). Now, in Normal OS this takes a relative ages to do because so many Services etc. still run there and they all need to be shut down and be confirmed that they have been shut down indeed before playback commences.

In MinOS most of these services have been shut down natively at boot, and thus now don't take time to shut down. Except for a first time per listening session, it now takes 1-2 seconds only (depending on your settings of what to shut down).

 

 

Warning : MinOS is only available with a licensed version (72 euros).

 

And yes, only yesterday I learned that Manuel's observations of XXHighEnd sounding "a best" came from an unlicensed version. Hence most of the SQ improvements can't even be done there.

It sounded fantastic even without MinOS. I can only wonder how much better it can get 🤩😍. I'll be sure to try the full version on optimal windows 10 build and update in my other thread.

[PeterSt]

7 minutes ago, manueljenkin said:

Thank you Peter. I made this thread to help first time users who are trying out the demo. Asking to change OS build will be a little too much to give a try for the tool.

 

Thank you. Yes.

But it will be more frustrated to end up in a black screen without possibility to escape from that, only because you applied something which apparently was not allowed.  So because you (Manuel) got this working so nicely, you may be the one who knows what to do and what not to do. You should list that.

Notice that this could already be as easy as not going to MinOS, which you can't anyway without license. I really can't tell.

 

Not using Unattended (where the UI is removed) could also help, but again, I don't know. So hopefully you do ?

[manueljenkin]

6 minutes ago, PeterSt said:

 

Thank you. Yes.

But it will be more frustrated to end up in a black screen without possibility to escape from that, only because you applied something which apparently was not allowed.  So because you (Manuel) got this working so nicely, you may be the one who knows what to do and what not to do. You should list that.

Notice that this could already be as easy as not going to MinOS, which you can't anyway without license. I really can't tell.

 

Not using Unattended (where the UI is removed) could also help, but again, I don't know. So hopefully you do ?

I just followed the steps I described in the first post of this thread. It has worked well for me and I've tried it again after formatting my system and worked fine again. I also have others who got it running following this method with unattended playback working. I'm not sure what version of windows 10 build each one of us are running but all of them are likely to be above 14393.0

 

The only glitch I experienced was it removed my windows wallpaper but it's a non issue for me.

[PeterSt]

 

 

What you see here is the special "Explorer" made for music files, from version 2.11. I never even explained it over at Phasure and I think I may grab the opportunity to do so over here at A/S, later. For now, however, two things are good to know:

 

The button where the green arrow points at, has a small icon in the top-right. This means it can be right-clicked and new functionality appears. In this case that will be normal Windows Explorer. And because people might be more convenient with that one ...

 

 

 

 

[LowOrbit]

Manuel

 

Great work. I haven't used XXHE for some time now, but this covers all the bases for getting started.

 

I did find Peter's work provided some very good results, but always found it a bit finicky to get right and a dedicated computer is pretty much eesential given the extent of modifications required.

 

I have wondered often about revisiting, (haven't used XXHE since before migrating to Windows 10) but not sure if my license would still be valid.

 

A lot of effort went into your tutorial above, I hope someone finds it helpful.

 

Mark

 

[PeterSt]

19 minutes ago, LowOrbit said:

I have wondered often about revisiting, (haven't used XXHE since before migrating to Windows 10) but not sure if my license would still be valid.

 

Mark, if you have a license for 2.xx (introduced in 2015) this would still be valid. And as always, you can re-obtain a Code as much as you want (the license money being refunded right away, or given by other (email) means) without paying.

 

Peter

[LowOrbit]

1 hour ago, PeterSt said:

 

Mark, if you have a license for 2.xx (introduced in 2015) this would still be valid. And as always, you can re-obtain a Code as much as you want (the license money being refunded right away, or given by other (email) means) without paying.

 

Peter

Hi Peter

 

Many thanks for confirming. I'll follow up on the advice at some point.

 

Regards

Mark

[manueljenkin]

1 hour ago, LowOrbit said:

Manuel

 

Great work. I haven't used XXHE for some time now, but this covers all the bases for getting started.

 

I did find Peter's work provided some very good results, but always found it a bit finicky to get right and a dedicated computer is pretty much eesential given the extent of modifications required.

 

I have wondered often about revisiting, (haven't used XXHE since before migrating to Windows 10) but not sure if my license would still be valid.

 

A lot of effort went into your tutorial above, I hope someone finds it helpful.

 

Mark

 

Thank you for your kind words Mark. Hope you have a great day. Happy listening!

[shreekant]

Manuel,

This is very helpful , great effort.