I am pleased to announce that new Rocksmith Custom Song Toolkit.
 
All thanks to the developers involved in the project that made this feasible possibility in so little time.
 
DEVS:
* me;
* Snakez;
* Maveth;
* Raynebc;
* Dreddfoxx;
* Alex360 (L0fka);
* Shrubbery (otaznik);
* Cozy1;
* Zephyrix;
* Xavatar (PowerSlinky);
* Chlipouni;
* Cgeorge;
 
TESTERS (consoles):
* Acid6D94 (XBox 360);
* Redeyed (PS3);
* Kim666 (PS3);
 
And among others for PC/Mac.
 
DOWNLOAD:
http://www.rscustom.net/
 
NOW WITH A RELEASE FOR MONO (CAN BE USED ON MAC) !!!
 
ANY ISSUE? TRY TO DOWNLOAD THE LAST BUILD:
http://www.rscustom.net/builds
 
IF PROBLEM PERSISTS, OPEN AN ISSUE IN THE PROJECT ON GITHUB:
https://github.com/rscustom/rocksmith-custom-song-toolkit/issues
 
 
NEW VERSION INCLUDE:
 

NEW IN 2.6.0.0:* New auto-update feature (shows changes from your version and allow update with one click);* Added InlayCreator (new package type to customize your guitar) [all credits to Cozy1 and Baoulletes for this feature];* Added config screen that you can pre-define some fields in toolkit;* Added song preview volume box to make preview independant of song volume;* Added structured project import option;* Added package author (charter name) inside the package (can be setup on config screen, default value is "Custom Song Creator", but you can define your name if you want);* Added background worker with progress bar for most toolkit features (Generate package, unpacker, update appid, etc);* Added option to use acronym in file names when generate packages;* Fixed DLCConverter CLI issues;* Fixed packer for mod purposes;* SNG 2 XML general issues fixed;* Enhanced package validation;* Toolkit random hangs fixed;* Package random crashes fixed;* Fixed auto-tone load with ToneC and ToneD in some cases;* Fixed Import Template from package (tuning frequency and some minor issues);* Fixed some existent appIds and added new ones;* DDC updated to 2.2;* Fixed packer for larger than 100mb files;* Minor issue fixes.

 
Note: RS2014 CDLC support almost all new features like new techniques, custom tunings, Tuning Pitch (frequency), Mac platform, etc.
 
This new version of toolkit require lastest version of Editor-on-Fire (EoF) 1.8RC8(r1281) or above.
 
To play custom songs on PC and Mac platform is required a patch to bypass song signature that will be released in a tutorial in smithyanvil. (for consoles is not required).
 





 
==============================================
 
CHANGE LOG:

 

