António Brites

alright thank you all it must be musescore I'll try to fix it.

41 minutes ago, pwalpwal said:

there are several points in that chain where any change might take place - exporting (might exclude certain data), importing (might ignore certain data), rendering to screen (does it look right in the track view)

first step is export using the same settings, then open the exported file again in musescore - is it the same there, does it look right?

if it does, how about in some other scoring software?

does opening it in cakewalk in the various different ways available make any difference? (file-open vs. double-click in explorer vs. import into project vs. drag from browser, etc)

/good luck!

Yeah when I imported it again to musescore it was different... but I don't know where the change happened...

2 hours ago, pwalpwal said:

i can't read notation but those score screenshots are definitely different - is something getting changed or ignored on import?

I'm not sure... where can i check that?

12 minutes ago, Nigel Mackay said:

So that's not the problem. Just as a cross-check, can you import the exported midi back into the notation software? And save your Cakewalk project as a midi file and import it into the notation software.

And just to satisfy yourself that it is not VSTi related, right-click on the track pane, insert a midi track, and then import your midi file into the midi track. Doesn't need to be associated with any instrument. Can't play it, but you can see if everything looks right.

yeah I think you're right the imported file looked different from the original... take a look, the original is the one that says Sidon.

and also in the midi track it was the same...

3 hours ago, Nigel Mackay said:

Maybe the BPM is not being imported. Make sure that Cakewalk shows the same BPM as your notation software. If written at say 120BPM and Cakewalk is set to 30BPM then a chord would end up as an arpeggio.

Also check time signature. If Cakewalk is expecting more beats per measure then a whole note will end before the end of the measure.

 

Is this what you mean by bpm? If so it's the same they'r both 150... 

Also in the image it shows what I mean. they were supposed to go all the way since the 3 notes are whole yet they  end soon and with different timings...

13 hours ago, rsinger said:

I'm not familiar with Spitfire's Soft Piano VST, but from my experience pianos don't necessarily sustain notes. They have a sustain pedal that you need to hold down. EPs may not sustain notes. The fact that you have a whole note doesn't mean that a particular instrument will sound that long. What happens depends both on the real instrument and how it's implemented in a given vst. If you have a MIDI controller what happens when you hold down a key?

Yes I did think about that possibility... but in previous project it sustained the note, and it works when I press the midi controler.

Hey What's up?

So I exported a midi file from a music notation software. I went to Cakewalk, opened Spitfire's Soft Piano VST and imported that same midi file to it. When I started listening to it I noticed that whole notes were always cut earlier than they were supposed to... I also noticed that when I had chords the different notes would end in a sequence and not together... Ex: I've a chord with 3 notes that is supposed to last for 4 measures. The first note ends in half a measure the other one in 1 measure and the other one in 1 measure and a half... Can someone Help Me?

It's happening with other vsts to I think It's something with the DAW itself...

I checked again and in the end there is a part where there is a whole note and it played correctly... I 'm starting to get confused here...

35 minutes ago, Matthew Sorrels said:

The DLL must be in the directory above the samples.  Just like it is in the zip file.  You put the DLL into the same dir as the samples and that won't work.  Move it up one directory (leave the samples the .mse file in Iowq Piano - 64.instruments, move the DLL)

IT WORKED! thank you so much!

1 hour ago, HIBI said:

@António Brites
Iowa Piano - 64.mse file must be located in a sub folder it's named Iowa Piano - 64.instruments, I think.
So make Iowa Piano - 64.instruments folder there and then move Iowa Piano - 64.mse file into that folder.

Aight i did but it didn't work still...

On 11/4/2019 at 5:51 PM, Robert Bone said:

If you right-click on the Cakewalk launch icon, one of the options you will then see, is Run As Administrator, and when you click that, you will then see a message pop up, asking if you want to allow that program (Cakewalk) to make changes, (or some text like that), and when you click OK, Cakewalk will be launched with the elevated execution privileges that come with Run As Administrator.

Give that a shot - for whichever pain in the ' ' you were referring to.

As far as your Iowa piano not finding its presets, I just downloaded the zip file for it, copied the contents of the zip folder (a folder named 'Iowa Piano - 64.instruments' and a 64-bit dll called 'Iowa Piano - 64.dll', into a folder I created, called Iowa Piano, in  C:\\Program Files\VST64 (all my 64-bit VST2 plugins are in here), then launched Cakewalk.  Cakewalk scanned the new plugin, and it became available in the Uncategorized category. 

When I loaded it into the project, it opened up to the Iowa Piano instrument, and works just fine.

SO, as also mentioned in the above post, bi @HIBI, you need to have BOTH that sub-folder and the dll itself, copied into your VST Plugins folder - I suggest you put them into a folder called Iowa Piano, that you create in your VST Plugins folder, like I did.  Works like a champ.

If you need to download the Iowa Piano again, here is a link to it, which is where I got it: http://www.vst4free.com/free_vst.php?plugin=Iowa_Piano&id=2294

Bob Bone

On 11/4/2019 at 5:51 PM, Robert Bone said:

If you right-click on the Cakewalk launch icon, one of the options you will then see, is Run As Administrator, and when you click that, you will then see a message pop up, asking if you want to allow that program (Cakewalk) to make changes, (or some text like that), and when you click OK, Cakewalk will be launched with the elevated execution privileges that come with Run As Administrator.

Give that a shot - for whichever pain in the ' ' you were referring to.

As far as your Iowa piano not finding its presets, I just downloaded the zip file for it, copied the contents of the zip folder (a folder named 'Iowa Piano - 64.instruments' and a 64-bit dll called 'Iowa Piano - 64.dll', into a folder I created, called Iowa Piano, in  C:\\Program Files\VST64 (all my 64-bit VST2 plugins are in here), then launched Cakewalk.  Cakewalk scanned the new plugin, and it became available in the Uncategorized category. 

When I loaded it into the project, it opened up to the Iowa Piano instrument, and works just fine.

SO, as also mentioned in the above post, bi @HIBI, you need to have BOTH that sub-folder and the dll itself, copied into your VST Plugins folder - I suggest you put them into a folder called Iowa Piano, that you create in your VST Plugins folder, like I did.  Works like a champ.

If you need to download the Iowa Piano again, here is a link to it, which is where I got it: http://www.vst4free.com/free_vst.php?plugin=Iowa_Piano&id=2294

Bob Bone

3 minutes ago, António Brites said:

yes! in the beggining i thougth that was the problem but i don't think it is...

On 11/4/2019 at 3:25 PM, HIBI said:

@António Brites Seems missing "Iowa Piano - 64.mse" file.
Is there "Iowa Piano - 64.instruments" folder it contains "Iowa Piano - 64.mse" in "Iowa_Piano_-_64" folder which installed (copied) to plugin folder?

yes! in the beggining i thougth that was the problem but i don't think it is...

hey!

I recently intalled a couple of grand piano vst s. Cakewalk found them but whenever i try to enter the instrument itself this happens... can someone please help me?