I corrected the path ahk > ahk\scripts This is the ahk script that gets BB to make the temp.txt that is in C:\bb\Data or wherever you have it. The ; just comments the line out. bb_track_info.ahk
Code:
#NoEnv
#SingleInstance Force
;MsgBox, Track Data to Text
Winactivate, ahk_class TBandWindow
WinMenuSelectItem, ahk_class TBandWindow, , Help, Utilities, Get Track Info
Send, 40
Send, +{Tab}
Send, {DOWN}
Send, {ENTER}
Send, {ENTER}
;Sleep, 3000
WinWait, ahk_class NOTEPAD.EXE, temp.txt,3
WinSet, Transparent, 100, ahk_class Notepad
Sleep, 50
;MsgBox, Pause
WinMenuSelectItem, ahk_exe NOTEPAD.EXE, , File, Exit
WinClose, ahk_class NOTEPAD.EXE, temp.txt ;close notepad
I've moved them to there, replacing files that existed.
Originally Posted By: musocity
I corrected the path ahk > ahk\scripts This is the ahk script that gets BB to make the temp.txt that is in C:\bb\Data or wherever you have it. The ; just comments the line out. bb_track_info.ahk
Code:
#NoEnv
#SingleInstance Force
;MsgBox, Track Data to Text
Winactivate, ahk_class TBandWindow
WinMenuSelectItem, ahk_class TBandWindow, , Help, Utilities, Get Track Info
Send, 40
Send, +{Tab}
Send, {DOWN}
Send, {ENTER}
Send, {ENTER}
;Sleep, 3000
WinWait, ahk_class NOTEPAD.EXE, temp.txt,3
WinSet, Transparent, 100, ahk_class Notepad
Sleep, 50
;MsgBox, Pause
WinMenuSelectItem, ahk_exe NOTEPAD.EXE, , File, Exit
WinClose, ahk_class NOTEPAD.EXE, temp.txt ;close notepad
I think my file is equivalent ... I have a few more commented-out lines:
Jazz relative beginner, starting at a much older age than was helpful. AVL:MXE Linux; Windows 11 BIAB2024 Audiophile, a bunch of other software. Kawai MP6, Ui24R, Focusrite Saffire Pro40 and Scarletts .
To check that Autohotkey is running the script and sending, put a pause in it, if it sends 40 then it should work, so then take the MsgBox line out and try again.
Code:
Code:
#NoEnv
#SingleInstance Force
;MsgBox, Track Data to Text
Winactivate, ahk_class TBandWindow
WinMenuSelectItem, ahk_class TBandWindow, , Help, Utilities, Get Track Info
Send, 40
MsgBox, Paused
....
....
It would be good if you get it all working on Linux.
I've eliminated a few things, but still get the, (like RTs with no notation) but still get the fail. I'm increasingly thinking that it's a failure to run AutoHotKey properly.
If I comment out import_sel_mid_trk_btn_click() it doesn't crash.
I've tried several variations on a theme of running AutoHotKey, but I'm very unclear at present which is the culprit. At line 37 in "Biab track injector GUI.lua" I have enabled the Msg and appended another thus:
Some earlier things I'd tried that may give clues where I can debug... I deleted the temp.txt file and ran the track import again.
I have a MsgBox at the line you suggested and also enabled to one right at the start. I don't get either dialog, which implies I'm not even getting to the code in biab_track_info.ahk
temp.txt has not been created.
This is the console output:
Code:
Error: Biab track injector GUI.lua:1334: cannot open file '/var/BiaB_etc/bb/Data/temp.txt' (No such file or directory)
Stack traceback:
ReaTrak_Core.lua:93: in function </home/gordon/.config/REAPER/Scripts/ReaTrak_Core.lua:84>
[C]: in function 'io.input'
Biab track injector GUI.lua:1334: in function 'read_lines'
Biab track injector GUI.lua:2694: in function 'gen_cur_track_sec_btn_click'
Biab track injector GUI.lua:2617: in function 'import_sel_trk_btn_click'
Biab track injector GUI.lua:1545: in function 'import_all_chk_tracks_btn_click'
Class - Button.lua:138: in method 'onmouseup'
ReaTrak_Core.lua:887: in field 'Update'
ReaTrak_Core.lua:440: in field 'Main_Update_Elms'
ReaTrak_Core.lua:307: in function </home/gordon/.config/REAPER/Scripts/ReaTrak_Core.lua:303>
[C]: in function 'xpcall'
ReaTrak_Core.lua:303: in function </home/gordon/.config/REAPER/Scripts/ReaTrak_Core.lua:302>
Lokasenna_GUI:this is the console output
v2.16.8
Reaper:
6.71/linux-x86_64
Platform:
Other
If generate an apparently sensible temp.txt file from BiaB, so that something does exist and then try to import tracks, this is the console output:
Code:
Error: Biab track injector GUI.lua:2485: attempt to perform arithmetic on a string value (global 'ppq_set')
Stack traceback:
ReaTrak_Core.lua:93: in metamethod '__div'
Biab track injector GUI.lua:2485: in function 'import_sel_mid_trk_btn_click'
Biab track injector GUI.lua:1546: in function 'import_all_chk_tracks_btn_click'
Class - Button.lua:138: in method 'onmouseup'
ReaTrak_Core.lua:887: in field 'Update'
ReaTrak_Core.lua:440: in field 'Main_Update_Elms'
ReaTrak_Core.lua:307: in function </home/gordon/.config/REAPER/Scripts/ReaTrak_Core.lua:303>
[C]: in function 'xpcall'
ReaTrak_Core.lua:303: in function </home/gordon/.config/REAPER/Scripts/ReaTrak_Core.lua:302>
Lokasenna_GUI:
v2.16.8
Reaper:
6.71/linux-x86_64
Platform:
Other
The "Attempt to perform arithmetic..." error suggests a further problem where perhaps the code and a field type don't match as they should?
Jazz relative beginner, starting at a much older age than was helpful. AVL:MXE Linux; Windows 11 BIAB2024 Audiophile, a bunch of other software. Kawai MP6, Ui24R, Focusrite Saffire Pro40 and Scarletts .
BTW, I wonder if we should continue this out of the thread as most BiaB users won't be interested it. If you presently don't have a Linux system, I may be the only person on the planet trying to do this.
Jazz relative beginner, starting at a much older age than was helpful. AVL:MXE Linux; Windows 11 BIAB2024 Audiophile, a bunch of other software. Kawai MP6, Ui24R, Focusrite Saffire Pro40 and Scarletts .
The Track Injector was made to show how quick things can work rather than waiting for renders. This was a bit complex for most users not too familiar with Reaper to implement. I simplified this into one script to make things easier:
If PG put the BBoutput.txt in C:\bb\Data this will contain all the track data for all current tracks so all tracks could be transferred with one click this will then work on Mac also:
When I try to import from Biab to Reaper selected Mixer Track (or what ever other actions) I get following error messages:
================================== Error: Biab track injector GUI.lua:1335: cannot open file 'C:\bb\Data\temp.txt' (No such file or directory Stack traceback: ReaTrak_Core.lua:93: in function <...o Talvio\AppData\Roaming\REAPER\Scripts\ReaTrak_Core.lua:84> [C]: in function 'io.input' Biab track injector GUI.lua:1335: in function 'read_lines' Biab track injector GUI.lua:2693: in function 'gen_cur_track_sec_btn_click' Biab track injector GUI.lua:2617: in function 'import_sel_trk_btn_click' Class - Button.lua:138: in method 'onmouseup' ReaTrak_Core.lua:887: in field 'Update' ReaTrak_Core.lua:440: in field 'Main_Update_Elms' ReaTrak_Core.lua:307: in function <...o Talvio\AppData\Roaming\REAPER\Scripts\ReaTrak_Core.lua:303> [C]: in function 'xpcall' ReaTrak_Core.lua:303: in function <...o Talvio\AppData\Roaming\REAPER\Scripts\ReaTrak_Core.lua:302>
Have you got AutoHotkey installed along with the scripts. Is AutoHotket set to Run As Administrator. Did you edit the menu in bbw64.exe so Reaper can access the Biab commands. Are you using Biab ver up to 1003
So when you click "Import Selected Mixer Track" in the Reaper Injector GUI it will run bb_track_info.ahk that will access the Biab menu > Help, Utilities, Get Track Info this will write the C:\bb\Data\temp.txt with the track data that Reaper will import.
This is what you should get, you should see notepad popup then close, I have it set to import wav as I have the Audiophile version: this is the temp.txt for 388 Bass in C:\bb\RealTracks right click Save Link/Target As Bass temp.txt out it in C:\bb\Data\ then try, if that works ok when you click Import Selected Track then it's just not accessing the Biab menu.
>> Have you got AutoHotkey installed along with the scripts. I have installed version AutoHotkey_1.1.36.02_setup. I don't understand what you mean by "along with the scripts"
>> Is AutoHotket set to Run As Administrator. Yes it is.
>> Did you edit the menu in bbw64.exe so Reaper can access the Biab commands. Yes by this commands:
object Track: TMenuItem Caption = 'T&rack' object TrackMenuItemID1224: TMenuItem Tag = 1224 Caption = 'Get Track Info' end end
>> Are you using Biab ver up to 1003 My Biab version is 1011 (Audiophile). I noticed that if I open bbw64.exe after compile, save and close the Resource Hacker window again nothing has been changed?? Might there be in new Resource Hacker session the text above ( object Track: ... end)?
>> This is what you should get, you should see notepad popup then close I can't see this at all
>> I have it set to import wav as I have the Audiophile version I have Audiophile version 1011 also. Where I can set to import wav??
When I try to "Import Selected Mixer Track" I get following error message:
----------------------------------- Oops
Biab track injector GUI.lua has Crashed! Would you like to have a crash report printed to the Reaper console? Yes/ No -----------------------------------
Error: Biab track injector GUI.lua:1335: cannot open file 'C:\bb\Data\temp.txt' (No such file or directory)
Stack traceback: ReaTrak_Core.lua:93: in function <...o Talvio\AppData\Roaming\REAPER\Scripts\ReaTrak_Core.lua:84> [C]: in function 'io.input' Biab track injector GUI.lua:1335: in function 'read_lines' Biab track injector GUI.lua:2693: in function 'gen_cur_track_sec_btn_click' Biab track injector GUI.lua:2617: in function 'import_sel_trk_btn_click' Class - Button.lua:138: in method 'onmouseup' ReaTrak_Core.lua:887: in field 'Update' ReaTrak_Core.lua:440: in field 'Main_Update_Elms' ReaTrak_Core.lua:307: in function <...o Talvio\AppData\Roaming\REAPER\Scripts\ReaTrak_Core.lua:303> [C]: in function 'xpcall' ReaTrak_Core.lua:303: in function <...o Talvio\AppData\Roaming\REAPER\Scripts\ReaTrak_Core.lua:302>
You need to run 1003 or earlier for the menu to work. Even a 2022 version will open a frozen SGU of 2023 you can run an old version along side the current just to use track injector. This way you will get the exact same track sections in Reaper as in Biab, you can even convert the track to DI or from DI.
That temp.txt is set to look for the tracks on C:\ it's good you are using Audiophile, just edit the temp.txt all Replace all C:\ with your drive letter for Audiophile eg: F:\
For those that don't have the Audiophile you just select wma in the settings. You can also batch convert your RealTracks & Drums to any format you want to use in Reaper, so you will have original wma or wav and also FLAC WavePack MP3 OGG M4A AIFF etc... You can have a frozen SGU with 255 bars and the tracks will be injected into Reaper instantly without Biab even having to generate them up into RAM. If you have a 255 bar Biab song with Util tracks it can take a very long time to generate up then render but with the track injector you don't need to as they are instantly in Reaper. Any section of track in Reaper can be replaced at any time giving total user control of a song build being able to replace FX RT's with DI RT's or vice versa keeping the same notes. The tracks are fitted to any decimal changing tempo map allowing you to easily add extra instrument tracks/sections to a live recorded session.
Here is a very simple way, these are 2 simple Reaper scripts that will import selected Biab mixer tracks directly into Reaper instantly. Insert new track import bb temp txt data.zip Import bb temp txt data section to selected track.zip To insert new section of track into Reaper, delete the section you don't like then in Biab on an empty track use Alt+F8 to generate up the RT section you need then run the script to transfer to selected track in Reaper. This allows you to change any section you like as you don't have a consolidated wav file, it uses your source wma or wav files. **DON'T use the "move" option when saving in Reaper, it will load the files direct from the RealTracks and RealDrums folders same as Biab will do. If you open a frozen SGU in Biab it will import the tracks without having to generate them up first.
Just spent several hours following the install instructions to the letter for both the injector and the two scripts recently posted in this thread. No joy. Much frustration. But alas, it's more complicated than I was hoping for. Having to run AutoKey in "no-UAC" mode is a show stopper for this security conscious musician.
That said, I don't easily give up but I have run out of time and patience in trying to get this to work, let alone have it be something that makes my workstream easier, faster, etcetera. While I can appreciate that dragging and dropping RealTracks from BIAB to Reaper has limitations, I personally don't mind waiting the few seconds it takes to generate a track.
The main issue I had was decimal point tempos, and was hoping the injector could improve upon my process. Specifically: how to get a RealTrack generated at 90bpm in BIAB to play in Reaper at the 90.8 tempo my project is set for? The answer is Real Band. BIAB doesn't allow decimal point tempos, but Real Band does. This means I'm setting up tracks in BIAB, then open the SGU in RealBand, and RealBand will put the 90bpm tracks at 90.8 after which you then drag and drop from Real Band to Reaper. I'm waiting on average 3 or 5 seconds for RealBand to adjust the tracks to the decimal tempos and then I am good to go.
In summary, this injector is a fantastic idea and it would really give us users a great deal of control creatively without having to change the underlying architecture. Autokey, SWS, editing scripts, and compiling executables ain't for the faint of heart or the non-technical musician, at least not this one.
In summary, this injector is a fantastic idea and it would really give us users a great deal of control creatively without having to change the underlying architecture.
It would all just work so easy to give users this ease of use, I have asked PG to write the track data for all tracks by default to to C:bb\Data as a text file each time Biab generates to save having to hack into menus just to get what you need, BUT PG have blocked this from working in newer versions and have even blocked the BBoutput.txt in the BBPlugin from working to give track section data to allow users to import the track data direct to Reaper as wma or wav, this is craziness as I went to so much trouble creating something to give Biab users a quantum leap in total control of creativity that I have been looking for 14 years for. Reaper implemented wma to be played from disk and this works really well, and PG are the ONLY company to use WMA for this whole purpose. PG don't seem to want to give this control and creativity to Biab users, they would rather users wait for Biab to take ages rendering to a consolidated wav. I can't work out why Biab has to be behind rather than out front leading the way ? The whole idea of Reaper like it's predecessor WinAmp is to give control to the users and not wait for years and years and years for something to be implemented like PG do, then they get it wrong because they don't listen and we have to wait yet another year in hopes that it will be fixed, users actually die waiting.
I have been at this for 14 years (I could be next) because when I first used Biab/RB back then to add tracks to artist recorded sessions it was the most frustrating piece of software to get what you needed. It has been such an incredibly slow year in year out process to try and get it there. I know PG hate me saying the obvious and usually delete these post rather than acting on constructive criticism and understanding that I have stayed the long haul. Maybe it's a slow drip-sell thing so that it keeps users coming back every year to buy Biab again for drip feed features rather than buying it for the great new content added each year ! it's a creativity killer
This is all got too much so what I'm thinking about looking into now is having Reaper access a server that will give all the txt track data to the user from Reaper chords or SGU they upload, all the tracks or sections will just go instantly into Reaper from the user's source RT RD tracks.
This is all got too much so what I'm thinking about looking into now is having Reaper access a server that will give all the txt track data to the user from Reaper chords or SGU they upload, all the tracks or sections will just go instantly into Reaper from the user's source RT RD tracks.
That reads like a cool thing. Lots of work, lots of time & lots of frustration for you but you're doing excellent work.
Last edited by rayc; 06/26/2311:42 AM.
Cheers rayc "What's so funny about peace, love & understanding?" - N.Lowe
Update your Band-in-a-Box® 2025 for Windows® Today!
If you’ve already purchased Band-in-a-Box® 2025 for Windows®, great news—a new update is now available! This update introduces a handy new feature: a vertical cursor in the Tracks window that shows the current location across all tracks, and more.
Video: Band-in-a-Box® 2025 for Windows®: Boot Camp: The AI Lyrics Generator
With Band-in-a-Box 2025® for Windows®, we've introduced an exciting new feature: the AI Lyrics Generator! In this video, Tobin guides you step-by-step on how to make the most of this new tool.
Band-in-a-Box® 2025 for Windows®: Boot Camp: The AI Lyrics Generator video.
Video: Band-in-a-Box® 2025 for Windows®: Using VST3 Plugins
Band-in-a-Box 2025® for Windows® now includes support for VST3 plugins, bringing even more creative possibilities to your music production. Join Simon as he guides you through the process in this easy-to-follow demonstration!
Video: Band-in-a-Box® 2025 for Windows®: Using VST3 Plugins
Video: Band-in-a-Box 2025 for Windows: Using The BB Stem Splitter!
In this video, Tobin provides a crash course on using the new BB Stem Splitter feature included in Band-in-a-Box 2025® for Windows®. During this process he also uses the Audio Chord Wizard (ACW) and the new Equalize Tempo feature.
Video: Band-in-a-Box® 2025 for Windows®: Using the BB Stem Splitter
Check out the forum post for some optional Tips & Tricks!
Congrats to Misha (Rustyspoon)…downloaded/installed a full Audiophile 2025!
Breaking News!
We’re thrilled to announce that Rustyspoon has made PG history as the very first person to successfully complete the download and install of the full Band-in-a-Box 2025 Windows Audiophile Edition (with FLAC files)—a whopping 610GB of data!
A big shoutout to Rustyspoon for stepping up to be our test "elf!"
With the launch of Band-in-a-Box® 2025 for Windows, we're adding new videos to our YouTube channel. We'll also share them here once they are published so you can easily find all the Band-in-a-Box® 2025 and new Add-on videos in one place!
Whether it's a summary of the new features, demonstrations of the 202 new RealTracks, new XPro Styles PAK 8, or Xtra Styles PAKs 18, information on the 2025 49-PAK, or detailed tutorials for other Band-in-a-Box® 2025 features, we have you covered!
Band-in-a-Box® 2025 for Windows is here, packed with major new features and an incredible collection of available new content! This includes 202 RealTracks (in Sets 449-467), plus 20 bonus Unreleased RealTracks in the 2025 49-PAK. There are new RealStyles, MIDI SuperTracks, Instrumental Studies, “Songs with Vocals” Artist Performance Sets, Playable RealTracks Set 4, two new sets of “RealDrums Stems,” XPro Styles PAK 8, Xtra Styles PAK 19, and more!
Special Offers
Upgrade to Band-in-a-Box® 2025 with savings of up to 50% on most upgrade packages during our special—available until December 31, 2024! Visit our Band-in-a-Box® packages page for all the purchase options available.
2025 Free Bonus PAK & 49-PAK Add-ons
We've packed our Free Bonus PAK & 49-PAK with some incredible Add-ons! The Free Bonus PAK is automatically included with most Band-in-a-Box® for Windows 2025 packages, but for even more Add-ons (including 20 Unreleased RealTracks!) upgrade to the 2025 49-PAK for only $49. You can see the full lists of items in each package, and listen to demos here.
If you have any questions, feel free to connect with us directly—we’re here to help!
One of our representatives will be happy to help you over the phone. Our hours of operation are from
6:00AM to 6:00PM PST (GMT -8) Monday thru Friday, and 8:00AM to 4:00PM PST Saturday. We are closed Sunday. You can also send us your questions via email.
One of our representatives will be happy to help you on our Live Chat or by email. Our hours of operation are from
6:00AM to 6:00PM PST (GMT -8) Monday thru Friday; 8:00AM to 4:00PM PST (GMT -8) Saturday; Closed Sunday.
?
Dansk
Deutsch - Windows
Español
Français - Windows
Italiano - Windows
Nederlands
Polski
Português
Svenskt
русский
Japanese
Simplified Chinese
Traditional Chinese
Korean