2.5.0.0:* Packer/Unpacker Tab new layout;* New SNG Tab, that is the gui to sng2014 CLI;* New tool sng2014 CLI that allow pack/encrypt and decrypt/unpack sng, convert song xml to sng and sng to song xml;* DDC 2.1 update;* Packer/Unpacker now generate song xml if it doesn't exists;* DLC Converter now supports non custom packages;* DDC now supports non custom packages;* Changed keyboard shortcuts from Global to OnFocus;* Fixed game file packer like cache.psarc for mod purposes;* Allow DragDrop in DDC Tab file list;* Fixed absolute paths in Mac;* Fixed DD bars not appears in song preview;* Changed package and template default name replacing "_" to "-" in name spaces;* Fixed tuning frequency in toolkit is not the same in game;* Fixed DDC progress bar not update;* Fixed tuning pitch/frequency is not imported on Import template or DLC Converter;* AppId updated;* Fixed sng cleanups that cause arrangement don't start play after tuning in some cases;* New showlight algorithm that works better;* Fixed tuning auto selector in some cases;2.4.1.0:* Allow Update AppId for Mac packages;* Showlights are now generated by toolkit;* Fixed a lot of bugs in DLC Converter envolved XBox 360 and PS3 conversions;* Added sng2014 CLI to unpack/decrypt and encrypt/pack a SNG 2014 file;* Fixed error when Dynamic Difficulty level bars are not displayed in DDC generated files;* Added recent AppIds;* Added arguments to predefine platform and game version on packer CLI;* Fixed RS1 Packer/Unpacker and RS1 AppId Updater;* DDC Tab was improved;* Fixed "Index out of range" on any key is pressed in DLC Package Creator Tab;* Fixed issue when wem file was wrongly converted in some cases;* General small fixes. 2.4.0.1:* Added One Click Dynamic Difficulty Generator for custom song packages;* Added Import project template from Package (You generate a project from a package, edit values and regenerate song again without loss information);* Added Tuning Editor (now you can edit and add new tunings from GUI);* New tunings are now automatically imported to local database when add new arrangement or import packages;* Added option to use DDC Tab with Clean Process (overwrite original arrangament xml and don't generate DDC logs);* DDC updated to 2.0 with two new difficulty templates (thanks to Chlipouni);* Removed "Change output folder" from DDC Tab because the normal process doesn't overwrite original file, so this feature have no utility;* Fixed Mac > PC DLC conversion;* Added shortcut for most used actions in DLC Package Creator Tab:--- Ctrl + Shift + O = Open Package Template;--- Ctrl + Shift + S = Save Package Template;--- Ctrl + Shift + I = Import * Package Template;--- Ctrl + Shift + G = Generate Package (song);--- Ctrl + Shift + A = Add new Arrangement;--- Ctrl + Shift + T = Add new Tone;* Fixed some packer CLI issues. 2.3.1.0:* Fixed CAPO feature in CLDC;* Fixed Tuning Pitch (CentOffSet) for some tuning frequencies;* Added option to duplicate a tone;* Fixed DLC Converter when convert X360 packages from another platform;* A lot of fixes in DLC Converter (song year is 0, lost dynamic density, vocal and preview are lost, etc);* Recover RS2012 package generation support;* DDC updated to 1.9;* A lot fixes for DDC integration;* Added default name when generate package;* Added version field for user define version of the package;* Added validation for null tones to avoid problem with CDLC;* Added recently official DLC App Ids;* Fixed ParentPrevNote in song file (sng);* Set RS14 as default version in DLC Packer/Unpacker;* Defined Cherub Rock as default app id in DLC Converter;* A lot of fixes in showlights;* Added option to open folder where package was saved;* A lot of minor bug fixes. 2.3.0.0:* Package Creator only need one audio file to create packages for all platforms (RS1 and RS2014);* Tone import from profile (You can design your tone in Tone Design in game and import in Toolkit);* DDC update to v1.5 (thanks to chlipouni);* Added java check/explanation for PS3 package creation;* DLC Converter minor fixes;* Fixed AppId disappears when PC is not selected;* Fixed problem with pack/unpack RS2014 game files (for mod purporses);* Minor bug fixes. 2.2.2.1:* Fixed issue with load/create new and save tones;* Fixed bonus Arrangement displaying as normal arrangement;* Make the second arrangement of the same arrangement type as ALTERNATE arrangement ingame;* DDC Tab fixes and enhancements;* Fixed issue with load bass arrangement that have more than one tuning match in tuningdefinition repository;* Added fixes to solution to compile with mono in Mac;* Fixed default AppId is not setup when toolkit load;* Make US Holliday Pack (RS1) and Cherub Rock (RS14) as default AppId;* Fixed AppId not update on DLC Converter tab when target is PC/Mac. 2.2.2.0:* New DLC Converter CLI tool;* Fixed Audio Decode when Unpack songs in some environments;* Added option to convert ogg audio file between platforms like (WEM file);* RS1: Fixed error knob button not enable for editing and not load from package template;* DLC Converter: Fixed tmp folder not deleted after conversion;* DLC Converter: Fixed some arrangement identifications that cause crash on some conversions;* Fixed tone slot not enable for any arrangements;* Tone slot are now disabled when arrangement with auto tone setup is selected to prevent auto tone change to fail (user can enable slots again by check an option); 2.2.1.0:* Audio Converter Tab now can convert .WEM files between platforms (Desktop  Console);* DLC Converter now convert any platform with one click;* DLC Converter now convert multiples files at once;* DDC updated to 1.4 (thanks to chlipouni);* More Auto Tone Change Improvements and validations;* packer CLI: Fixed file paths;* Minor bug fixes. 2.2.0.2:* DDC Tab updated with new DDC 1.3 and new better interface that allow to apply DD in arrangements xmls or packages;* DLC Convert fix for Mac platform and many improvements;* PS3 package name fix (can't be space character due to encryption limitation);* Added validation to average tempo to avoid invalid value alert;* New Appids;* Sorted AppIds by name to easy artist identification;* Fixed tone edit when imported tone;* Auto tone change improvements;* Removed gameplay path for RS1 packages;* Fixed tuning issues for RS1 packages;* Many improvements and bug fixes. 2.2.0.0:* Full support for create RS2014 custom songs (all toolkit features included like packer/unpacker, packer CLI, AppId Update, tone import, etc);* New improved interface;* All platforms supported, including Mac (RS2014) and a improved PS3 support;* RS2014 only: New DLC Converter (allow user to convert from any platform to another with one click);* DDC integrated (Dynamic Difficulty Creator) [thanks to chlipouni];* Packer/Unpacker now compatible with any platform and game version include PS3;* So many improvements and bug fixes. 1.4.0.1:* Added option to encrypt files on 'pcdecrypt.exe' CLI.* Fixed Repack (APP_ID) problem (issues #59 #61);* Fixed problem with special/accented characters on save/load DLC template and Tones (XML) (issue #54);* Fixed HandShape ChordId field is wrong type (issue 66). 1.4.0.0:* Added 'SNG/Package 2 Tablature' (ASCI) converter [thanks to Thierry Steinberg];* Added 'Packer/Unpacker' CLI (Using 'packer.exe' users can pack/unpack a song in command line);* Added 'Build' CLI (Using 'packer.exe' users can build a song in command line from Rocksmith DLC template *.dlc.xml)[thanks to Adam Sloboda]* Added an option to recreate SNG on 'Packer/Unpacker' tab;* Added an option to specify PersistentID and MasterID on arrangement (this feature allow user to maintain scores after rebuild a song)[thanks to Adam Sloboda];* SongAppId list moved to a Xml file (now users can add new AppId);* Several fixes and minor improvements. 1.3.0.0:* Added fully support for PS3 custom songs (generate edat files);* Fix US holiday pack ID;* Fixed executable name;* Minor bug fixes. 1.2.0.1:* Added partial support for PS3 custom songs (generate PSAC files, but need other tool to encrypt to .edat and pack into .pkg file);* Fixed a problem where bass tones were not labeled as bass tones;* Added a few APP_ID's, and fixed the Rush ones;* Minor bug fixes. 1.1.5.2:* Fixed problem in Ogg Converter Wwise decode in some environments;* Removed validation that requires them to have a section near the END phrase at the end of the song;* Added validation to block special characters in tone name to avoid unpacking problems and others;* Added function to allow user reorder arrangements and tones (using keyboard keys: up, down, page up, page down, -, +);* Changed packing function to preserve package signature type and all license keys of package. 1.1.5.1:* Fixed error when pack a XBox 360 multi-song DLC (DLC Pack);* Fixed the OGG decode process when path have spaces;* Added support to import tones from XBox 360 DLC packages;* Added option to decode OGG when unpack songs;* Added button to restart application. 1.1.5.0:* Added function to convert Wwise/Rocksmith OGG format to OGG default readable by EoF and players. 1.1.4.4:* Fixed problem when XBox 360 packages are generated with double size. 1.1.4.3:* Fixed the volume value don't load from DLC saved data. 1.1.4.2:* Fixed "Tone Import" on packed song. 1.1.4.1:* Fixed "Packer/Unpacker" > "Update App Id" function. 1.1.4.0:* Packer/Unpacker now supports XBox360. 1.1.3.1:* Added song volume control;* PC and XBox 360 are now with same volume level;* Changed tab order (since it's no longer necessary to use the "SNG File Creator" and "Ogg Converter" tab). 1.1.3.0:* Fixed tone bug in XBox360 packages;* Enabled XBox360 tone;* Fixed MasterID for consoles;* Removed tone reference in vocal arrangement. 1.1.2.4:* Delete temp generated SNG files when generate packages;* Fix bass hopo technique and bass chord density. 1.1.2.3:* New APP ID;* Fixed problem when edit an arrangement and try load information from XML chart. 1.1.2.2:* Fixed tone not saving when loaded. 1.1.2.1:* Little fix to import data of arrangement XML chart;* Fixed Bass arrangement not selected when imported data from arrangement XML chart. 1.1.2.0:* Automatically populate some fields information from the arrangement XML chart. 1.1.1.6:* Allow multiple Bass arrangement in song. 1.1.1.5:* Fixed tone changes not saved when name don't changed. 1.1.1.4:* Fixed a bug when try to generate a package that has no vocals arrangement. 1.1.1.3:* Changed the arrangement list to not display tone name on vocals arrangement, they don't use;* Changed the add arrangement window to show only relevant options for arrangement type;* Fixed knob settings crash error if more than 9 knob settings like with (Bass) Boutique 800;* Changes Xlock to generate in same order of the official DLC file to make easy comparison;* Added validation in DLC name to remove invalid characters. 1.1.1.2:* Fixed song partition count that set up arrangement name count, eg.: "Combo 1", "Combo 2", now Bass always is "Bass" and not "Bass 3" anymore;* Fixed title ID to default Rocksmith title ID for XBox 360;* Removed dynamic information from imported tone;* Added validation in DLC name to remove invalid characters;* Fixed BinaryVersion (arrangement type) in XBlock file that is not anymore with fixed values. 1.1.1.1:* Fixed Packer/Unpacker display position. 1.1.1.0:* XBox 360 support (tones not work for XBox at this time);* Added fields to define song name sort and artist name sort;* Fixed problem with CueTextBox, now has greater compatibility in all environments;* Fixed problem when user cancel tone editing and it's saved anyway;* Fixed app id don't selected from saved app id in saved DLC data;* Fixed field tab index in Package Creator;* Fixed problem on Ziggy Pro Converter Tab width that don't display "browse" buttons;* Fixed width of the form to view all tabs correctly.

 

 

I HAVE A BUG!  =]

 

