Version 0.9y-2 feedback

[Eric]

Hey Eric,

Sorry that I summarized some things, but I want to make clear what can and what cannot work.
So, right now I show the currently playing track at the bottom (can undo that in a second, and it only shows (me) what will be happening).

Allright, if you look below first pic, you see 02-Call the Doctor.wav playing (the .wav may go, and "Album" should be named differently). Now, whether I click another track or scroll to it with the arrow buttons, another track will get highlighted. In my case track 07. The track title at the bottom won't change from that. The time scale does though and I guess I can do something about that. However ...

The inherent mechanism (and that won't be changed) causes the highlighted track to be played next. A, say, DJ-like.
So what I mean is that clicking this other track is nothing for returning to where you were (playing), and it is an awkward thing in the end. It will work though, if you only click on the playing track before it ends playing or otherwise the current highlighted track will (second pic below).

Allright ?
Or ... maybe I add a rightclick option "return to playing track" ? I'm not sure though whether I can get that into focus again (that it shows in the visible area). These kind of things are not 100% decent for the means I use ...

Peter

Hello Peter,
Thanks for the explanation, I think I understand what you are saying. No problem with the way it has been setup. When you would also show the currently playing track at the bottom (like in the picture), I would be more than satisfied.
Next version, hopefully?

Cheers, Eric.

[Leon]

Hi Peter,

I like Alfa a lot, though yesterday it was Palm!!.

That might have caused the problem, cause you were completely right with an error in the shortcut.
After repairing that, the system functions ........... though only now in "demomode".

So all in all Mea Culpa, I am deeply sorry for the inconvenience and I am on my knees before the pc with red eyes from crying about my own stupidity.

Thanks in advance for taking care of the activation code.

best regards
Leon

[PeterSt]

Leon, no problem ! This is how I get my Alfa ... win a few, loose a few, but in general I'm okay. Don't need peanut butter either.

You can enter your before in use Activation Code again; that should work.
If you have lost it, in the folder you used before (if still there) there's a XXHighEnd1xx.dat file where the code is stored in. Copy that file into your current now working folder.

If all fails, let me know (still no problem).

[PeterSt]

Hi Peter, here are the numbers you requested when switching between 16/44 and 24/96 files, and vice versa. I don't think the DAC has anything to do with this issue because I ran the test once using the DAC and once just using the internal sound card in my laptop and got the exact same results. Here are the numbers:

Song 1, 16/44, length 3:26.42 to Song 2, 24/96, length 4:29.63 generates:
2/32/44100/352800/8 and 2/24/96000/576000/6

Song 2, 24/96, length 4:29.63 to Song 3, 16/44, length 5:45.04 generates:
2/32/9600/768000/8 and 2/24/44100/264600/6

Playing and stopping each song respectively generates:
Song 1: 2/32/44100/352800
Song 2: 2/32/96000/768000
Song 3: 2/32/44100/352800

Hope this helps.

boleary - hi,

It just slipped through my mind how easy it is to let the device initialization work as before. Or anyway for that part that should be causing it.
I think - but can not be sure - this is about how your M-Audio responds to relative changes, and it may not be able to do it at all. Or at least not how WASAPI this dictates. Also, I of course assume that you didn't change anything with your chain (being M-Audio - MSB according to you signature), and that *that* chain worked before.

If the below XXEngine3.exe helps I can make a parameter for it ("Initialization type" or something), and you would be using the old way.
Important : This is not a production version and it won't be consistent with your XXHighend.exe, but I expect you can use it sufficiently to try this. If you were used to try it by dragging the time cursor to near the end of "track 1" and that gives you errors, just try it with running "track 1" all the way through. That will most probably work for this combination.
Do not forget to save your current XXEngine3.exe.

If this helps, I wonder what is special about the M-Audio. One thing I can expect : if this is a 24 bit device @ 96KHz (and it should since you seem to use it like that), how is that different from a. the other USB devices which don't support 24/96 and b. how is it different from the "24 bit only" devices where the new method of initialization was made for. IOW ...
I feel something more is going on here, because I don't suspect a 3rd method for USB to exist. But what about this being 16/96 (which is normal for USB), and what do you actually do to let this work with the MSB ... if this is true *and* you know this in the first place (whether it is 16/96).
Another question would be : what do you select for "DAC Needs" ? 24 or 32 ?

Sorry for the question, but I merely like to know what is going on than just solve the problem without understanding.
Anyway let me know whether it helps.
Peter