• SONAR
  • Do we OWN our project files? (p.9)
2018/01/22 02:12:38
Sir Les
If the principle is not withheld by all parties...the eula is also not withstanding of any licence agreement ..as it is nul and voided by..owner....Not user...User has no EULA for it is broken by owner...even if they own the codex...the agreements agreed to are no longer withstanding by their own doing it to be dead...the also if you have the codex, you can nibble the code with not withstanding under any agreement, if the primary holders no longer suit the interested licence terms of agreement...it is broken Eula...to use under those terms...so go and nibble, hack and fix to enhance the user base of honouring what they did not honour!...what court would not see this..if you use those terms they put, yet still needs fixing...they may own the old code...but the new code is now in grey area to any one who wants to fix it..if found broken or error in any of that code!..one must read it to know...nothing wrong in reading it...and fixing to enhance any error.
 
2018/01/22 03:16:10
Sir Les
See it liken this...if some did pay for life time updates...and agreement was met by these paid parties...it does not matter who updates the licence or the code...as long as it is for life done as agreed....By those parties agreeing!...if they walk away from that agreement ...They break it...But if you fix it the code, you honour the part agreed to...then no law can sue, no party on its own can take that ..if they broke the agreement of, and  broke up due to capital, which is not a living entity or reason to disband the company and entities whom were in that agreement of with.....User has rights to agreements honoured by any of the paid and signed to that agreement was was offered as..is honoured by...Entities of the living and bound by law...Parties of...and in there in...You have rights to updates....for life!
 
2018/01/22 07:42:17
jamesg1213
Well, all that makes sense.
 

2018/01/22 08:04:51
ampfixer
I think it's written in French and the translated.
2018/01/22 13:39:06
subtlearts
ptheisen
By the way, are you still planning to port AZController to Reaper? I'm hoping you are, because even with an existing dedicated third-party app for the Alphatrack in Reaper, there are a few things that need fixing, and I'll bet AZController could do it!

 
Yes, the AlphaTrack preset for the AZ Controller is great, and of course you can do pretty much whatever you want with the plugin, so I'm happy to know it will make its way to Reaper at some point. But I'm glad you drew my attention to the existing AlphaTrack Pro plugin for Reaper, as it's also great, quite deep and configurable - a bit different so takes some getting used to, but for the moment, I'm glad to have more functionality out of the AT than what Reaper provides natively. Thanks for the tip!
2018/01/22 13:50:28
Brando
ampfixer
I think it's written in French and the translated.


I think it's written under the influence, and not translated
2018/01/22 18:08:58
azslow3
subtlearts
ptheisen
By the way, are you still planning to port AZController to Reaper? I'm hoping you are, because even with an existing dedicated third-party app for the Alphatrack in Reaper, there are a few things that need fixing, and I'll bet AZController could do it!

Yes, the AlphaTrack preset for the AZ Controller is great, and of course you can do pretty much whatever you want with the plugin, so I'm happy to know it will make its way to Reaper at some point. But I'm glad you drew my attention to the existing AlphaTrack Pro plugin for Reaper, as it's also great, quite deep and configurable - a bit different so takes some getting used to, but for the moment, I'm glad to have more functionality out of the AT than what Reaper provides natively. Thanks for the tip!

Reaper community has many active developers and API is always up to date (Reaper can "generate" corresponding source file). So there are several projects ongoing, some are surfaces oriented. Unlike with Sonar, there is some "competition" for me
 
Brando
ampfixer
I think it's written in French and the translated.

I think it's written under the influence, and not translated

I do not think that is the first time you see his posts. There are most of the time cryptic, but have sense.
I guess this bunch of posts has the following meaning:
"If Gibson/CW think it is ok to sell Lifetime Updates and abandon the development in less then a year, just using the fact they have (almost...) never promised particular nor minimal length of the "lifetime", following the same logic, since in EULA nothing is explicitly written about any output files, it should be ok to parse them." In other words, parsing CWP is not more "gray" then what CW has done with users.
 
And I see that point as: an attempt to attack (foreign) legal customer of "lifetime updates" for questionable violations of not explicitly written rules concerning output files from abruptly abandoned project sounds rather risky idea.
 
Ok, point taken. Thanks
 
For the progress.
Routing in CWP is saved in Sir Les style 
Normal audio routing is clarified (including sends), I still have to look at SynthRack (Audio input, Synth audio and MIDI in general is not in audio patch-bay). I plan to skip DM, freeze and MIDI track settings till after the first prototype, but I have decided that general routing is good to have from the beginning.
 
2018/01/22 21:43:38
subtlearts
azslow3
Brando
ampfixer
I think it's written in French and the translated.

I think it's written under the influence, and not translated

I do not think that is the first time you see his posts. There are most of the time cryptic, but have sense.
I guess this bunch of posts has the following meaning:
"If Gibson/CW think it is ok to sell Lifetime Updates and abandon the development in less then a year, just using the fact they have (almost...) never promised particular nor minimal length of the "lifetime", following the same logic, since in EULA nothing is explicitly written about any output files, it should be ok to parse them." In other words, parsing CWP is not more "gray" then what CW has done with users.

 
Alexey, you're a more patient man than I am (though to be honest that's not really saying much) but I suspect you have it about right. I sometimes have a hard time ploughing through "cryptic" posts - whether they are deliberately obfuscated or merely the product of (how to say this?) a freely wandering poetic mind. A long time ago I had a friend who was a technical writer, and she told me her method of assessing clarity in writing was something along the lines of, "Do you want me to understand what you are saying? If so, make it clear and precise; if not, f%$k off and stop wasting my time!"... This always struck me as good advice, though it hasn't kept me from making some rambling posts of my own from time to time...
 

Normal audio routing is clarified (including sends), I still have to look at SynthRack (Audio input, Synth audio and MIDI in general is not in audio patch-bay). I plan to skip DM, freeze and MIDI track settings till after the first prototype, but I have decided that general routing is good to have from the beginning.



Again, you're a patient man!... By the way I'd be very happy to do some testing for you whenever you get to an alpha stage, and I'll even try to give you, ermm, clear and precise feedback!
2018/01/22 21:45:35
ptheisen
subtlearts
 
But I'm glad you drew my attention to the existing AlphaTrack Pro plugin for Reaper, as it's also great, quite deep and configurable - a bit different so takes some getting used to, but for the moment, I'm glad to have more functionality out of the AT than what Reaper provides natively. Thanks for the tip!



If I'm the one that got you connected with AlphaTrack Pro, even though I didn't name it specifically, then I'm glad I could help.
 
The one definite weakness that I experience with AlphaTrack Pro is related to the plug-in tab. Though plug-in parameters are well mapped to the rotary encoders, and parameters that use continuous data work well, the vast majority of parameters that are buttons or selectors, meaning they have just two or maybe several discrete states, do not work, turning or pushing the encoder has no effect on the parameter. Do you also see this?
2018/01/22 22:08:27
subtlearts
Yes, your post indirectly alerted me to it. And yes, I've noticed it doesn't seem to handle discretized controls very well. Alexey's plugin does that and pretty much everything else, so hopefully it makes the transition at some point! In the meantime, the AT Pro plugin is pretty good. 
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account