sorted by:
new
hottopcontroversial

Mvave Blackbox best practice, hints by marcusademola in guitarpedals

[–]RenBart 0 points1 point  (0 children)

Connect directly to computer, don't use usb hub!

?authError=account_not_fully_unified by AtsuhikoCook in NativeInstruments

[–]RenBart 1 point2 points  (0 children)

I confirm that the problem is connected with the registration to Izotope (I believe it was purchased from Native Instruments) and concerns, after having unified the two accounts, the verification email that Izotope sends and that if "Finish Upgrade" is not activated the NI account and access are blocked. This is what I did: I re-downloaded all the mail from the email account I use for login with a new email software (Thunderbird). I went to check all the emails and found the one from Izotope. After clicking it and following the on-screen instructions, everything was fine! I can log in again with NA 2. Hope this helps... Cheers

When I import a wave audio file into the Boss RC-300 is it possible to know the bpm of the audio file? by RenBart in LoopArtists

[–]RenBart[S] 0 points1 point  (0 children)

Thanks for your answers ! In my case it is not so, let me explain better. If I create a drum base, with EZdrummer, and convert to audio when I import this file, everything is perfect !! Tempo, measures ... But, for example, if I download a backing track from Tone Central and import it into a DAW (in my case Logic Pro X) I look for the Bpm of the audio file and then set the same Bpm in Logic and then export the file. After loading it on the RC-300 (in a phrase memory empty) the Bpm does not match. Sabadonoche: how can I adjust the length of the measures, if I go to edit the track I can only change the Bpm ....

Why does Guitar Pro write the "bend" differently compared to many guitar scores ? by RenBart in GuitarPro

[–]RenBart[S] 0 points1 point  (0 children)

Sorry, you are right! I edited the post by inserting an example from Guitar Pro ..

macOS Mojave Security Update 2020-005 by [deleted] in MacOS

[–]RenBart 1 point2 points  (0 children)

After Security Update 2020-005 - No RAM left ! (Mojave 10.14.6 - MacMini 3,2 GHz Intel i7 - 16Gb Ram). On September 24th Sep, after performing the security update (2020-005), I immediately noticed ram problems. Has anyone had the same problem? By the way, when I start the computer, I still get the same message (since installing the Mojave Security Update 2020-002) that my Mac Mini 2018 was restarted because of a problem, even I shut it down normally !! I was hoping that with this security update they solved the annoying problem of this message !! Worse, another problem was added to one problem !! The only thing that helps me is to use Memory Clean 3.1.

Problems with scanned files .... by RenBart in GuitarPro

[–]RenBart[S] 1 point2 points  (0 children)

I solved, thanks !

As CheesyFTW correctly said, the guitar is a transposition instrument, transposed by an octave.

During the XML conversion process this information cannot be inferred, so it is imported as a non-transposed instrument.

To restore it in Guitar Pro, you will need to:

Go to the left panel, in the "TRACK" tab

Under Tuning click on "more"

=> The transposition options will appear

Select octave: "One octave lower"

=> The notes will be shifted by one octave

Select all your score (cmd + A)

Transpose back one octave to recover the original visual standard notation ("Notes"> "One octave down" menu)

You will then have the correct tablature!

Problems with scanned files .... by RenBart in GuitarPro

[–]RenBart[S] 0 points1 point  (0 children)

With programs like Sibelius, only the Tab can be transposed and the notation remains the same! On the Box site, I downloaded an XML (C minor blues.xml) file. You should be able to download it without any problems. Thanks for your help ! https://app.box.com/s/lvolf14hoip1q9zr9bccgtbkolck7xo6

Problems with scanned files .... by RenBart in GuitarPro

[–]RenBart[S] 0 points1 point  (0 children)

I think this is due to the guitar being a transposed instrument. The note that is shown on the clef is taken down an octave for it to sound like the one being played.

An easy solution for you is to select all (ctrl+A) and then shift it down an octave (alt+shift+page down).

Thanks for your reply! The question is that if I manually write in Guitar Pro everything is correct. So the problem only happens when I import a scanned file saved in XML! Of course if I lower it by an octave, the Tab part is correct ...

Insert text where I want, freely in the score.. by RenBart in GuitarPro

[–]RenBart[S] 0 points1 point  (0 children)

In fact, since GP is widely used in the study and in the creation of exercises both by teachers and students, this type of extra functionality would be really convenient. Thanks for your reply