Log in
Log in

or
Enlarge
Add this product to
  • My former gear
  • My current gear
  • My wishlist
Yamaha NP-V80
Images
1/48
Yamaha NP-V80

Keyboard Arranger from Yamaha belonging to the Piaggero series

Thread Yamaha NP-V80 issue

  • 4 replies
  • 2 participants
  • 6,298 views
  • 2 followers
wildetudor

wildetudor

3 posts
New AFfiliate
First post
1 Posted on 01/06/2011 at 04:03:45

Hi all,

I recently got a Yamaha Piaggero NP-V80, and I've started to learn a few pieces, using mostly the Waiting feature from the Yamaha Education Suite (Y.E.S.), which I believe is found on many other Yamaha keyboards.

I'm guessing many people here have used that feature: you select a certain MIDI song, then press the Waiting button on the keyboard, and after a few beats are sounded (which give you the tempo), the LCD will display the first key (or combination of keys) that you have to press, and will wait until you do so, at which moment everything is repeated for the next key that needs to be pressed, and so on.

Problem is, this feature only seems to work for certain MIDIs. It certainly works for all songs that are built-in, and it worked for some MIDIs that I loaded into the keyboard, but not for others. For those MIDIs in the last category, when the Waiting button is pressed, nothing happens.

Without this function, learning a piece using a MIDI rendition of it is much more difficult, you essentially have to play a few seconds of it back, pause it, then try to play everything yourself till that point, then resume playback, and so on.

I have no idea what the keyboard doesn't like about those MIDIs - has anyone else noticed/found a fix for this? Maybe they have to be somehow edited to make them work with the Waiting function? Many thanks in advance for any replies!

Duch_Edward

Duch_Edward

2 posts
New AFfiliate
2 Posted on 02/08/2011 at 09:15:16

Hi Wildetudor,

I have the same "problem" with my MIDI files and lessons on my Yamaha Piaggero NP-V80. Did you already find a solution for this issue ?

Best regard,

Edward

wildetudor

wildetudor

3 posts
New AFfiliate
3 Posted on 02/08/2011 at 09:26:55

Hi, I'm afraid I didn't, all I was able to find out was that it is something to do with the Sysex commands contained in a MIDI file, i.e. those that don't work have some missing (or: extra) of those commands. Importing them into Cubase and saving them back into MIDI seems to be a workaround, however none of the freeware MIDI editors that I tried replicate this effect (Cubase is a very expensive software).

 

I thought it was a problem with the Waiting mode on all Yamaha, but apparently other Yamahas (e.g. the ESR/PSR series) work just fine in Learning mode with any external MIDI.

 

If anyone else reading this finds a solution please create an account (if you don't have one already) and tell us about it, thanks!

Duch_Edward

Duch_Edward

2 posts
New AFfiliate
4 Posted on 02/10/2011 at 07:56:28


Hi Wildetutor,

Please read the text in the link below:

http://www.notation.com/vb-forum/showthread.php?t=2878

For me it works to converts the MIDI File Format Type 1 to Type 0. I hope you can use this information.

Best regards from The Netherlands,

Edward

wildetudor

wildetudor

3 posts
New AFfiliate
5 Posted on 02/14/2011 at 09:39:07

Hi Edward, many thanks for that link, hope this will solve this problem once and for all!

cookies
We are using cookies!

Yes, Audiofanzine is using cookies. Since the last thing that we want is disturbing your diet with too much fat or too much sugar, you'll be glad to learn that we made them ourselves with fresh, organic and fair ingredients, and with a perfect nutritional balance. What this means is that the data we store in them is used to enhance your use of our website as well as improve your user experience on our pages and show you personalised ads (learn more). To configure your cookie preferences, click here.

We did not wait for a law to make us respect our members and visitors' privacy. The cookies that we use are only meant to improve your experience on our website.

Our cookies
Cookies not subject to consent
These are cookies that guarantee the proper functioning of Audiofanzine and allow its optimization. The website cannot function properly without these cookies. Example: cookies that help you stay logged in from page to page or that help customizing your usage of the website (dark mode or filters).
Audience analysis (Google Analytics)
We are using Google Analytics in order to better understand the use that our visitors make of our website in an attempt to improve it.
Advertising (Google Ads)
This information allows us to show you personalized advertisements thanks to which Audiofanzine is financed. By unchecking this box you will still have advertisements but they may be less interesting :) We are using Google Ad Manager to display part of our ads, or tools integrated to our own CMS for the rest. We are likely to display advertisements from our own platform, from Google Advertising Products or from Adform.
Marketing (Meta Pixel)

