Yamaha n Series

[d3man]

Originally Posted by Geosync

Lemontree,

Take the unit in for service, let our techs suss out the problem

You shouldn't have to spend hours on this.
Sorry you are having these problems

Wait a minute!

I had a SAME problem today

And I saw that n12 Firmware update software has 6 pages of manual!

Here's the secret:


Updade operation
1. Connect a computer directly to a n8/n12 (without using a hub) by using an IEEE1394 cable.
Be sure to disconnect all other IEEE1394 devices, except the one to be updated.

2. Simultaneously hold down the [PREV] button and [CLICK REMOTE ON] buttons and turn the power on for the n8/n12.
The n8/n12 will boot up in update mode. When booting up in update mode, the LED at the top of the MASTER LEVEL METER-L lights up. After a few seconds, the LED at the bottom of the MASTER LEVEL METER-R will flash.
3
3. Double-click "nUpdate.exe" to start the program.
When the program works correctly, "Searching for FW device…" will briefly be shown in the Status column for a short time. Then, the Output Port column will display "FIRM." .......



....etc etc



.......


That's it!

I was also trying to uninstal and install Tools and drivers and update firmware(s) 4-5 times, but i was always "updating" the firmware without THAT STEP WHICH INCLUDES TURNING ON N12 WITH THAT 2 BUTTONS PRESSED!

[d3man]

Just to let you know, I was already in my bed whatching this thread on my smartphone and I saw someone has a same problem I had today afternoon ... I came to studio below my flat to type this

[Lemontree]

Originally Posted by d3man

2. Simultaneously hold down the [PREV] button and [CLICK REMOTE ON] buttons and turn the power on for the n8/n12.
The n8/n12 will boot up in update mode. When booting up in update mode, the LED at the top of the MASTER LEVEL METER-L lights up. After a few seconds, the LED at the bottom of the MASTER LEVEL METER-R will flash.


That's it!


I was also trying to uninstal and install things 4-5 times, but i was always "updating" the firmware without THAT STEP WHICH INCLUDES TURNING ON N12 WITH THAT 2 BUTTONS PRESSED!

I just figured that out about an hour ago... I spent the last half hour making my own templates for the stem work I do and hooking up the TD3 and triggering Superior 2.0 with no audable latency

I must be one of the stupidest guys posting in here to miss that step

Appologies to everyone for my random rants, especialy George.

Now.... do I try it on xp64? LMAO!! I'm happy as larry on xp32 for now.

[d3man]

Originally Posted by Lemontree

I just figured that out about an hour ago... I spent the last half hour making my own templates for the stem work I do and hooking up the TD3 and triggering Superior 2.0 with no audable latency

I must be one of the stupidest guys posting in here to miss that step

Appologies to everyone for my random rants, especialy George.

Now.... do I try it on xp64? LMAO!! I'm happy as larry on xp32 for now.

Yes, I missed that step today too - Noboby expects that way of operation after previous installations...

"Hold down those two buttons while standing on one foot and citating Old Testament..."

[Geosync]

Originally Posted by Lemontree

I just figured that out about an hour ago... I spent the last half hour making my own templates for the stem work I do and hooking up the TD3 and triggering Superior 2.0 with no audable latency

I must be one of the stupidest guys posting in here to miss that step

Appologies to everyone for my random rants, especialy George.

Now.... do I try it on xp64? LMAO!! I'm happy as larry on xp32 for now.

Glad it was just a Homer Simpson moment instead of a sick n12

[funkycornwall]

I have installed all the new drivers (eventually) and everything appears to be working fine. I also checked in Device Manager to see list of required drivers and they were all present and correct. However I also noticed that there was still a mLanBus driver present on my system - I feel sure this should have been removed. It is not listed in my list of software so I am not sure how it can be removed. Am I OK to leave it there?

Does anyone here know if it should be removed now that I have the new FW driver installed? (I am on Windows XP by the way)

Thanks for any advice

[Geosync]

Originally Posted by funkycornwall

