Solid State Logic SSL2+ Confirmed Working

[Aensland]

I recently purchased a Solid State Logic SSL2+ audio interface. I can confirm it works great with Rocksmith using RS_ASIO.

These are the config settings I use:

[Config]
EnableWasapiOutputs=0
EnableWasapiInputs=0
EnableAsio=1

[Asio]
; available buffer size modes:
;    driver - respect buffer size setting set in the driver
;    host   - use a buffer size as close as possible as that requested by the host application
;    custom - use the buffer size specified in CustomBufferSize field
BufferSizeMode=driver
CustomBufferSize=

[Asio.Output]
Driver=Solid State Logic ASIO Driver
BaseChannel=0
AltBaseChannel=
EnableSoftwareEndpointVolumeControl=1
EnableSoftwareMasterVolumeControl=1
SoftwareMasterVolumePercent=100

[Asio.Input.0]
Driver=Solid State Logic ASIO Driver
Channel=0
EnableSoftwareEndpointVolumeControl=1
EnableSoftwareMasterVolumeControl=1
SoftwareMasterVolumePercent=100

[Asio.Input.1]
Driver=
Channel=1
EnableSoftwareEndpointVolumeControl=1
EnableSoftwareMasterVolumeControl=1
SoftwareMasterVolumePercent=100

[Asio.Input.Mic]
Driver=
Channel=1
EnableSoftwareEndpointVolumeControl=1
EnableSoftwareMasterVolumeControl=1
SoftwareMasterVolumePercent=100

I'm sure the SSL2 (non plus) works perfectly fine as well, but I haven't tested that. I hope this helps!

[mdias]

Thank you for the report.
I will be adding it to the list soon.

[mdias]

List is updated. Thank you again 👍

[x-ticker]

It also work on Solid State Logic SSL12 audio interface.

[mdias]

Thanks. Added 👍

[chybanieczaje]

SSL 2+ MK II user here, setup above didn't work for me. After some figuring out, this is what made it work:

[Config]
EnableWasapiOutputs=0
EnableWasapiInputs=0
EnableAsio=1

[Asio]
; available buffer size modes:
; driver - respect buffer size setting set in the driver
; host - use a buffer size as close as possible as that requested by the host application
; custom - use the buffer size specified in CustomBufferSize field
BufferSizeMode=driver
CustomBufferSize=

[Asio.Output]
Driver=SSL ASIO Driver 1
BaseChannel=0
AltBaseChannel=
EnableSoftwareEndpointVolumeControl=1
EnableSoftwareMasterVolumeControl=1
SoftwareMasterVolumePercent=100

[Asio.Input.0]
Driver=SSL ASIO Driver 1
Channel=0
EnableSoftwareEndpointVolumeControl=1
EnableSoftwareMasterVolumeControl=1
SoftwareMasterVolumePercent=100

[Asio.Input.1]
Driver=SSL ASIO Driver 1
Channel=1
EnableSoftwareEndpointVolumeControl=1
EnableSoftwareMasterVolumeControl=1
SoftwareMasterVolumePercent=100

[Asio.Input.Mic]
Driver=
Channel=1
EnableSoftwareEndpointVolumeControl=1
EnableSoftwareMasterVolumeControl=1
SoftwareMasterVolumePercent=100

[chybanieczaje]

In ASIO settings, there are 4 options -SSL ASIO1 - 4. I am using SSL ASIO 1, hence why that is in my config file.

[mdias]

@chybanieczaje thank you. I've added an entry in the docs for the SSL 2+ MKII variant linking directly to your comment.

[x-ticker]

@mdias I can confirm the new format is the same for others SSL interfaces. This is because of new driver version.

[mdias]

@x-ticker can you provide a list of which ones you specifically tested?
I'd rather have on the list only ones that people specifically tested and not try to assume other will work fine.

[x-ticker]

@mdias I tested only SSL 12 but they all share the same driver.

SSL 2/2+ - MK I / MK II and 12 driver page

[mdias]

@x-ticker I agree with that it's extremely likely that those interfaces will also work.

However, the driver being the same does not mean it will behave in exactly the same way for all models.
With that in mind I'd prefer to not say "it's been reported to work" in the docs without someone having tested the specific models, as we might get unlucky and encounter an incompatibility issue with a specific model after someone already spending money to buy one.