been chasing this down for a few days, and with some help from the DDC guy and some others, i finally figured out its happening when the package is generated by the RST.

 

heres the files: 

https://drive.google.com/file/d/0B2TjljRp4LJucVJYdmQxWWx3M0k/view?usp=sharing

 

using the latest beta (2.6.1.0-0f95ae0d - this doesnt happen with 2.6.0.0), when i hit 'generate', the original xml files are being re-written with some extra garbage at the end. i assume thats whats going into the package too.

 

should the original xml files even be touched? i assumed they were just dropped into the package. 

 

anyway... at this point this is just a bug report, since i've figured out enough to fix the issue with zero problems... but i figured i should at least report the bug.

 

thanx a ton for everything you guys do.

Im on the latest revision. In the Add Arrangement window the Scroll Speed bar can be dragged below 1.0 till 0.5. Is this intended or a bug? It has always been only till 1.0 and even in the configuration tab you can at the moment only set a default scroll speed of 1.0 and not less.

 

About the Wwise convert feature in the Toolkit. I updated only recently to the newest revision of the toolkit with that feature, what i noticed is that if you enter an already converted .wem file that the toolkit will still converted it again based on the audio quality setting in the gui. A check should probably be added that does jump the convert feature of the toolkit if the .wem file is already entered using the file chooser.

