Hi Ian. Thanks.
You said:
However, if I moved the Zoom ratio to 10secs or lower, then the small object
would be selected but not reported properly by JAWS.
When you say it's not reported correctly, what exactly do you mean? Jaws will
only announce what is visible. So, if you have an object called "this is a
test", then when it's compressed, Jaws might only say "this I". This is because
the zoom ratio is so compressed that the full object name isn't visible.
Anyway, I have so far been unable to repro this. I created 4 objects, 2 which
were 17MS and 30MS, but jaws still picked them up. I was however able to get
jaws to report there where no more objects, after changing the zoom ratio to 10
and 1 mins, but this isn't surprising, due to the objects being
hidden/compressed. I have changed 1 line in the function that determines if an
object is selected or not. I changed the existing pause into a delay of 1 to
see if this improves things, as I have a suspicion that pause doesn't work well
in some circumstances with some users for some reason.
This doesn't mean everything should always work, as we're dealing with a lot of
different Pc's, but that function now tries to find the object, if it fails, it
then waits for 5 MS to see if the area where it's looking gets populated.
Hopefully that might help, but I'll still take you up on the tandam, just let
me know a good time for you.
Best Steve.
-----Original Message-----
From: vipaudioaccess-bounce@xxxxxxxxxxxxx <vipaudioaccess-bounce@xxxxxxxxxxxxx>
On Behalf Of il@xxxxxxxxxxxxx
Sent: 18 March 2021 11:53
To: vipaudioaccess@xxxxxxxxxxxxx
Subject: [vipaudioaccess] Re: Audio quantise
Hi Steve
Sure, if you'd like to Tandem in that's fine. However, I did a little trying
out this morning as follows:
I split an object of about 30secs long into 4, 2 of the objects were about 80ms
each a little way in.
Using Z, the first object was picked up, then using Alt + right-arrow, the
first of the small objects was picked up and reported correctly.
However, if I moved the Zoom ratio to 10secs or lower, then the small object
would be selected but not reported properly by JAWS.
I hope this makes sense.
I can't connect today as I'm waiting on some audio to finish a job. Anytime
tomorrow should be fine though.
Best
Ian
-----Original Message-----
From: vipaudioaccess-bounce@xxxxxxxxxxxxx <vipaudioaccess-bounce@xxxxxxxxxxxxx>
On Behalf Of Steve Spamer
Sent: 18 March 2021 11:34
To: vipaudioaccess@xxxxxxxxxxxxx
Subject: [vipaudioaccess] Re: Audio quantise
Again, Ian, if this is easily reproducible at your end, perhaps a tandam would
give me the best opportunity to see what's going on if you're up for it.
Best Steve.
-----Original Message-----
From: vipaudioaccess-bounce@xxxxxxxxxxxxx <vipaudioaccess-bounce@xxxxxxxxxxxxx>
On Behalf Of il@xxxxxxxxxxxxx
Sent: 18 March 2021 05:41
To: vipaudioaccess@xxxxxxxxxxxxx
Subject: [vipaudioaccess] Re: Audio quantise
Hi JP
I also have the same kind of issues with very small objects. However, what
I've found is that they do get selected but JAWS doesn't report the fact.
Steve, would increasing the object size, so zoom in to 500ms, would this help?
Best
Ian
-----Original Message-----
From: vipaudioaccess-bounce@xxxxxxxxxxxxx <vipaudioaccess-bounce@xxxxxxxxxxxxx>
On Behalf Of Jean-Philippe Rykiel
Sent: 17 March 2021 22:47
To: viplist <vipaudioaccess@xxxxxxxxxxxxx>
Subject: [vipaudioaccess] Re: Audio quantise
Hi again,
a small update to my issue, I tried it again after restarting my computer, no
change. Then, whilst in the audio quantise wizard dialogue, I tried to switch
Jaws to its alternate mode, but I was unlucky again, as the whole dialog became
inaccessible. Steve, really sorry to put this on you just a few days before you
released the new script version, I should have tried it before.
Best,
JPR
2021-03-17 20:07 UTC+01:00, Jean-philippe Rykiel <jprykiel@xxxxxxxxx>:
hi Steve,
I remember we had a discussion about this before the current script
version, I asked you to Add some buttons and change some labels, which
you kindly did. Strangely enough, I Never had the Opportunity to test
audio quantising before tonight. So, I would like you to check if you
can. I used a pair of tracks with only one object Each to start with,
An African callebash recorded with 2 microphones, but on 2 mono
tracks;So I grouped both Objects and started using the audio quantise wizard
on them.
Splitting at transience seemed to work right, but After that, I
noticed I couldn't reached the created objects. Is it because of your
new object detection system, as Splitting by transience create very
very small objects, and it seems to put Jaws into some kind of trouble.
Then, back to the audio quantise wizard dialogue, I was unable to
reach my Goal, as tabbing through the buttons I reached the Transient
sensitivity slider that I had set to 60% before doing the split by
transience, but at that point, when I reached the slider again, Jaws
became totally silent and I had to restart Samplitude which I couldn't
do except by killing it in the task manager.
If This issue is caused by the new object detection system, is it
possible to temporarily disable it in case of audio quantise? It
doesn't happen that often to get so many micro objects.
Do you have a solution?
Cheers,
JPR
--
http://www.jprykiel.com
https://www.youtube.com/c/jprykiel
http://soundcloud.com/ryksounet
https://www.youtube.com/c/jprykielhttp://facebook.com/jeanphilipperyki
el
