Scenarist 5.2 vs 5.5 about 2D

[lutinor]

Hi all,

I seen a lot of post about 5.2 vs 5.5 on many forum but i'm not sure so i need pro help :)

The question is simple :

Is it possible to 2d prj in scenarist 5.5 or you must stay in 5.2 to avoid issue ?

Thx in adv,

Max.

[mp3dom]

While with 5.5/5.6 it is possible to build 2D only projects, Sonic discourages it so if you work for replication project I suggest to stay on the safe side with 5.2/5.3

[pepelugil]

... Or use new version 5.7 that finally includes 2D and 3D in the same pack.

[lutinor]

I will test this tomorow at work

[lutinor]

I have a bug with the 5.7 version, when i mux my prj all is fine but when i take a look to my files i see this (on my stream directory) :

00000.mt2s but it's a directory and not a readable stream.

On this directory i get :

ES.list
Packet.base
Packet.info
Seek list

Wtf is that ? :(

[pepelugil]

Scenarist 5.7 uses a faster muxing engine that doesn't really create the final files, in fact they are virtual files... You need to mount the images Scenarist creates with FMXMounter to get access to the "final" files.

[lutinor]

Scenarist 5.7 uses a faster muxing engine that doesn't really create the final files, in fact they are virtual files... You need to mount the images Scenarist creates with FMXMounter to get access to the "final" files.
Just popping here a minute (my boss is near...lol).

I see the FMXMounter but my question is : When the muxing process is done, where are the final m2ts ? i don't understand how a tool can magically acess to a file if they aren't on the hdd :( (Or maybe on a tmp directory somewhere on the hdd ?)

[pepelugil]

My guess is that they are refering to the raw files you have used to create your project clips, but I don't really know it... Maybe trying to mount one of those images deleting/moving source files and see what happens will give a hint.

[lutinor]

Yea that's what i thought but actually i haven't test this way. Nonetheless you seem to have succefully test it so this 5.7 version seems '2d possible'.

Btw, i found another way : Use cmf formating to Sony standart and you get a big .dat file, change this file to 'something.iso' and you get a valid compiled version, at least it work in my total media theatre 5, in an hardware player, good question i dunno.

If someone want to share some experience about that it will be cool

[mp3dom]

You need to run both mux and image processing. Then with FMXMounter mount the Wrapping.img file (it's the virtual file that give accesso to both image and BDMV).

[lutinor]

You need to run both mux and image processing. Then with FMXMounter mount the Wrapping.img file (it's the virtual file that give accesso to both image and BDMV).
From what i remember about that i put :

-full mux and img (i will screenshot you asap)

Nonetheless, on the output directory it was very little file, even the img (10 times shorter that suposed m2ts stream.) Maybe they link to raw files 'on the fly compiled' or something like that ?

Can you tell me what box do you check ?

[rik1138]

Yea that's what i thought but actually i haven't test this way. Nonetheless you seem to have succefully test it so this 5.7 version seems '2d possible'.

Btw, i found another way : Use cmf formating to Sony standart and you get a big .dat file, change this file to 'something.iso' and you get a valid compiled version, at least it work in my total media theatre 5, in an hardware player, good question i dunno.

If someone want to share some experience about that it will be cool

Is 5.7 officially released yet? I don't see it on their site for downloading...

But this version is replacing all other versions of Sonic Scenarist (Rovi Scenarist now I suppose). There will no longer be a 2D and 3D version, just 5.7. 3D will be enabled if your activator code allows it.

I was running a beta of this a month or so ago and noticed they are using the same 'virtual mux' engine that the 3D version creates, and I absolutely HATE it... It didn't really seem that much faster when doing a mux for some reason (I suppose because it still has to read the entire elemental streams anyway to create the virtual file information), and the work flow I use requires actual files to be able to be burned to disk for testing in real Blu-ray players. These can't be burned from an ISO since we later need to update individual files, or add Java code, etc to the disc without completely re-burning the disc...

Sonic doesn't seem to think testing on actual players is really a necessity, they kept telling me I could use Sonic QC to test with... (yeah, that's going to happen! :D )

I suppose I'll have to get used to it eventually, but this is first time I've really had a good reason NOT to update to the latest version... I suspect we can find a way to make the disc burning thing work, it's just not something we had time to investigate yet...

Anyone know if it's possible to burn a BD-RE from an ISO, and then replace individual files later without re-burning the entire disc? Using Nero preferably... but if there's other options... Nero has always worked (from files though, not from ISOs), so never looked into it further...

[mp3dom]

Is 5.7 officially released yet? I don't see it on their site for downloading...

Me too. It's funny anyway that the download is not available yet but the knowledge base contains articles about version 5.7. Probably (I suppose) it's due to the Sonic Care support (maybe we need to renew it?)

[rik1138]

I have full Sonic Care support, and it's not there for me either. I'd also get an Email announcement with a new activator code as well, since it won't work with any code less than 5.7...

I've always been able to download the software that I haven't paid for though (like Cinevision, Lemony, etc), but I don't have dongles for any of them so I can't actually use them... They just seem to give everyone access to download everything.

They probably have the knowledge base stuff up already because they know that the muxing engine of 5.7 is a pretty radical change for any users that have never tried the 3D software. They want the help articles up first, then the software, so maybe it's a good sign that it's coming soon... The beta build I have is nearly final (so I was told), so they have to be really close to releasing it...

And they changed all the icons... :) I guess that's a Rovi decision...

[pepelugil]

If you have your download link for version 5.6 just change all the "6" for "7" and you'll get version 5.7

[lutinor]

Well, basically i must use the FMXMounter (and i really hate that) or i can use my tip :

Cmf sony standart and rename the big.dat in xxx.iso and after that i get my old school directory but the question is :

Is it really bd compliant ?

[rik1138]

If you have your download link for version 5.6 just change all the "6" for "7" and you'll get version 5.7

Well, technically it's version 5.6.2 (5.6 is no longer available), and the download links are Javascript. The download link for 5.6.2 is:

javascript:checkDownloadMsg(0, 35, 381, -1, 0);

Where are you downloading these from? I get them directly from Sonic's download/knowledgebase site (in the US). Maybe the international sites are different?

But either way, they shouldn't be allowing 5.6 to still be downloaded as it's outdated (and has potential bugs in it)... 5.6.2 should be the only version available in the 5.6.x range... Hopefully if you click on 5.6 you are actually getting 5.6.2...

What's the full version # of the 5.7 you are using? (in the little box that appears during load up, you should see:
5.7.0 xxxxx
where xxxxx is the actual build number of the software...

[pepelugil]

I have a direct http link to Sonic server. As for build number I don't have access to Scenarist right now, in 8 hours i'll give you that info.

EDIT:
Build number is 570B14A

[rik1138]

That's newer than my version... :) As long as you know it's coming from a Sonic server, you should be good... It's probably final (build number looks like a release number), and it might just be taking them some time getting it on the server that I use and announcing it.

[pepelugil]

Yes, it comes from docs.sonic.com

By the way I also hate new muxing engine... I hope in next version they let you choose at least if you want a full mux or this virtual muxing s**t

[Ghitulescu]

Sonic doesn't seem to think testing on actual players is really a necessity, they kept telling me I could use Sonic QC to test with... (yeah, that's going to happen! :D )

Not on BDR/E :) but on BR-ROMs.

