0.9z-7-4: Unattended mode behaving like AB

[PeterSt]

Keeping fingers crossed

What to do else with those fingers now eh ? haha

[PeterSt]

I can't imagine that this driver for your Logitech can imply this issue. However, maybe your remote can cause the A-B to get activated ? In that case you would see it though, at the next startup of XXHighEnd (the buttons are active).
Also, notice that remote commands Alt-A and Alt-B exist to activate the A-B buttons, so maybe it goes that route somehow when using the remote.

Peter

[charliemb]

Thanks but no, false alarm, the AB problem exhibited itself again last night, but only after I had to raise SFS to 6 w/max6. 
I had to change from SFS=2 because I had an issue that when a tracklist changes sampling rates, I get ticks like missing samples throughout the next song(s).  Otherwise SFS=2 went two nights without the problem. 

Then, when I turned logging on, the AB problem did not repeat.  But that was only for the last 1/2 hour.   So no log files just yet.   And now I've moved to SFS=60 as you requested.

The Logitech palm sized keyboard attaches through USB and I think might be a proprietary form of Bluetooth.  ..if that helps.

No the AB is not active when I return to xxHE.

When it skips to the next song, it starts from the beginning of the next song.  So it is like A=0 and B is a few minutes into the song.

Back to the ticks with SFS=2, since SFS=2 seemed like it was fully working and therefore pertinent to a solution,  I am able to get the ticks to stop by stopping the song with alt-s and restarting with alt-p.  Sometimes pausing works but mostly not (which is a pain because sometimes alt-s restarts playback at the beginning of the track list rather than at the current song).

[PeterSt]

Too bad Charlie ...

But now you suddenly start about "ticking". And *this* I recognize. Now, I didn't look back into the topic whether you changed XXHE versions, but I suddenly see this 0.9z-7-4 in the topic title. In that version things like that happened and it could happen for reasons like format changes, up to changing the volume while playing. And this is solved ... (I think per 0.9z-8).

The repeat could happen just the same and this too was related to and format change and changing volume (so, both !). I do NOT know whether this has been solved, because it is hard to mimic. Anyway ...

1. Upgrade to the latest version please;
2. Try to concentrate on format changes + volume changes or otherwise volume changes alone.

And if this already rings bells, let me know ...
Regards,
Peter


PS: But remedy always has been to kill the sound engine (blue led in the right border of the screen). And I recall from the beginning of this topic that this did not help you - so maybe a moot idea after all.

[charliemb]

Updated subject line to reflect that I have upgraded to z8-3a

[Meaning that the last few nights have been z8-3a, from when I mentioned it earlier in this thread or a day before that or two.]

[charliemb]

Wow...  2 hours listening and with sfs 60 and logging turned on and so far I could not recreate the problem. 

I'd say that it must have something to do with whatever or one of the changes you made for z83a.

And, btw, now sfs=60 is sounding better than sfs=2.  Smoother, still detailed, and much better soundstage and far fewer ticks.  Go figure.

[charliemb]

Finally, error with logging turned on.

The album playing was Beck - Sea Change.  The track playing was track 2. Paper Tiger.

Attached are the log files.  There are four files in total and two them are XX, the smaller XX is the more recent and MUCH smaller than the other.

[PeterSt]

Charlie,

The log files are helpful. So, at least I can see that it happens and I even see some "logic" in your skipping to the next track (as happened in this case).

And notice that you mix all formats in the world in one playlist although in the Beck situation (and the second time you played it) it was only 24/88.2.

Strange question perhaps : Why did you play Beck for the second time on one day ? Not that you now should go to mental hospital, but it is as if you could expect it to go wrong. If so, you may have more hints for me ?

Thanks,
Peter

[PeterSt]

OK. All I can tell for now is that it has to be related to somehow interpreting the length of the track as were it exactly 3 times less as it really is, which comes down to 16/44.1 instead of 24/88.2. This, while you played the Beck track 2 times. And hey, super convenient that you did, because it allowed me to compare and find this.

It originates in the user interface (XXHighEnd.exe) so already there something strange has to happen. And ... this, while the first track (of Beck) was OK, and the second fails on this. Right now I can't see how that happens.

Below you'll find a 09.z-8-3d with some additional log lines in there. Unzip and paste this over your current 0.9z-8-3a folder, and hope it will happen again soon. I think I can do with the XX log file only (the large one), but coughing up the same set as you did last night is ok just the same.

Now I'm curious what I will see. I guess a similar mixed bag of formats in the Playlist Area will help letting it occur.

It is not said that this is the last round of new log data (hence attempts). But it will bring me closer.

Please never ever used A-B (if you ever did) because I didn't incorporate special log data for that.

Peter


PS: It is not so that you used the 88.2 version of Beck and later the 44.1 to compare or something ?

[charliemb]

Why did you play Beck for the second time on one day ?

I purposely had queued up albums of mixed rates.  Never touched anything and just hit play.   That playlist made it beyond Bonnie Raitte and into 16/44.1 material with no problems.  But i was very uncharacteristically listening in the background while working on an electronics project...  and I thought, wow, that Beck album is very good, I'll listen tonight intently like I usually do from my listening chair.  Then l finally made it to my listening chair to really listen and that's when I started playing with the mouse cursor and such, and restarted the entire playlist, now at higher volume levels.   And as you can see, it only took to track 2 for the problem to happen.

I agree that it is a lucky coincidence that I played it twice.

BTW, I'm using 4x arcPreduct and PE.

But it seems that the problem happens more often when I start stopping and restarting as I did above.   I normally select portions of an album with click and Ctrl-click.

[charliemb]

PS: It is not so that you used the 88.2 version of Beck and later the 44.1 to compare or something ?

No.  Both were 88.2/24

[PeterSt]

Only notice : You also restarted playback just at that Beck album. Not the entire playlist from the beginning (in one go). For me not important, but maybe it helps you remember something else you did (and hey, I personally can't think of anything !).

If I am totally wrong on this it will also be important to rectify me.

Thanks ...
Peter

[charliemb]

Only notice : You also restarted playback just at that Beck album.

That sounds right, I remember that now, sort of.  The funny thing is that I also remember intending to load the entire list again, and I remember waiting a long time and it starting after the wait.   But as I said, I also remember selecting only the Beck album.   If that's what the log shows, that's probably correct.   Perhaps I did both (started it three times, why not?). 

This might help:  If I selected only the Beck album, then that was with the mouse cursor with click and Ctrl-click like I usually do and with the entire list still up there.  The tracks that followed and were unselected started with Bonnie Raitte, also hiRes but might have been 96k.

I'll try 09.z-8-3d now.

[charliemb]

Here you go with 'd.  The song that played short was Santana Abraxas, track 1 Singing Winds and Crying Beasts.   (@ 24/88.2)

The track list was from random selection from the Nice Stuff gallery.  (Which has in interesting "feature/bug" which I may mention at some point in another thread.)

There are two XX files because both were very recent and I wasn't sure which one was right.  I think the one to look at first is XX-20130326-214814.log.

For next time, when this happens,  To copy the log files I have to alt-x, alt-s.  Should I then quit xxHE?, and then go looking for the log files?   ..or do I just keep xxHE loaded?

[PeterSt]

Arghhhh ... The last two XX logs now are from the alt-s you aplied and next the alt-x (not the other way around btw). So you will need the larger one just preceeding these in time.

Please post ASAP !
Thanks,
Peter