Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - ajith

Pages: [1] 2 3 ... 6
1
Amulet Remote / Re: Amulet Remote and VirtualBox
« on: October 18, 2015, 11:59:58 PM »
So its a Win10 guest VM inside a Win10 host! Like Nime5ter, I too was under the impression you were running something else (Linux) as the host OS. I'm sure you'll have your reasons for the redundancy :)
Sadly, my experience is with VB on Linux hosts. I don't have a Win 10 machine to try it either.

I had a bit of struggle initially to make the Amulet mic work on Linux.  (See beginning of this thread) Part of the problem was some permission related issues. I had to add my Linux host user to a "vboxusers" group. Now I'm wondering if the current problem is similar. Try running VirtualBox as Administrator, see if you can "allow" VB through UAC, etc. Also, try playing around with the VirtualBox Audio Controller. Try the solution in this link: stackoverflow.com/questions/28134018/microphone-in-windows-10-in-virtualbox

Check the Windows Event viewer logs on the guest OS as well as the host for any clues.

-Ajith

2
Amulet Remote / Re: Amulet Remote and VirtualBox
« on: October 18, 2015, 04:38:00 PM »
Hmm .... can't think of anything else that can be tried at the moment (its 1:00 am here in India, and I'm half asleep :)
Will try to figure out something tomorrow. Meanwhile what's the host OS you're using? Maybe the answer is somewhere in this thread, but in my present state, I couldn't find it!

-Ajith

3
Amulet Remote / Re: Amulet Remote and VirtualBox
« on: October 18, 2015, 04:15:58 PM »
...Confirmed amulet works on the host too. Still cant get the actual audio in the guest to work.

If the Amulet dongle is properly recognized in the guest OS, then it shouldn't work in the host at the same time. Is this the case?  Or does it continue to work in the host OS as a microphone at all times?

What is the host OS you're using?

4
Amulet Remote / Re: Amulet Remote and VirtualBox
« on: October 18, 2015, 03:01:35 PM »
@vulcanjedi - James and Nime5ter already have suggested most of the things I can think of. Did you try the Amulet remote with your Win 10 laptop? Did it work as a microphone (could you record audio using Sound Recorder?)?

Here's something I would try at this point:

What is the version of Oracle Virtualbox you're using? If it isn't the latest, can you try upgrading it to the latest (5.0.6 right now)? To upgrade, it only takes a download and an install, as you'd do if it were the first time. The guest VM definition and virtual OS disk is preserved across the upgrade. After this install,
1. make sure you also install Virtualbox's companion "extension pack" for the corresponding version of Virtualbox and
2. Install and upgrade the "guest additions" within the guest VM using the CD ISO image that Virtualbox provides.
3. Reboot the VM and try the Amulet as a microphone.

Also, I hope you are not creating the USB filters by hand. The filters should appear under USB configuration in Virtualbox automatically, once the Amulet USB dongle is plugged in. At this point, you should have to just enable the checkbox against the filter. If you upgrade as described above, try to remove all USB filters, reboot VM and re-create the filters by plugging in the Amulet dongle.

-Ajith

@Nime5ter - those are some very kind words you mentioned about me :)

5
General Discussion / Re: Does VCSetEventTimer to time of day work?
« on: April 07, 2014, 04:26:37 AM »
I don't think you really followed the course of the whole thread, but in particular, after we established what the problem was, I posted this:

http://voxcommando.com/forum/index.php?topic=1484.msg12900#msg12900

The problem was identified, and I said I would fix it, by adding 24 hours if the time was "before now".

Oops! I missed the part where you said you meant to fix it!  :-[
Sorry for wasting your time!

6
General Discussion / Re: Does VCSetEventTimer to time of day work?
« on: April 06, 2014, 11:32:23 PM »
It is not too demanding because this is the way it already is.

Hmm... in that case I'd have thought the SetEventTimer command would accept a time parameter like 00:30 without a workaround, and the event would have fired at 30 min past midnight, no matter what the current time is. What am I missing?

7
General Discussion / Re: Does VCSetEventTimer to time of day work?
« on: April 06, 2014, 11:26:29 PM »
I think it's been a while since you've had time for the VC forum, Ajith, so you may not have noticed that quite a few of the new VC users have made it clear they're not comfortable with things like Python scripting.

It turns out that what makes intuitive sense to a black-box user is rather different than what makes intuitive sense to programmers.  :biglaugh

But it means that it will be less work/stress for James to keep the front end as layperson-oriented as possible and leave the Python workarounds to folks like you.

I understand. But the programmer friendly interface was what attracted me to VOX, in the first place! I guess I'm in the minority now. Everyone cannot be pleased at the same time, I guess  :)

8
General Discussion / Re: Does VCSetEventTimer to time of day work?
« on: April 06, 2014, 02:12:18 PM »
I'm not sure what you mean by this.  Are you suggesting we all use the 24 hour convention when talking on the forum, or are you suggesting that the program assume a 24 hour format?

AFAIK VC will assume a 24 hour format if you don't specify AM or PM and so will I.

My reply is a little late, but what I meant was the latter. I'd like the program to have one unambiguous way to specify time. And it shouldn't depend on whether the specified time is in the past, etc., A past time should just mean that the time is specified for the next day, like all alarm clock settings! This way of doing it might be technical, and not conforming to conventional language like "remind me to take the dog out at 10". But once we have that technical, unambiguous way of inputting time, making it understand conventional language could be done as per individual preference using tools like Python Scripting etc.,

Just my 2 paisa!  Just ignore this if it doesn't make sense or too demanding :)

PS: Thanks, nime5ter for the creative solution. :) I am yet to try it out.

