Xojo Developer Conference
25/27th April 2018 in Denver.
MBS Xojo Conference
6/7th September 2018 in Munich, Germany.

[MBS] DR - kDRBurnRequestedSpeedKey (MBS Xojo Plugin Mailinglist archive)

Back to the thread list
Previous thread: [MBS] 4.0dr2
Next thread: [MBS] AppleScript.script


Re: [MBS] MIDI Destinations and External Devices   -   Ron Benditt
  [MBS] DR - kDRBurnRequestedSpeedKey   -   Bryan Lund
   Re: [MBS] DR - kDRBurnRequestedSpeedKey   -   Christian Schmitz
    Re: [MBS] DR - kDRBurnRequestedSpeedKey   -   Bryan Lund
     Re: [MBS] DR - kDRBurnRequestedSpeedKey   -   Christian Schmitz
      Re: [MBS] DR - kDRBurnRequestedSpeedKey   -   Bryan Lund

[MBS] DR - kDRBurnRequestedSpeedKey
Date: 04.01.04 05:29 (Sat, 3 Jan 2004 20:29:08 -0800)
From: Bryan Lund
Can someone give me an example of what parameter
kDRBurnRequestedSpeedKey (part of the DiscRecording classes) would work
with?

It takes a CFString as a paremeter, so I'm wondering if I should pass
the bytes/sec (as some other parts of DR do) or the speed designation
(such as "1x" speed).

Thanks!
-Bryan

Re: [MBS] DR - kDRBurnRequestedSpeedKey
Date: 04.01.04 18:00 (Sun, 4 Jan 2004 18:00:26 +0100)
From: Christian Schmitz
Bryan Lund <<email address removed>> wrote:

> Can someone give me an example of what parameter
> kDRBurnRequestedSpeedKey (part of the DiscRecording classes) would work
> with?

CFNumber.

> It takes a CFString as a paremeter, so I'm wondering if I should pass
> the bytes/sec (as some other parts of DR do) or the speed designation
> (such as "1x" speed).

It's a key for a dictionary where you use it with a CFNumber as a value.

e.g. you can use it like this: (untested)

dim d as CFDictionaryMBS
dim m as CFMutableDictionaryMBS
dim burn as DRBurnMBS

const x345 // Whatever speed you want

d°rn.Properties // get existing properties
mÐEdit // Make editable copy
m.set burn.kDRBurnRequestedSpeedKey,NewCFNumberMBSInteger(x)
burn.Properties=m // Apply them

Mfg
Christian

Re: [MBS] DR - kDRBurnRequestedSpeedKey
Date: 05.01.04 00:17 (Sun, 4 Jan 2004 15:17:02 -0800)
From: Bryan Lund

On Jan 4, 2004, at 9:00 AM, Christian Schmitz wrote:

> It's a key for a dictionary where you use it with a CFNumber as a
> value.
>
> e.g. you can use it like this: (untested)
>
> dim d as CFDictionaryMBS
> dim m as CFMutableDictionaryMBS
> dim burn as DRBurnMBS
>
> const x345 // Whatever speed you want
>
> d°rn.Properties // get existing properties
> mÐEdit // Make editable copy
> m.set burn.kDRBurnRequestedSpeedKey,NewCFNumberMBSInteger(x)
> burn.Properties=m // Apply them

Thanks, but say for const x above would I pass the bytes per second for
the burn (1024, etc) or the logical burn speed (1, 2, 4, 8, etc)?

-Bryan

Re: [MBS] DR - kDRBurnRequestedSpeedKey
Date: 05.01.04 00:32 (Mon, 5 Jan 2004 00:32:33 +0100)
From: Christian Schmitz
Bryan Lund <<email address removed>> wrote:

> Thanks, but say for const x above would I pass the bytes per second for
> the burn (1024, etc) or the logical burn speed (1, 2, 4, 8, etc)?

Please try and report as I don't know this.
But I bet it's in bytes per second.

PS: You can check it by checking what it returns for the current burn
speed later.

Mfg
Christian

Re: [MBS] DR - kDRBurnRequestedSpeedKey
Date: 05.01.04 10:01 (Mon, 5 Jan 2004 01:01:15 -0800)
From: Bryan Lund

On Jan 4, 2004, at 3:32 PM, Christian Schmitz wrote:

> Bryan Lund <<email address removed>> wrote:
>
>> Thanks, but say for const x above would I pass the bytes per second
>> for
>> the burn (1024, etc) or the logical burn speed (1, 2, 4, 8, etc)?
>
> Please try and report as I don't know this.
> But I bet it's in bytes per second.
>
> PS: You can check it by checking what it returns for the current burn
> speed later.

It's bytes per second. So passing in something like "1 *
burner.kdrDeviceBurnSpeedCD1x" works nicely for 1x speed write.

-Bryan