Hi Steve.
About the object thing, when you say the information is not super
important, I don't think I could do without it now. It is so comfortable
to get the name of the object you just selected. I think it is now time
for Magix To keep their promises, and I know you did all you could…
About the tracks being reported as tempo tracks, it happens randomly,
and at least I have a workaround to restore things to normal, which is
opening and closing the effect browser, it seems to always work.
If anything new I let you know. Do you know if the VST 3 quirk has been
solved?
Cheers,
JPR
http://www.jprykiel.com
https://www.youtube.com/c/jprykiel
http://soundcloud.com/ryksounet
https://www.youtube.com/c/jprykielhttp://facebook.com/jeanphilipperykiel
Le 11/03/2021 à 21:35, Steve Spamer a écrit :
Regarding the object thing. As I've said many times before, the > VIP/Arranger window is extremely complex, due to how tracks are >displayed and zoomed. The scripts have to rely on some aspects of the > UI that fit into that complexity, hence making them less reliable > then I would like. I've gone over different ways of tackling some of > the core issues lots of times, but the bottom line is, it's very > difficult to get a 100% success rate all the time. However, I am > always thinking of improving things., but Magix really have to step > up to the plate to address some of these issues. > > JP, regarding the tempo being reported. Can you reproduce this all > the time? When a tempo track is reported, it's usually down to 1 of 2 > things. One being another window obscuring part of the screen and the > other being a zoom issue. > > What exactly do you do with volume and effects to make this happen? A > solution to both of these problems is to possibly do away with some > specific feedback we get, as things break down in both scenarios due > to the scripts trying to obtain information the user may want to > know. > > For example, it's not super imperative that a user is told the track > they're on is a tempo track IMO, and it wouldn't be the end of the > world if you weren't informed of whether or not an object is present > on the track, as the OE just wouldn't open. It's a matter of trying > to give info people need to make the experience easier, but this kind > of info isn't given in all the currently accessible DAW's I don't > think. > > If you have the steps to repro the tempo issue JP, let me know and > I'll look into it. Otherwise, I'll put my thinking cap on with both > of these issues. > > Also, if users want this feedback to be taken away, I'm up for > considering it. Best Steve. -----Original Message----- From: > vipaudioaccess-bounce@xxxxxxxxxxxxx > <vipaudioaccess-bounce@xxxxxxxxxxxxx> On Behalf Of Jean-philippe > Rykiel Sent: 11 March 2021 18:15 To: vipaudioaccess@xxxxxxxxxxxxx > Subject: [vipaudioaccess] Re: Slightly odd behaviour > > Hi Steve and all. > > I get this occasionally too. I seem to remember it is not related to > a specific project, and restarting Samplitude often cures it. If it > shows back, I'll give it some more attention. > > The other thing I'm getting, and maybe it's worth starting a new > subject about this one, is tracks showing as tempo tracks when I want > to change their volume or add an effect. > > The cure I found for this one is to press the letter B to open the > effect browser and close it with escape. > > Cheers, > > JPR > > > > http://www.jprykiel.com https://www.youtube.com/c/jprykiel > http://soundcloud.com/ryksounet > https://www.youtube.com/c/jprykielhttp://facebook.com/jeanphilipperykiel > > > Le 11/03/2021 à 18:53, Steve Spamer a écrit :
object, the script is taking information from the >> values that Samplitude populates, like object length etc. So, if >> these values get populated when pressing a keystroke to select an >> object, then the script knows there's an object, if it doesn't get >> it, it presumes there isn't. >> >> Now, if this wasn't working, it would fail every time, and that's >> the difficult part. Maybe it's just a timing issue, I guess it is, >> but I'll take a look at this specific code and see if it can be >> improved. Needless to say, if you get a project that shows this >> behaviour consistently, then let me know. >> >> Timing could always be increased, but I'd be hesitant to do that, >> as it has a real impact on useability. The only other thing to do >> is to not have that feedback. Anyway, leave it with me and if I can >> do something I will. Best Steve. -----Original Message----- From: >> vipaudioaccess-bounce@xxxxxxxxxxxxx >> <vipaudioaccess-bounce@xxxxxxxxxxxxx> On Behalf Of >> il@xxxxxxxxxxxxx Sent: 11 March 2021 11:39 To: >> vipaudioaccess@xxxxxxxxxxxxx Subject: [vipaudioaccess] Slightly odd >> behaviour >> >> Win 10 64bit, JAWS 2021, SA 9.1 >> >> Hi Steve >> >> I've been getting some slightly odd behaviour when selecting >> objects. JAWS keeps reporting object can't be found or no object >> selected, however, an object is selected as I'm able to open the >> object manager. And at other times I can't select an object at all, >> JAWS keeps reporting object not visible. This is intermittent >> behaviour and difficult to reproduce at will. I've not updated yet >> as you suggested a while ago not too. But, I'm wondering if >> updating may help. Any advice welcome. >> >> Best >> >> Ian >> >> -- - To post to the mailing list, simply send email to >> vipaudioaccess@xxxxxxxxxxxxx. >> >> - To subscribe to the list, send an email to >> vipaudioaccess-request@xxxxxxxxxxxxx with 'subscribe' in the >> Subject field. >> >> - To unsubscribe from the list, send an email to >> vipaudioaccess-request@xxxxxxxxxxxxx with 'unsubscribe' in the >> Subject field. >> >> - For more list options, like setting digest and vacation modes, >> visit //www.freelists.org/list/vipaudioaccess >> >> - Online, searchable archives of the list are available at >> //www.freelists.org/archive/vipaudioaccess >> >> -- - To post to the mailing list, simply send email to >> vipaudioaccess@xxxxxxxxxxxxx. >> >> - To subscribe to the list, send an email to >> vipaudioaccess-request@xxxxxxxxxxxxx with 'subscribe' in the >> Subject field. >> >> - To unsubscribe from the list, send an email to >> vipaudioaccess-request@xxxxxxxxxxxxx with 'unsubscribe' in the >> Subject field. >> >> - For more list options, like setting digest and vacation modes, >> visit //www.freelists.org/list/vipaudioaccess >> >> - Online, searchable archives of the list are available at >> //www.freelists.org/archive/vipaudioaccess > -- - To post to the mailing list, simply send email to > vipaudioaccess@xxxxxxxxxxxxx. > > - To subscribe to the list, send an email to > vipaudioaccess-request@xxxxxxxxxxxxx with 'subscribe' in the Subject > field. > > - To unsubscribe from the list, send an email to > vipaudioaccess-request@xxxxxxxxxxxxx with 'unsubscribe' in the > Subject field. > > - For more list options, like setting digest and vacation modes, > visit //www.freelists.org/list/vipaudioaccess > > - Online, searchable archives of the list are available at > //www.freelists.org/archive/vipaudioaccess > > -- - To post to the mailing list, simply send email to > vipaudioaccess@xxxxxxxxxxxxx. > > - To subscribe to the list, send an email to > vipaudioaccess-request@xxxxxxxxxxxxx with 'subscribe' in the Subject > field. > > - To unsubscribe from the list, send an email to > vipaudioaccess-request@xxxxxxxxxxxxx with 'unsubscribe' in the > Subject field. > > - For more list options, like setting digest and vacation modes, > visit //www.freelists.org/list/vipaudioaccess > > - Online, searchable archives of the list are available at > //www.freelists.org/archive/Hi Ian. I have seen this occasionally as well, but it's a tricky >> one to reproduce, hence difficult to solve. >> >> When we select an
Philips Sonicare HX6871/47
