-
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!
Since update 7.2, some macros no longer work properly for me.
- Thread starter Chris
- Start date
- Status
Welcome!
As Trucky said, we cannot confirm anything without knowing which macros you mean. I have more than 600 macros in my macros folder
Also, it makes a huge difference if you a) run macros from the arrangement or with the Note Editor focused, and b) if notes are selected.
I've just tried all the Music Editing macros I created (including Double -> Create Chords -> Major Triad / Minor Triad / Sus4 etc.) and they worked as expected.
As Trucky said, we cannot confirm anything without knowing which macros you mean. I have more than 600 macros in my macros folder
Also, it makes a huge difference if you a) run macros from the arrangement or with the Note Editor focused, and b) if notes are selected.I've just tried all the Music Editing macros I created (including Double -> Create Chords -> Major Triad / Minor Triad / Sus4 etc.) and they worked as expected.
Gary Shepherd
Member
Had some similar problems - my macros on Loop Selection/Toggle Off stopped working - these are ones tied to my Studio One logickeyboard which has set macros for named and coloured keys.
Thanks for the answers. I have already mentioned the macros for chord formation as an example (triads, sevenths etc.).
If I enter the root of a seventh chord in the editor and then run the macro, the chords are entered but the root note is deleted. Here is an example:
This was not the case before the update, and it affects the existing macros from S1 as well as my own and also a macro bar from the Exchange forum. If I rewrite the macros manually, they work, but some of the existing ones are now buggy (on my computer)!
If I enter the root of a seventh chord in the editor and then run the macro, the chords are entered but the root note is deleted. Here is an example:This was not the case before the update, and it affects the existing macros from S1 as well as my own and also a macro bar from the Exchange forum. If I rewrite the macros manually, they work, but some of the existing ones are now buggy (on my computer)!
Thanks for reply. If you mean the macro bar/page from the video: You can get it from the ExchangeForum (“Chord Builder”). But I can also export it from my DAW if you really need it.
[Deleted: superfluous stuff]
Last edited:
I downloaded and installed the Chord Builder macropage from Exchange.
Everything is working as expected for me using Studio One Pro 7.2 and Windows 11 (24H2).
I checked and found that Studio One 6 did not have the option for "No overlap" in the Editor.
This option was added to the Studio One 7 release.
The issue you're having is related to having the "No overlap" option enabled.
Disabling the "No overlap" option (as shown here) should fix the issue you're having.
Ok, if some of the macros on my system can no longer be interpreted correctly, then it seems that one of the S1 program files has been corrupted or the source code has been changed since the update.
It would still be interesting to know whether other users are also affected. At least this seems to be the case with user Gery Sheperd. And if the problem could be validated by other users, then a bug report to Presonus would probably also be an option.
Have you read Trucky's posts?
Nothing has changed in this regard in version 7.2, except that you enabled the "No Overlap" option. Since "Paste at Original Position" copies and inserts the note in the same position as the original note, the original note will obviously be overwritten (deleted) with this option enabled.
The "Double Notes" macros in Studio One are somewhat of a hacky workaround. I know because I created them. These macros only work when notes are selected, as they rely on the "Copy" command, which requires a selection. Unfortunately, the selection behavior after running the macros is also a bit clunky: Only the last inserted note remains selected. This is why I created native commands for this with Harmony Wizard. The "Double at Intervals" command in HW does not rely on any hacks. It can also select added notes, which is helpful for further editing, such as changing the velocity of the top notes. And you can create your own interval structures without editing macros.
[Post edited by Admin/Moderator - see Forum rules]
https://studiooneforum.com/help/terms
No, I deliberately didn't.
In any case, the problem is not yet solved for me and the “no-overlapping” option is definitely not the reason! The macros for chord formation were just one example. In the meantime, S1 is also showing strange behavior in other places. When I started the program this morning, it “installed” files like an update, without there even being a new update.
I will perform a clean install, then the spook should be over. So far, S1 has been very stable since version 6.
@Chrisch
Yes there is something odd going on. What I did to check
1. Add note in midi editor C3
2. Select macro "Major"
3. Delete the notes (then without placing another note)
4. Select the "Minor"
Result a two note chord with no root note.
1. Add note in midi editor C3
2. Select macro "Minor" with root note. OK
3. Delete the notes
4. Select the "Major"
Result a two note chord with no root note.
1. Add note in midi editor C3
2. Select macro "Minor" with root note. OK
3. Delete just the two higher notes, leaving the original root note in place
4. Select the "Major"
Result the chord is created as expected.
when no root note is selected it removes the root note. If a note is selected then the chord is created as expected.
What is the intended use case in this instance, should the chord builder remember that you placed and then deleted the root note, or just build another chord in place of the previously deleted chord,
or does the chord builder expect a note to build the chord off ?
Hope this helps in some way.
Regards
Edit: deleted incorrect assumption!
Yes there is something odd going on. What I did to check
1. Add note in midi editor C3
2. Select macro "Major"
3. Delete the notes (then without placing another note)
4. Select the "Minor"
Result a two note chord with no root note.
1. Add note in midi editor C3
2. Select macro "Minor" with root note. OK
3. Delete the notes
4. Select the "Major"
Result a two note chord with no root note.
1. Add note in midi editor C3
2. Select macro "Minor" with root note. OK
3. Delete just the two higher notes, leaving the original root note in place
4. Select the "Major"
Result the chord is created as expected.
when no root note is selected it removes the root note. If a note is selected then the chord is created as expected.
What is the intended use case in this instance, should the chord builder remember that you placed and then deleted the root note, or just build another chord in place of the previously deleted chord,
or does the chord builder expect a note to build the chord off ?
Hope this helps in some way.
Regards
Edit: deleted incorrect assumption!
Last edited:
@Chrisch Remember to follow our forum rules and netiquette. Personal attacks and dismissive remarks toward moderators or other users are not acceptable.
If you deliberately choose not to read explanations or suggested solutions, you cannot expect any help in this forum.
If you believe that's the case, please do A/B comparisons between version 7.1 and 7.2, and report specifically what behaves differently in 7.2. Considering the "No overlap" option which - again, as explained above - affects the result.
I can't see anything odd going on. It doesn't matter whether you added any new notes or not - I've explained above that...
Studio One isn't "recognizing" anything. These are just macros - they simply execute the commands they contain. Nothing less, nothing more.
@Lucas
My reference to something "odd" going on is in refrence to his #5 post and the YTube vid posted.
It works OK on my maschine, I'm trying to examine why, when the OP tries to input a note and select a chord the root note he places gets deleted?
I wonder if the OP gets the same result if he selects a different root note, will it delete the root note in that instance.
From where I'm sitting the issue resides on his maschine.
Anyway It's his post i'll butt out of here as I may be just confusing the matter...
My reference to something "odd" going on is in refrence to his #5 post and the YTube vid posted.
It works OK on my maschine, I'm trying to examine why, when the OP tries to input a note and select a chord the root note he places gets deleted?
I wonder if the OP gets the same result if he selects a different root note, will it delete the root note in that instance.
From where I'm sitting the issue resides on his maschine.
Anyway It's his post i'll butt out of here as I may be just confusing the matter...
Trucky explained it already: The video clearly shows that the "No Overlap" option was enabled. Nothing odd.
With regard to the no-overlap option, I find it questionable that Presonus is building in a function that sabotages the functionality of their own macros. That's why it's a bug and not a user error! And on my computer probably a corrupt update (for whatever reason). Incidentally, S1 has been running flawlessly again since the clean install.
Probably, the clean install resetted the "No Overlap" option which you had turned on before.
The cause of the issue and a working solution have been explained. It's by design that macros may or may not work depending in which context they're applied or which settings are enabled (in this case: the "No Overlap" option). However, I’ve submitted a request to adapt the affected stock macros to the new "No Overlap" option.
Last edited:
- Status