On our websites, we use the Meta Pixel. The Meta Pixel is a remarketing pixel implemented on our websites that allows us to target you directly via the Meta Network by serving ads to visitors of our websites when they visit the social networks Facebook and Instagram. The meta pixel are code snippets which are able to identify your browser type via the browser ID - the individual fingerprint of your browser - and to recognise that you have visited our websites and what exactly you have looked at on our websites. When you visit our websites, the pixel establishes a direct connection to Meta's servers. Meta is able to identify you by your browser ID, as this is linked to other data about you stored by Meta on your Facebook or Instagram user account. Meta then delivers individualised ads from us on Facebook or on Instagram that are tailored to your needs.

We ourselves are not in a position to identify you personally via the meta pixel, as apart from your browser ID no other data is stored with us via the pixel.

For more information about the Meta Pixel, the details of data processing via this service and Meta's privacy policy, please visit Meta Privacy Policy - How Meta collects and uses user data for Facebook and Meta Privacy Policy - How Meta collects and uses user data for Instagram.

Meta Platforms Ireland Ltd. is a subsidiary of Meta Platforms, Inc. based in the USA. It cannot be ruled out that your data collected by Facebook will also be transmitted to the USA.


We did not wait for a law to make us respect our members and visitors' privacy. The cookies that we use are only meant to improve your experience on our website.

Our cookies
Cookies not subject to consent

These are cookies that guarantee the proper functioning of Audiofanzine. The website cannot function properly without these cookies. Examples: cookies that help you stay logged in from page to page or that help customizing your usage of the website (dark mode or filters).

Audience analysis (Google Analytics)

We are using Google Analytics in order to better understand the use that our visitors make of our website in an attempt to improve it. When this parameter is activated, no personal information is sent to Google and the IP addresses are anonymized.

Advertising (Google Ads)

This information allows us to show you personalized advertisements thanks to which Audiofanzine is financed. By unchecking this box you will still have advertisements but they may be less interesting :) We are using Google Ad Manager to display part of our ads, or tools integrated to our own CMS for the rest. We are likely to display advertisements from our own platform, from Google Advertising Products or from Adform.

Marketing (Meta Pixel)

On our websites, we use the Meta Pixel. The Meta Pixel is a remarketing pixel implemented on our websites that allows us to target you directly via the Meta Network by serving ads to visitors of our websites when they visit the social networks Facebook and Instagram. The meta pixel are code snippets which are able to identify your browser type via the browser ID - the individual fingerprint of your browser - and to recognise that you have visited our websites and what exactly you have looked at on our websites. When you visit our websites, the pixel establishes a direct connection to Meta's servers. Meta is able to identify you by your browser ID, as this is linked to other data about you stored by Meta on your Facebook or Instagram user account. Meta then delivers individualised ads from us on Facebook or on Instagram that are tailored to your needs.

We ourselves are not in a position to identify you personally via the meta pixel, as apart from your browser ID no other data is stored with us via the pixel.

For more information about the Meta Pixel, the details of data processing via this service and Meta's privacy policy, please visit Meta Privacy Policy - How Meta collects and uses user data for Facebook and Meta Privacy Policy - How Meta collects and uses user data for Instagram.

Meta Platforms Ireland Ltd. is a subsidiary of Meta Platforms, Inc. based in the USA. It cannot be ruled out that your data collected by Facebook will also be transmitted to the USA.


You can find more details on data protection in our privacy policy.
You can also find information about how Google uses personal data by following this link.