![]() We're having a SALE on Band-in-a-Box® 2023 for Mac Upgrade purchases until save up to 50% when you purchase your Band-in-a-Box® 2023 for Mac Upgrade! With Band-in-a-Box® 2023 for Mac, we've added 70+ new features, including 10 MAJOR features: #387978 - 01/02/17 01:04 PM Re: BIAB MIDI export to Guitar Pro 6īand-in-a-Box® 2023 for Mac is here, and it includes over 70 new features and an amazing collection of new content, including 222 RealTracks (20 more than we've released in previous versions), new RealStyles, MIDI SuperTracks, Instrumental Studies, "Song with Vocals" Artist Performances, Playable RealTracks Set 2, Playable RealDrums Set 1, 2 new sets of "RealDrums Stems," and more! I'm using BIAB 2017 (recently upgraded from 2009) as administrator on Windows 7 (64bit), Intel i5 CPU, 8GB RAM But even when it worked to import the BIAB MIDI into, say, REAPER (my DAW), and then export it from there again, the resulting file behaves exactly the same in GP6, so the bug(?) seems to be passed on.Īfter searching the Internet the whole day for possible solutions I'm at a loss, so if anyone has any idea I'd be glad as BIAB is more or less useless for me without this functionality. Besides reinstalling BIAB and experimenting with the various options for MIDI in BIAB itself, I tried to import and re-export the files in various programs that can read MIDI. The MIDI files from BIAB are the only ones that generate this problem, GP6 usually takes any 3rd party MIDI without difficulties. Till here everything seems to work fine but when I try to re-open the just saved. I open Guitar Pro and import the MIDI file - the file opens fine and can be edited I hit F6 to open the export MIDI dialogue and save the file to disk as a type-1 MIDI with default options I type in some basic chords in BIAB and pick a style (no RealTracks or RealStyles etc. I've got a problem with the MIDI files generated by BIAB when importing and saving them in Guitar Pro 6.
0 Comments
Leave a Reply. |