9
General Discussion / Re: Does VCSetEventTimer to time of day work?
« on: April 06, 2014, 09:40:13 AM »
I think the error is thrown when you try to set a time that is before the current time.  Anything else I try with a time later than "now" seems to work perfectly.  I could improve the handling of this by automatically adding 24:00 hours when the specified time is earlier than "now".

I had intended to do that, but I guess I was waffling about whether or not I should add 12 hours or 24 hours.  If it is 10:00 AM and you say "set the alarm for 9:00", it is not clear if you want it to be at 9:00 PM today or 9:00 AM tomorrow.  A lot of people (including me) use a 12 hour clock even though it is as stoopid as using feet and miles and Fahrenheit.

I'll just set it to add 24 hrs for now.

I just verified this. I get the error when I set a time (in 24 hr format, without AM/PM, or even in 12 hr format) that is before the current time.
The way I want to use this is to set a timer on VC.Loaded event for 12:30 AM (this is actually 00:30 in 24 hr format) to generate a "TIMER_SHUTDOWN" event. I would then use the TIMER_SHUTDOWN event to shutdown my media center PC automatically. Presently, neither 00:30 nor 12:30 AM works, because both seem to be "before" the current time.

To remove the confusion, can we just stick to the 24 hr format and assume 09:00 means 9 AM and 21:00 means 9 PM?


10
James,

If you need any help with researching APIs and stuff, I'm available.

-Ajith

11
VoxWav Free and VoxWav Pro / Re: Voxwav 2.2.1
« on: October 02, 2012, 12:24:39 AM »
I too experienced the "second thing" that painy reported above. There is no error message from VC, but Windows reports that "This application has stopped. Do you want to close it?" or something to that effect. I'm afraid I haven't observed any pattern to this behavior. One difference I noted from painy is that, for me, VC also stops responding when this happens. I need to do a full restart of VC to recover from this condition. So maybe it is not exactly the same issue I am facing. I'd be glad to test anything specific and report. Do let me know.

12
I will post new features here (LEGACY BOARD ONLY) / Re: Version 0.964
« on: September 14, 2012, 01:22:59 PM »
>> How long do I  have, if I want to get feedback from you today?

It is 9:50 pm IST now. Given that tomorrow is a weekend (yay  ;D), I can be up till 2:00 am, that means I can provide feedback for another 4 hours.

13
I will post new features here (LEGACY BOARD ONLY) / Re: Version 0.964
« on: September 14, 2012, 11:50:13 AM »
>> >> You could also try ignoring the "visual on" and just start speaking immediately and let me know if it still works reliably.
>> Will try that now.
Did that. It seems to work reliably most of the time, even if I start speaking commands ignoring the visual ON. I'm sorry about the uncertainty there - I am not really 100% sure of this since on a couple of occasions, for a couple of short commands, I thought it didn't recognize it because I started too early.


Also, I do not see a pattern to the null exception. It is seemingly random.

Another thing I noticed is that I can do a quick tap on the "Press and hold to speak" button and make it stick in the "ON" position. It remains in that state till I touch the button again. It gave the null error when it came out of this induced "ON" state on a couple of occasions. Again, I am unable to see a pattern here.

Note: I never did the "tap" test on the previous samba versions!


EDIT: Tested a bit more on the Tab, specifically the "tap" test. I can make the button stick here too, but try as I may, I couldn't reproduce the null exception on it even once.

All of the above on the S2 of course. Will try the same on the Tab.


14
I will post new features here (LEGACY BOARD ONLY) / Re: Version 0.964
« on: September 14, 2012, 11:27:33 AM »
>> which two times?  First two?  Or just randomly.  See if you can detect any kind of pattern please.
The first 2 commands actually worked. It failed the first time on the 3rd command. Then again after a few successful commands.

Will watch for any pattern and report.

15
I will post new features here (LEGACY BOARD ONLY) / Re: Version 0.964
« on: September 14, 2012, 11:26:02 AM »
>> I wonder what kind of WIFI setup / speed you have? 
WiFi is from a Cisco Linksys E4200  N-Router.

>> When you finish speaking does VC respond quickly?
Yes, it ddoes respond quickly

>>  This part in particular should be significantly faster, especially for longer commands.
Yes, it is indeed faster as I said earlier.

>> You could also try ignoring the "visual on" and just start speaking immediately and let me know if it still works reliably.
Will try that now.

Pages: [1] 2 3 ... 6