Jump to content

Recommended Posts

  • Members

Hello,

I am not sure how to translate my Roland's patch list into the format that Studio one is asking for. The Web help for Studio one says:

 

Quote

 

You can add the Bank and Program Change message in the "Inspector" per track. First enable the "Program" option listed in the "Inspector". Then enter numbers for the Bank and Program Change.

For the Bank you will have to enter the combined bank number. Some external devices select banks by combining the MSB (Most Significant Bit) and LSB (Least Significant Bit) into one single “MIDI Bank Select” message. They calculate the necessary MIDI Bank Select value using the equation (MSB x 128) + LSB. Some devices will give you this number in their patch listing.

Once you enter that number for the bank you then enter the program change number in the appropriate field in the "Inspector".

 

I have attached pictures of a small bit of the patch list and the fields Studio one asks for.  

 

Any help would be appreciated. 

Capture.PNG

Capture2.PNG

Link to post
Share on other sites
  • 2 weeks later...
  • Members

Cakewalk (now Sonar Cakewalk by BandLab or somthing....) used to have "instrument definition files" that would you could download from the internet and install them in Calkewalk, where your various hardware synths and their patches would be installed and integrated into the DAW's workflow.... I used to use Sonar and you could select instruments and patches from a drop down list in the MIDI tracks. I don't know if any other DAWs support instrument definition files, but I suspect not. Everything I read about them references Cakewalk, so they're the only one. 

It looks like you'll have to enter the data manually. 

 

Link to post
Share on other sites
  • 3 months later...
  • Members

Yeah it's a real hassle and something I hope will be addressed with midi 2.0. The cakewalk .ins files were great. Mac had a similar thing going on with midinam/mididev files, however that got lost in the switch away from 5 pin DIN connections to USB.

Link to post
Share on other sites
  • 7 months later...
  • Members

Yeah, Mr. Grumpy, you're right. The *.ins files were great once you set them up. I think Cubase had a related format that you could use *.ins templates and somehow translate them, but SO never had any such thing, In fact, my Alesis Fusion was never able to make a good translation in SO. I'm hoping the mfrs simply create a firmware that will make that update along with M'soft. I don't care about Macs. I also hope they FINALLY make adequate drum maps a universal feature as well, where they're not only translateable from 1 DAW to another, but where if you disconnect a device the map will still be there so you don't have to remember what the old map said. I haven't used it in such a long time I've forgotten all of the features I wanted addressed and Bandlab never addressed it either.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...