I have installed all the new drivers (eventually) and everything appears to be working fine. I also checked in Device Manager to see list of required drivers and they were all present and correct. However I also noticed that there was still a mLanBus driver present on my system - I feel sure this should have been removed. It is not listed in my list of software so I am not sure how it can be removed. Am I OK to leave it there?

Does anyone here know if it should be removed now that I have the new FW driver installed? (I am on Windows XP by the way)

Thanks for any advice

Pages 6&7 of the Tools update guide that you downloaded to install the software ;-)

[kire]

I currently have a MacBook (a dual core but not the Pro), Cubase 5 and an N12.
I need more microphone inputs and have waited for the MR816x but before ordering I thought I should check here.

Do you think a MacBook (with Cubase 5) can do 16-24 channels in (using the N12, MR816x and a firewire disk) or do I need a new computer as well (like a MacBook Pro where I can run two firewire interfaces)?

Thanks for your help
(PS. George, you deserve a medal!)

[grame99]

anyone know why the n12 is suddenly so much more expensive? i got mine for 675 pounds last year - now it's at least a thousand...

[trock]

wow

thanks a ton for that TIP!! i did it and NOW i am correct with the new firmware, drivers, etc

sheesh

[smoke]

Glad everyone is back in business.

I resolved all of my issues as well. I believe that N12 and my computer do not like 88 sample rates. I can run it smoothly in Cubase, but the N12 does not want to start up correctly in this mode. Switching back to 48, and it loads as usual.

Also reinstalled all my software, and have Cubase 5 running as well as I can expect.

UAD-2 klonked out after reinstalling Cubase, reseated the card and reinstalled UAD5.2, and that works too.

Lets get back to making music now!

[smoke]

Originally Posted by trock

wow

thanks a ton for that TIP!! i did it and NOW i am correct with the new firmware, drivers, etc

sheesh

Feel free to toss your Mac questions around here. For example Spectrasonics software can indeed be hard to install/authorize, because the actual wizard is broken. You have to physically copy the challenge and response. You also may have to repair permissions. And you may need the wrapper, although it doesn't work too well.

[mikeynyuk]

Hey all,

Thanks to some helpful advice from George (thanks man, that worked fine of course) I have just bought an N12 second hand, got to playing with it last night. I only installed the tools that came on the CD because I read you guys were all in the middle of updating firmware etc and I figure I may as well do all the upgrading in one go. Anyhow, things are more or less working but I am experiencing drop outs and pops and clicks from the N12 both in cubase AI and whilst playing back files through windows media player.

I believe I'm using 1.00.00 N driver (or is it 2.00.00).

I'm on a PC,
windows xp pro 32 SP3
Intel core 2 quad Q6600
Asus P5QL Motherboard
4 gigs of RAM

I have a firewire PCI card in the back, I'm not computer literate enough to know how to find out its name or model and the guy who built my computer threw away any box or CD it came with. Perhaps someone can tell me how to check this? All I know is it cost 10 euros and worked fine with my firewire 410.

So my guess is its either a case of my needing to update the driver/and or firmware or I need to change my firewire card?

Any help would be much appreciated. Just a newb here whos trying to get it stable enough to try and learn how the desk and cubase work together before buying a full version of cubase and updating everything.

I have attached a sample I recorded in cubase with the drop outs and clicks. You can hear them at 17 secs and again at 30 etc...

thanks
Mike

[sundancexy]

Hello all,

I have followed this thread for quite some time and it actually convinced me to buy a Yamaha n12 as I first thought about other (cheaper) alternatives. George's continuing support in this forum and the fact that I ride several Yamaha motor bikes was probably the thing that tipped me in Yamaha's direction It's good to see someone really "live" and stand behind "his" product in a way like this. It's also very reassuring to see that in case of emergency there is support at hand. thumbsup

Anyway, what made me register at gearslutz and make my first post today is that I saw a few irritated people and some confusion about the upgrade/installation process with the new firmware.

I used the n12 with a MacBook Pro 17" together with Cubase AI 4.5.2 via the AI mLan driver. Yesterday I decided to buy Cubase 5 and the upgrade experience was a very pleasant one - everything is working fine and smoother now than ever before.

There are a few things to note though but if you read the installation instructions carefully you should not encounter any problems.

