Page 678 of 804

Re: MQN

Posted: Mon Feb 16, 2015 9:41 pm
by sbgk
jmmbarco wrote:Hi Aleg! Thank you. Vega has a KS driver, in fact it is what am using through JPLAY. I will test this utility to get the string.

I hope some version to be available for Ivy....

Best,
JM
join the queue, have a cold at the moment so progress is difficult.

Re: MQN

Posted: Mon Feb 16, 2015 11:01 pm
by Aleg
sbgk wrote:Hi Aleg or anyone really,

am having an issue with my gustard u12 convertor, the driver (Thesycon) is installed so that
the device appears as a speaker. I am able to play other sounds through the speaker while it is playing ks or wasapi exclusive.
So it is either using the windows mixer or there is something in the hardware allowing this to happen.
ksstudio shows it has 3 nodes, a dac, mute and volume control, so could be hardware. Would like to get it to install as a digital device and wonder if there is anything in the inf file that I could alter.

Any advice much appreciated.
The USB Terminal ID is translated into the KSNODETYPE and this is set inside the driver.
I don't believe this is configurable inside an inf as far as I'm aware.
All three of my USB audio devices are shown as "Speakers" inside the Control Panel / Sound Devices.
Output Terminal Types
USB Terminal ID KS Pin Category GUID
0x0301 KSNODETYPE_SPEAKER
0x0302 KSNODETYPE_HEADPHONES
0x0303 KSNODETYPE_HEAD_MOUNTED_DISPLAY_AUDIO
0x0304 KSNODETYPE_DESKTOP_SPEAKER
0x0305 KSNODETYPE_ROOM_SPEAKER
0x0306 KSNODETYPE_COMMUNICATION_SPEAKER
0x0307 KSNODETYPE_LOW_FREQUENCY_EFFECTS_SPEAKER

External Terminal Types
USB Terminal ID KS Pin Category GUID
0x0601 KSNODETYPE_ANALOG_CONNECTOR
0x0602 KSNODETYPE_DIGITAL_AUDIO_INTERFACE
0x0603 KSNODETYPE_LINE_CONNECTOR
0x0604 KSNODETYPE_LEGACY_AUDIO_CONNECTOR
0x0605 KSNODETYPE_SPDIF_INTERFACE
0x0606 KSNODETYPE_1394_DA_STREAM
0x0607 KSNODETYPE_1394_DV_STREAM_SOUNDTRACK
I have not found more on this than:
https://msdn.microsoft.com/en-us/librar ... s.85).aspx
https://msdn.microsoft.com/en-us/librar ... s.85).aspx
https://msdn.microsoft.com/en-us/librar ... s.85).aspx

Re: MQN

Posted: Mon Feb 16, 2015 11:31 pm
by sbgk
Aleg wrote:
sbgk wrote:Hi Aleg or anyone really,

am having an issue with my gustard u12 convertor, the driver (Thesycon) is installed so that
the device appears as a speaker. I am able to play other sounds through the speaker while it is playing ks or wasapi exclusive.
So it is either using the windows mixer or there is something in the hardware allowing this to happen.
ksstudio shows it has 3 nodes, a dac, mute and volume control, so could be hardware. Would like to get it to install as a digital device and wonder if there is anything in the inf file that I could alter.

Any advice much appreciated.
The USB Terminal ID is translated into the KSNODETYPE and this is set inside the driver.
I don't believe this is configurable inside an inf as far as I'm aware.
All three of my USB audio devices are shown as "Speakers" inside the Control Panel / Sound Devices.
Output Terminal Types
USB Terminal ID KS Pin Category GUID
0x0301 KSNODETYPE_SPEAKER
0x0302 KSNODETYPE_HEADPHONES
0x0303 KSNODETYPE_HEAD_MOUNTED_DISPLAY_AUDIO
0x0304 KSNODETYPE_DESKTOP_SPEAKER
0x0305 KSNODETYPE_ROOM_SPEAKER
0x0306 KSNODETYPE_COMMUNICATION_SPEAKER
0x0307 KSNODETYPE_LOW_FREQUENCY_EFFECTS_SPEAKER

External Terminal Types
USB Terminal ID KS Pin Category GUID
0x0601 KSNODETYPE_ANALOG_CONNECTOR
0x0602 KSNODETYPE_DIGITAL_AUDIO_INTERFACE
0x0603 KSNODETYPE_LINE_CONNECTOR
0x0604 KSNODETYPE_LEGACY_AUDIO_CONNECTOR
0x0605 KSNODETYPE_SPDIF_INTERFACE
0x0606 KSNODETYPE_1394_DA_STREAM
0x0607 KSNODETYPE_1394_DV_STREAM_SOUNDTRACK
I have not found more on this than:
https://msdn.microsoft.com/en-us/librar ... s.85).aspx
https://msdn.microsoft.com/en-us/librar ... s.85).aspx
https://msdn.microsoft.com/en-us/librar ... s.85).aspx

thanks, think the ability to play multiple tracks at the same time is a function of xcore architecture, so set vol to max and just play one tune/sound at a time for best quality, I guess. After trying to avoid mixers, I got a bit twitchy when the xmos chip started doing it.

https://www.xmos.com/download/public/xC ... 1.2%29.pdf

