1.1.0 - CC starting value is not stored or loaded on document save/load
Closed this issue · 9 comments
ScreenPlane commented
In a CC the End Amount value (which is actually the starting value) of a slew is not stored (or not loaded). When loaded the value is always 0 and the values are gone.
Therefor the transition is always starting with 0 and going to the value of the Amount.
ScreenPlane commented
Most often the starting value for a transition (Slew) would be the current value. A check box with "use current value" would be a fast way for operating. If a starting value is typed in it could use this particular value.
ScreenPlane commented
This most critical issue I still have with using Midinous is that the end value (actually the start value) of a cc is not written into the file. After a crash on the beta, it means putting them all back in manually. If the store/load function would be included, I could at least restore it to where I was. Thanks.
Nornec commented
Fixed in upcoming release candidate.
ScreenPlane commented
Hi Jay,
thanks, this sounds great. Is the new beta already up and running? I have just checked and it’s still listed as 1.1.0.
Best,
Sebastian
… Am 14.04.2023 um 05:57 schrieb Jay ***@***.***>:
Fixed in upcoming release candidate.
—
Reply to this email directly, view it on GitHub <#33 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6O2GLCD2UJ25DPZCABFBM3XBDDKHANCNFSM6AAAAAAVZJHQCA>.
You are receiving this because you authored the thread.
Nornec commented
Not yet. There will likely be an update out before the end of the weekend.
Please check Discord for more info.
…On Fri, Apr 14, 2023, 15:33 ScreenPlane ***@***.***> wrote:
Hi Jay,
thanks, this sounds great. Is the new beta already up and running? I have
just checked and it’s still listed as 1.1.0.
Best,
Sebastian
> Am 14.04.2023 um 05:57 schrieb Jay ***@***.***>:
>
>
> Fixed in upcoming release candidate.
>
> —
> Reply to this email directly, view it on GitHub <
#33 (comment)>,
or unsubscribe <
https://github.com/notifications/unsubscribe-auth/A6O2GLCD2UJ25DPZCABFBM3XBDDKHANCNFSM6AAAAAAVZJHQCA
>.
> You are receiving this because you authored the thread.
>
—
Reply to this email directly, view it on GitHub
<#33 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFQ2UVUC4R5ZWEHWCNBQOATXBGRCBANCNFSM6AAAAAAVZJHQCA>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
ScreenPlane commented
Great, thanks for making it happen!
… Am 14.04.2023 um 22:31 schrieb Jay ***@***.***>:
Not yet. There will likely be an update out before the end of the weekend.
Please check Discord for more info.
On Fri, Apr 14, 2023, 15:33 ScreenPlane ***@***.***> wrote:
> Hi Jay,
> thanks, this sounds great. Is the new beta already up and running? I have
> just checked and it’s still listed as 1.1.0.
>
> Best,
> Sebastian
>
>
>
> > Am 14.04.2023 um 05:57 schrieb Jay ***@***.***>:
> >
> >
> > Fixed in upcoming release candidate.
> >
> > —
> > Reply to this email directly, view it on GitHub <
> #33 (comment)>,
> or unsubscribe <
> https://github.com/notifications/unsubscribe-auth/A6O2GLCD2UJ25DPZCABFBM3XBDDKHANCNFSM6AAAAAAVZJHQCA
> >.
> > You are receiving this because you authored the thread.
> >
>
> —
> Reply to this email directly, view it on GitHub
> <#33 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AFQ2UVUC4R5ZWEHWCNBQOATXBGRCBANCNFSM6AAAAAAVZJHQCA>
> .
> You are receiving this because you modified the open/close state.Message
> ID: ***@***.***>
>
—
Reply to this email directly, view it on GitHub <#33 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6O2GLDSIQGAQ4OYYFFZAXTXBGX25ANCNFSM6AAAAAAVZJHQCA>.
You are receiving this because you authored the thread.
ScreenPlane commented
Hi Jay,
storage of the CC starting values seems to work. Great!
Just a suggestion: under slew mode it’s still namend as „end amount“. Might be good to change it to „starting value“ or „starting amount“.
Cheers
… Am 14.04.2023 um 22:31 schrieb Jay ***@***.***>:
Not yet. There will likely be an update out before the end of the weekend.
Please check Discord for more info.
On Fri, Apr 14, 2023, 15:33 ScreenPlane ***@***.***> wrote:
> Hi Jay,
> thanks, this sounds great. Is the new beta already up and running? I have
> just checked and it’s still listed as 1.1.0.
>
> Best,
> Sebastian
>
>
>
> > Am 14.04.2023 um 05:57 schrieb Jay ***@***.***>:
> >
> >
> > Fixed in upcoming release candidate.
> >
> > —
> > Reply to this email directly, view it on GitHub <
> #33 (comment)>,
> or unsubscribe <
> https://github.com/notifications/unsubscribe-auth/A6O2GLCD2UJ25DPZCABFBM3XBDDKHANCNFSM6AAAAAAVZJHQCA
> >.
> > You are receiving this because you authored the thread.
> >
>
> —
> Reply to this email directly, view it on GitHub
> <#33 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AFQ2UVUC4R5ZWEHWCNBQOATXBGRCBANCNFSM6AAAAAAVZJHQCA>
> .
> You are receiving this because you modified the open/close state.Message
> ID: ***@***.***>
>
—
Reply to this email directly, view it on GitHub <#33 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6O2GLDSIQGAQ4OYYFFZAXTXBGX25ANCNFSM6AAAAAAVZJHQCA>.
You are receiving this because you authored the thread.
Nornec commented
End Amount behaves as an actual end amount. Please let me know otherwise.
…On Sun, Apr 16, 2023, 07:57 ScreenPlane ***@***.***> wrote:
Hi Jay,
storage of the CC starting values seems to work. Great!
Just a suggestion: under slew mode it’s still namend as „end amount“.
Might be good to change it to „starting value“ or „starting amount“.
Cheers
> Am 14.04.2023 um 22:31 schrieb Jay ***@***.***>:
>
>
> Not yet. There will likely be an update out before the end of the
weekend.
> Please check Discord for more info.
>
> On Fri, Apr 14, 2023, 15:33 ScreenPlane ***@***.***> wrote:
>
> > Hi Jay,
> > thanks, this sounds great. Is the new beta already up and running? I
have
> > just checked and it’s still listed as 1.1.0.
> >
> > Best,
> > Sebastian
> >
> >
> >
> > > Am 14.04.2023 um 05:57 schrieb Jay ***@***.***>:
> > >
> > >
> > > Fixed in upcoming release candidate.
> > >
> > > —
> > > Reply to this email directly, view it on GitHub <
> >
#33 (comment)
>,
> > or unsubscribe <
> >
https://github.com/notifications/unsubscribe-auth/A6O2GLCD2UJ25DPZCABFBM3XBDDKHANCNFSM6AAAAAAVZJHQCA
> > >.
> > > You are receiving this because you authored the thread.
> > >
> >
> > —
> > Reply to this email directly, view it on GitHub
> > <
#33 (comment)
>,
> > or unsubscribe
> > <
https://github.com/notifications/unsubscribe-auth/AFQ2UVUC4R5ZWEHWCNBQOATXBGRCBANCNFSM6AAAAAAVZJHQCA
>
> > .
> > You are receiving this because you modified the open/close
state.Message
> > ID: ***@***.***>
> >
> —
> Reply to this email directly, view it on GitHub <
#33 (comment)>,
or unsubscribe <
https://github.com/notifications/unsubscribe-auth/A6O2GLDSIQGAQ4OYYFFZAXTXBGX25ANCNFSM6AAAAAAVZJHQCA
>.
> You are receiving this because you authored the thread.
>
—
Reply to this email directly, view it on GitHub
<#33 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFQ2UVWEXLDJLPJP2WOFQZDXBPNA3ANCNFSM6AAAAAAVZJHQCA>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
ScreenPlane commented
I see, yes, this is right.
From the general feeling I would think amount is the value that should be reached, while slew is the transition to this value. Therefore having the starting value in slew, sounded right to me.
… Am 16.04.2023 um 14:39 schrieb Jay ***@***.***>:
End Amount behaves as an actual end amount. Please let me know otherwise.
On Sun, Apr 16, 2023, 07:57 ScreenPlane ***@***.***> wrote:
> Hi Jay,
> storage of the CC starting values seems to work. Great!
>
> Just a suggestion: under slew mode it’s still namend as „end amount“.
> Might be good to change it to „starting value“ or „starting amount“.
>
> Cheers
>
>
>
> > Am 14.04.2023 um 22:31 schrieb Jay ***@***.***>:
> >
> >
> > Not yet. There will likely be an update out before the end of the
> weekend.
> > Please check Discord for more info.
> >
> > On Fri, Apr 14, 2023, 15:33 ScreenPlane ***@***.***> wrote:
> >
> > > Hi Jay,
> > > thanks, this sounds great. Is the new beta already up and running? I
> have
> > > just checked and it’s still listed as 1.1.0.
> > >
> > > Best,
> > > Sebastian
> > >
> > >
> > >
> > > > Am 14.04.2023 um 05:57 schrieb Jay ***@***.***>:
> > > >
> > > >
> > > > Fixed in upcoming release candidate.
> > > >
> > > > —
> > > > Reply to this email directly, view it on GitHub <
> > >
> #33 (comment)
> >,
> > > or unsubscribe <
> > >
> https://github.com/notifications/unsubscribe-auth/A6O2GLCD2UJ25DPZCABFBM3XBDDKHANCNFSM6AAAAAAVZJHQCA
> > > >.
> > > > You are receiving this because you authored the thread.
> > > >
> > >
> > > —
> > > Reply to this email directly, view it on GitHub
> > > <
> #33 (comment)
> >,
> > > or unsubscribe
> > > <
> https://github.com/notifications/unsubscribe-auth/AFQ2UVUC4R5ZWEHWCNBQOATXBGRCBANCNFSM6AAAAAAVZJHQCA
> >
> > > .
> > > You are receiving this because you modified the open/close
> state.Message
> > > ID: ***@***.***>
> > >
> > —
> > Reply to this email directly, view it on GitHub <
> #33 (comment)>,
> or unsubscribe <
> https://github.com/notifications/unsubscribe-auth/A6O2GLDSIQGAQ4OYYFFZAXTXBGX25ANCNFSM6AAAAAAVZJHQCA
> >.
> > You are receiving this because you authored the thread.
> >
>
> —
> Reply to this email directly, view it on GitHub
> <#33 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AFQ2UVWEXLDJLPJP2WOFQZDXBPNA3ANCNFSM6AAAAAAVZJHQCA>
> .
> You are receiving this because you modified the open/close state.Message
> ID: ***@***.***>
>
—
Reply to this email directly, view it on GitHub <#33 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6O2GLDW2WHFSC3WAFGSMODXBPR73ANCNFSM6AAAAAAVZJHQCA>.
You are receiving this because you authored the thread.