Let me be the first to thank Peter for the gargantuan effort in getting version 0.9y out

A couple of quick notes.

When I first started 0.9y up, sox.exe complained about some missing dll's ( cygwin.dll and cyggomp-1.dll ). I downloaded the latest release of SoX from SourceForge ( http://sourceforge.net/projects/sox/files/sox-win/14.3.0/ ), and copied the two missing dll's into the XXHighEnd folder.

Next surprise was when I initially set my working parameters. I have a Juli@ sound card, so mistakingly thought I would need to have the "24 bits" button highlighted for the DAC. Big mistake! Should have been set at '32'. Upon first attempting to play a file at the '24 bit' setting, I was greeted by an almighty squeal from the speakers, and the system brought up a blue screen of death and I think it said page fault error. Suffice it to say, when the system rebooted I quickly reset that DAC button to '32' and all was well. Before you alter than button, make sure you have the volume low .. haha.

I shall continue playing.

Cheers,

Russ

hey guys ..

if you don't want that message box appearing why not simply 'comment' the line out within the XX.ahk script that brings it up !

Open up XX.ahk with notepad, and look for line 31 or thereabouts starting with ...

msgbox ,48,,% StartUpDir . " <<== sho

Insert ;*** at the start [note space at the end of last asterisk] and *** at the end [note space at the beginning of first asterisk], and you won't see that message again.

It should end up looking like this ..

;*** msgbox ,48,,% StartUpDir . " <<== should show your current XX folder." . chr(13) . "If not, Hot Keys work out wrongly !!" ***

See the commented lines at the start of the script to check how the syntax should look.

Cheers,

Russ

Hi Peter,

I normally use XXHE in unattended but as a test for you I play a couple of albums in attended mode just now and all seemed to behave normally here. That's with 0.9x-7

I have attached the logs that session generated as you wished.

Cheers,

Russ

I'm still on SP0. If anyone can give me some definitive proof that it is going to be beneficial from a sound quality perspective I'd consider putting on SP1, but until that time I'll remain status quo. I come from the 'if it ain't broke .. don't try and fix it' school.

Perhaps a poll might be useful to see who is running what.

Cheers,

Russ

Here's a nice simple way:

Open up the .pdf as normal and use the readers zoom function so the size of the image is of a suitable quality, then do a screen capture ( SHIFT/PRINT SCREEN ).  Use something like Photoshop to crop the section of the screen capture to want.

Cheers,

Russ

HI Andrew,


IF you have the SPDIF working correctly which I presume you have,  simply go to the Juli@ control panel, and press the 'MON' button just beneath the 'S/PDIF OUT' words. The button should turn orange. You should now be getting output via the analogue channels.

The Juli@ card is now monitoring the SPDIF channel ( which is still operating in Exclusive Audio mode ~ check by clicking the mute function ~ play should continue unheeded ) and converting it via its internal DAC's to analogue.

Job done!

See if that works.

Russ

G'day Roy,

no can do unfortunately as they are different topographies. However, you should be able to use the 2nd PCIe x16 slot ( orange ) , assumming you are not one of those mad gamers that runs dual video cards 

Have a look here for some geek talk ... http://en.wikipedia.org/wiki/PCI_Express


Cheers,

Russ

EDIT: Telstar pipped me to the post !

Hey there Peter,

does the software on this forum have the facility to prevent a newly created userid from posting a new thread immediately ?

You will no doubt have seen the 2 threads started by unlaranak earlier, which by the time you read this will have been purged I guess. I also noticed a few weeks back another userid created and posted a pile of cr*p also, which you thankfully purged. By preventing these cretins from posted immediately it might help stop any pollution occurring here, and may help in reducing administration work for yourself. Another idea in use in a number of other forums, is to have a section where new members are only permitted to post, and they have to introduce themselves. Until such time that another member has acknowledged that thread and said 'hello' back, then the new user is not permitted to start threads outside the "introduction" section. Of course it may not prevent them from creating junk in that "introduction" section but it confines such junk to one area only then.

Food for thought.

Cheers,

Russ

PS.  go Ferrari !! 

It's already been invented. We just have to wait till we are old enough to use it 

http://memory-alpha.org/en/wiki/Isolinear_chip

I wonder if all programmers are bald as the result of pulling their hair out trying to accommodate every possible combination of hardware/software in use and the way the end user uses their product.

I fully sympathise with the difficulty you face and simply trust that by finding these peculiarities, we , the 'beta testers' if you like, are able to help bring these issues to your attention, so you can improve the product to the stage where you are comfortable to call it version 1.0. Champagne corks will pop on that momentous day I am sure.

The progress of XXHE from when I first heard about it back in mid '07 has been fantastic and you should be very proud of your achievements so far. I for one am most grateful for your dedication and the occasional glitch in a new version doesn't faze me in the slightest.

Now go and enjoy your fine single malt

Cheers,

Russ

  Working as expected now

While testing this new version I also discovered by accident that ( while in Unattended mode ) if you use Alt-P then music stops and an error message comes up indicating that Engine3 has stopped working and needs closing. Another Alt-P will commence playback again though. Normally one wouldn't choose to use the PLAY function when things are already playing, but first thing in the morning, when one has just woken up, anything is possible .. hehe

Might to prudent to include some code to check what's currently happening if Alt-P is used in that situation.

Thanks Peter,

Russ

Gotcha ... thanks for the logic flow

Must be beer o'clock here by now !

Think I'll spent some "Quiet Night's"  with Diana Krall for a while. Have heard first couple of tracks .. loverly album.

Hooroo ...

RGB

hmmm ... might have lost a bit in translation .

The slider is at the TOP ( 0db ) when I click on the play button.

When GUI disappears vol is still OK until Alt-N is invoked, then vol drops to -120 during the second warning message.

That seems to contradict what you just wrote about vol being "initiated" at -120db.

Are we both on the same page yet .. hehe

Ta .. Russ

OK .. sequence of events:

Start play with Vol = 0
When GUI disappears use Alt-N and a message about not being about to change vol to/from 0db. This comes up twice. Then I notice in addition to selecting the next track, the vol has gone to -120 as indicated in the "spine" between the front and 'back' coverart sections.

Doing a Alt-X to get back to GUI shows the slider actually at -120dB now.

Have also just noticed that OSD disappears after the next track is started playing. ( although you can't hear it because the vol is now at -120dB ).

When vol starts off at anything other than 0dB is seems to behave.

You don't get this occuring then ?

Just with the keyboard. If the vol is set at -1.5db or lower it behaves itself. I'm guessing because you have VOL set quite low you may not have tested starting at Vol=0.

Regs,

RGB