---- Verifying intra-filter topology of filter \\?\tusbaudio_enum#vid_20b1&pid_000a&ks#6&1e31c658&8&1#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\pcm_out_02_00 (xCORE USB Audio 2.0 Output) ----
~~ Examining Nodes ~~
Verifying that each node has at least 2 connections
Verifying Node [0] KSNODETYPE_DAC (DAC) ...
1 incoming connections (1 from Pins, 0 from other Nodes)
1 outgoing connections (0 to Pins, 1 to other Nodes)
Verifying Node [1] KSNODETYPE_MUTE (Master Mute) ...
1 incoming connections (0 from Pins, 1 from other Nodes)
1 outgoing connections (0 to Pins, 1 to other Nodes)
Verifying Node [2] KSNODETYPE_VOLUME (Speakers) ...
1 incoming connections (0 from Pins, 1 from other Nodes)
1 outgoing connections (1 to Pins, 0 to other Nodes)
~~ Examining Pins ~~
Verifying that each pin has at least 1 connection
Verifying Pin [0] ...
0 incoming connections (0 from other Pins, 0 from Nodes)
1 outgoing connections (0 to other Pins, 1 to Nodes)
Verifying Pin [1] (Speakers) ...
1 incoming connections (0 from other Pins, 1 from Nodes)
0 outgoing connections (0 to other Pins, 0 to Nodes)

Re: MQN

Posted: Mon Feb 16, 2015 11:48 pm
by rickmcinnis
I was playing with JPlay (evaluation) in my continuing attempt to use MQn just to see if I could get ANYTHING to work.

I am using WAVE IO with its somewhat debased THESYCON drivers.

I will look again tonight (will need to re-install JPlay) But I do not think I had ANYTHING in HARDWARE/SOUND. Along with no need for WINDOWS Audio or Endpoint services.

I think MQn will take a big step forward if you are able to disentangle it from ALL of that WINDOWS stuff. Along with making it much easier for anyone to use.

Looking forward to the next GREAT LEAP FORWARD. The "m" does stand for Mao, right?

Re: MQN

Posted: Mon Feb 16, 2015 11:59 pm
by sbgk
rickmcinnis wrote:I was playing with JPlay (evaluation) in my continuing attempt to use MQn just to see if I could get ANYTHING to work.

I am using WAVE IO with its somewhat debased THESYCON drivers.

I will look again tonight (will need to re-install JPlay) But I do not think I had ANYTHING in HARDWARE/SOUND. Along with no need for WINDOWS Audio or Endpoint services.

I think MQn will take a big step forward if you are able to disentangle it from ALL of that WINDOWS stuff. Along with making it much easier for anyone to use.

Looking forward to the next GREAT LEAP FORWARD. The "m" does stand for Mao, right?
mqn is rather dependent on the windows kernel, the alternative is asio, but I think it is flawed due to the amount of copying required, the stream must be split into left and right buffers rather than being interleaved. ks also gets the advantage of it's operations taking place in kernel mode, asio is user mode.

Re: MQN

Posted: Tue Feb 17, 2015 1:23 am
by rickmcinnis
Certainly not an adherent of JPlay - only reason I tried it was because you asked if I could get any other player to work on my machine.

It says it is kernel streaming and I have no ASIO drivers installed.

That is all I know.

Re: MQN

Posted: Tue Feb 17, 2015 7:23 am
by Aleg
rickmcinnis wrote:....

I am using WAVE IO with its somewhat debased THESYCON drivers.

...
WaveIO has NO debased Thesycon drivers. These are the proper full Thesycon driver set with no reduction in functionality.
I'm glad this set for WaveIO exists!!!

Re: MQN

Posted: Tue Feb 17, 2015 4:25 pm
by rickmcinnis
Aleg,

I should not have said debased drivers since I was thinking debased functionality of the tools one sees with some other applications compared to what is there with Lucien's.

Which do you prefer? 2.23 or 2.24? Seems there is some disagreement with some preferring the older set. Could this be, simply, system dependent?

Re: MQN

Posted: Tue Feb 17, 2015 4:28 pm
by Aleg
rickmcinnis wrote:Aleg,

I should not have said debased drivers since I was thinking debased functionality of the tools one sees with some other applications compared to what is there with Lucien's.

Which do you prefer? 2.23 or 2.24? Seems there is some disagreement with some preferring the older set. Could this be, simply, system dependent?
I haven't noticed any difference, though I wasn't looking for any.
Have used 2.23 only very shortly, few weeks when stepping up to the 2.24.

Re: MQN

Posted: Tue Feb 17, 2015 4:54 pm
by sima66
Aleg wrote:
rickmcinnis wrote:Aleg,

I should not have said debased drivers since I was thinking debased functionality of the tools one sees with some other applications compared to what is there with Lucien's.

Which do you prefer? 2.23 or 2.24? Seems there is some disagreement with some preferring the older set. Could this be, simply, system dependent?
I haven't noticed any difference, though I wasn't looking for any.
Have used 2.23 only very shortly, few weeks when stepping up to the 2.24.
Aleg,

I have the 2.23 (adapted to accept 24 bits containers) from you.
Did you had the same "adaptation" for the 2.24?