Scroll speed is just inconsistent and will be fixed in future release.   About Wwise conversion, if you only provide main auido WEM then toolkit will regenerate main audio WEM and also prepare preview WEM.  You must provide both main auido and preview WEM files in order for the toolkit to not regenerate the audio.  This is the expected behavior.

 

EDIT:  Alex360 tells me that giri giri chop has a 0.9 scroll speed, so that is reason for scroll speed minimum changed.

@@III_Demon

The latest version of the toolkit does update the XML file(s) if the user make any changes to song information, e.g. title, date, tuning, tones, etc. This is the expected behavior and gives greater flexibility to the user to make last minute changes or revisions to existing CDLC songs from within the toolkit.

 

I am seeing the data you referenced after the "song" end tag.  Only seems to occur with XML from EOF.  No fix is need since the latest version takes away user changes to XML.

 

Edit: Re enabled Xml updating after user edits for testing.  End tag issue is fixed.

btw. the auto convert with the toolkit from ogg to wem is a nice feature. thanks.

Toolkit version: c37d42bd9b

I get a new error when I want to save a template as an XML:

 

 

http://puu.sh/gSQZk/77bfa908f2.png/ss%20%282015-03-28%20at%2010.57.21%29.png

 

It also comes up with errors like: "Part REAL_GUITAR" does not exist, when I try to generate a package. It saves just fine when there are no arrangements added.

 

When I downgrade to eea374be0e the errors are gone, and the toolkit saves the file just fine.