This is the way I installed the new drivers/firmware upgrades: First, I installed the firewire fw-upgrade version 1.0.7 while the n12 was still connected via the mLan driver.
Then I removed the AI/mLan driver files following the instructions for deinstallation found in the document packaged with the old "Tools for n"install files.

After that I installed the "Tools for n" Version 2.0 and the n12 firmware upgrade to version 1.0.3. While the firmware upgrade runs, please note the simulated progress bar on the n8/n12 i.e. the master volume LEDs lighting up one by one increasing to the top. After the update is done and all LEDs light up it takes 1-2 minutes for the n8/n12 to restart automatically.

You can see the LEDs go off on the n8/n12 and then light up the way they usually do if you turn on the device. Note that the status message in the installer window does not! change automatically after the installation procedure is done! The firmware upgrade has been installed successfully when the n8/n12 restarts. You can then safely close the installer window by clicking on the red "x" Button at the top of the window and check if the new firmware version has been correctly installed by pressing the "stop" button in the control section of the n8/n12 right after you turn the device on - as described in the install docs. This has probably got some people confused.

If you follow instructions closely the upgrade procedure should be very smooth. The new driver seems to work a lot better than the mLan driver used before. Now the connection just works reliably in the background. No checking icon status colors anymore. Just plug in the n12, start up Cubase and start working.

As this actually works even better than Cubase AI 4 integration I can only recommend the upgrade to Cubase 5!

So, George, if anyone ever asks you what you are doing all day please let people know that you are actively promoting sales here probably more successful than any sales rep anywhere else. I would not have considered buying Cubase 5 without the n12.

Now the next step may be the cc121. Yamaha really did a fine job getting people addicted to their stuff one step at a time

Cheers from Germany,

Philipp

[johnnyz]

At the present time i am using the latest version of cuabase ai4,should i upgrade the firmware on my n12 or just leave well enough alone,at the present time i will not be upgrading to cubase 5.Or does the new firmware update make the n12 more stable?jz

[grame99]

does the start-up order still matter with the new driver or can i just turn it on with the computer...?

[Geosync]

Originally Posted by grame99

does the start-up order still matter with the new driver or can i just turn it on with the computer...?

The new driver is much more robust and forgiving. I would think startup would not be so much of issue. There is not enough use time to give you a solid answer.

[Geosync]

Originally Posted by johnnyz

At the present time i am using the latest version of cuabase ai4,should i upgrade the firmware on my n12 or just leave well enough alone,at the present time i will not be upgrading to cubase 5.Or does the new firmware update make the n12 more stable?jz

It should be. That is my personal experience.

[grame99]

Originally Posted by Geosync

The new driver is much more robust and forgiving. I would think startup would not be so much of issue. There is not enough use time to give you a solid answer.

cool. thanks for that.

[Lemontree]

I couldn't help myself.... After getting everything working on XP32 again I instaled everything on xp64 bit today...with the firmware upgrade done correctly last night everything went great. The drivers are SOLID on xp64 but allas there is no transport control or cubase light.

Atleast I know on really big projects, if I need that extra RAM I can move over to xp64 and use the mouse for transport and still get the job done.

Any ideas why it doesn't connect george? It's no biggie. I'm actualy thinking it might be cause I'm running 32bit cubase on 64bit XP...hmmm, 64bit driver with the 32 bit extensions?

Main thing is everything is super sweet on my 32bit system. And is that an audio input I see under windows sound manager? Thats new! Main reason I gave up doing internet broadcasts when I got the N12 was cause it didn't have this reature. I'm guessing I can do a windows messenger live video call now with a bit of sweet spot compression and some nice plate verb on my mic? HAHAHA!

[mikeynyuk]

Hey George,
Could you take a look at post 2536 for me? I'm not sure if this is the right place to be posting for this kind of support, if not perhaps someone could direct me to a more appropriate forum. I should add that I played with the buffer size in cubase and it makes no difference to my problem.
thanks
Mike

[d3man]

Originally Posted by Randall

So after reading that I would get enhanced FW performance I decided to take the plunge and update everything... something is not right here.. I followed the instructions installed everything.. updated the N12.. all seemed to go well..
but now when I open a project I get a "missing ports" message that shows everything is "unmapped"