[lutinor]

Yes, it comes from docs.sonic.com

By the way I also hate new muxing engine... I hope in next version they let you choose at least if you want a full mux or this virtual muxing s**t

My previous message is not visible by other than me or what ? :'(

Quote again :

When you mux your prj put this :
Cmf sony standart and rename the big.dat in xxx.iso and after that i get my old school directory. Conclusion you get the SAME thing but the way is...strange.

[pepelugil]

My previous message is not visible by other than me or what ? :'(

Quote again :

When you mux your prj put this :
Cmf sony standart and rename the big.dat in xxx.iso and after that i get my old school directory. Conclusion you get the SAME thing but the way is...strange.

That's also a waste of time... I want to have BDMV folder directly after muxing as with previous versions.

Having an ISO is the same to me as having a virtual mux: I have to mount that image and copy its content to the HDD in order to work with it... No thanks!

[lutinor]

That's also a waste of time... I want to have BDMV folder directly after muxing as with previous versions.

Having an ISO is the same to me as having a virtual mux: I have to mount that image and copy its content to the HDD in order to work with it... No thanks!
It's the same : when your mux is finished, you rename 1 file (you don't have to make a new long process, renaming 1 file take 1 second).

After that you use a mounter (i use elby free mounter) and that's done you see your 'old good directory'

Nonetheless i agree it's strange :s

