It sort of worked, the P1-Nano.I opened a project with 20 tracks and it appeared to work fine. I then opened a folder with 16 tracks so i had 36 channels displaying. It would not recognize the first 16 channels. From 17 to 36 it worked fine. I have sold the Nano but if you get the plugin params past the 8 only limit, I may look at the P1-M/-X a second time. Great stuff you are doing here!!
@@robertjensen2774 Thanks for the feedback. Sounds like it will take quite a bit of work to get the Nano working. I'm hoping to release the plugin control update with a video by the end of the month. You can see if it meets your requirements.
It's going to take a bit longer unfortunately, but it's progressing well. It looks like I'll be able to do 192 plugin params (8 pages of 24 controls - 8 rotaries, 8 faders, 8 push buttons).
Great job on writing the script! especially on the multiple lines of text on the display. Would have loved to be able to use this but im unfortunately a fl studio user
Thanks. It's a pity every DAW is so different when it comes to controllers. There really needs to be a better standard than the out-dated Mackie control.
I think you and I will become VERY good friends lol. I’m hoping to get these working with Studio One and RANDOMLY found your video looking for any recent uploads on them to see if Icon has been working on fixing the bugs. So, your scripts basically make all this happen?? Also and maybe more importantly unless I haven’t gotten there yet, is there a way to navigate by either spilling VCA’s or folders?
My script is used instead of the Mackie Control script that comes with Studio One. The Mackie scripts come with many limitations, partly because of the nature of the Mackie protocol (e.g. there's no way to pass down track colours) and partly just how Presonus have written them (e.g. timecode being unreadable). So my script was designed from scratch to make much better use of these controllers. Currently my script does not allow VCA or folder spilling. It's on the list of things to look at, but I don't know if it's possible yet. I'm currently working on adding plugin control for the next release.
can you do something similar for the UF1? Primarily DAW follows controller and Controller follows DAW along with expanding the number of params for plugins to greater than 8. Faderport allows for 10 pages of 8 i believe. Thanks
I've not considered the Nano. The scripts are designed for the 8 channel display, so I'm not sure how usable it would be with only one. I don't think the 'focused' scenes would work very well. The unfocused scenes might be okay. You could try it and see if it's usable at all. Using the P1-M script would be best as its master section looks to be the same as the Nano. I'd be interested in any feedback you can give. I'm working on adding Plugin control at the moment, but after that I could look at how feasible it would be to make modifications for the Nano.
I don't know much about Pro Tools so I can't really say. I did have a quick look at the documentation for the Pro Tools scripting SDK a while back. It seemed to be designed for workflow automation rather than real-time midi data I/O, so it might not be possible. You'd have to ask a Pro Tools expert really. It's a pity there isn't a better standard across all DAWs for driving these kinds of controllers. Every DAW is unique in how it handles them and if/how they allow users to write custom scripts.
I'm not looking to take on any more projects at the moment. I'm not sure it's even possible with Pro Tools. Their SDK looks like it's designed for workflow automation rather than real-time data i/o.
Is there any chance to implement a function that present the inserts in a channel in a focus view so you can press the pan button to show the plugin window?
Yes it's probably possible as I think the Faderport 8/16 can do that. I'll look into it. It'll probably another scene that works like the sends and cues.
I'm working on this now. I have the plugin opening working here. I'm also adding the ability to control the plugin parameters using the rotaries and faders.
i replaced it with a UF1 / UC1 combo but have not sold it yet I have some time next week and will give it a try...
You made my P1-M so much more useful. Thank you so much. Icon should pay you for the job.
Thanks, that's good to hear. I'm glad others are finding it useful.
It sort of worked, the P1-Nano.I opened a project with 20 tracks and it appeared to work fine. I then opened a folder with 16 tracks so i had 36 channels displaying. It would not recognize the first 16 channels. From 17 to 36 it worked fine. I have sold the Nano but if you get the plugin params past the 8 only limit, I may look at the P1-M/-X a second time. Great stuff you are doing here!!
@@robertjensen2774 Thanks for the feedback. Sounds like it will take quite a bit of work to get the Nano working. I'm hoping to release the plugin control update with a video by the end of the month. You can see if it meets your requirements.
It's going to take a bit longer unfortunately, but it's progressing well. It looks like I'll be able to do 192 plugin params (8 pages of 24 controls - 8 rotaries, 8 faders, 8 push buttons).
Great job on writing the script!
especially on the multiple lines of text on the display.
Would have loved to be able to use this but im unfortunately a fl studio user
Thanks. It's a pity every DAW is so different when it comes to controllers. There really needs to be a better standard than the out-dated Mackie control.
I think you and I will become VERY good friends lol. I’m hoping to get these working with Studio One and RANDOMLY found your video looking for any recent uploads on them to see if Icon has been working on fixing the bugs. So, your scripts basically make all this happen?? Also and maybe more importantly unless I haven’t gotten there yet, is there a way to navigate by either spilling VCA’s or folders?
My script is used instead of the Mackie Control script that comes with Studio One. The Mackie scripts come with many limitations, partly because of the nature of the Mackie protocol (e.g. there's no way to pass down track colours) and partly just how Presonus have written them (e.g. timecode being unreadable). So my script was designed from scratch to make much better use of these controllers.
Currently my script does not allow VCA or folder spilling. It's on the list of things to look at, but I don't know if it's possible yet.
I'm currently working on adding plugin control for the next release.
can you do something similar for the UF1? Primarily DAW follows controller and Controller follows DAW along with expanding the number of params for plugins to greater than 8. Faderport allows for 10 pages of 8 i believe. Thanks
Unfortunately not; I don't own a UF1 so I've no idea how it works.
Do you think this will work with a P1-Nano??? Should I try it?
I've not considered the Nano. The scripts are designed for the 8 channel display, so I'm not sure how usable it would be with only one. I don't think the 'focused' scenes would work very well. The unfocused scenes might be okay. You could try it and see if it's usable at all. Using the P1-M script would be best as its master section looks to be the same as the Nano. I'd be interested in any feedback you can give. I'm working on adding Plugin control at the moment, but after that I could look at how feasible it would be to make modifications for the Nano.
Is it possible to make one of these for pro tools?
I don't know much about Pro Tools so I can't really say. I did have a quick look at the documentation for the Pro Tools scripting SDK a while back. It seemed to be designed for workflow automation rather than real-time midi data I/O, so it might not be possible. You'd have to ask a Pro Tools expert really.
It's a pity there isn't a better standard across all DAWs for driving these kinds of controllers. Every DAW is unique in how it handles them and if/how they allow users to write custom scripts.
Can I pay you for a custom script for ProTools?
I'm not looking to take on any more projects at the moment. I'm not sure it's even possible with Pro Tools. Their SDK looks like it's designed for workflow automation rather than real-time data i/o.
Is there any chance to implement a function that present the inserts in a channel in a focus view so you can press the pan button to show the plugin window?
Yes it's probably possible as I think the Faderport 8/16 can do that. I'll look into it. It'll probably another scene that works like the sends and cues.
I'm working on this now. I have the plugin opening working here. I'm also adding the ability to control the plugin parameters using the rotaries and faders.