copy/paste problem

SteveMTNO wrote on 9/9/2020, 5:18 PM

I'm having a problem copy/pasting content and having the markers carry thru when pasting in SF14Pro.. This used to work, now it isn't.

Previously, I could work on a region, then paste it into another file - bringing all of the markers along with it.

Now, when I paste the content into the new file, the markers get left behind. How can I change this back to the way it was?

Thanks in advance..

SteveMTNO

Comments

rraud wrote on 9/10/2020, 12:41 PM

Are you using the latest build (111) ? I do not recall an issue with previous Pro 14 builds. I will investigate this behavior with build 111 ASAP.

You can try a cache clean and defaults reset. (File menu)

SteveMTNO wrote on 9/10/2020, 12:56 PM

Are you using the latest build (111) ? I do not recall an issue with previous Pro 14 builds. I will investigate this behavior with build 111 ASAP.

You can try a cache clean and defaults reset. (File menu)

Yes, I'm using build 111. If I reset defaults, won't that get rid of any customizations that I've made?

 

rraud wrote on 9/10/2020, 1:21 PM

Yes some, though the custom keyboard <.ini> and window layouts <.ForgeWindowLayout> can be copied to another location and pasted back in. AppData/Roaming/Magix/Sound Forge/14.0 Plug-in presets should remain intact.

FYI, If you are not already aware, there was a "Multi-instancing default" change in build 111 that can cause a workflow issue. I am not sure this would affect Makers/Regions though. See this thread:
https://www.magix.info/us/forum/sound-forge-opening-multiple-instances-instead-of-multiple-windows--1252594/

rraud wrote on 9/12/2020, 10:01 AM

Hi @SteveMTNO, I cannot duplicate that behavior. Markers and regions paste into a new or existing files along with the audio data.

What file types are being used? Some formats cannot write the metadata, but it should paste from within SF. So if you working with lossy file types. MP3, AAC, ect., try enabling, "Always proxy compressed formats" in "Options> Preferences> General".
Otherwise, I do not recall a setting that would affect this either. If the reset does not help... reinstall.

SteveMTNO wrote on 9/12/2020, 11:32 AM

I'm using .wav files.

If I open a file that has markers/regions, then hit ctrl-c followed by ctrl-e, it pastes the content from the clipboard - minus the regions/markers..

I made the internal settings change mentioned in the "multiple instances" link above. No change.

I also selected the "Always proxy compressed formats" option. That didn't make any difference either.

Not sure what else to do, aside from restoring default settings (which I really don't want to do unless I have to) and/or reinstalling..

rraud wrote on 9/12/2020, 1:11 PM

Ctrl+E and Ctrl+V as well and the other paste methods, paste in the markers/regions and audio.

You could try a repair/reinstall which should retain your customized settings,

SteveMTNO wrote on 9/12/2020, 1:32 PM

I just did an uninstall and reinstall - same thing.

There must be a setting somewhere that's keeping this from working...

SteveMTNO wrote on 9/12/2020, 2:02 PM

Just did a system restore and that got the copy/paste functionality back. Nothing else worked...

rraud wrote on 9/12/2020, 3:10 PM

The one basic thing I did not think of ..duh.

SteveMTNO wrote on 11/26/2020, 10:51 AM

This behavior is back. I updated to the newest build.

Frustrating, because I use this in my workflow a lot.

SteveMTNO wrote on 12/12/2020, 11:38 AM

Just tried this again, same results.

Here's what I'm doing:

Open a 24/192 wav file
add markers
ctrl-a (select all), ctrl-e (create new file)

But instead of the markers showing up in the new file, I get a new file with no markers.

Hopefully someone can help me with this...

Thanks,
SteveMTNO

dnulf wrote on 12/15/2020, 5:19 PM

Just tried this again, same results.

Here's what I'm doing:

Open a 24/192 wav file
add markers
ctrl-a (select all), ctrl-e (create new file)

But instead of the markers showing up in the new file, I get a new file with no markers.

Hopefully someone can help me with this...

Thanks,
SteveMTNO

ctrl-a (select all), ctrl-c (copy selection), ctrl-e (paste to new file)

SteveMTNO wrote on 12/15/2020, 6:11 PM

Sorry - that's the same thing I'm doing. I left out the middle step (ctrl-c).

Just tried it again to confirm. Same result.

rraud wrote on 12/16/2020, 10:36 AM

Uninstall*/reinstall and/or contact Magix Sound Forge Tech Support

* I recommend uninstalling using a third-party uninstaller that can remove left-over registry entries and other pertinent data the OS uninstall leaves behind, which in usually the root of recurring issues
Revo Uninstall and Geek Uninstall are two that have pro and freeware versions.



 

SteveMTNO wrote on 12/16/2020, 11:54 AM

I just opened a ticket. I really don't want to have to uninstall/reinstall and lose all my settings (again)...

rraud wrote on 12/16/2020, 12:47 PM

I just opened a ticket. I really don't want to have to uninstall/reinstall and lose all my settings (again)...


I can certainly understand that. Good luck and please keep us updated.

SteveMTNO wrote on 12/16/2020, 1:20 PM

will do

SteveMTNO wrote on 12/18/2020, 12:34 PM

Here's the reply I got from Magix support yesterday:

Hi Steve,

Thank you for contacting us.  Yes, this is indeed a confirmed bug...and we apologize for the inconvenience of that.  It was a side effect of update 111, just as you suspected, and the developers are working on that at the moment.  It may take some time to fix it, as over half of our team is out due to corona, so I apologize for that as well...these are crazy times.  But what I will do is this:  I'm sending you build 65...that was the last build number released before version 111.  It is too big to attach to this email, so I will send it via WeTransfer.  Please be on the lookout for a WeTransfer notice (if you don't see it in your inbox, you may need to check your spam folder).  You will need to uninstall the version you have before installing the earlier version, so please be aware of that.  Also, it will then ask you if you want to update to a later version, but of course, you should click No, as that would only bring you back to the version with the bug.  I hope this is helpful for you, and the developers will continue to work on a fix for this as quickly as they can given the circumstances.  I thank you for your time and patience, and hope you have a great day!   
--
Best regards,

MAGIX Software GmbH

-------------------------------------------------------------------------------

-- I have not received the build 65 file yet...

SteveMTNO wrote on 12/22/2020, 1:26 PM

I received the build 65 file - didn't make any difference.

I wrote back to Magix support and told them. This is the reply I received:

 

"I have just heard from a developer that they are now aware of this and they are working on a fix for it...the problem is that they are really stretched thin because several of the developers are out due to covid so it's thrown a monkey wrench into the system...they are working on it though and will release a patch to fix it as soon as they can. "