• Hi and welcome to the Studio One User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!

Studio Pro 8 didn't port this...

Slacknote

New member
For some reason I had to reinstall Harmony Wizard and Navigation Essentials which was a bit of a faff mainly because it Lukas Ruschitzka makes it a bit difficult to locate his otherwise excellent tools.
Then there was Gregor Beyerle's macro called "Track Folder Bus" that disappeared on me. For some reason I couldn't find it on the Exchange server, where I got it from either, neither could I find the video that must've explained it. I ended up copying the Track Folder Bus.studioonemacro file across.
 
For some reason I had to reinstall Harmony Wizard and Navigation Essentials
And all other 3rd party scripts, like the Color Toolbar script (Color Toolbar script). Why? Because installs rewrite the Scripts folder with just the default scripts. You need to readd 3rd party scripts .package file each time. Harmony Wizard, Nav Essentials and Scoring Tools install via .install files. I haven't found which folder they install into yet, so I can't check if they are removed during update installs.
 
Last edited:
And all other 3rd party scripts, like his Color Toolbar script. Why? Because installs rewrite the Scripts folder with just the default scripts. You need to readd 3rd party scripts .package file each time. Harmony Wizard, Nav Essentials and Scoring Tools install via .install files. I haven't found which folder they install into yet, so I can't check if they are removed during update installs.
Right, was this normal in the S1 days too? Can't remember, not complaining just mentioning it since anyone else struggles with it.
 
Right, was this normal in the S1 days too? Can't remember, not complaining just mentioning it since anyone else struggles with it.
Yup. Since forever. I added a link to the free Color Toolbar script after you quoted my reply.
 
It would be so much easier if Presonus coded these scripts into the software, they are great additional features that bring lots of benefits
 
It would be so much easier if Presonus coded these scripts into the software, they are great additional features that bring lots of benefits

Except it would not benefit (or fund) those skilled third party pros like Lukas who coded them in the first place.

VP
 
You had to reinstall the Color Toolbar every update of Presonus Studio One. So this is nothing to do with Fender. Although why it is not included in Studio Pro is beyond me......
 
Whilst that is true it shows a lack of functionality from the main program that is needed

"Needed" is a very subjective word.

Just because Lukas goes deep and brings some awesome new functionality to the tables - in no way does that equal "needed".

Maybe you think it's needed - but that does not mean I do.

Lukas could have also create a dud that no one wanted at all - should that be included automatically as well?

VP
 
Lukas could have also create a dud that no one wanted at all - should that be included automatically as well?
…and there are some exotic and nerdy features in my scripts that PreSonus would never have added in that way (or at all) to the program. It’s actually the reason why the dev team and I started this collaboration in the first place to allow me to create scripting extensions.

For some reason I had to reinstall Harmony Wizard and Navigation Essentials...
It’s not supposed to be like that. I’ve tested this extensively, and many users have confirmed that Harmony Wizard and the other extensions continue working in FSP 8 without any reinstallation or reactivation. However, it seems that the FSP 8 migration of settings from previous versions (macros, user settings, presets, correct user data location) fails in certain situations. Did you perhaps have your previous (or the new) version installed on a different drive or partition?

...which was a bit of a faff mainly because it Lukas Ruschitzka makes it a bit difficult to locate his otherwise excellent tools.
Thank you! Could you elaborate on why you feel they are difficult to locate? All my paid script extensions are provided via a download link in the purchase email or via direct download immediately after purchase. By checking that email, you can re-download them at any time, without any time limitation. Also, if this is mainly about downloading, you can always get the latest version from the manual page:


Some for Scoring Tools or Navigation Essentials:

 
"Needed" is a very subjective word.

Just because Lukas goes deep and brings some awesome new functionality to the tables - in no way does that equal "needed".

Maybe you think it's needed - but that does not mean I do.

Lukas could have also create a dud that no one wanted at all - should that be included automatically as well?

VP
But the difference is that Lukas identified a deficit in the program and was in the position to benefit Studio One through his contacts with the developers. Ideally including his great ideas as part of the program would benefit those who do a lot of score writing. For me I don't need these features but it is evident that plenty of others do.
 
Ideally including his great ideas as part of the program would benefit those who do a lot of score writing. For me I don't need these features but it is evident that plenty of others do.

Well - I don't need them either.

I also do not want to be forced to pay for them either if they were "included" in some future version of SP. (Do not make any assumptions that this good stuff would be free)

Or maybe higher up - the actual Presonus/Fender development team - doesn't want any of this stuff messing with (or included in) their master DEV environments.

Finally - it goes without saying that Lukas probably likes getting paid as well. :)

