AMP Wishlist Thread

[macalanche]

Ok, I'll do what I can to help. I'm a ****ty editor but I can do reseach. I'll see what I can find out about gesture input.

Let us know if you need anything else(beside time).

[LightningMac]

I've tried to send as much as info as I could on GPS, I personally think OBD II would be great, but realistically I think XM and GPS should be a priority, but hey maybe that's just me...

[JakobMetzger]

Heres some stuff I found on Equalizers...(I dont know which one you need)
http://developer.apple.com/cgi-bin/s...ult_collection

[LightningMac]

I think this is what you're looking for on an equalizer, it says it's built into OS 10.4

http://developer.apple.com/documenta...section_1.html

[Jirka Jirout]

I think this is what you're looking for on an equalizer, it says it's built into OS 10.4

http://developer.apple.com/documenta...section_1.html

This is CoreAudio framework, which is pretty low-level and you cannot use it easily (if at all) with NSMovieView, that is used in AMP (BTW: It might not be a bad idea to replace it with QTMovie view - more functions and quite a few issues fixed).

By far the easiest way of implementing an equalizer is to use iTunes for playback and control its equalizer via AppleScript.

[aychamo]

This is CoreAudio framework, which is pretty low-level and you cannot use it easily (if at all) with NSMovieView, that is used in AMP (BTW: It might not be a bad idea to replace it with QTMovie view - more functions and quite a few issues fixed).

By far the easiest way of implementing an equalizer is to use iTunes for playback and control its equalizer via AppleScript.

Jirka, is it possible to get/set the current play position (time, like you are at minute 2:03 of a 4:00 minute song) via iTunes & AppleScript interfacing?

[Jirka Jirout]

Jirka, is it possible to get/set the current play position (time, like you are at minute 2:03 of a 4:00 minute song) via iTunes & AppleScript interfacing?

Yes. I use this to store the position when the app goes down and then resume the playback the next time it is started.

here is how to store the position (moduleSetup is NSMutableDictionary):

- (void) readCurrentPosition{
    NSAppleScript *asExecutor;
    NSAppleEventDescriptor *asResult;
    asExecutor = [[[NSAppleScript alloc] initWithSource: @"tell app \"iTunes\" to get {player position, index of current track, index of current playlist}"] autorelease];
    asResult = [asExecutor executeAndReturnError:nil];
    [moduleSetup setObject: [NSNumber numberWithInt:[[asResult descriptorAtIndex:1]int32Value]] forKey:@"CURR_TIME"];
    [moduleSetup setObject: [NSNumber numberWithInt:[[asResult descriptorAtIndex:2]int32Value]] forKey:@"CURR_TRACK"];
    [moduleSetup setObject: [NSNumber numberWithInt:[[asResult descriptorAtIndex:3]int32Value]] forKey:@"CURR_PLIST"];
}

and here how to resume from the stored position:

- (void)doPlay{
    NSString *asCommand = [NSString stringWithFormat:@"tell application \"iTunes\"\r play track %i of playlist %i of source \"%@\"\r set player position to %i\r end tell", 
	[[moduleSetup objectForKey:@"CURR_TRACK"] intValue], [[moduleSetup objectForKey:@"CURR_PLIST"] intValue], [moduleSetup objectForKey:@"CURR_SRC"],
	[[moduleSetup objectForKey:@"CURR_TIME"] intValue]];

    //NSLog(asCommand); //DEBUG
        [[[[NSAppleScript alloc] initWithSource:asCommand] autorelease] executeAndReturnError:nil];
}

[sdashiki]

All I know of Mac OBDII is the python script thing that deals with it.

Youd need a serial to USB converter, and basically a way to read the info off the USB signal and interpret it into graphical or numerical data with labels etc.

Scantool has their own software for doing that, but its Windoze

[LightningMac]

here's info on pyobd, I think it's what you're referring to and it says it works with OS X:

http://www.cs.unm.edu/~donour/cars/pyobd/

[Jirka Jirout]

Youd need a serial to USB converter, and basically a way to read the info off the USB signal and interpret it into graphical or numerical data with labels etc.

If you use a serial to USB converter, its driver creates a device file in /dev/ and you can read/write data exactly the same way you read data from a file (using NSFileHandle). Reading the data is a piece of cake. What is (a little) more difficult is to parse the data you read, but since there is so much documentation and examples out there, it is not that difficult either.