scook Posted December 2, 2019 Author Posted December 2, 2019 6 minutes ago, gmp said: I understand why I should use Launchpad with 2019.09 and any later versions, because of CW130auto.dll. And I see only 2 CW130auto.dll in the "sub" folder. So how is Launchpad handling 2019.07 and all earlier versions of CbB? It seems like it would need all those versions of CW130auto.dll in the sub folder also. Yes, all versions of CbB need the dll. I use a generic dll for versions older than 2019-09.
scook Posted December 2, 2019 Author Posted December 2, 2019 3 minutes ago, User 905133 said: For the most part, programs seem to launch as expected (including appropriate warnings about files being made on newer versions, missing plug-ins, etc.). All of this is handled by the DAW. Launchpad just runs the DAW with or without file on the command line. The program serves two purposes: switching between versions of CbB managing lists of CbB projects, project templates and MIDI files (an alternative to the start screen).
gmp Posted December 2, 2019 Posted December 2, 2019 49 minutes ago, scook said: Yes, all versions of CbB need the dll. I use a generic dll for versions older than 2019-09. Thank you, I now understand
scook Posted December 2, 2019 Author Posted December 2, 2019 Updated Launchpad to v1.9 -Now it silently skips unsupported Cakewalk products instead of shutting down. See the OP for the link. For existing users do not delete the current Launchpad folder. To update, overwrite the current folder with the contents of the new zip. 1 1
chuckebaby Posted December 2, 2019 Posted December 2, 2019 I haven't tried this out yet but I have been following this thread. I must say this is really good Steve. I just downloaded it. Great details in the PDF as well. 1
user905133 Posted December 2, 2019 Posted December 2, 2019 (edited) 3 hours ago, scook said: Updated Launchpad to v1.9 -Now it silently skips unsupported Cakewalk products instead of shutting down. Just tested a few simple things (listing projects from different sources/folder locations, and launching projects and *.mid files to test). Seems to work just fine. Thanks again for adding the silent skip-unsupported-older-versions feature!! Edited December 2, 2019 by User 905133 fix typo 1
gmp Posted December 4, 2019 Posted December 4, 2019 On 12/1/2019 at 11:11 PM, scook said: Yes, all versions of CbB need the dll. I use a generic dll for versions older than 2019-09. T his all makes sense now, except I'm still curious how older Platinum versions can work without Launchpad. Do they use W130auto.dll? I also have Sonar 8.5, is hta tok too?
scook Posted December 4, 2019 Author Posted December 4, 2019 38 minutes ago, gmp said: I'm still curious how older Platinum versions can work without Launchpad. Do they use W130auto.dll? I also have Sonar 8.5, is hta tok too? CW130Auto.dll was created for CbB. SONAR releases have similar files under different names located in the same folder. What makes CbB different is rather than create a new dll and adjust the program to look for the new file, the decision was made to reuse dll name even though it is incompatible with prior releases of CbB. As I wrote above, this is CbB issue; it is not a SONAR issue. SONAR is not affected at all.
scook Posted March 18, 2021 Author Posted March 18, 2021 All new versions of Launchpad, Tools Editor, Upsample Editor and VST Inventory released as CbB Tools. A complete rewrite. All tools have font, style support and improved table displays Delivered as "CbB Tools.zip" containing a readme.pdf and "cbb tools.exe" As noted in the OP the zip is available from my Google page. Existing Launchpad users should copy "CbB Tools.exe" into their existing Launchpad folder. Other may copy "cbb tools.exe" into any folder such as "c:\program files\cbb tools". The readme has a little more info on install. Any questions? Please post them in this thread. thanks Some sample images follow 5
Jim Hurley Posted March 19, 2021 Posted March 19, 2021 I downloaded this and put it in 'C:\Program Files' as per the ReadMe.PDF I encountered one error on install, and each tool generated an error on start and some on close. 1
scook Posted March 19, 2021 Author Posted March 19, 2021 Hmm, that should be a Windows environment variable I will remove the code. It is not needed any more Give me a minute and I will post a new release.
scook Posted March 19, 2021 Author Posted March 19, 2021 The iniWrite failure for the UpsampleEditor happens when no PluginUpsample entry is present in Aud.ini I'll need to add a check for that. That will take a minute. Can you tell me which programs are throwing the other iniWrite errors?
scook Posted March 19, 2021 Author Posted March 19, 2021 Ok, Google finally refreshed. I believe v2.0.2 addresses the environment and upsampleeditor.ini errors. After recompile, I could not generate the two other iniWrite $tbl errors. They may be related to the environment failure. If they continue, please let me know which tools are throwing them I will take another look. Thanks for the feedback.
Jim Hurley Posted March 19, 2021 Posted March 19, 2021 When I use Load on the upsample editor I see this: Here is the log: ups-edit.log
scook Posted March 19, 2021 Author Posted March 19, 2021 v2.0.3 should be available now Fixes to upsampleeditor export and load Thanks again
Jim Hurley Posted March 19, 2021 Posted March 19, 2021 OK, I did a lot more testing this time and everything seems to work except the Upsample Editor. When i launch it is is empty and I can use Add to add one or more or all VSTs to the list. But when I exit I get this message in all cases: can't read "dawBox"...
scook Posted March 19, 2021 Author Posted March 19, 2021 Yeah, there is no DAW selection box in the main UI between File and Add. I will take a look at it.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now