Leaving these items as separate paid "addons" benefits everyone - each for their own situation.

VP
 
Ideally including his great ideas as part of the program would benefit those who do a lot of score writing.
Let me put it this way: If you want the features I developed to keep evolving instead of being abandoned, then leave them to me.

Leaving these items as separate paid "addons" benefits everyone - each for their own situation.
+100
 
Well - I don't need them either.

I also do not want to be forced to pay for them either if they were "included" in some future version of SP. (Do not make any assumptions that this good stuff would be free)

Or maybe higher up - the actual Presonus/Fender development team - doesn't want any of this stuff messing with (or included in) their master DEV environments.

Finally - it goes without saying that Lukas probably likes getting paid as well. :)

Leaving these items as separate paid "addons" benefits everyone - each for their own situation.

VP
I get that. But at the same time when a new version of the software rolls around I can guarantee that I may only have an interest in a minority of the new feature set. It's not realistic to think that a new release will cater 100% to what I want. It would be an amazing coincidence if ever that happened. Instead we have to weigh up whether the minority of new features is sufficient to justify the investment.
Regarding implementing Lukas's work into the software. He's got the relationship with the developers, the code is right there, and he can support them with it unlike the colour toolbar written by a user with no contact to the team. In that aspect I'd expect that if the team wanted to implement the colour toolbar they've have to reverse engineer it.
 
But at the same time when a new version of the software rolls around I can guarantee that I may only have an interest in a minority of the new feature set. It's not realistic to think that a new release will cater 100% to what I want. It would be an amazing coincidence if ever that happened. Instead we have to weigh up whether the minority of new features is sufficient to justify the investment.

Now you are talking about something else here completely. None of us ever gets what we want from every release. But I do not understand how getting even more of what I don't want (if an one or more addons do not appeal to me) - is better

Regarding implementing Lukas's work into the software. He's got the relationship with the developers, the code is right there, and he can support them with it unlike the colour toolbar written by a user with no contact to the team. In that aspect I'd expect that if the team wanted to implement the colour toolbar they've have to reverse engineer it.

Well - I think Lukas summed it all up in his post. This is his thing and it is prudent to leave it to him to manage - in whatever way he sees fit.

There are more than likely a number of other key deterrents in why none of these addons will ever be included starting with the giant difference in Lukas building cool addons on the side and Fender (the corporation) and how they structure their IT and commercial development. To me these are two vastly different worlds.

I say be thankful these addons exist at all , remain affordable and the added bonus of the guy that makes them hangs out in here with us.

VP
 
Now you are talking about something else here completely. None of us ever gets what we want from every release. But I do not understand how getting even more of what I don't want (if an one or more addons do not appeal to me) - is better



Well - I think Lukas summed it all up in his post. This is his thing and it is prudent to leave it to him to manage - in whatever way he sees fit.

There are more than likely a number of other key deterrents in why none of these addons will ever be included starting with the giant difference in Lukas building cool addons on the side and Fender (the corporation) and how they structure their IT and commercial development. To me these are two vastly different worlds.

I say be thankful these addons exist at all , remain affordable and the added bonus of the guy that makes them hangs out in here with us.

VP
That would be a real shame if Fender cannot recognise the benefits these extensions would bring. Lukas has identified the shortcomings of the existing feature set and thought "if only" and decided to enhance existing features taking them to where they should have been in the first place. Look at his navigation essentials for example. These aren't esoteric features that are so niche as to only appeal to a tiny amount of users, they bring workflow enhancements that every user can benefit from. If the Fender development team were to implement these extensions it would expose the functionality to a wider Studio Pro audience rather than just those who frequent this forum. With Fenders promotional reach way more users could benefit from these great tools that Lukas has developed. I've nothing against Lukas getting paid for his efforts, let Fender buy his work, he's already put the time in.
 
That would be a real shame if Fender cannot recognise the benefits these extensions would bring. Lukas has identified the shortcomings of the existing feature set and thought "if only" and decided to enhance existing features taking them to where they should have been in the first place. Look at his navigation essentials for example. These aren't esoteric features that are so niche as to only appeal to a tiny amount of users, they bring workflow enhancements that every user can benefit from. If the Fender development team were to implement these extensions it would expose the functionality to a wider Studio Pro audience rather than just those who frequent this forum. With Fenders promotional reach way more users could benefit from these great tools that Lukas has developed. I've nothing against Lukas getting paid for his efforts, let Fender buy his work, he's already put the time in.

Not disagreeing with you. But again - you and I have no idea what goes on behind the scenes or how any of this works.

For me - I am glad to support Lukas - I have a couple of his addons and that is good enough for me.

VP
 
Back
Top