Toolkit version: c37d42bd9b

I get a new error when I want to save a template as an XML:

 

Same problem here.

related topic: http://customsforge.com/topic/18148-cant-save-packages/

The most recent test build seems to allow me to save packages again, but the Configuration information seems to constantly blank itself still.

 

That is, no matter what I change in the Configuration tab, it resets to blank (or the first option for lists) the next time I check it, even in the same session. Anyone else having this issue? I notice a lot of the information doesn't match up with a file created from scratch (AppID in particular defaulting to Amber by 311 in Configuration, whereas the Toolkit still defaults to Cherub Rock with a new project), so is it mostly visual or?

 

Thanks for your time,

 

(also i love the ability to bypass Wwise entirely so i just thought i'd say thanks for that as well)

Guys thanks for your patience.  @@Alex360 and I are trying to make some upgrades to the toolkit as you figured out by the number of bugs you are finding.  Please hang in there, we promise it will get better and we think you will like the new features.  Like on the fly modification of song information right from the toolkit without having to re author in EOF.  Like converting your RS2012 CDLC to RS2014 CDLC automatically.  Like automatically converting wav/ogg audio files directly to wem audio from the toolkit without even having to open the Wwise GUI. And other new upgraded features.

 

If you are working on critical charting project then I might suggest that you continue to use the latest official release of the toolkit.  If you are willing to test drive the toolkit beta releases and give us feedback, it would be appreciated.

 

The error that is discussed in this thread should have been corrected in the latest beta release if you would like to test it.  convert2012 CLI now has 99% sucessful conversion ratio. RS2012 CDLC's that can not be auto converted may still be able to be converted using the GUI. Converted RS2012 tones may/should be modified with the GUI. Fixed Template Save feature. Fixed XML Comment preserver. Fix Config save feature.  Fix Tone Not Found error.

 

Thanks for your patience and helping us make the toolkit better.

Cozy1

 

Feel free to PM feedback if you would like.

Tried new toolkit 838c30c3cb

 

Setup correct path to Wwise in config.

 

Populated all fields.

 

On save or generate I get "Please use WwiseCLI.exe to generate banks from the command line."

 

Then

 

http://images.ukcs.net/13647/New_Toolkit_Fault.JPG

 

 

Can't see any evidence of extended tone class to accomodate alternate amp skins, so I'm not too fussed.  Thought I would report anyway.

 

 

Thanks for the great work :D

 

 

 

I presume its just the way I have Wwise installed, its not a defualt installation by any means.

 

The toolkit worked when I fed it hand made .wems

Tried new toolkit 838c30c3cb

 

Setup correct path to Wwise in config.

 

Populated all fields...

 

 

 

I attempted to test the latest beta as well, set it up correctly in cofig. 

 

 

http://i.imgur.com/5052jKw.png

 

 

Thanks again for all the work!

With 838c30c3cb i also cant save the template, i get a Wwise exception. It was working fine with older builds.

 

The exceptions seems to be different

 

http://s3.postimg.org/ic8dvks5f/error.jpg

 

Edit: it works fine now, i had to enter the path of the WwiseCLI.exe, after that wem files converted fine. Its strange that in older builds i never entered the path but it was still working.

Thanks for the feedback. 

 

For the latest toolkit build the user has to enter path to WwiseCLI.exe in the toolkit configuration menu.  This was done at a user's suggestion, for users who do not have Wwise installed in the default path.  Setting the path to WwiseCLI.exe also makes loading the wem converter script much faster.  Please make sure you have specified the path to WwiseCLI.exe build 4828 in the configuration menu.

 

Please let me know if it is still not working and I will fix it.

 

EDIT:  Based on the error messages that are posted here the problem may be that users do not have Wwise Build 4828 installed.  This error message is typical of newer builds of Wwise.  Please check, confirm and report back.  Thanks

 

 

Based on the error messages that are posted here the problem may be that users do not have Wwise Build 4828 installed.  This error message is typical of newer builds of Wwise.  Please check, confirm and report back.  Thanks

 

 

Wwise Build 4828 doesn't appear to be available anymore.  The oldest one listed for download is 4856.

@@KJParsley It works with 4865 which is available, i haven't tried with the other version available.

@@KJParsley It works with 4865 which is available, i haven't tried with the other version available.

 

 

I had read that in someone's post earlier in the thread, so I downloaded it and replaced the Wwise2014 build I had installed originally.  However, yesterday Cozy1 said it needs to be build 4828 to work reliably?  Just trying to figure out what I should have installed to make things work right!

@@KJParsley,  cozy has a r4828 build so he tested it, I tested it also, Fire seems to have that recent build vvhich vvorks vvell too, you  can  choose any of them

@@Alex360

@@cozy1

 

The tuning Editor does have an annoying bug where the strings get changed.

 

For example:

I added in my new project as first the guitar lead arr. The Tuning is B Standard, the Tuning Editor Pops up with all strings set to -5, i enter as a name B Standard and its in the tuning list.

 

Now i add the second Rhythm guitar arr and the Tuning Editor pops up again, now i select the X to close the Tuning Editor because the tuning is already in the tuning list. To double check it i click on ... and open up the tuning of that last added Rhythm guitar arr and i see that the strings are fucked up.

String 0 = -5

String 1 = -5

String 2 = -5

String 3 = -5

String 4 = 0

String 5 = 0

 

The last 2 Strings are set at 0 and thats wrong.

@@MadMaxx, that's bass array, I tried to fix this long ago but I couldn't, Novv I have more exp in this, I knovv vvhat to do vvith this, need just time and vvill

btw. @@Alex360

 

i have noticed that the Wwise Audio Quality setting does not get stored or loaded correctly. I usually use 5 but i have noticed it a few times that 4 is loaded. If i save and load the project with the same toolkit instance the 5 is loaded fine but if i close the toolkit and start it again after i load the project xml 4 is loaded.

 

Is the quality setting supposed to be stored in the template/project xml file?

@MadMax  Turns out B Standard is not so standard ;)   It needs to be added to the tuning database first.  Here's is how to do it and work around for now till it can be fixed properly.

 

