Jump to content

gwbuiter

Member
  • Posts

    51
  • Joined

  • Last visited

  • Country

    Netherlands
  • Donations

    0.00 USD 

Posts posted by gwbuiter

  1. 7 hours ago, Phantatsy said:

    Seems to be a problem with the Focusrite USB ASIO driver to me.

    Try taking a look at the directory for the FocusriteUsbAsio32.dll located in

    (C:) > Program Files > Focusrite > Drivers

    Maybe the file is missing, and that's causing the problems. Could also be why you needed to use WASAPI output instead of ASIO too.

    If it's there, then I'm not exactly sure what the issue is.

    Well, I re-installed al the drivers several times. And I checked the location. The driver is really there.  Maybe someone else on Discord may have  solution? I can try that. It looks like something in windows is still blocked the conection to rocksmith. Or maybe some restrictions. 
     

    strangely though, when I run Amplitube it works flawlessly! Input… output.. everything!

  2. I think i finaly found the problem. I found an older RS_ASIO log file. and when you look at the 1st screenshot,

    you see output requesting ASIO driver, Creating AsioSharedHost and it refers to a ASIO driver focusriteusbasio32.ddl.

    followed by the input and output channel info.  (and the file is acually there in the right directory)

    RS_ASIO_LOG1.jpg.aa353c66af7ade34b28bc6e4a5cfcac4.jpg

    In the 2nd screenshot (after re-installing Windows 10/11) i got errors.

    I thought i place back the old files in the Rocksmith directory, and problem solved. But unfortunately that was not the case.

    I double checked it, and the driver referred to, is there.

    IS there a way how i can fix this?

    RS_ASIO_LOG2.thumb.jpg.3f892e52a2526db56a88982b3b3c2fa8.jpg

  3.  

    but isn't this strange? Wouldn't it be an issue with Rocksmith and Windows 11? 
    I have never had these problems in Windows 10, and I am almost considering switching back to Windows 10
    I have a Discord account, so we can try that. but I am not familiar with how that works. but I accepted your request.
    Only I hope it doesn't conflict with my settings for AMplitube, because that works fine for now

    Only why using a chatbox kind of app instead of this customforge forum, where you can share so much more information 😉

     

  4. 7 hours ago, Phantatsy said:

    Regarding the wineasio, no that is normal for it to not find it. Wine should be for Linux systems.

    As far as the stuttering/distorted audio. You'll have to play around with the buffer size value to find something that doesn't cause issues. You might also try changing the latency buffer in the rocksmith settings. You can go higher than the default 4. Something to think about.

    -

    Now, for the real problem, the input.

    Input 1, channel 1definately should be the correct setting. However; it seems it's not working correctly. At this point, you may as well try other channels, 0 and 2, to see if you can get any input from them.

    If not, then you may need to just try the direct connect mode available in RSMods under the Set and Forget mods, in the Misc tab.

    for now to be sure, everytime i made a change,i do a windows reboot.

    Still nothing. tried input 1, and channel 0,1,2,3,4...en so on...

    Also the direct connect mode won't work.

     

    but the cable is physically connected to the interface on input 2 (input 1 is my mic, which I don't use).
    Shouldn't I also use input 2 instead of input 1 in RSMods? that makes more sense to me.

     

     

  5. Yes, the sound is a bit distorted, it stutters..but yes the sound output works. but still no input. Rocksmith keeps asking me to connect the rocksmith cable.

    Here are all the screens of all the settings i've done in Windows, RSMods, and in the settings app from my interface, i also put some screenshots of the rocksmith.ini,

    and the RS_ASIO_log file.

    Does it have something to do with some asio drivers that are not found? wineasio, wineasio32.dll (see the RS_asio log screenshot).

    and i also did a full re-install of the interface drivers.  by default it is already set to 48000 sample rate and buffer size 192. so that is ok.

    on Latency information by default "safe mode" is checked.

    rocksmith_ini.png.8ea3419b9cb3eb85bc81c8e9853f5697.pngRS_ASIO_log.thumb.png.b894f908bc57858492703eeed52bba58.pngwindowsrecordsettings.png.20c02dce0e4b183b8e9542346527f6c3.pngwindowsplaybacksettings.png.e32a5df390f8ebca96f266cc883ca9a3.pngfocusritesettings.thumb.png.4b8d4257fac42bdb48edaa52097ddc10.png

  6. 1 hour ago, Phantatsy said:

    Nothing wrong with starting over. I haven't really watched any videos of how to get it working, so I'm not sure what steps they take. However, this is how I have done it, and how I've had lots of other people do it. I know you've already covered some of these steps, but I'm going to list everything for anyone who might stumble across this thread.

    Starting with a fresh install of Rocksmith and with the latest drivers for your interface installed. Proceed with the following:

    1. Change the sample rate of your interface in the Focusrite (or other manufacturer's) device settings. It should be 48000 Hz. Bit depth can be 16-bit or 24-bit.
    2. Install RSMods.
    3. Install RS_ASIO by dragging the 3 files from the .zip archive into the base Rocksmith folder. (Where the Rocksmith.exe file is)
    4. Run Rocksmith. Ignore any SOUND INITIALIZATION ERRORs. Once the game has loaded; close it.
    5. Open RSMods and navigate to the RS_ASIO Settings tab.
    6. Set your input 1 to your interface (Focusrite USB ASIO).
    7. Change the channel to match the input you're using for your instrument. (Input 1 on an interface = channel 0| Input 2 on an interface = channel 1 - and so on)
    8. Set your output to your interface (Focusrite USB ASIO).
    9. Input 2 and Input Microphone should not have anything selected (unless you plan on playing mutiplayer for some reason).
    10. Set your Buffer Size. "Driver" will use the number your interface is already set to. To use a different value, use "Custom". If using custom, set the value to 192 to start with.
    11.  Navigate to the Rocksmith Settings tab.
    12. "Exclusive Mode" should be enabled.
    13. * OPTIONAL * Check "Real Tone Cable Only"     --- This makes it so Rocksmith doesn't take over your microphone, allowing you to use it in Discord. (It also doesn't change the volume level on the Mic like it normally would)
    14. * OPTIONAL * Uncheck "Enable Microphone"      --- Additional setting to make sure Rocksmith doesn't try to use your mic.
    15. Run Rocksmith.

    -

    If you are using the RealTone Cable but an audio interface for sound output:

    1. Instead of selecting your interface in step 6. leave it blank.
    2. Select "Use WASAPI Input".
      • This will use Windows default audio input (recording device).
      • Make sure it is set to 48000 Hz, 16/24-bit in Windows sound settings.
      • Also make sure Windows allows applications to take exclusive control of this device. (Found in "More sound settings", then the advanced tab of properties)

    -

    If you are using the interface for input, but headphones or speakers connected to your PC using something other than the interface (USB or 3.5mm aux into motherboard):

    1. Instead of selecting your interface in step 8. leave it blank.
    2. Select "Use WASAPI Output".
      • This will use Windows default audio output (playback device).
      • Make sure it is set to 48000 Hz, 16/24-bit in Windows sound settings.
      • Also make sure Windows allows applications to take exclusive control of this device. (Found in "More sound settings", then the advanced tab of properties)

    -

    That should be it for the set up. After you have confirmed input works and you have sound output (even if it's distorted or unusable). Then you can attempt to fix audio quality and latency.

    • Latency Buffer (In Rocksmith Settings, or the Rocksmith.ini file). 4 is default, lowest in-game setting is 2. (The game will say it's 1, but the file will say 2).
    • Buffer Size (set in RS_ASIO and/or your driver settings for the interface.
      • A buffer size of 192 should work without any audio distortion, however you may want to have slightly less latency.
      • A step down from 192 should be 96. A step down from 96 should be 48.
      • You're free to try numbers between 192 and 96, but in my experience; other numbers will cause problems.

    If, when changing buffer sizes, you lose audio in Rocksmith (audio from other sources should still be fine), you will need to:

    1. Change the buffer size back to the previous value that worked before losing audio (or distortion).
    2. Restart your PC. (Unplugging and re-plugging in your interface may also work, but I know restarting works for me)

    -

    Getting a SOUND INITIALIZATION ERROR after following the 14 steps mentioned earlier on should only be because:

    1. The sample rate isn't 16/24-bit 48000 Hz.
    2. Rocksmith can't get exclusive control of your audio device.

    Folllowed exactly all the steps above. and i completely re-installed steam and rocksmith, but still no input.

    Maybe here it go's wrong:

    I use the Focusrite interface for input & output, so there are no speakers or headphones connected directly to my pc, because i have disabled te onboard soundcard in the bios settings. i only have connected the interface directly into the motherboards USB port.  and use the line-output on the back of the interface, and goes directly into my speakerset.

    My Focusrite Solo( 3rd edition)  has 2 inputs. input 1 is the microphone, and input 2 is the instrument port. so my guitar is connected to input 2 on my interface.

    You told me, input 2 on my interface (where my guitar is connected) is channel 1, so in RSMODS i set the input 1 Focusrite USB ASIO at channel1.

    and the output also on Focusrite USB ASIO.

    I didn't try Focusrite Thunderbold ASIO.

    Here are the new screenshots.

    rsmods.thumb.png.96fe60abbe2938101fe9083c217451ab.pngrsmods2.thumb.png.bf6074502354641bb609096405fa86ba.png

     

     

  7. No i don't use any headphones to my Focusrite or into my PC

    I've connected a 2RCA to 2RCA male cable direcltly from the line outputs (left/right)on the back of the Focusrite into my aux-in (left/right) on the back of my Logitech speakerset. I had already connected it that way in Windows 10.

    and when looking at the sound settings in Windows, i have this:

    both playback and recording are set to Focusrite USB Audio (default) at 16bit, 48000Hz (DVD Quality)

    playback.png.38ffec7114abba65f3f6c592fb81d36d.pngrecording.png.5a7af8f547e5d94fb04f87118f668f0a.png

     

    these settings work perfectly with my Focusrite Scarlett in Windows for playing music, movies and also 
    for using my guitar in Amplitube for example, but not in Rocksmith. 

     

     

    amplitube.thumb.png.fe95c16b778d69f64f82b3c49f260281.png

     

     

     

     

     

  8. 21 minutes ago, Phantatsy said:

    That's because you changed the channel to 2. If you interface has 2 inputs, you will be using:

    Channel: 0 (for the first input) or

    Channel: 1 (for the second input)

    Also, you now have "Use WASAPI Output" checked, which means it shouldn't be using the interface for sound output.

    That is fine, it'll just use whatever is default in Windows.  But you shouldn't have the interface selected if that's the case.

     

    Sorry,  I don't get it. When i uncheck "Use WASAPI Output", i got the Error Sound Initialization message again. and "Audio Output device is unplugged".

    When i check it again, my sound works.

    I think i have tried all combinations of settings....with both inputs and channels.

     I have the Focusrite Solo 3rd gen. with 2 inputs. 1 mic, and 1 instrument.  and my guitar is connected to the second (instrument) input

    so than it has to be this right?

     

     

    input2channel1.thumb.png.1db7894dde667eb9db5803af682d3034.png

     

     

     

  9. 3 hours ago, gwbuiter said:

    That would be great, thanks!

    Focusrite Control software, newest version (3.18.0) already installed.

    I just did a full re-install of Rocksmith, without any modifications, and run Rocksmith for the first time.

    I got sound, but it stutters.

    After that i close Rocksmith and placed the RS_ASIO files into the directory, and made the changes as mentioned  in the tutorial above.

    No sound, and i got the Error Sound Initialization message.

    Installed Rocksmith Mods Installer 1.2.7.4, but made not any changes yet.

    Rocksmith.ini.png

    RS_ASIO.png

    RS Mods Installer screen.png

     

     

  10. That would be great, thanks!

    Focusrite Control software, newest version (3.18.0) already installed.

    I just did a full re-install of Rocksmith, without any modifications, and run Rocksmith for the first time.

    I got sound, but it stutters.

    After that i close Rocksmith and placed the RS_ASIO files into the directory, and made the changes as mentioned  in the tutorial above.

    No sound, and i got the Error Sound Initialization message.

    Installed Rocksmith Mods Installer 1.2.7.4, but made not any changes yet.

     

    Rocksmith.ini.png

    RS_ASIO.png

    RS Mods Installer screen.png

  11.  

    Does anyone have a solution to get the Focusrite Solo 3rd edition working under Windows 11?
    I recently switched from Windows 10 to Windows 11.
    
    It took a lot of effort, but I finally managed to get the Focusrite working in Windows 10 using the info in the link below:

    https://github.com/mdias/rs_asio

     

    Before switching to Windows 11 I made a backup of the most important files needed such as avrt.dll, RS_ASIO.dll, RS_ASIO.ini, and Rocksmith.ini.
    After the new Windows 11 and Rocksmith installation, I placed the files back in the correct directory. problem solved!
    but no...No matter what I try, Rocksmith just no longer sees my Focusrite interface. I then get the message that the Rocksmith cable is not connected.
    the sound in rocksmith works normally.
    So I reinstalled Rocksmith and went through the above procedure again, and again...and again.!:P Re-installed Rocksmith..but with no luck

     

    My Focusrite interface works fine under windows 11 because i use it also with Amplitube, so it must be a Rocksmith issue.

    So, what i have done so far:

    setting audio interface at 48khz . also tried 96 and 192, but than i get  Error Sound Initialization. so i put it back to default.

    Disabled all other audio devices incl the onboard soundcard

    changed the channel settings from 1 to 2 corresponding to the channel settings i use in Amplitube.

    in rocksmith.ini I had to set ExclusiveMode from 1 to 0 otherwise my sound would stutter,

     

    but even then the interface is not recognized.

     

    changing TheRealtoneCableonly setting from 0 to 1 makes no difference.

    Tried RSmods

    changed the windows audio settings to: 24bit, 48000(studio quality)

    and followed a lot of youtube tutorials  to find a solution for the problem.

    For now, the only way that works is with the Rocksmith cable plugged in....

     

     

     

     

     

    Who has the solution for this because I don't know anymore

     

     

     

     

     

  12. Rocksmith 2014 has rocked out for the last time: Almost 10 years to the day after the acclaimed learn-to-play-guitar game debuted, Ubisoft has removed it from sale on all digital storefronts as of October 23, 2023. DLC packs and Singles for Rocksmith 2014 will be removed from those storefronts over time as well."

    Of course I have already purchased Rocksmith via Steam and I play it daily. 
    It is said that once you have purchased Rocksmith via Steam, you can simply download it and install it again. 
    But who guarantees for how long? therefore my next question. 
    Is there a method to re-download the installer files from steam, for example, so that I can save them for later installation of the game? 
    Of course it is in my Steam library, but who guarantees that if I ever want to clean up my PC and I have to reinstall Steam, I can also reinstall Rocksmith.
    With this they force you to make the switch to Rocksmith +. And I do not want that.

     

  13. 3 hours ago, Shroud said:

    Do you mean that the original audio of the song is too loud, or that the sound of your guitar is too loud?

    If the problem is with the original song audio, you can open the CDLC with Custom Forge Song Manager, right-click on it, select "Edit Song Information" and then modify the "Song Volume" value.

    If the problem is with the guitar sound, you need to edit the "tones" used by the CDLC, but Custom Forge Song Manager doesn't do that. If you don't mind a non-permanent solution, from within the Rocksmith game you can pick any existing tone from your DLC/CDLC collection or create your own tone, and assign it to one of the quick tones slots, so that you can switch to using that tone while playing a song by hitting the corresponding key 2, 3 or 4 on the keyboard. This is what I use when I stumble on a CDLC that has an annoying or flat-out wrong tone 🙂

    No sure, i think the original audio is ok. It only happens when in Rocksmith while playing the tone switch changes to the destorted part. than the guitar sound is way too loud.

    But thanks! i'll try to find out how to edit the tones within rocksmith

  14. Won't work for me. tried above instructions. on MacOS Monterey Intel CPU.

    Think i've bricked Rocksmith. Game crashes immediately. Got an error messsage Rocksmith2014 quit unexpectedly

    used newest patch 1.6.

     

     

    ----------------

     

    Problem solved! used the older patch. Now it works perfect!

  15. Bryan Adams & Mel C - When You're Gone CDLC PC

    The CDLC of the song is actually already made by user PC Plum so i think it has to be arround somewhere but not downloadable here on Customforge.

    Do you have it? let me know! 😉

×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. - Privacy Policy