[rik1138]

It's the same : when your mux is finished, you rename 1 file (you don't have to make a new long process, renaming 1 file take 1 second).

After that you use a mounter (i use elby free mounter) and that's done you see your 'old good directory'

Nonetheless i agree it's strange :s

The problem is, I need the BDMV directory to be _created by Scenarist_. That way, when I change something, and do a partial mux, only the files that changed are updated.

Then, when I put my disc in and start Nero, Nero searches the directory for all files with newer dates and automatically burns just those files to the disc for further testing...

That's the work flow that they've ruined by using this virtual muxer... Since the files in the BDMV folder don't, technically, exist, they can't be updated by Scenarist. Every way I can think of to actually use 5.7 adds hours of extra work (primarily because I have to either copy the BDMV out of a virtual image, or burn 40+GB BD-REs over and over).

Another thing- I can't use a mounted image in the end because I have to share the BDMV folder with others over a network (and they need to make updates in the folders). That doesn't seem to work well with mounting... But it might just need more investigation...)

By the way I also hate new muxing engine... I hope in next version they let you choose at least if you want a full mux or this virtual muxing s**t

I have spoken with Sonic at length about this, and how it affects the work flow at my company, and at least 3 of the major studios facilities as well. (Not that they'd update anyway, some of them are still using 5.1.3! :rolleyes: )

They are aware of the problem, and they are considering the possibility of allowing the user to turn this feature off for a non-3D disc (it's required for 3D work though).

The muxing engine is largely a Sony product, so I'm not entirely sure how much Sonic can do to it, but they may be the ones responsible for how the output works so maybe they can do it... I'll have to keep on them though so they don't 'forget'...

[lutinor]

You are right about the partial mux: it was VERY useful and sadly it's now impossible.

[pepelugil]

Sorry to bring back this old post, but I wanted to say that Scenarist HDMV has been updated from build number 570B14A to build number 570B21A.

New solved issues:

[SBD-1661] In case the number of extents is exceeding 10,000 on a 3D title3D title Scenarist BD issues a warning message. Some players have problems with this limitation. Please the support knowledge base for updated information regarding this problem.
[SBD-1658] In case a project does not contain stereoscopic content the ‘Initial Output Mode’ now defaults to 2D. In case the user overrides the setting a warning message is shown prior to multiplexing.

[rik1138]

Sonic still hasn't officially released this (5.7) for the US market... They must not be comfortable with it yet. :)

I assume you in another country? Do you get official announcements about it, or just Emails from a contact at Sonic?

The fact that they are changing build numbers on 5.7.0 seems to imply it's still, technically, in beta (even though they may state it's an official release).
I'm just curious what's taking them so long. I expected a release announcement on this last year...

[pepelugil]

No I don't get any official announcements about them... I just check from time to time my download link to see if a new revision has been released :)

[rik1138]

But what is the download link? They have locations they store beta builds for client testing (not intended for use for production use), and then there's the official download links that everyone can access... Just makes me curious about the builds... Seems they are still trying to solve some issues before it's a final release, looks largely based on the 3D side of things.

Still don't think I can easily use it my workflow with that new muxing engine though. I'd love to know if they are considering a way for normal muxing vs virtual muxing when doing 2D work. :)

[pepelugil]

Yes, I neither like new muxing engine.

And I don't know if I can post the full download link, but I can tell you that the files are hosted on docs.sonic.com

[rik1138]

Yes, I neither like new muxing engine.

And I don't know if I can post the full download link, but I can tell you that the files are hosted on docs.sonic.com

Yeah, probably wouldn't post the link... Even though you can't use it without the hardware dongle, probably still not approved by the forum... I can get it from Sonic (Rovi, whatever...).

I looked into the 'publicly available' downloads (public meaning people that have purchased the software that is) I have access to through the normal Sonic support login, and once I get through the hoops of logging in and agreeing to the EULA, I see the file is coming from docs.sonic.com, so that's obviously where they keep their files.

But since they haven't publicly announced a 5.7 release and provided download links for everyone, it's obviously still being worked on. Since they originally said it would be out in December, and it's not, that tells me they encountered some issue that's delaying the release...

Kinda funny actually, I hadn't even thought about this version until you posted that update. :cool:

[rik1138]

Just got the Email... Looks like 5.7 is officially released.
570B23A, downloadable at the usual locations.

Took 'em long enough...