# Mactel

**URL:** <https://forum.juce.com/t/mactel/597>\
**Category:** MacOSX and iOS\
**Created:** [January 12, 2006, 2:40pm UTC](https://forum.juce.com/t/mactel/597 "2006-01-12T14:40:50Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![graffiti](https://avatars.discourse-cdn.com/v4/letter/g/8dc957/32.png) [@graffiti](https://forum.juce.com/u/graffiti)\
**Post date:** [January 12, 2006, 2:40pm UTC](https://forum.juce.com/t/mactel/597/1 "2006-01-12T14:40:50Z")

</div>

Howdy Jules,

Just wandering what the skinny is with Juce and the Intel Macs?? Do you anticipate any problems with the current Juce on Intel Mac? Do you plan to get an Intel Mac anytime soon??!!!

Cheers,  
graf.

---

<div class="post-metadata">

**Author:** ![jules](https://avatars.discourse-cdn.com/v4/letter/j/41988e/32.png) [@jules](https://forum.juce.com/u/jules)\
**Post date:** [January 12, 2006, 3:25pm UTC](https://forum.juce.com/t/mactel/597/2 "2006-01-12T15:25:23Z")

</div>

At least one person’s had it running on intel, though I’ve not got a machine myself yet.

Anyone know if the new MacBooks can run Windows? I need a new PC laptop anyway, and would love to get one of those if it can do both…

---

<div class="post-metadata">

**Author:** ![ring2](https://avatars.discourse-cdn.com/v4/letter/r/b5ac83/32.png) [@ring2](https://forum.juce.com/u/ring2)\
**Post date:** [January 12, 2006, 5:00pm UTC](https://forum.juce.com/t/mactel/597/3 "2006-01-12T17:00:40Z")

</div>

> [@](#):
>
> Anyone know if the new MacBooks can run Windows?

Unfortunately, that’s very hard. Because MacBook firmware is EFI, not BIOS. Currently windows does not support EFI…

I would LOVE to JUCE to support x86 Mac ASAP. Because Apple announced that they will release Logic Pro universal binary update in March.

I’ve got a confimation by my boss to use JUCE for our next product if it can build x86 Mac plugins…

Best regards,  
Masanao Hayashi

---

<div class="post-metadata">

**Author:** ![jules](https://avatars.discourse-cdn.com/v4/letter/j/41988e/32.png) [@jules](https://forum.juce.com/u/jules)\
**Post date:** [January 12, 2006, 5:28pm UTC](https://forum.juce.com/t/mactel/597/4 "2006-01-12T17:28:41Z")

</div>

Oh, it’ll certainly work by then - as I say, it already compiles for intel, and has been run by at least one person with no problems.

---

<div class="post-metadata">

**Author:** ![ring2](https://avatars.discourse-cdn.com/v4/letter/r/b5ac83/32.png) [@ring2](https://forum.juce.com/u/ring2)\
**Post date:** [January 12, 2006, 6:43pm UTC](https://forum.juce.com/t/mactel/597/5 "2006-01-12T18:43:52Z")

</div>

> [@jules](#):
>
> Oh, it’ll certainly work by then - as I say, it already compiles for intel, and has been run by at least one person with no problems.

At the line 284 of the juce\_mac\_Windowing.cpp,

```auto

        {
            for (int y = 0; y < h; ++y)
            {
                uint32* const lineData = (uint32*) (imageData + lineStride * y);
                
                for (int x = 0; x < w; ++x)
                    lineData[i] = CFSwapInt32BigToHost (lineData[i]);
            }
        }

}
```

The “i” should be “x”? That’s very tiny bug. 🙂

I’ll try to run my project on DTK tomorrow! Thanks!

Best regards,  
Masanao Hayashi

---

<div class="post-metadata">

**Author:** ![jules](https://avatars.discourse-cdn.com/v4/letter/j/41988e/32.png) [@jules](https://forum.juce.com/u/jules)\
**Post date:** [January 12, 2006, 8:39pm UTC](https://forum.juce.com/t/mactel/597/6 "2006-01-12T20:39:33Z")

</div>

oh, well spotted… strange that I didn’t see that one.

---

<div class="post-metadata">

**Author:** ![ring2](https://avatars.discourse-cdn.com/v4/letter/r/b5ac83/32.png) [@ring2](https://forum.juce.com/u/ring2)\
**Post date:** [January 13, 2006, 9:35am UTC](https://forum.juce.com/t/mactel/597/7 "2006-01-13T09:35:56Z")

</div>

I tested my project on DTK. Basically, it worked!! Cool!!

I found a problem. The internal audio device was listed separately. I saw “HD Audio Input” and “HD Audio Output”. They should be handled as one device. But it was on DTK, not on iMac. I don’t know the result on Intel iMac… And I don’t know the problem is OS bug or not.

Thanks! It’s time to buy JUCE!! 😃

Best regards,  
Masanao Hayashi

---

<div class="post-metadata">

**Author:** ![jules](https://avatars.discourse-cdn.com/v4/letter/j/41988e/32.png) [@jules](https://forum.juce.com/u/jules)\
**Post date:** [January 13, 2006, 9:47am UTC](https://forum.juce.com/t/mactel/597/8 "2006-01-13T09:47:00Z")

</div>

Wouldn’t have thought the CPU would make any difference to the CoreAudio code, so must be a driver wierdness on the DTK.

But if the two devices do show up separately, I can’t think of any way in juce of making them stick together - you’d need to set up an aggregated device.

---

<div class="post-metadata">

**Author:** ![Dogym](https://avatars.discourse-cdn.com/v4/letter/d/b4bc9f/32.png) [@Dogym](https://forum.juce.com/u/Dogym)\
**Post date:** [January 16, 2006, 1:00pm UTC](https://forum.juce.com/t/mactel/597/9 "2006-01-16T13:00:58Z")

</div>

Typically many USB devices appear as 2 device in the system, one for the input endpoint, one for the output endpoint, so you should expect this behaviour when dealing with I/O on OSX. Only with a custom driver this doesn’t happen.

---

<div class="post-metadata">

**Author:** ![jules](https://avatars.discourse-cdn.com/v4/letter/j/41988e/32.png) [@jules](https://forum.juce.com/u/jules)\
**Post date:** [May 12, 2017, 10:04am UTC](https://forum.juce.com/t/mactel/597/10 "2017-05-12T10:04:16Z")

</div>