When I go in to devices in Cubase to "VST audio system" it shows "yamaha steiberg FW ASIO" but when I try to switch to it I get a meesage that says "Device could not be opened"

in Yamaha Stenberg FW Driver panel the ASIO buffer size.. sample rate.. word clock master and clock source are all greyed out and I can't select anything.

Also no control of the software via the N12 transport.. at all

This is more than a little frustrating.. I've been on it a couple houes and feel like an idiot.

Look at the top of this page - Lemontree's and mine posts. The secret is in proper firmware upgrading. Read the red letters....thumbsup

[Lemontree]

Nice one Randall. welcome to the club!

[Geosync]

So my guess is its either a case of my needing to update the driver/and or firmware or I need to change my firewire card?

Things to try

1: Disable 1394 networking (network connections)
2: If you have wireless, turn it off
3: make sure you have the 1394 patch that sets speed of the bus back to S400 or S800

If all that fails, try a new card

[Lemontree]

Originally Posted by Lemontree

I'm actualy thinking it might be cause I'm running 32bit cubase on 64bit XP...hmmm, 64bit driver with the 32 bit extensions?

After a quick PM from george suggesting the quote above might work I've decided to get out of bed at 1am and test the theory.

I can now CONFIRM using windows XP 64bit, 32bit cubase, the 64bit YSFW driver and the 32bit extensions instaler results in a GREEN FOR ALL SYSTEMS GO big CUBASE LIGHT on the N12 all transport features are working...it just works !!!!!!!!!!!!!




WOOHOO!!!!!

I'm pretty shattered so I'll do some more testing with it and post up my results but for now it's doing everything it's supposed to do but instead of having 2.7GB of memory available a have 3.4GB available. And I still have 2 empty slots. This is fabulous!

[ScottFreeStyle]

Arghh Lemontree I am really really pleased for you mate...

I have just had a fantastic session with a female vocalist, I have written a great little pop song.. this song and the artist have real potential, but I am on a huge learning curve. I better get to bed...!!

Night Lemon mate, Im sure you will sleep better tonight brother!!

[Lemontree]

Thanks Scott, testing over and everything is A OK. It's 3:30am....I'm gonna sneek in quietly behind the wife while I still have one lol

[sirthought]

Glad to hear you are all making your way in Cubase 5 and the n12 updates. I hope what someone said about the n12 not handling computers with more than 4 gigs RAM isn't true. Any confirmation? All computers are going that route.

I'd love to hear how some of those new Cubase 5 features are working for you guys. Very interested the "Melodyne" type of tools. I'm still on Studio 4.1. I am not that active at recording at the moment, so I don't see a need to upgrade. But now and then the slutty side comes out to want the new thing!

[sundancexy]

just wanted to let you know that today I did my second installation of Cubase 5 - this time on Windows XP 32. Also with no problems. I uninstalled mLan driver and Cubase AI 4 first then installed Cubase 5, then the tools for n 2.0 from yamahasynth.com.
As I already upgraded the firewire and n12 firmware everything went fine. Took me 15 minutes to install everything. The new driver runs very smoothly just as on OS X. You can plug the n12 in and out while Cubase is running and there is no problem at all.

[Cinemuso]

Originally Posted by sirthought

Glad to hear you are all making your way in Cubase 5 and the n12 updates. I hope what someone said about the n12 not handling computers with more than 4 gigs RAM isn't true. Any confirmation? All computers are going that route.

I'd love to hear how some of those new Cubase 5 features are working for you guys. Very interested the "Melodyne" type of tools. I'm still on Studio 4.1. I am not that active at recording at the moment, so I don't see a need to upgrade. But now and then the slutty side comes out to want the new thing!

My understanding is that FW under Windows xp64 is not compatible with more than 4 gigs ram. Its a bug in xp64, if you like. Possibly Windows 7 beta is a different story, ie FW is fine with > 4G ram.

If your using 32 bit sequencer in windows xp64, the n12 should be ok with the new drivers, because your restricted to <4 G Ram. Now I'll go test it with the n8...