Troubleshooting WINE (Melodyne specifically)
Moderators: MattKingUSA, khz
-
wolftune
- Established Member
- Posts: 1354
- Joined: Fri Feb 24, 2012 7:40 pm
- Location: Portland, OR
- Been thanked: 3 times
- Contact:
Troubleshooting WINE (Melodyne specifically)
Ok, I decided not to give up after all.
According to somebody's test, they actually got Melodyne working in Linux:
http://appdb.winehq.org/objectManager.p ... ngId=38035
But like this guy: http://forum.winehq.org/viewtopic.php?p ... b17a0dc4f8
I get a crash at the beginning.
I got farther than when I tried before. I was able to register successfully, and things look promising, but some crash happens after the load screen finishes and the app starts. Apparently, the guy in the forum didn't actually post a bug because I couldn't find any bug report listed anywhere.
WINE says not to post bugs unless I've tested with the latest development version. But I just have my one Linux system. Do I have to (or ought I) set up a whole additional Linux installation for testing purposes? Or is there an easy enough way to install the latest development version of WINE without losing anything and still able to fully return to my previous setup? Or no?
Is it worth trying Crossover or other options?
Being able to get just this working could mean I really could just switch mainly to Linux…
For reference, I'm running KXStudio 12.04.
Anyway, I guess I'm feeling more optimistic that the goals I have aren't impossible. But I'm wondering how much to be proactive, how much to be patient, and how to go about things.
All help is greatly appreciated. Thanks.
P.S. Obviously I'd ideally like a Linux-native FLOSS program effectively replacing Melodyne, but there isn't even anything comparable in any way right now.
According to somebody's test, they actually got Melodyne working in Linux:
http://appdb.winehq.org/objectManager.p ... ngId=38035
But like this guy: http://forum.winehq.org/viewtopic.php?p ... b17a0dc4f8
I get a crash at the beginning.
I got farther than when I tried before. I was able to register successfully, and things look promising, but some crash happens after the load screen finishes and the app starts. Apparently, the guy in the forum didn't actually post a bug because I couldn't find any bug report listed anywhere.
WINE says not to post bugs unless I've tested with the latest development version. But I just have my one Linux system. Do I have to (or ought I) set up a whole additional Linux installation for testing purposes? Or is there an easy enough way to install the latest development version of WINE without losing anything and still able to fully return to my previous setup? Or no?
Is it worth trying Crossover or other options?
Being able to get just this working could mean I really could just switch mainly to Linux…
For reference, I'm running KXStudio 12.04.
Anyway, I guess I'm feeling more optimistic that the goals I have aren't impossible. But I'm wondering how much to be proactive, how much to be patient, and how to go about things.
All help is greatly appreciated. Thanks.
P.S. Obviously I'd ideally like a Linux-native FLOSS program effectively replacing Melodyne, but there isn't even anything comparable in any way right now.
Last edited by wolftune on Wed Aug 01, 2012 6:38 pm, edited 2 times in total.
-
wolftune
- Established Member
- Posts: 1354
- Joined: Fri Feb 24, 2012 7:40 pm
- Location: Portland, OR
- Been thanked: 3 times
- Contact:
Re: Troubleshooting WINE (Melodyne specifically)
No, Melodyne is far more than just pitch switching.
Melodyne is so different from zita-at1 that there is no comparison.
It's barely worth discussing, but:
Zita is limited to just brute correcting pitch to only tempered tuning with no consideration of formant or anything else.
Melodyne is an extremely powerful tool with a full visual editing platform, tuning control to the cent, control of vibrato, glides, timing, formants, and much much more. It is a fine-detail professional editing tool.
I use Melodyne to do vocal editing with careful control for independence of attacks vs sustained parts of notes, control over degree of natural vibrato, timing editing, and tuning for Just Intonation and more.
Anyway, re: post by falkTX,
If I go with the Ubuntu-Wine PPA and install on my current system, do I risk messing up my current WINE install with no easy way to revert? If not, I'm happy to test things. I just want to make sure I don't lose what is already working and set up well… Thanks for the advice!
Melodyne is so different from zita-at1 that there is no comparison.
It's barely worth discussing, but:
Zita is limited to just brute correcting pitch to only tempered tuning with no consideration of formant or anything else.
Melodyne is an extremely powerful tool with a full visual editing platform, tuning control to the cent, control of vibrato, glides, timing, formants, and much much more. It is a fine-detail professional editing tool.
I use Melodyne to do vocal editing with careful control for independence of attacks vs sustained parts of notes, control over degree of natural vibrato, timing editing, and tuning for Just Intonation and more.
Anyway, re: post by falkTX,
If I go with the Ubuntu-Wine PPA and install on my current system, do I risk messing up my current WINE install with no easy way to revert? If not, I'm happy to test things. I just want to make sure I don't lose what is already working and set up well… Thanks for the advice!
-
wolftune
- Established Member
- Posts: 1354
- Joined: Fri Feb 24, 2012 7:40 pm
- Location: Portland, OR
- Been thanked: 3 times
- Contact:
Re: Troubleshooting WINE
Update:
Now everything in WINE is messed up! But I didn't mess it up by trying this. I found out BEFORE trying the development version that the programs that had worked before (at least certainly were working with WINE 1.4 and Ubuntu 11.10) are having the same fatal errors.
Here's what happens even with a program that worked flawlessly before: and on one trial I got this: Here's the error report:
Basically the same error happened when I was in WINE 1.4.1
And I tried to uninstall and reinstall WINE stuff, purging everything I could…
Some programs work in WINE still. One that used to be flawless now has glitchy sound but some sound. Other programs consistently crash, even though they worked before. There is nothing about my WINE setup that I think is special or matters. I'm at the point of wanting to just start fresh if necessary. I just want WINE working, at least as well as before. And I think that if I figure out what is going wrong, maybe Melodyne will work. It may be that Melodyne isn't the problem really. Or maybe trying Melodyne messed something up…
Some clarifications:
* I noticed at some point, BEFORE I had installed the WINE development version, that my apps, including the dysfunctioning Melodyne, were all gone from my WINE install, although I didn't uninstall them.
* Winecfg works perfectly still.
* I'm testing (and getting this crash) with a portable .exe app that doesn't require installation.
* I tried reinstalling software that worked before (Canta from http://singintune.org/) and it runs correctly, interface works etc. — but when when I try to quit nothing happens, and it hangs and has to be forced closed. That did not happen before…
Now everything in WINE is messed up! But I didn't mess it up by trying this. I found out BEFORE trying the development version that the programs that had worked before (at least certainly were working with WINE 1.4 and Ubuntu 11.10) are having the same fatal errors.
Here's what happens even with a program that worked flawlessly before: and on one trial I got this: Here's the error report:
Code: Select all
Unhandled exception: page fault on read access to 0x00000018 in 32-bit code (0x004b0f56).
Register dump:
CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b
EIP:004b0f56 ESP:0033efa0 EBP:0033efa0 EFLAGS:00210246( R- -- I Z- -P- )
EAX:00000000 EBX:00000000 ECX:01aec6d0 EDX:01aec6d0
ESI:00000000 EDI:01aa9418
Stack dump:
0x0033efa0: 0033efd0 0091d05a 00000000 00000000
0x0033efb0: 0033efb0 004d1340 01aec6d0 0000ef00
0x0033efc0: 00000000 01aec6d0 00000000 0033efd8
0x0033efd0: 0033f258 00a9c8ca 00000000 00000000
0x0033efe0: 00000000 00000000 0033efe0 00796000
0x0033eff0: 7bca7ff4 00000000 7bc47503 00000000
Backtrace:
=>0 0x004b0f56 in tpxe-1r6x1 (+0xb0f56) (0x0033efa0)
1 0x0091d05a (0x0033efd0)
2 0x00a9c8ca (0x0033f258)
3 0x00aa7072 (0x0033f5ec)
4 0x00aa9165 (0x0033f60c)
5 0x00aa8dc5 (0x0033f8c4)
6 0x00a98d57 (0x0033f964)
7 0x004e61b0 in tpxe-1r6x1 (+0xe61af) (0x0033f988)
8 0x00947065 (0x0033fa14)
9 0x004e7f54 in tpxe-1r6x1 (+0xe7f53) (0x0033fa2c)
10 0x004e61f6 in tpxe-1r6x1 (+0xe61f5) (0x0033fa74)
11 0x008b6c6a (0x0033faac)
12 0x008b0261 (0x0033fae4)
13 0x008b0402 (0x0033faf8)
14 0x004e5f6c in tpxe-1r6x1 (+0xe5f6b) (0x0033fb04)
15 0x008b7651 (0x0033fb24)
16 0x008b04c2 (0x0033fb64)
17 0x008b0024 (0x0033fb70)
18 0x0046c37c in tpxe-1r6x1 (+0x6c37b) (0x0033fdd0)
19 0x004e78ca in tpxe-1r6x1 (+0xe78c9) (0x0033fdd8)
20 0x0055d319 in tpxe-1r6x1 (+0x15d318) (0x0033fe70)
21 0x7b85b91c call_process_entry+0xb() in kernel32 (0x0033fe88)
22 0x7b85cb8f in kernel32 (+0x4cb8e) (0x0033fec8)
23 0x7bc71fc0 call_thread_func_wrapper+0xb() in ntdll (0x0033fed8)
24 0x7bc74a9d call_thread_func+0x7c() in ntdll (0x0033ffa8)
25 0x7bc71f9e RtlRaiseException+0x21() in ntdll (0x0033ffc8)
26 0x7bc4a15e call_dll_entry_point+0x61d() in ntdll (0x0033ffe8)
0x004b0f56: cmpl $0,0x18(%eax)
Modules:
Module Address Debug info Name (111 modules)
PE 350000- 360000 Deferred mbsregistrationplugin16151
PE 3d0000- 3ea000 Deferred browser plugin
PE 400000- 686000 Export tpxe-1r6x1
PE 1e40000- 1e52000 Deferred internet encodings
PE 1f70000- 1f8a000 Deferred md5
PE 21b0000- 21ca000 Deferred shell
PE 22e0000- 22f8000 Deferred mbswindowsmidiplugin16151
PE 10000000-10024000 Deferred appearance pak
PE 652c0000-65f0b000 Deferred rbscript
ELF 7b800000-7ba30000 Dwarf kernel32<elf>
\-PE 7b810000-7ba30000 \ kernel32
ELF 7bc00000-7bcc4000 Dwarf ntdll<elf>
\-PE 7bc10000-7bcc4000 \ ntdll
ELF 7bf00000-7bf04000 Deferred <wine-loader>
ELF 7d7b8000-7d846000 Deferred msvcrt<elf>
\-PE 7d7d0000-7d846000 \ msvcrt
ELF 7d846000-7d85a000 Deferred psapi<elf>
\-PE 7d850000-7d85a000 \ psapi
ELF 7d85a000-7d8b8000 Deferred dbghelp<elf>
\-PE 7d860000-7d8b8000 \ dbghelp
ELF 7d8b8000-7d8d2000 Deferred imagehlp<elf>
\-PE 7d8c0000-7d8d2000 \ imagehlp
ELF 7d8d2000-7d904000 Deferred ws2_32<elf>
\-PE 7d8e0000-7d904000 \ ws2_32
ELF 7d904000-7d91f000 Deferred wsock32<elf>
\-PE 7d910000-7d91f000 \ wsock32
ELF 7d91f000-7d928000 Deferred librt.so.1
ELF 7d928000-7d92d000 Deferred libgpg-error.so.0
ELF 7d92d000-7d945000 Deferred libresolv.so.2
ELF 7d945000-7d949000 Deferred libkeyutils.so.1
ELF 7d949000-7d992000 Deferred libdbus-1.so.3
ELF 7d992000-7d9a4000 Deferred libp11-kit.so.0
ELF 7d9a4000-7da29000 Deferred libgcrypt.so.11
ELF 7da29000-7da3b000 Deferred libtasn1.so.3
ELF 7da3b000-7da44000 Deferred libkrb5support.so.0
ELF 7da44000-7da49000 Deferred libcom_err.so.2
ELF 7da49000-7da71000 Deferred libk5crypto.so.3
ELF 7da71000-7db40000 Deferred libkrb5.so.3
ELF 7db40000-7db52000 Deferred libavahi-client.so.3
ELF 7db52000-7db60000 Deferred libavahi-common.so.3
ELF 7db60000-7dc24000 Deferred libgnutls.so.26
ELF 7dc24000-7dc62000 Deferred libgssapi_krb5.so.2
ELF 7dc62000-7dcb5000 Deferred libcups.so.2
ELF 7dcbd000-7dcd0000 Deferred gnome-keyring-pkcs11.so
ELF 7dce6000-7dd1a000 Deferred uxtheme<elf>
\-PE 7dcf0000-7dd1a000 \ uxtheme
ELF 7dd1a000-7dd20000 Deferred libxfixes.so.3
ELF 7dd20000-7dd2b000 Deferred libxcursor.so.1
ELF 7de60000-7de8a000 Deferred libexpat.so.1
ELF 7de8a000-7debe000 Deferred libfontconfig.so.1
ELF 7dfbe000-7dfce000 Deferred libxi.so.6
ELF 7dfce000-7dfd2000 Deferred libxcomposite.so.1
ELF 7dfd2000-7dfdb000 Deferred libxrandr.so.2
ELF 7dfdb000-7dfe5000 Deferred libxrender.so.1
ELF 7dfe5000-7dfeb000 Deferred libxxf86vm.so.1
ELF 7dfeb000-7e00d000 Deferred imm32<elf>
\-PE 7dff0000-7e00d000 \ imm32
ELF 7e00d000-7e02e000 Deferred libxcb.so.1
ELF 7e02e000-7e162000 Deferred libx11.so.6
ELF 7e162000-7e1e9000 Deferred winex11<elf>
\-PE 7e170000-7e1e9000 \ winex11
ELF 7e1e9000-7e283000 Deferred libfreetype.so.6
ELF 7e283000-7e392000 Deferred oleaut32<elf>
\-PE 7e2a0000-7e392000 \ oleaut32
ELF 7e3b4000-7e3b8000 Deferred libxinerama.so.1
ELF 7e3b8000-7e3bf000 Deferred libxdmcp.so.6
ELF 7e3bf000-7e3d9000 Deferred libice.so.6
ELF 7e3d9000-7e3eb000 Deferred libxext.so.6
ELF 7e406000-7e41c000 Deferred libz.so.1
ELF 7e41d000-7e421000 Deferred libxau.so.6
ELF 7e421000-7e427000 Deferred libuuid.so.1
ELF 7e427000-7e430000 Deferred libsm.so.6
ELF 7e437000-7e474000 Deferred winspool<elf>
\-PE 7e440000-7e474000 \ winspool
ELF 7e474000-7e4de000 Deferred shlwapi<elf>
\-PE 7e480000-7e4de000 \ shlwapi
ELF 7e4de000-7e6f2000 Deferred shell32<elf>
\-PE 7e4f0000-7e6f2000 \ shell32
ELF 7e6f2000-7e7d1000 Deferred comdlg32<elf>
\-PE 7e700000-7e7d1000 \ comdlg32
ELF 7e7d1000-7e7f3000 Deferred iphlpapi<elf>
\-PE 7e7e0000-7e7f3000 \ iphlpapi
ELF 7e7f3000-7e81b000 Deferred msacm32<elf>
\-PE 7e800000-7e81b000 \ msacm32
ELF 7e81b000-7e891000 Deferred rpcrt4<elf>
\-PE 7e830000-7e891000 \ rpcrt4
ELF 7e891000-7e999000 Deferred ole32<elf>
\-PE 7e8b0000-7e999000 \ ole32
ELF 7e999000-7ea46000 Deferred winmm<elf>
\-PE 7e9a0000-7ea46000 \ winmm
ELF 7ea46000-7eaa8000 Deferred advapi32<elf>
\-PE 7ea50000-7eaa8000 \ advapi32
ELF 7eaa8000-7eb67000 Deferred gdi32<elf>
\-PE 7eab0000-7eb67000 \ gdi32
ELF 7eb67000-7eca7000 Deferred user32<elf>
\-PE 7eb80000-7eca7000 \ user32
ELF 7eca7000-7eda0000 Deferred comctl32<elf>
\-PE 7ecb0000-7eda0000 \ comctl32
ELF 7eda0000-7edad000 Deferred libnss_files.so.2
ELF 7edad000-7edb9000 Deferred libnss_nis.so.2
ELF 7efb9000-7efe5000 Deferred libm.so.6
ELF 7efe6000-7f000000 Deferred libnsl.so.1
ELF b7471000-b747a000 Deferred libnss_compat.so.2
ELF b747b000-b7480000 Deferred libdl.so.2
ELF b7480000-b7625000 Deferred libc.so.6
ELF b7626000-b7641000 Deferred libpthread.so.0
ELF b7643000-b765c000 Deferred version<elf>
\-PE b7650000-b765c000 \ version
ELF b765c000-b779e000 Dwarf libwine.so.1
ELF b77a0000-b77c2000 Deferred ld-linux.so.2
ELF b77c2000-b77c3000 Deferred [vdso].so
Threads:
process tid prio (all id:s are in hex)
0000000e services.exe
0000001f 0
0000001e 0
00000015 0
00000010 0
0000000f 0
00000012 winedevice.exe
0000001c 0
00000019 0
00000014 0
00000013 0
0000001a plugplay.exe
00000020 0
0000001d 0
0000001b 0
00000021 explorer.exe
00000022 0
00000023 (D) Z:\home\aaron\downloadedprograms\H-Pi\TPXE-WIN\TPXE-1r6x1.exe
00000026 0
00000025 0
00000024 0 <==
System information:
Wine build: wine-1.5.9
Platform: i386
Host system: Linux
Host version: 3.2.0-27-generic-pae
And I tried to uninstall and reinstall WINE stuff, purging everything I could…
Some programs work in WINE still. One that used to be flawless now has glitchy sound but some sound. Other programs consistently crash, even though they worked before. There is nothing about my WINE setup that I think is special or matters. I'm at the point of wanting to just start fresh if necessary. I just want WINE working, at least as well as before. And I think that if I figure out what is going wrong, maybe Melodyne will work. It may be that Melodyne isn't the problem really. Or maybe trying Melodyne messed something up…
Some clarifications:
* I noticed at some point, BEFORE I had installed the WINE development version, that my apps, including the dysfunctioning Melodyne, were all gone from my WINE install, although I didn't uninstall them.
* Winecfg works perfectly still.
* I'm testing (and getting this crash) with a portable .exe app that doesn't require installation.
* I tried reinstalling software that worked before (Canta from http://singintune.org/) and it runs correctly, interface works etc. — but when when I try to quit nothing happens, and it hangs and has to be forced closed. That did not happen before…
-
wolftune
- Established Member
- Posts: 1354
- Joined: Fri Feb 24, 2012 7:40 pm
- Location: Portland, OR
- Been thanked: 3 times
- Contact:
Re: Troubleshooting WINE
Ok, update:
I tried a lot of things, nothing seemed to work.
Then I tested some other programs and was surprised that they worked when they were basically the same as other that failed. Turns out WINE 1.4 ran the same file when it was in my downloads folder, but the new version requires it to be in the c drive Program Files.
Question is: how do I add a link so I can access the file easily? It isn't showing in WINE apps in the launcher. And when I run it from the c drive it works, but when I made a linked file in my documents folder, it had a Runtime error (even though I thought it would be identical!)
I can see the .exe file in my recently used documents, but I can't figure out how to make a link or launcher or command or something so I can run it in the future…
Finally, since I got a similar error running Melodyne as I got with this other program, maybe the same solution could work? Maybe it just needs files to be in certain places that are not currently right??
I tried a lot of things, nothing seemed to work.
Then I tested some other programs and was surprised that they worked when they were basically the same as other that failed. Turns out WINE 1.4 ran the same file when it was in my downloads folder, but the new version requires it to be in the c drive Program Files.
Question is: how do I add a link so I can access the file easily? It isn't showing in WINE apps in the launcher. And when I run it from the c drive it works, but when I made a linked file in my documents folder, it had a Runtime error (even though I thought it would be identical!)
I can see the .exe file in my recently used documents, but I can't figure out how to make a link or launcher or command or something so I can run it in the future…
Finally, since I got a similar error running Melodyne as I got with this other program, maybe the same solution could work? Maybe it just needs files to be in certain places that are not currently right??
-
wolftune
- Established Member
- Posts: 1354
- Joined: Fri Feb 24, 2012 7:40 pm
- Location: Portland, OR
- Been thanked: 3 times
- Contact:
Re: Troubleshooting WINE
Thanks! Now the old programs work portably again.
Everything works that ever worked.
Melodyne still crashes the same way though. Is there any change reinstalling Melodyne after doing the drive auto-detect would make a difference?
I'm still be grateful for whatever help gets Melodyne to actually work. It's about the one thing that really keeps me from doing most of my audio work in Linux…
Everything works that ever worked.
Melodyne still crashes the same way though. Is there any change reinstalling Melodyne after doing the drive auto-detect would make a difference?
I'm still be grateful for whatever help gets Melodyne to actually work. It's about the one thing that really keeps me from doing most of my audio work in Linux…
-
wolftune
- Established Member
- Posts: 1354
- Joined: Fri Feb 24, 2012 7:40 pm
- Location: Portland, OR
- Been thanked: 3 times
- Contact:
Re: Troubleshooting WINE (Melodyne specifically)
Another Melodyne update:
Someone from Crossover said they successfully ran the demo. Seems it's doable and there's something wrong with my system.
Same guy said: "I also noticed that installing the "Platform SDK Redistributable: GDI+" package into the same bottle solved some problems with non-existant text and odd button rendering, though the application ran slower after I did so."
And I did some more searching and found some other error logs from Melodyne:
one error: "no minidump @ C:/users/aaron/Temp/gnminidump.dmp"
And from a Melodyne log file:
Maybe the PACE system is part of the problem? PACE makes the iLok, and Melodyne has an option to use it, but it does NOT require the iLok, it can use a different copy-protection thing instead, which is what I do.
Anyway, the fact that the demo runs for others indicates that it should be doable!
Any of these hints add anything?
Someone from Crossover said they successfully ran the demo. Seems it's doable and there's something wrong with my system.
Same guy said: "I also noticed that installing the "Platform SDK Redistributable: GDI+" package into the same bottle solved some problems with non-existant text and odd button rendering, though the application ran slower after I did so."
And I did some more searching and found some other error logs from Melodyne:
one error: "no minidump @ C:/users/aaron/Temp/gnminidump.dmp"
And from a Melodyne log file:
Code: Select all
********** 01.08.2012 17:04
Cannot open file C:\Program Files\Celemony\Melodyne.3.2\Melodyne.pref (Lasterror 2)
********** 01.08.2012 17:04
Cannot open file H:\Melodyne.pref (Lasterror 2)
********** 01.08.2012 17:04
Could not open file 'C:\Program Files\Celemony\Melodyne.3.2\Melodyne.pref' (Lasterror 0)
********** 01.08.2012 17:04
Realexception GNFileException Cannot open Melodyne.pref.
********** 01.08.2012 17:04
PlugIn found.
********** 01.08.2012 17:04
Creating PlugIn instance...
********** 01.08.2012 17:04
... PlugIn instance created.
********** 01.08.2012 17:04
Celemony PlugIn Test succeeded.
********** 01.08.2012 17:04
DirectSound: Hardware format is: 2 channels of 16 bit at 44100 Hz
********** 01.08.2012 17:04
DirectSound: Hardware format is: 2 channels of 16 bit at 44100 Hz
********** 01.08.2012 17:04
PACEOpenProtectionFromBundle failed with error:4105
********** 01.08.2012 17:04
PACEOpenProtectionFromBundle failed with error:4105
********** 01.08.2012 17:04
PACEOpenProtectionFromBundle failed with error:4105
Anyway, the fact that the demo runs for others indicates that it should be doable!
Any of these hints add anything?
-
wolftune
- Established Member
- Posts: 1354
- Joined: Fri Feb 24, 2012 7:40 pm
- Location: Portland, OR
- Been thanked: 3 times
- Contact:
Re: Troubleshooting WINE (Melodyne specifically)
No I am not using an iLok! I have a legal ownership that uses a net-based authorization and DOES NOT require iLok. iLok is just an option that they include for those who choose it.
I expect that iLok would fail. But I'm NOT using the iLok option.
And to be clear, when I first ran Melodyne, it SUCCESSFULLY ran the over-the-internet authorization program, and my authorization of this machine is listed with my account on their website.
When I open Melodyne, all the start up works, and it crashes when it opens the main screen.
So it is all authorized, and that part I thought would be fine.
I guess I need to try a krack… just to do what is already legal and paid for? I suppose that's worth trying. But the authorization didn't seem to be the problem.
I expect that iLok would fail. But I'm NOT using the iLok option.
And to be clear, when I first ran Melodyne, it SUCCESSFULLY ran the over-the-internet authorization program, and my authorization of this machine is listed with my account on their website.
When I open Melodyne, all the start up works, and it crashes when it opens the main screen.
So it is all authorized, and that part I thought would be fine.
I guess I need to try a krack… just to do what is already legal and paid for? I suppose that's worth trying. But the authorization didn't seem to be the problem.
-
wolftune
- Established Member
- Posts: 1354
- Joined: Fri Feb 24, 2012 7:40 pm
- Location: Portland, OR
- Been thanked: 3 times
- Contact:
Re: Troubleshooting WINE (Melodyne specifically)
OK, I tried a krack version I found online. All it was is a keygen licensing thing though along with the regular software. All it did was register the program. Again, I am not using iLok, that shouldn't be the issue, and the program successfully registered. I really think the problem has nothing to do with authorization. And anyway, other people report it working…
At this point, I'm guessing that the main problem has to do with the crash that Melodyne itself is reporting
Anyone know what that means?
At this point, I'm guessing that the main problem has to do with the crash that Melodyne itself is reporting
Code: Select all
no minidump @ C:/users/aaron/Temp/gnminidump.dmpRe: Troubleshooting WINE (Melodyne specifically)
I know nothing about Melodyne, but it appears to be looking for a file C:/users/aaron/Temp/gnminidump.dmp.
If you have Melodyne working on another platform you could look for a file of the same name and copy to the equivalent wine location which would likely be ~/.wine/drive_c/users/aaron/Temp/gnminidump.dmp. Or maybe his is a file Melodyne wants to create, but this directory does not exist on your system, in which case create it. Or contact some Melodyne forum or help to find out what this file is used for which might add some insight.
If you have Melodyne working on another platform you could look for a file of the same name and copy to the equivalent wine location which would likely be ~/.wine/drive_c/users/aaron/Temp/gnminidump.dmp. Or maybe his is a file Melodyne wants to create, but this directory does not exist on your system, in which case create it. Or contact some Melodyne forum or help to find out what this file is used for which might add some insight.
-
wolftune
- Established Member
- Posts: 1354
- Joined: Fri Feb 24, 2012 7:40 pm
- Location: Portland, OR
- Been thanked: 3 times
- Contact:
Re: Troubleshooting WINE (Melodyne specifically)
Arg! I'm so confused and frustrated. I tried starting fresh to get Melodyne working again and now the other program TPXE is failing again! I thought that moving it to the programs folder solved it. Or that doing the winecfg to identify drives did it. It DID work just before!
So I've got two programs failing. And the error WINE gives is the same.
Did I have some winetricks thing set up? Does KXStudio DVD come with a WINE set up that is different from what I'd have if I just delete my prefix and start fresh?
I have this feeling that either I'm not successfully truly clearing everything to start fresh, or that there is something needing to be set or installed that I'm failing to do when I start fresh. I'd be grateful for any help about knowing that ALL wine stuff is truly gone or reset and then go from there…
I still don't know what the problem here is. And I'm not so sure the two programs are having the same problem. I'm pretty baffled.
varpa: I still like your suggestion, and I'll try that, but I want to get the program that WAS working fine back to working now!
So I've got two programs failing. And the error WINE gives is the same.
Did I have some winetricks thing set up? Does KXStudio DVD come with a WINE set up that is different from what I'd have if I just delete my prefix and start fresh?
I have this feeling that either I'm not successfully truly clearing everything to start fresh, or that there is something needing to be set or installed that I'm failing to do when I start fresh. I'd be grateful for any help about knowing that ALL wine stuff is truly gone or reset and then go from there…
I still don't know what the problem here is. And I'm not so sure the two programs are having the same problem. I'm pretty baffled.
varpa: I still like your suggestion, and I'll try that, but I want to get the program that WAS working fine back to working now!
-
wolftune
- Established Member
- Posts: 1354
- Joined: Fri Feb 24, 2012 7:40 pm
- Location: Portland, OR
- Been thanked: 3 times
- Contact:
Re: Troubleshooting WINE (Melodyne specifically)
Ok, thanks. when would I need to reregister wineasio?
-
wolftune
- Established Member
- Posts: 1354
- Joined: Fri Feb 24, 2012 7:40 pm
- Location: Portland, OR
- Been thanked: 3 times
- Contact:
Re: Troubleshooting WINE (Melodyne specifically)
And winetricks and whatever else? That's all totally clear when I delete the prefix?
I suppose I'll have to learn how to use winetricks for later troubleshooting.
Is there any chance that a Windows install program puts some file somewhere that persists even after deleting the prefix?
I suppose I'll have to learn how to use winetricks for later troubleshooting.
Is there any chance that a Windows install program puts some file somewhere that persists even after deleting the prefix?