Code editor crash on start
  • Lapin

    Hello,
    Code editor crash on start, when it try to scan for device
    Win Xp sp3, java & quicktime (downloaded today)

  • JayLivid

    Check out the beta version of our new web based editor http://www.lividserver.com/editor/editor.html

  • Lapin

    Doesn't work too

    I got an error message when i try to install jazz plugin "JazzControl.dll failed to register" (firefox)

  • Lapin

    Very nice !
    http://www.hostingpics.net/viewer.php?id=484581020113153614Screen.jpg
    Jazz plugins 1.1 installed via firefox

    I don't see the midi in menu
    it doesn't recognise the device (I Tried all midi input i have)

  • Peter
    I'm unclear on the result here: you tried to install and you got "JazzControl.dll failed to register", but somehow you got it install correctly? 
    You'll need to install Jazz Plugin 1.2: Download

    What is the firmware version on your code? Which code editor (standalone app) did you try? 


  • Lapin

    "somehow you got it install correctly"
    here (version 1.1)
    https://addons.mozilla.org/fr/firefox/addon/jazz-plugin/

    I know I need to install 1.2, but it doesn't work. (exactly the same result than with the 1.1 version)

    "What is the firmware version on your code"
    How can I know it ? (don't tell me it's with "Code editor" ...)

    "Which code editor (standalone app) did you try? "
    2.09
    2.08

    with Java 6 & 7 and quicktime 6 & 7 (lastest versions)






  • Lapin

    It's normal to see 2 midi (unnamed ...) inputs used by the Code in my sequencer ?

  • Peter

    XP unfortunately doesn't show the ports with their proper names - it just shows "USB-AUDIO" or something like that. There are 2 ports on the Code - one for the USB and one for the MIDI jacks.

    For the browser plug-in, you'll definitely need version 1.2. I'm curious if you can get the 1.2 version installed on Chrome? 
    Here's some other considerations:
    Quit all browsers and applications before installing the Jazz plugin.
    Make sure you don't have any other MIDI apps open when using the editor. Windows only allows one application to "bind" to a controller.
    Make sure that your OS is behaving correctly with MIDI. You can test the controller with MIDIOX http://www.midiox.com

  • Lapin

    I'm curious if you can get the 1.2 version installed on Chrome?

    Jazz plugin is a "msi package" it's the same problem, i have the message "JazzControl.dll failed to register" (even with chrome installed)

    "Here's some other considerations: ..."
    Be sure I tried all of this with a clean machine, and with another one too.

    "    Make sure that your OS is behaving correctly with MIDI"
    I'm sure, I never had a midi problem. and I don't think it's a midi problem.
    For the Code editor I think it's Java or quicktime (two softwares I don't like ...)
    For the Jazz plugin I don't know.

    The Code seems to working well in Cubase, no problem.

  • Peter

    Ah, so you get "JazzControl.dll failed to register" when you try to install, not from the browser?


  • Lapin

    Yes

  • Peter

    I found this:

    that indicates a similar issue. However, it sounds like the plugin worked in Chrome regardless of that error. Can you see if that is the case?

  • Lapin

    It doesn't work, i got this:
    http://www.hostingpics.net/viewer.php?id=118546020113220735Screen.jpg
    It's a little bit better, i see the midi in/out section

    when I go to editor page, (when the midi in/out section is yellow and prompt) the device selected is the Code (usb) (it's the first on the list)
    I can't select this one but I can select the others ... but just when it's yellow, after I can select the Code
    It's the same on Firefox or Chrome

  • Lapin

    "XP unfortunately doesn't show the ports with their proper names"
    unfortunately Livid didn't make a driver ...

  • Lapin

    I found a way to install the jazz plugin (1.2) without error message
    I had to install the visual c++ library (2008)
    but it still doesn't work (firefox & chrome)

    The only change is: I see the midi in/out selector in firefox now, but not the devices
    I see my "nanokorg" inside (a very cheap 40$ master keyboard but supplied with a driver .......) but that's all (in firefox)

    I plugged my code in windows 7, my firmeware is 2.07





  • Peter

    hmm...I'm a bit stumped on this one. if possible, I'd like to take a look at this remotely. Please email me at pete at lividinstruments dot com

  • Peter

    After spending some time on Lapin's computer, it seems the issue is related to windows XP and the French language. Windows XP doesn't properly pass the port name. It lists it as "P riph rique Audio USB" - for whatever reason, XP is unable to pass the "é" character. As a result, any attempt to use this name to open a MIDI port results in failure. 

    This is just an educated guess, however, and I'm unable to confirm with my own install of XP. Can anyone confirm this?

  • Lapin

    "Can anyone confirm this?" I can !
    I just solved it !

    I edited C:\windows\inf\wdma_usb.inf
    lines 1521 & 1522 (maybe only one is enough but I don't test it)

    USB\CLASS_01.DeviceDesc="Périphérique audio USB"
    USBGenericDesc="Périphérique audio USB"

    changed to

    USB\CLASS_01.DeviceDesc="Paripharique audio USB"
    USBGenericDesc="Paripharique audio USB"

    and reinstall the driver so now the code is "Paripharique audio USB" 'I will choose a better name later ...

    Tested with Jazzplugin/java/firefox

    It works !!!






  • Lapin

    Screenshot:
    http://www.hostingpics.net/viewer.php?id=127566020613154853Screen.jpg

    Thank you very much Peter.

  • Peter

    Wow! Great work! I searched for a way to do this, and only found other people's frustrations!

    For the sake of google...
    how do I change the name of the MIDI port on windows XP for class compliant USB MIDI driver?

    Amazing! Thank you again.


  • Lapin

    That's not all, I made a "driver" (not really a driver but now the Code is recognised by the Code ID)
    because the first solution doesn't solve the conflict problem between the code and others no named devices, just change the name of the generic devices




    so I edited a second time the C:\windows\inf\wdma_usb.inf


    add this line in [Manufacturer] section:
    %Livid.Mfg%=Livid.Section

    add this two lines in [Strings] section: (end of the file)
    Livid.Mfg="Livid"
    USB\Vid_04D8&PID_FB3C&MI_00.DeviceDesc="Livid Code"


    add all of this:
    [Livid.Section]
    %USB\Vid_04D8&PID_FB3C&MI_00.DeviceDesc%=USBMIDI.Livid,USB\Vid_04D8&PID_FB3C&MI_00

    [USBMIDI.Livid]
    Include=ks.inf, wdmaudio.inf
    Needs=KS.Registration, WDMAUDIO.Registration
    CopyFiles=USBAudio.CopyList
    AddReg=USBMIDI.AddReg
    KnownFiles = USBAudio.KnownFiles

    [USBAudio.Interface.LividMIDI]
    AddReg=USBAudio.Interface.Addreg.LividMIDI

    [USBAudio.Interface.AddReg.LividMIDI]
    HKR,,FriendlyName,,%USB\Vid_04D8&PID_FB3C&MI_00.DeviceDesc%
    HKR,,CLSID,,%Proxy.CLSID%

    [USBMIDI.Livid.NT]
    Include=ks.inf, wdmaudio.inf
    Needs=KS.Registration, WDMAUDIO.Registration
    CopyFiles=USBAudio.CopyList
    AddReg=USBMIDI.AddReg
    KnownFiles = USBAudio.KnownFiles

    [USBMIDI.Livid.NT.Services]
    AddService = usbaudio,0x00000002, usbaudio_Service_Inst

    [USBMIDI.Livid.Interfaces]
    AddInterface=%KSCATEGORY_AUDIO%,"GLOBAL",USBAudio.Interface.LividMIDI,
    AddInterface=%KSCATEGORY_RENDER%,"GLOBAL",USBAudio.Interface.LividMIDI,
    AddInterface=%KSCATEGORY_CAPTURE%,"GLOBAL",USBAudio.Interface.LividMIDI,


    I used "USBDeview" to got the code ID:
    http://www.nirsoft.net/utils/usb_devices_view.html


    I think this method work with any no driver devices (on win XP)
















Add a Comment

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In with Twitter
Sign In Apply for Membership

Categories

Tagged