1.  From the Creator GUI, Add a new fake arrangement, open the Tuning Editor,  add B Standard tuning (-5, -5, -5, -5, -5, -5),  make sure you check box "Add as new Tuning", click OK.  Gracefully, close out of the toolkit so that toolkit saves the new tuning to the tuning database.

 

2.  Reopen the toolkit and add your lead arrangement in B Standard.  DO NOT open the tuning editor while in "Add Arrangement" mode.  Close "Add Arrangment" so that you are back at the main Creator GUI.  Now click "Edit" and go into "Edit Arrangement" mode.  Now you can open the "Tuning Editor" and will see the proper tuning.  So the trick (work around) here is to make sure you are in "Edit Arrangement" mode when subsequently using the Tuning Editor to check the tuning.

 

Arrangements will not revert to bass tuning if you follow this method.

Audio quality setting is not store.  You have to select it each time if you want something different than the default.  The default of 4 is actually quite good ~ 128 to 192 vbr kbps.

So the trick (work around) here is to make sure you are in "Edit Arrangement" mode when subsequently using the Tuning Editor to check the tuning.

 

Arrangements will not revert to bass tuning if you follow this method.

 

yeah i tried what you said and indeed if i dont open the Tuning Editor while i add the arrangement everything is fine after i double check the tuning in edit mode.

Thanks for the feedback. 

 

For the latest toolkit build the user has to enter path to WwiseCLI.exe in the toolkit configuration menu.  This was done at a user's suggestion, for users who do not have Wwise installed in the default path.  Setting the path to WwiseCLI.exe also makes loading the wem converter script much faster.  Please make sure you have specified the path to WwiseCLI.exe build 4828 in the configuration menu.

 

Please let me know if it is still not working and I will fix it.

 

EDIT:  Based on the error messages that are posted here the problem may be that users do not have Wwise Build 4828 installed.  This error message is typical of newer builds of Wwise.  Please check, confirm and report back.  Thanks

 

Ah now its clear thanks, than if the path to the WwiseCLI.exe was not entered just catch the exception and throw a messagebox stating that the path should be entered. That way the user knows what went wrong. A message like "The patch to WwiseCLI.exe is missing, please enter it in Configuration".

Another feature, in latest build, the toolkit will look for the default install of WwiseCLI.exe if the user does not set path in configuration.  So as long as you have a default install of Wwise build 4828 it will also work without configuration. 

 

Only exceptions thrown are if you have custom install and do not set configuration, and/or you have wrong version of Wwise.